On Thu,08.Apr.10, 14:11:02, Stephen Powell wrote:
>
> Andrei, I already told the OP about modinfo in an earlier post; but
If you look at the headers you can see that in theory I beat you by ~30
minutes, but in practice, the mail was stuck in my postfix queue until
today, because wicd does not r
On Sun, 4 Apr 2010 18:15:33 -0400 (EDT), Andrei Popescu wrote:
> On Mon,05.Apr.10, 07:36:03, Lubos Rendek wrote:
>> thanks guys for this.. Now what is the best way to link modules to a
>> specific hardware. for example my lsmod shows that I use 'ecb' module.
>> For someone like me this name does no
On Mon,05.Apr.10, 07:36:03, Lubos Rendek wrote:
> thanks guys for this.. Now what is the best way to link modules to a
> specific hardware. for example my lsmod shows that I use 'ecb' module.
> For someone like me this name does not say much. Is there a way to
> find which module belongs to which p
On Wed, 7 Apr 2010 07:45:25 -0400 (EDT), Lubos Rendek wrote:
> On Mon, Apr 5, 2010 at 8:53 AM, Stephen Powell wrote:
>> On Sun, 4 Apr 2010 17:36:03 -0400 (EDT), Lubos Rendek wrote:
>>>
>>> thanks guys for this.. Now what is the best way to link modules to a
>>> specific hardware. for example my lsm
thanks Stephen this is exactly what I was looking for. :-)
On Mon, Apr 5, 2010 at 8:53 AM, Stephen Powell wrote:
> On Sun, 4 Apr 2010 17:36:03 -0400 (EDT), Lubos Rendek wrote:
>>
>> thanks guys for this.. Now what is the best way to link modules to a
>> specific hardware. for example my lsmod sho
On Mon, Apr 5, 2010 at 6:38 AM, Sven Joachim wrote:
> On 2010-04-05 00:19 +0200, Stan Hoeppner wrote:
>
>> With some Google help I figured out how to fix the missing
>> /var/lib/dpkg/available problem and got lshw removed. Hopefully there's no
>> remaining hidden damage on my server.
>
> The less
Sven Joachim wrote:
> You are shooting the messenger. lshw is a userspace program, not a
> device driver. If running it locks up your system, this is almost
> surely a bug in the kernel.
Userspace programs run as root, such as lshw, have access to the entire
machine memory, registers, and data b
On 2010-04-05 00:19 +0200, Stan Hoeppner wrote:
> With some Google help I figured out how to fix the missing
> /var/lib/dpkg/available problem and got lshw removed. Hopefully there's no
> remaining hidden damage on my server.
The lesson from this problem is that it is a bad idea to put /var on
e
On Mon, Apr 5, 2010 at 04:43, Stan Hoeppner wrote:
> Ron Johnson put forth on 4/4/2010 9:08 PM:
> Your analogy, regardless of how cute, sarcastic, and applicable you believe
> it to be doesn't fit. If I run lshw, it will lock the system every time,
> not only after adding salt to the machine for
Ron Johnson put forth on 4/4/2010 9:08 PM:
> On 2010-04-04 17:19, Stan Hoeppner wrote:
>> With some Google help I figured out how to fix the missing
>> /var/lib/dpkg/available problem and got lshw removed. Hopefully
>> there's no
>> remaining hidden damage on my server. I don't think I'll ever be
On 2010-04-04 17:19, Stan Hoeppner wrote:
With some Google help I figured out how to fix the missing
/var/lib/dpkg/available problem and got lshw removed. Hopefully there's no
remaining hidden damage on my server. I don't think I'll ever be messing
with lshw again. It could be that it expects
On 10-04-04 17:03:30, Celejar wrote:
On Sun, 04 Apr 2010 15:57:09 -0500
Stan Hoeppner wrote:
> Celejar put forth on 4/4/2010 11:53 AM:
>
> > $ apt-cache show lshw
> >
> > ...
> >
> > Description: information about hardware configuration
> > A small tool to provide detailed information on the h
On Sun, 4 Apr 2010 17:36:03 -0400 (EDT), Lubos Rendek wrote:
>
> thanks guys for this.. Now what is the best way to link modules to a
> specific hardware. for example my lsmod shows that I use 'ecb' module.
> For someone like me this name does not say much. Is there a way to
> find which module be
With some Google help I figured out how to fix the missing
/var/lib/dpkg/available problem and got lshw removed. Hopefully there's no
remaining hidden damage on my server. I don't think I'll ever be messing
with lshw again. It could be that it expects something my old server
doesn't have, and lo
Celejar put forth on 4/4/2010 4:03 PM:
> Not a clue - I've just been in the habit of using lshw (although I
> don't use it all that often). I'll have to look into dmidecode.
I thought I'd give lshw a try. Based on my brief experience, I'd recommend
others not do so.
This is interesting, and re
thanks guys for this.. Now what is the best way to link modules to a
specific hardware. for example my lsmod shows that I use 'ecb' module.
For someone like me this name does not say much. Is there a way to
find which module belongs to which piece of hardware?
>> Other than html or xml output, wha
On Sun, 04 Apr 2010 15:57:09 -0500
Stan Hoeppner wrote:
> Celejar put forth on 4/4/2010 11:53 AM:
>
> > $ apt-cache show lshw
> >
> > ...
> >
> > Description: information about hardware configuration
> > A small tool to provide detailed information on the hardware
> > configuration of the ma
Celejar put forth on 4/4/2010 11:53 AM:
> $ apt-cache show lshw
>
> ...
>
> Description: information about hardware configuration
> A small tool to provide detailed information on the hardware
> configuration of the machine. It can report exact memory
> configuration, firmware version, mainbo
On Sun, 4 Apr 2010 10:37:34 +1000
Lubos Rendek wrote:
> HI guys,
>
> Suppose that I have a some laptop in my hands and I would like to find
> out what hardware this laptop has and what is supported by Debian out
> of the box by which modules. Is there any tool which will be able to
> retrieve a
On Sun, Apr 04, 2010 at 10:37:34AM +1000, Lubos Rendek wrote:
> HI guys,
>
> Suppose that I have a some laptop in my hands and I would like to find
> out what hardware this laptop has and what is supported by Debian out
> of the box by which modules. Is there any tool which will be able to
> retr
On 2010-04-03 19:37, Lubos Rendek wrote:
HI guys,
Suppose that I have a some laptop in my hands and I would like to find
out what hardware this laptop has and what is supported by Debian out
of the box by which modules. Is there any tool which will be able to
retrieve all important hardware inf
HI guys,
Suppose that I have a some laptop in my hands and I would like to find
out what hardware this laptop has and what is supported by Debian out
of the box by which modules. Is there any tool which will be able to
retrieve all important hardware information. I know that this can be
achieved
22 matches
Mail list logo
