Pluscom Forum: Latest Ubuntu But No Network Device

Author

Message

alexmay
Newbie
Newbie

Joined: 06 Mar 2008
Online Status: Offline
Posts: 7

Topic: Latest Ubuntu But No Network Device
Posted: 06 Mar 2008 at 9:10am

As I have no other network device, I did a CD install from the latest iso from Ubuntu.
I then tried to install my Wifi Stick using the drivers downloaded from you. I got an endless string of warning messages, but make finished without actual error. Result? Nothing. No network device. Ipconfig shows lo and nothing else.
I tried installing firmware as well. Result? No difference.

Can anyone help?

Here is the result of dmesg.




[ 4417.545893] |__  /   _|  _ \  / \  / ___|

[ 4417.545903]   / / | | | | | |/ _ \ \___ \

[ 4417.545912]  / /| |_| | |_| / ___ \ ___) |

[ 4417.545921] /____\__, |____/_/   \_\____/

[ 4417.545930]      |___/

[ 4417.545939] ZD1211B - version 2.22.0.0-development

[ 4417.568722] vendor_id = 0ace

[ 4417.568758] product_id = 1215

[ 4417.568768] USB 1.1 Host

[ 4417.569259] Release Ver = 4810

[ 4417.569308] EEPORM Ver = 4810

[ 4417.606277] Finsih download Firmware. Ready to reboot 

[ 4417.630102] PA type: 0

[ 4417.641673] UW2453 RF

[ 4417.957467] OverWrite CR157 = 0xF0

[ 4418.033466] zd1205_config: EEP(HWFeature)=0x2000

[ 4418.037792] AllowedChannel = 000107ff

[ 4418.037814] Region:48

[ 4419.006545] usbcore: registered new interface driver zd1211b

[ 4508.873409] usb 1-1: USB disconnect, address 9

[ 4513.680527] usb 1-1: new full speed USB device using ohci_hcd and address 10

[ 4513.894186] usb 1-1: configuration #1 chosen from 1 choice

[ 4514.068512] usb 1-1: reset full speed USB device using ohci_hcd and address 10

[ 4514.781239] zd1211rw 1-1:1.0: RF UW2453_RF 0x9 is not supported

[ 4514.956401] usb 1-1: reset full speed USB device using ohci_hcd and address 10

[ 4515.165444] vendor_id = 0ace

[ 4515.165481] product_id = 1215

[ 4515.165490] USB 1.1 Host

[ 4515.165988] Release Ver = 4810

[ 4515.166039] EEPORM Ver = 4810

[ 4515.183173] Finsih download Firmware. Ready to reboot 

[ 4515.204338] PA type: 0

[ 4515.208339] UW2453 RF

[ 4515.500273] OverWrite CR157 = 0xF0

[ 4515.576221] zd1205_config: EEP(HWFeature)=0x2000

[ 4515.580257] AllowedChannel = 000107ff

[ 4515.580284] Region:48

IP Logged

PluscomTech
Admin Group

Joined: 07 Apr 2007
Location: China
Online Status: Offline
Posts: 1375

Posted: 10 Mar 2008 at 10:51am

Click here to download the latest driver for Linux then follow the steps given in Linux Installation guide to install the driver.

In case you need Phone Support, feel free to call us on 0871 789 0948 from Monday to Saturday between 10:00am to 7:00pm.

IP Logged

alexmay
Newbie
Newbie

Joined: 06 Mar 2008
Online Status: Offline
Posts: 7

Posted: 10 Mar 2008 at 12:49pm

I thought I had made it clear that I had done that.

The result you see above is the result of downloading the latest driver and following the installation guide.

IP Logged

RobS
Newbie
Newbie

Joined: 06 Dec 2007
Online Status: Offline
Posts: 4

Posted: 11 Mar 2008 at 1:05pm

There are possibly two problems.

(1) First is that you have two drivers for your stick, the pluscom one, and one built into the linux kernel called zd1211rw. You need to prevent the module zd1211rw (which doesn't support the pluscom stick unless you're using kernel 2.6.24) from loading. (Search for "module blacklist" on google)

(2) I think you might be plugging your device into a USB1 port. I have been completely unable to get this device running under USB1 and Linux without upgrading to Kernel 2.6.24 and using zd1211rw module.

Good luck

Rob

IP Logged

alexmay
Newbie
Newbie

Joined: 06 Mar 2008
Online Status: Offline
Posts: 7

Posted: 11 Mar 2008 at 1:26pm

Thanks for your reply.

I think I can solve the first issue that you raised. That makes sense and it seems to be well documented how to blacklist a module.

But I don't know what to do about the second issue. Do I really have to upgrade the Kernel? The 2.6.24 Kernel is only available in the alpha test version of my current distro (I have switched to OpenSuse because of the problems I had, but don't seem to have solved anything as far as the stick is concerned), and I really don't want to go there. I now have 2.6.23 running which seems to be the latest current stable release.

I have two USB ports right next to each other on my machine. Are you saying it makes a difference which one I use?

IP Logged

RobS
Newbie
Newbie

Joined: 06 Dec 2007
Online Status: Offline
Posts: 4

Posted: 12 Mar 2008 at 2:27pm

Originally posted by alexmay

Thanks for your reply.

I think I can solve the first issue that you raised. That makes sense and it seems to be well documented how to blacklist a module.

I have two USB ports right next to each other on my machine. Are you saying it makes a difference which one I use?

USB 1 refers to the type (or speed) of the USB port. USB 1 ports are slower than USB 2 ports. USB 2 devices should plug happily into USB 1 ports and work, but mine didn't (and niether did others)

It sounds like you have 2 USB 1 ports.

However, after blacklisting the module zd1211rw, you may find everything works. The log you showed in your original post looks more promising that mine ever did.

So blacklist away, give the pluscom driver a go, and more importantly, if it does work. Let everyone know back here.

Rob

IP Logged

alexmay
Newbie
Newbie

Joined: 06 Mar 2008
Online Status: Offline
Posts: 7

Posted: 25 Mar 2008 at 8:06pm

I'm sorry for the delay in replying, but I decided to fix everything that you suggested. I bought myself a new USB card with 2.0 support. I also blacklisted the zd1211rw driver and reinstalled from the link you gave above. I got a load of warning messages, but the installation completed successfully. I still get a message in dmesg saying that I should install the firmware, but.... it works.... well almost..... no well it does.... but...

my only problem now is that I can get it to work manually, but I can't get it to work from boot.

Here is the log on connecting the dongle (I get more or less the exact same thing when I boot).


aptiva:/home/alex # tail -f /var/log/messages
Mar 25 14:47:58 aptiva kernel: usb 4-4: new high speed USB device using ehci_hcd
 and address 2
Mar 25 14:47:58 aptiva kernel: klogd 1.4.1, ---------- state change ----------
Mar 25 14:47:58 aptiva kernel: usb 4-4: new device found, idVendor=0ace, idProdu
ct=1215
Mar 25 14:47:58 aptiva kernel: usb 4-4: new device strings: Mfr=16, Product=32,
SerialNumber=0
Mar 25 14:47:58 aptiva kernel: usb 4-4: Product: USB2.0 WLAN
Mar 25 14:47:58 aptiva kernel: usb 4-4: Manufacturer: ZyDAS
Mar 25 14:47:58 aptiva kernel: usb 4-4: configuration #1 chosen from 1 choice
Mar 25 14:47:58 aptiva kernel:
Mar 25 14:47:58 aptiva kernel:  _____     ____    _    ____
Mar 25 14:47:58 aptiva kernel: |__  /   _|  _ \  / \  / ___|
Mar 25 14:47:58 aptiva kernel:   / / | | | | | |/ _ \ \___ \
Mar 25 14:47:58 aptiva kernel:  / /| |_| | |_| / ___ \ ___) |
Mar 25 14:47:58 aptiva kernel: /____\__, |____/_/   \_\____/
Mar 25 14:47:58 aptiva kernel:      |___/
Mar 25 14:47:58 aptiva kernel: ZD1211B - version 2.21.0.0
Mar 25 14:47:58 aptiva kernel: vendor_id = 0ace
Mar 25 14:47:58 aptiva kernel: product_id = 1215
Mar 25 14:47:58 aptiva kernel: USB 2.0 Host
Mar 25 14:47:58 aptiva kernel: Release Ver = 4810
Mar 25 14:47:58 aptiva kernel: EEPORM Ver = 4810
Mar 25 14:47:58 aptiva kernel: Finsih download Firmware. Ready to reboot
Mar 25 14:47:58 aptiva kernel: PA type: 0
Mar 25 14:47:58 aptiva kernel: UW2453 RF
Mar 25 14:47:58 aptiva kernel: OverWrite CR157 = 0xF0
Mar 25 14:47:58 aptiva kernel: zd1205_config: EEP(HWFeature)=0x2000
Mar 25 14:47:58 aptiva kernel: AllowedChannel = 000107ff
Mar 25 14:47:58 aptiva kernel: Region:48
Mar 25 14:47:59 aptiva kernel: usbcore: registered new interface driver zd1211b
Mar 25 14:48:01 aptiva ifup:     eth1
Mar 25 14:48:02 aptiva ifup-wireless:     eth1      warning: using NO encryption
Mar 25 14:48:02 aptiva ifup-wireless: command 'iwconfig eth1 mode Managed' retur
ned
Mar 25 14:48:02 aptiva ifup-wireless:  Error for wireless request "Set Mode" (8B
06) :
Mar 25 14:48:02 aptiva ifup-wireless:     SET failed on device eth1 ; Invalid ar
gument.
Mar 25 14:48:02 aptiva ifup-wireless: command 'iwconfig eth1 nick aptiva' return
ed
Mar 25 14:48:02 aptiva ifup-wireless:  Error for wireless request "Set Nickname"
 (8B1C) :
Mar 25 14:48:02 aptiva ifup-wireless:     SET failed on device eth1 ; Invalid ar
gument.
Mar 25 14:48:02 aptiva ifup-wireless: command 'iwconfig eth1 key off' returned
Mar 25 14:48:02 aptiva ifup-wireless:  Error for wireless request "Set Encode" (
8B2A) :
Mar 25 14:48:02 aptiva ifup-wireless:     SET failed on device eth1 ; Invalid ar
gument.
Mar 25 14:48:02 aptiva ifup-wireless: command 'iwconfig eth1 essid Wireless' ret
urned
Mar 25 14:48:02 aptiva ifup-wireless:  Error for wireless request "Set ESSID" (8
B1A) :
Mar 25 14:48:02 aptiva ifup-wireless:     SET failed on device eth1 ; Invalid ar
gument.
aptiva:/home/alex # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:30:4F:1A:CC:8D
          inet addr:192.168.1.73  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::230:4fff:fe1a:cc8d/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:422 errors:0 dropped:0 overruns:0 frame:0
          TX packets:338 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:33843 (33.0 Kb)  TX bytes:48262 (47.1 Kb)
          Interrupt:10 Base address:0x8000
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:50 errors:0 dropped:0 overruns:0 frame:0
          TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3652 (3.5 Kb)  TX bytes:3652 (3.5 Kb)

aptiva:/home/alex # iwconfig
lo        no wireless extensions.
eth0      no wireless extensions.
eth1      no wireless extensions.

But if I enter the following, it works.


ifconfig eth1 up
ifup eth1

Trouble is that this is supposed to be a headless server, so even though that's not much, having to log in and type that before I can get a network connection is a problem.

Any ideas?

Thanks,

Alex

IP Logged

RobS
Newbie
Newbie

Joined: 06 Dec 2007
Online Status: Offline
Posts: 4

Posted: 26 Mar 2008 at 8:38am

Glad it's working

Using Google and searching for "ubuntu network device boot" you'll find that you need to edit /etc/networking/interfaces

Rob

IP Logged

alexmay
Newbie
Newbie

Joined: 06 Mar 2008
Online Status: Offline
Posts: 7

Posted: 26 Mar 2008 at 8:46am

Sorry, my mistake.

I thought that I had said (but I hadn't) in all my trials, I switched from Ubuntu to Suse 10.3.

I found the stuff you are talking about with /etc/networking/interfaces, but Suse uses a different approach, and I can't work out the equivalent.

It seems like I just need to set "ifconfig eth1 up" to execute just before the boot sequence executes "ifup eth1" which it seems to be doing automatically.

But I can't work out how to do that in Suse.

I did try lots of googling, but got nowhere.

IP Logged

54Mbps WiFi Wireless USB LAN Adapter 802.11g WU-ZD1211B
Pluscom Forum : Networking : Wireless Adapters : 54Mbps WiFi Wireless USB LAN Adapter 802.11g WU-ZD1211B