VectorLinux
October 02, 2014, 06:08:25 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1] 2
  Print  
Author Topic: lsusb command won't work in VL6.0-Light-Final -SOLVED-  (Read 3316 times)
hardrockgeo
Member
*
Posts: 18


« on: November 19, 2009, 03:33:27 pm »

Help:

Trying to configure usb wireless card.

Got this output w/ VL5.9-Light lsusb command:

lsusb:
Bus 2 Device 2: ID 13b1:000e Linksys
Bus 2 Device 1: ID 0000:0000
Bus 1 Device 1: ID 0000:0000

When I try lsusd command w/ VL6.0-Light, xterm window freezes. 

Does anyone have any suggestions?

Thanks
« Last Edit: November 23, 2009, 08:24:38 pm by hardrockgeo » Logged
nightflier
Administrator
Vectorian
*****
Posts: 4024



« Reply #1 on: November 19, 2009, 06:02:04 pm »

Try booting into "tui" and see if it makes any difference.
Logged
hardrockgeo
Member
*
Posts: 18


« Reply #2 on: November 19, 2009, 07:36:12 pm »

I get pretty much the same in tui.  After I hit return in tui, I just get a blinking cursor.
Logged
nightflier
Administrator
Vectorian
*****
Posts: 4024



« Reply #3 on: November 20, 2009, 06:00:49 am »

Something is definitely not as it should be.
Does it do the same thing if the device is not plugged in?
Do other tools like "lspci" work?
Logged
hardrockgeo
Member
*
Posts: 18


« Reply #4 on: November 20, 2009, 01:30:46 pm »

lspci works.  I tried a few others & they also worked.  I checked the files before installing and also did a md5 sum check w/ no errors.

I have another issue (Linksys WUSB54GS Wireless Install Help) open under the Hardware & Drivers topic for VL5.9-Light.

The lspci command worked under VL5.9-Light, so I reinstalled VL5.9 light, tried the lsusb command again. It worked and returned: Bus 2 Device 2: ID 13b1:000e Linksys
                              Bus 2 Device 1: ID 0000:0000
                              Bus 1 Device 1: ID 0000:0000

Maybe the lsusb command on the VL6.0-Light copy is corrupt. I will download VL6.0-Light again, burn another copy and reinstall.  Hopefully VL6.0-Light will have the module for my Linksys wireless adaptor.

Logged
nightflier
Administrator
Vectorian
*****
Posts: 4024



« Reply #5 on: November 20, 2009, 02:18:39 pm »

If you have a high speed internet connection, you can also give VL6.0-Light-LIVE a try. You would not need to install to test it. Handy to keep around anyways.
Logged
hardrockgeo
Member
*
Posts: 18


« Reply #6 on: November 21, 2009, 08:35:39 am »

I downloaded another copy of VL6.0-Light-Final and tried the lsusb command again w/ the same result, the xterm terminal freezes.  then I downloaded  VL6.0-Light-Live-Final and it worked w/ this output:

vector:/~
root:# lsusb
Bus 002 Device 002: ID 0781:5150 SanDisk Corp. SDCZ2 Cruzer Mini Flash Drive (thin)
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 13b1:000e Linksys
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

The only option that I recall I didn't load diring installation was for the modem dialer. Could there be some conflict w/ my system?  I have a:
AMD K6-2 550 Mhz CPU
384 meg memory
Tyan S1598 Motherboard
Logged
newt
Vectorian
****
Posts: 1132



« Reply #7 on: November 21, 2009, 09:09:14 am »

I notice the bus/device of your Linksys device fluctuating between Bus2 Device2 and Bus1 Device2 depending on distro (59light and 60lightlive, respectively).  I also notice that your cruzer mini only shows in 6.0 light live.  Has this device been plugged in every time you've tried the 'lsusb' command in 6.0 Light Final? If so, perhaps try again with the device unplugged. In fact, try making sure your usb ports are as empty as possible before issuing the command. Then, one by one, plug in a device and check the command again. See if you can determine if a device is causing the stalling issue.
Logged
hardrockgeo
Member
*
Posts: 18


« Reply #8 on: November 21, 2009, 12:30:35 pm »

Newt:

I have bee switching and devices around.  cruzer mini shows up in both 59light and 60lightlive and 6.0 Light Final w/ no problem.  Linksys WUSB54GS shows up in 59light and 60lightlive, but not 6.0 Light Final.

I followed your suggestiion and found that the Linksys WUSB54G was causing the 6.0 Light Final xterm window to freeze.  I tried a Dell 1450 USB ataptor that works w/ the VL6.0 Light Final lsusb command to produce the output below. 

vector:/~
root:# lsusb
Bus 002 Device 002: ID 0781:5150 SanDisk Corp. SDCZ2 Cruzer Mini Flash Drive (thin)
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 413c:8104 Dell Computer Corp. Wireless 1450 Dual-band (802.11a/b/g) USB2.0 Adapter
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

The Dell installation disk contains drivers for RedHat Linux 9.0 running kernel version 2.4.20-8 and RedHat Enterprise Linux WS3 running kernel version 2.4.21-4.

I should probably mark this topic solved & start a new one for the Dell adaptor, but before I do that, I will ask one question.

Do you know if the RedHat drivers will work w/ VL6.0 Light Final?  The driver files are:
rpm -i Prism-modules-2.4.20-8.dkms1.0.7.i686.rpm for RedHat Linux 9.0 or
rpm -i Prism-modules-2.4.21-4.EL.dkms1.0.7.i686.rpm for RedHat Enterprise Linux.

The Linux installation instructions w/ the Dell CD are provided below:

Verify if you have DKMS 1.10 or newer installed by typing dkms -v.
If needed, download the latest version of DKMS from http://linux.dell.com/dkms  and install it.
From the root account execute the following command:
rpm -i Prism-modules-2.4.20-8.dkms1.0.7.i686.rpm if you are running RedHat Linux 9.0 or
rpm -i Prism-modules-2.4.21-4.EL.dkms1.0.7.i686.rpm if you are running RedHat Enterprise Linux.
Verify the status of the installation by executing the dkms status command. The output of the command should be Prism, 1.0.7, 2.4.20-8: installed

Thanks for your help!
Logged
newt
Vectorian
****
Posts: 1132



« Reply #9 on: November 21, 2009, 01:45:28 pm »

I would doubt that those drivers will work since they are for kernel 2.4.x and VL 6.0 runs 2.6.x.  Besides, prism drivers are pretty standard and are probably supported out-of-the-box with kernel 2.6.x.  You can check 'lsmod' to see if the modules were loaded by default - you'd be looking for at least one module with 'prism' in the name (probably prism54). If not then probably a simple 'modprobe prism54' will load necessary modules - there is usually no indication of success after running that command. You can check 'iwconfig' to see if a device with wireless extensions is found. If it is, then the next step would be to just configure the device for your network.
« Last Edit: November 21, 2009, 01:48:11 pm by newt » Logged
hardrockgeo
Member
*
Posts: 18


« Reply #10 on: November 21, 2009, 03:02:38 pm »

Earlier today, I followed the Intro to Wireless Networking guide w/ the p54usb driver for the Dell 1450 adaptor, I found at:
http://linuxwireless.org/en/users/Devices/USB.

I used:
'cat /etc/modprobe.conf'
and there was no entry for p54usb

So I entered:
'depmod -aq'
'modprobe p54usb'
to check the driver and got no errors.

Then I used:
'mcedit /etc/modprobe.conf'
to create a new alias w/
'alias wlan0 p54usb'

I did not reboot after performing the above operations.
I checked back and read your last comment, ran 'lsusb' and got theses two entries related to p54usb:

Module                 Size    Used by
p54usb                 13824  0
p54common          11648  1 p54usb


'iwconfig' returns:
lo        no wireless extensions.

eth0      no wireless extensions.

I tried 'mcedit /etc/ifplug.d/ifplugd.conf. as specified in the Intro to Wireless Networking guide and got the an error message stating "Cannot open file for reading /etc/ifplug.d/ifplugd.conf for reading" w/ a Dismiss command option.
Logged
newt
Vectorian
****
Posts: 1132



« Reply #11 on: November 21, 2009, 03:39:41 pm »

Do you also see 'mac80211' listed in lsmod? If not then add it as well (modprobe mac80211).

And then reload your p54usb module (rmmod p54usb; modprobe p54usb; depmod -aq).
« Last Edit: November 21, 2009, 03:44:28 pm by newt » Logged
hardrockgeo
Member
*
Posts: 18


« Reply #12 on: November 21, 2009, 04:31:36 pm »

Yes, mac80211 was in there as:
Module                   Size     Used by
mac80211              155548  2 p54usb,p54common

Inbetween responses I used 'mcedit /etc/ifplugd.conf. and the file opened, but it was blank, so I added INTERFACES='wlan0'.  Will thei affect anything?

I entered rmmod p54usb; modprobe p54usb; depmod -aq w/ no errors reported.  What do I do next?

Logged
hardrockgeo
Member
*
Posts: 18


« Reply #13 on: November 21, 2009, 04:38:07 pm »

'wiconfig' still returns
lo        no wireless extensions.

eth0      no wireless extensions.
Logged
newt
Vectorian
****
Posts: 1132



« Reply #14 on: November 21, 2009, 08:57:50 pm »

Please check lsmod for an instances of prism54 or ndiswrapper. They should not appear as loaded modules or they could conflict with the p54usb/common modules.

Also, I do no believe that VL 6 Light or Standard use ifplugd like the VL 5.x series did, so those steps may be irrelevant.

After making sure that the correct modules are loaded (p54usb, p54common, mac80211), and the incorrect ones are not (prism54, ndiswrapper), please reboot your system and ensure that they remain loaded after the reboot - they should.

Last, does your usb device give any kind of indication of connectivity (i.e. lights, leds, green, yellow, red, blinking, not blinking)?
Logged
Pages: [1] 2
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!