Created attachment 428776 [details] xorg.0.log file Description of problem: it is display problem and LCD resolution is only limited to 1024x768, but it supports upto 1600x900. It is default using vesa, while on-system, Intel and nvidia cards, while those are not detected. even installation only possible with text mode (or vnc) Version-Release number of selected component (if applicable): kernel-2.6.33.5-124.fc13.x86_64 kernel-2.6.33.3-85.fc13.x86_64 kernel-2.6.35-0.15.rc3.git3.fc14.x86_64 xorg-x11-drv-intel-2.11.0-5.fc13.x86_64 xorg-x11-drv-nv-2.1.15-5.fc13.x86_64 xorg-x11-drv-nouveau-0.0.16-7.20100423git13c1043.fc13.x86_64 xorg-x11-drv-vesa-2.3.0-1.fc13.x86_64 How reproducible: 100% Steps to Reproduce: 1. gnome-display-properties 2. 3. Actual results: resolution is only 1025x768 Expected results: can be 1600x900 Additional info: [aalam@zhawk]$ lspci 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) 00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) 00:19.0 Ethernet controller: Intel Corporation 82577LC Gigabit Network Connection (rev 05) 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) 00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05) 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05) 00:1f.2 RAID bus controller: Intel Corporation Mobile 82801 SATA RAID Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05) 01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 330M] (rev a2) 01:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev a1) 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) 03:00.0 SD Host controller: Ricoh Co Ltd Device e822 03:00.1 System peripheral: Ricoh Co Ltd Device e230 03:00.4 SD Host controller: Ricoh Co Ltd Device e822 3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02) 3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02) 3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) 3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02) 3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02) 3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
vesa is supported only 1024x768. nouveau driver failed to show display, while system has "01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 330M] (rev a2)". (currently working with vesa, if removed /etc/X11/xorg.conf, no display, will that Xorg.0.log can be usefull?) trying to get VBIOS using [1], update bug after getting that [1] http://cgit.freedesktop.org/~stuart/vbtracetool/
This is likely a dup of another bug I seen recently, can you provide the output of "dmesg". Thanks :)
Created attachment 431632 [details] myvga.rom file
Created attachment 431633 [details] deloopd logfile with postandrestore.bash
Created attachment 431636 [details] deloopd logfile with postandrestore.bash - Updated
Created attachment 431747 [details] dmesg file
Can I see the dmesg from removing nomodeset, and your xorg.conf so vesa isn't used? It's the only way I'll be able to see what's wrong with the real driver. Vesa's available modes depend on what your video bios allows, and isn't something we can fix. Also, the ROM image you posted is from an Intel GPU.
without nomodeset, not able to boot machine (now reboot again to confirm) Current (working) Display is with nomodeset + xorg.conf with vesa only
Can you attach /var/log/messages then please, hopefully from a failed boot some useful info made it there.
Created attachment 431959 [details] /var/log/messages attached
Can you configure your bios to put the GPU into speed mode (rather than switchable graphics), and remove nomodeset and see what happens? Then, can you also try putting your GPU into stamina mode and do the same?
(In reply to comment #11) > Can you configure your bios to put the GPU into speed mode (rather than > switchable graphics), and remove nomodeset and see what happens? > Sorry, but there is no entry in bios to Enable/disable/change GPU:-( only have hardware switch to Speed/Auto/Stamina (which is not working properly in Linux).
Created attachment 434582 [details] new VGA.rom file Tried to Switch SPEED mode by hardware button and then got this vga.rom file in VT in init 3 mode
during more testing MODE: SPEED - SPEED LED glow /postandrestore.bash -d 2> logfile Step - Laptop Hanged Mode: STAMINA - SPEED LED glow /postandrestore.bash -d 2> logfile - logfile produced Mode: Auto - AUTO/SPEED LEDs glow (both) /postandrestore.bash -d 2> logfile - Laptop Hanged
I believe this is a related bug to 618481 as well as the following report: http://www.mail-archive.com/nouveau@lists.freedesktop.org/msg05678.html My laptop is a Sony Vaio VPCZ1190X with nvidia 330M GT and experience identical failure modes to those listed in the bug reports.
This is a dupe of my bug, Ben. You've fixed it to some extent in F14 already. I haven't tested it without the BIOS hack that lets you 'hide' the system's other graphics card, though, it may still be broken in that case. A S, I sent a link to the mailing list with a guide to hacking the BIOS to expose the control you need. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** This bug has been marked as a duplicate of bug 596562 ***
It is still broken without the BIOS hack. BIOS hack fixes it though. You also need to remove "nomodeset" parameter from the kernel parameters.
the inability of X / kernel / whatever to cope with the configuration where both video cards are available to the system is a separate bug. I wasn't going to bother filing that one till at least both basic bugs (inability of either card to work at all) were fixed; the nvidia card is now fixed to some degree, but the intel one still doesn't work at all. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers