Re: WiFi setup & FC2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Timothy,
Thanks very much for your response & help. Hope this isn't too long & detailed, but it just got deeper & deeper... But, some success by the end.


So, the "device" name is a function of the driver (hostap being wlan* &
orinoco being eth*), not the device?

Yes, there's an onboard ethernet device at eth0, but started manually -
not at boot (more on that below).

Here's the output from cardctl ident:
[root@morgansmachine morgan]# /sbin/cardctl ident
Socket 0:
  product info: "Allied Telesyn", "AT-WCL452 Wireless PCMCIA Radio",
"Ver. 1.00", ""
  manfid: 0xc00f, 0x0000
  function: 6 (network)
[root@morgansmachine morgan]#

hostap_cs.conf got renamed to hostap_cs.conf.rpmsave when I uninstalled
it - happy to leave it as this with the addition of the card to
/etc/pcmcia/config (as below in first post with the "bind "orinoco_cs""
included).  I've commented out the line in modprobe.conf as you suggest,
but also in modules.conf hope this is ok too.

Hmm.  Did iwconfig eth0 and expected to get nothing, but got the card...
  So, if I don't start my ethernet as boot, as I don't, and do put in
my card then it'll take eth0 which has been set up for the wired
ethernet.  And, so if I start the ethernet now it'll take eth1?...  Well
actually system-config-network says eth0 not found and then shows it as
active, but I'd expect some weirdness wouldn't I?  And, I can't
deactivate it because it has a different MAC address than expected -
well I expected that, but the machine didn't.  And, if I pop the card
out the system-config-network changes the status to inactive and I've
got control of the wired ethernet device back...

I've actually set up system-config-network for two locations with two
profiles and given my devices meaningful "nicknames".  So, I have ppp0
as Planet (my ISP) and eth0 as HomeWiredEthernet on a profile called
Home and, eth0:1 as UofAWiredEthernet and wlan0 as UofAWireless on a
profile called (surprise) UofA.  This means that
/etc/sysconfig/network-scripts changes depending on what profile I have
active in system-config-network.

Is this going to be as much of a pain as it seems now - can I give an
alias or something to take the card off the "eth*" devices and put it on
the "wlan*" devices?

I created a special profile with only the the wifi card in and after
rebooting (only after rebooting) I can happily report that
system-config-network seems to set up my card properly: the card name
(not driver) is reported in select wireless device; configure wireless
connection doesn't freeze; opperating the Mode dropdown doesn't freeze
the system -

Ahhrrr, it's taken my wired ethernet - turns out, that booting with the card in seems to have somehow deleted the top line of /etc/modprobe.conf - "alias eth0 sis900". I've put it back, rebooted & now I've got my wired ethernet back... Started it, put in the wireless card & set up a wireless device for eth1. So, I've got eth1 & eth0:2 as wireless devices at UofA (depending on whether I've got the wired ethernet up), and eth0 & eth0:1 as wired devices for home & UofA respectively - very messy!

I've copied the out put for iwconfig & ifconfig with things the sensible
way round for your info, also at bottom I've include the last few lines
of /var/log/messages where I've taken the card in and out.

I look forward to any suggestions you may have to getting things in
order.  Thanks again for your help - I was in Dublin this time last
year, fond memories.

Regards,
Morgan.

[root@morgansmachine morgan]# /sbin/ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:90:F5:13:D2:5F
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:406 (406.0 b)
          Interrupt:10 Base address:0x3200

[root@morgansmachine morgan]# /sbin/ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:30:84:1F:AE:F7
          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:3 Base address:0x100

[root@morgansmachine morgan]# /sbin/iwconfig eth1
eth1      IEEE 802.11-DS  ESSID:""  Nickname:"Prism  I"
          Mode:Managed  Access Point: 00:00:00:00:00:00  Bit Rate:11Mb/s
          Tx-Power=15 dBm   Sensitivity:1/3
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0/92  Signal level:-68 dBm  Noise level:-122 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
*******************************************************
Aug 18 22:32:21 localhost kernel: cs: memory probe
0xa0000000-0xa0ffffff: clean.
Aug 18 22:32:21 localhost cardmgr[1367]: socket 0: AT-WCL452
Aug 18 22:38:59 localhost kernel: spurious 8259A interrupt: IRQ7.
Aug 18 22:45:07 localhost cardmgr[1367]: stop cmd exited with status 1
Aug 18 22:45:07 localhost net.agent[3471]: remove event not handled
Aug 18 22:48:42 localhost cardmgr[1367]: socket 0: AT-WCL452
Aug 18 22:55:48 localhost kernel: sis900.c: v1.08.07 11/02/2003
Aug 18 22:55:48 localhost kernel: PCI: Found IRQ 10 for device 0000:00:01.1
Aug 18 22:55:48 localhost kernel: PCI: Sharing IRQ 10 with 0000:00:01.6
Aug 18 22:55:48 localhost kernel: eth1: ICS LAN PHY transceiver found at
address 1.
Aug 18 22:55:48 localhost kernel: eth1: Using transceiver found at
address 1 as default
Aug 18 22:55:48 localhost kernel: eth1: SiS 900 PCI Fast Ethernet at
0x3200, IRQ 10, 00:90:f5:13:d2:5f.
Aug 18 22:56:16 localhost kernel: eth0: error -110 reading info frame.
Frame dropped.
Aug 18 22:56:16 localhost kernel: eth0: Error -110 setting multicast list.
Aug 18 22:56:18 localhost last message repeated 3 times
Aug 18 22:56:19 localhost su(pam_unix)[4109]: session opened for user
root by (uid=0)
Aug 18 22:56:19 localhost su(pam_unix)[4109]: session closed for user root
Aug 18 22:56:19 localhost kernel: hermes @ IO 0x100: Timeout waiting for
command completion.
Aug 18 22:56:19 localhost kernel: hermes @ IO 0x100: Error -16 issuing
command.
Aug 18 22:56:51 localhost last message repeated 417 times
Aug 18 22:57:53 localhost last message repeated 660 times
Aug 18 22:58:54 localhost last message repeated 682 times
Aug 18 22:59:49 localhost last message repeated 615 times
Aug 18 22:59:50 localhost cardmgr[1367]: stop cmd exited with status 1
Aug 18 22:59:50 localhost net.agent[4483]: remove event not handled
Aug 18 23:00:00 localhost kernel: sis900.c: v1.08.07 11/02/2003
Aug 18 23:00:00 localhost kernel: PCI: Found IRQ 10 for device 0000:00:01.1
Aug 18 23:00:00 localhost kernel: PCI: Sharing IRQ 10 with 0000:00:01.6
Aug 18 23:00:00 localhost kernel: eth0: ICS LAN PHY transceiver found at
address 1.
Aug 18 23:00:00 localhost kernel: eth0: Using transceiver found at
address 1 as default
Aug 18 23:00:00 localhost kernel: eth0: SiS 900 PCI Fast Ethernet at
0x3200, IRQ 10, 00:90:f5:13:d2:5f.
Aug 18 23:00:01 localhost kernel: eth0: Media Link Off
Aug 18 23:00:03 localhost su(pam_unix)[4597]: session opened for user
root by (uid=0)
Aug 18 23:00:03 localhost su(pam_unix)[4597]: session closed for user root
Aug 18 23:00:06 localhost su(pam_unix)[4661]: session opened for user
root by (uid=0)
Aug 18 23:00:06 localhost su(pam_unix)[4661]: session closed for user root
Aug 18 23:04:51 localhost cardmgr[1367]: socket 0: AT-WCL452
*******************************************************

Timothy Murphy wrote:
Morgan Read wrote:


I have pcmcia wifi card with a prism 3 chipset - Allied Telesyn
AT-WCL452 (Intersil firmware apparently).

Running fc2 kernel 2.6.6-1.435.2.3

I installed this and confidently re-booted following advice that the
prism chipsets were well supported.

Nothing.

I went through the set-up process in system-config-network but the card
wasn't there:(

I googled and found that the driver de jour for prism was the hostap,
not the orinoco that comes installed.

I installed the 0.1.3 rpm (0.2.4 now stable, but no rpms yet).  And,
followed some configuration info I'd found in various places on the net:
inserted lines -
"alias wlan0 hostap_cs" in /etc/modules.conf
"alias wlan0 hostap_cs" in /etc/modprobe.conf
"card "AT-WCL452"
   version "Allied Telesyn", "AT-WCL452 Wireless PCMCIA Radio", "Ver.
   1.00" manfid 0xc00f, 0x0000
   bind "hostap_cs""
in /etc/pcmcia/hostap_cs.conf

There seemed to be some success (once I'd worked out I needed to
reference hostap_cs rather hostap_pci); iwconfig gave sensible
responses, as did ifconfig.  However, system-config-network seemed to be
playing up and freezing the whole system if I tried to change the mode
form "master" to "managed", and just touching the "Wireless Settings"
tab froze the window.

Then card stopped working altogether.  So, I discovered a bug and fixed
it by placing the start script for pcmcia before the network startup.

The card worked again.  But, it kept wanting to be Master and not
Managed (don't we all).

About then I discovered that Allied Telesyn provide the wlan-ng driver
on their web site, not rpm.  And, it didn't compile:(  I've successfully
compiled a soft-modem driver.  Also, Open1x Xsupplicant from cvs.  But,
this didn't sing.  Any ideas?  Something to do with matched sources?

After a bit more googleing I discovered that the orinoco driver provided
some support for prism.  So, why not put what I've learnt into putting
the systems driver to work: inserted lines -
"alias wlan0 orinoco_cs" in /etc/modules.conf
"alias wlan0 orinoco_cs" in /etc/modprobe.conf
"card "AT-WCL452"
   version "Allied Telesyn", "AT-WCL452 Wireless PCMCIA Radio", "Ver.
   1.00" manfid 0xc00f, 0x0000
   bind "hostap_cs""
in /etc/pcmcia/config

Success, well some...  Seems to give me partially sensible things with
iwconfig and ifconfig, but keeps returning eth1 instead of wlan0?  Then
things started getting very strange - loading orinoco_cs for the
ethernet driver instead of the sis900??  Worked out that if I booted
with out the card in and then inserted it, I got the right driver on the
ethernet?  But, at some point I have AT-WCL452 under the ethernet and
orinoco_cs under wireless!!!  OK, so it wants eth1 not wlan0?  It can
have it!  I changed "alias wlan0 orinoco_cs" (no "" of course) to "alias
eth1 orinoco_cs".  Rebootted, but still the wireless entry in
system-config-network shows wlan0 (where does it get this from!).  And,
the mode option has gone back to Master!  (Of course, it still freezes
up if I use that Wireless Settings tab.)  So, I deleted the wireless
entry in order to set up a new entry.  And what to I get when I go
through the add new device dialogue...  No wireless entry (where once
the driver or card name showed up thought the wireless dialogue)  And!
If I go through the new ethernet dialogue I have the offerings of: "SiS
900/7016 PCI Fast Ethernet (eth0)" as expected AND "orinoco_cs (eth1)"
AND!!! "AT-WCL452 (eth0)!

How grey do I have to get?


I'm not an expert, but firstly the default WiFi drivers in the kernel
use eth*, while the wlan-ng driver (which is not in the kernel) uses wlan*.

It sounds to me as though the kernel orinoco_cs driver worked,
in which case that would be the simplest thing to use.

First run "cardctl ident" to see what the card manager thinks your card is.
(It's not clear if you did this.)
Assuming it is the one you say,
then your file hostap_cs.conf will be used.
(If you look at the end of /etc/pcmcia/config
you will see that it reads all files *.conf in that directory.)
This will determine which driver is used.

Alternatively, if there is an entry for the card in /etc/pcmcia/config
you can just edit that file and give the driver you want.
(That is what I would do, but you'd have to remove your hostap_cs.conf .)
Try giving the driver orinoco_cs there.
I would comment out the alias line you added in modprobe.conf
as it will only confuse matters.

Now put in the card, and run iwconfig eth0 or eth1.
(Why does it use eth1?
Is there an inbuilt eth0 interface?
You could probably tell from /var/log/messages .)

You could try "service pcmcia restart" (as root)
if iwconfig doesn't give a sensible response.

If you get to this stage, you could run "service-config-network"
as you suggest, or equivalently
edit /etc/sysconfig/network-scripts/ifcfg-eth1 .
Also you should look at the settings in /etc/pcmcia/wireless.opts .








-- Morgan Read <mailto:mstuffATplDOTnet>




[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux