[Jaunty] 82865G Integrated Graphics Controller fails to load X

[Edmundo]

Since I moved to jaunty from intrepid (dist-upgrade) about 2 weeks ago I haven't been able to use the intel driver on my box. It simply doesn't work. sat down yesterday and collected xorg logs for you to see.

At first (say... two weeks ago) I got a kdm screen (use kubuntu) that looked almost normal... but there were some artifacts showing up when I moved my my mouse around.... and I couldn't type a thing. alt+ctrl+backspace didn't work. I couldn't get to the VTs... and I couldn't alt-ctrl-del either. The only way out was to press the power button opf my box and wait for it to reboot (at least that did work).

Yesterday when I was doing the text, when I ran "X" from the terminal, I got a black screen and never got to the "net" (you know... (X background). Key's didn't work.... and not even pressing the power button worked. I had to use the alt-SysRq keys to reset it.

This is my lspci:
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:02.0 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI (rev 03)

Here's the xorg.conf created with Xorg -config:
Section "ServerLayout"
        Identifier "X.org Configured"
        Screen 0 "Screen0" 0 0
        InputDevice "Mouse0" "CorePointer"
        InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
        ModulePath "/usr/lib/xorg/modules"
        FontPath "/usr/share/fonts/X11/misc"
        FontPath "/usr/share/fonts/X11/cyrillic"
        FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
        FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
        FontPath "/usr/share/fonts/X11/Type1"
        FontPath "/usr/share/fonts/X11/100dpi"
        FontPath "/usr/share/fonts/X11/75dpi"
        FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
        Load "extmod"
        Load "dbe"
        Load "dri"
        Load "dri2"
        Load "record"
        Load "glx"
EndSection

Section "InputDevice"
        Identifier "Keyboard0"
        Driver "kbd"
EndSection

Section "InputDevice"
        Identifier "Mouse0"
        Driver "mouse"
        Option "Protocol" "auto"
        Option "Device" "/dev/input/mice"
        Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
        Identifier "Monitor0"
        VendorName "Monitor Vendor"
        ModelName "Monitor Model"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
        ### [arg]: arg optional
        #Option "NoAccel" # [<bool>]
        #Option "SWcursor" # [<bool>]
        #Option "ColorKey" # <i>
        #Option "CacheLines" # <i>
        #Option "Dac6Bit" # [<bool>]
        #Option "DRI" # [<bool>]
        #Option "NoDDC" # [<bool>]
        #Option "ShowCache" # [<bool>]
        #Option "XvMCSurfaces" # <i>
        #Option "PageFlip" # [<bool>]
        Identifier "Card0"
        Driver "intel"
        VendorName "Intel Corporation"
        BoardName "82865G Integrated Graphics Controller"
        BusID "PCI:0:2:0"
EndSection

Section "Screen"
        Identifier "Screen0"
        Device "Card0"
        Monitor "Monitor0"
        SubSection "Display"
                Viewport 0 0
                Depth 1
        EndSubSection
        SubSection "Display"
                Viewport 0 0
                Depth 4
        EndSubSection
        SubSection "Display"
                Viewport 0 0
                Depth 8
        EndSubSection
        SubSection "Display"
                Viewport 0 0
                Depth 15
        EndSubSection
        SubSection "Display"
                Viewport 0 0
                Depth 16
        EndSubSection
        SubSection "Display"
                Viewport 0 0
                Depth 24
        EndSubSection
EndSection

The log is the attachment

[Edmundo (eantoranz)]

There's the xorg.log with NO xorg.conf

[Richard Seguin (sectech)]

Thank you for reporting this issue. Are you able to login via a text terminal at all (pressing CTRL-ALT-F1)? Also they disabled the CTRL-ALT-BACKSPACE sequence in Jaunty for reasons I don't completely agree with.

I have looked around at your video chipset and noticed that other issues have been reported, such as bad rendering against it so I don't have a problem with confirming this issue after a bit of troubleshooting.

So you have tried with and without an xorg.conf file. I am curious which situation actually gave you the basic X screen and if any error messages followed once you got it. X no longer requires xorg.conf and it is generally recommended to use X without it, but of course you can tweak it as I did with mine. One thing for sure is that your old xorg.conf will not (at least with my experience) work with Jaunty, you would need to create a new one as xorg has changed frequently.

If you can get to a text login can you please run:

sudo apt-get-update
sudo apt-get upgrade
sudo apt-get install (just to make sure we didn't miss anything)

after the updates ran through please reboot your computer and report if there were changes.

Thanks,

Richard Seguin

[Richard Seguin (sectech)]

I have flagged this issue as incomplete and set the status as medium as it appears as it is related to your chipset. Please leave the bug at incomplete until we have enough information, I will then mark it as triaged.

I also changed the title of your bug to something that states your chipset, that way if others are having the same issue they can reference the same bug.

Thanks,

Richard Seguin

[Edmundo (eantoranz)]

I just updated my box. Removed the xorg.conf and rebooted.

I got to kdm, I was able to see kdm's background, I was able to move
the mouse around... however, there was nothing else displayed from kdm
(just the background), I couldn't use the keyboard (not even the caps
lock led turned on / off), I couldn't get to the VTs. So I used the
alt-SysRq keys (I didnt test pressing the power button, though....
sorry) to restart. So... right now I'm using the same xorg.conf that
xorg created for me with Xorg -config with the driver saying "vesa"
instead.

There goes the log

[Edmundo (eantoranz)]

I just tested the driver that was downloaded on the update (like 15 minutes ago).

When kdm starts, I get to see its background, but no other thing shows up. I get to move the mouse around. Can't get to the VTs. Caps lock doesn't switch (at least, there's no led blinking). The power button was able to shut down the box, only that there was no change in the kdm background till a little before booting (a lot of color noise showed up). Then the box shut down gracefully.

[Richard Seguin (sectech)]

Unfortunately there isn't much we can do in terms of troubleshooting without you getting to a VT of some kind. Did you install openssh where you might be able to ssh into the box? If so you can run sudo chmod -x /etc/init.d/kdm then restart the box.

[Bryce Harrington (bryce)]

Richard: https://wiki.ubuntu.com/X/NonGraphicalBoot

[Edmundo (eantoranz)]

Sure.... I can use my wife's laptop to come into the box remotely.
Just tell me what you need.

Would a backtrace help?

On Wed, Mar 18, 2009 at 7:08 PM, Bryce Harrington
<email address hidden> wrote:
> Richard: https://wiki.ubuntu.com/X/NonGraphicalBoot
>
> --
> [Jaunty] 82865G Integrated Graphics Controller fails to load X
> https://bugs.launchpad.net/bugs/343690
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Richard Seguin (sectech)]

Bryce: This is why launchpad is so great, didn't even think of using the live CD for some reason. Thank you for bringing that to my attention, I will bookmark that.

[Richard Seguin (sectech)]

Edmundo excellent! If it was me trouble shooting and I wanted to work directly on that box I would through a
sudo chmod -x /etc/init.d/kdm at first and reboot that box, that way when it reboots you will be at a local VT. It's totally up to you if you choose to do that as you can pretty much do everything through ssh.

Please take a look at this link https://help.ubuntu.com/community/DebuggingXAutoconfiguration more specifically some of the links regarding ati cards on that page. The benefit of disabling kdm on boot is that you can run a X --configure command which usually will grab a correct X configuration for your card. Different triagers have different ways of going about it.

[Edmundo (eantoranz)]

I can do the LiveCD stuff too... just tell me what you need to get.

[Richard Seguin (sectech)]

More specifically the steps that I would follow would be

1. Disabling kdm temporarily on that box: sudo chmod -x /etc/init.d/kdm
2. Reboot that box
3. Login as your regular user
4. then I would try X -configure
It will put the new configurating file either in /root or in your users home directory /home/<username>
5. find the new file which should be called xorg.conf.new I believe and issue a sudo cp <filename> /etc/X11/xorg.conf
6. then as your regular user I would try issuing the startx command and see what you get.

[Edmundo (eantoranz)]

Well.... that's a bit of adding insult to injury. I "know" how to
start my box without X without having to disable kdm. Also I said
before that I was running X without xorg.conf, with an xorg.conf
created by Xorg --config, with the old xorg.conf (from intrepid)
modified to use vesa and the opne I'm running now (the "created by
xorg" xorg.conf modified to use vesa).

Well... let me just try to run startx to see how it's gonna be (but I
bet it won't work). Give me some minutes. Do I get a backtrace through
ssh for you?

[Edmundo (eantoranz)]

I recreated another xorg.conf.

It appeared like it was going to start. I saw the splashscreen of kdm,
though the first icon appeaded with noise.... but then no other icon
of the splash screen showed up and I got to a blank screen where I
have the mouse, but I can't do anything else. Can't get the the
TVs.... well... you already know from my previous posts.

This is the process list:
$ ps axf
  PID TTY STAT TIME COMMAND
    2 ? S< 0:00 [kthreadd]
    3 ? S< 0:00 \_ [migration/0]
    4 ? S< 0:00 \_ [ksoftirqd/0]
    5 ? S< 0:00 \_ [watchdog/0]
    6 ? S< 0:00 \_ [events/0]
    7 ? S< 0:00 \_ [khelper]
   10 ? S< 0:00 \_ [kstop/0]
  148 ? S< 0:00 \_ [kintegrityd/0]
  150 ? S< 0:00 \_ [kblockd/0]
  152 ? S< 0:00 \_ [kacpid]
  153 ? S< 0:00 \_ [kacpi_notify]
  212 ? S< 0:00 \_ [cqueue]
  219 ? S< 0:00 \_ [ata/0]
  220 ? S< 0:00 \_ [ata_aux]
  221 ? S< 0:00 \_ [ksuspend_usbd]
  226 ? S< 0:00 \_ [khubd]
  229 ? S< 0:00 \_ [kseriod]
  235 ? S< 0:00 \_ [kmmcd]
  241 ? S< 0:00 \_ [btaddconn]
  242 ? S< 0:00 \_ [btdelconn]
  293 ? S< 0:00 \_ [kswapd0]
  335 ? S< 0:00 \_ [aio/0]
  351 ? S< 0:00 \_ [ecryptfs-kthrea]
  532 ? S< 0:00 \_ [scsi_eh_0]
  535 ? S< 0:00 \_ [scsi_eh_1]
  559 ? S< 0:00 \_ [scsi_eh_2]
  562 ? S< 0:00 \_ [scsi_eh_3]
  667 ? S< 0:00 \_ [kstriped]
  670 ? S< 0:00 \_ [kmpathd/0]
  671 ? S< 0:00 \_ [kmpath_handlerd]
  672 ? S< 0:00 \_ [ksnapd]
  675 ? S< 0:00 \_ [kondemand/0]
  681 ? S< 0:00 \_ [krfcommd]
 1376 ? R< 0:00 \_ [kjournald]
 1958 ? S< 0:00 \_ [kpsmoused]
 2386 ? S< 0:00 \_ [kjournald]
 2403 ? S< 0:00 \_ [loop0]
 2404 ? S< 0:00 \_ [kjournald]
 5050 ? S 0:00 \_ [pdflush]
12885 ? S 0:00 \_ [pdflush]
    1 ? Ss 0:01 /sbin/init
 1509 ? S<s 0:00 /sbin/udevd --daemon
 2402 ? Ss 0:00 /sbin/mount.ntfs-3g /dev/sda2 /media/hda2
-o rw,nls=utf8,umask=007,gid=46
 2927 ? S<s 0:00 dhclient3 -e IF_METRIC=100 -pf
/var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases
eth0
 3071 tty4 Ss+ 0:00 /sbin/getty 38400 tty4
 3072 tty5 Ss+ 0:00 /sbin/getty 38400 tty5
 3078 tty2 Ss+ 0:00 /sbin/getty 38400 tty2
 3080 tty3 Ss+ 0:00 /sbin/getty 38400 tty3
 3083 tty6 Ss+ 0:00 /sbin/getty 38400 tty6
 3190 ? Ss 0:00 /usr/sbin/acpid -c /etc/acpi/events -s
/var/run/acpid.socket
 3268 ? Ss 0:00 /sbin/syslogd -u syslog
 3289 ? S 0:00 /bin/dd bs 1 if /proc/kmsg of
/var/run/klogd/kmsg
 3291 ? Ss 0:00 /sbin/klogd -P /var/run/klogd/kmsg
 3312 ? Ss 0:02 /bin/dbus-daemon --system
 3347 ? Ss 0:00 /usr/sbin/sshd
13469 ? Ss 0:00 \_ sshd: antoranz [priv]
13477 ? S 0:00 \_ sshd: antoranz@pts/0
13480 pts/0 Ss ...

[damianos (damian-linux)]

I also have same issue with onboard intel vga :

00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)

I worked around it by booting a intrepid kernel :

damian@anfield:~$ uname -a
Linux anfield 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

I do see the odd artifact on screen though. No X11/xorg.conf file configured. Using intel driver with EXA.

Any info needed let me know.

[Edmundo (eantoranz)]

Really? Well.... by looking at the backtrace X is getting stuck in a
kernel call. So perhaps the problem is in that direction. Let me try
the "intrepid kernel" approach to see how it goes.

[Edmundo (eantoranz)]

Right on! It _does_ work with intrepid's kernel.

Now X is running with no xorg.conf and it's _nice_. I had to change
menu.lst so that it uses the "saved" kernel as the default... but I
can live with that.

So.... how can we help to get this problem fixed in jaunty?

[Anders Nylund (nylund-anders)]

I have the same chipset:
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
Just tried booting with the jaunty alpha6 live cd. It could not start X. Attached xorg.log from the live cd.
(Choosing failsafe did start X in vesa mode)

[cornflake000 (de.facto7)]

Just for the record, I also have had this bug for a couple of weeks now... same chipset. Using vesa in the meantime. It's my only bug to date with jaunty.

[cornflake000 (de.facto7)]

My problem was fixed adding the following to xorg.conf

Section "Device"
    VendorName "Intel Corporation"
    Identifier "82865G Integrated Graphics Controller"
    Driver "Intel"
    BusID "PCI:0:2:0"
    Option "DRI" "False"
EndSection

I found this fix per another bug but I was so happy to see it work I didn't notice which bug# it was from...

[Edmundo (eantoranz)]

So, you turned off DRI. Do you have acceleration?

[Edmundo (eantoranz)]

I just tested starting jaunty's kernel with intel's driver (got an update today or yesterday) and it worked on my machine. Is the problem still there for you, guys?

[Carey Underwood (cwillu)]

Edmundo, is that with a stock xorg.conf, or are you running with UXA, or DRI disabled, or anything like that?

[Edmundo (eantoranz)]

It would be without xorg.conf (in other words, I'm letting Xorg do its
default stuff)

Here's the log, in case you want it.

[Edmundo (eantoranz)]

I just got an xorg-video-intel update. I'll see on my next reboot
(probably) if it still works.

[Carey Underwood (cwillu)]

Edmundo, I'm going to mark this as Fix Released then, feel free to remark it back to Confirmed if the issue returns.

[Edmundo (eantoranz)]

It's OK. I just rebooted and it's working normally. I'll come back to
it if I see the bug is back.