Bug 777
Summary: | vesafb fails to initalize 1GB system memory and 128MB video memory | ||
---|---|---|---|
Product: | Drivers | Reporter: | Christopher Rude (crude) |
Component: | Console/Framebuffers | Assignee: | James Simmons (jsimmons) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | crude |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.5.63 - Current | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: | the patch in patch form ;) |
Description
Christopher Rude
2003-06-05 02:57:06 UTC
Created attachment 396 [details]
the patch in patch form ;)
relevent dmesg output on vanilla 2.5.73 grub kernel line: kernel /boot/bzImage.dev root=/dev/hda3 vga=794 video=vesa:1280x1024@70 vesafb: abort, cannot ioremap video memory 0x8000000 @ 0xf0000000 as you might supposes, still no framebuffer console present relevent dmesg output on 2.5.73 w/ submitted patch vesafb: framebuffer at 0xf0000000, mapped to 0xf880a000, size 2560k vesafb: mode is 1280x1024x16, linelength=2560, pages=1 vesafb: protected mode interface info at c000:e350 vesafb: scrolling: redraw vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0 fb0: VESA VGA frame buffer device Console: switching to colour frame buffer device 160x64 grub kernel line: kernel /boot/bzImage.dev root=/dev/hda3 vga=794 video=vesa:1280x1024@70 and yes my framebuffer console works ;) 2.6 testing (i know test2, and test1-mm1) no longer suffer from the mentiond problem ;) good workd to whomever fixed the underlying issue closing is cool Thank you tried kernel 2.6 test4 and test5 and i still get the blank console problem. tried the patch (had to disable the rivafb module, because of some reference errors) and its working now. this is with a geforce4 128mb and 1gig of ram. lars update 2.6-test6-bk4 works fine out of the box!! thats really sweet! lars |