[Bug 246269] Re: Switched from vesafb to uvesafb, but uvesafb can't work without v86d

bugmenot bugmenot at mailinator.com
Sat Aug 9 19:32:41 UTC 2008


I am also experiencing this problem -- multiple beeps upon reboot (sometimes) followed by either:
1. A black screen until kdm loads
2. Blue/Red background with white vertical bands instead of boot kernel messages
3. Normal boot with kernel messages but no usplash whatsoever.

It seems the beeps happen in concert with either 1. or 2., when it does
3. there are no beeps.

Interesting messages from dmesg:
=====
[ 1.703488] uvesafb: NVIDIA Corporation, GT200 Board - 0651s004, Chip Rev , OEM: NVIDIA, VBE v3.0
[ 1.772790] Program usplash tried to access /dev/mem between 0->e00000.
[ 2.594371] uvesafb: VBIOS/hardware doesn't support DDC transfers
[ 2.594371] uvesafb: no monitor limits have been set, default refresh rate will be used
[ 2.594371] uvesafb: scrolling: redraw
=====

See the second line especially...

followed by:
=====
[ 2.598371] mtrr: type mismatch for f5000000,800000 old: write-back new: write-combining
[ 2.598371] mtrr: type mismatch for f5000000,400000 old: write-back new: write-combining
[ 2.598371] mtrr: type mismatch for f5000000,200000 old: write-back new: write-combining
[ 2.598371] mtrr: type mismatch for f5000000,100000 old: write-back new: write-combining
[ 2.598371] mtrr: type mismatch for f5000000,80000 old: write-back new: write-combining
[ 2.598371] mtrr: type mismatch for f5000000,40000 old: write-back new: write-combining
[ 2.598371] mtrr: type mismatch for f5000000,20000 old: write-back new: write-combining
[ 2.598371] mtrr: type mismatch for f5000000,10000 old: write-back new: write-combining
[ 2.598371] mtrr: type mismatch for f5000000,8000 old: write-back new: write-combining
[ 2.598371] mtrr: type mismatch for f5000000,4000 old: write-back new: write-combining
[ 2.598371] mtrr: type mismatch for f5000000,2000 old: write-back new: write-combining
[ 2.598371] mtrr: type mismatch for f5000000,1000 old: write-back new: write-combining
[ 2.598371] uvesafb: framebuffer at 0xf5000000, mapped to 0xffffc20011800000, using 14336k, total 14336k
[ 2.598371] fb0: VESA VGA frame buffer device
[ 2.605070] Console: switching to colour frame buffer device 80x30
=====

System specs follow:
Hardware: Core2Duo/Intel P45/nVidia GTX260
Software: KUbuntu 8.10 Intrepid Ibex installed at Alpha 2, updated to latest via 'aptitude dist-upgrade'.
The v86d package is installed (repeatedly situation 3. without it).

=====[/etc/usplash.conf]=====
# Usplash configuration file
# These parameters will only apply after running update-initramfs.
xres=1920
yres=1200
=====[/etc/usplash.conf]=====

=====[/boot/grub/menu.lst]=====
(...)
title Ubuntu intrepid (development branch), kernel 2.6.26-5-generic
root (hd0,1)
kernel /boot/vmlinuz-2.6.26-5-generic root=UUID=03cbe687-58cb-4805-a4f3-5b6c5d11c4db ro quiet splash crashkernel=384M-2G:64M at 16M,2G-:128M at 16M
initrd /boot/initrd.img-2.6.26-5-generic
quiet
(...)
=====[/boot/grub/menu.lst]=====

If any more details are needed, please ask...

-- 
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.




More information about the kernel-bugs mailing list