What is the make and model of laptop again please?
-----Original Message-----
From: Roger Searle [mailto:[EMAIL PROTECTED]
Sent: Thursday, 1 April 2004 10:53 a.m.
To: [EMAIL PROTECTED]
Subject: back to square 1...
Hi Matthew and anyone else following my dramas...
I think I'm in for (yet another) reinstall - I've lost count of how many
of those I've done now!
I just found the lilo boot options, and changed the acpi and noapic
options as you suggest. (I really ought to do some work - will be going
until late today).
Yes, as you note, I have some hardware issues under linux, the mouse
normally doesn't work, nor the sound, the touch pad does. Under xp it's
all fine. Ocassionally the mouse (usb) will sort of work which it just
did now for the first time in weeks. As I went to restart, it was
extremely slow to do so, got there eventually, but wouldn't unmount
/proc and some other errors that flashed by too quickly, now on
rebooting detected a change in mouse, removed psaux, added a usb mouse,
gets to the line "bringing up interface eth0 [OK] and now hangs on
"starting pcmcia".
I suspect this is more to do with the mouse than changing the boot
options... I just completely walked away from linux forever - for about
5 minutes, and now I'm back ;-)
Matthew Gregan wrote:
>On Thu, Apr 01, 2004 at 08:16:56AM +1200, Roger Searle wrote:
>
>
>> 3: 0 IO-APIC-edge usb-uhci, eth0
>>
>>
>
>Presumably this output was produced after the machine had been up for a
>while, and you'd tried to bring the network up and perform tests pings,
>etc. If that's true, then it looks as if the kernel is screwing up
>interrupt routing (note that the interrupt that eth0 is associated with
>has been never been raised). It's quite likely that specifying
>'acpi=off' (and possibly also 'noapic') with your kernel boot command
>will allow the NIC to work--but these options are only a temporary fix.
>
>The permanent fix will likely require a kernel upgrade--what version
>are you currently running? ('uname -r' to check)
>
>
>
>>(dmesg isn't short !!)
>>
>>
>
>No, it's not, and unfortunately the information I wanted to see was
>long gone. Somewhat unrelated to your NIC problems, I noticed that the
>dmesg you provided had two kernel oops messages, both related to APM.
>This suggests either a kernel bug, or a problem with your hardware.
>
>Cheers,
>-mjg
>
>
