On Mon, Oct 19, 2009 at 8:30 PM, Israel Garcia wrote:
> On 10/19/09, Javier Barroso wrote:
>> Hi,
>>
>> On Mon, Oct 19, 2009 at 5:36 PM, Israel Garcia wrote:
>>> I'm having this dmseg output on some domU:
>>>
>>> XENBUS: Device with no driver: device/console/0
>>> processor: Unknown symbol pm_id
On 10/19/09, Javier Barroso wrote:
> Hi,
>
> On Mon, Oct 19, 2009 at 5:36 PM, Israel Garcia wrote:
>> I'm having this dmseg output on some domU:
>>
>> XENBUS: Device with no driver: device/console/0
>> processor: Unknown symbol pm_idle
>> thermal: Unknown symbol acpi_processor_set_thermal_limit
>
Hi,
On Mon, Oct 19, 2009 at 5:36 PM, Israel Garcia wrote:
> I'm having this dmseg output on some domU:
>
> XENBUS: Device with no driver: device/console/0
> processor: Unknown symbol pm_idle
> thermal: Unknown symbol acpi_processor_set_thermal_limit
> EXT3-fs: INFO: recovery required on readonly
I'm having this dmseg output on some domU:
XENBUS: Device with no driver: device/console/0
processor: Unknown symbol pm_idle
thermal: Unknown symbol acpi_processor_set_thermal_limit
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjou
Hello List,
I am having a peculiar problem. I have a lan card and a modem connected to my box. but the dmesg shows 2 ethernet cards as --
Linux version 2.2.20-idepci ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #1 Sat Apr 20 12:45:19 EST 2002
3c59x.c 18Feb01 Donald Becker and others
http://www.oddquad.org/
-
There's no future in time travel.
On Mon, 4 Aug 2003, Robert Tilley wrote:
> Date: Mon, 4 Aug 2003 16:20:59 -0400
> From: Robert Tilley <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: RealTex 8139 Problem -
Andreas writes:
> Robert wrote:
>
> > I am unable to use my D-Link RTL-8139 with any of kernel 2.4.19,
> > 2.4.21, or 2.6.0-test2 despite the Network Device explicitly being set
> > to RTL-8139 with
> > make menuconfig. Dmesg reports that my NIC is found and the 8139too
> > driver
> > loaded. B
On Sun, 2003-08-03 at 15:54, Andreas Janssen wrote:
> Hello
>
> Robert Tilley (<[EMAIL PROTECTED]>) wrote:
>
> > I am including the entire output from dmesg in the hopes of
> > successfully being able to use my NIC. The relevant portions are
> > highlighted.
>
> > I am unable to use my D-Link
Hello
Robert Tilley (<[EMAIL PROTECTED]>) wrote:
> I am including the entire output from dmesg in the hopes of
> successfully being able to use my NIC. The relevant portions are
> highlighted.
> I am unable to use my D-Link RTL-8139 with any of kernel 2.4.19,
> 2.4.21, or 2.6.0-test2 despite t
I am including the entire output from dmesg in the hopes of successfully being
able to use my NIC. The relevant portions are highlighted.
I am unable to use my D-Link RTL-8139 with any of kernel 2.4.19, 2.4.21, or
2.6.0-test2 despite the Network Device explicitly being set to RTL-8139 with
mak
utput is going to the files kern.log, syslog, debug and the
output of dmesg. If I stop klogd then it just gets into the dmesg
output.
Anyone have any bright ideas on whatever my dim brain is missing? I
know I could probably install ulogd and use the --ulog options on
iptables rules, and that's
Hi,
I have included the dmesg output, showing exactly what is happening
when the CDROM times out during boot. Since this worked once, I
am hoping that something stands out, and someonce can advise me
on how to increase the timeout. Again this is a H45 QuickCD.
When it did work once, it worked
Hi,
I have included the dmesg output, showing exactly what is happening
when the CDROM times out during boot. Since this worked once, I
am hoping that something stands out, and someonce can advise me
on how to increase the timeout. Again this is a H45 QuickCD.
When it did work once, it worked
13 matches
Mail list logo
