| View previous topic :: View next topic |
| Author |
Message |
k2laz
n00b
Joined: 06 Apr 2004
Posts: 55
Location: New York City, USA
|
 Posted: Fri Apr 16, 2004 3:31 am Post subject: Took the udev plunge and... |
 |
|
after a few miscues I was able to install it. I am covering the problems I had and my solutions so that other will not have to suffer (at least not the same way).
I was following the udev guide however I found it lacking in certain areas. First I never trust anything written down, it tends to quickly become outdated, so the first thing I did before doing any of the suggestions was to save my dev directory. The best way to do this is to boot up your gentoo live CD; you know you got one around somewhere. Now mount your real disk, /mnt/gentoo is available just for this so:
mount /dev/hda? /mnt/gentoo. Replace ? with your actual partition.
next go to your old /
cd /mnt/gentoo
now save your dev to a tar in your old root home dir
tar -cvf /mnt/gentoo/root/old-dev.tar dev/
You can now follow the directions in the udev guide without fear of losing anything; and there are a few buggies
The manual says that you will need to remove all of the entries in dev and start with just two: null and console. I found that this is is incorrect. I needed to restore the following items also for my config, maybe others for yours: fb/* and its links fb0...fb15 rd/* and its links ram0..ram15 as well as raminitrd. I don't know if I needed but I also restored vc's and ttys. After that it all worked fine If you are in pinch you can copy the dev items on the live cd from /dev to /mnt/gentoo/dev however you will have to start the udev migration again.
.
I still have to work on the scripts to assign devices by names but at least all of the devices on the base system (ie those that are not plugged in like zips) are working fine including the sound system. I did plug in the mouse and udev assigned it correctly (at least what it was what was in my Xconfig, so Ican't complain). Next I will try to add the zip drive so that it always shows up in the same place, makes mounting a whole lot easier without a moving target.
--laz |
|
| Back to top |
|
 |
k2laz
n00b
Joined: 06 Apr 2004
Posts: 55
Location: New York City, USA
|
| Posted: Tue Apr 27, 2004 10:34 am Post subject: ...had some problems with udev and frame buffers |
|
|
So far, all but one thing is amiss. Udev does a good job with the devices however it fails to create a frame-buffer for the bootsplash, etc. Does anyone know how to configure it? Well I will put udev on hold until I find a good solution to this.
--laz |
|
| Back to top |
|
|
burrelln
n00b
Joined: 08 Apr 2004
Posts: 13
|
| Posted: Tue Apr 27, 2004 3:32 pm Post subject: |
|
|
udev can only deal with devices that use the kernel's sysfs facility. Support for framebuffers in sysfs is very new. You can get it now in 2.6.6-rc2-love1, otherwise I would wait until the official gentoo-dev-sources-2.6.6 release.
To avoid error messages about /dev/fb0 not being found when using bootsplash, you can edit the /etc/init.d/bootsplash script and replace the calls to /sbin/fbresolution with the resolution of your framebuffer. Bootsplash only uses /dev/fb0 when calling /sbin/fbresolution to find out which bootsplash config to use.
-Neil |
|
| Back to top |
|
|
timmfin
Guru
Joined: 04 Sep 2002
Posts: 336
Location: Maryland, USA
|
| Posted: Tue Apr 27, 2004 4:53 pm Post subject: |
|
|
Thanks, that error message was annoying. Do you guys have any problems where alsa is not reloading its mixer volume settings with a pure udev setup (not using the device tarball).
Tim |
|
| Back to top |
|
|
GenKreton
l33t
Joined: 20 Sep 2003
Posts: 828
Location: Cambridge, MA
|
| Posted: Tue Apr 27, 2004 5:02 pm Post subject: |
|
|
its really easy to switch...
all I needed to do was emerge udev, make sure load at boot was not compiled in, and reboot. I had to add myself to the video group as well to play games since it wouldn't let me access nvidiactl, but that's minor. Also tts support is lacking still. |
|
| Back to top |
|
|
steel300
Veteran
Joined: 10 Jul 2003
Posts: 1155
|
| Posted: Tue Apr 27, 2004 5:18 pm Post subject: |
|
|
| GenKreton wrote: | its really easy to switch...
all I needed to do was emerge udev, make sure load at boot was not compiled in, and reboot. I had to add myself to the video group as well to play games since it wouldn't let me access nvidiactl, but that's minor. Also tts support is lacking still. |
You can change the number of tty devices in the newer love's. I made a patch that allowed that to change.
The alsa mixer setting is probably a mismatch of als-lib and alsa-utils with the version of alsa in the kernel.
_________________
Rationality is the recognition of the fact that nothing can alter the truth and nothing can take precedence over that act of perceiving it. |
|
| Back to top |
|
|
Jeld
Tux's lil' helper
Joined: 28 Jun 2002
Posts: 84
Location: NYC, US
|
| Posted: Tue Apr 27, 2004 6:13 pm Post subject: |
|
|
Actualy, I have just created fb0 device manualy, udev will save your changes to /dev tree unless you explicitely prohibit it to do so in /etc/conf.d/rc. The command should be something like
| Code: | | mknod /dev/fb0 c 29 0 |
_________________
package JAPH;sub x{$/='$';@1=map{$_=ord;$_--;chr}
split//,<DATA>;@2=map{$_=ord;$_++;chr}split//
,<DATA>;$_=sub{$.++%2?shift@2:shift@1};bless$_;}
1;$x=JAPH->x;for(1..25){print&$x,;}__DATA__
Kt!ouf!fmIdf"$ts@ngqOq`jq |
|
| Back to top |
|
|
AlterEgo
Veteran
Joined: 25 Apr 2002
Posts: 1619
|
| Posted: Tue Apr 27, 2004 6:39 pm Post subject: Re: ...had some problems with udev and frame buffers |
|
|
| k2laz wrote: | So far, all but one thing is amiss. Udev does a good job with the devices however it fails to create a frame-buffer for the bootsplash, etc. Does anyone know how to configure it? Well I will put udev on hold until I find a good solution to this.
--laz |
You need a kernel patch for this: fb_sysfs_udev.patch |
|
| Back to top |
|
|
k2laz
n00b
Joined: 06 Apr 2004
Posts: 55
Location: New York City, USA
|
| Posted: Tue Apr 27, 2004 6:47 pm Post subject: Thanks for the info on the bootsplash |
|
|
| Jeld wrote: | Actualy, I have just created fb0 device manualy, udev will save your changes to /dev tree unless you explicitely prohibit it to do so in /etc/conf.d/rc. The command should be something like
| Code: | | mknod /dev/fb0 c 29 0 |
|
I tried this approach but it failed for me (it did make shutdown happy  ), but I could not seem to have it saved for the next reboot regardless whether I tried with or without the TARBALL saving. But I will may give a try a little later when I finish my wifi configuring. My Wifi works nicely except I have yet to find a good automated tool for configuring; I am doing it by hand right now; the KDE tool does not seem to work!? I move around a lot with my laptop at campus an they have many, many access points. I may just have to write some bash script to get the names of the available ap and maybe create a preference file to pick the best (or I could just use the signal strength report). That is a little more important than the bootsplash, but a lot less cool 
Thanks everybody,
--laz |
|
| Back to top |
|
|
k2laz
n00b
Joined: 06 Apr 2004
Posts: 55
Location: New York City, USA
|
| Posted: Tue Apr 27, 2004 7:13 pm Post subject: |
|
|
| timmfin wrote: | Thanks, that error message was annoying. Do you guys have any problems where alsa is not reloading its mixer volume settings with a pure udev setup (not using the device tarball).
Tim |
What version linux are you using; linux here is 2.6.3-gentoo-r1 from the "dev-sources" pacakge. Alsa here seems to save them into /etc/asound.state which seems to be stable from one reboot to the next, unlike most of the /dev tree.
--laz
PS, and yes I agree that the fb error messages are annoying.  |
|
| Back to top |
|
|
|
Kernel & Hardware
