How to blacklist orinoco_cs wireless module in 2.17?

Using applications, configuring, problems
Post Reply
Message
Author
svaens
Posts: 46
Joined: Mon 13 Aug 2007, 15:02

How to blacklist orinoco_cs wireless module in 2.17?

#1 Post by svaens »

Hi all,

I'm using Puppy 2.17, and have a question for you, if anyone would be kind enough to find me a solution, i'd be ever so happy! ;)

I have a wireless problem.... the module that is loading by default. This module is documented as being a little broken for my PRISM2 like Mini PCI card Wireless Adapter, in that it works for insecure connections, but try and use WEP, and you have no hope.

So, now I want to try and use another module.

Problem is, I can't stop puppy from loading the module (offender being orinoco_cs).

I have tried editing the MODULESCONFIG file, adding the orinoco_cs to the SKIPLIST, and I even looked at the new Boot manager (SYSTEM Menu), but that also simply adds the module to the same SKIPLIST... which I had already done. Nevertheless, save my session to puppy save file, and reboot, and the damn orinoco_cs module is still there, loaded and unable to be removed by a rmmod (because it is being used by something... not listed).

Is this something that is broken in puppy 2.17 ?
Am I actually doing something wrong?
Have I missed something?
Is there something else I can try?

I have also tried forcing the module to unload, using rmmod -f, but this also doesn't work.... won't unload it.

What can I do?!!! If I can't get this module unloaded, i can't use my wireless network, and I can't use puppy. Do I really need to get myself an earlier version of puppy ? I really didn't want to allocate the time to testing an earlier version. Newer version should be able to do it for me.

Kind regards, and thanks to all readers in advance...

svaens

p.s. the files referred to here are attached in zip form (MODULESCONFIG and rc.modules)
Attachments
mods.zip
(3.76 KiB) Downloaded 225 times

Kal
Posts: 626
Joined: Thu 05 May 2005, 16:59
Location: California, High Desert

#2 Post by Kal »

With jwm, take a look at Boot Manager at Menu>System>BootManager configure bootup. Blacklist is there.

Good Luck, Kal

svaens
Posts: 46
Joined: Mon 13 Aug 2007, 15:02

#3 Post by svaens »

Hi Kal, and thanks for you reply,

however, as I stated above

"and I even looked at the new Boot manager (SYSTEM Menu), but that also simply adds the module to the same SKIPLIST... which I had already done. "

i have already done this, to no effect. This is the problem. SKIPLIST doesn't work.

Boot Manager at Menu>System>BootManager configure bootup uses SKIPLIST, and that don't work.

Or at least, something is going wrong.

If you look at my attached files (last post) you will see that i already have the orinoco_cs module in the blacklist.

thanks,

svaens.

Kal
Posts: 626
Joined: Thu 05 May 2005, 16:59
Location: California, High Desert

#4 Post by Kal »

Sorry, your title miss lead me. At my level, I don't see anything wrong with your entries in MODULESCONFIG. Maybe one of our experts will come along.

Kal

svaens
Posts: 46
Joined: Mon 13 Aug 2007, 15:02

#5 Post by svaens »

yeah, its kind of driving me nuts...
I read somewhere in the middle of the topic of 2.17, someone else having the same problem, of not being able to blacklist a module. The comment was by someone else was to check that he was using the correct module name (as there is a problem with dash vs underscore). So, I asked how to determine the correct module name. I was pointed to the file:

/lib/modules/modules.pcimap.$KERNELVERSION

however, this file doesn't even list the module I am trying to blacklist.
It lists a bunch of other similar named modules.... such as
orinoco_nortel
orinoco_pci
orinoco_plx
orinoco_tmd


but no orinoco_cs.
In anycase, i think the name is fine...

this shouldn't be such a hard problem....

Kal
Posts: 626
Joined: Thu 05 May 2005, 16:59
Location: California, High Desert

#6 Post by Kal »

svaens

The listings in add a new module show it as an underscore. I assume you have looked at the postings by tempestuous, I believe this is up his alley on the wireless. Did you try "rmmod orinoco_cs" or maybe "rmmod -w orinoco_cs" in rc.local, just an idea, it might kill it sooner before it gets started. Was looking under rmmod -h in terminal.

Just as interest. it should be listed in /proc/modules and Menu>System>PupScan interface info as loaded. Know this may be worthless, but was a thought.

Kal

svaens
Posts: 46
Joined: Mon 13 Aug 2007, 15:02

#7 Post by svaens »

Hi Kal,

I'll give a few more things a go.... unfortunately, i am forced away from the computer this weekend...... so i'll give it another go when i get back... thanks for your help though..... i'll let you know how i go later....

User avatar
Dougal
Posts: 2502
Joined: Wed 19 Oct 2005, 13:06
Location: Hell more grotesque than any medieval woodcut

#8 Post by Dougal »

Ok, I figured it out:
orinoco_cs is a PCMCIA plugin! Thus it gets loaded automatically by cardmgr.
To prevent it from loading you could disable running cardmgr (disble pcmcia) or you could look in /etc/pcmcia, find where orinoco_cs is listed and comment it out.
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

svaens
Posts: 46
Joined: Mon 13 Aug 2007, 15:02

i'm back!

#9 Post by svaens »

Hi Dougal, and Kal, and others who have been perplexed by my troubles.

Dougal, you were right!! Thanks (so far ;))
The 'config' file at the path "etc/pcmcia" contained binding instructions for the orinoco_cs module to various wireless interfaces (including mine). I commented mine out, like this:

#card "Intersil PRISM2 11 Mbps Wireless Adapter"
# manfid 0x0156, 0x0002
# bind "orinoco_cs"

The orinoco_cs was no longer loaded! Yay!

However, now the search for another module that completely supports my wireless mini pci card begins. I wrongly thought this would be the easy part!


Here is the list of modules I have tried (just to get my eth 1) interface showing up again, as it at least did for orinoco_cs. None of these even allow me to configure the interface.

ndiswrapper with 2 recent versions of the windows driver that actually work for me in windows.

hostap_cs
hostap_pci
hostap_plx

prism2_pci
prism2_plx
prism54

orinoco_pci
orinoco_plx
lpw3945

Again, my card is internal (not pcmai).
Toshiba Wireless LAN Mini PCI Card

and i have been using the windows drivers (succesfully) on windows:


Agere Systems
22/09/2003
7.82.0.550

This is unfortunately the latest driver that seems to be available, as, Agere systems has been bought out by some other company, and Toshiba doesn't seem to provide driver updates for this thing... even in windows... never mind linux. To be honest, it IS an old card. but still. I would like to be able to avoid buying new hardware to suit an operating system.

For fear of sounding like a whimp, i hate to cry 'help', but......
help!!!!

jonyo

#10 Post by jonyo »

If no luck, or you get fed up, easiest solution is a usb wifi dongle. Then you can also easily wifi any 'pute (that is usb capable) with pup. Perhaps a pcmcia card might be preferable for a lap.

Stuff that's known to work takes a few minutes to sort out.

User avatar
Dougal
Posts: 2502
Joined: Wed 19 Oct 2005, 13:06
Location: Hell more grotesque than any medieval woodcut

Re: i'm back!

#11 Post by Dougal »

svaens wrote:Again, my card is internal (not pcmai).
Toshiba Wireless LAN Mini PCI Card
You could try googling and see if you find anything.
You could try the Windows driver with Ndiswrapper.

What I don't understand is why cardmgr is loadign the module if it's not a pcmcia device...
What does "elspci -l" show? Maybe it's a pci device and we can find a module for it that way?

BTW, google gave me this:
http://www.murga-linux.com/puppy/viewtopic.php?t=20815
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

svaens
Posts: 46
Joined: Mon 13 Aug 2007, 15:02

#12 Post by svaens »

You are right. I should move my questions back to the other thread. I started this one when I couldn't 'unload' a module, and decided that was another topic.

I have been googling,
and I have tried ndiswrapper.... ndiswrapper did not even provide me with an eth1 interface to configure. And i was using the exact windows driver that i successfully use in windows :(

I will try the elspci -l to see if it provides me with any extra information.
I believe it is a pci device, as it is listed that way "Toshiba Wireless LAN Mini PCI".

But anyway, If I feel the urge to post for further help, I will revert back to the old thread, which is now, more appropriate.

svaens
Posts: 46
Joined: Mon 13 Aug 2007, 15:02

#13 Post by svaens »

since you asked,
here is the output to the elspci -l


# elspci -l
09:00.2 0C0320 1033:00E0 <>
09:00.1 0C0310 1033:0035 <>
09:00.0 0C0310 1033:0035 <>
02:0d.0 088000 1179:0805 <>
02:0b.1 060700 1179:0617 <yenta_cardbus>
02:0b.0 060700 1179:0617 <yenta_cardbus>
02:0a.0 060700 104C:AC50 <yenta_cardbus>
02:08.0 020000 8086:1031 <eepro100>
02:07.0 0C0010 104C:8023 <>
01:00.0 030000 10DE:0175 <>
00:1f.6 070300 8086:2486 <>
00:1f.5 040100 8086:2485 <Intel ICH>
00:1f.1 01018A 8086:248A <PIIX_IDE>
00:1f.0 060100 8086:248C <>
00:1e.0 060400 8086:2448 <>
00:1d.1 0C0300 8086:2484 <uhci_hcd>
00:1d.0 0C0300 8086:2482 <uhci_hcd>
00:01.0 060400 8086:1A31 <>
00:00.0 060000 8086:1A30 <agpgart-intel>

Post Reply