[Lucid] blank screen after gdm login intel 945GM works with nomodeset

[whwi]

login works with nomodeset

does not work with Linux 2.6.33-020633-generic kernel upstream

i think is an intel driver or kernel KMS problem

after login i get an blank black screen and hear the login sound but nothings works
only hard reset and boot with nomodset

(log files are from the nomodset boot)

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+3ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic x86_64
Architecture: amd64
Date: Tue Mar 30 03:37:50 2010
DkmsStatus:
 virtualbox-ose, 3.1.4, 2.6.32-17-generic, x86_64: installed
 virtualbox-ose, 3.1.4, 2.6.32-16-generic, x86_64: installed
 virtualbox-ose, 3.1.4, 2.6.32-18-generic, x86_64: installed
 virtualbox-ose, 3.1.4, 2.6.31-20-generic, x86_64: installed
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Apple Inc. MacBook2,1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-18-generic root=UUID=b6defade-07b5-4fd2-9c4e-369afe7c8314 ro quiet splash nomodeset
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
dmi.bios.date: 06/27/07
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB21.88Z.00A5.B07.0706270922
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F4208CAA
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F4208CAA
dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA:
dmi.product.name: MacBook2,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-18-generic

[Davidiam (hectorjerezano)]

I had same issue until I saw this error using kernel 2.6.31 in the kernel.log ;
i915 0000:00:02.0: LVDS-1: no EDID data
fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver

so did a search on google and found that the framebuffer that the kernel has for default is the "efifb" and that i915 or inteldrmfb was trying to by the fb , then seens I had to customized my dstd and change the cpu to atom following this http://ubuntuforums.org/showthread.php?t=1341580
 I downloaded the source for 2.6.32 recompile my kernel with the option CONFIG_FB_EFI=NO and also but sure if necessary CONFIG_DRM_I915_KMS=NO and then add the kms manually in grub kernel options as i915:modeset=1.
And now my screen is correctly detected no more errors of EDID nor conflicting fb.

[Jeremy Foshee (jeremyfoshee)]

Hi whwi,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[whwi (whitewindow)]

lucid lts works for me

thx
close the bug ?

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]