Date: Tue, 25 Apr 2000 01:11:58 -0400 From: Peter G <pgatz@tiac.net> To: Sean O'Connell <sean@stat.Duke.EDU> Cc: freebsd-mobile@freebsd.org Subject: Re: Netgear FA410TX and 4.0, anyone recall soln? Message-ID: <3905291D.2928A197@tiac.net> References: <20000421201038.A42757@skriver.dk> <39004EEB.C3803816@seicom.net> <200004211754.LAA18740@harmony.village.org> <200004230157.TAA28002@harmony.village.org> <39026135.369B415B@tiac.net> <20000423205547.A21131@stat.Duke.EDU>
index | next in thread | previous in thread | raw e-mail
Sean thanx for response, tried what you suggested and some combos thereof,
here's some addl' info;
The NETGEAR DOS utility yields this info for the FA410:
I/O: 300
IRQ: 9
H/W Rev Level: C
About all I can do is turn the FA410's power on and off w/ pccardc power
... (BTW nothing in slot 1)
dumpcis yields:
Read return -1 bytes (expected 2)
pccardc: CIS code read: Cannot allocate memory
Read return -1 bytes (expected 10)
Configuration data for card in slot 0
2 slots found
pccardc enabler w/ the right? settings yields:
drv ed0, mem 0xd4000, size 32768, io 768, irq 0x200, flags 0x0
pccardc: set driver: Device not configured
rdmap yields:
Mem 0: flags 0x041 host 0xd4000 card 2000 size 32768 bytes
Mem 1: flags 0x000 host 0x0 card 0000 size 0 bytes
Mem 2: flags 0x000 host 0x0 card 0000 size 0 bytes
Mem 3: flags 0x000 host 0x0 card 0000 size 0 bytes
Mem 4: flags 0x000 host 0x0 card 0000 size 0 bytes
I/O 0: flags 0x004 port 0x300 size 32 bytes
I/O 1: flags 0x000 port 0x 0 size 0 bytes
Mem 0: flags 0x000 host 0x0 card 0000 size 0 bytes
Mem 1: flags 0x000 host 0x0 card 0000 size 0 bytes
Mem 2: flags 0x000 host 0x0 card 0000 size 0 bytes
Mem 3: flags 0x000 host 0x0 card 0000 size 0 bytes
Mem 4: flags 0x000 host 0x0 card 0000 size 0 bytes
I/O 0: flags 0x000 port 0x 0 size 0 bytes
I/O 1: flags 0x000 port 0x 0 size 0 bytes
rdreg yields:
Registers for slot 0
00: 83 7f 90 60 00 af 01 02 00 00 00 00 00 00 00 00
10: d4 80 db 00 2e 3f c0 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Registers for slot 1
00: 83 00 10 00 00 af 00 00 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 c0 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
dmesg has this relevant output for pcic:
pcic-pci0: <TI PCI-1130 PCI-CardBus Bridge> mem 0x10812000-0x10812fff at
device 2.0 on pci0
pcic-pci1: <TI PCI-1130 PCI-CardBus Bridge> mem 0x10811000-0x10811fff at
device 2.1 on pci0
pcic0: <Intel i82365> at port 0x3e0 iomem 0xd0000 irq 10 on isa0
pcic0: management irq 10
pccard0: <PC Card bus -- kludge version> on pcic0
pccard1: <PC Card bus -- kludge version> on pcic0
nothing relevant in my /boot/loader.conf (tried your suggestions and some
"twists" also)
in my /etc/rc.conf I did state that pccard.conf would be config file, as
you suggested
my /boot/kernel.conf;
di lnc0
di le0
di ie0
di fe0
di bt0
di aic0
di aha0
di adv0
di ed0
di cnw0
en ux0
po ux0 0x300 # I put these here following convention from 3.4 PAO and my
former settings w/ other card
ir ux0 9
f ux0 0
q
lastly the relevant portions of pccard.conf;
# Generally available IO ports
io 0x300-0x360
# Generally available IRQs (Built-in sound-card owners remove 5)
irq 3 9 10 11 13 15
ignirq 5
ignirq 3
ignirq 15
# Available memory slots
memory 0xd4000 96k
# BayNetworks NETGEAR FA410TXC Fast Ethernet
# Modified by Peter G on April 23, 2000
card "NETGEAR" "FA410TX"
# config 0x20 "ed0" ? # tried it both ways either this line or
the next
config 0x20 "ed0" 9
insert logger -t pccard:$device -s NETGEAR FA410TX Ethernet
inserted
insert /etc/pccard_ether $device
remove logger -t pccard:$device -s NETGEAR FA410TX Ethernet
removed
remove /sbin/ifconfig $device delete
Sean O'Connell wrote:
> Peter G stated:
> > Trying to get 2 IBM Thinkpads to reckognize Netgear FA410's via ed0
> > They are 760ED notebooks, p/n 9546-U9A
> > the pcic is a TI 1130
> >
> > I recall a messg awhile back that dealt with this same issue
> > anyone recall how it was solved?
>
> Peter-
>
> Not sure, what are the errors you are getting? Most problems
> involving pccard nic's (and pccard's in general) come down to
> irq conflicts.
>
> 1) make sure that you pcic is either in polling mode or using
> a totally free irq.
>
> The best way to do this is to have you kernel config file
> only contain
>
> # PCCARD (PCMCIA) support
> device card
> device pcic0 at isa?
>
> to force polling, add
>
> machdep.pccard.pcic_irq="0"
>
> to /boot/loader.conf
>
> If you want to specify a known free irq (say 4 if you disable the
> onboard serial console in the bios), then add
>
> machdep.pccard.pcic_irq="4"
>
> 2) make sure that you and pccardd agree on the pccard config file
> you are using. by default (literally, /etc/defaults/rc.conf)
> pccardd is invoked with /etc/pccard.conf.sample as its config
> file ... a massive source of confusion. A recent commit to
> RELENG_4 uses a /etc/defaults/pccard.conf with /etc/pccard.conf
> as an override ... as a bonus with this change, pccardd also
> rereads its config file on a SIGHUP
>
> I typically use a greatly pared down pccard.conf and therefore add
>
> pccard_conf="/etc/pccard.conf" # pccardd(8) config file
>
> to /etc/rc.conf
>
> 3) make sure that your list of irq in /etc/pccard.conf are all
> available and free. I often "cheat" and hardcode the irq into
> the card entry.
>
> dmesg | grep irq
>
> will often reveal the irq's in use. watch out for sound cards
> and winmodems and usb controllers.
>
> ibm usually lumps a lot of this on irq 11. unless 9 shows up
> with your video card, both 9 and 10 are good bets to be free.
>
> 4) with the if_ed driver and pccards, just add
>
> device ed
>
> to your kernel (no 0's or irqs or i/o ports etc).
>
> Hope this helps
> S
> -----------------------------------------------------------------------
> Sean O'Connell Email: sean@stat.Duke.EDU
> Institute of Statistics and Decision Sciences Phone: (919) 684-5419
> Duke University Fax: (919) 684-8594
N…'²æìr¸›zǧvf¢–Ú&j:+v‰¨·ž è®"¶§²æìr¸›yúÞy»š†â•è§¶›¡Ü¨~Ø^™ë,j
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3905291D.2928A197>
