[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: PCMCIA network card with woody install



On Sun, 14 Jul 2002 10:19:34 -0400
Seneca <seneca-cunningham@rogers.com> wrote:

> On Sat, Jul 13, 2002 at 09:33:50PM -0700, Shawn Dunn wrote:
> > On Sat, 13 Jul 2002 23:42:50 -0400
> > Seneca <seneca-cunningham@rogers.com> wrote:
> > 
> > 
<snip>
> > > > > pcmcia-cs/FAQ.Debian.gz). 2.2.20 (defualt woody kernel)
> > > >  
> > 
> > > > Ok, so here goes, managed to get it to boot w/o pcmcia enabled,
> > > > if I'modprobe i82365'  I get a kernel panic, and have to reboot,
> > > > if I'insmod i82365'  I get the following:
> > > > 
> > > > max:/lib/modules/2.2.20/pcmcia# insmod i82365
> > > > Using /lib/modules/2.2.20/pcmcia/i82365.o
> > > > /lib/modules/2.2.20/pcmcia/i82365.o: unresolved symbol
> > > > pci_set_power_state...so on and so forth for about ten lines of
> > > > unresolved symbols
> > > > 
<snip>
> > > 
> > > > vendor.   Ok, so I assume that there's a module not yet loaded,
> > > > and do an 'insmod pcmcia_core'  and another kernel panic.......
> > > 
> > > Your assumption about the unresolved symbols is correct, i82365
> > > requires pcmcia_core.
> > > 
<snip>
> > > I have put the 2.2.20 kernel that is in woody on this system (a
> > > laptop that uses i82365 for the bridge). However, I have have not
> > > seen it panic (even after multiple boots). So, what does it say
> > > when the kernel panics (it probably says something more than just
> > > "kernel panic")?
> > > 
> > Ok, a couple screens worth of what I would assume to be debuggin
> > symbols, and these are the last 4 lines of the kernel panic (after
> > setting /etc/default/pcmcia to pcmcia="yes" and rebooting).
> > 
> > Code: 8b 41 04 85 c9 74 22 8b 5a 18 8b 02 89 01 8b 0a 85 c9 74 08
> > Aiee, killing interrupt handler
> > Kernel Panic: Attempted to kill the idel task!
> > In interrupt handler - not syncing
> > 
> > 
> > and that's it, right after INIT starts the pcmcia services (I think,
> > it flashes into the debug for the kernel awful quick)
> 
> Those messages show a definite problem. The last time I saw a line
> starting with "Code: ", my kernel Oopsed.
> 
> What does it say before the registers && the stack? (you might need to
> set up a serial console, but scroll lock should work after init starts
> if you don't mind using pen && paper) What do your logs say (I'm
> wondering about what they said for the successful boot with pcmcia)?
> 
ok, how would I go about setting up a serial console, I have all PPC
machines here, and one lonely i386 (486 running Slackware 8, headless),
can I just string a serial cable to the Slack box, or is there something
I'm going to need to boot into single user and change on the laptop???

writing all those debuggin symbols down by hand doesn't sound like a
good time.


			--Shawn


-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: