svlug-balug-debuggery_usb_device_problems_modprobe_vs_insmod-etc

This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.



Subject: [svlug] modprobe does nothing, but insmod works fine. Any idea?
Date: Sat, 25 Oct 2003 00:24:55 -0700
To: SVLUG <svlug@lists.svlug.org>

Recently I bought a USB 802.11b stick, NetGear MA111, at Fry's.

It works fine on my main laptop with Gentoo 1.4, but it fails on my
second laptop which is running Gentoo 1.4 as well. 

Here is the description what's going on.

When I insert the MA111 into USB port, the kernel says:
usb.c:  USB device 2 (vend/prod 0x846/0x4110) is not claimed by any
active driver.

I made sure the hotplug is running because it detects HID keyboard or
USB mice. So I suspected the driver for MA111 isn't working. I tried

# modprobe prism2_usb
# 

then there happened nothing. The module prism2_usb wasn't
loaded. There was no error message on the console, syslog, or kernel
message(dmesg).  

However,

# insmod /lib/modules/2.4.20-gentoo-r8/usb/prism2_usb.o

worked. The module prism2_usb was loaded and MA111 was recognized by
the kernel. 

I made sure that prism2_usb.o is included to the search path by using
'modprobe -l -t usb'.


Is there any possible reason why modprobe does nothing but insmod
works? I'm screwed up...

===
Subject: Re: [svlug] modprobe does nothing, but insmod works fine. Any idea?
Cc: SVLUG <svlug@lists.svlug.org>
Date: Sat, 25 Oct 2003 13:35:46 -0700
To: Mark Nakamura <masayang@nri.com>

Try doing a depmod -av and confirm that you driver is in the output. 
Then a modprobe.

Look at the messages in /var/log/messages in the above does not work.

===

Subject: [Balug-talk] Help getting started with Linux
Date: Fri, 7 Nov 2003 11:39:18 -0800

I am a Unix-Linux newbie looking for a good 
support group to help me as I learn the ropes.
If this is the right place, here's my dilemma:

I installed Mandrake 9.1 on my Sony laptop in a dual boot
configuration. I cannot (after weeks of trying) figure out 
why Linux cannot see my USB mouse. I've run the
configuration tool and done a dmesg |grep USB but the output
is more than I can decipher at this point. I would love
it if someone would give me some hints on how to
resolve this (or if not how I can get a workable
Linux environment on my PC.)

Want to learn, but stuck,

===
Subject: [Balug-talk] Help getting started with Linux
Date: Sat, 8 Nov 2003 15:21:17 -0800

I erred in the direction of keeping my message (too) brief.
Here is what happens after failed attempts to configure a USB mouse
for Mandrake running on a SONY laptop (dual boot with XP):

[root@localhost cabellni]# mousedrake
/lib/modules/2.4.21-0.13mdk/kernel/drivers/usb/hcd/ehci-hcd.o.gz:
init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
modprobe: insmod
/lib/modules/2.4.21-0.13mdk/kernel/drivers/usb/hcd/ehci-hcd.o.gz failed
modprobe: Can't locate module

[root@localhost cabellni]# dmesg |grep USB
usb-uhci.c: USB UHCI at I/O 0x1020, IRQ 9
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
hub.c: new USB device 00:10.0-1, assigned address 2
usb.c: USB device 2 (vend/prod 0x46d/0xc501) is not claimed by any active
driver.
input0: USB HID v1.10 Mouse [Logitech USB Receiver] on usb1:2.0
hid-core.c: USB HID support drivers
usbmouse.c: v1.6:USB HID Boot Protocol mouse driver

I know that the USB port works 'cause the keyboard was OK when it was
connected.
The vend/prod id is the correct one for the USB mouse I attached.

Any analysis at all or suggestions how to debug are welcome.

===
From: Jason R McVetta <jmcvetta@sfobug.org>
To: balug-talk@balug.org
Subject: Re: [Balug-talk] Help getting started with Linux
Date: Sat, 8 Nov 2003 17:21:15 -0800

> modprobe: insmod
> /lib/modules/2.4.21-0.13mdk/kernel/drivers/usb/hcd/ehci-hcd.o.gz failed
> modprobe: Can't locate module

Maybe it's as simple as the needed module not being compiled.  Are you
usuing a totally generic setup, or have you compiled your own kernel &
modules?


> [root@localhost cabellni]# dmesg |grep USB

use "grep -i" instead, for case-insensitive mode

===

From: hvrietsc@myrealbox.com
Subject: [svlug] looking for help on belkin bluetooth f8t002 pcmcia card driver
Date: Sun, 23 Nov 2003 15:13:27 -0800
To: svlug@lists.svlug.org

I bought a belkin f8t002 bluetooth pcmcia card for my laptop
neither google nor the bluez project have any help with this card
when i insert it cardctl ident says:

Socket 0:
  product info: "OXSEMI", "OXCB950", "Rev A"
  manfid: 0x0279, 0x0001
  function: 2 (serial)
  PCI id: 0x1415, 0x950b

/var/log/messages says:

Nov 23 14:55:13 [cardmgr] unsupported card in socket 0
Nov 23 14:55:13 [kernel] cs: cb_alloc(bus 3): vendor 0x1415, device 0x950b
Nov 23 14:55:14 [cardmgr] no product info available
Nov 23 14:55:14 [cardmgr] PCI id: 0x1415, 0x950b

i did a manual insmod of serial_cs bluez serial
i installed all the bluez sw
I have a /etc/pcmica/bluetooth.conf file but it has no 
listing for my card

lspci WITHOUT the card inserted says:

00:00.0 Host bridge: Intel Corp. 82830 830 Chipset Host Bridge (rev 04)
00:02.0 VGA compatible controller: Intel Corp. 82830 CGC [Chipset Graphics Controller] (rev 04)
00:02.1 Display controller: Intel Corp. 82830 CGC [Chipset Graphics Controller]
00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #3) (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02)
00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02)
02:03.0 CardBus bridge: Ricoh Co Ltd RL5c475 (rev b8)
02:03.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C551 IEEE 1394 Controller
02:05.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
02:07.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01)


lspci WITH the card INSERTED says same thing but also gives
an error msg:

pcilib: Cannot open /proc/bus/pci/03/00.0
Unable to read 64 bytes of configuration space.

anyone with any clues for my bluez?
my laptop is a dell x200 running gentoo linux


===

From: George Georgalis <list-svlug-sender-19fa62@lists.galis.org>
Subject: Re: [svlug] printing on usb Brother HL-1440 with hl1250.ppd
Date: Sat, 13 Dec 2003 10:05:20 -0500
To: SVLUG <svlug@lists.svlug.org>

On Wed, Nov 12, 2003 at 11:28:57AM -0500, Walt Reed wrote:
>On Wed, Nov 12, 2003 at 11:06:38AM -0500, George Georgalis said:
>> Have not configured a usb printer before and having some trouble,
>> partly from not having an understanding of how the process works.
>> 
>> I've gotten some info from these pages:
>> http://www.linuxprinting.org/brother-faq.html#free_software_support
>> http://www.linuxprinting.org/cups-doc.html
>> http://www.linuxprinting.org/show_printer.cgi?recnum=Brother-HL-1440
>> 
>> and tried various debian packages to help me set it up and run lpd...
>> I think this printcap file will work...
>
>First, make sure the printer usb module is loaded (or compiled in).
>
>I personally use cups, which you configure through the web interface
>(localhost:631) and it works dandy. I did manually install the brother
>PPD file that I grabbed from the Windows driver set by copying it into
>the appropriate directory.
>
>I have a HL-1270N, so I normally use ethernet, but I have made the usb
>port work with cups too (and use USB for my epson color printer.)

thanks, this is kinda a slow process because it's my friends.
Indeed, didn't think about the 'usbprinter' module. so looks like
I'll be building a kernel for this laptop, At least I can do most
of that remotely.

===

Date: Fri, 4 Apr 2003 23:47:32 +0000 (UTC)
From: Robert Hajime Lanning <lanning@lanning.cc>
To: "svlug@lists.svlug.org" <svlug@lists.svlug.org>
Subject: Re: [svlug] start usb mouse after X has started?

On Fri, 4 Apr 2003, matt@vazor.com wrote:
> Hi,
>
> I have a usb mouse that works in my laptop if it's plugged in when X
> starts, otherwise I get:
>
> (EE) xf86OpenSerial: Cannot open device /dev/input/mice
>         No such file or directory.
> (EE) xf86OpenSerial: Cannot open device /dev/input/mice
>         No such file or directory.
> (WW) Mouse2: cannot open input device
>
> So when I plug in the mouse, I can cat /dev/input/mice and see that the mouse
> is sending events, but how do I get X to use the mouse without restarting it?

The problem is that you are dynamicaly loading the HID driver (Human Interface
Device).  This driver creates (in devfs) the /dev/input/mice.

You either need to load the driver manualy, so it won't be autocleaned.  Or
compile the USB interface driver and the HID driver staticaly in the kernel.

Even if you do not use devfs, you will have a problem.  Because, when X
connects to the "mice" device, it will get a "no such device" error, as
no loaded driver will have the major/minor combination claimed.

===

Date: Sun, 6 Apr 2003 06:12:55 -0600 (MDT)
From: "Karl F. Larsen" <k5di@zianet.com>
To: matt@vazor.com
Cc: svlug@lists.svlug.org
Subject: Re: [svlug] start usb mouse after X has started?


Hi Matt, your linux is working like it should. Your system has "hotplug" 
working so that hotplug looks at each USB port, reads what the device on 
the USB port is, and then orders the proper kernel modules to be loaded. 

Alas hotplug doesn't work after bootup well at all. So when you plug in 
your mouse after booting, it doesn't load the proper kernel modules and 
fails to work.

It's amazing that hotplug works at all!


===

From: <clee@spiralis.merseine.nu>
To: matt@vazor.com
Cc: svlug@lists.svlug.org
Subject: Re: [svlug] start usb mouse after X has started?

Hi Matt, 

What you want to happen is possible; on my computers, I have the
ability to plugin a USB mouse anytime--before or after X starts up
(I'm using XFree 4.1).  Unfortunately, I worked this out a while ago,
so the process is no longer fresh in my mind.  I think that the USB
kernel modules are being loaded automatically, but I'm not sure---I
don't have my laptop available to check and my desktop doesn't get the
mouse changed anymore.

One tidbit that I remember: configure both the default pointer
"Mouse0" and the potential USB mouse in your XFConfig-4 file like so
(here's the example I have a for serial mouse and a USB mouse on my
desktop). Make sure that the "AllowMouseOpenFail" option is set.
Here's an example:

Section "ServerLayout"
        Option "AllowMouseOpenFail"  "1"
	Identifier "XFree86 Configured"
	Screen      0  "Screen0" 0 0
# when using both serial and USB
	InputDevice    "Mouse0" "CorePointer"
        InputDevice    "Mouse1"  "SendCoreEvents"
# when using just USB
#        InputDevice    "Mouse1"  "CorePointer"
#	InputDevice    "Keyboard0" "CoreKeyboard"
        Option "AllowMouseOpenFail"  "1"
EndSection

"Mouse1" was the USB mouse.

===

To: balug-talk@balug.org
Subject: Re: [Balug-talk] USB mass media.
From: Rick Moen <rick@linuxmafia.com>
Date: Wed, 16 Jul 2003 10:14:46 -0700

Quoting Abu Zafur Ziauddin Ahmed (zahmed@ssl-idt.net):

> I have 64 MB Sony USB ( USB 2 compatible with USB 1) mass media flash ROM.
> I can access it through windows 2000 as a  another drive. But how can I
> access it from linux. What will be the device name in linux?

Abu Zafur Ziauddin --

First, you'll need the usb-uhci or usb-ohci USB-chipset driver
(depending on your chipset[1]), plus the usb-storage driver.  Then,
you'll need to enable the USB extended support for /proc :

# mount -t usbdevfs usb /proc/bus/usb

Having done that, you should now be able to mount the device as either
/dev/sda or /dev/sda1 (filesystem type vfat), depending on what type of
controller chip the USB drive uses.  (Note that it'll be some higher
SCSI device letter on a SCSI-based system.)

Having a look at /proc/bus/usb/devices and /proc/scsi/scsi should
clarify the exact device to use.

Linux Journal is supposed to print my article about USB flash ROM
devices in its September issue.

[1] If "lspci -v" returns USB information that includes "I/O ports at",
then you have a UHCI controller.  If the returned USB-controller text
includes "Memory at", then it's OHCI.

===

To: balug-talk@balug.org
From: Joseph Brenner <doom@kzsu.stanford.edu>
Subject: [Balug-talk] Confusion from moving a module into the kernel
Date: Sun, 20 Jul 2003 17:01:07 -0700


When I rebuild my kernel, I sometimes will take something 
I previously compiled as a module, and build it into the 
core.  Whenever I do that though, I get complaints that 
the module is missing.  So, something is not getting the 
word that that the module isn't a module any more... 
Can someone give me some hints as to what needs to be 
told about this? 

Here's an example, after moving the low-level scsi driver
sym53c8xx into the core of the kernel, doing a "make
install" complains:

  [...]
  Kernel: arch/i386/boot/bzImage is ready
  sh arch/i386/boot/install.sh 2.6.0-test1 arch/i386/boot/bzImage System.map ""
  No module sym53c8xx found for kernel 2.6.0-test1
  make[1]: *** [install] Error 1
  make: *** [install] Error 2

And here's a complaint reported in /var/log/messages, which
I believe is the reason my USB interface stopped working recently:

  Jul  4 19:36:27 crack kernel: usb-uhci.c: USB UHCI at I/O 0xb400, IRQ 7
  Jul  4 19:36:27 crack kernel: usb-uhci.c: Detected 2 ports
  Jul  4 19:36:27 crack kernel: usb.c: new USB bus registered, assigned bus number 1
  Jul  4 19:36:27 crack kernel: hub.c: USB hub found
  Jul  4 19:36:27 crack kernel: hub.c: 2 ports detected
  Jul  4 19:36:27 crack kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
  Jul  4 19:36:30 crack /etc/hotplug/usb.agent: Setup usbcore for USB product 0/0/0
  Jul  4 19:36:30 crack modprobe: modprobe: Can't locate module usbcore

Hm.  Maybe I need to run depmod after a "make modules_install"?  
I guess I'll look into this next... 

===

Subject: Re: [Balug-talk] Confusion from moving a module into the kernel 
From: Joseph Brenner <doom@kzsu.stanford.edu>
Date: Tue, 22 Jul 2003 12:41:58 -0700

Joseph Brenner <doom@kzsu.stanford.edu> wrote:

> When I rebuild my kernel, I sometimes will take something 
> I previously compiled as a module, and build it into the 
> core.  Whenever I do that though, I get complaints that 
> the module is missing.  So, something is not getting the 
> word that that the module isn't a module any more... 
> Can someone give me some hints as to what needs to be 
> told about this? 
> 
> Here's an example, after moving the low-level scsi driver
> sym53c8xx into the core of the kernel, doing a "make
> install" complains:

>   No module sym53c8xx found for kernel 2.6.0-test1

And the answer is... /etc/modules.conf!

I still had this line sitting around from trying to use
this driver as a module: 

   alias scsi_hostadapter sym53c8xx

Interesting that /etc/modules.conf (and all the other /etc files,
for that matter) has no versioning associated with it.  You can
set-up grub (or lilo) to boot different kernel versions easily
enough, but you'd need some serious magic to get a different
version of an /etc/modules.conf file swapped in.

Next up, I get to figure out why one of my ethernet cards stops 
working with the 2.4.21 kernel build... looks like I did a 
CONFIG_TULIP=y so it's compiled into the core, which means this 
line doesn't work any more in modules.conf:

   alias eth1 tulip

How else would you tell the system what driver to use with eth1? 

Eh.  I'll probably just go back to compiling it as a module.

===

the rest of The Pile (a partial mailing list archive)

doom@kzsu.stanford.edu