linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: HELP: udev config.
Date: Wed, 03 Mar 2004 18:39:10 +0000	[thread overview]
Message-ID: <20040303183908.GC27709@kroah.com> (raw)
In-Reply-To: <200403030757.i237vBjY018430@orion.dwf.com>

On Wed, Mar 03, 2004 at 12:57:11AM -0700, reg@dwf.com wrote:
> Mar  3 00:45:11 orion modprobe: FATAL: Module ide_probe_mod not found. 
> Mar  3 00:45:11 orion modprobe: FATAL: Module ide_probe not found. 

These lines have nothing to do with udev

> ---
> 
> I have 4 lines in udev.rules, none of them work:
> 
> ---
> 
> BUS="usb", SYSFS{model}="USB DISK        ", NAME="usb_key1"
> 
> BUS="usb", model="USB DISK        ", NAME="usb_key2"
> 
> BUS="scsi", SYSFS{model}="USB DISK        ", NAME="usb_key3"
> 
> BUS="scsi", model="USB DISK        ", NAME="usb_key4"
> 
> ---
> 
> and yes, the model is returned with 8 trailing blanks.
> there are now new entries of ANY sort in /udev, not usb_key? nor sda?

What does:	
	udevinfo -p /sys/block/sda -a
show?

Why do you have those "model=" lines in your rules file?  They will not
do anything.

thanks,

greg k-h


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2004-03-03 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03  7:57 HELP: udev config reg
2004-03-03 18:39 ` Greg KH [this message]
2004-03-03 19:39 ` reg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040303183908.GC27709@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).