On Wed, 2005-07-20 at 07:11 +0200, Richard Fish wrote: > LostSon wrote: > > >On Tue, 2005-07-19 at 23:31 +0200, Holly Bostick wrote: > > > > > >>Christoph Eckert schreef: > >> > >> > >>>>I checked this per your instructions as well and no it > >>>>hasnt cut it off its all on one line. Still no luck im > >>>>still just getting the cant open config file on /etc/splash > >>>>error and fd0 crap, heh > >>>> > >>>> > >>Umm... pardon me for asking, but you've said at least twice that an > >>error informs you that splash can't open the config file on > >>/etc/splash-- but you've never said that you checked the config file at > >>/etc/splash to confirm that it 1) exists 2) is readable (permissions, > >>syntax).... does something in or related to /etc/splash (like > >>/etc/conf.d/splash, or in some strange twist of fate, > >>/etc/init.d/splash, in addition to the config file found in each theme > >>folder in /etc/splash itself) have some association with fd0 (the floppy > >>drive) for some reason? Do you even have a floppy drive? Even so, the > >>splash config file certainly won't be found there. > >> > >> > > > > Yes the files exist and the permissions are right where i should be > >able to use them. and the /dev/fb0 and /dev/fb/0 i have no idea wtf they > >are. > > > > > > /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. -- LostSon
http://www.lostsonsvault.org Fox Cities Linux User Group = www.foxlug.org
signature.asc
Description: This is a digitally signed message part
