vesa framebuffer console won't work in intrepid even with modules loaded
Bug #264153 reported by
dunDer
This bug report is a duplicate of:
Bug #246269: Switched from vesafb to uvesafb, but uvesafb can't work without v86d.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Screen blank when vga=xxx even with framebuffer modules loaded. Running kernel w/o vesa shows at boot:
[ 2.400668] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
[ 2.400719] uvesafb: vbe_init() failed with -22
[ 2.400771] uvesafb: probe of uvesafb.0 failed with error -22
To post a comment you must log in.
Confirmed here.
Linux merlin 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686 GNU/Linux
With a nVidia
hwinfo --framebuffer gives:
02: None 00.0: 11001 VESA Framebuffer 0xd5dfffff (rw)
[Created at bios.450]
Unique ID: rdCR.VSBbdW2x3qC
Hardware Class: framebuffer
Model: "NVIDIA G86 Board - NV_NB8M "
Vendor: "NVIDIA Corporation"
Device: "G86 Board - NV_NB8M "
SubVendor: "NVIDIA"
SubDevice:
Revision: "Chip Rev"
Memory Size: 14 MB
Memory Range: 0xd5000000-
--- SOME MODES ---
Config Status: cfg=new, avail=yes, need=no, active=unknown