Ubuntu
linux package

Intrepid weird hardware boot issues with MSI x86_64 motherboard

Bug #257751 reported by Caroline Ford
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm really not sure what's going on here so I don't know which package to file it against. I'm going to guess the kernel.

This is a fully updated version of Intrepid x86_64 running on an MSI P4M900M3-L motherboard with the VIA P4M900 chipset. The motherboard comes with inbuilt S3 Chrome9 HC graphics, I've added an Nvidia 8600GT PCI-E card.

This booting problem only occurs on intrepid, hardy (i386 and x86_64) is fine.

During the boot process an error is displayed on the screen. At this point beeping starts from the PC speaker. The machine continues to boot with the beeping. gdm loads fine.

After logging in the screen flashes 3 to 4 times. It then goes off and the monitor goes on power save. The machine is still beeping and the fan still going. Failsafe gnome has the same problem, failsafe xterm works okay but the machine is still beeping.

I thought the beeping may have been the case fan - but I think it may be graphics related after googling for the error message.

The beeping starts when the following error is displayed:

uvesafb: failed to execute /sbin/v86d
uvesafb: make sure that the v86d helper is installed and executable
 uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2)
 uvesafb: vbe_init() failed with -22
 uvesafb: probe of uvesafb.0 failed with error -22

This is apparently the vesa frame buffer.

Xorg.0.log has a lot of:

(--) NV(0): Trying load detection on VGA1 ... nothing.
(II) NV(0): Probing for EDID on I2C bus 1...
(II) NV(0): I2C device "I2C1:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "I2C1:ddc2" removed.
(II) NV(0): ... none found
(--) NV(0): Trying load detection on VGA2 ... found one!
(II) NV(0): Probing for EDID on I2C bus 3...
(II) NV(0): I2C device "I2C3:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "I2C3:ddc2" removed.
(II) NV(0): ... none found

I guess VGA1 is the inbuilt chip and EDID doesn't seem to work on this architecture.

The last things in kern.log are:

Aug 10 18:10:08 elektronika kernel: [ 2602.519283] gvfs-fuse-daemo[5932] general protection rip:7f5d8dccf423 rsp:7fff978f9db0 error:0
Aug 10 18:10:08 elektronika kernel: [ 2602.521440] gvfs-fuse-daemo[5607] general protection rip:7f8b7c6f6423 rsp:7fff8631ea30 error:0
Aug 10 18:13:12 elektronika kernel: [ 2787.216770] audit(1218388392.994:5): type=1505 operation="profile_replace" info="unsupported interface version" pid=10247
Aug 10 18:14:13 elektronika kernel: Kernel logging (proc) stopped.
Aug 10 18:14:13 elektronika kernel: Kernel log daemon terminating.

I'm not really sure where to go from here..

See original description
Revision history for this message
Caroline Ford (secretlondon) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :
Revision history for this message
Caroline Ford (secretlondon) wrote :

Looking at the logs for hardy it has the same stuff in Xorg.0.log :

(--) NV(0): Trying load detection on VGA1 ... nothing.
(II) NV(0): Probing for EDID on I2C bus 1...
(II) NV(0): I2C device "I2C1:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "I2C1:ddc2" removed.
(II) NV(0): ... none found
(--) NV(0): Trying load detection on VGA2 ... found one!
(II) NV(0): Probing for EDID on I2C bus 3...
(II) NV(0): I2C device "I2C3:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "I2C3:ddc2" removed.
(II) NV(0): ... none found

Revision history for this message
Caroline Ford (secretlondon) wrote :

/sbin/v86d doesn't seem to exist.

Revision history for this message
Caroline Ford (secretlondon) wrote :

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473176

Revision history for this message
Caroline Ford (secretlondon) wrote :

Do we need v86d (0.1.5.2-1) in main for AMD64?

http://packages.ubuntu.com/intrepid/v86d

I'll try installing it and see if it fixes this bug.

description: updated
Revision history for this message
Caroline Ford (secretlondon) wrote :

It fixes half the bug (or rather there are probably 2 different bugs here). There is no error and no beeping - but still no graphics when gnome session starts.

Revision history for this message
Caroline Ford (secretlondon) wrote :

from messages post install of v86d:

Aug 14 00:00:01 elektronika klogd: [ 2.030450] uvesafb: NVIDIA Corporation, G84 Board - p403h02, Chip Rev , OEM: NVIDIA, VBE v3.0
Aug 14 00:00:01 elektronika klogd: [ 2.231407] uvesafb: VBIOS/hardware doesn't support DDC transfers
Aug 14 00:00:01 elektronika klogd: [ 2.231410] uvesafb: no monitor limits have been set, default refresh rate will be used
Aug 14 00:00:01 elektronika klogd: [ 2.233135] uvesafb: scrolling: redraw
Aug 14 00:00:01 elektronika klogd: [ 2.235529] uvesafb: framebuffer at 0xfb000000, mapped to 0xffffc20010980000, using 14336k, total 14336k
Aug 14 00:00:01 elektronika klogd: [ 2.235532] fb0: VESA VGA frame buffer device
Aug 14 00:00:01 elektronika klogd: [ 2.486019] Console: switching to colour frame buffer device 80x30

Revision history for this message
Caroline Ford (secretlondon) wrote :

I've also found this in messages:

Aug 14 00:00:01 elektronika klogd: [ 0.736632] ACPI Warning (tbutils-0217): Incorrect checksum in table [OEMB] - 7A, should be 6D [20080321]

Revision history for this message
Caroline Ford (secretlondon) wrote :

Could the checksum error be connected to the Foxcomm bug? bug #251338

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Caroline,

Care to take a peek at bug 246269 ? Based on the error messages you posted in your description it seems this report may be a duplicate of bug 246269 . Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Caroline Ford (secretlondon) wrote :

Hi Leann

The pre-GDM stuff is certainly bug #246269, although I am not using any kernel options, just the defaults.

I get graphics throughout the boot just with beeping (as though there was a graphics failure).

I guessing the graphics failure once gnome-session starts is a different bug? It still happens with v86d installed.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks Caroline,

You might just want to subscribe yourself to bug 246269 just to be notified of any updates/fixes. Could you attach an updated dmesg output from after you've installed v86d ? Thanks.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Christoph Roeder (brightdroid) wrote :

For me it's fixed since one of the last updates.

PS: I don't have and never had v86d installed

Revision history for this message
Amit Kucheria (amitk) wrote :

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . Let us know your results. Thanks.

Revision history for this message
Caroline Ford (secretlondon) wrote : Re: [Bug 257751] Re: Intrepid weird hardware boot issues with MSI x86_64 motherboard

Long fixed for me.

Revision history for this message
Bartosz Kosiorek (gang65) wrote :

Hi Caroline.
Does this bug exist in the recent Jaunty Jackalope 9.04 release?

Revision history for this message
Caroline Ford (secretlondon) wrote :

As I said above this is long fixed for me.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Marking this Fix Released per Caroline's comments.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.