Toshiba Wireless Card problems.

[loom001]

I am using a Toshiba Satalllite Pro 4600 and I can not get the built in wireless card to work.

It was working just fine with RH 9 and Fedora Core1, but I did a clean install of Fedora Core 2 and it will not even detect it.

Can anyone tell me how I might solve this problem? I have tried a manual install using the intel express pro 100 driver and setting it to irq 11, but had no luck. Any help would be great.

[greeners]

I too have this problem. I'm very new to Linux although I have developing on Unix (various) for years. The NIC is detected but is not a device I can intstall. I too have gone with core 2 and am starting to regret it.
Thoughts and suggestions very welcome.
Sound is also not working. [sigh]

[Ug]

I also have a Toshiba laptop. Basically FC2 doesn't load a required kernel module to kick start PCMCIA. So you need to do the following to make it work.su -
modprobe yenta-socket
service pcmcia restart

[AtomiX]

Thank you sooo much! You're a GENIUS! :) After dumping windows and loading FC2, I've been working on this problem for hours.... Now I can be Microsoft Free :D

[Ug]

By FC3 I hope this problem will have been fixed. But your welcome for the advice. ;)

[mrguytx]

I wonder if this will fix my "sleep of death" wireless nic issue?
I will try this tonite and report both here and in the other thread about the issue:

(close lid on laptop, come back later, OS comes up but nic is permanently asleep)...

Thanks.

[mrguytx]

a quick fix! just go to "server settings" - "services", the click on "pcmcia" and click restart. fixes it every time.

[greeners]

Tried with FC3 and had the same problems. After a lot of messing about I have got this down to the following. There is a problem with IRQ 11 being used by ACPI and it is incompatible with both the wireless NIC interface (pcmcia) and onboard sound for my Toshiba Satellite Pro 4600. To fix the situation I add an option to the kernel load statement in the grub loader configuration. Add pci=noacpi and reboot.

At this point the sound is working but not the wireless NIC.

I then also have to restart the pcmcia service by opening a terminal console , switch to root user (using "su -") and executing "service pcmcia restart". After that the built in wireless NIC works!

We thought this would be solved in FC3 but apparently not. Best of luck for FC4 in the spring! :)

[wkrasl]

I also have a Toshiba laptop. Basically FC2 doesn't load a required kernel module to kick start PCMCIA. So you need to do the following to make it work.su -
modprobe yenta-socket
service pcmcia restart

Well, it seemed like it was worth a try on my Dell Inspiron 300m with Intel PRO 2100 wireless.

"modprobe yenta-socket" came back quietly with another prompt.
"service pcmcia restart" came back with the following:
Shutting down PCMCIA services: done.
Starting PCMCIA services: cardmgr[3781]: open_sock(socket 2) failed: Bad file descriptor
cardmgr[3781]: watching 2 sockets
done.

Network configuration still shows inactive status for eth1

Edit on Devices still shows "eth1 (Intel EtherExpro Pro 100B)" on the Hardware Device tab

checking "Bind" and clicking "Probe" still gives "[Errno 19] No such device." Entering the known MAC address "00:0c:f1:2a:f3:92" gives "Cannot activate network device eth1! Device eth1 has different MAC address than expected, ignoring." (DOS "ipconfig -all" shows the eth1 Intel 2100 MAC address)

Deleting the manually-entered MAC address and unchecking "Bind" goes back to original error, "eepro100 device eth1 does not seem to be present, delaying initialization."

Can anyone suggest a new approach? :confused:

[jim]

I have run into thesame problem before i have uninstalled all the drivers associated with the wireless device.
take a look at this article http://www.fedoranews.org/contributors/jim_lawrence/network_manager/ make surew to check out the first 2 articles and let me know if you have any other questions

[jarifed]

Wlell have similar problems.
Using PCMCI Card Wired internet interface
2 * PCMCIA Card Wireless (these don't work under ME either.
Device is recognised
My problem is that it will not allocate an interrupt for the device.
Has worked under Mandrake 9.1
Not working under Mandrake 9.2 and 10.0 Knoppix FC2 and FC3.
SONY VAIO laptop.
So using a USB Network interface.

[matt_ev]

greeners - you are a star. I can't tell you how many hours I had wasted on this.

I have posted a link to an entry on my pages about how I got this to work:

http://www.deepblue.uk.net/fortopic107.html

When trying to restart pcmcia my satellite pro 4600 reported that yenta-socket was in use and pcmcia would not restart. Instead, the solution for me was to tick the 'start at boot' option in the wireless config. It now works each and every time stright from boot :)

Matt

[jaschwar]

I just installed Fedora Core 3 on my Toshiba Satellite P15 laptop, and executed your three lines in my xterm to try to get the wireless working. It spat back the following:

Shutting down PCMCIA services: done
Starting PCMCIA services: cardmgr[3748]: open_socket(socket 1) failed: Bad file descriptor cardmgr [3748]: watching 1 socket
done

Any thoughts? Obviously, this didn't cure my problems :(

[grachtenpatser]

Hello,

All good advices but i still don't have it working.... i added the pci=noacpi to /boot/grub/grub.conf but no luck, on start it still tells that he disconnects irq 11 with detecting sound hardware. i even added apcia=off no luck what so ever..

could somebody assist me please, i had it even running perfectly with RH8 :(

Thanks

[grachtenpatser]

Hello,

All good advices but i still don't have it working.... i added the pci=noacpi to /boot/grub/grub.conf but no luck, on start it still tells that he disconnects irq 11 with detecting sound hardware. i even added apcia=off no luck what so ever..

could somebody assist me please, i had it even running perfectly with RH8 :(

Thanks


Sorry about that didn't know where to put the extra commands :p for poeple who are as stupid as me..

edit /boot/grub/grub.conf
after LogVol00 rhgb quiet type pci=noacpi

[greeners]

Glad to know some have been helped by my humble posting. I since found that disabling the on-board ethernet NIC would allow the wireless to come up without any need to restart the pcmcia service. It's as though the first [ethernet] NIC failure, because it was not connected to anything, caused the kernel to give up and not bother to try the Wireless NIC. This worked for me very well as I have no reason to use the ethernet interface at all.

Unfortunately the latest kernel update has once again disabled the wireless NIC on reboot so I have to re-enable it each time the machine restarts. Very frustrating. Thinking of giving Linspire a go - it is supposed to have very good laptop integration.

[mrguytx]

If I might recommend Ubuntu?

If I wasn't a Fedora Core addict that is what I'd be using.

[greeners]

I fixed my wireless stet-up so it will now start properly when the machine boots. The kernel update which caused it to stop working at boot seems to have simply disabled the wireless NIC at startup. So simply marking the wireless NIC to be enabled fixed it. Very simple. Can't understand why I didn't notice it to start with.

Not sure if this was a new feature in this build to get around the issued of the ordering of modules as they start or not. The updates are all a bit of a blur and I'm no longer going to run up2date in the gnome panel. Updating my system two or three times a week is too risky. Now it's stable I would like to leave it alone.

So I'm a happy wireless camper again. Any I will stick with FC3 for now. No reason to change! Oh, lack of Mono rpms from Redhat is one reason to change. But that's another topic for another day isn't it !
:O)