[i845] Intrepid Ibex not compatible with Intel(R) 82845G/GL/GE/PE/GV Graphics Controller

[Olivier Jacquet]

I've got a motherboard with an on-board Intel(R) 82845G/GL/GE/PE/GV Graphics Controller. When starting X with the "i810" driver the screen stays black. The only way I can get it to work is with the "vesa" driver. It works find under Windows though. Which info is needed to investigate this further.

[Olivier Jacquet (ojacquet)]

With "noapic acpi=off nolapic" I does not black out so it's probably not related to the graphics chipsets.

[Olivier Jacquet (ojacquet)]

The above comment is incorrect. I've just updated the title and description to properly describe the issue.

[Bernd Schlapsi (bernd-sch)]

I've also got a notebook with an on-board Intel(R) Intel 82845G/GL Graphic Controller. The screen stays black after the usplash screen.

With with the boot-option you mentioned before ("noapic acpi=off nolapic") my notebook doesn't black out anymore

[Bryce Harrington (bryce)]

Hi ojacquet,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

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

[Naxa (anaxagramma)]

I've got the same problem. With "noapic acpi=off nolapic" options gdm is able to start, but I've noticed that if I log out or press Ctrl-Alt-Backspace, then X is not able to restore itself and the blank black screens comes back again. Also, on my computer these options make the Console Terminal 1-6 look wierd, with very big "font" size and much lesser lines and coloumns than expected (I don't know if this is normal or trivial, I've just wanted to mention.)

[Naxa (anaxagramma)]

(p.s. when the black screen comes up, my monitor actually turns it's led from orange to green, and it seems that it thinks that there is a signal.)

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.