View previous topic :: View next topic |
Author |
Message |
Lorijho n00b
Joined: 22 Jul 2003 Posts: 38 Location: Luxembourg
|
Posted: Tue Mar 16, 2004 4:05 am Post subject: gentoo-dev-2.6.3-r1 & udev & framebuffer working |
|
|
Hi to All !
After some hardware rearrangements on my gentoo desktop box i decided to start all over again with a fresh install.
A month ago, i did another fresh install on my server box, migrated from clarkconnect (rh9 based) to gentoo 2.6, so i gained quite a lot of experience on the latest kernel generation...
Everthing went just fine, but i seemed that bootsplash (splash=silent) would not work with udev.
Code: | /dev/fb/0 and /dev/fb0 do not exist |
But after some research i managed to fire up the Gentoo LiveCD-2004.0 Bootsplash Theme which looks so good !!
I was using sys-kernel/gentoo-dev-sources version 2.6.3-r1.
No time to check but maybe the problem is already fixed with 2.6.4, although nothing concerning fb was mentionned in Changelog.
Another solution are the recent (2.6.x) mm or love sources as they come with a set of "desktop" patches and even an framebuffer-udev patch.
Well anyway here is the mini-howto to get it working on gentoo-dev-sources 2.6.3-r1 :
1) Follow all steps of the "Gentoo udev Guide" to set up udev.
http://www.gentoo.org/doc/en/udev-guide.xml
udev is still in heavy development so be sure to prepend ACCEPT_KEYWORDS="~x86" when you install the packages, to get the latest versions.
Code: | ACCEPT_KEYWORDS="~x86" emerge baselayout udev hotplug |
2) Follow the excellent "Gentoo Framebuffer, Bootsplash & Grubsplash How-To".
https://forums.gentoo.org/viewtopic.php?t=49036
3) And finally you add the framebuffer device manually to /dev.
Code: | mknod -m 660 /dev/fb0 c 29 0 |
Reboot and enjoy the eye candy
See also:
http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html
Feel free to post other solutions or patches from mm and/or love sources or any suggestions. |
|
Back to top |
|
|
trawi n00b
Joined: 13 Feb 2004 Posts: 28
|
Posted: Wed Mar 17, 2004 9:13 am Post subject: Do you use /dev tarball saving? |
|
|
I have disabled /dev tarball saving in /etc/conf.d/rc
Code: |
RC_DEVICE_TARBALL="no"
RC_DEVFSD_STARTUP="no"
|
The result is pretty strange:
- Framebuffer & Bootsplash does work fine
- I get a lots of /dev/fb0 no such file errors
Problem is that fbset is looking for /dev/fb0 which isn't created by udev. If I create /dev/fb0 with:
Code: |
mknod -m 660 /dev/fb0 c 29 0
|
fbset is working fine, but the /dev/fb0 entry is lost after the next reboot. I'm probably going to add the mknod command to /sbin/rc as a temporary solution.
Looks like ist a bug in /sbin/splash I have filed a bug for it: https://bugs.gentoo.org/show_bug.cgi?id=44932 |
|
Back to top |
|
|
Jefklak l33t
Joined: 26 Oct 2003 Posts: 818 Location: Belgium
|
Posted: Wed Mar 17, 2004 10:49 am Post subject: |
|
|
You should stay away from rc. Yust add it:
Code: | echo "mknod -m 660 /dev/fb0 c 29 0" > /etc/conf.d/local.start |
That also works. |
|
Back to top |
|
|
Lorijho n00b
Joined: 22 Jul 2003 Posts: 38 Location: Luxembourg
|
Posted: Wed Mar 17, 2004 1:43 pm Post subject: |
|
|
@ trawi
For your configuration
Code: | echo "mknod -m 660 /dev/fb0 c 29 0" > /etc/conf.d/local.start |
is definitely required to get framebuffer working. |
|
Back to top |
|
|
trawi n00b
Joined: 13 Feb 2004 Posts: 28
|
Posted: Thu Mar 18, 2004 10:25 am Post subject: Framebuffers & Bootsplash does work fine without /dev/fb |
|
|
Did dig through /sbin/splash. Funny thing is that you don't need /dev/fb0 for bootsplash. It is only need by fbresolution in /sbin/splash to determine the screensize.
My quick solution was to disable fbresolution and harcode res.
Code: |
#
# Source theme config file
#
#if [ ! -x /sbin/fbresolution ]; then
# echo "$0: '/sbin/fbresolution' does not exist on your system... aborting !"
#else
# res="$(/sbin/fbresolution)"
#fi
res="1024x768"
|
Since that I live a happy life with one entry less in /dev (I'm now down to 157). |
|
Back to top |
|
|
Admiral LSD Guru
Joined: 27 Jun 2003 Posts: 522 Location: Northam, W.A., Australia
|
Posted: Sun Mar 21, 2004 11:40 am Post subject: |
|
|
A more permanent solution to this problem can be achieved by applying this patch to your kernel sources:
http://home.insightbb.com/~g.rude/Linux_patches/fb_sysfs_udev.patch
What's happening is that, for udev to create a node for a give device the driver for said device has to make info available in the sysfs and none of the framebuffer drivers do that at present. This patch fixes that. I've used it successfully on kernels 2.6.3, 2.6.4 and 2.6.5-rc1 without any trouble. _________________ Wasurenaide...
...watashi ga iru koto o.
Itsudatte soba ni iru yo.
Registered Linux user #319839 |
|
Back to top |
|
|
Luud Apprentice
Joined: 05 Jun 2003 Posts: 246 Location: Netherlands
|
Posted: Mon May 10, 2004 2:39 pm Post subject: |
|
|
Just looked in the 2.6.5 -> 2.6.6 changelog and it seems the framebuffer sysfs patch is mainstream now: Quote: | <kronos@kronoz.cjb.net>
[PATCH] Sysfs for framebuffer
the following patch (against 2.6.5-rc2) teaches fb to use class_simple.
With this patch udev will automagically create device nodes for each
framebuffer registered. Once all drivers are converted to
framebuffer_{alloc,release} we can switch to our own class.
This is what sysfs dir looks like:
notebook:~# tree /sys/class/graphics/
/sys/class/graphics/
`-- fb0
`-- dev
|
So we will see this when gentoo-dev-sources switches to 2.6.6.
Cheers _________________ "Great minds don't think alike. If they did, the patent office would only have about fifty inventions." - Wally |
|
Back to top |
|
|
mlybarger Guru
Joined: 04 Sep 2002 Posts: 475
|
Posted: Sat Jun 12, 2004 9:24 pm Post subject: |
|
|
well, it seems tha thte gentoo-dev-sources still isn't up to 2.6.6 yet. i created the node as described above, and can now use links in a fb console. but the links area is about 1/4 of the entire screen area (upper left). strange.
any ideas why links is taking up so little space? |
|
Back to top |
|
|
yogipsu Tux's lil' helper
Joined: 30 Aug 2003 Posts: 98
|
Posted: Mon Jun 14, 2004 12:24 am Post subject: |
|
|
Had the same problem.
In /etc/fb.modes, the buffer will auto-default to the first resolution listed, so change the first one to whatever your FB resolution is. This should fix the problem. |
|
Back to top |
|
|
|