conflicts with pcmcia are probably going to be popping up a lot with the new 
2.4.1 kernel - linus took out pnp bios handling I guess. I have a problem 
with my Dell Inspiron laptop where starting cardmgr locks the system. Been 
talking to Dave of pcmcia-cs and he suggested a couple things for me to try. 
Check out the bug list at http://pcmcia-cs.sourceforge.net/ - The dell 
inspiron one by leejunfan  (me), and check the comments he posted.



On Thursday 22 February 2001 10:56, you wrote:
> Second time I've sent this - not sure if the message is getting out there!
>
> Anyone having problems with pcmcia networking? The pcmcia service starts
> up,
> but as soon as the net interface is ifup'ed (3c574 pcmcia module),
> networking
> starts but seems to cause some conflicts (resource?):
>
> Any attempt to log in from a virtual console is rejected with no error
> after a
> very long pause - including after boot into initlevel3 - I have to pop
> card out, login
> and then push card back in!
> New KDE terminals take a long time to show a prompt - another shell
> problem I
> guess.
> Mozilla takes forever to open up each connection to a URI.
> MandrakeUpdate will not appear on screen until after a long pause.
> X/KDE takes forever to start up.
>
> However, WGet/rsync work fine after tedious wait for initial connection.
>
> Any ideas - I'm using most recent updates applied to 'beta' isos, but
> this has always happened under 8.0 (but not 7.2). Please help, I may
> have missed something obvious! How can I check for resource conflicts
> for example?
>
> Here's my /proc/interrupts:
>
> 0: 246033 XT-PIC timer
> 1: 7060 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 5: 0 XT-PIC ESS Maestro 2E
> 10: 8038 XT-PIC 3c574_cs
> 11: 12 XT-PIC i82365
> 12: 61671 XT-PIC PS/2 Mouse
> 14: 16982 XT-PIC ide0
> 15: 2 XT-PIC ide1
> NMI: 0
> ERR:          1
>
> And a dmesg portion:
>
> Linux PCMCIA Card Services 3.1.24
>  kernel build: 2.4.1-22mdk #1 Wed Feb 21 12:55:54 CET 2001
>  options:  [pci] [cardbus] [apm]
> Intel PCIC probe: PCI: Found IRQ 11 for device 00:04.0
> PCI: The same IRQ used for device 00:04.1
> PCI: The same IRQ used for device 01:00.0
> PCI: Found IRQ 11 for device 00:04.1
> PCI: The same IRQ used for device 00:04.0
> PCI: The same IRQ used for device 01:00.0
>
>  TI 1225 rev 01 PCI-to-CardBus at slot 00:04, mem 0x20000000
>   host opts [0]: [ring] [serial pci & irq] [pci irq 11] [lat 168/32]
> [bus 2/5]    host opts [1]: [ring] [serial pci & irq] [pci irq 11] [lat
> 168/32] [bus 6/9]    ISA irqs (scanned) = 3,4,7,10 PCI status changes
> cs: IO port probe 0x0c00-0x0cff: clean.
> cs: IO port probe 0x0800-0x08ff: clean.
> cs: IO port probe 0x0100-0x04ff: excluding 0x258-0x25f 0x378-0x37f
> 0x3c0-0x3df 0x4d0-0x4d7
> cs: IO port probe 0x0a00-0x0aff: clean.
> cs: memory probe 0xa0000000-0xa0ffffff: clean.
> 3c574_cs.c v1.08 9/24/98 Donald Becker/David Hinds,
> [EMAIL PROTECTED]:
> <mailto:[EMAIL PROTECTED]:> 3Com 3c574 at io 0x300, irq
> 10, hw_addr 00:00:86:5C:5B:DA.
>  ASIC rev 1, 64K FIFO split 1:1 Rx:Tx, autoselect MII interface.
> ttyS03 at port 0x02e8 (irq = 10) is a 16550A
> eth0: found link beat
> eth0: autonegotiation complete: 100baseT-HD selected
> Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ...
> SMSC Super-IO detection, now testing Ports 2F0, 370 ...
> parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
> parport0: cpp_daisy: aa5500ff(38)
> parport0: assign_addrs: aa5500ff(38)
> parport0: cpp_daisy: aa5500ff(38)
> parport0: assign_addrs: aa5500ff(38)
> lp0: using parport0 (polling).
> lp0: console ready
> LSR safety check engaged!
> tty03 unloaded
> 3c574_cs.c v1.08 9/24/98 Donald Becker/David Hinds,
> [EMAIL PROTECTED]:
> <mailto:[EMAIL PROTECTED]:> 3Com 3c574 at io 0x300, irq
> 10, hw_addr 00:00:86:5C:5B:DA.
>  ASIC rev 1, 64K FIFO split 1:1 Rx:Tx, autoselect MII interface.
> ttyS03 at port 0x02e8 (irq = 10) is a 16550A
> eth0: found link beat
> eth0: autonegotiation complete: 100baseT-HD selected
> spurious 8259A interrupt: IRQ7.
>
> Not sure what the suprious interrupt is!
>
> Fingers crossed, some superb work going on there - well done people,
> Simon.

-- 
Jason Straight

Reply via email to