On Thu, 2005-07-21 at 23:36 +0200, Richard Fish wrote: > LostSon wrote: > > >>/dev/fb/0 (symlinked from /dev/fb0) are the device nodes for accessing > >>the framebuffer device. During services startup (i.e, the part that > >>happens after after the root filesystem is mounted and the kernel starts > >>init) these nodes are created automatically when udevstart is run by > >>/sbin/rc. This only happens if a usable framebuffer driver is compiled > >>into your kernel (not as a module!) and the driver found a usable > >>graphics card. > >> > >>Could you post your dmesg output right after booting. I want to make > >>sure that the framebuffer device is being found at boot time. You > >>should be seeing messages like this: > >> > >> > >>radeonfb: Retreived PLL infos from BIOS > >>radeonfb: Reference=27.00 MHz (RefDiv=6) Memory=344.00 Mhz, > >>System=236.00 MHz > >>radeonfb: PLL min 20000 max 35000 > >>Non-DDC laptop panel detected > >>radeonfb: Monitor 1 type LCD found > >>radeonfb: Monitor 2 type no found > >>radeonfb: panel ID string: 1600x1200 > >>radeonfb: detected LVDS panel size from BIOS: 1600x1200 > >>radeondb: BIOS provided dividers will be used > >>radeonfb: Dynamic Clock Power Management enabled > >>Console: switching to colour frame buffer device 200x75 > >>fbsplash: console 0 using theme 'emergence' > >>fbsplash: switched splash state to 'on' on console 0 > >>radeonfb (0000:01:00.0): ATI Radeon NP > >> > >>I think yours should say something about vesafb-tng. > >> > >>-Richard > >> > >> > >> > > My dmesg output shows nothing like that at all im digging around for > >the /dev/fb0 and /dev/fb/0 but dont have either of these either. I must > >of screwed something up pretty damn bad. > > > > > > No, don't be so hard on yourself. Most likely you just missed a kernel > configuration option, or configured things as modules instead of > statically into the kernel, both of which are pretty common mistakes. > > What does "grep CONFIG_FB /usr/src/linux/.config" report? > > -Richard > Aha!! Success yeah it was just me screwing up my kernel config not setting a resolution right. And switching to vesafb-tng helped out alot also. Thanks for your help and patience, it is greatly appreciated. -- LostSon
http://www.lostsonsvault.org Fox Cities Linux User Group = www.foxlug.org
signature.asc
Description: This is a digitally signed message part
