Kernel 2.4 issues and PCMCIA

OK, don't know what I missed in the kernel config the first time through, second
time I just downloaded the src.rpm file for kernel 2.4.9 from redhat, borrowed
the i386 config and changed it so it would compile for Pentium Classic (586).
Now I'm running 2.4.14 with pcmcia 3.1.29. YAY. Thanks for the help.

> OK, that was interesting. Rebooted the system and after going through the
> hassle of having to manually fsck the drive I booted into the old kernel (ended
> up in init mode 3) and it booted up, started pcmcia and bang, here I am and it
> recognized the card that I inserted. So, um, what?
>
> Guess I musta missed something in the kernel (2.4.14), but I can verify that it
> is 3.1.29 that is running right now. So, guess I can screw with it like this
> for now and try again later (takes over an hour to do a compile) to redo 2.4.14
> and compile pcmcia 3.1.29 to link to it (thought I had since I pointed it to the
> headers for it, but musta only linked to the version I have running now,
> 2.4.7-10 <redhat binary rpm>)
>
> Kevin Brown wrote:
> >
> > OK, compiled 2.4.14 without its own PCMCIA stuff. Compiled pcmcia-cs 3.1.29
> > from the sourceforge site. Added it to the grub.conf file and rebooted.
> >
> > System comes up, starts to load pcmcia and crashes hard, kernel panic.
> >
> > Gist of the error was:
> >
> > Process insmod (pid:: 559, stackpage=c4ac5000)
> > Stack: <3 rows, 7 columns of 8 characters (guess Hex numbers)>
> > Call Trace: <more hex numbers>
> >
> > Code: 66 8b 42 02 a9 00 40 00 00 74 0f 8b 42 44 c7 00 ff ff ff ff
> > <0>Kernel Panic: Aiee, killing interrupt handler!
> > In interrrupt handler - not syncing
> >
> > This is basically what I have always gotten since 3.1.8 of the pcmcia-cs stuff
> > on my laptop. Don't know if it's a compile option I screwed up or what. Oh
> > well, time to try and figure out how to get grub to take me into single user
> > mode since I need to stop pcmcia from starting or I'll never get in.
> >
> > Kevin Brown wrote:
> > >
> > > OK, guess I'll give this a try. Haven't had much success with compiling the
> > > pcmcia stuff from source. Usually after compiling pcmcia from source I end up
> > > having the system crash on boot spitting out a bunch of Hex numbers.
> > >
> > > > No need to step back to a 2.2 kernel, just recompile and turn off the pcmcia
> > > > in the kernel and use the pcmcia_cs package. There are directions on how to do
> > > > this.
> > >
> > > > -----Original Message-----
> > > > From: Nancy Sollars [mailto:dnancy2@qwest.net]
> > > > Sent: Monday, November 19, 2001 2:44 PM
> > > > To: plug-discuss@lists.PLUG.phoenix.az.us
> > > > Subject: Re: Kernel 2.4 issues and PCMCIA
> > > >
> > > > id step back to kernel 2.2 then go look at
> > > >
> > > > http://sourceforge.net/project/showfiles.php?group_id=2405
> > > >
> > > > the pcmcia-cs page ..
> > > >
> > > > latest pcmcia driver set
> > > >
> > > > is :- 3.1.29
> > > >
> > > > I had the same issues with kernel 2.4 with a Dell Latitude 266XT
> > > >
> > > > Regards
> > > >
> > > > Nigel
> > > >
> > > > ----- Original Message -----
> > > > From: "Kevin Brown" <kevin_brown@qwest.net>
> > > > To: <plug-discuss@lists.PLUG.phoenix.az.us>
> > > > Sent: Monday, November 19, 2001 2:34 PM
> > > > Subject: Kernel 2.4 issues and PCMCIA
> > > >
> > > > > Ok, well I decided to update my version of linux from RH6.2 to 7.2 to get
> > > > > newer libs and whatnot. Install went ok, was able to keep the size down
> > > > to
> > > > > 650MB (uggh) and got it to boot.
> > > > >
> > > > > Unfortunately it seems that there is an issue with all 2.4 series kernels
> > > > and
> > > > > pcmcia stuff on my laptop (Panasonic Toughbook CF-25mkII, P150).
> > > > According to
> > > > > dmesg:
> > > > >
> > > > > Linux Kernel Card Services 3.1.22
> > > > > options: [pci] [cardbus] [pm]
> > > > > PCI: No IRQ known for interrupt pin A of device 00:10.0
> > > > > PCI: No IRQ known for interrupt pin B of device 00:10.1
> > > > > PCI: No IRQ known for interrupt pin A of device 00:13.0
> > > > > PCI: No IRQ known for interrupt pin B of device 00:13.1
> > > > > Yenta IRQ list 0e98, PCI irq0
> > > > > socket status: 30000046
> > > > >
> > > > > That last stuff is basically repeated 4 times (one for each socket I
> > > > have).
> > > > >
> > > > > doing 'cat /proc/pci' shows all four slots:
> > > > > Bus 0, device 19, function 0:
> > > > > Cardbus bridge: ricoh co ltd tl5c466
> > > > >
> > > > > I tried searching the web for answers, but the closest I got was Torvalds
> > > > > saying that they have it working, but it is from more than a year ago.
> > > > >
> > > > > Anyone have a clue as to how to fix this? Without pcmcia support my
> > > > laptop is
> > > > > useless since I can't connect to anything in linux with it now.
> > > > >
> > > > > P.S. All this because I wanted to be able to use my Wireless Orinoco card
> > > > in
> > > > > linux and windows, sigh.
> > > ________________________________________________
> > > See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
> > >
> > > PLUG-discuss mailing list - PLUG-discuss@lists.PLUG.phoenix.az.us
> > > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> > ________________________________________________
> > See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
> >
> > PLUG-discuss mailing list - PLUG-discuss@lists.PLUG.phoenix.az.us
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> ________________________________________________
> See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
>
> PLUG-discuss mailing list - PLUG-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss