Menu
▾
▴
vectorlinux-devel
|
From: Jose J. R. <jo...@gm...> - 2006-04-09 06:49:02
|
Well, I tried Vec's kernel 2.6.16 and udev 088 packages and it works. Sound, network, even the modem which uses the alsa module snd_intel8x0m that I had to manually modprobe in rc.modules before. Parallel port seems to be loaded, though I can't test it ATM. Of course, vl-hot works too. It even coldplugs, that is, if you have a pendrive attached on boot, it will be mounted. Of course, where the heck the desktop icon ends up is anybody's guess, lol, as there's no logged-in user at that point! DRM/DRI failed, but that's probably because Vec forgot the i915 module in the kernel ;). Regards, Joe1962 |
|
From: Jose J. R. <jo...@gm...> - 2006-04-09 08:05:21
|
On 4/9/06, Jose J. Rodriguez <jo...@gm...> wrote: > Of course, vl-hot works too. It even coldplugs, that is, if you have a > pendrive attached on boot, it will be mounted. Of course, where the > heck the desktop icon ends up is anybody's guess, lol, as there's no > logged-in user at that point! > Guess I spoke too soon! After some careful study and testing, I found that the udev.rules file has mounting/unmounting rules for usb devices, that call /lib/udev/usbmount.sh, which conflicts with vl-hot. It turned out vl-hot was doing the mounting, but usbmount.sh was doing the unmounting, bith to different mountpoints, which is of course bad. I have modified the vl-hot rules and scripts to use the /lib/udev dir, as is now standard, instead of /etc/udev/scripts. I also made the necessary mods to get it working with this new udev version (required mods to 10-vl-hot.rules). I could modify usbmount.sh for our purposes, but vl-hot is already there and more complete (if I do say so myself, lol). The vl-hot rules are also designed to handle more than just usb devices (which means I must check udev.rules for further interference in the case of pccard or firewire drives). Anyway, I suggest we stick to vl-hot for now, meaning some stuff has to be commented out in udev.rules. So far this is limited to the usb devices in lines 24 and 26, like this: # USB storage devices #KERNEL=3D"sd?[0-9]*", ACTION=3D=3D"add", BUS=3D=3D"usb", NAME=3D"%k", SYMLINK=3D"usbmedia%e", GROUP=3D"cdrom", MODE=3D"0660", RUN+=3D"/lib/udev/usbmount.sh add /dev/%k" KERNEL=3D"ub?[0-9]*", ACTION=3D=3D"add", BUS=3D=3D"usb", NAME=3D"%k", SYMLINK=3D"usbmedia%e", GROUP=3D"cdrom", MODE=3D"0660", RUN+=3D"/lib/udev/usbmount.sh add /dev/%k" #KERNEL=3D"sd?[0-9]*", ACTION=3D=3D"remove", RUN+=3D"/lib/udev/usbmount.sh remove /dev/%k" KERNEL=3D"ub?[0-9]*", ACTION=3D=3D"remove", RUN+=3D"/lib/udev/usbmount.sh remove /dev/%k" I'll leave the ub devices to usbmount.sh, lol. I'm calling this a new branch of vl-hot, 0.3.0, and it's committed to the SF cvs already. If you want it and don't want to mess with the cvs yet, just let me know. Regards, Joe1962 |
|
From: Jose J. R. <jo...@gm...> - 2006-04-09 08:21:37
|
On 4/9/06, Jose J. Rodriguez <jo...@gm...> wrote: > On 4/9/06, Jose J. Rodriguez <jo...@gm...> wrote: > > > Of course, vl-hot works too. It even coldplugs, that is, if you have a > > pendrive attached on boot, it will be mounted. Of course, where the > > heck the desktop icon ends up is anybody's guess, lol, as there's no > > logged-in user at that point! > > > > I'm calling this a new branch of vl-hot, 0.3.0, and it's committed to > the SF cvs already. If you want it and don't want to mess with the cvs > yet, just let me know. > Sorry, forgot one little detail, lol. You need to edit /etc/sudoers to reflect the change in path for vl-hot, like this: from: MOUNT1=3D/etc/udev/scripts/vl-hot_mount,/etc/udev/scripts/vl-hot_umou= nt, ..... to: MOUNT1=3D/lib/udev/vl-hot_mount,/lib/udev/vl-hot_umount, ..... In actual fact, only vl-hot_umount is relevant in /etc/sudoers, as this is only needed to allow the desktop icon to unmount the drive. Regards, Joe1962 |
|
From: Tony B. <tb...@gm...> - 2006-04-09 12:43:22
|
You need to disable hotplug. echo "/dev/null" > /proc/sys/kernel/hotplug On boot or hotplug will continue to work. On 4/9/06, Jose J. Rodriguez <jo...@gm...> wrote: > > On 4/9/06, Jose J. Rodriguez <jo...@gm...> wrote: > > On 4/9/06, Jose J. Rodriguez <jo...@gm...> wrote: > > > > > Of course, vl-hot works too. It even coldplugs, that is, if you have = a > > > pendrive attached on boot, it will be mounted. Of course, where the > > > heck the desktop icon ends up is anybody's guess, lol, as there's no > > > logged-in user at that point! > > > > > > > I'm calling this a new branch of vl-hot, 0.3.0, and it's committed to > > the SF cvs already. If you want it and don't want to mess with the cvs > > yet, just let me know. > > > > Sorry, forgot one little detail, lol. You need to edit /etc/sudoers to > reflect the change in path for vl-hot, like this: > > from: > MOUNT1=3D/etc/udev/scripts/vl-hot_mount,/etc/udev/scripts/vl-hot_umount, > ..... > to: MOUNT1=3D/lib/udev/vl-hot_mount,/lib/udev/vl-hot_umount, ..... > > In actual fact, only vl-hot_umount is relevant in /etc/sudoers, as > this is only needed to allow the desktop icon to unmount the drive. > > Regards, > Joe1962 > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmdlnk&kid=110944&bid$1720&dat=121642 > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > |
|
From: Jose J. R. <jo...@gm...> - 2006-04-09 12:58:18
|
On 4/9/06, Tony Brijeski <tb...@gm...> wrote: > You need to disable hotplug. > > echo "/dev/null" > /proc/sys/kernel/hotplug > > On boot or hotplug will continue to work. > Interesting, at the start of Vec's rc.udev there is the following: =09# disable hotplug helper, udevd listens to netlink =09echo "" > /proc/sys/kernel/hotplug Is it the same thing? Regards, Joe1962 |
|
From: Tony B. <tb...@gm...> - 2006-04-09 13:26:12
|
Basically the same thing. If the kernel doesn't complain about this, then it is fine. IF it complains, just change it to /dev/null. On 4/9/06, Jose J. Rodriguez <jo...@gm...> wrote: > > On 4/9/06, Tony Brijeski <tb...@gm...> wrote: > > You need to disable hotplug. > > > > echo "/dev/null" > /proc/sys/kernel/hotplug > > > > On boot or hotplug will continue to work. > > > > Interesting, at the start of Vec's rc.udev there is the following: > > # disable hotplug helper, udevd listens to netlink > echo "" > /proc/sys/kernel/hotplug > > Is it the same thing? > > Regards, > Joe1962 > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmdlnk&kid=110944&bid$1720&dat=121642 > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > |
|
From: Jose J. R. <jo...@gm...> - 2006-04-12 13:21:28
|
The new kernel 2.6.16 + udev 0.88 stuff causes a problem in D4X (probably in other apps, too), where there is no sound and an error of missing /dev/dsp is given. Maybe this device needs to be preset in /lib/udev/devices? Or is there another way to handle this? Regards, Joe1962 |
|
From: Jose J. R. <jo...@gm...> - 2006-04-12 13:40:51
|
On 4/12/06, Jose J. Rodriguez <jo...@gm...> wrote: > The new kernel 2.6.16 + udev 0.88 stuff causes a problem in D4X > (probably in other apps, too), where there is no sound and an error of > missing /dev/dsp is given. Maybe this device needs to be preset in > /lib/udev/devices? Or is there another way to handle this? > Well, possibly answering my own question. Found this in an udev primer: ---------------------------------------------------------------------------= --- Mixer/Midi/Dsp Devices: Some people, including me, report that the /dev/mixer isn't being created or /dev/midi or /dev/dsp. The problem is not udev. If you compiled your kernel with them as modules you have to load them in /etc/modules.autoload.d/kernel-2.6. So if those devices aren't being created add: snd_pcm_oss & snd_seq_oss to kernel-2.6 file. The snd_pcm_oss will load snd_mixer_oss itself. snd_mixer_oss alias is /dev/mixer snd_pcm_oss alias is /dev/dsp snd_seq_oss alias is /dev/midi ---------------------------------------------------------------------------= --- So those need to be loaded manually in rc.modules still? Regards, Joe1962 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X