[NBLUG/talk] HP 5200c scanner, Fedora Core 2, 2.6.5 kernel

Dave Sisley dsisley at arczip.com
Mon Jun 14 15:12:18 PDT 2004


On Mon, Jun 14, 2004 at 09:05:06AM -0700, Mark Street wrote:
> Let's think this through from a low level to a higher level.  We know that 
> jumping from a 2.4 to a 2.6 kernel can introduce unforeseen effects.
>

Yeah, I know that *now*, and should have known beforehand.  I find I'm
doing more cleanup this time than I've had to previously (RH7.3 -> RH8
-> RH9 -> FC1 -> FC2).  Perhaps I was upgrading after letting each new
version mature a bit before I grabbed it.  FC2 was *very* fresh when I
installed it.  Not beta or testing, but fresh nonetheless.

Okay, Mark.  Thanks for the help, here.  Here's your info:
 
> Let's look at /etc/modules.conf

Hmmm... That's a bit long - what am I looking for here?  Hey.  Why are
these lines repeated 37 times?

alias /dev/ttySHSF[0-9]* /dev/ttySHSF
alias /dev/cuaHSF[0-9]* /dev/ttySHSF
alias /dev/hsfdiag* /dev/hsfdiag

After removing those lines, the rest of modules.conf looks like this
(I haven't edited the actual file, but I should remove 36 of those,
shouldn't I?):

alias usb-controller ehci-hcd
alias usb-controller1 usb-uhci
alias char-major-240 /dev/ttySHSF
alias /dev/modem /dev/ttySHSF
alias char-major-241 /dev/ttySHSF
options hsfserial serialmajor=240 calloutmajor=241 
alias char-major-243 /dev/hsfdiag
options hsfosspec dcpmajor=242 diagmajor=243 
probeall /dev/ttySHSF hsfpcibasic2 hsfmc97ich hsfmc97via hsfmc97ali
probeall hsfserial hsfpcibasic2 hsfmc97ich hsfmc97via hsfmc97ali
alias sound-slot-0 i810_audio
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :
alias eth0 bcm4400
alias eth1 adm8211
# Note: for use under 2.6, changes must also be made to modprobe.conf!

> Let's look at /etc/modprobe.conf

# Note: for use under 2.4, changes must also be made to modules.conf!
alias usb-controller ehci-hcd
alias usb-controller1 uhci-hcd
alias /dev/ttySHSF0 /dev/ttySHSF1
alias char-major-240-* /dev/ttySHSF
alias /dev/modem /dev/ttySHSF
alias /dev/cuaHSF0 /dev/cuaHSF1
alias char-major-241-* /dev/ttySHSF
options hsfserial serialmajor=240 calloutmajor=241 
alias /dev/hsfdiag0 /dev/hsfdiag1
alias char-major-243-* /dev/hsfdiag
options hsfosspec dcpmajor=242 diagmajor=243 
alias snd-card-0 snd-intel8x0
alias eth0 bcm4400
alias eth1 bcm4400
install /dev/ttySHSF /sbin/modprobe hsfpcibasic2; /sbin/modprobe hsfmc97ich; /sbin/modprobe hsfmc97via; /sbin/modprobe hsfmc97ali; /bin/true
install hsfserial /sbin/modprobe hsfpcibasic2; /sbin/modprobe hsfmc97ich; /sbin/modprobe hsfmc97via; /sbin/modprobe hsfmc97ali; /bin/true
install sound-slot-0 /sbin/modprobe --first-time --ignore-install sound-slot-0 && { /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :; }
remove sound-slot-0 { /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :; } ; /sbin/modprobe -r --first-time --ignore-remove sound-slot-0
alias char-major-240-* /dev/ttySHSF
alias char-major-241-* /dev/ttySHSF
alias char-major-243-* /dev/hsfdiag
alias char-major-240-* /dev/ttySHSF
alias char-major-241-* /dev/ttySHSF
alias char-major-243-* /dev/hsfdiag
alias char-major-240-* /dev/ttySHSF
alias char-major-241-* /dev/ttySHSF
alias char-major-243-* /dev/hsfdiag

> 
> Let's see output of the /sbin/lsusb command when the scanner is plugged in.

Bus 004 Device 001: ID 0000:0000  
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 002: ID 03f0:0401 Hewlett-Packard ScanJet 5200c
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 001: ID 0000:0000  

> 
> Let's see a listing of the drivers available for the usb scanners from
> /lib/modules/***2.6.5***/kernel/drivers/usb/image
> 
hpusbscsi.ko
mdc800.ko
microtek.ko

> and maybe the file names from the 'core' and 'host' directories
> /lib/modules/***2.6.5***/kernel/drivers/usb/core

No such file or directory.

> /lib/modules/***2.6.5***/kernel/drivers/usb/host

ehci-hcd.ko
ohci-hcd.ko
uhci-hcd.ko

> 
> Why?  We need to see what modules your system is loading, and in what order 
> they are loaded in.  We also need to know if those modules exist by their 
> given name or some other name.
> 

Sure.  I wouldn't even have known where to start looking (so thanks,
Mark!).

I really appreciate your sifting through this. My googling has turned
up lots of stuff that gets me close to a solution, but never quite
close enough.

-dave.

-- 
Dave Sisley
dsisley at arczip.com
roth-sisley.net




More information about the talk mailing list