| 1 |
On Wed, 2005-07-20 at 07:11 +0200, Richard Fish wrote: |
| 2 |
> LostSon wrote: |
| 3 |
> |
| 4 |
> >On Tue, 2005-07-19 at 23:31 +0200, Holly Bostick wrote: |
| 5 |
> > |
| 6 |
> > |
| 7 |
> >>Christoph Eckert schreef: |
| 8 |
> >> |
| 9 |
> >> |
| 10 |
> >>>>I checked this per your instructions as well and no it |
| 11 |
> >>>>hasnt cut it off its all on one line. Still no luck im |
| 12 |
> >>>>still just getting the cant open config file on /etc/splash |
| 13 |
> >>>>error and fd0 crap, heh |
| 14 |
> >>>> |
| 15 |
> >>>> |
| 16 |
> >>Umm... pardon me for asking, but you've said at least twice that an |
| 17 |
> >>error informs you that splash can't open the config file on |
| 18 |
> >>/etc/splash-- but you've never said that you checked the config file at |
| 19 |
> >>/etc/splash to confirm that it 1) exists 2) is readable (permissions, |
| 20 |
> >>syntax).... does something in or related to /etc/splash (like |
| 21 |
> >>/etc/conf.d/splash, or in some strange twist of fate, |
| 22 |
> >>/etc/init.d/splash, in addition to the config file found in each theme |
| 23 |
> >>folder in /etc/splash itself) have some association with fd0 (the floppy |
| 24 |
> >>drive) for some reason? Do you even have a floppy drive? Even so, the |
| 25 |
> >>splash config file certainly won't be found there. |
| 26 |
> >> |
| 27 |
> >> |
| 28 |
> > |
| 29 |
> > Yes the files exist and the permissions are right where i should be |
| 30 |
> >able to use them. and the /dev/fb0 and /dev/fb/0 i have no idea wtf they |
| 31 |
> >are. |
| 32 |
> > |
| 33 |
> > |
| 34 |
> |
| 35 |
> /dev/fb/0 (symlinked from /dev/fb0) are the device nodes for accessing |
| 36 |
> the framebuffer device. During services startup (i.e, the part that |
| 37 |
> happens after after the root filesystem is mounted and the kernel starts |
| 38 |
> init) these nodes are created automatically when udevstart is run by |
| 39 |
> /sbin/rc. This only happens if a usable framebuffer driver is compiled |
| 40 |
> into your kernel (not as a module!) and the driver found a usable |
| 41 |
> graphics card. |
| 42 |
> |
| 43 |
> Could you post your dmesg output right after booting. I want to make |
| 44 |
> sure that the framebuffer device is being found at boot time. You |
| 45 |
> should be seeing messages like this: |
| 46 |
> |
| 47 |
> |
| 48 |
> radeonfb: Retreived PLL infos from BIOS |
| 49 |
> radeonfb: Reference=27.00 MHz (RefDiv=6) Memory=344.00 Mhz, |
| 50 |
> System=236.00 MHz |
| 51 |
> radeonfb: PLL min 20000 max 35000 |
| 52 |
> Non-DDC laptop panel detected |
| 53 |
> radeonfb: Monitor 1 type LCD found |
| 54 |
> radeonfb: Monitor 2 type no found |
| 55 |
> radeonfb: panel ID string: 1600x1200 |
| 56 |
> radeonfb: detected LVDS panel size from BIOS: 1600x1200 |
| 57 |
> radeondb: BIOS provided dividers will be used |
| 58 |
> radeonfb: Dynamic Clock Power Management enabled |
| 59 |
> Console: switching to colour frame buffer device 200x75 |
| 60 |
> fbsplash: console 0 using theme 'emergence' |
| 61 |
> fbsplash: switched splash state to 'on' on console 0 |
| 62 |
> radeonfb (0000:01:00.0): ATI Radeon NP |
| 63 |
> |
| 64 |
> I think yours should say something about vesafb-tng. |
| 65 |
> |
| 66 |
> -Richard |
| 67 |
> |
| 68 |
My dmesg output shows nothing like that at all im digging around for |
| 69 |
the /dev/fb0 and /dev/fb/0 but dont have either of these either. I must |
| 70 |
of screwed something up pretty damn bad. |
| 71 |
-- |
| 72 |
LostSon |
| 73 |
|
| 74 |
http://www.lostsonsvault.org |
| 75 |
|
| 76 |
Fox Cities Linux User Group = www.foxlug.org |
Archives