At 5:26 PM +0200 7/30/05, Alexander Dalloz wrote:
>Content-Type: multipart/signed; micalg=pgp-sha1;
> protocol="application/pgp-signature";
> boundary="=-bk5ioauDW7D4PPUb1pix"
>
>Am Sa, den 30.07.2005 schrieb Hoffmann um 17:17:
>
>> (1) MY NETWORKCARD IS: Intel Pro/100 VE
>> (2) THE OUT PUT OF TYPYING lspci IS: command not found
>> Could I hear from you again?
>
>/sbin/lspci -v
>
>dmesg | grep e100
>
>/sbin/lsmod | grep e100
>
>If the module is not listed as loaded, then run:
>
>/sbin/modprobe -v e100
>
>and in another terminal run at same time:
>
>tail -f /var/log/messages
>
>> Hoffmann
>
>man su --> please see the difference between "su" and "su -".
Very important!
Also, one can use the whereis command to find where a command is:
$ whereis lspci
lspci: /sbin/lspci /usr/share/man/man8/lspci.8.gz
Things in sbin are mostly for root's use, but some of them work even when
not root, and lspci seems to be one of them. You can sometimes find the
command you want with apropos:
$ apropos lspci
lspci (8) - list all PCI devices
(whatis lspci would have done the same thing in this case, but apropos pci
would have been useful.) And also try man lspci. These commands help one
get past that "helpless" feeling when using Linux.
Searching the list archive does not work (though they're working on that);
until then here's a list mirror to search:
http://marc.theaimsgroup.com/?l=fedora-list&r=1&w=2
or use Google, but Google isn't as current:
<search terms> site:www.redhat.com/archives/fedora-list
____________________________________________________________________
TonyN.:' <mailto:tonynelson@xxxxxxxxxxxxxxxxx>
' <http://www.georgeanelson.com/>
