Orinoco Driver on old Toshiba Portege not working in Mint

Questions about WIFI networks and devices
Forum rules
Before you post please read this

Orinoco Driver on old Toshiba Portege not working in Mint

Postby Ramblin on Thu Jan 17, 2013 10:13 am

I have an old Toshiba Portege PP350C-002GJP 32-bit laptop with 1GB RAM
It came with Windows XP and had stayed that way until recently when I decided to move to a more efficient OS - Linux
After looking around, Linux Mint won the contest so, using the Ethernet wired connection, I installed Linux Mint 13 Maya - Nate edition and I love it

Because it has only 1GB RAM, I had to sudo apt-get remove ubiquity-slideshow-mint before running the 32- bit installer, but after that, the install went fine
I ran apt-get update && apt-get upgrade and all went well

Problem: I cannot get the wireless card to work and I am getting inconsistent results from the command-line entries (see below) and I am wondering if there is a hardware problem with the wireless card or if it is an install configuration error on my part. When I run
Code: Select all
lshw -C network

I get
*-network
description: Ethernet interface
product: 82551QM Ethernet Controller
vendor: Intel Corporation
physical id: a
bus info: pci@0000:00:0a.0
logical name: eth0
version: 10
serial: 00:00:39:65:8b:e0
size: 100Mbit/s
capacity: 100Mbit/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=e100 driverversion=3.5.24-k2-NAPI duplex=half firmware=N/A ip=192.168.1.152 latency=64 link=yes maxlatency=56 mingnt=8 multicast=yes port=MII speed=100Mbit/s
resources: irq:11 memory:f7eff000-f7efffff ioport:eec0(size=64) memory:f7ec0000-f7edffff
*-network
description: Wireless interface
physical id: 2
logical name: eth1
serial: 00:02:2d:6c:e5:db
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=orinoco_cs driverversion=3.2.0-23-generic firmware=Lucent/Agere 9.48 link=no multicast=yes wireless=IEEE 802.11b

Which tells me the wireless mini-pci card is there and recognized but I cannot get the wireless hookup to work.

but when I run
Code: Select all
lspci

I get
00:00.0 Host bridge: ALi Corporation M1644/M1644T Northbridge+Trident (rev 01)
00:01.0 PCI bridge: ALi Corporation PCI to AGP Controller
00:04.0 IDE interface: ALi Corporation M5229 IDE (rev c3)
00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 01)
00:07.0 ISA bridge: ALi Corporation M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+]
00:08.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
00:0a.0 Ethernet controller: Intel Corporation 82551QM Ethernet Controller (rev 10)
00:0c.0 USB controller: NEC Corporation USB (rev 41)
00:0c.1 USB controller: NEC Corporation USB (rev 41)
00:0c.2 USB controller: NEC Corporation USB 2.0 (rev 02)
00:10.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01)
00:11.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support (rev 32)
00:11.1 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support (rev 32)
00:12.0 System peripheral: Toshiba America Info Systems SD TypA Controller (rev 03)
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade XPAi1 (rev 82)

which does NOT show a wireless card, just the wired Ethernet interface

When I run
Code: Select all
mintwifi

I get
-------------------------
* I. scanning WIFI PCI devices...
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
lo no wireless extensions.

eth1 IEEE 802.11b ESSID:""
Mode:Managed Frequency:2.457 GHz Access Point: None
Bit Rate:11 Mb/s Sensitivity:1/0
Retry limit:8 RTS thr=2347 B Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/70 Signal level=-122 dBm Noise level=-122 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:6
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 00:00:39:65:8b:e0
inet addr:192.168.1.152 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::200:39ff:fe65:8be0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7445 errors:0 dropped:0 overruns:0 frame:0
TX packets:7038 errors:0 dropped:0 overruns:0 carrier:0
collisions:186 txqueuelen:1000
RX bytes:494361 (494.3 KB) TX bytes:2102710 (2.1 MB)

eth1 Link encap:Ethernet HWaddr 00:02:2d:6c:e5:db
UP BROADCAST 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:11 Base address:0x100

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)

-------------------------
* V. querying DHCP...
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service smbd reload

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the reload(8) utility, e.g. reload smbd
RTNETLINK answers: File exists
-------------------------
* VI. querying nslookup google.com...
Server: 192.168.1.1
Address: 192.168.1.1#53

which again shows the existence of a wireless card

I have read numerous postings, some of which say that, since 2010, Linux Mint does not need to use ndiswrapper to load Windows many drivers but so far, I am tearing out my (already thin) hair trying to get it to work natively. I have read that once you initiate ndiswrapper, it then prevents any native drivers from being usable so I do not want to try this until I have exhausted the native Linux Mint options.

I think the Windows driver that was used for this card was net5211.inf and I did find this at
/usr/lib/linuxmint/mintWifi/drivers/i386/Atheros_AR5007eg/net5211.inf

so if needed, I think I know how to try using the Windows driver within ndiswrapper but do not want to go there if I can get the system working natively.

Interestingly, when I run
Code: Select all
iwlist eth1 scan

I get
eth1 Scan completed :
Cell 01 - Address: 00:50:7F:AB:C4:00
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=70/70 Signal level=-21 dBm
Encryption key:on
ESSID:"RC_DraytekWAP"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=0000000aa08d6d1e
Extra: Last beacon: 188ms ago
IE: Unknown: 000D52435F4472617974656B574150
IE: Unknown: 010882848B961224486C
IE: Unknown: 030106
IE: Unknown: 2A0100
IE: Unknown: 32040C183060
IE: Unknown: 2D1A6E1017FFFFFF0001000000000000000000000000000000000000
IE: Unknown: 3D1606000000000000000000000000000000000000000000
IE: Unknown: 3E0100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
IE: Unknown: 0B050000107A12
IE: Unknown: 7F0101
IE: Unknown: DD07000C4300000000
IE: Unknown: 0706545720010E10
IE: Unknown: DD1E00904C336E1017FFFFFF0001000000000000000000000000000000000000
IE: Unknown: DD1A00904C3406000000000000000000000000000000000000000000
IE: Unknown: DD9D0050F204104A0001101044000101103B00010310470010BC329E001DD811B2860100507FABC4001021001852616C696E6B20546563686E6F6C6F67792C20436F72702E1023001C52616C696E6B20576972656C6573732041636365737320506F696E74102400065254323836301042000831323334353637381054000800060050F20400011011000952616C696E6B415053100800020084103C000100
Cell 02 - Address: 00:14:D1:E6:6D:74
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=29/70 Signal level=-81 dBm
Encryption key:on
ESSID:"TRENDnet652"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000017323b5b052
Extra: Last beacon: 156ms ago
IE: Unknown: 000B5452454E446E6574363532
IE: Unknown: 010882848B960C121824
IE: Unknown: 03010B
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
IE: Unknown: 2D1A6C181EFFFF000000000000000000000000000000000000000000
IE: Unknown: 3D160B000300000000000000000000000000000000000000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
IE: Unknown: DD1E00904C336C181EFFFF000000000000000000000000000000000000000000
IE: Unknown: DD1A00904C340B000300000000000000000000000000000000000000
IE: Unknown: DD0700E04C02022000

which makes it look like the card is actually working.

But I cannot get connected to any wireless network. The RC_DraytekWAP shown above is my wireless access point so I thought that maybe the encryption was preventing connection so I disabled all security encryption and tried to connect but no luck.

Sorry for the long and rambling post, but I have been working on this for days and cannot get it to work so wanted you to know I have tried all the obvious things I can think of.

Questions:
1) Do I need to use ndiswrapper to get the Windows drivers to work? I have the Windows drivers available if needed.
- if so, can someone give me clear step-=by-step instructions on how?
(I have read conflicting posts on how to do this)
2) If I do NOT need to use ndiswrapper, how do I get the native Linux Mint wireless drivers to work?

Thank you in advance
Ramblin
Last edited by Ramblin on Thu Jan 17, 2013 5:22 pm, edited 2 times in total.
Ramblin
Level 1
Level 1
 
Posts: 18
Joined: Thu Jan 17, 2013 9:39 am

Linux Mint is funded by ads and donations.
 

Re: Atheros Drivers on old Toshiba Portege not working in Mi

Postby AlbertP on Thu Jan 17, 2013 10:18 am

You do not appear to have an Atheros card at all. According to lshw, your wireless network card is a PCMCIA device using the orinoco_cs driver. It will appear in lspcmcia instead of lspci as it is not a PCI device (PCMCIA chips are sometimes actually a PCI device so appearing in lspci, but yours isn't).
Please post lspcmcia output.

Edit. Support for WPA protected networks is not available for some orinoco devices, and your network is WPA protected. That may be why it doesn't connect.
2nd edit. You have the right firmware in your device, Agere 9.48, so WPA should work.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6513
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Atheros Drivers on old Toshiba Portege not working in Mi

Postby Ramblin on Thu Jan 17, 2013 11:05 am

When I run
Code: Select all
lspcmcia

I get
Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:00:10.0)
Socket 0 Device 0: [orinoco_cs] (bus ID: 0.0)
Socket 1 Bridge: [yenta_cardbus] (bus ID: 0000:00:11.0)
Socket 2 Bridge: [yenta_cardbus] (bus ID: 0000:00:11.1)


Does this mean I have a PCMCIA wireless card?
And if so, where do I look to get it working?

I looked in the PCMCIA slot and there is nothing there.
Is there an internal PCMCIA slot that is not intended to be used for removable media?

Thanks for your quick reply - you may have corrected my (fruitless) attempts to get the mini-PCI card working :-)

Richard
Ramblin
Level 1
Level 1
 
Posts: 18
Joined: Thu Jan 17, 2013 9:39 am

Re: Atheros Drivers on old Toshiba Portege not working in Mi

Postby AlbertP on Thu Jan 17, 2013 11:59 am

I think it's indeed internal (there may not even be a slot, it could also be a soldered connection) since your lspci shows three CardBus bridges and most laptops have only one or two external slots.

Right, the card is detected, but this doesn't give us much information yet about the card, apart from its driver orinoco_cs. Could you run pccardctl ident? I was unaware that lspcmcia had such a concise output, since I don't own any PCMCIA (non-PCI) devices myself.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6513
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Atheros Drivers on old Toshiba Portege not working in Mi

Postby AlbertP on Thu Jan 17, 2013 12:06 pm

I just read on http://www.linuxwireless.org/en/users/Drivers/orinoco that only WPA with TKIP is supported by the Linux orinoco driver, and no WPA with CCMP. Your RC_DraytekWAP access point, as per iwlist scan output, only uses CCMP as opposed to the detected TRENDnet652 network which can do TKIP too. Probably you can change this in your router's configuration

Note: if you change the encryption type, you will also have to change this on all connected Windows computers. Else Windows will complain that the security settings don't match (even if the actual key or password has not changed). An easy workaround to this is deleting the network from the preferred networks, then connecting again.

If you don't manage to get the WPA encryption working, you could revert to WEP but this will make your network less secure. Or you could buy a USB dongle, or a more recent card (for the CardBus/PCMCIA slot) that does not have any problem with modern wi-fi security.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6513
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Atheros Drivers on old Toshiba Portege not working in Mi

Postby Ramblin on Thu Jan 17, 2013 12:51 pm

When I run
Code: Select all
pccardctl ident

I get
Socket 0:
product info: "TOSHIBA
", "Wireless LAN Card
", "Version 01.01
", ""
manfid: 0x0156, 0x0002
function: 6 (network)
Socket 1:
no product info available
Socket 2:
no product info available


I also looked at the Security setting on my router and it says I am set for WPA2/PSK which lists, as the encryption mode
TKIP for WPA/AES for WPA2

which leads me to believe that the setting does allow TKIP encryption

I did, in a previous test, disable ALL encryption to see if the encryption was in fact part of the problem and it did not make a difference. (So I put the encyrption back on to be safe)

I found a Linux_Orinoco driver page at
http://www.nongnu.org/orinoco/documentation/
but there is some confusion if it is included OOTB or if it was deprecated back in Kernel 2.4 and with the newer Kernel in Linux Mint Maya, I am not sure if the driver will still work.

Does the information above from pccardctl ident help you at all?

I really appreciate you helping out here
Ramblin
Level 1
Level 1
 
Posts: 18
Joined: Thu Jan 17, 2013 9:39 am

Re: Atheros Drivers on old Toshiba Portege not working in Mi

Postby AlbertP on Thu Jan 17, 2013 1:29 pm

Ok, it looks like a generic Lucent Orinoco card rebranded by Toshiba, nothing special. The page you linked suggests that it could be a Mini PCI card with integrated PCI to PCMCIA bridge chip, which sounds reasonable since most old laptops use Mini PCI for the wifi card. In that case, it would be possible to swap the card for an Intel 2200 Mini PCI card for example. Then wifi would work well.

About the kernel version, this one certainly has the orinoco driver included, else you wouldn't have been able to get an iwlist or iwconfig output about this card at all.

It could be that the drivers for ancient hardware aren't maintained very good anymore.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6513
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Atheros Drivers on old Toshiba Portege not working in Mi

Postby Ramblin on Thu Jan 17, 2013 2:03 pm

I am guessing this is just going to have to be logged as one of life's little mysteries.

When I click on the network icon in the taskbar, I can see 2 or 3 wireless networks in range, including my own, RC_DraytekWAP which has a full 4 bar signal strength (it should, it is sitting 6 feet from the WAP).

So that tells me the card is there and the driver is there ...

But I cannot connect.

I tried (again) temporarily eliminating all the security on my WAP
- disabled encryption
- disable Mac filtering
- disabled WPS
but it made no difference. I can see but not connect to the WAP.

I then thought I remembered something I read in one of the Orinoco we pages that the Orinoco driver only supports Ad-hoc mode, not Infrastructure, which is the default mode of the Linux Mint connection, so I went in and edited the RC-DraytekWAP to use Ad-hoc mode. No difference.

Is there any chance the receive part of the wireless card is working but the transmit is not?

Thanks for your help. If you or anyone else comes up with some inspiration and would like to suggest fixes to test or get the existing card/driver working, please feel free. I don't want to invest in additional hardware for a 10 year-old laptop, so fixing what I have is the preferred route.
Ramblin
Level 1
Level 1
 
Posts: 18
Joined: Thu Jan 17, 2013 9:39 am

Re: Atheros Drivers on old Toshiba Portege not working in Mi

Postby AlbertP on Thu Jan 17, 2013 2:54 pm

Could you click the network in the list and then run "dmesg" in terminal to find out what's going wrong when connecting?
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6513
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Atheros Drivers on old Toshiba Portege not working in Mi

Postby Ramblin on Thu Jan 17, 2013 3:22 pm

when i run
Code: Select all
dmesg

I get (the last set starting with Rate Limit ... repeats multiple times which I did not include - same content over and over again)(I started the copy after the networking information started; did you want the full dmesg from the beginning?)

[ 20.316255] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 20.801182] snd_ali5451 0000:00:06.0: power state changed by ACPI to D0
[ 20.801201] snd_ali5451 0000:00:06.0: power state changed by ACPI to D0
[ 20.801212] snd_ali5451 0000:00:06.0: enabling device (0000 -> 0003)
[ 20.801826] ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11
[ 20.801839] snd_ali5451 0000:00:06.0: PCI INT A -> Link[LNKH] -> GSI 11 (level, low) -> IRQ 11
[ 21.029345] init: failsafe main process (556) killed by TERM signal
[ 22.585447] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1e0-0x1e7 0x1f0-0x1f7 0x200-0x207 0x220-0x22f 0x330-0x33f 0x370-0x377 0x388-0x38f
[ 22.587842] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff:
[ 22.604504] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1e0-0x1e7 0x1f0-0x1f7 0x200-0x207 0x220-0x22f 0x330-0x33f 0x370-0x377 0x388-0x38f
[ 22.606897] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x3f0-0x3f7 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
[ 22.607876] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff:
[ 22.662913] pcmcia_socket pcmcia_socket2: cs: IO port probe 0x100-0x3af: excluding 0x3f0-0x3f7 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
[ 22.702280] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x820-0x8ff: clean.
[ 22.703167] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcf7: excluding 0x170-0x177 0x1e0-0x1e7 0x1f0-0x1f7 0x200-0x207 0x220-0x22f 0x330-0x33f 0x370-0x377 0x388-0x38f
[ 22.711843] pcmcia_socket pcmcia_socket2: cs: IO port probe 0x3e0-0x4ff: clean.
[ 22.755031] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
[ 22.773911] excluding 0x3f0-0x3f7 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
[ 22.774560] pcmcia_socket pcmcia_socket2: cs: IO port probe 0x820-0x8ff: clean.
[ 22.775440] pcmcia_socket pcmcia_socket2: cs: IO port probe 0xc00-0xcf7:
[ 22.784347] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcbfff 0xe0000-0xfffff
[ 22.784483] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean.
[ 22.784539] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff
[ 22.784602] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
[ 22.785649] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean.
[ 22.807984] pcmcia_socket pcmcia_socket1: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcbfff 0xe0000-0xfffff
[ 22.818102] pcmcia_socket pcmcia_socket1: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0e00000-0xa0efffff
[ 22.818163] pcmcia_socket pcmcia_socket1: cs: memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff
[ 22.818224] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa00-0xaff: clean.
[ 22.829111] clean.
[ 22.829516] pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 11)
[ 22.843585] clean.
[ 22.843806] pcmcia_socket pcmcia_socket2: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcbfff 0xe0000-0xfffff
[ 22.843864] pcmcia_socket pcmcia_socket2: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa00fffff
[ 22.843924] pcmcia_socket pcmcia_socket2: cs: memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff
[ 22.843979] pcmcia_socket pcmcia_socket2: cs: IO port probe 0xa00-0xaff: clean.
[ 22.868970] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 22.871499] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 22.956845] cfg80211: Calling CRDA to update world regulatory domain
[ 22.978276] orinoco 0.15 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
[ 23.080001] orinoco_cs 0.0: Hardware identity 0005:0004:0005:0000
[ 23.080166] orinoco_cs 0.0: Station identity 001f:0001:0008:000a
[ 23.080174] orinoco_cs 0.0: Firmware determined as Lucent/Agere 8.10
[ 23.215559] orinoco_cs 0.0: Hardware identity 0005:0004:0005:0000
[ 23.215698] orinoco_cs 0.0: Station identity 001f:0002:0009:0030
[ 23.215706] orinoco_cs 0.0: Firmware determined as Lucent/Agere 9.48
[ 23.215713] orinoco_cs 0.0: Ad-hoc demo mode supported
[ 23.215718] orinoco_cs 0.0: IEEE standard IBSS ad-hoc mode supported
[ 23.215723] orinoco_cs 0.0: WEP supported, 104-bit key
[ 23.215727] orinoco_cs 0.0: WPA-PSK supported
[ 23.236590] cfg80211: World regulatory domain updated:
[ 23.236612] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 23.236619] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.236625] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 23.236631] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 23.236637] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.236643] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.246925] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[ 23.246938] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.246944] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[ 23.246951] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.246956] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[ 23.246963] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.246968] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[ 23.246975] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.246980] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[ 23.246986] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.246992] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[ 23.246998] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.247003] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[ 23.247010] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.247015] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[ 23.247022] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.247027] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 23.247033] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.247039] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 23.247045] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.247050] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 23.247057] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.326168] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 23.333905] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 24.012897] eth1: Lucent/Agere firmware doesn't support manual roaming
[ 24.437111] vesafb: mode is 1024x768x32, linelength=4096, pages=0
[ 24.437124] vesafb: scrolling: redraw
[ 24.437132] vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
[ 24.439293] vesafb: framebuffer at 0xfc000000, mapped to 0xf8300000, using 3072k, total 3072k
[ 24.443118] fbcon: VESA VGA (fb0) is primary device
[ 24.443591] Console: switching to colour frame buffer device 128x48
[ 24.443664] fb0: VESA VGA frame buffer device
[ 24.471741] eth1: New link status: Connected (0001)
[ 24.472463] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 25.068486] eth1: Information frame lost.
[ 26.076489] eth1: Information frame lost.
[ 26.159931] eth1: Information frame lost.
[ 26.170054] eth1: Information frame lost.
[ 26.170437] eth1: Information frame lost.
[ 26.421379] eth1: Information frame lost.
[ 26.672349] eth1: Information frame lost.
[ 26.918751] eth1: Information frame lost.
[ 27.170992] eth1: Information frame lost.
[ 27.209096] eth1: Information frame lost.
[ 28.562667] init: plymouth-stop pre-start process (1200) terminated with status 1
[ 30.790875] eth1: New link status: Disconnected (0002)
[ 31.819727] net_ratelimit: 4 callbacks suppressed
[ 31.819742] eth1: Information frame lost.
[ 31.827259] eth1: Information frame lost.
[ 31.846722] eth1: Information frame lost.
[ 31.853904] eth1: Information frame lost.
[ 31.861076] eth1: Information frame lost.
[ 31.880768] eth1: Information frame lost.
[ 31.887824] eth1: Information frame lost.
[ 31.894961] eth1: Information frame lost.
[ 31.917540] eth1: Information frame lost.
[ 31.924709] eth1: Information frame lost.
[ 32.023396] eth1: New link status: Connected (0001)
[ 38.368661] eth1: New link status: Disconnected (0002)
[ 39.396812] net_ratelimit: 5 callbacks suppressed
[ 39.396827] eth1: Information frame lost.
[ 39.404320] eth1: Information frame lost.
[ 39.411501] eth1: Information frame lost.
[ 39.418696] eth1: Information frame lost.
[ 39.425862] eth1: Information frame lost.
[ 39.445359] eth1: Information frame lost.
[ 39.452526] eth1: Information frame lost.
[ 39.462761] eth1: Information frame lost.
[ 39.485344] eth1: Information frame lost.
[ 39.492527] eth1: Information frame lost.
Ramblin
Level 1
Level 1
 
Posts: 18
Joined: Thu Jan 17, 2013 9:39 am

Re: Orinoco Driver on old Toshiba Portege not working in Min

Postby Ramblin on Thu Jan 17, 2013 3:41 pm

In case it matters, I also ran dmesg after eliminating all the security on my WAP (RC_DraytekWAP) and I got this

[ 20.316255] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 20.801182] snd_ali5451 0000:00:06.0: power state changed by ACPI to D0
[ 20.801201] snd_ali5451 0000:00:06.0: power state changed by ACPI to D0
[ 20.801212] snd_ali5451 0000:00:06.0: enabling device (0000 -> 0003)
[ 20.801826] ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11
[ 20.801839] snd_ali5451 0000:00:06.0: PCI INT A -> Link[LNKH] -> GSI 11 (level, low) -> IRQ 11
[ 21.029345] init: failsafe main process (556) killed by TERM signal
[ 22.585447] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1e0-0x1e7 0x1f0-0x1f7 0x200-0x207 0x220-0x22f 0x330-0x33f 0x370-0x377 0x388-0x38f
[ 22.587842] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff:
[ 22.604504] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1e0-0x1e7 0x1f0-0x1f7 0x200-0x207 0x220-0x22f 0x330-0x33f 0x370-0x377 0x388-0x38f
[ 22.606897] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x3f0-0x3f7 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
[ 22.607876] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff:
[ 22.662913] pcmcia_socket pcmcia_socket2: cs: IO port probe 0x100-0x3af: excluding 0x3f0-0x3f7 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
[ 22.702280] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x820-0x8ff: clean.
[ 22.703167] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcf7: excluding 0x170-0x177 0x1e0-0x1e7 0x1f0-0x1f7 0x200-0x207 0x220-0x22f 0x330-0x33f 0x370-0x377 0x388-0x38f
[ 22.711843] pcmcia_socket pcmcia_socket2: cs: IO port probe 0x3e0-0x4ff: clean.
[ 22.755031] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
[ 22.773911] excluding 0x3f0-0x3f7 0x408-0x40f 0x480-0x48f 0x4d0-0x4d7
[ 22.774560] pcmcia_socket pcmcia_socket2: cs: IO port probe 0x820-0x8ff: clean.
[ 22.775440] pcmcia_socket pcmcia_socket2: cs: IO port probe 0xc00-0xcf7:
[ 22.784347] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcbfff 0xe0000-0xfffff
[ 22.784483] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean.
[ 22.784539] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff
[ 22.784602] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
[ 22.785649] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean.
[ 22.807984] pcmcia_socket pcmcia_socket1: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcbfff 0xe0000-0xfffff
[ 22.818102] pcmcia_socket pcmcia_socket1: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0e00000-0xa0efffff
[ 22.818163] pcmcia_socket pcmcia_socket1: cs: memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff
[ 22.818224] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa00-0xaff: clean.
[ 22.829111] clean.
[ 22.829516] pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 11)
[ 22.843585] clean.
[ 22.843806] pcmcia_socket pcmcia_socket2: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcbfff 0xe0000-0xfffff
[ 22.843864] pcmcia_socket pcmcia_socket2: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa00fffff
[ 22.843924] pcmcia_socket pcmcia_socket2: cs: memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff
[ 22.843979] pcmcia_socket pcmcia_socket2: cs: IO port probe 0xa00-0xaff: clean.
[ 22.868970] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 22.871499] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 22.956845] cfg80211: Calling CRDA to update world regulatory domain
[ 22.978276] orinoco 0.15 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
[ 23.080001] orinoco_cs 0.0: Hardware identity 0005:0004:0005:0000
[ 23.080166] orinoco_cs 0.0: Station identity 001f:0001:0008:000a
[ 23.080174] orinoco_cs 0.0: Firmware determined as Lucent/Agere 8.10
[ 23.215559] orinoco_cs 0.0: Hardware identity 0005:0004:0005:0000
[ 23.215698] orinoco_cs 0.0: Station identity 001f:0002:0009:0030
[ 23.215706] orinoco_cs 0.0: Firmware determined as Lucent/Agere 9.48
[ 23.215713] orinoco_cs 0.0: Ad-hoc demo mode supported
[ 23.215718] orinoco_cs 0.0: IEEE standard IBSS ad-hoc mode supported
[ 23.215723] orinoco_cs 0.0: WEP supported, 104-bit key
[ 23.215727] orinoco_cs 0.0: WPA-PSK supported
[ 23.236590] cfg80211: World regulatory domain updated:
[ 23.236612] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 23.236619] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.236625] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 23.236631] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 23.236637] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.236643] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.246925] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[ 23.246938] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.246944] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[ 23.246951] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.246956] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[ 23.246963] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.246968] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[ 23.246975] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.246980] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[ 23.246986] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.246992] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[ 23.246998] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.247003] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[ 23.247010] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.247015] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[ 23.247022] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.247027] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 23.247033] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.247039] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 23.247045] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.247050] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 23.247057] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 23.326168] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 23.333905] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 24.012897] eth1: Lucent/Agere firmware doesn't support manual roaming
[ 24.437111] vesafb: mode is 1024x768x32, linelength=4096, pages=0
[ 24.437124] vesafb: scrolling: redraw
[ 24.437132] vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
[ 24.439293] vesafb: framebuffer at 0xfc000000, mapped to 0xf8300000, using 3072k, total 3072k
[ 24.443118] fbcon: VESA VGA (fb0) is primary device
[ 24.443591] Console: switching to colour frame buffer device 128x48
[ 24.443664] fb0: VESA VGA frame buffer device
[ 24.471741] eth1: New link status: Connected (0001)
[ 24.472463] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 25.068486] eth1: Information frame lost.
[ 26.076489] eth1: Information frame lost.
[ 26.159931] eth1: Information frame lost.
[ 26.170054] eth1: Information frame lost.
[ 26.170437] eth1: Information frame lost.
[ 26.421379] eth1: Information frame lost.
[ 26.672349] eth1: Information frame lost.
[ 26.918751] eth1: Information frame lost.
[ 27.170992] eth1: Information frame lost.
[ 27.209096] eth1: Information frame lost.
[ 28.562667] init: plymouth-stop pre-start process (1200) terminated with status 1
[ 30.790875] eth1: New link status: Disconnected (0002)
[ 31.819727] net_ratelimit: 4 callbacks suppressed
[ 31.819742] eth1: Information frame lost.
[ 31.827259] eth1: Information frame lost.
[ 31.846722] eth1: Information frame lost.
[ 31.853904] eth1: Information frame lost.
[ 31.861076] eth1: Information frame lost.
[ 31.880768] eth1: Information frame lost.
[ 31.887824] eth1: Information frame lost.
[ 31.894961] eth1: Information frame lost.
[ 31.917540] eth1: Information frame lost.
[ 31.924709] eth1: Information frame lost.
[ 32.023396] eth1: New link status: Connected (0001)
[ 38.368661] eth1: New link status: Disconnected (0002)
[ 39.396812] net_ratelimit: 5 callbacks suppressed
[ 39.396827] eth1: Information frame lost.
[ 39.404320] eth1: Information frame lost.
[ 39.411501] eth1: Information frame lost.
[ 39.418696] eth1: Information frame lost.
[ 39.425862] eth1: Information frame lost.
[ 39.445359] eth1: Information frame lost.
[ 39.452526] eth1: Information frame lost.
[ 39.462761] eth1: Information frame lost.
[ 39.485344] eth1: Information frame lost.
[ 39.492527] eth1: Information frame lost.
[ 39.632831] eth1: New link status: Connected (0001)
[ 45.946447] eth1: New link status: Disconnected (0002)
[ 46.974922] net_ratelimit: 4 callbacks suppressed
[ 46.974936] eth1: Information frame lost.
[ 46.982452] eth1: Information frame lost.
[ 46.989629] eth1: Information frame lost.
[ 46.996811] eth1: Information frame lost.
[ 47.003996] eth1: Information frame lost.
[ 47.023879] eth1: Information frame lost.
[ 47.031476] eth1: Information frame lost.
[ 47.038373] eth1: Information frame lost.
[ 47.063336] eth1: Information frame lost.
[ 47.069628] eth1: Information frame lost.

... (repeated many times)

[ 1335.325680] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1335.336044] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1335.346695] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1335.369209] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1335.382034] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1335.393035] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1335.402095] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1335.413012] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1335.425176] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1474.113160] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1474.125236] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1474.136066] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1474.142499] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1474.165482] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1474.184047] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1474.193083] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1474.238816] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
[ 1474.250632] eth1: This firmware requires an ESSID in IBSS-Ad-Hoc mode.
Ramblin
Level 1
Level 1
 
Posts: 18
Joined: Thu Jan 17, 2013 9:39 am

Re: Orinoco Driver on old Toshiba Portege not working in Min

Postby AlbertP on Thu Jan 17, 2013 3:44 pm

Information frame lost. It could be a driver bug. You could try installing new drivers using this package: http://www.kernel.org/pub/linux/kernel/ ... 1-3.tar.xz
After extracting the XZ file, go to the folder where you extracted it, right-click > Open in Terminal, then run these commands to install it:
Code: Select all
make
sudo make install

If they finish without errors then you don't need to post the output. Please reboot when it's done.

It will take some time, because there's no choice for only installing the orinoco module (that can only be done with some commonly used drivers, mostly for far newer hardware).

Also, when used with no encryption, could you disable Ad-Hoc mode and use the normal infrastructure/station mode?
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6513
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Orinoco Driver on old Toshiba Portege not working in Min

Postby Ramblin on Thu Jan 17, 2013 5:31 pm

Wow - a LOT of drivers!
Question: Will the new drivers all load and take up memory/processing power or will the system just load and use the ones it needs?

Unfortunately, no change: I can see the WAP(s) but cannot connect
I did remove all security and I did use infrastructure not Ad-hoc but no connnection. I thought I read that the Orinoco drivers only support Ad-hoc so I also tried Ad-hoc after the Infrastructure failed, but no difference.

I did as instructed (yes, it did take a long time for the make command)
I had no errors with the make command but with the make install command, at the start and end of the process, i received some warnings which I am not sure I should have acted on or not. I did nothing more than you instructed
Code: Select all
make
make install

(I was SSH'd in as root) so if I need to go back and do anything based on the warnings, please let me know. For example, when they say "send a patch against ..." I do not know what they are talking about nor how to do it.

Here is the output from the make install
Warning:
You may or may not need to update your initframfs, you should if
any of the modules installed are part of your initramfs. To add
support for your distribution to do this automatically send a
patch against ./scripts/update-initramfs. If your distribution does not require this
send a patch against the '/usr/bin/lsb_release -i -s': LinuxMint
tag for your distribution to avoid this warning.

make -C /lib/modules/3.2.0-23-generic/build M=/etc/network-wireless/orinoco/compat-drivers-3.7.1-3 modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-23-generic'
Building modules, stage 2.
MODPOST 122 modules
WARNING: "drm_load_edid_firmware" [/etc/network-wireless/orinoco/compat-drivers-3.7.1-3/drivers/gpu/drm/drm_kms_helper.ko] undefined!
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-23-generic'
make -C /lib/modules/3.2.0-23-generic/build M=/etc/network-wireless/orinoco/compat-drivers-3.7.1-3 "INSTALL_MOD_DIR=updates" \
modules_install
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-23-generic'
INSTALL /etc/network-wireless/orinoco/compat-drivers-3.7.1-3/compat/compat.ko
INSTALL /etc/network-wireless/orinoco/compat-drivers-3.7.1-3/compat/sch_codel.ko

... many more of these (122 I think) ...

DEPMOD 3.2.0-23-generic
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-23-generic'
Warning:
You may or may not need to update your initframfs, you should if
any of the modules installed are part of your initramfs. To add
support for your distribution to do this automatically send a
patch against ./scripts/update-initramfs. If your distribution does not require this
send a patch against the '/usr/bin/lsb_release -i -s': LinuxMint
tag for your distribution to avoid this warning.

Note: iwl4965 detected, we're going to disable it. If you would like to enable it later you can run:
sudo iwl-load iwl4965

Running iwl-enable iwlagn...
2 iwl4965 modules found we'll disable all of them
Disabling iwl4965 (1) ... [OK] Module disabled:
kernel/drivers/net/wireless/iwlegacy/iwl4965.ko
Disabling iwl4965 (2) ... [OK] Module disabled:
kernel/drivers/net/wireless/iwlegacy/iwl4965.ko
depmod will prefer updates/ over kernel/ -- OK!

Now run:

sudo make unload to unload all: wireless, bluetooth and ethernet modules
sudo make wlunload to unload wireless modules
sudo make btunload to unload bluetooth modules

Run sudo modprobe driver-name to load your desired driver.
If unsure reboot.
Ramblin
Level 1
Level 1
 
Posts: 18
Joined: Thu Jan 17, 2013 9:39 am

Re: Orinoco Driver on old Toshiba Portege not working in Min

Postby AlbertP on Fri Jan 18, 2013 7:24 am

Ramblin wrote:Question: Will the new drivers all load and take up memory/processing power or will the system just load and use the ones it needs?

No, it's not loading all of that. In fact it's just updating existing drivers to a newer version so it won't make the system heavier. Also, the output from make install looks OK.

Edit: the orinoco driver currently has no maintainer. That may be why bugs don't get fixed anymore. It's only for really old hardware so in fact this is not very surprising.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6513
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Orinoco Driver on old Toshiba Portege not working in Min

Postby Ramblin on Fri Jan 18, 2013 7:39 am

Thank you for working with me on this

No, we did not get it working, but it sounds like there is no way to do so with a native Linux driver

You did help me by stopping my (fruitless) search for a driver solution for the non-existent mini-PCI card :-)

I know the wireless was working in the Windows XP version, so maybe there is a Windows driver out there I can use with ndiswrapper that can get this thing going

Thanks again

Ramblin
Ramblin
Level 1
Level 1
 
Posts: 18
Joined: Thu Jan 17, 2013 9:39 am

Re: Orinoco Driver on old Toshiba Portege not working in Min

Postby AlbertP on Fri Jan 18, 2013 8:14 am

If you still have Windows XP, you can go to Device Manager to see which driver is loaded (name of .inf file) and then copy the folder with that name from C:\Windows\System32\DriverStore. Then you will be able to load the .inf file inside it using Windows Wireless Drivers in the menu.

If you only have an .exe installer of the driver (probably available from Toshiba's website) it may be harder to get the .inf and .sys files out of it; maybe "cabextract filename.exe" in terminal can extract the EXE file (if you open a terminal from the folder where you saved the file).
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6513
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Orinoco Driver on old Toshiba Portege not working in Min

Postby Ramblin on Fri Jan 18, 2013 8:42 am

Now that I know what I am looking for, I did go to the Toshiba site and downloaded the Windows driver for the Wireless LAN card (NOT the Mini-PCI card ...)

It comes as an executable (.exe) file so I used 7zip to extract the .inf and .sys files from the package

I have to run off to work now but I'll try this with ndiswrapper when I get back and let you know how it goes.

R
Ramblin
Level 1
Level 1
 
Posts: 18
Joined: Thu Jan 17, 2013 9:39 am

Re: Orinoco Driver on old Toshiba Portege not working in Min

Postby AlbertP on Fri Jan 18, 2013 8:57 am

I suppose you have WLAGS48B.INF? That would be right. It might also require the .cat and .dll files. If you just put everything in one folder, then it should be fine.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6513
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Re: Orinoco Driver on old Toshiba Portege not working in Min

Postby Ramblin on Fri Jan 18, 2013 3:37 pm

Yes, I have WLAGS48B.INF - thanks for confirming that is the right one

The ndiswrapper instructions say I have to blacklist the existing (partially working) native Linux driver. I do not know which driver/module to blacklist. Do you know?

Richard
Ramblin
Level 1
Level 1
 
Posts: 18
Joined: Thu Jan 17, 2013 9:39 am

Re: Orinoco Driver on old Toshiba Portege not working in Min

Postby AlbertP on Fri Jan 18, 2013 3:59 pm

I think if you use Windows Wireless Drivers in the menu (if it's not available, please install ndisgtk from the repository), instead of manually setting up ndiswrapper, it will be working too. Maybe you don't even need to blacklist it manually then.

If you really want to do it manually then you would need to blacklist orinoco_cs.
Registered Linux User #528502
Image
Feel free to correct me if I'm trying to write in Spanish, French or German.
AlbertP
Level 16
Level 16
 
Posts: 6513
Joined: Sun Jan 30, 2011 12:38 pm
Location: The Netherlands

Linux Mint is funded by ads and donations.
 
Next

Return to Wireless

Who is online

Users browsing this forum: Habitual and 4 guests