Surecom EP-428X PCCARD in -CURRENT
Morning all ... Just got my Vaio Z505s upgraded to -CURRENT, in order to get my new Surecom Ethernet PCMCIA card to work ... looked in /etc/defaults/pccard.conf, and found the EP-427X card(s) in there, but haven't got a clue on how to setup a similar entry for the -428X to be recognized ... Pointers/directions? Thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
With my inspiron:
cvsupped Tues. Evening PDT.
pci_cfgintr_unique: hard-routed to irq 11
pci_cfgintr: 0:4 INTA routed to irq 11
pcic0: TI PCI-1225 PCI-CardBus Bridge irq 11 at device 4.0 on pci0
pcic0: Memory mapped device, will work.
pcic0: PCI Memory allocated: 0x4400
pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][pci only]
pccard0: PC Card bus (classic) on pcic0
pci_cfgintr_unique: hard-routed to irq 11
pci_cfgintr: 0:4 INTA routed to irq 11
pcic1: TI PCI-1225 PCI-CardBus Bridge irq 11 at device 4.1 on pci0
pcic1: Memory mapped device, will work.
pcic1: PCI Memory allocated: 0x44001000
pcic1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][pci only]
pccard1: PC Card bus (classic) on pcic1
after inserting first card:
pcic0: Event mask 0x4
pcic0: Event mask 0x4
pcic0: Event mask 0x6
pcic0: Event mask 0x6
pcic0: Event mask 0x4
pcic0: debounced state is 0x3282
pcic0: Unsupported card type inserted
pcic0: Event mask 0x4
pcic0: Event mask 0x6
pcic0: debounced state is 0x3610
pccard: card inserted, slot 0
pcic0: Event mask 0x9
lxtphy0: LXT970 10/100 media interface on miibus0
lxtphy0: 100baseFX, 100baseFX-FDX, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-F
DX, auto
ed0 at port 0x300-0x31f irq 11 slot 0 on pccard0
ed0: address 00:e0:98:74:49:0d, type Linksys (16 bit)
after inserting 2nd card:
pcic1: Event mask 0x6
pcic1: debounced state is 0x3610
pccard: card inserted, slot 1
pcic1: Event mask 0x9
and pccardd says:
Jun 20 17:36:29 jules pccardd[158]: Card "Zoom Telephonics, Inc."("PCMCIA 56K LT
DataFax") [(null)] [(null)] matched "Zoom Telephonics, Inc." ("PCMCIA 56K LT
DataFax") [(null)] [(null)]
Jun 20 17:36:29 jules pccardd[158]: Failed to allocate IRQ for Zoom Telephonics,
Inc.
rc.conf has:
pccard_enable="YES" # Set to YES if you want to configure PCCARD devices.
pccard_mem="DEFAULT"# If pccard_enable=YES, this is card memory address.
pccard_beep="1" # pccard beep type.
#pccard_ifconfig=DHCP # DHCP on the wavelan please
pccardd_flags="-I -i 11" # Additional flags for pccardd.
whichever card is in the top slot (2nd slot I think) doesn't work.
--
++ __ _ __
| __--_|\ Julian Elischer | \ U \/ / hard at work in
| / \ [EMAIL PROTECTED] +--x USA\ a very strange
| ( OZ)\___ ___ | country !
+- X_.---._/presently in San Francisco \_/ \\
v
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PCCARD and -current
In message [EMAIL PROTECTED] Julian Elischer writes: : whichever card is in the top slot (2nd slot I think) doesn't work. Noted. I don't have a laptop with two slots to test with :-(. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
In message [EMAIL PROTECTED] [EMAIL PROTECTED] writes: : I make a short patch to sharing IRQ between a PCIC and a PC Card when using : PCI IRQ routing. : #Does this patch help you? Yes. I've made a larger patch and committed it that mostly works without changes (you still need to add -I, but not -i) to the old configuration. Your patch motivated me to make it. I think this will fix some problems that people with multiple slots. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
I make a short patch to sharing IRQ between a PCIC and a PC Card when using
PCI IRQ routing.
#Does this patch help you?
---
YAMAMOTO ShigeruInternet Initiative Japan Inc.
[EMAIL PROTECTED] Network Engineering Div.
Index: pcic.c
===
RCS file: /share/cvsup/FreeBSD/current/usr/src/sys/pccard/pcic.c,v
retrieving revision 1.141
diff -u -r1.141 pcic.c
--- pcic.c 2001/06/04 03:29:06 1.141
+++ pcic.c 2001/06/13 04:18:17
@@ -805,8 +805,13 @@
/*
* If we're routing via pci, we can share.
*/
- if (sc-func_route == pci_parallel type == SYS_RES_IRQ)
+ if (sc-func_route == pci_parallel type == SYS_RES_IRQ) {
flags |= RF_SHAREABLE;
+ if (sc-irqres) {
+ start = rman_get_start(sc-irqres);
+ end = rman_get_start(sc-irqres);
+ }
+ }
return (bus_generic_alloc_resource(dev, child, type, rid, start, end,
count, flags));
Index: pcic_pci.c
===
RCS file: /share/cvsup/FreeBSD/current/usr/src/sys/pccard/pcic_pci.c,v
retrieving revision 1.48
diff -u -r1.48 pcic_pci.c
--- pcic_pci.c 2001/06/09 07:34:17 1.48
+++ pcic_pci.c 2001/06/13 04:26:52
@@ -446,9 +446,10 @@
sc-flags = PCIC_PD_POWER;
num6729++;
} else {
+ device_printf(dev, MEMORY mapped device!\n);
sc-memrid = CB_PCI_SOCKET_BASE;
sc-memres = bus_alloc_resource(dev, SYS_RES_MEMORY,
- sc-memrid, 0, ~0, 1, RF_ACTIVE);
+ sc-memrid, 0, ~0, 0x1000, RF_ACTIVE);
if (sc-memres == NULL pcic_pci_get_memory(dev) != 0)
return (ENOMEM);
sp-getb = pcic_pci_getb2;
Re: PCCARD and -current
In message [EMAIL PROTECTED] [EMAIL PROTECTED] writes: : I make a short patch to sharing IRQ between a PCIC and a PC Card when using : PCI IRQ routing. : #Does this patch help you? Yes. It does. Thank you! Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
Warner == Warner Losh [EMAIL PROTECTED] writes: Warner In summary: Warner o Use the same config file you used before. Warner o Update pccardd Warner o Add -I -i 9 to pccardd_flags (if your pcic's irq is 9). Warner o rebuild and reinstall the kernel. Warner o reboot. Send your panics to me. :-) I just did that. I got a panic, which I could not save (I cannot panic From ddb, it just doesn't work). ddb reports the faulty process as being ddb, and it relates to trap 12 being called ... (I don't remember the exact message unfortunately, I should find a null cable and use gdb). Here is my latest dmesg in case you see something wrong. The pcic irq is 9 here, right? Sam -- Samuel Tardieu -- [EMAIL PROTECTED] Copyright (c) 1992-2001 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.0-CURRENT #8: Tue Jun 12 11:40:44 CEST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TRILLIAN Timecounter i8254 frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (645.20-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 134152192 (131008K bytes) avail memory = 126197760 (123240K bytes) Preloaded elf kernel kernel at 0xc0437000. Pentium Pro MTRR support enabled Using $PIR table, 7 entries at 0xc00fdf50 apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xfcb0-0xfcbf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xfc60-0xfc7f at device 7.2 on pci0 pci_cfgintr_unique: hard-routed to irq 9 pci_cfgintr: 0:7 INTD routed to irq 9 usb0: Intel 82371AB/EB (PIIX4) USB controller 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 ums0: Logitech USB Mouse, rev 1.10/4.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. pci0: bridge, PCI-unknown at 7.3 (no driver attached) pci0: serial bus, FireWire at 8.0 (no driver attached) pcm0: Yamaha DS-1E (YMF744) mem 0xfecf-0xfecf7fff irq 9 at device 9.0 on pci0 pci0: simple comms at 10.0 (no driver attached) fxp0: Intel Pro 10/100B/100+ Ethernet port 0xfcc0-0xfcff mem 0xfed0-0xfedf,0xfecff000-0xfecf irq 9 at device 11.0 on pci0 fxp0: Ethernet address 08:00:46:0c:b4:c7 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci_cfgintr_unique: hard-routed to irq 9 pci_cfgintr: 0:12 INTA routed to irq 9 pcic0: Ricoh RL5C475 PCI-CardBus Bridge irq 9 at device 12.0 on pci0 pcic0: PCI Memory allocated: 0x4400 pccard0: PC Card bus (classic) on pcic0 pci0: memory, flash at 13.0 (no driver attached) orm0: Option ROMs at iomem 0xc-0xcbfff,0xdc000-0xd on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 pmtimer0 on isa0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A spic0: Sony Programmable I/O Controller at port 0x10a0-0x10a4 on isa0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources atspeaker0: AT speaker at port 0x61 on isa0 unknown: PNP0c02 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0401 can't assign resources IPsec: Initialized Security Association Processing. ad0: 11513MB IBM-DARA-212000 [23392/16/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s2a PGP signature
Re: PCCARD and -current
Sam == Samuel Tardieu [EMAIL PROTECTED] writes: Sam I just did that. I got a panic, which I could not save (I cannot Sam panic From ddb, it just doesn't work). ddb reports the faulty Sam process as being ddb, and it relates to trap 12 being called Sam ... (I don't remember the exact message unfortunately, I should Sam find a null cable and use gdb). Some more info: I just borrowed an Aironet card, and it works just fine by adding -I -i 9. It seems to be only my Psion Dacom Gold Card that has a problem. Sam -- Samuel Tardieu -- [EMAIL PROTECTED] PGP signature
Re: PCCARD and -current
In message [EMAIL PROTECTED] Samuel Tardieu writes: : I just did that. I got a panic, which I could not save (I cannot panic : From=20ddb, it just doesn't work). ddb reports the faulty process as : being ddb, and it relates to trap 12 being called ... (I don't : remember the exact message unfortunately, I should find a null cable : and use gdb). I'll need a stack traceback to track this down. Maybe you've told me before, but what kind of card are you using? : Here is my latest dmesg in case you see something wrong. The pcic irq : is 9 here, right? According to the dmesg you've sent, that is correct. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
In message [EMAIL PROTECTED] Samuel Tardieu writes: : fine by adding -I -i 9. It seems to be only my Psion Dacom Gold Card : that has a problem. OK. This is the second report of a modem failing (but mine worked, grump) so I'll look into this some more. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
I also had to add options from NEWCARD to my kern cofiguration file. That is why I couldn't get it to work with my GENERIC based configuration. I haven't seen that documented, but it worked for me after 3 days of suffering. ed Quoting Warner Losh [EMAIL PROTECTED]: In message [EMAIL PROTECTED] Brian Somers writes: : With a ? instead of the 9 on the config line, I got an irq resource : allocation failure. Go figure ! Add -I to pccardd_flags. warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message --- The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn and relearn. --Alvin Toffler To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
In message [EMAIL PROTECTED] Edwin Culp writes: : I also had to add options from NEWCARD to my kern cofiguration file. : That is why I couldn't get it to work with my GENERIC based configuration. : I haven't seen that documented, but it worked for me after 3 days of : suffering. You shouldn't have had to do that. which ones were they, and are you still running pccard (classic) aka OLDCARD? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
Warner == Warner Losh [EMAIL PROTECTED] writes: Warner You shouldn't have had to do that. which ones were they, and Warner are you still running pccard (classic) aka OLDCARD? Warner, I think that a short HOWTO-UPGRADE would benefit to everyone. For example, should I: - keep my old kernel settings (using the glue compatibility layer) or use the new one? (copied from NEWCARD) - make sure that my hints file matches the interrupt of my pcic device? (9 in my case, shared with all the other PCI stuff) - should I still be running pccardd if I choose the new settings? (pccardd reports that no PCCARD can be found in my case) - should I force the IRQ? (if I do that, while keeping the old settings (as pccardd won't start with the new ones albeit it's a new pccardd), then I get a panic using -I -i 9) Thanks. Sam -- Samuel Tardieu -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
The kernel configuration that I couldn't get to work was basically GENERIC with SCSI, USB commented out and IPFW added. The one that works is the NEWCARD with almost identical but with the following differences only, I think. #device card# pccard bus #device pcic# pcmcia bridge devicepccard devicecardbus devicepccbb # cardbus (yenta) bridge and the -I -i 10 in my case. Generic still has card and pcic and doesn't have pccard, cardbus and pccbb. Those changes seem to have made my old k-6 laptop a very happy camper.:-) The only problem was it took me three days to find a combination that worked. This helps maintain the level of excitement generated by current, that has abounded recently:-) Thanks for the months of work on the integration fo cardbus into current. ed Quoting Warner Losh [EMAIL PROTECTED]: In message [EMAIL PROTECTED] Edwin Culp writes: : I also had to add options from NEWCARD to my kern cofiguration file. : That is why I couldn't get it to work with my GENERIC based configuration. : I haven't seen that documented, but it worked for me after 3 days of : suffering. You shouldn't have had to do that. which ones were they, and are you still running pccard (classic) aka OLDCARD? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message --- The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn and relearn. --Alvin Toffler To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
In message [EMAIL PROTECTED] Samuel Tardieu writes: : I think that a short HOWTO-UPGRADE would benefit to everyone. For The entry in UPDATING should do that. If it is unclear, let me know and I'll update it. : example, should I: : : - keep my old kernel settings (using the glue compatibility layer) : or use the new one? (copied from NEWCARD) Keep old kernel settings, do not use new ones. : - make sure that my hints file matches the interrupt of my pcic : device? (9 in my case, shared with all the other PCI stuff) Hints adjustment is not necessary. Hints are only used for ISA attachment. : - should I still be running pccardd if I choose the new settings? : (pccardd reports that no PCCARD can be found in my case) Use pccardd. If it is reporting no pccard slots found, then either your cardbus bridge isn't being recognized or you are running newcard. : - should I force the IRQ? (if I do that, while keeping the old : settings (as pccardd won't start with the new ones albeit it's a : new pccardd), then I get a panic using -I -i 9) You shouldn't be getting a panic. If you are seeing a panic, make sure that you have a new pccardd and have rebuilt the kernel. If you get a panic, please report a traceback. In summary: o Use the same config file you used before. o Update pccardd o Add -I -i 9 to pccardd_flags (if your pcic's irq is 9). o rebuild and reinstall the kernel. o reboot. Send your panics to me. :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
In message [EMAIL PROTECTED] Edwin Culp writes: : The kernel configuration that I couldn't get to work was basically GENERIC with : SCSI, USB commented out and IPFW added. The one that works is the NEWCARD with : almost identical but with the following differences only, I think. : : #device card# pccard bus : #device pcic# pcmcia bridge : devicepccard : devicecardbus : devicepccbb # cardbus (yenta) bridge : : and the -I -i 10 in my case. : : Generic still has card and pcic and doesn't have pccard, cardbus and pccbb. : Those changes seem to have made my old k-6 laptop a very happy camper.:-) : : The only problem was it took me three days to find a combination that worked. : This helps maintain the level of excitement generated by current, that has : abounded recently:-) : : Thanks for the months of work on the integration fo cardbus into current. If you have device pccard rather than card in your kernel, you are running NEWCARD. Also, do you have one slot or two? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
In message [EMAIL PROTECTED] Julian Elischer writes: : Failed to allocate IRQ for Linksys Add -I to your pccardd_flags in rc.conf. Others have suggested '-I -i 11' for your case. Also, it is very important that you install a new pccardd too. Otherwise, you may find your system hanging when the card is reset after power on, but before it is assigned resources. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
In message [EMAIL PROTECTED] Seth Kingsley writes: : Sorry, I guess maybe this directive is counter-intuative. It supposed to : be a list of the free irq's in the system for pccardd to use with : inserted pccards when configuring them. Trying to use the irq that the : cardbus bridge already has will definetly result in a resource : allocation failure. But it shouldn't with the pci attachment in very current currents :-) Actaully, the irq in pccard.conf will likely be ignored in the not too distant future. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
I got the same results as you. It eventually worked when I copied the entry matching my card into /etc/pccard.conf and hard-wired the irq as the same as the pcic device (9 in my case): $ cat /etc/pccard.conf irq 9 card Lucent Technologies WaveLAN/IEEE config auto wi 9 insert /etc/pccard_ether $device start remove /etc/pccard_ether $device stop With a ? instead of the 9 on the config line, I got an irq resource allocation failure. Go figure ! So the question remains.. where was I supposed to change the interrupt mentionned in the UPDATING entry.. if not in the pccard.conf, then where? I certainly get the 'hangs' mentionned as being a symptom of NOT doing it.. Warner? On Fri, 8 Jun 2001, Mike Smith wrote: On Fri, Jun 08, 2001 at 11:19:10AM -0700, Julian Elischer wrote: kernel: pcic1: TI PCI-1225 PCI-CardBus Bridge irq 11 at device 4.1 on pci0 in pccard.conf I had irq 11 is this not what I was supposed to do? Sorry, I guess maybe this directive is counter-intuative. It supposed to be a list of the free irq's in the system for pccardd to use with inserted pccards when configuring them. Trying to use the irq that the cardbus bridge already has will definetly result in a resource allocation failure. Er, well, it shouldn't, and more to the point, in most modern laptops you *have* to share the two. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
In message [EMAIL PROTECTED] Brian Somers writes: : With a ? instead of the 9 on the config line, I got an irq resource : allocation failure. Go figure ! Add -I to pccardd_flags. warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
PCCARD and -current
I upgraded to last nights's -current.
UPGRADING said:
20010604:
pccard support for pci cards has been committed. You must change
your /etc/pccard.conf irq lines. It must match the irq used by
pcic device. Interrupt storms may result if you fail to do this.
Interrupt storms look a lot like a hang.
dmesg says:
kernel: pci_cfgintr_unique: hard-routed to irq 11
kernel: pci_cfgintr: 0:4 INTA routed to irq 11
kernel: pcic0: TI PCI-1225 PCI-CardBus Bridge irq 11 at device 4.0 on pci0
kernel: pcic0: PCI Memory allocated: 0x4400
kernel: pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr
save][pci only]
kernel: pccard0: PC Card bus (classic) on pcic0
kernel: pci_cfgintr_unique: hard-routed to irq 11
kernel: pci_cfgintr: 0:4 INTA routed to irq 11
kernel: pcic1: TI PCI-1225 PCI-CardBus Bridge irq 11 at device 4.1 on pci0
kernel: pcic1: PCI Memory allocated: 0x44001000
kernel: pcic1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr
save][pci only]
kernel: pccard1: PC Card bus (classic) on pcic1
but:
Card "Linksys"("EtherFast 10/100 PC Card (PCMPC100)") [] [(null)] matched
"Linksys" ("/Ether[Ff]ast 10/100 PC Card \(PCMPC100.*\)/") [(null)] [(null
)]
Failed to allocate IRQ for Linksys
pccardd started
in pccard.conf I had
irq 11
is this not what I was supposed to do?
what do I need to get my ethernet card working again?
--
__--_|\ Julian Elischer
/ \ [EMAIL PROTECTED]
( OZ) World tour 2000-2001
--- X_.---._/ Presently in San Francisco, CA
v
config file follows:
machine i386
cpu I686_CPU
ident NMDM
maxusers32
#To statically compile in device wiring instead of /boot/device.hints
#hints "GENERIC.hints" #Default places to look for devices.
makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols
options MATH_EMULATE
options INET#InterNETworking
options FFS #Berkeley Fast Filesystem
options SOFTUPDATES #Enable FFS soft updates support
options NFS #Network Filesystem
options MSDOSFS #MSDOS Filesystem
options CD9660 #ISO 9660 Filesystem
#optionsDEVFS #Device Filesystem
options PROCFS #Process filesystem
options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!]
options UCONSOLE#Allow users to grab the console
options USERCONFIG #boot -c editor
options VISUAL_USERCONFIG #visual boot -c editor
options KTRACE #ktrace(1) support
options P1003_1B#Posix P1003_1B real-time extensions
options _KPOSIX_PRIORITY_SCHEDULING
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options DDB
# To make an SMP kernel, the next two are needed
device isa
device pci
# parallel port
device ppc
device ppbus
device lpt
# Floppy drives
device fdc
# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
device atapicd # ATAPI CDROM drives
options ATA_STATIC_ID #Static device numbering
# atkbdc0 controls both the keyboard and the PS/2 mouse
device atkbdc # At keyboard controller
device atkbd # at keyboard
device psm # psm mouse
device vga # VGA screen
# syscons is the default console driver, resembling an SCO console
device sc
# Floating point support - do not disable.
device npx
# Power management support (see NOTES for more options)
device apm
# Add suspend/resume support for the i8254.
device pmtimer
# Audio support
device pcm
# PCCARD (PCMCIA) support
device card# pccard bus
device pcic# PCMCIA bridge
# Serial (COM) ports
device sio # 8250, 16[45]50 based serial ports
# Parallel port
# ISA Ethernet NICs. pccard nics included.
device miibus # MII bus support
device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards
# Pseudo devices - the number indicates how many units to allocated.
device random # Entropy device
device loop# Network loopback
device ether # Ethernet support
device tun # Packet tunnel.
device pty # Pseudo-ttys (telnet etc)
device md # Memory "disks"
# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
device bpf # Berkeley packet filter
device nmdm #
Re: PCCARD and -current
On Fri, Jun 08, 2001 at 01:55:40PM -0700, Seth Kingsley wrote: On Fri, Jun 08, 2001 at 11:19:10AM -0700, Julian Elischer wrote: kernel: pcic1: TI PCI-1225 PCI-CardBus Bridge irq 11 at device 4.1 on pci0 in pccard.conf I had irq 11 is this not what I was supposed to do? Sorry, I guess maybe this directive is counter-intuative. It supposed to be a list of the free irq's in the system for pccardd to use with inserted pccards when configuring them. Trying to use the irq that the cardbus bridge already has will definetly result in a resource allocation failure. Oops! I didn't even read the UPDATING line even. I withdraw all of my comments. -- || Seth Kingsley || Platforms Lab Opps || [EMAIL PROTECTED] || To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
So the question remains.. where was I supposed to change the interrupt mentionned in the UPDATING entry.. if not in the pccard.conf, then where? I certainly get the 'hangs' mentionned as being a symptom of NOT doing it.. Warner? On Fri, 8 Jun 2001, Mike Smith wrote: On Fri, Jun 08, 2001 at 11:19:10AM -0700, Julian Elischer wrote: kernel: pcic1: TI PCI-1225 PCI-CardBus Bridge irq 11 at device 4.1 on pci0 in pccard.conf I had irq 11 is this not what I was supposed to do? Sorry, I guess maybe this directive is counter-intuative. It supposed to be a list of the free irq's in the system for pccardd to use with inserted pccards when configuring them. Trying to use the irq that the cardbus bridge already has will definetly result in a resource allocation failure. Er, well, it shouldn't, and more to the point, in most modern laptops you *have* to share the two. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
