Bug 29222 - X cannot start up, screen flickers in console mode
X cannot start up, screen flickers in console mode
Status: CLOSED UNREPRODUCIBLE
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel)
All Linux
: P1 normal
Assigned To: drivers_video-dri
:
Depends on:
Blocks: 27352
  Show dependency treegraph
 
Reported: 2011-02-16 08:56 UTC by Johannes Berg
Modified: 2011-02-21 21:07 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.38-rc5
Tree: Mainline
Regression: Yes


Attachments

Description Johannes Berg 2011-02-16 08:56:01 UTC
This is a regression from 2.6.37 that has been there throughout the RCs -- on my macbook 5,1 the X server now refuses to start up and the screen just flickers in console mode. I can press ctrl-alt-del to reboot.

The device is

02:00.0 VGA compatible controller: nVidia Corporation C79 [GeForce 9400M] (rev b1) (prog-if 00 [VGA controller])
	Subsystem: Apple Computer Inc. Device 00aa
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 256 bytes
	Interrupt: pin A routed to IRQ 23
	Region 0: Memory at 92000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at 80000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at 90000000 (64-bit, prefetchable) [size=32M]
	Region 5: I/O ports at 1000 [size=128]
	Expansion ROM at 93000000 [disabled] [size=128K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Kernel driver in use: nouveau
Comment 1 Johannes Berg 2011-02-18 11:39:53 UTC
Err, ok, upon closer investigation it seems that I didn't even have nouveau even though it says "Kernel driver in use: nouveau"?? Or the recent nouveau fixes fixed it now, not sure. In any case, it's gone.

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