Help with Dynex Wireless G/Model DX-BUSB in Ubuntu 9.04...

The manufacturer and model is moot in linux, its the chip the manufacturer has used which we need to know

Please provide:

uname -a
sudo lshw -C network
lsusb
sudo iwlist scan
ifconfig

Thanks

anti00@anti00:~$ uname -a
Linux anti00 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux
anti00@anti00:~$ sudo lshw -C network
[sudo] password for anti00:
  *-network
       description: Ethernet interface
       product: SiS900 PCI Fast Ethernet
       vendor: Silicon Integrated Systems [SiS]
       physical id: 3
       bus info: pci@0000:00:03.0
       logical name: eth0
       version: 90
       serial: 00:0a:e6:c3:5b:59
       size: 10MB/s
       capacity: 100MB/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=sis900 driverversion=v1.08.10 Apr. 2 2006 duplex=half latency=64 link=no maxlatency=11 mingnt=52 module=sis900 multicast=yes port=MII speed=10MB/s
  *-network DISABLED
       description: Ethernet interface
       physical id: 1
       logical name: pan0
       serial: fa:a0:0e:2a:8a:96
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes
anti00@anti00:~$ lsusb
Bus 001 Device 003: ID 4317:0720
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
anti00@anti00:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

pan0 Interface doesn't support scanning.

anti00@anti00:~$ iconfig
bash: iconfig: command not found

But, I'm trying to get my usb adapter to work... not my internal ethernet card.

anti00@anti00:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0a:e6:c3:5b:59
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:10 Base address:0xd400

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:480 (480.0 B) TX bytes:480 (480.0 B)

(Sorry,,. forgot to include this... like I said: NEW to linux).

lsusb should show the device but your output of:

anti00@anti00:~$ lsusb
Bus 001 Device 003: ID 4317:0720
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Shows it is not even detected. You may have to use some boot options on the kernel at boot to get it detected. Does the device get detected in other systems> Does it have a kill-switch to turn it off and on?

Make sure all your USB ports are enabled in BIOS and also try:

removing the device, wait 10 seconds, plug it in, wait 10 seconds, then run:

dmesg | tail

and paste the output here

Bootoptions you may want to try can be found here:

https://help.ubuntu.com/community/BootOptions

Disabling ACPI, APIC, DMA etc may help the situation.

anti00@anti00:~$ dmesg | tail
[64295.649750] sd 4:0:0:0: [sdc] Attached SCSI removable disk
[64295.649926] sd 4:0:0:0: Attached scsi generic sg3 type 0
[64887.230119] usb 1-4: USB disconnect, address 8
[66665.244042] usb 1-3: new high speed USB device using ehci_hcd and address 9
[66665.426613] usb 1-3: configuration #1 chosen from 1 choice
[66704.202039] eth0: Media Link Off
[66704.202232] ADDRCONF(NETDEV_UP): eth0: link is not ready
[66773.415985] usb 1-3: USB disconnect, address 9
[66779.336043] usb 1-4: new high speed USB device using ehci_hcd and address 10
[66779.471668] usb 1-4: configuration #1 chosen from 1 choice

And I know that usb port is active... it's the same port I'm using for the flashdrive to transfer this information. Here's the lsusb now.

anti00@anti00:~$ lsusb
Bus 001 Device 011: ID 0930:653d Toshiba Corp. Kingston DataTraveler 2.0 USB Stick (1GB)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

The wireless adapter worked fine in win2k... there's no kill-switch that I'm aware of. And, I'm sorry... but I don't know how to disable all that other stuff.

The guide I posted shows you how to disable stuff, from the dmesg output you can see the kernel initiating and uninitiating the device

and you have a 1Gb USB stick attached right now.

My only suggestion is:

sudo apt-get install madwifi-tools

see if that makes it come back up after a reboot, failing that READ the bootoptions guide and disable certain kernel functionality. The Ubuntu team dont expect anyone to KNOW how to do that sort of thing. Thats why they've made guides to follow.

I'll check that out... I have to download the package onto the usb stick. And I know the 1gb stick was in there when I ran the lsusb... I was just trying to point out that the port was functional... so it had to be a driver issue with the wireless adapter.

And, sorry, I thought the bootoptions link was for the usb port functionality... not the kernel functionality. I thought you wrote that last bit simply as an afterthought. I wasn't being intentionally thick. :P

anti00@anti00:~$ dmesg | tail
[ 36.464297] type=1505 audit(1241352092.394:7): operation="profile_load" name="/usr/lib/cups/backend/cups-pdf" name2="default" pid=1869
[ 36.465076] type=1505 audit(1241352092.394:8): operation="profile_load" name="/usr/sbin/cupsd" name2="default" pid=1869
[ 36.539990] type=1505 audit(1241352092.466:9): operation="profile_load" name="/usr/sbin/tcpdump" name2="default" pid=1873
[ 40.403702] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 40.403711] Bluetooth: BNEP filters: protocol multicast
[ 40.457243] Bridge firewalling registered
[ 46.072145] eth0: Media Link Off
[ 46.072354] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 111.796043] usb 1-4: new high speed USB device using ehci_hcd and address 2
[ 111.982312] usb 1-4: configuration #1 chosen from 1 choice
anti00@anti00:~$

Seems like something changed... but the green light still shows no activity. I'll check out the BootOptions.

I messed with the kernel boot options... still no go. Maybe the Dynex line is simply unsupportable in Ubuntu. I'll try a couple other packages tomorrow?

Hi,

I don't think your Dynex Wireless G/Model DX-BUSB wireless card is supported by the Linux kernel or any third party drivers.

I suggest buying one of these supported adapters instead with a rating of 5.0:

http://ubuntuhcl.org/browse/search?offset=0&category=25&manufacturer=&os=1&order-by=rating-desc&keywords=

Anything on the list with a rating lower than 5.0 is not good enough.

Regards,

Mark

It looks like you're right... I've looked all over the freaking place and can't find a single positive ending regarding that particular USB adapter. That's really unfortunate... perhaps Dynex should look into a little more support for Linux!!! Boo!

NOTE TO FUTURE UBUNTU USERS: DON'T BUY A DYNEX WIRELESS G "DX-BUSB" NETWORK ADAPTER!!!

Just research what will work well BEFORE you part with any cash. Linksys are usually good but if you get the make and model and do a very thorough research you can see what chip is usually in it (It may not be the same in every country so check thoroughly) and then you can see which will give you most support, or an install method that you like.