[i965] [gm965] kubuntu final live cd doesn't start xorg for HP 2710p laptop

[kirys]

Binary package hint: xorg

The Kubuntu 9.04 live cd doesn't start x.org on my laptop "hp 2710p" (but as i reported into the forum neither the beta and previous versions).

if x is launched with startx seems to work as expected.
I've checked this on latest x86_64 of kubuntu 9.04 final

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c)
     Subsystem: Hewlett-Packard Company Device [103c:30c8]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)
     Subsystem: Hewlett-Packard Company Device [103c:30c8]

[Bryce Harrington (bryce)]

Hi kirys,

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.]

[kirys (kirys)]

Hi, sorry for the late answer but I was outside home this week and my laptop does not have an integrated cd drive.
I've just checked the new stable kubuntu live cd and the problem worsened, in the RC the cd didn't start x automatically but ended into terminal, but using startx from the command line x started, while in the stable version startx just bring up a black screen.
I'll attach the required files in this and next reply.
There was no xorg.conf into the livecd (kubuntu amd64).
Thank You
K.

[kirys (kirys)]

And here we have the xorg.0.log

[kirys (kirys)]

addenum
Previous lspci log was generated without root privileges, so I generated a new one with root privileges

[Martin Olsson (mnemo)]

Is this a laptop? Are you using an external monitor? If so, is it connected using VGA, DVI or HDMI? Do you have a TV-out cable connected to this machine?

There are some unusual warnings in the xorg.log:

(II) intel(0): Comparing regs from server start up to After PreInit
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x80000207 to 0x80000237
(WW) intel(0): PIPEASTAT before: status: FIFO_UNDERRUN VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): PIPEASTAT after: status: FIFO_UNDERRUN VSYNC_INT_STATUS OFIELD_INT_STATUS EFIELD_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): Register 0x68000 (TV_CTL) changed from 0x100000c0 to 0x000c00c0
(WW) intel(0): Register 0x68010 (TV_CSC_Y) changed from 0x00000000 to 0x0332012d
(WW) intel(0): Register 0x68014 (TV_CSC_Y2) changed from 0x00000000 to 0x07d30104

[Martin Olsson (mnemo)]

Can you also attach the output of "dmesg" and a copy of /var/log/Xorg.0.log.old ?? (if it exists).

[kirys (kirys)]

> Is this a laptop?
Yes it's an hp 2710p booting from the cd of the docking station (it's detected as an usbcd), the laptop doesn't have an internal cd, so the docking station is required.

> Are you using an external monitor? If so, is it connected using VGA, DVI or HDMI?
It's just the same booting with the external monitor connected to the vga port or using the internal monitor only. Those files were generated using the external monitor.

>Do you have a TV-out cable connected to this machine?
No tv out cable is connected the tv-out port laptop.

>Can you also attach the output of "dmesg" and a copy of /var/log/Xorg.0.log.old ?? (if it exists).
no xorg.0.log.old exists I've attached dmesg to this reply.

Some notes you may find of interest.
I'm currently running kubuntu 8.04 on my laptop (with the known issues of x3100), it's live cd works as expected.
The latest chakra live cd (the only other live cd i currently have ready to test) works perfectly.
I've done many tries on this live cd and once it started correctly after booting the live cd after a reboot from my current kubuntu (instead of booting it after powering on the laptop), so maybe can be an initialization issue. Anyway till now i was unable to "repeat the event".
Sometimes calling startx start the x.org as expected sometimes doesn't (this also make me thing that it is an initialization issue).
Hope this helps

[Martin Olsson (mnemo)]

After looking at your xorg.log, I see yours include:
(II) intel(0): Output VGA connected
(II) intel(0): Output LVDS connected

So I assume you have an external monitor attached to this laptop of yours. Can you please try to disconnect that monitor and then boot from the jaunty final live CD?

I'm attaching xorg.log from my 965 machine in case anyone wants to look at a diff between the two.

[kirys (kirys)]

as i've already said in previous reply the behavior is exactly the same booting with the external monitor connected or not ;)

[Martin Olsson (mnemo)]

Another difference is that in my 965 xorg.log I have these lines which you don't have:

(WW) intel(0): ESR is 0x00000001
(WW) intel(0): Existing errors found in hardware state.

I'm not sure exactly what that means though. I think it would be useful if you downloaded the final version of jaunty and then _completely_ powered off the laptop (to rule out that any bad state lingers on inside the graphics card) and then tried to boot of the final live CD.

The dmesg also has these errors:

[ 127.588166] [drm] Initialized i915 1.6.0 20080730 on minor 0
[ 127.592209] [drm:i915_setparam] *ERROR* unknown parameter 4
[ 132.162949] [drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
[ 132.169558] mtrr: no MTRR for d0000000,10000000 found

But I also have those in my 965 dmesg.

[kirys (kirys)]

All those logs came from latest stable kubuntu jaunty amd64 booted after the pc has been off for at least a minute.
In one of previous posts i've reported that once the live started correctly after booting after a reboot from my kubuntu 8.04 (i've already tried twice and i was unable to repeat that result). But all other check were done in the "proper way".
Actually I'm downloading the i386 iso to check if its a problem related to 64bit architecture.

[Martin Olsson (mnemo)]

Can you describe in more detail what you mean by "if x is launched with startx seems to work as expected"?

And when you boot, what exactly happens? Does the machine freeze? Do you see garbage on the screen or is it just black? Or do you end up in a text mode console prompt?

[kirys (kirys)]

The boot is just the kubuntu logo with the "progress bar", after a while there is some flicker of the screen (seem some kind o card probing process, or maybe a multiple restart of xorg), and then the console is shown.
The console is somewhat at a "wrong" resolution (i cannot see some lines at the bottom). But it works normally.
So I, as reported in a previous reply, executing startx sometimes starts x correctly (with kde4 and all the various accessories) I can also enable the effects.
I've just recorded the i386 version of jaunty and i have exactly the same problem.

[kirys (kirys)]

Xorg.failsafe.log from jaunty i386

[Martin Olsson (mnemo)]

When you get to the console can you please run "ls -al /dev/dri/card*" and attach output. Also, do you have a wacom board? If so, does the bug still happen if you disconnect it? Thirdly, can you think of anything else which is "special" or unusual with you hardware configuration?

What you describe as a "probing process" is probably what prints the following stuff into your xorg.log:

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card1
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card2
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card3
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card4
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card5
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card6
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card7
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card8
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card9
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card10
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card11
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card12
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card13
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card14
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmGetBusid returned ''

[kirys (kirys)]

> Also, do you have a wacom board? If so, does the bug still happen if you disconnect it? Thirdly, can you think of anything else which is "special" or unusual with you hardware configuration?

it's a tabletpc 12'' no internal cdrom, the cd/dvd reader is provided by an external docking station, it's not possible to disconnect the wacom board cause it's integrated into the pc, neither I can boot the distro "undocked". All these features work into 8.04.

more detailed specification are available here:
http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/321957-321957-64295-321838-306995-3355644.html

[Martin Olsson (mnemo)]

Permissions on the /dev/dri/card* looks as they are supposed to look.
To bad we can't try without the wacom, it would be nice to rule that out.

Please see if you have any log files in /var/log/gdm/ and attach them if they exist.

[kirys (kirys)]

There is no /var/log/gdm/ directory after the boot of the live cd.
I'll be away from home till friday, so i will not be able to provide further log files till that day.
Bye

[Mario A. Vazquez (darkcoder)]

I have a similar problem like the one described by the bug reporter. The Kubuntu 9.04 cd boots, but instead of starting X with KDE, it just drops to a shell prompt. I was able to start KDE by typing:
    sudo /etc/init.d/kdm start

My system is a Desktop Intel Core Duo with 2GB ram.
Kubuntu 9.04 i386 boots fine
Kubuntu 9.04 amd64 fails to load KDE.
Have an nvidia card.

But in my case the 9.04 RC and betas booted fine, the issue is only with 9.04 final.

[Martin Olsson (mnemo)]

@Mario, since you have an nvidia card please open a separate bug. When you open this bug do it using the terminal command "ubuntu-bug xorg" so we can gets hardware and software configuration details attach to the bug report. Also, it would be in particularly valuable for us if you saved a copy of xorg.log and xorg.log.old right when you tried to boot but ended up in a text mode console instead. Thanks.

[Mario A. Vazquez (darkcoder)]

I tried the Kubuntu 9.04 RC again (amd64 edition), and the cd boot to KDE without any issue, but tried again the Kubuntu 9.04 and it stays on a prompt.

The starting messages in the console in both releases shows that kdm is executed, but something is killing it in the final release.

And the comment above that said I fixed it with starting the service, I had to kill the kdm that was started (but not available to use) before restarting it again.

[Mario A. Vazquez (darkcoder)]

Ok, going to submit as a separate report.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

A new major version of the -intel driver is now available in Karmic.

This version includes a major reworking of the acceleration
architecture, which resolves a huge number of issues. We do not know
whether it resolves the issue you reported.

Would you mind testing Karmic Alpha-2 and seeing if it is still a
problem? CD ISO images are available here:

  http://cdimages.ubuntu.com/releases/karmic/

If the issue can still be reproduced on karmic, please report here with
your findings, and attach a fresh Xorg.0.log from your test, and we will
be able to forward the bug upstream.

Otherwise, if the bug no longer exists in Karmic, let us know that as
well.

In the off chance you encounter different bugs while attempting to test
Karmic, please report those as new bug reports.

[kirys (kirys)]

I'm downloading the alpha 2 now, I'll let you know if the issue is still present.

[kirys (kirys)]

I'm sad to report that i have exactly the same issue of the previous release.

[kirys (kirys)]

Ok, I've made a little test, is not an intel driver problem it's a KDM problem.
Ubuntu live starts while kubuntu doesn't, and, as you may view from my previous post kde starts if i run 'startx' from the console.
So It is not an intel driver problem, but some issue between my hw configuration and kdm.
Let me know if there are logfiles that can be used by you for further investigations.
Bye
K.

[kirys (kirys)]

I thought that this log could be usefull

[kirys (kirys)]

Did the new information I've provided bring you any clues on the causes?

[kirys (kirys)]

Why the status is set as incomplete, do you need more info?

[kirys (kirys)]

Ok i've tested latest koala A4 live cd and still kdm fail to start.
I'll attach here the various logs.

[kirys (kirys)]

I want to remember that only KDM fails to start, gdm works and startx launch x.org if executed from command line.

[kirys (kirys)]

Still does happen with latest alpha iso...
the kdm.log report
"failed to load module "i810""

loggin fromthe textual console and executing
sudo /etc/init.d/kdm restart
starts kdm and progress into the livecd "start"

There must be is some script on the livecd that makes kdm trying to use the old i810 driver

Cya

[Geir Ove Myhr (gomyhr)]

This bug report has been inactive for quite some time and in the meantime Ubuntu has moved along. I hope the reported problem has been resolved in the current version of Ubuntu. If it has not and there are people willing to follow up with information collecting and testing, it is best to file a new bug report with the latest Ubuntu development version (currently 10.04, but soon 10.10), using the ubuntu-bug command if possible. Feel free to mention the bug number of this bug.

We are sorry that we are not always have the capacity to look at all reported bugs in a timely manner. Occationally we have to purge old bug reports where no progress has been made, whether it is due to reporter not being able to respond or lack of manpower on the Ubuntu side, in order to keep our list of "active" bugs current. Sorry for the inconvenience this may cause.

Here are a few tips that will increase the chances that your bug gets priority:
* Read https://wiki.ubuntu.com/X/Reporting
* Browse https://wiki.ubuntu.com/X and see if there is some relevant information for you problem
* Respond quickly to questions from triagers
* Try changing things to see if the behaviour changes, e.g.
  * A new mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D (more information at https://wiki.ubuntu.com/KernelTeam/MainlineBuilds)
  * The xorg-edgers PPA: https://launchpad.net/~xorg-edgers/+archive/ppa
  * Various options in `/etc/X11/xorg.conf` (see `man intel`)
* Browse other bug reports to see if you find a similar one and provide the information that is being asked for there.