[solved] Incorrect Screen Resolution on Boot

As the title suggests my screen has the incorrect resolution on boot. I have an Nvidia card with two monitors plugged into it.
After installing arch I found that screen was blank on boot. This could be fixed in two ways.
Unplugging one monitor from the graphic's card DVI output and plugging it into the motherboard's DVI output. This gave me the correct resolution but if It would require me to reconnect the monitor to the graphics card after I logged in and started X (configured to use twinview with nvidia)
Adding 'nomodeset' to the end of the my kernel line. This option will not require me to reconnect one monitor but uses an incorrect resolution
The second option is what I am currently using. I am wondering if there is anything I can do to fix the resolution whilst retaining the convenience of not unplugging my monitor.
Last edited by Pat55word (2012-03-17 01:03:25)

Sounds like you have the internal graphics activated in the bios even though you use a dedicated Nvidia card. If I were you, I'd deactivate the internal graphics.
Then we come to the resolution. The nvidia driver does not handle the console, so you'll have tp use either vesafb or uvesafb for it. They generally work ok, but they're limited to resolutions in your card's vbios, and in many cases the resolution you want isn't there.
Do a search on the forums and the wiki about (u)vesafb, there's plenty written about them.
Last edited by Gusar (2012-03-17 00:28:38)

Similar Messages

Screen resolution at boot time and in single user mode?

Hello!
I remember back in 10.3.8 or earlier my Mac booted right away in 1280 by 1024 pixels screen resolution, thus avoiding the video mode change when showing the progress bar.
I didn't manage to get it back to work this way.
Reset NVRAM ( a zillion times!) didn't help, nor did setting the screen mode from the admin or root account.
I'd really like to have it back!
It's no fun working in single user mode on 640 by 480.
I know this has been working with the original ATI Rage 128 and with the Radeon 7000 PCI I built in 3 years ago.
Any ideas?
Gerhard
Powermac G3 b/w Rev. B Mac OS X (10.4.7) RAM: 896 MB

Not sure if this is related enough, but I just wrestled trying to restore from time machine too, trying to reinstall 10.5.8 after putting a new HD in my MBP, 2006 vintage.
That took sooooo long to get back to where I was before swapping disks; what did the trick was ordering a free copy of Snow Leopard install disk (free due to Apple trying to push people from idisk to icloud) which was rushed FedEx (yay) and which allowed me to access Time Machine where my ancient original OSX install disk had not.
And all it took was 2 weeks of cursing!

Unable to retain screen resolution on boot/reset

Hello,
I have an external LCD connected to my mini, which has worked very well for the past few months. However, now the screen resolution that I use (1280x1024) is not applied on boot, and something along the lines of 640x480 is used (I can only judge this from the large size of the login prompt).
I can get the proper resolution by putting the system to sleep at the login screen. When I log in at the low resolution, my screen goes off to display 'resolution no supported' message. Again, I can bring back the proper resolution in this state by putting the system to sleep.
This situation is recent. The last major change before this problem, was upgrading to 10.5.4 form 10.5.3. Any help in resolving this annoying issue would be appreciated. Thanks.

Welcome to Apple Discussions, darthvinyll.
It sounds like possibly the preferences file(s) for displays has become corrupted on the mini. Probably the best thing to do at this point will be to trash the preferences file(s) associated with displays. Starting from the top level in the file system, meaning starting from the hard disk's icon within the Finder, in /Library/Preferences there should be a file labeled com.apple.windowserver.plist. Throw it in the trash. Also, for however many user accounts are on the mini, there should be files in /Users/name/Library/Preferences/ByHost that are named com.apple.windowserver.xxxxxxx.plist where xxxxxx is a random string of letters and numbers and where name is the name on the account. Throw all of those files in the trash as well, then restart the mini.
When OS X restarts and finds those files missing from their expected location, it will generate fresh copies with factory default values. That should give you a fresh start with the monitor. Good luck.

Screen resolution on Boot Camp

Hi
I bought a macbook whitch Screen resolution is 2650 x 1600, and installed Windows 8 by bootcamp so I expected to see very small screen of my apps. For my surprise most screens are too large.
But Java script application screen its so high resolution that I cant read fonts.
Is there a way to solve it ?
Moises

In Windows 8 use the help menu and search for external display.

[Solved] Set Screen Resolution in Openbox

Is there a utility to set the screen resolution in Openbox?
Last edited by Wintervenom (2008-09-26 07:43:03)

You can make an Openbox submenu with various xrandr settings.
Like so:
<menu id="res-menu" label="Resolution">
<separator label="Resolution"/>
<item label="1280x1024">
<action name="Execute">
<execute>
xrandr -s 1280x1024
</execute>
</action>
</item>
<item label="1024x768">
<action name="Execute">
<execute>
xrandr -s 1024x768
</execute>
</action>
</item>
<item label="800x600">
<action name="Execute">
<execute>
xrandr -s 800x600
</execute>
</action>
</item>
Of course, you need to have those modes defined in xorg.conf.
Last edited by moljac024 (2008-09-26 00:06:37)

[SOLVED] Changing screen resolution with xrandr.

Been googling around after a way to change my screen resolution.
I'm on a Acer Aspire Timeline 3810t with the resolution 1366x768.
I wanted to change my resolution to something like 1900x1200 and found a guide explaining how to do this with xrandr.
This is what I did:
jorgen ~ $ xrandr
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
LVDS1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm
1366x768 60.0*+
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
TV1 disconnected (normal left inverted right x axis y axis)
jorgen ~ $ cvt 1900 1200
# 1904x1200 59.93 Hz (CVT) hsync: 74.61 kHz; pclk: 191.00 MHz
Modeline "1904x1200_60.00" 191.00 1904 2032 2232 2560 1200 1203 1213 1245 -hsync +vsync
jorgen ~ $ xrandr --newmode "1904x1200_60.00" 191.00 1904 2032 2232 2560 1200 1203 1213 1245 -hsync +vsync
jorgen ~ $ xrandr --addmode LVDS1 1904x1200_60.00
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 150 (RANDR)
Minor opcode of failed request: 18 (RRAddOutputMode)
Serial number of failed request: 33
Current serial number in output stream: 34
Does anybody have an idea about what I am doing wrong, or why I get this error?
Last edited by jorg1 (2011-03-12 04:20:39)

jorg1 wrote:
Ok, I found some good documentation - the wiki. (Been in ubuntu so long that I forgot to check the official documentation before going to the forums :S)
Made myself a 10-monitor.conf file:
Section "Monitor"
Identifier "Monitor0"
EndSection
Section "Device"
Identifier "Device0"
Driver "intel"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 16
Modes "1900x1200_60.00" #Choose the resolution
EndSubSection
EndSection
But it still won't switch to any other resolution than 1366x768. Anybody see anything wrong with this?
Good, you've learnt to use the wiki, please do that first from now on (google as well). Also, please use code-tags, makes it easier to read code/conf-files.
It looks like you're trying to set your laptop screen to a resolution higher than it can go. Hint: not possible. If you had an external screen with a higher res then you could use that, but the resolution is limited both by the screen and the graphics card, and I haven't heard of any laptop screen with such a high resolution.

[SOLVED] Black screen after kernel boot after pacman -Syu

Hi, after full system upgrade with pacman -Syu, I get after the kernel boot black screen and everything is freezing. Then need to manually shut down the power button!
Normally when my system starts up after the kernel boot I get straight to the command line terminal login.
Can anybody help me how to fix this? Any clues? Any advice is welcome!
The problem is solved by downgrading to kernel 3.6.11.-1
Many thanks for the help from the people on #archlinux !
Last edited by OpenEye (2013-01-29 05:14:04)

jasonwryan wrote:
Please stop bumping your thread: use the edit button
https://wiki.archlinux.org/index.php/Fo … te#Bumping
What have you done about the errors being printed to your logs? You could start by fixing the network error and the broken udev rule...
Are you still using intiscripts? They are no longer supported: https://www.archlinux.org/news/end-of-i … s-support/
# edit: not a pacman issue, moving to Newbie Corner
I have searched for many hours and days for solutions on the internet and forums, tried some things, but with no results! I don't know how to fix the errors! Do you know how to fix that? I'm a total n00b! I'm doing my best as I can! Need help, thanks!

[solved]Different Screen Resolution for different Users[/solved]

hello
i'm running kdemod
i'd like to set up an account for my mum
she prefers a resolution of 800X600
whereas i like 1024X768
my xorg.conf is set up like
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "1024x768 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
when i log into the newly created account and use nvidia-settings
the resolution can be changed successfully
but upon restarting
it reverts back to 1024X768
i'd like to know how i could set up different resolutions for both of us
Last edited by nikbhardwaj (2009-10-03 12:23:21)

arkham wrote:You could add a startup script for your user with "xrandr -s 1024x768", while adding another for your mother account with "xrandr -s 800x600"
where do i add this
.xinitrc in the home directory ??
or .xsession in the home directory

[SOLVED] Virtual screen resolution in xorg.conf being ignored

I'm trying to configure a dual monitor set up but xrandr is telling me the max screen size is 1600x1600. I have already enterd a virtual resolution in xorg.conf.
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection
Section "Files"
EndSection
Section "Module"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Virtual 2832 1050
EndSubSection
EndSection
When I first installed Arch I was using the radeon drivers. I had no problem configuring my monitors the way I wanted. Now I'm using catalyst and getting errors.
Am I just doing something wrong?
Last edited by thetoxikavenger (2010-06-06 15:58:18)

I didn't really fix the issue with xrandr, but I did manage to get my dual monitors to work with Xinerama.

[SOLVED] Black screen halfway through boot before login screen appears

I originally installed my Arch Linux 64 system on a quad core intel cpu with 4GB RAM and a Nvidia 9600 GT graphics card. Arch is installed on 2 500 GB HDD running on software RAID and LVM. A few months ago I decided I wanted to upgrade my machine to an i7-2600K with 8 GB RAM and a Nvidia 580 GTX graphics card. Since I was using pure software RAID I knew that I could just reuse my installation. So I popped in the drives into the new machine and glory glory Arch booted just fine. One thing I notied though and this has been bothered me since then. On my old machine I could see the whole boot process from start to finish. On my new machine I only see the first few seconds and then a black screen for few seconds and then I get the login screen (KDM in my case). Now I'm running a pure systemd system and I can see the boot process until
[ok] started loading random ...
and then the black screen sets in. Why does this happen? Why can't see if udev, samba etc. start correctly anymore?
Last edited by fettouhi (2012-10-11 21:46:56)

DSpider wrote:Then remove Nouveau completely, undo any changes to mkinitcpio.conf, and re-generate your initramfs.
I don't have the nouveau driver installed at all. But I finally got rid of the black screen. I simply added nomodeset to the kernel parameters in grub and now everything ass before.

[Solved] Login Screen Dim on Boot-Up

I was having a problem with my new Arch Enlightenment 18 install using the SLiM login manager on my Lenovo X220. The login screen was dim, but once logged in, the screen was normal brightness. I don't think SLiM itself was causing the dim login screen, but I found the solution!
# systemctl mask systemd-backlight@acpi_video0.service
Actually I stopped the service first, then disabled it, then masked it, however It was the masking of the systemd service that was required.
Found tip from following thread.
https://bbs.archlinux.org/viewtopic.php?id=171227

iTwenty wrote:Have you tried setting own_window to no?
When I do, I conky doesn't load at all.
EDIT: It works, but it's hidden by my PCManFM Wallpaper. I have to not set a wallpaper to see it...
KingX wrote:Are you using double buffer for conky? This is a good topic where users using different DE and WM are sharing their conkyrc files. You should take a look and compare your conkyrc.
Nope, not using double buffer. I've tried different settings here and there to no avail.
Last edited by Ward (2011-11-26 14:50:23)

[SOLVED]Screen resolution began to be incorrectly detected

After installing some packages not having obvious relations to video issues (mysql and zfs related packages), the screen resolution on my 1280x1024 screen began to be set as 1024x768 without 1280x1024 in the list of possible modes. I tried to X -configure but to no avail. Reinstalling xorg-server also didn't help. I tried to manually detect and add 1280x1024 mode with xrandr, this mode began to appear in the modes list, but the resolution remains 1024x768 when it's selected.
I have an ancient SiS videocard, but it worked OK with the standard vesa driver.
What can be the cause of this issue and how it could be corrected?
Some fragments of Xorg log:
[ 769.623] (II) VESA(0): Total Memory: 512 64KB banks (32768kB)
[ 769.623] (II) VESA(0): Monitor0: Using default hsync range of 31.50-48.00 kHz
[ 769.623] (II) VESA(0): Monitor0: Using default vrefresh range of 50.00-70.00 Hz
[ 769.623] (II) VESA(0): Monitor0: Using default maximum pixel clock of 65.00 MHz
[ 769.623] (WW) VESA(0): Unable to estimate virtual size
[ 769.623] (II) VESA(0): Not using built-in mode "1600x1200" (no mode of this name)
[ 769.623] (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
[ 769.623] (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
[ 769.623] (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
[ 769.623] (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
[ 769.623] (WW) VESA(0): No valid modes left. Trying less strict filter...
[ 769.623] (II) VESA(0): Monitor0: Using hsync range of 31.50-48.00 kHz
[ 769.623] (II) VESA(0): Monitor0: Using vrefresh range of 50.00-70.00 Hz
[ 769.623] (II) VESA(0): Monitor0: Using maximum pixel clock of 65.00 MHz
[ 769.623] (WW) VESA(0): Unable to estimate virtual size
[ 769.623] (II) VESA(0): Not using built-in mode "1600x1200" (hsync out of range)
[ 769.623] (II) VESA(0): Not using built-in mode "1280x1024" (hsync out of range)
[ 769.623] (--) VESA(0): Virtual size is 1024x768 (pitch 1024)
[ 769.623] (**) VESA(0): *Built-in mode "1024x768"
[ 769.623] (**) VESA(0): *Built-in mode "800x600"
[ 769.623] (**) VESA(0): *Built-in mode "640x480"
[ 769.623] (==) VESA(0): DPI set to (96, 96)
[ 769.623] (II) VESA(0): Attempting to use 60Hz refresh for mode "1024x768" (118)
[ 769.624] (II) VESA(0): Attempting to use 60Hz refresh for mode "800x600" (115)
[ 769.624] (II) VESA(0): Attempting to use 60Hz refresh for mode "640x480" (112)
// Another fragment:
[ 769.384] (II) LoadModule: "glx"
[ 769.384] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 769.392] (II) Module glx: vendor="X.Org Foundation"
[ 769.392] compiled for 1.16.0, module version = 1.0.0
[ 769.392] ABI class: X.Org Server Extension, version 8.0
[ 769.392] (==) AIGLX enabled
[ 769.392] (II) LoadModule: "vesa"
[ 769.393] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 769.395] (II) Module vesa: vendor="X.Org Foundation"
[ 769.395] compiled for 1.16.0, module version = 2.3.2
[ 769.395] Module class: X.Org Video Driver
[ 769.395] ABI class: X.Org Video Driver, version 18.0
[ 769.395] (II) VESA: driver for VESA chipsets: vesa
[ 769.395] (++) using VT number 1
[ 769.395] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 769.395] (II) Loading sub module "vbe"
[ 769.395] (II) LoadModule: "vbe"
[ 769.396] (II) Loading /usr/lib/xorg/modules/libvbe.so
[ 769.396] (II) Module vbe: vendor="X.Org Foundation"
[ 769.396] compiled for 1.16.0, module version = 1.1.0
[ 769.396] ABI class: X.Org Video Driver, version 18.0
[ 769.396] (II) Loading sub module "int10"
[ 769.396] (II) LoadModule: "int10"
[ 769.398] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 769.399] (II) Module int10: vendor="X.Org Foundation"
[ 769.399] compiled for 1.16.0, module version = 1.0.0
[ 769.399] ABI class: X.Org Video Driver, version 18.0
[ 769.399] (II) VESA(0): initializing int10
[ 769.421] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[ 769.424] (II) VESA(0): VESA BIOS detected
[ 769.424] (II) VESA(0): VESA VBE Version 3.0
[ 769.424] (II) VESA(0): VESA VBE Total Mem: 32768 kB
[ 769.424] (II) VESA(0): VESA VBE OEM: SiS
[ 769.424] (II) VESA(0): VESA VBE OEM Software Rev: 1.0
[ 769.424] (II) VESA(0): VESA VBE OEM Vendor: Silicon Integrated Systems Corp.
[ 769.424] (II) VESA(0): VESA VBE OEM Product: 6330
[ 769.424] (II) VESA(0): VESA VBE OEM Product Rev: 3.72.10
[ 769.448] (==) VESA(0): Depth 24, (--) framebuffer bpp 32
[ 769.448] (==) VESA(0): RGB weight 888
[ 769.448] (==) VESA(0): Default visual is TrueColor
[ 769.448] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 769.448] (II) Loading sub module "ddc"
[ 769.448] (II) LoadModule: "ddc"
[ 769.448] (II) Module "ddc" already built-in
[ 769.533] (II) VESA(0): VESA VBE DDC supported
[ 769.533] (II) VESA(0): VESA VBE DDC Level none
[ 769.533] (II) VESA(0): VESA VBE DDC transfer in appr. 0 sec.
[ 769.576] (II) VESA(0): VESA VBE DDC read failed
[ 769.576] (II) VESA(0): Searching for matching VESA mode(s):
Last edited by nbd (2014-08-05 09:17:50)

I tried the 'xf86-video-sis' from the official repositories, but it didn't work: 'X -configure' outputs that no devices are found.
The command
# lspci | grep SiS
gives the output:
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 662 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] LPC Controller (rev 36)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE Controller (rev 01)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller (rev a0)
00:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.2 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.3 USB controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
00:05.0 IDE interface: Silicon Integrated Systems [SiS] SATA (rev 01)
00:1f.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (rev 04)
The command 'X -configure' with the 'xf86-video-vesa' driver produces the following xorg.conf file:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
Identifier "Card0"
Driver "vesa"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
The X server is started via startxfce4 in the ~/.xinitrc file:
#!/bin/sh
# ~/.xinitrc
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
exec startxfce4
I tried to use the recommendations about using xrandr. The command
# cvt 1280 1024
produces the following:
# 1280x1024 59.89 Hz (CVT 1.31M4) hsync: 63.67 kHz; pclk: 109.00 MHz
Modeline "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync
Then I perfrom the following two commands:
# xrandr --newmode "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync
# xrandr --addmode default "1280x1024_60.00"
This adds the 1280x1024 mode to the list of available modes in the display control panel, but when
this mode is selected - nothing happens and the resolution remains the same: 1024x768.
EDIT:
I tried all three SiS drivers from the repository: sis, sisusb and sisimedia. In all three cases 'X -configure' failed with an error message: "No devices to configure". The strange thing is that the vesa driver worked OK out of the box. What could cause such a strange problem with the screen resolution?
EDIT 2:
The cause of the problem was the cable from the monitor to the computer: it was twisted and apparently was causing some aberrations to the signal. I found out it when added to the xorg.conf file the line HorizSync = 58-61. After adding that line the problem disappeared. I began to think why the things previously have been working OK without that line. And supposed that the matter is in hardware. I straighted out the cable and the problem isn't occuring anymore even without the xorg.conf editings.
Last edited by nbd (2014-08-04 17:58:13)

Screen resolution when PXE boot from WDS vs Install Windows 8.1 from USB

Hi all
I own a Lenovo ThinkPad T430s, X230 Tablet, and now have my hands on a T440. All three machines have UEFI Secure Boot enabled properly, i.e. Windows boot screen shows Lenovo logo instead of Windows logo.
However, if I do a PXE boot (using Windows Deployment Services from Windows Server 2012, not R2) and boot to the same boot.wim provided on a Windows 8.1 ISO image, the boot screen resolution turns crap, and the WinPE environment runs in 640x480. Also, as opposed
to the Lenovo logo showing on the boot screen, the Windows logo shows up instead, indicating it's not doing a secure boot?
When booting from a USB stick however, using the same Windows 8.1 boot.wim (copied from ISO), the screen resolution in Windows Setup is detected correctly, and the Lenovo logo shows up.
This occurs on all three machines since MDT was upgraded to MDT 2013 or when I replaced Windows 8 boot.wim with Windows 8.1 boot.wim (as the Windows ADK 8 --> ADK 8.1).
Is there a fix for this? Do others have the same problem elsewhere?
Many thanks

Hi,
When boot UEFI-based computer from PXE you should take more into consideration.
For some computers, you might have to perform additional steps to make sure that Windows is installed in UEFI mode, and not in legacy BIOS-compatibility mode.
Some computers might support UEFI. However, they do not support a PXE-initiated boot when in UEFI mode.
How to Create a PXE-Initiated Windows 8 Deployment for UEFI-Based or BIOS-Based Computers in Configuration Manager
http://technet.microsoft.com/en-us/library/jj938037.aspx
Especially for “Pre-Deployment Considerations”
If you still cannot find a way to make it boot from UEFI mode, you should contact with manufacture to confirm if PXE-initiated boot is supported.
Hope this helps.

Screen resolution in Vista Ultimate in Boot camp cant' select HD

I am using a new imac 24" and can only seem to increase the screen resolution to 1600 x1200.
Shouldn't I be able to select HD 1080 x 1900

Best I can think of if your iMac has Nvidia chipset...
Download graphic driver directly from Nvidia.
Uninstall and delete the Apple driver.
Boot into Safe Mode and run "Driver Sweeper" (found on Guru3D along with instructions).

IMac/Boot Camp Screen Resolution Issue on XP

Anyone here running Boot Camp on an iMac? I just loaded it on my MBPro and it works great, but on my iMac I can't get the screen resolution straight. My images are stretched when shown in XP. It's a 24" iMac.
Thanks

Post your question in the Boot Camp discussions:
http://discussions.apple.com/forum.jspa?forumID=1165

[solved] Incorrect Screen Resolution on Boot

Similar Messages

Maybe you are looking for