Hi Jason, Rafael,
thanks for the comments. I figured out via /sys/devices/pnp0/ that it
was the keyboard that "does not support activation"; certainly makes
sense now that the keyboard doesn't do anything... Also, the item in
my DSDT that has an error is the "EC=embedded controller". Sounds bad
On Wednesday 05 July 2006 16:29, Marten van Kerkwijk wrote:
> Greetings again!
>
> I wasn't aware of anything as handy as netconsole until Jason
> mentioned it. With that, it is obvious that for the Dell X200 it does
> come alive after resume from RAM, but not for long. Rather,
>
> .
> .
> .
>
Hi Jason,
yes, I had checked dmesg, but it only mentions
.
.
.
pnp: PnP ACPI init
pnp: PnP ACPI: found 10 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
pnp: 00:01: ioport range 0x7b0-0x7bb has b
[EMAIL PROTECTED] said:
> Any suggestions? (Even if only how to figure out what pnp device
> 00:07 and 00:08 are?)
I found this info in dmesg output after boot, where the pnp code
initializes and probes hardware.
Jason
Using Tomcat but need to do more? Need to support web services, security?
G
Greetings again!
I wasn't aware of anything as handy as netconsole until Jason
mentioned it. With that, it is obvious that for the Dell X200 it does
come alive after resume from RAM, but not for long. Rather,
.
.
.
netconsole: network logging started
Freezing cpus ...
Stopping tasks: ==
