Bug 740746 - vesa fallback mode do not work on HP8440p
Summary: vesa fallback mode do not work on HP8440p
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-nouveau
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ben Skeggs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-23 07:58 UTC by Tomas Pelka
Modified: 2011-09-23 13:20 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-23 13:20:56 UTC


Attachments (Terms of Use)
dmesg (49.57 KB, text/plain)
2011-09-23 08:15 UTC, Tomas Pelka
no flags Details
Xorg.log (9.76 KB, text/plain)
2011-09-23 08:16 UTC, Tomas Pelka
no flags Details

Description Tomas Pelka 2011-09-23 07:58:47 UTC
Description of problem:
Not able to start X when booting with nomodeset rdblacklist=nouveau 


Version-Release number of selected component (if applicable):
kernel-2.6.32-201.el6.x86_64
xorg-x11-drv-nouveau-0.0.16-13.20110719gitde9d1ba.el6.x86_64
xorg-x11-drv-vesa-2.3.0-2.el6.x86_64
xorg-x11-server-Xorg-1.10.4-3.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Boot up with nomodeset rdblacklist=nouveau
2.
3.
  
Actual results:
No X start, log attached

Expected results:
X should start using vesa driver.

Additional info:
Possible regression 6.1 worked fine.

01:00.0 VGA compatible controller [0300]: nVidia Corporation GT218 [NVS 3100M] [10de:0a6c] (rev a2)

Comment 2 Tomas Pelka 2011-09-23 08:15:37 UTC
Created attachment 524548 [details]
dmesg

Comment 3 Tomas Pelka 2011-09-23 08:16:22 UTC
Created attachment 524549 [details]
Xorg.log

Comment 4 Ben Skeggs 2011-09-23 08:58:17 UTC
Hmm, strange.  X didn't even try to load vesa from the looks of it.  I'm not 100% sure if it's even supposed to if there's and xorg.conf, I think perhaps not.

Does it autoload vesa if you get rid of it?

Also, any particular reason for disabling nouveau, should we have a bug for that too?

Comment 5 Tomas Pelka 2011-09-23 09:10:46 UTC
Ohh crap I forgot on ol xorg.conf.

So you are right removing xorg.conf will fix this.

So I think NOTABUG, or?

BTW speaking about balcklisting, it acts same in moth cases (blacklist/not blacklist).

Comment 6 Ben Skeggs 2011-09-23 09:23:42 UTC
Yep, if that fixes it it'd be find to close as NOTABUG.

Yeah, blacklisting isn't necessary with nomodeset.  Nouveau will load, but it won't actually touch the device at all.


Note You need to log in before you can comment on or make changes to this bug.