All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 015 release
Date: Fri, 30 Jan 2004 17:23:11 +0000	[thread overview]
Message-ID: <20040130172310.GB5265@kroah.com> (raw)
In-Reply-To: <401A8A35.1020105@gmx.de>

On Fri, Jan 30, 2004 at 05:45:41PM +0100, Prakash K. Cheemplavam wrote:
> Hi Greg,
> 
> perhaps you remember me being a gentoo user wanting to switch to udev. 
> Well I did so, but am having some problems:
> 
> 1.) Minor one: Nodes for Nvidia (I am using binary display modules 
> 1.0.5328) ar not created. I have to do it by hand each start-up (written 
> into loacal.start.):
> mknod /dev/nvidia0 c 195 0
> mknod /dev/nvidiactl c 195 255

Heh, and you expect me to be able to modify a binary driver to work with
udev how?  :)

You're on your own here...

> 2.) More probelmatic: I am having some serious troubles with my Epson 
> Perfection USB scanner:
> a) I am to dumb to write a rule for it to map it to /dev/usb/scanner0
> 
> I don't exactly know which SYSFS_ field to use as the don't match the 
> lsusb descriptor. I tried various ones, but the scanner always gets 
> mapped to /dev/scanner0. I managed to get my HP printer to be mapped to 
> usb/lp0 by using its serial. This is my (latest non working )line for 
> the scanner:

What does:
	usbinfo -a -p /sys/class/usb/scanner0
say?

That should help you generate a proper rule.

> Now the serious issue: When rebooting or disconnecting the scanner I get 
> a kernel oops:

That's because you shouldn't be using the scanner driver at all :)
Please just use the latest xscane, it can talk to the scanner through
usbfs/libusb with no kernel module needed.  This is a well known bug if
you search the lkml archives...

Hope this helps.

greg k-h


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 015 release
Date: Fri, 30 Jan 2004 09:23:11 -0800	[thread overview]
Message-ID: <20040130172310.GB5265@kroah.com> (raw)
In-Reply-To: <401A8A35.1020105@gmx.de>

On Fri, Jan 30, 2004 at 05:45:41PM +0100, Prakash K. Cheemplavam wrote:
> Hi Greg,
> 
> perhaps you remember me being a gentoo user wanting to switch to udev. 
> Well I did so, but am having some problems:
> 
> 1.) Minor one: Nodes for Nvidia (I am using binary display modules 
> 1.0.5328) ar not created. I have to do it by hand each start-up (written 
> into loacal.start.):
> mknod /dev/nvidia0 c 195 0
> mknod /dev/nvidiactl c 195 255

Heh, and you expect me to be able to modify a binary driver to work with
udev how?  :)

You're on your own here...

> 2.) More probelmatic: I am having some serious troubles with my Epson 
> Perfection USB scanner:
> a) I am to dumb to write a rule for it to map it to /dev/usb/scanner0
> 
> I don't exactly know which SYSFS_ field to use as the don't match the 
> lsusb descriptor. I tried various ones, but the scanner always gets 
> mapped to /dev/scanner0. I managed to get my HP printer to be mapped to 
> usb/lp0 by using its serial. This is my (latest non working )line for 
> the scanner:

What does:
	usbinfo -a -p /sys/class/usb/scanner0
say?

That should help you generate a proper rule.

> Now the serious issue: When rebooting or disconnecting the scanner I get 
> a kernel oops:

That's because you shouldn't be using the scanner driver at all :)
Please just use the latest xscane, it can talk to the scanner through
usbfs/libusb with no kernel module needed.  This is a well known bug if
you search the lkml archives...

Hope this helps.

greg k-h

  reply	other threads:[~2004-01-30 17:23 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 21:50 [ANNOUNCE] udev 015 release Greg KH
2004-01-26 21:50 ` Greg KH
2004-01-26 22:15 ` Tomasz Torcz
2004-01-26 23:56 ` Greg KH
2004-01-27  5:52 ` Chris Friesen
2004-01-27  5:52   ` Chris Friesen
2004-01-27 22:22   ` Greg KH
2004-01-27 22:22     ` Greg KH
2004-01-29  4:52 ` Martin Schlemmer
2004-01-29 21:54   ` Greg KH
2004-01-29 21:54     ` Greg KH
2004-01-29 16:52 ` Martin Schlemmer
2004-01-29 21:55   ` Greg KH
2004-01-29 21:55     ` Greg KH
2004-01-31  3:17     ` Kay Sievers
2004-01-31  3:17       ` Kay Sievers
2004-01-31 17:54       ` Martin Schlemmer
2004-01-31 18:15         ` Kay Sievers
2004-01-31 18:15           ` Kay Sievers
2004-01-31 18:27           ` Martin Schlemmer
2004-01-31 18:39             ` Kay Sievers
2004-01-31 18:39               ` Kay Sievers
2004-01-31 18:47               ` Martin Schlemmer
2004-01-29 18:30 ` Martin Schlemmer
2004-01-30  4:41   ` Martin Schlemmer
2004-02-02 23:32   ` Greg KH
2004-02-02 23:32     ` Greg KH
2004-02-03  4:12     ` Martin Schlemmer
2004-01-30 16:45 ` Prakash K. Cheemplavam
2004-01-30 16:45   ` Prakash K. Cheemplavam
2004-01-30 17:23   ` Greg KH [this message]
2004-01-30 17:23     ` Greg KH
2004-01-30 17:44     ` Prakash K. Cheemplavam
2004-01-30 17:44       ` Prakash K. Cheemplavam
2004-01-30 17:49       ` Greg KH
2004-01-30 17:49         ` Greg KH
2004-01-30 18:17         ` Prakash K. Cheemplavam
2004-01-30 18:17           ` Prakash K. Cheemplavam
2004-02-01 15:24     ` Martin Schlemmer
2004-02-02  8:46       ` Prakash K. Cheemplavam
2004-02-02  8:46         ` Prakash K. Cheemplavam
2004-01-30 17:33   ` Martin Schlemmer
2004-01-30 18:03   ` Andre Noll
2004-01-30 23:06     ` Tom Rini
2004-02-02 21:43       ` Greg KH
2004-02-05  0:31         ` [2.6 patch] remove USB_SCANNER Adrian Bunk
2004-02-05  1:14           ` Greg KH
2004-02-05 17:20             ` Azog
2004-02-05 17:30               ` Greg KH
2004-02-05 17:50                 ` Stian Jordet
2004-02-05 17:57                   ` Greg KH
2004-02-05 20:24                 ` Leopold Gouverneur
2004-02-05 21:15                   ` Stian Jordet
2004-02-05 21:36                     ` Leopold Gouverneur
2004-02-06  1:15               ` Gene Heskett
2004-02-06 20:59                 ` Bill Davidsen
2004-02-06 21:04                   ` Greg KH
2004-02-01 22:52 ` hal daemon and ide-floppy J.A. Magallon
2004-02-01 22:52   ` J.A. Magallon
2004-02-02  3:16   ` Greg KH
2004-02-02  3:16     ` Greg KH
2004-02-02  7:35   ` reflex
2004-02-02 22:32 ` udev depends on /usr J.A. Magallon
2004-02-02 22:32   ` J.A. Magallon
2004-02-02 22:44   ` Greg KH
2004-02-02 22:44     ` Greg KH
2004-02-02 23:01     ` J.A. Magallon
2004-02-02 23:01       ` J.A. Magallon
2004-02-03  4:10     ` Martin Schlemmer
2004-02-02 23:08 ` [ANNOUNCE] udev 015 release Prakash K. Cheemplavam
2004-02-02 23:08   ` Prakash K. Cheemplavam
2004-02-02 23:11   ` Greg KH
2004-02-02 23:11     ` Greg KH

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=20040130172310.GB5265@kroah.com \
    --to=greg@kroah.com \
    --cc=PrakashKC@gmx.de \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.