Re: pcmcia lockup inserting or removing cards in 2.4.5-ac{13,22}
Trevor Hemsley wrote: > > On Thu, 5 Jul 2001 03:06:11, Erik Mouw <[EMAIL PROTECTED]> > wrote: > > > Hmm, Cardbus and USB problems... you probably have both Cardbus and > > i82365 support in your kernel configuration. > > Once I have the BIOS set to "cardbus/16 bit" instead of "auto-detect" > I don't have a problem with having both Cardbus and i82365 support > compiled in. If the BIOS is set to auto then the PCI tables don't have > an IRQ specified and yenta.c uses IRQ 0! Interesting... That sounds like the kernel's plug-n-play code isn't doing its job. -- Jeff Garzik | Thalidomide, eh? Building 1024| So you're saying the eggplant has an accomplice? MandrakeSoft | - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: pcmcia lockup inserting or removing cards in 2.4.5-ac{13,22}
On Thu, 5 Jul 2001 03:06:11, Erik Mouw <[EMAIL PROTECTED]> wrote: > Hmm, Cardbus and USB problems... you probably have both Cardbus and > i82365 support in your kernel configuration. Once I have the BIOS set to "cardbus/16 bit" instead of "auto-detect" I don't have a problem with having both Cardbus and i82365 support compiled in. If the BIOS is set to auto then the PCI tables don't have an IRQ specified and yenta.c uses IRQ 0! -- Trevor Hemsley, Brighton, UK. [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: pcmcia lockup inserting or removing cards in 2.4.5-ac{13,22}
On Thu, Jul 05, 2001 at 12:41:15AM +, Trevor Hemsley wrote: > OK, I've done quite a lot more work on this. It isn't 2.4.5, I'd > compiled USB support in when I went to 2.4.5 and it's that that causes > the problems. I backed out all changes made between 2.4.2 and 2.4.5 in > drivers/pcmcia and that made no difference to the lockup so then I > went back to the .config file from 2.4.2 and that worked. Hmm, Cardbus and USB problems... you probably have both Cardbus and i82365 support in your kernel configuration. Your .config file should have this: # # PCMCIA/CardBus support # CONFIG_PCMCIA=y CONFIG_CARDBUS=y # CONFIG_I82365 is not set # CONFIG_TCIC is not set That fixed it for me for at least three laptops. Erik -- J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department of Electrical Engineering, Faculty of Information Technology and Systems, Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands Phone: +31-15-2783635 Fax: +31-15-2781843 Email: [EMAIL PROTECTED] WWW: http://www-ict.its.tudelft.nl/~erik/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: pcmcia lockup inserting or removing cards in 2.4.5-ac{13,22}
On Tue, 3 Jul 2001 00:30:10, "Trevor Hemsley" <[EMAIL PROTECTED]> wrote: > Somewhere between 2.4.2 and 2.4.5-ac13, PCMCIA card insertion and > removal appears to have broken on my Toshiba Libretto. On 2.4.2 all was > fine. On both 2.4.5-ac13 and ac22 it's broken. The whole machine freezes > solid, no SAK-s, SAK-u, SAK-b, no Ctrl-Alt-Fn to switch VC's. No messages > are issued. Problem occurs when inserting/removing any of YE-Data PCMCIA > floppy, TDK Smartmedia adapter (ide_cs), or 3c589 ethernet card. [large snip] OK, I've done quite a lot more work on this. It isn't 2.4.5, I'd compiled USB support in when I went to 2.4.5 and it's that that causes the problems. I backed out all changes made between 2.4.2 and 2.4.5 in drivers/pcmcia and that made no difference to the lockup so then I went back to the .config file from 2.4.2 and that worked. My best guess is that the USB support is using IRQ 11 and that the PCMCIA card sockets are wired to use that as well. I have a bypass for now - if I set the Toshiba BIOS up to use the slots in PCIC mode then it assigns them IRQ 15. In cardbus mode they get assigned IRQ 11 in Win9x but dmesg reports Linux Kernel Card Services 3.1.22 options: [pci] [cardbus] [pm] PCI: No IRQ known for interrupt pin A of device 00:06.0. Please try using pci=biosirq. PCI: No IRQ known for interrupt pin B of device 00:06.1. Please try using pci=biosirq. and Yenta IRQ list 0eb8, PCI irq0 Socket status: 3007 Yenta IRQ list 0eb8, PCI irq0 Socket status: 3007 Using pci=biosirq makes no difference when in cardbus mode. Ah, got it, flipping the PCMCIA setup in the BIOS from "Auto-detect" to "Cardbus/16 bit" fixes it. lspci -vv now lists the cardbus ports as having IRQ 11 assigned (instead of 0 before). Everything (famous last words) appears to be working. -- Trevor Hemsley, Brighton, UK. [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
re: pcmcia lockup inserting or removing cards in 2.4.5-ac{13,22}
On Mon, 2 Jul 2001, mr sam jooky wrote: >>Somewhere between 2.4.2 and 2.4.5-ac13, PCMCIA card insertion and >>removal appears to have broken on my Toshiba Libretto. On 2.4.2 all was >>fine. On both 2.4.5-ac13 and ac22 it's broken. The whole machine >>freezes >>solid, no SAK-s, SAK-u, SAK-b, no Ctrl-Alt-Fn to switch VC's. No >>messages >>are issued. Problem occurs when inserting/removing any of YE-Data >>PCMCIA >>floppy, TDK Smartmedia adapter (ide_cs), or 3c589 ethernet card. > >On my IBM Thinkpad 390E my PCMCIA works fine with 2.4.5, on very rare >occasions >the mouse will drift diagonaly to the lower right corner. I read in the kernel >sources that this happens normaly due to probing of the PCMCIA which screws up >the mouse device. It happens so rarely I have not yet taken the time to try to >debug it. > >- >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >the body of a message to [EMAIL PROTECTED] >More majordomo info at http://vger.kernel.org/majordomo-info.html >Please read the FAQ at http://www.tux.org/lkml/ ... Just FYI.(maybe worthless without ksymoops report) My ThinkPad 600X(Coppermine 500 MHZ, 100 MHZ SDRAM 320 MB, NeoMagic 256Z Video chipset, UDMA3 IDE hdd, cardbus IBM Etherjet 10/100 - Xircom oem, tulip 21143 compatible, external mii tranceiver - Cirrus CS46XX sound chipset) was completely locked up the system while loading yenta_socket and other modules. But, Mr. David Hinds' pcmcia-cs-3.1.26(i82365, tulip_cs) always works well. This was the first time for me to try to experiment with built-in pcmcia support of regular linux kernel after 2.4.0 kernel was released. I have been using only pcmcia-cs-3.1.2x since I bought 600X in Dec 2000, because pcmcia drivers of 2.4.0-testX kernel doesn't worked wel at that time. I use kernel-2.4.3-ac22, gcc-2.96-88, binutils-2.11.90.0.19, glibc-2.2.3, XFree86-4.1.0, ..). -- Where there is a will, there is a way. [EMAIL PROTECTED] For the future of you and me! [EMAIL PROTECTED] fingerprint = 1429 8AAF 8A2C 6043 DA2E BD4C 964C 2698 687D 4B7D - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
re: pcmcia lockup inserting or removing cards in 2.4.5-ac{13,22}
>Somewhere between 2.4.2 and 2.4.5-ac13, PCMCIA card insertion and >removal appears to have broken on my Toshiba Libretto. On 2.4.2 all was >fine. On both 2.4.5-ac13 and ac22 it's broken. The whole machine >freezes >solid, no SAK-s, SAK-u, SAK-b, no Ctrl-Alt-Fn to switch VC's. No >messages >are issued. Problem occurs when inserting/removing any of YE-Data >PCMCIA >floppy, TDK Smartmedia adapter (ide_cs), or 3c589 ethernet card. On my IBM Thinkpad 390E my PCMCIA works fine with 2.4.5, on very rare occasions the mouse will drift diagonaly to the lower right corner. I read in the kernel sources that this happens normaly due to probing of the PCMCIA which screws up the mouse device. It happens so rarely I have not yet taken the time to try to debug it. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
