headers
Kay Sievers | 1 Mar 2006 20:02

Re: typo in udev_run_hotplugd.c

On Wed, Feb 22, 2006 at 06:49:56AM +0900, Masatake YAMATO wrote:
> Hi,
> 
> I found a very small typo in 
> udev-085/extras/run_directory/udev_run_hotplugd.c.patch.

Applied.

Thanks,
Kay

-------------------------------------------------------
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?cmd=lnk&kid=110944&bid=241720&dat=121642
Permalink | Reply | 0 comments |
headers
Ricardo Biloti | 1 Mar 2006 20:31
Picon
Gravatar

udev fails to create sda* for usb pendrive

Hy guys.

I'm experiencing a curious problem. I'm using Debian sarge (upgraded
from a woody installation), with kernel 2.6.13, udev 0.56 (from my
distro).

I was trying that my pendrive was recognized and mounted automatically
when inserted. I installed then hal, udev, pmount and
gnome-volume-manager. The last one at least seems to work since my USB
camera is recognized and an application pops up to handle it
correctly. It is a hole different situation when the pendrive is
inserted.

Take a look at syslog just after it is inserted:

Mar  1 07:30:02 caruara kernel: usb 1-2: new full speed USB device
using uhci_hcd and address 2
Mar  1 07:30:02 caruara kernel: scsi0 : SCSI emulation for USB Mass
Storage devices
Mar  1 07:30:02 caruara kernel: usb-storage: device found at 2
Mar  1 07:30:02 caruara kernel: usb-storage: waiting for device to
settle before scanning
Mar  1 07:30:02 caruara usb.agent[4256]:      usb-storage: already loaded
Mar  1 07:30:07 caruara kernel:   Vendor: Kingston  Model:
DataTraveler 2.0  Rev: 4.10
Mar  1 07:30:07 caruara kernel:   Type:   Direct-Access               
      ANSI SCSI revision: 02
Mar  1 07:30:07 caruara kernel: usb-storage: device scan complete

I expected that /dev/sda (and its partitions) were created by udev,
(Continue reading)

Permalink | Reply | 2 comments |
headers
Greg KH | 1 Mar 2006 22:00
Gravatar

Re: udev fails to create sda* for usb pendrive

On Wed, Mar 01, 2006 at 04:31:41PM -0300, Ricardo Biloti wrote:
> Hy guys.
> 
> I'm experiencing a curious problem. I'm using Debian sarge (upgraded
> from a woody installation), with kernel 2.6.13, udev 0.56 (from my
> distro).

I'd really recommend upgrading both your kernel and your version of udev
if you wish to get help here.  There's not much we can do about very old
kernel and udev versions, sorry.

I also see that you already filed this as a bug with debian.  Why not
wait to see how it works out there first?

> I was trying that my pendrive was recognized and mounted automatically
> when inserted. I installed then hal, udev, pmount and
> gnome-volume-manager. The last one at least seems to work since my USB
> camera is recognized and an application pops up to handle it
> correctly. It is a hole different situation when the pendrive is
> inserted.
> 
> Take a look at syslog just after it is inserted:
> 
> Mar  1 07:30:02 caruara kernel: usb 1-2: new full speed USB device
> using uhci_hcd and address 2
> Mar  1 07:30:02 caruara kernel: scsi0 : SCSI emulation for USB Mass
> Storage devices
> Mar  1 07:30:02 caruara kernel: usb-storage: device found at 2
> Mar  1 07:30:02 caruara kernel: usb-storage: waiting for device to
> settle before scanning
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ricardo Biloti | 1 Mar 2006 23:16
Picon
Favicon

Re: udev fails to create sda* for usb pendrive

On 3/1/06, Greg KH <greg <at> kroah.com> wrote:
> On Wed, Mar 01, 2006 at 04:31:41PM -0300, Ricardo Biloti wrote:
> > Hy guys.
> >
> > I'm experiencing a curious problem. I'm using Debian sarge (upgraded
> > from a woody installation), with kernel 2.6.13, udev 0.56 (from my
> > distro).
>
> I'd really recommend upgrading both your kernel and your version of udev
> if you wish to get help here.  There's not much we can do about very old
> kernel and udev versions, sorry.

That's because I'm running udev from my distro. Updating it means
migrating from stable  to unstable debian, which is more than what I
want to do.

>
> I also see that you already filed this as a bug with debian.  Why not
> wait to see how it works out there first?

You are right. I apologize for that.

>
> > I was trying that my pendrive was recognized and mounted automatically
> > when inserted. I installed then hal, udev, pmount and
> > gnome-volume-manager. The last one at least seems to work since my USB
> > camera is recognized and an application pops up to handle it
> > correctly. It is a hole different situation when the pendrive is
> > inserted.
> >
(Continue reading)

Permalink | Reply | 0 comments |
headers
Albert Veli | 3 Mar 2006 14:20
Favicon

Udev + /dev/rtf

Hi,

I have a question about udev and /dev/rtf* device nodes. They are needed
to interact with the module rtai_fifos.ko (part of RTAI, a Linux
realtime extension).

But I'm not sure if rtai_fifos.ko support sysfs or not.

/sys/module/rtai_fifos/ gets created when I load the module but there is
not much in it.

The output of 'udevinfo -a -p /sys/module/rtai_fifos/' is just:

  looking at class device '/sys/module/rtai_fifos':
    SUBSYSTEM=="unknown"
    SYSFS{refcnt}=="0"

When this module gets loaded, it would be ideal if the device
nodes /dev/rtf[0-9] could be created.

crw-rw-rw-  1 root root 150, 0 2006-03-03 14:05 /dev/rtf0
crw-rw-rw-  1 root root 150, 1 2006-03-03 14:05 /dev/rtf1
...
crw-rw-rw-  1 root root 150, 9 2006-03-03 14:05 /dev/rtf9

If I create the device nodes manually with mknod they get erased when
the box is rebooted.

Does anobody know if it is possible to make these device nodes
persistent with udev somehow?
(Continue reading)

Permalink | Reply | 1 comment |
headers
Marco d'Itri | 3 Mar 2006 14:24
Picon
Favicon

Re: Udev + /dev/rtf

On Mar 03, Albert Veli <Albert.Veli <at> afconsult.com> wrote:

> But I'm not sure if rtai_fifos.ko support sysfs or not.
If no device at all is being created, then obviously not.
Ask the RTAI maintainers to fix the driver.

> /sys/module/rtai_fifos/ gets created when I load the module but there is
> not much in it.
This is not the right path, the RTAI files will have to appear in
/sys/class/.

--

-- 
ciao,
Marco
Permalink | Reply | 0 comments |
headers
juuso.alasuutari | 3 Mar 2006 21:35

How to check if driver is in-built or module?

Hello. This is my first post on this list, and I hope I'm not asking something
that's already been dealt with. (I searched the docs and this list before
posting.)

How can I tell udev to modprobe <module> only if <module> exists and hasn't been
compiled in the kernel? In my experience modules are visible to udev only when
and after they are loaded, which makes finding a solution to my problem a bit
of a paradox.

I need this feature for those modules that aren't autoloaded, such as rtc. The
idea would not be to modprobe all modules that exist, but to add conditional
that would run modprobe only if necessary.

The rule I use for autoloading is:
SYSFS{modalias}=="?*", ACTION=="add", RUN+="/sbin/modprobe $env{MODALIAS}

Thank you. Sincerelly,
Juuso Alasuutari

----------------------------------------------------------------
This mail sent through L-secure: http://www.l-secure.net/

-------------------------------------------------------
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?cmd=lnk&kid=110944&bid=241720&dat=121642
Permalink | Reply | 11 comments |
headers
Marco d'Itri | 3 Mar 2006 22:01
Picon
Favicon

Re: How to check if driver is in-built or module?

On Mar 03, juuso.alasuutari <at> tamperelainen.org wrote:

> How can I tell udev to modprobe <module> only if <module> exists and hasn't been
> compiled in the kernel? In my experience modules are visible to udev only when

# check if the device has already been claimed by a driver
ENV{PHYSDEVDRIVER}=="?*", GOTO="hotplug_driver_loaded"

ENV{MODALIAS}=="?*",    RUN+="/sbin/modprobe $env{MODALIAS}"

LABEL="hotplug_driver_loaded"

Look at the Debian rules files for details.

> I need this feature for those modules that aren't autoloaded, such as rtc. The
> idea would not be to modprobe all modules that exist, but to add conditional
> that would run modprobe only if necessary.
I doubt that this buys you much anyway.

--

-- 
ciao,
Marco

-------------------------------------------------------
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?cmd=lnk&kid=110944&bid=241720&dat=121642
Permalink | Reply | 1 comment |
headers
Scott James Remnant | 4 Mar 2006 01:12
Favicon

Re: How to check if driver is in-built or module?

On Fri, 2006-03-03 at 22:01 +0100, Marco d'Itri wrote:

> On Mar 03, juuso.alasuutari <at> tamperelainen.org wrote:
> 
> > How can I tell udev to modprobe <module> only if <module> exists and hasn't been
> > compiled in the kernel? In my experience modules are visible to udev only when
> 
> # check if the device has already been claimed by a driver
> ENV{PHYSDEVDRIVER}=="?*", GOTO="hotplug_driver_loaded"
> 
> ENV{MODALIAS}=="?*",    RUN+="/sbin/modprobe $env{MODALIAS}"
> 
> LABEL="hotplug_driver_loaded"
> 
This breaks drivers like joydev which augment an existing loaded driver.
PHYSDEVDRIVER contains usbhid, so you never load joydev (which is
expanded by the MODALIAS).

Scott
--

-- 
Scott James Remnant
scott <at> ubuntu.com
Permalink | Reply | 0 comments |
headers
Greg KH | 4 Mar 2006 01:51
Gravatar

Re: How to check if driver is in-built or module?

On Fri, Mar 03, 2006 at 10:35:50PM +0200, juuso.alasuutari <at> tamperelainen.org wrote:
> Hello. This is my first post on this list, and I hope I'm not asking something
> that's already been dealt with. (I searched the docs and this list before
> posting.)
> 
> How can I tell udev to modprobe <module> only if <module> exists and hasn't been
> compiled in the kernel? In my experience modules are visible to udev only when
> and after they are loaded, which makes finding a solution to my problem a bit
> of a paradox.

Look in /sys/module/  That will have the module name if the module is
loaded _or_ if the module is built into the kernel.

If it's not there, then it should be safe to load it.

Or you can always just try to load the thing, as if it's already in the
kernel built in, it will not be present in the tree as a module.

Hope this helps,

greg k-h

-------------------------------------------------------
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?cmd=lnk&kid=110944&bid=241720&dat=121642
Permalink | Reply | 8 comments |

Gmane