Cardbus Atheros 5212 and Dell laptop(s)...

2004-10-20 Thread Eric Schuele
Hello,

I'm having difficulty getting my Atheros 5212 based card to work in 
either of my dell laptops.  The card only has its power LED on for 
about half a second when it is identified by the os (5.3BETA7), then it 
goes off.  dhclient causes the link LED to blink in a very consistent 
manner but it never aquires any info from DHCP server.

'wicontrol -i ath0 -l' shows the correct wireless nets in the immediate 
area.  'ifconfig' shows correct info.  My entire dmesg is appended to 
the bottom of this message.

The card behaves the same on both my dell 5100 and my dell 1100.  
Thought maybe it was a bad card so I returned it and picked up another 
(same make and model)... but it behaves exactly the same.  Its a Blitzz 
BWP 712 Super G (Atheros 5212)... wal-mart special.  It behaves as 
described wether its inserted before I boot... or after it boots and 
I'm logged in.

I have
  device ath
  device ath_hal
  device wlan

I have a dhclient.conf with something to the effect of:
  media ssid wLAN_SSID channel 1 weptxkey 1 wepmode on wepkey 
0x35CE7F608436C02D11583BDB7F3;

Other (maybe unimportant) things:
ACPI is on... APM is off.
#option SMP
AGP is on
DRM is on

Tried disabling PC Card support and just leaving Cardbus support... no 
go.  I suspect I have something misconfigured with respect to the 
pcmcia slot... but that's just a guess.

Any/All help is appreciated.
-- 
Regards,
Eric

dmesg follows:
==
Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
 The Regents of the University of California. All rights reserved.
FreeBSD 5.3-BETA7 #8: Tue Oct 19 08:29:06 CDT 2004
    [EMAIL PROTECTED]:/usr/obj/usr/src/sys/INSPIRON5100
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz (2657.82-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0xf29  Stepping = 9
  
Features=0xbfebf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
real memory  = 536645632 (511 MB)
avail memory = 515461120 (491 MB)
npx0: [FAST]
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: DELL CPi R   on motherboard
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0
cpu0: ACPI CPU on acpi0
acpi_tz0: Thermal Zone on acpi0
acpi_acad0: AC Adapter on acpi0
acpi_cmbat0: Control Method Battery on acpi0
acpi_lid0: Control Method Lid Switch on acpi0
acpi_button0: Power Button on acpi0
acpi_button1: Sleep Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
ACPI link \\_SB_.PCI0.LNKB has invalid initial irq 11, ignoring
pci0: ACPI PCI bus on pcib0
agp0: Intel 82845G host to AGP bridge mem 0xe000-0xe7ff at 
device 0.0 on pci0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
drm0: ATI Radeon LW Mobility 7500 M7 port 0xc000-0xc0ff mem 
0xfcff-0xfcff,0xe800-0xefff irq 11 at device 0.0 on 
pci1
info: [drm] AGP at 0xe000 128MB
info: [drm] Initialized radeon 1.11.0 20020828 on minor 0
uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xbf80-0xbf9f 
irq 11 at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0xbf40-0xbf5f 
irq 11 at device 29.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0xbf20-0xbf3f 
irq 11 at device 29.2 on pci0
uhci2: [GIANT-LOCKED]
usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
pci0: serial bus, USB at device 29.7 (no driver attached)
pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0
pci2: ACPI PCI bus on pcib2
bfe0: Broadcom BCM4401 Fast Ethernet mem 0xfaffe000-0xfaff irq 5 
at device 1.0 on pci2
miibus0: MII bus on bfe0
bmtphy0: BCM4401 10/100baseTX PHY on miibus0
bmtphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
bfe0: Ethernet address: 00:0d:56:b4:f1:50
bfe0: [GIANT-LOCKED]
ndis0: Dell TrueMobile 1300 WLAN Mini-PCI Card mem 
0xfaffc000-0xfaffdfff irq 11 at device 2.0 on pci2
ndis0: NDIS API version: 5.0
ndis0: Ethernet address: 00:90:4b:69:39:7c
ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 36Mbps 48Mbps 54Mbps
cbb0: TI4510 PCI-CardBus Bridge at device 4.0 on pci2
cardbus0: CardBus bus on cbb0
pccard0: 16-bit PCCard bus on cbb0
fwohci0: 1394 Open Host Controller Interface mem 
0xfaff4000-0xfaff7fff,0xfaffb800-0xfaffbfff irq 11 at device 4.1 on 

Re: Cardbus Atheros 5212 and Dell laptop(s)...

2004-10-20 Thread Andrew L. Gould
On Wednesday 20 October 2004 10:58 am, Eric Schuele wrote:
 On Wednesday 20 October 2004 10:22 am, Eric Schuele wrote:
  Hello,
 
  I'm having difficulty getting my Atheros 5212 based card to work in
  either of my dell laptops.  The card only has its power LED on for
  about half a second when it is identified by the os (5.3BETA7),
  then it goes off.  dhclient causes the link LED to blink in a very
  consistent manner but it never aquires any info from DHCP server.

 I should also note that it will not associate with any WAP even when
 I force all settings (IP address, wepkey, etc..)...

 Thanks,

When I moved to FreeBSD 5*, I found that I had to remove certain 
wireless configuration options that worked in FreeBSD 4*.  That was 
with a wi device; but the later configuration works well with my new 
atheros devices.

I'm using the following atheros products successfully:

D-Link DWL-G520 (pci in a generic desktop running FreeBSD 5.3RC1)
D-Link DWL-G650 (pccard in a Dell Inspiron 8100 running FreeBSD 5.2.1)

FYI:  D-Link is displaying the Atheros logo on the retail boxes of its 
atheros chipset products; which should make purchasing these easier.

I use the script below, with a real wep code and different IP addresses, 
for each of these devices.  Other than setting hostname info 
in /etc/rc.conf and /etc/hosts, I haven't edited any other network 
configuration files.

(Beware the effects of email wordwrap.)


#!/bin/sh
# /usr/local/etc/rc.d/ath0

NIC=ath0

case $1 in
start)
ifconfig ${NIC} inet 192.168.42.21 netmask 255.255.255.0 ssid datawok  
wepmode on wepkey 0x11 
route add default 192.168.42.1
echo search cablelynx.com  /etc/resolv.conf
echo nameserver 24.204.0.4  /etc/resolv.conf
echo nameserver 24.204.0.5  /etc/resolv.conf
echo ${NIC}
;;
dyn)
ifconfig ${NIC} ssid datawok wepmode on wepkey 0x11
dhclient ${NIC}
echo ${NIC}
;;
stop)
[ -s /var/run/dhclient.pid ]  kill `cat /var/run/dhclient.pid`   
rm /var/run/dhclient.pid 
ifconfig ${NIC} remove
echo  ${NIC} removed
;;
status)
ifconfig ${NIC}
;;
*)
echo usage: /usr/local/etc/${NIC} [start|dyn|stop|status]
;;
esac

##end of script

Best of luck,

Andrew Gould
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Cardbus Atheros 5212 and Dell laptop(s)...

2004-10-20 Thread Andrew L. Gould
On Wednesday 20 October 2004 01:38 pm, scott renna wrote:
 Andrew,

 Just saw your post and was wondering how you were able
 to get the Dlink-G520 to work.  I'm running 5.2.1
 currently and tried to add additional devices into my
 kernel according to a post I found on the subject:

 they mention to add:

 device  ath_hal # Dlink Support
 device  hal # Dlink card support

 and recompile the kernel however my 5.2 says it
 doesn't know what hal is.  have you gotten that dlink
 to work on 5.2.1 or just 5.3?

 -scott


Replace device  hal with device  ath.:-)

Dr. Seuss  could have had such fun with a kernel config file!

Also, if you comment out unused hardware devices, make sure you didn't 
comment out device  wlan.  (yep, this is the mistake I made.)

Best of luck,

Andrew Gould
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Cardbus Atheros 5212 and Dell laptop(s)...

2004-10-20 Thread Eric Schuele
On Wednesday 20 October 2004 11:47 am, Andrew L. Gould wrote:
 I'm using the following atheros products successfully:

 D-Link DWL-G520 (pci in a generic desktop running FreeBSD 5.3RC1)
 D-Link DWL-G650 (pccard in a Dell Inspiron 8100 running FreeBSD
 5.2.1)

I went out a grabbed a DWL-G650.  It needed a little encouragement, but 
not much.  It began _trying_ to associate immediately.. but kept flip 
flopping from b/g/b/g... so I forced it to g and it works fine.  Not 
sure what was up with the Blitzz cards.  They have the same chipset.


 FYI:  D-Link is displaying the Atheros logo on the retail boxes of
 its atheros chipset products; which should make purchasing these
 easier.

 I use the script below, with a real wep code and different IP
 addresses, for each of these devices.  Other than setting hostname
 info in /etc/rc.conf and /etc/hosts, I haven't edited any other
 network configuration files.

 (Beware the effects of email wordwrap.)


I have not tried the script yet, but would like to.  I'm still a bit new 
to BSD/*nix  How does it work?  Its under the rc.d folder so it 
runs automagically right.  Who/what provides the parameter you switch 
on? and under what circumstances would each case get executed?


 #!/bin/sh
 # /usr/local/etc/rc.d/ath0

 NIC=ath0

 case $1 in
 start)
  ifconfig ${NIC} inet 192.168.42.21 netmask 255.255.255.0 ssid
 datawok wepmode on wepkey 0x11
 

Thanks for the help!
-- 
Regards,
Eric
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Cardbus Atheros 5212 and Dell laptop(s)...

2004-10-20 Thread Andrew L. Gould
On Wednesday 20 October 2004 09:33 pm, Eric Schuele wrote:
 On Wednesday 20 October 2004 11:47 am, Andrew L. Gould wrote:
  I'm using the following atheros products successfully:
 
  D-Link DWL-G520 (pci in a generic desktop running FreeBSD 5.3RC1)
  D-Link DWL-G650 (pccard in a Dell Inspiron 8100 running FreeBSD
  5.2.1)

 I went out a grabbed a DWL-G650.  It needed a little encouragement,
 but not much.  It began _trying_ to associate immediately.. but kept
 flip flopping from b/g/b/g... so I forced it to g and it works fine. 
 Not sure what was up with the Blitzz cards.  They have the same
 chipset.

  FYI:  D-Link is displaying the Atheros logo on the retail boxes of
  its atheros chipset products; which should make purchasing these
  easier.
 
  I use the script below, with a real wep code and different IP
  addresses, for each of these devices.  Other than setting hostname
  info in /etc/rc.conf and /etc/hosts, I haven't edited any other
  network configuration files.
 
  (Beware the effects of email wordwrap.)

 I have not tried the script yet, but would like to.  I'm still a bit
 new to BSD/*nix  How does it work?  Its under the rc.d folder so
 it runs automagically right.  Who/what provides the parameter you
 switch on? and under what circumstances would each case get executed?

/snip/

 Thanks for the help!

I put the script under /usr/local/etc/rc.d/.  FreeBSD will attempt to 
execute any file in that directory that ends with .sh during bootup and 
shutdown.  During bootup, it will execute the file with the argument 
start.  During shutdown, it will execute the file with the argument 
stop.

In the script's current state, ath0 is configured at bootup with a 
static IP address.  To use dhcp after bootup, root would have to 
execute the following commands:

/usr/local/etc/rc.d/ath0 stop
/usr/local/etc/rc.d/ath0 dyn

The first command would undo the static IP configuration.  The second 
command would execute dhclient per the dyn section of the script.

If you wanted to use dhcp at bootup, you would have to change start) 
to something else; and then change dyn) to start).

Please note that if your using the script for a pccard, the card needs 
to be inserted prior to bootup for configuration to occur 
automatically.  If not, /usr/local/etc/rc.d/ath0 start would need to 
be executed manually after bootup.

I hope this helps.

Andrew Gould
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]