View previous topic :: View next topic |
Author |
Message |
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
|
Back to top |
|
|
merkaba n00b
Joined: 10 Jul 2003 Posts: 56
|
Posted: Thu Jan 01, 2004 2:33 am Post subject: |
|
|
damn you guys are fast.
i was just going to pop on here and mention about 012.
for those that don't want to live quite so dangerously i expect someone who actually knows what they're doing will come along and we'll have an official ebuild in portage within the next day or two.
oh, the bit about adding gentoo rules & permissions - these are just included with the official release now. they appear to be identical to the ones that the ebuild was already installing from the files directory before.
edit: make that hours. bug's been resolved & ebuild can apparently be expected in the next sync. they're certainly on the ball around here. |
|
Back to top |
|
|
asimon l33t
Joined: 27 Jun 2002 Posts: 979 Location: Germany, Old Europe
|
Posted: Thu Jan 01, 2004 5:40 pm Post subject: |
|
|
With devfs I got links like /dev/dvd or /dev/cdwriter to the actual devices. What would be the right strategy to get such aliases with udev?
I thought something like
Code: |
REPLACE, KERNEL="hdb", NAME="dvd", SYMLINK="%k"
REPLACE, KERNEL="hdd", NAME="cdwriter", SYMLINK="%k"
|
in /etc/udev/udev.rules.
Is this the right way to get such symlinks, or are there better ways? |
|
Back to top |
|
|
Kompi Apprentice
Joined: 05 Oct 2002 Posts: 252 Location: Germany
|
Posted: Thu Jan 01, 2004 5:53 pm Post subject: |
|
|
According to what Decibels said some posts before:
Quote: | Things are changing in udev, but I don't think Gentoo is using those scripts yet, at least I haven't seen any evidence of it yet. They use a devices.tar.bz2 file to populate the /dev. There is a off chance that it does, and if you have a device that is seen correctly and not in devices.tar.bz2 that it might create it. |
So, you can try out if there's any reaction from udev, if you change udev.rules.
If not, you could just create the links manually, i.e. ln -s /dev/hdb /dev/dvd. They will be stored in devices.tar.bz2 when your system shuts down. So next startup the links will still be there. |
|
Back to top |
|
|
rincewind Apprentice
Joined: 16 Aug 2002 Posts: 172 Location: Essen, Germany
|
Posted: Thu Jan 01, 2004 11:16 pm Post subject: |
|
|
For those who are interested :
I figured out why my system got borked, I updated bzip2 with the buggy gcc-3.2.3-r2 so every shutdown I got garbage in my devices.tar.bz2.
But Is is possible to add a script to the udev startup-sequence that in case the file could not be extracted the system goes with devsd ? |
|
Back to top |
|
|
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
Posted: Thu Jan 01, 2004 11:47 pm Post subject: |
|
|
asimon I agree with Kompi. There is a file called /etc/udev/udev.rules.devfs that you might want to play with.
Report any success or failures.
Think I am going to play with 012 here for a bit and see anything
changed for me. _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
|
ValKov n00b
Joined: 17 May 2003 Posts: 71 Location: Russin Federation
|
Posted: Fri Jan 02, 2004 7:25 am Post subject: |
|
|
Hi, all
I have udev-012 installed, and everything seems o'k. Just small problem with AverMedia TV Studio. Wnen I run gQradio, I have no stations, just noise Presets are o'k. After restarting gQradio I have all my stations. With devfs I hadn't this problem... |
|
Back to top |
|
|
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
Posted: Fri Jan 02, 2004 2:08 pm Post subject: |
|
|
udev-012, not much change in results. Does depend on more files now:
Code: | bash-2.05b# emerge -Up udev
>>> --upgradeonly implies --update... adding --update to options.
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild U ] sys-libs/zlib-1.2.1-r2 [1.2.1]
[ebuild U ] sys-devel/gcc-3.3.2-r5 [3.3.2-r4]
[ebuild U ] sys-libs/glibc-2.3.3_pre20031222 [2.3.3_pre20031212]
[ebuild U ] sys-apps/gawk-3.1.3-r1 [3.1.3]
[ebuild N ] app-crypt/hashalot-0.1.0
[ebuild U ] sys-devel/autoconf-2.58 [2.57-r1]
[ebuild U ] sys-devel/automake-1.7.8 [1.7.5-r2]
[ebuild U ] sys-apps/miscfiles-1.3-r1 [1.3]
[ebuild U ] sys-libs/cracklib-2.7-r8 [2.7-r7]
[ebuild U ] sys-libs/pam-0.77 [0.75-r11]
[ebuild U ] sys-apps/pam-login-3.14 [3.11]
[ebuild U ] sys-apps/util-linux-2.12-r4 [2.11z-r8]
[ebuild U ] sys-apps/baselayout-1.8.6.12-r3 [1.8.6.12-r2]
[ebuild U ] sys-fs/udev-012 [011] |
Couple things noticed is two more init scripts look for udev now:
Code: |
1) /etc/init.d/consolefont now checks for udev
2) /etc/init.d/numlock now checks for udev |
Did see a little improvement (I think) in syslog for udev/hotplug/sysfs.
It recognizes both microtek scanner and mouse, both usb, vendor/product id's. Still doesn't know what to do with them. Mainly complains they are not a valid block device.
So, small step forward. Looks like from what I have seen in the scripts that Gentoo is working not toward using udev as 'replacement', but making udev work with the devfs naming scheme, so that everything will be as close as possible to how it was with devfs, just using udev to do it. Did I write that clear enough?
Another thing found during this update: the file that sets the permissions for devices upon login/logout.
3) File that sets lot of device permissions at login and logout.
/etc/security/console.perms Code: | # This file determines the permissions that will be given to priviledged
# users of the console at login time, and the permissions to which to
# revert when the users log out. |
_________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
|
rommel Veteran
Joined: 19 Apr 2002 Posts: 1145 Location: Williamsburg Virginia
|
Posted: Sat Jan 03, 2004 10:50 pm Post subject: |
|
|
hey i have udev working but i have noticed two errors... when hotplug loads the usb devices at boot it gives a fatal error cant find mousedev and xmms doesnt work any longer... anyone have an idea on either.. sound is working |
|
Back to top |
|
|
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
Posted: Sun Jan 04, 2004 1:49 am Post subject: |
|
|
rommel wrote: | hey i have udev working but i have noticed two errors... when hotplug loads the usb devices at boot it gives a fatal error cant find mousedev and xmms doesnt work any longer... anyone have an idea on either.. sound is working |
I get the mousedev also and a couple others think, haven't booted to that partition for a while, but think is related to this bug, haven't tried the response on it yet to see if will work. Guess could tonight if think about it.
https://bugs.gentoo.org/show_bug.cgi?id=37086
Just an idea.
LATER:: Well, that ended up getting rid of one, the snd_ens1371 error, but not the mousedev or input. Besides, 'q' option is just for 'quiet'. It just surpresses the error messages and don't think that is really a fix. Not really broken though, works.
I think some of this has to do with module-init-tools, didn't use to see this stuff before until started putting module info in the /etc/modules.autoload.d/kernel files. Maybe there is a connection between
this and /etc/modules.autoload . I think may be removed entries from one or the other, but didn't test it fully to see what was up. The good thing is it just produces errors and doesn't really seem to do anything, just looks bad. _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
|
rommel Veteran
Joined: 19 Apr 2002 Posts: 1145 Location: Williamsburg Virginia
|
Posted: Sun Jan 04, 2004 3:41 am Post subject: |
|
|
hey Decibels.... well your right the error is more an annoyance then a problem , and send -q to shut it up isnt much good , so we agree there too.. i am running a 12" g4 powerbook and had pbbuttonsd installed and it needs /dev/pmu to function so anyone else using a mac and pbbuttons you'l need to Code: | mknod /dev/pmu c 10 154 | still havent a clue what happened to xmms , everything else i have checked so far has sound.
ciao
edit:well not that its much better then -q but in the case of my mousedev error i added it to the /etc/hotplug/blacklist .... it will stop hotplug from trying to load it and obviously no more error... mousedev is no longer available as a module so this works for me. |
|
Back to top |
|
|
theine n00b
Joined: 08 Jun 2003 Posts: 7
|
Posted: Mon Jan 12, 2004 10:51 am Post subject: |
|
|
Hi Decibels,
I think your modifications in /etc/fstab are not needed -- at least not any more.
In /sbin/rc
Code: |
if [ -d /sys -a "$(get_KV)" -ge "$(KV_to_int '2.6.0')" ]
then
ebegin "Mounting sysfs at /sys"
mount -t sysfs none /sys
eend $?
|
as well as
Code: |
if [ -d /dev/pts ]
then
ebegin "Mounting devpts at /dev/pts"
try mount -n -t devpts none /dev/pts
eend $?
|
So obviously there is no information required from /etc/fstab. |
|
Back to top |
|
|
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
Posted: Tue Jan 13, 2004 3:51 am Post subject: |
|
|
Udev Primer wrote: | 5) Udev needs to know where sysfs is mounted. You will need to add an entry to /etc/fstab.
Add: none /sys sysfs defaults 0 0 .
Gentoo is now handling the mounting of devpts now. So you don't have to add an entry to /etc/fstab. I haven't had any issues with it in fstab, but if you do, it is safe to remove that entry now. If you are having a problem with devpts not mounting and not being able to open a console session, you should probably look for other issues causing this. But, if you think not having an entry for it in /etc/fstab is your problem.
Add: none /dev/pts devpts defaults 0 0 . |
Okay, thanks. I already added the removal of /dev/pts to fstab while back. I will look into removing the sysfs entry tomorrow. Thanks for the heads up.
Haven't been looking at this much lately due to nothing really new happening and Gentoo using the devices.tar.bz2 file (because udev isn't really ready yet). I did check out 2.6.1 kernel though.
If you find something like this has changed, let me know so can update the Udev Primer. Otherwise I will go back to working on my python stocks app again. _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
|
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
Posted: Wed Jan 14, 2004 1:50 am Post subject: |
|
|
Curious, did you test if still have to make the /sys folder manually? Haven't had time to test/look yet.
Just wondering, cause have in the tutorial (according to docs) that you have to make the folder in /. Is that still the case? Might as well change both the /sys notes if that is also now the case.
Only thing gotten too so far is that sys doesn't have to be mounted now in fstab. df -a shows everything mounted without it. If don't hear from you will test it out this weekend I guess. Then will remove both references in tutorial. _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
|
latexer Retired Dev
Joined: 05 Mar 2003 Posts: 239 Location: NYC
|
Posted: Thu Jan 15, 2004 3:59 pm Post subject: Patches for sysfs support for input, alsa, oss, etc |
|
|
Hey all,
2.6.1-mm3 has patches from gregkh (the udev guy) to add sysfs support to input, alsa, oss, etc stuff. What this means is udev now sees these devices!
I've got a system running purely udev, and i've commented out the silly tarball stuff to populate /dev since udev is handling *all of it* now. To put the alsa and input stuff in the "traditional" location, add this stuff to your /etc/udev/udev.rules:
Code: |
# input devices
KERNEL="mice", NAME="input/%k"
KERNEL="keyboard", NAME="input/%k"
KERNEL="mouse*", NAME="input/%k"
KERNEL="event*", NAME="input/%k"
KERNEL="js*", NAME="input/%k"
KERNEL="ts*", NAME="input/%k"
# alsa devices
KERNEL="controlC[0-9]", NAME="snd/%k"
KERNEL="pcm*", NAME="snd/%k"
KERNEL="hw[0-9]", NAME="snd/%k"
KERNEL="midi[0-9]", NAME="snd/%k"
KERNEL="timer", NAME="snd/%k"
KERNEL="seq", NAME="snd/%k"
KERNEL="mixer", NAME="snd/%k"
|
(this assumes you're running udev-013, if you're not, add "REPLACE, " to the beginning of each of these lines)
Only problems i'm having are with alsactl not actually restoring mixer settings on rebooting. Other than that sound, X, etc all work.
good luck all. (:
---
edit - forgot one node for alsa stuff _________________ overlays - Use at your own risk. File bug reports on this stuff and i'll kick you in the junk. Ask me before asking upstream if these fail. I mean it. No, really.
#gentoo-dotnet on freenode |
|
Back to top |
|
|
infirit l33t
Joined: 11 Jan 2003 Posts: 778 Location: Hoofddorp / The Netherlands
|
Posted: Fri Jan 16, 2004 10:28 pm Post subject: |
|
|
There is a new version of udev available 013-r1 which has the alsa and input stuf.
A couple of devices need to e added by hand like nvidia and nvidiactl. Also i'm having a weird permission thing going on My alsa devices are owned by a normal user (me) and not root as specified in udev.permissions. Are there more people with this? _________________ EASY TO INSTALL = Difficult to install, but instruction manual has pictures.
Join the adopt an unanswered post initiative today |
|
Back to top |
|
|
TheCoop Veteran
Joined: 15 Jun 2002 Posts: 1814 Location: Where you least expect it
|
Posted: Fri Jan 16, 2004 11:33 pm Post subject: |
|
|
unfortunately, when i try to run an entirely udev setup, it complains about not being able to mount root and stalls. The only devices in /dev are initctl, null, ./pts and ./shm. whats in the relevant parts of /sbin/rc and /etc/udev/* for you? _________________ 95% of all computer errors occur between chair and keyboard (TM)
"One World, One web, One program" - Microsoft Promo ad.
"Ein Volk, Ein Reich, Ein Führer" - Adolf Hitler
Change the world - move a rock |
|
Back to top |
|
|
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
Posted: Fri Jan 16, 2004 11:52 pm Post subject: Re: Patches for sysfs support for input, alsa, oss, etc |
|
|
latexer wrote: | Hey all,
2.6.1-mm3 has patches from gregkh (the udev guy) to add sysfs support to input, alsa, oss, etc stuff. What this means is udev now sees these devices!
|
I haven't tried the 2.6.1-mm3 sources yet, still working on the plain 2.6.1, but was able to get it up, strictly udev.
Emerged the udev-013-r1 and commented out the devices.tar.bz2 in rc script.
Before switch over to the mm3 sources, was wondering a few things.
In order to get system up to X, still had to mknod /dev/mem and my /dev/input/mice. Then still had to make the nvidia devices.
The big question: Looking in the new udev.rules can see the alsa, input.... stuff in there. But there was no /dev/snd or /dev/input folder made.
SO, will mm3 sources make the difference on this? Are those folders going to be made?
Further look in the rules and see /dev/dsp, sequencer,.... in there and they are missing also. System seems okay, except for the few things had to do at beginning and no sound. Will probably end up trying the mm3 sources before get these questions answered. _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
|
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
Posted: Sat Jan 17, 2004 12:28 am Post subject: |
|
|
I would also suggest that if going to try the pure udev system without the devices.tar.bz2, you might also want to comment out the part in /etc/init.d/halt.sh where it saves the file.
Code: | then
ebegin "Saving device nodes"
#cd /dev
#try tar -jclpf "/tmp/devices-$$.tar.bz2" *
#try mv -f "/tmp/devices-$$.tar.bz2" /lib/udev-state/devices.tar.bz2
eend 0
fi |
Your going to loose a lot of devices if it doesn't work and you want to go back. Thinking of this probably saved myself some time, if wanted to go back to previous way. _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
|
infirit l33t
Joined: 11 Jan 2003 Posts: 778 Location: Hoofddorp / The Netherlands
|
Posted: Sat Jan 17, 2004 12:30 am Post subject: Re: Patches for sysfs support for input, alsa, oss, etc |
|
|
Decibels wrote: | SO, will mm3 sources make the difference on this? Are those folders going to be made? | All 2.6.1-mm patches will do and yes this makes the difference, from the 2.6.1-mm4 announce Quote: | -sysfs-add-simple-class-device-support.patch
-sysfs-remove-tty-class-device-logic.patch
-sysfs-add-mem-device-support.patch
-sysfs-add-misc-class.patch
-vc-init-race-fix.patch
-sysfs-add-video-class.patch
-sysfs-add-oss-class.patch
-sysfs-add-alsa-class.patch
-sysfs-add-input-class-support.patch
+sysfs-class-01-simple.patch
+sysfs-class-02-input.patch
+sysfs-class-03-lp.patch
+sysfs-class-04-mem.patch
+sysfs-class-05-misc.patch
+sysfs-class-06-raw.patch
+sysfs-class-07-oss-sound.patch
+sysfs-class-08-alsa-sound.patch
+sysfs-class-09-cleanup-tty.patch
+sysfs-class-10-vc.patch |
Currently i'm running love3 (based on mm3) and its working perfect _________________ EASY TO INSTALL = Difficult to install, but instruction manual has pictures.
Join the adopt an unanswered post initiative today |
|
Back to top |
|
|
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
Posted: Sat Jan 17, 2004 1:59 am Post subject: |
|
|
Got the mm4 sources also, just a bit ago and it did make a big difference.
Still there is problems, do you have these problems also with it.
1) /dev/dsp and /dev/dsp#
According to the rules, they put it in /dev/sound. But don't have them directly in /dev or in /dev/sound. So aRts doesn't work. Funny thing though. Restarted /etc/init.d/alsasound and used 'play' to play a wave and worked. After that told control center to play a sound and worked.
***** Tested this out: Kde starts and complains of no /dev/dsp or nothing in /dev/sound. Restart alsasound and bamb, everything shows up. Looks like a big delay. They should start at boot. Going to see if adding alsasound restart to local.start does anything.
Put in local.start and works at bootup. Unfortunetely little bit later get error: Sound server fatal error: cpu overload, aborting. Then sound is just noise after that. Then after awhile works again.
I notice there is a 'artsd -a' option to choose also, though when do -A it doesn't give it as an option and chosing 'arts -a alsa':
Code: | bash-2.05b$ artsd -a alsa
Error while initializing the sound driver:
unable to select 'alsa' style audio I/O |
Hmmm, maybe I didn't compile kde with alsa support, keeps chosing oss.
Alsa is in USE flags, going to recompile arts and see what happens.
Later: Fixed Emerged arts-1.1.5 and give choice for alsa now, changed it in the control panel and removed the lines for /dev/sound and restarting alsasound in local.start. Alsa works fine now.
Notice that /dev/sound wasn't created now since removed line, but guess isn't necessary since using Alsa.
2) Nvidia devices not made so put them in local.start also.
3) It still doesn't know what to do with my scanner. Microteck Scanmaker V6UPL. See's problem at bootup. Doesn't want to create any sg devices.
I want my darn scanner to work! grrrh
Looks like closer, but still problems. Tried adding sg stuff to udev.rules and not getting it right or not working.
Still, nice being able to do away with the tarball and see how it is actually working now. _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
|
Chaosite Guru
Joined: 13 Dec 2003 Posts: 540 Location: Right over here.
|
Posted: Sat Jan 17, 2004 9:51 am Post subject: Re: Patches for sysfs support for input, alsa, oss, etc |
|
|
infirit wrote: |
Currently i'm running love3 (based on mm3) and its working perfect |
Umm... love3 is only based on mm2, not mm3... |
|
Back to top |
|
|
nepenthe Guru
Joined: 14 Jul 2002 Posts: 317 Location: Sanford, ME
|
|
Back to top |
|
|
TheCoop Veteran
Joined: 15 Jun 2002 Posts: 1814 Location: Where you least expect it
|
Posted: Sat Jan 17, 2004 6:54 pm Post subject: |
|
|
udev-only still doesnt work for me - complains about not having /dev/console or /dev/hda*, which are kind of necessary for bootup... _________________ 95% of all computer errors occur between chair and keyboard (TM)
"One World, One web, One program" - Microsoft Promo ad.
"Ein Volk, Ein Reich, Ein Führer" - Adolf Hitler
Change the world - move a rock |
|
Back to top |
|
|
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
Posted: Sat Jan 17, 2004 11:06 pm Post subject: |
|
|
I assume you did all the stuff mentioned.
1) Comment out the /sbin/rc script line to load the tarball.
Code: | then
ebegin "Mounting ramfs at /dev"
try mount -n -t ramfs none /dev
eend $?
ebegin "Configuring system to use udev"
einfo " Populating /dev with device nodes..."
##try tar -jxpf /lib/udev-state/devices.tar.bz2 -C /dev |
2) emerge the udev-013 or greater and one of the sources other than vanilla. Think 2.6.1-mm3, 2.6.1-mm4, love3 (based on mm3 or mm2).
Move new bzImage to /boot folder and rerun lilo/grub.
3)Comment out /etc/init.d/halt.sh line to save the tarball when halt.
Code: | then
ebegin "Saving device nodes"
#cd /dev
#try tar -jclpf "/tmp/devices-$$.tar.bz2" *
#try mv -f "/tmp/devices-$$.tar.bz2" /lib/udev-state/devices.tar.bz2
eend 0
fi |
4) Make sure the new /etc/udev/udev.rules is in place.
5) Add Code: | mknod /dev/nvidia0 c 195 0
mknod /dev/nvidiactl c 195 255 | to /etc/conf.d/local.start if using nvidia drivers.
6) Make sure USE flags in /etc/make.conf has: alsa
And if have any troubles with aRts change 'Sound I/O method' to Alsa' and if that isn't available, recompile arts possibly to 1.1.5 version.
7) The only other things can think of are: have the latest hotplug .
This is more just a recap for those wanting to try it. Cause I figure you tried all this. _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|