Lan Barnes wrote:
On Sun, January 7, 2007 9:47 am, Gus Wirth wrote:
Without knowing the make and model of your wireless card and the output
of lspci, I can't tell you which is the correct module for the wireless
card. Why are you making it hard to help you?
Sorry. Not trying to be unresponsive. I have a lot of distractions (I'm
watching the AFC game) and I'm trying to poke around and solve things
myself.
I pulled the card: it is a D-Link DWL-520 Rev B1
This is an old 802.11b card. I'd be surprised if you can get enough
bandwidth from this to properly stream MythTV. You need at least 7Mbps
sustained for proper streaming, and the supposed 11Mbps for 802.11b is
mostly wishful thinking. But the only way to find out for sure is to
test it.
The seemingly pertinent line from lspci is (retyped)
00:06.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset
(rev 01)
OK, that matches the make and model for the card, which is a good thing.
Apparently later versions of the card lie. See
<http://www.seattlewireless.net/index.cgi/DlinkCard> for some information.
HTH
There are several modules for Prism chipsets depending on which variant
you have. The original orinoco driver was for PCMCIA (laptop) wireless
cards which have a Prism 2 chipset. After awhile, some manufactures
adapted the PCMCIA card onto a PCI card that fit in a desktop
motherboard. Some of those cards also use the orinoco driver. However, a
follow on variant stripped off the PCMCIA stuff and went with a straight
PCI bus connection. The chipset is a Prism 2.5/3 and uses the
orinoco-pci module. Then there are the later versions which use the
prism54 module.
So maybe the orinoco is correct.
The module you need is the orinoco-pci, NOT the plain orinoco. Notice
the PCI suffix. It DOES make a difference!
Now on to other stuff.
You need to check some configuration items. Look at /etc/modprobe.conf
You should see a line like:
alias eth1 orinoco-pci
where eth1 is the actual interface for the wireless card.
This helps to ensure that when network interface eth1 comes up the
module is loaded. It happens through script magic with Fedora's ifup
which gets called in the /etc/rc.d/network service script. The module
should actually load on startup due to udev magic.
It might be best to change the ONBOOT parameter in the ifcfg-eth1 file
to be "no" so that you can run ifup manually to monitor for any error
messages.
You may also run into the Random Ethernet Assignment Problem (REAP - I
just made this up). For some reason, when udev iterates through the
devices it randomly assigns eth0 to one ethernet device and eth1 to the
other. I haven't been able to predict this and I think it has to do with
kernel timing issues at initialization. There are a couple ways around
it but this is what I do. I blacklist the ethernet modules and make them
load only when the network starts. To do that, edit
/etc/modprobe.d/blacklist You will see a bunch of lines blacklisting
certain modules. At the bottom of the file add your own line
blacklisting the ethernet modules. Something like this (Note: this is
for Fedora, Debian style is different):
# Realtek 10/100 card
blacklist r8139
# D-Link DWL-520
blacklist orinoco-pci
This way the modules won't load until you activate the interface. If you
are really sure you don't want the wired interface you can blacklist its
module and just get rid of all references to it. Then the wireless
interface will become eth0.
Gus
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
