public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Adam Voigt <adam@cryptocomm.com>
To: Tom Prado <tprado@charter.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Linksys Wireless USB
Date: 09 Dec 2002 11:49:26 -0500	[thread overview]
Message-ID: <1039452566.14286.24.camel@beowulf.cryptocomm.com> (raw)
In-Reply-To: <Pine.LNX.4.50L0.0212091124570.20492-100000@scuzzlebutt.theswamp.priv>


[-- Attachment #1.1: Type: text/plain, Size: 2149 bytes --]

dmesg | grep "usb" 

Produces:

usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
init_module: prism2_usb.o: 0.1.16-pre7 Loaded
init_module: dev_info is: prism2_usb
usb.c: registered new driver prism2_usb

And no, there is nothing in /proc/bus/usb.

Modprobing usb-uhci, uhci, or usb-ohci all throw error's and are not
inserted.
However, usb-core is loaded automatically when I modprobe the prism2
driver.

On Mon, 2002-12-09 at 11:33, Tom Prado wrote:

    You have absolutely nothing in /proc/bus/usb?  Or do you have usb
    loaded 
    but the device is not listed in /proc/bus/usb/devices?  If the
    former, it 
    sounds like you don't have the usb drivers even loaded or you don't
    have 
    usbdevfs loaded.  
    
    Make sure you have USB compiled in the kernel (or as a module).
    
    Do you see any USB messages when you do dmesg | grep usb?
    
    If you have it as a module, make sure you have usbcore loaded, and
    one of 
    these depending on your hardware: usb-uhci, uhci, or usb-ohci.
    
    Good luck.
    
    Tom
    
    
    On Mon, 9 Dec 2002, Adam Voigt wrote:
    
    > I'm trying to get my Linksys Wireless USB adapter (version 1) to
    work,
    > following the instructions on:
    > 
    > ftp://ftp.linksys.com/pub/network/linux_release.txt
    > 
    > Yields the following in the message log:
    > 
    > Dec  9 10:07:46 ws1 modprobe: modprobe: Can't locate module wlan0
    > 
    > And nothing is in /proc/bus/usb. I compiled the wlan-ng as
    prompted,
    > and everything seemed to go fine, no error's, every step worked,
    > it's just this thing won't configure. (ifconfig wlan0 says no such
    > interface)
    > 
    > I'd appreciate the help. Any ideas?
    > 
    > -- 
    > Adam Voigt (adam@cryptocomm.com)
    > The Cryptocomm Group
    > My GPG Key: http://64.238.252.49:8080/adam_at_cryptocomm.asc
    > 
    
    --
    gentoo-dev@gentoo.org mailing list
    

-- 
Adam Voigt (adam@cryptocomm.com)
The Cryptocomm Group
My GPG Key: http://64.238.252.49:8080/adam_at_cryptocomm.asc

[-- Attachment #1.2: Type: text/html, Size: 5635 bytes --]

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-12-09 16:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09 16:04 [gentoo-dev] Linksys Wireless USB Adam Voigt
2002-12-09 16:33 ` Tom Prado
2002-12-09 16:49   ` Adam Voigt [this message]
2002-12-09 17:52     ` Tom Prado
2002-12-09 17:59       ` Adam Voigt
2002-12-09 18:28         ` Per-Erik Westerberg
2002-12-09 18:34           ` Adam Voigt
2002-12-09 19:15         ` Tom Prado
2002-12-10 14:18           ` Adam Voigt
2002-12-11  1:13             ` Luke Graham
2002-12-11  8:43               ` Mark Gordon

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=1039452566.14286.24.camel@beowulf.cryptocomm.com \
    --to=adam@cryptocomm.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=tprado@charter.net \
    /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