i have upgraded to kernel 2.6.26-rc5-686 and i am getting these messages in dmesg:
[ 0.991863] vesafb: cannot reserve video memory at 0x48000000 [ 0.991870] vesafb: abort, cannot ioremap video memory 0x300000 @ 0x48000000 [ 0.991896] vesafb: probe of vesafb.0 failed with error -5 and... [ 1.574657] splashy[367]: segfault at c ip b7f9a27d sp bf8c0590 error 4 in libsplashy.so.1[b7f98000+5000] [ 16.499375] splashy[1116]: segfault at c ip b7f5627d sp bfc9d9d0 error 4 in libsplashy.so.1.0.0[b7f54000+5000] i don't seem to have vesafb.ko but i tried video=radeon (i have radeonfb.ko) but it did not work either. On 6/8/08, Nadav Kavalerchik <[EMAIL PROTECTED]> wrote: > laptop:~# dfbinfo > > =======================| DirectFB 1.0.1 |======================= > (c) 2001-2007 The DirectFB Organization (directfb.org) > (c) 2000-2004 Convergence (integrated media) GmbH > ------------------------------------------------------------ > > (*) DirectFB/Core: Single Application Core. (2008-05-15 14:24) > (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed > --> No such file or directory > (!) DirectFB/FBDev: Error opening framebuffer device! > (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment > variable. > (!) DirectFB/Core: Could not initialize 'system' core! > --> Initialization error! > (#) DirectFBError [DirectFBCreate() failed]: Initialization error! > > laptop:~# cat /proc/cmdline > root=/dev/hda1 splash quiet ro > > ( you don't see vga=791 or 788 because it will not boot otherwise ! i get a > blank screen with a flashing hd led. ) > > laptop:~# cat /proc/fb > > laptop:~# ls -l /dev/fb* > ls: cannot access /dev/fb*: No such file or directory > > i have kernel 2.6.25-trunk on compaq presarion 1500 + ATI Technologies Inc > Radeon Mobility M7 LW [Radeon Mobility 7500] > > any ideas ? > > On Sun, Jun 8, 2008 at 5:44 PM, Luis Mondesi <[EMAIL PROTECTED]> wrote: > >> Please include the result from the following commands on this bug report: >> >> cat /proc/cmdline >> cat /proc/fb >> ls -l /dev/fb* >> >> From the output of your splashy process, it looks like your framebuffer is >> not setup correctly. What happens when you run: >> >> dfbinfo # as root if possible >> >> You are in trouble if you see something like: >> >> (*) DirectFB/Core: Single Application Core. (2008-04-08 15:15) >> (*) Direct/Memcpy: Using Generic 64bit memcpy() >> (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed >> --> No such file or directory >> (!) DirectFB/FBDev: Error opening framebuffer device! >> (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment >> variable. >> (!) DirectFB/Core: Could not initialize 'system' core! >> --> Initialization error! >> (#) DirectFBError [DirectFBCreate() failed]: Initialization error! >> >> All in all, splashy should not crash when this happens. We will look into >> this. >> >> -- >> ----)(----- >> Luis Mondesi >> Maestro Debiano >> >> ----- START ENCRYPTED BLOCK (Triple-ROT13) ------ >> Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur >> fbsgjner >> jbeyq. >> ----- END ENCRYPTED BLOCK (Triple-ROT13) ------ > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
