[gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot)

[gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot)

[Mark Knecht]

Hi,
   I've been upgrading a couple of machines. Things are going fairly
well but there have been a few problems. This one I need to work out
first.

1) My son's machine was rebuilt with gcc-4 following the upgrade
guide. Everything went well and it finished up yesterday afternoon.
Since I use ndiswrapper on that machine I rebuilt the kernel with
gcc-4 and I rebooted with the new kernel and new drivers. Everything
worked great including wireless, MythTV frontend, Aqualung, etc.

2) This morning I cold booted and everything worked. I did an eix-sync
and had a couple of things to build so I did that. One of them was new
a udev package. Coldplug was removed from the machine.

3) I *think* I warm booted at this point and things still worked but
I'm not positive on that. However I then booted the machine into
Windows to check that it was still there for games, and then warm
booted back into Gentoo. At this point wireless was completely gone. I
tried cold booting but that didn't help so I don't think running
Windows made any real difference.

a) /etc/init.d/net.wlan0 stays it's stopped. If I try to start wlan0
I'm told it doesn't exist.

b) I have the link from net.wlan0 to net.lo.

c) I rebuilt ndiswrapper and it loads. ndiswrapper -l tells me that
the driver is loaded and the device is present.

d) All the basic stuff like route doesn't see the interface, as
expected I guess.

   Where might I look for what's gone wrong?

   As an aside, the Gentoo kernels remove support for stack size
changes so ndiswrapper complains about the kernel when it's emerged.
Is there a patch to get an 8K stack size option back again? Why does
anyone remove this in the first place instead of just setting it to a
sane default?

   Sorry I Cannot send any info from the box but it's off the net.

Thanks in advance,
Mark
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot)

[Mick]

[-- Attachment #1: Type: text/plain, Size: 2069 bytes --]

On Saturday 25 November 2006 20:29, Mark Knecht wrote:
> Hi,
>    I've been upgrading a couple of machines. Things are going fairly
> well but there have been a few problems. This one I need to work out
> first.
>
> 1) My son's machine was rebuilt with gcc-4 following the upgrade
> guide. Everything went well and it finished up yesterday afternoon.
> Since I use ndiswrapper on that machine I rebuilt the kernel with
> gcc-4 and I rebooted with the new kernel and new drivers. Everything
> worked great including wireless, MythTV frontend, Aqualung, etc.
>
> 2) This morning I cold booted and everything worked. I did an eix-sync
> and had a couple of things to build so I did that. One of them was new
> a udev package. Coldplug was removed from the machine.
>
> 3) I *think* I warm booted at this point and things still worked but
> I'm not positive on that. However I then booted the machine into
> Windows to check that it was still there for games, and then warm
> booted back into Gentoo. At this point wireless was completely gone. I
> tried cold booting but that didn't help so I don't think running
> Windows made any real difference.
>
> a) /etc/init.d/net.wlan0 stays it's stopped. If I try to start wlan0
> I'm told it doesn't exist.
>
> b) I have the link from net.wlan0 to net.lo.
>
> c) I rebuilt ndiswrapper and it loads. ndiswrapper -l tells me that
> the driver is loaded and the device is present.
>
> d) All the basic stuff like route doesn't see the interface, as
> expected I guess.
>
>    Where might I look for what's gone wrong?
>
>    As an aside, the Gentoo kernels remove support for stack size
> changes so ndiswrapper complains about the kernel when it's emerged.
> Is there a patch to get an 8K stack size option back again? Why does
> anyone remove this in the first place instead of just setting it to a
> sane default?
>
>    Sorry I Cannot send any info from the box but it's off the net.

In case you haven't, remerge/modprobe the module for the wifi card.

HTH.
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot)

[Mark Knecht]

On 11/25/06, Mick <michaelkintzios@gmail.com> wrote:
<SNIP>
>
> In case you haven't, remerge/modprobe the module for the wifi card.
>
> HTH.
> --
> Regards,
> Mick

Mick,
   Unless I'm mistaken, that module is ndiswrapper which was emerged
again after the kernel was rebuilt.

   In case you're not familiar with it ndiswrapper wraps around a
Windows driver that talks to the hardware. It's an interface between
the Linux driver stack and the hardware running a Windows driver.
There is no apparent native support for these wireless NICs in Linux
unfortunately so I'm forced to use ndiswrapper which worked OK under
gcc-3.4.6.

   If I'm mistaken about the above description I'm happy to be informed.

Thanks,
Mark
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot)

[Sergio Polini]

Mark Knecht:
>    Unless I'm mistaken, that module is ndiswrapper which was
> emerged again after the kernel was rebuilt.

Was ndiswrapper emerged *and updated*?
My card name is Broadcom BCM4310 UART, my gcc is 4.1.1, my udev is 
087-r1. I have to use ndiswrapper 1.23 because more recent versions 
do not work.
HTH
Sergio
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot)

[Mark Knecht]

On 11/25/06, Sergio Polini <sp_rm_it@yahoo.it> wrote:
> Mark Knecht:
> >    Unless I'm mistaken, that module is ndiswrapper which was
> > emerged again after the kernel was rebuilt.
>
> Was ndiswrapper emerged *and updated*?
> My card name is Broadcom BCM4310 UART, my gcc is 4.1.1, my udev is
> 087-r1. I have to use ndiswrapper 1.23 because more recent versions
> do not work.
> HTH
> Sergio
> --

Sergio,
   Hi and thanks very much for responding. My apologies in advance for
the length of this post. Lots of info.

   In my case ndiswrapper was not updated. Before the upgrade and
after I was using 1.2-r1. It worked yesterday but fails today. I am
currently on the offending machine but using a wired interface with
the cable stretched across the house so that I can give real results.

   Following along in the spirit of your response I don't even see
version 1.23 so I've tried installing  the newest masked version, even
though I expect this failed on your machine:

Sector9 ~ # eix -I ndiswrapper
* net-wireless/ndiswrapper
     Available versions:  1.2-r1 1.25 1.26 1.28 1.29
     Installed:           1.29
     Homepage:            http://ndiswrapper.sourceforge.net/
     Description:         Wrapper for using Windows drivers for some
wireless cards

Sector9 ~ #

>From dmesg you can see the effects of loading each driver, one at a
time - not both together. I'm just posting both below to show the
difference in dmesg:

ndiswrapper version 1.2 loaded (preempt=yes,smp=no)

or...

ndiswrapper version 1.29 loaded (preempt=yes,smp=no)
usbcore: registered new driver ndiswrapper

(the second message was because there is a new usb USE flag. I turned
that off and I then do not get the second message when loading, but
the driver still doesn't work for me yet.)

They load slightly differently. Maybe part of the problem is the
changes in udev and the removal of hotplug and coldplug? Could that be
involved? I am now using the newest udev. Maybe that's part of the
problem?

The newest 1.29 version of the driver shows this when I run
ndiswrapper from the command line to install the Windows driver:

Sector9 ~ # ndiswrapper -i 802.11g/NetA3AB.inf
installing neta3ab ...
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
Sector9 ~ #

I don't like those messages. They don't happen with the older version 1.2-r1.

After modprobing ndiswrapper dmesg says it's loaded as does lsmod.
There are no error messages. However when I try to start the interface
it fails:

Sector9 ~ # /etc/init.d/net.wlan0 start
 * Starting wlan0
 *   Bringing up wlan0
 *     192.168.1.159/24
 *     network interface wlan0 does not exist
 *     Please verify hardware or kernel module (driver)                   [ !! ]
Sector9 ~ #

So it seems to be unhappy with the way the driver is working. That
said there is no difference in this output for 1.2-r1 and 1.29

>From the command line it appears that the newest version of
ndiswrapper is suggesting I can now use a Linux driver. I have no idea
how to actually do that though.

Sector9 ~ # ndiswrapper -l
installed drivers:
neta3ab         driver installed, hardware (168C:001A) present
(alternate driver: ath_pci)
Sector9 ~ #

I do have the ath_pci driver and I can modprobe it successfully:

Sector9 ~ # modprobe ath_pci
Sector9 ~ # lsmod
Module                  Size  Used by
<SNIP>
ath_pci                72800  0
ath_rate_sample        10880  1 ath_pci
<SNIP>
ath_hal               189264  3 ath_pci,ath_rate_sample
<SNIP>Sector9 ~ #

I don't see any errors in dmesg, or even any messages.

Since I cannot get ndiswrapper working how would I go about getting
ath_pci to work?

Sorry this got so long.

Thanks again,
Mark
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot)

[Stroller]

On 26 Nov 2006, at 02:01, Mark Knecht wrote:
> ...
> I do have the ath_pci driver and I can modprobe it successfully:
>
> Sector9 ~ # modprobe ath_pci
> Sector9 ~ # lsmod
> Module                  Size  Used by
> <SNIP>
> ath_pci                72800  0
> ath_rate_sample        10880  1 ath_pci
> <SNIP>
> ath_hal               189264  3 ath_pci,ath_rate_sample
> <SNIP>Sector9 ~ #
>
> I don't see any errors in dmesg, or even any messages.
>
> Since I cannot get ndiswrapper working how would I go about getting
> ath_pci to work?

What card do you actually have? IMO NDISwrapper is a last resort for  
cards that have no native support & for users who cannot afford a  
supported card. You should certainly be using madwifi or madwifi-ng  
(the driver which provides ath_pci, IIRC) if your card supports it.

What does `lspic -vt` say?
What does `iwconfig` say?

Stroller.



PS: please cc me on your reply. The pop-server which receives my  
mailing list messages seems to be on a go-slow ATM.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot)

[Sergio Polini]

Mark Knecht:
>    Following along in the spirit of your response I don't even see
> version 1.23 so I've tried installing  the newest masked version,
> even though I expect this failed on your machine:
>
> Sector9 ~ # eix -I ndiswrapper
> * net-wireless/ndiswrapper
>      Available versions:  1.2-r1 1.25 1.26 1.28 1.29
>      Installed:           1.29
>      Homepage:            http://ndiswrapper.sourceforge.net/
>      Description:         Wrapper for using Windows drivers for
> some wireless cards

This is why I now keep two Gentoo root partitions, "stable" 
and "testing": in "stable" there is a fully working system, 
in "testing" I.... update and look at what happens ;-)

> From the command line it appears that the newest version of
> ndiswrapper is suggesting I can now use a Linux driver. I have no
> idea how to actually do that though.
>
> Sector9 ~ # ndiswrapper -l
> installed drivers:
> neta3ab         driver installed, hardware (168C:001A) present
> (alternate driver: ath_pci)
> Sector9 ~ #
> [....]
> Since I cannot get ndiswrapper working how would I go about getting
> ath_pci to work?

I'd check Stroller's advice ;-)
You could also look at:
http://gentoo-wiki.com/HARDWARE_Wireless
http://gentoo-wiki.com/Index:Hardware#Wireless
http://ndiswrapper.sourceforge.net/mediawiki/index.php/List

Sergio
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot)

[Mark Knecht]

On 11/25/06, Stroller <stroller@stellar.eclipse.co.uk> wrote:
>
> On 26 Nov 2006, at 02:01, Mark Knecht wrote:
> > ...
> > I do have the ath_pci driver and I can modprobe it successfully:
> >
> > Sector9 ~ # modprobe ath_pci
> > Sector9 ~ # lsmod
> > Module                  Size  Used by
> > <SNIP>
> > ath_pci                72800  0
> > ath_rate_sample        10880  1 ath_pci
> > <SNIP>
> > ath_hal               189264  3 ath_pci,ath_rate_sample
> > <SNIP>Sector9 ~ #
> >
> > I don't see any errors in dmesg, or even any messages.
> >
> > Since I cannot get ndiswrapper working how would I go about getting
> > ath_pci to work?
>
> What card do you actually have? IMO NDISwrapper is a last resort for
> cards that have no native support & for users who cannot afford a
> supported card.

I completely agree.

> You should certainly be using madwifi or madwifi-ng
> (the driver which provides ath_pci, IIRC) if your card supports it.
>
> What does `lspic -vt` say?

I assume you meant lspci:

Sector9 ~ # lspci -vt
-[0000:00]-+-00.0  nVidia Corporation C51 Host Bridge
           +-00.1  nVidia Corporation C51 Memory Controller 0
           +-00.2  nVidia Corporation C51 Memory Controller 1
           +-00.3  nVidia Corporation C51 Memory Controller 5
           +-00.4  nVidia Corporation C51 Memory Controller 4
           +-00.5  nVidia Corporation C51 Host Bridge
           +-00.6  nVidia Corporation C51 Memory Controller 3
           +-00.7  nVidia Corporation C51 Memory Controller 2
           +-02.0-[0000:01]--
           +-04.0-[0000:02]--
           +-05.0  nVidia Corporation C51 PCI Express Bridge
           +-09.0  nVidia Corporation MCP51 Host Bridge
           +-0a.0  nVidia Corporation MCP51 LPC Bridge
           +-0a.1  nVidia Corporation MCP51 SMBus
           +-0a.2  nVidia Corporation MCP51 Memory Controller 0
           +-0b.0  nVidia Corporation MCP51 USB Controller
           +-0b.1  nVidia Corporation MCP51 USB Controller
           +-0d.0  nVidia Corporation MCP51 IDE
           +-0e.0  nVidia Corporation MCP51 Serial ATA Controller
           +-0f.0  nVidia Corporation MCP51 Serial ATA Controller
           +-10.0-[0000:03]--+-08.0  Lite-On Communications Inc LNE100TX
           |                 \-0a.0  Atheros Communications, Inc.
AR5005G 802.11abg NIC
           +-10.1  nVidia Corporation MCP51 High Definition Audio
           +-14.0  nVidia Corporation MCP51 Ethernet Controller
           +-18.0  Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
           +-18.1  Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Address Map
           +-18.2  Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
DRAM Controller
           \-18.3  Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control
Sector9 ~ #


> What does `iwconfig` say?
>

Actually, this is interesting and (so far) unexplained. I did not
intentionally ask the system to load ath_pci but it has done that. It
appears that ath_pci may have grabbed to hardware and hence stopped
ndiswrapper from using the card? No wonder I'm told that wlan0 doesn't
exist!

Sector9 ~ # iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

eth1      no wireless extensions.

wifi0     no wireless extensions.

ath0      IEEE 802.11b  ESSID:""
          Mode:Managed  Channel:0  Access Point: Not-Associated
          Bit Rate:0 kb/s   Tx-Power:0 dBm   Sensitivity=0/3
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/94  Signal level=-95 dBm  Noise level=-95 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Sector9 ~ #

So, then I have two questions:

1) What is the proper way to configure this card using ath0, assuming
it actually is supported?

2) If the above data is about my card then why isn't is coming up
802.11g? I get .11g support from ndiswrapper, or did when it
worked...)

I do have madwifi installed but I'm not intentionally trying to run
it, as far as I know:

Sector9 ~ # eix -I madwifi
* net-wireless/madwifi-ng
     Available versions:  0.0.1443.20060207 0.0.1531.20060427 0.9.2
     Installed:           0.9.2
     Homepage:            http://www.madwifi.org/
     Description:         Next Generation driver for Atheros based
IEEE 802.11a/b/g wireless LAN cards

* net-wireless/madwifi-ng-tools
     Available versions:  0.0.1443.20060207 0.0.1531.20060427 ~0.9.1
~0.9.2_rc1692 0.9.2
     Installed:           0.9.2
     Homepage:            http://www.madwifi.org/
     Description:         Next Generation tools for configuration of
Atheros based IEEE 802.11a/b/g wireless LAN cards

Found 2 matches.
Sector9 ~ #

Sector9 ~ # rc-update show
           alsasound |      default
            bootmisc | boot
             checkfs | boot
           checkroot | boot
               clock | boot
         consolefont | boot
               cupsd |      default
            hostname | boot
             hotplug |      default
             keymaps | boot
               local |      default nonetwork
          localmount | boot
             modules | boot
              net.lo | boot
           net.wlan0 |      default
            netmount |      default
                ntpd |      default
           rmnologin | boot
                sshd |      default
           syslog-ng |      default
             urandom | boot
          vixie-cron |      default
                 xdm |      default
Sector9 ~ # cat /etc/modules.autoload.d/kernel-2.6
# /etc/modules.autoload.d/kernel-2.6:  kernel modules to load when system boots.
#
# Note that this file is for 2.6 kernels.
#
# Add the names of modules that you'd like to load when the system
# starts into this file, one per line.  Comments begin with # and
# are ignored.  Read man modules.autoload for additional details.

# For example:
# 3c59x
#forcedeth
ndiswrapper
agpgart
nvidia-agp
#tulip
Sector9 ~ #



Thanks,
Mark
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot)

[Stroller]

On 26 Nov 2006, at 19:01, Mark Knecht wrote:
>> ...
>> What does `lspic -vt` say?
>
> I assume you meant lspci:
>
> Sector9 ~ # lspci -vt
> ...
>           |                 \-0a.0  Atheros Communications, Inc.
> AR5005G 802.11abg NIC

This should be supported by madwifi-ng, although from the comments at  
<http://madwifi.org/wiki/Compatibility#AtherosAR5005G> you might try  
emerging 0.0.1443.20060207 or 0.0.1531.20060427 if you have problems  
with the current release.

>> What does `iwconfig` say?
>>
>
> Actually, this is interesting and (so far) unexplained. I did not
> intentionally ask the system to load ath_pci but it has done that.

I'm pretty sure that udev / coldplug is _supposed_ to do stuff like  
that these days.

> It
> appears that ath_pci may have grabbed to hardware and hence stopped
> ndiswrapper from using the card?

Quite possibly so, although I wouldn't rely on NDISwrapper at all  
(myself - I have never tried it).

> Sector9 ~ # iwconfig
> ...
> ath0      IEEE 802.11b  ESSID:""
>          Mode:Managed  Channel:0  Access Point: Not-Associated

This is fairly clearly the madwifi driver. Did you emerge it some  
time in the past, or is it part of the main kernel tree these days?

> 1) What is the proper way to configure this card using ath0, assuming
> it actually is supported?

`iwconfig ath0 SSID "Linksys" channel auto key aabbccddeeff &&  
ifconfig ath0 up && dhclient ath0` might be a start.

/etc/conf.d/net contains lots of hints for a proper installation. You  
might need to `ln -s /etc/init.d/net.lo /etc/init.d/net.ath0`.

> 2) If the above data is about my card then why isn't is coming up
> 802.11g? I get .11g support from ndiswrapper, or did when it
> worked...)

Well, do you have it configured _as ath0_? If you have your wlan0 in  
all your configuration files then the init scripts are ignoring it.  
Assuming that dhcp is clever enough to run on interfaces that aren't  
mentioned in /etc/conf.d/net, the SSID & WEP key need to be set  
first. You need to have `essid_ath0="Linksys"',  
`key_NedNet="aabbccddeeff"' in /etc/conf.d/net.

Also, you might want to try different versions of the madwifi-ng  
driver due to the mentioned problems with that particular card.  
These'll surely be sorted out in 0.9.3 or 1.0.0, so there's no need  
to stress it - if you can't get ath0 working using `iwconfig` &  
`ifconfig` then just package mask 0.9.2 and try an earlier version.

Stroller.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] wlan0/ndiswrapper failing after gcc-4 upgrade (and dual Windows boot)

[Mark Knecht]

Hi Stroller.
   Thanks in advance!

On 11/26/06, Stroller <stroller@stellar.eclipse.co.uk> wrote:
>
<SNIP>
>
> This should be supported by madwifi-ng, although from the comments at
> <http://madwifi.org/wiki/Compatibility#AtherosAR5005G> you might try
> emerging 0.0.1443.20060207 or 0.0.1531.20060427 if you have problems
> with the current release.

OK - currently have 0.9.2 installed. Will try the others if I don't
make headway soon.

<SNIP>
>
> > 1) What is the proper way to configure this card using ath0, assuming
> > it actually is supported?
>
> `iwconfig ath0 SSID "Linksys" channel auto key aabbccddeeff &&
> ifconfig ath0 up && dhclient ath0` might be a start.
>
> /etc/conf.d/net contains lots of hints for a proper installation. You
> might need to `ln -s /etc/init.d/net.lo /etc/init.d/net.ath0`.

Yes. As you were writing back I was doing much the same stuff. I
created the net.ath0 link as well as adding some config data in
/etc/conf.d/wireless and can now start and stop the device:

Sector9 init.d # /etc/init.d/net.ath0 status
 * status:  started
Sector9 init.d # /etc/init.d/net.ath0 stop
 * Stopping ath0
 *   Bringing down ath0
 *     Shutting down ath0 ...
                      [ ok ]Sector9 init.d # /etc/init.d/net.ath0
start
 * Starting ath0
 *   Configuring wireless network for ath0
 *     ath0 connected to ESSID "LadySmithBliss" at 00:00:00:00:00:00
 *     in managed mode on channel 1 (WEP enabled - restricted)
 *   Bringing up ath0
 *     192.168.1.158/24
                      [ ok ] *   Adding routes
 *     default via 192.168.1.1 ...
                      [ ok ]Sector9 init.d #

I am not clear about the 00:00:00:00:00:00 thing. Does that mean it's
bound to any WAP on the network or is it bound to none of them. I'm
not sure how much of this I Can trust, but it is seeing things on the
network. Note that there is a LinkSys wireless router, 2 LinkSys
wireless access points and a Mac Mini that is wireless so it should
see 4 devices, or possibly 3 due to distance issues. Note that at
least one MAC address is duplicated in the list below:

Sector9 init.d # iwlist ath0 scan
ath0      Scan completed :
          Cell 01 - Address: 00:13:10:7D:8F:F9
                    ESSID:""
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Quality=31/94  Signal level=-64 dBm  Noise level=-95 dBm
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:bcn_int=100
          Cell 02 - Address: 00:90:4C:91:00:01
                    ESSID:"REMOVED"
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Quality=48/94  Signal level=-47 dBm  Noise level=-95 dBm
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:bcn_int=100
          Cell 03 - Address: 00:12:17:7A:99:03
                    ESSID:"REMOVED"
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Quality=11/94  Signal level=-84 dBm  Noise level=-95 dBm
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:bcn_int=100
          Cell 04 - Address: 00:13:10:7D:8F:F9
                    ESSID:"REMOVED"
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Quality=29/94  Signal level=-66 dBm  Noise level=-95 dBm
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:bcn_int=100
          Cell 05 - Address: 00:90:4C:91:00:01
                    ESSID:""
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Quality=41/94  Signal level=-54 dBm  Noise level=-95 dBm
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:bcn_int=100

Sector9 init.d #

With ath0 turned on I have a reasonable routing table except for two
'default' interfaces. That goes away when I turn off eth0 for testing,
but it's on now so that I can write this email. How do I set which
interface is the single default if they are both on?

Sector9 init.d # route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
192.168.1.0     *               255.255.255.0   U     0      0        0 ath0
loopback        *               255.0.0.0       U     0      0        0 lo
default         LinkSys         0.0.0.0         UG    0      0        0 eth0
default         LinkSys         0.0.0.0         UG    2000   0        0 ath0
Sector9 init.d #

Sector9 init.d # /etc/init.d/net.eth0 stop
 * Stopping eth0
 *   Bringing down eth0
 *     Shutting down eth0 ...
                      [ ok ]Sector9 init.d # route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 ath0
loopback        *               255.0.0.0       U     0      0        0 lo
default         LinkSys         0.0.0.0         UG    2000   0        0 ath0
Sector9 init.d # ifconfig
ath0      Link encap:Ethernet  HWaddr 00:11:95:88:C7:3A
          inet addr:192.168.1.158  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING 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:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:31 errors:0 dropped:0 overruns:0 frame:0
          TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3125 (3.0 Kb)  TX bytes:3125 (3.0 Kb)

wifi0     Link encap:UNSPEC  HWaddr
00-11-95-88-C7-3A-20-81-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:758243 errors:0 dropped:0 overruns:0 frame:4744
          TX packets:699186 errors:36 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:199
          RX bytes:34432569 (32.8 Mb)  TX bytes:23865464 (22.7 Mb)
          Interrupt:21 Memory:dc980000-dc990000

Sector9 init.d #

>
> > 2) If the above data is about my card then why isn't is coming up
> > 802.11g? I get .11g support from ndiswrapper, or did when it
> > worked...)
>
> Well, do you have it configured _as ath0_? If you have your wlan0 in
> all your configuration files then the init scripts are ignoring it.

No, as I say I have added it to the wireless config file:

Sector9 init.d # cat ../conf.d/wireless
# /etc/conf.d/wireless:
# Global wireless config file for net.* rc-scripts
##############################################################################
# SETTINGS
##############################################################################

essid_wlan0="MYESSID"
preferred_aps=( "MYESSID" )
channel_wlan0="6"
key_MYESSID="MYKEY enc restricted"

essid_ath0="MYESSID"
preferred_aps=( "MYESSID" )
channel_ath0="6"
key_MYESSID="MYKEY enc restricted"
Sector9 init.d #

<SNIP>
>
> Also, you might want to try different versions of the madwifi-ng
> driver due to the mentioned problems with that particular card.
> These'll surely be sorted out in 0.9.3 or 1.0.0, so there's no need
> to stress it - if you can't get ath0 working using `iwconfig` &
> `ifconfig` then just package mask 0.9.2 and try an earlier version.
>

That may be the proper next step but it seems like I'm quite close
with this version.

Any idea what I'm missing?

thanks,
Mark
-- 
gentoo-user@gentoo.org mailing list