From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ethernet card not working, tried tulip drivers...
Date: Wed, 28 Oct 2009 14:01:56 +0000 [thread overview]
Message-ID: <65A85796-2F1A-40CE-B640-1E190F548F92@stellar.eclipse.co.uk> (raw)
In-Reply-To: <4AE782F7.9010409@cox.net>
On 27 Oct 2009, at 23:32, Marcus Wanner wrote:
> ...
> To sum it up: How do I figure out what the name of my card is, and
> after that, what driver do I need?
Boot once again with the LiveCD, and the lspci and lshw commands
should work from there.
You can also run `lsmod` which will show which driver modules are
currently running in the LiveCD environment - the appropriate one is
likely to be amongst them.
From the LiveCD you can run these commands and redirect to a text
file on a USB drive - i.e. `lspci -v > /mnt/foo/file.txt`.
Also from the LiveCD, you can chroot back into the system you've
started building, and have network access. Follow the steps of the
handbook just as you did before - the disk is already partitioned, so
you can skip that bit; skip to mounting the disks at /mnt/gentoo, /mnt/
gentoo/boot &c, then do the mount where you bind /proc and execute the
chroot command just like you did before. Then you can `emerge sys-apps/
pciutils` to install lspci on the hard-drive of the new system and you
can add any other utilities you need (some of which might not be
included on the liveCD).
I find this easier, because once the liveCD has loaded you can set the
liveCD's root password, start ssh and you no longer need to do your
back in crouching over the new PC which is invariably, during the
duration of the build, located somewhere inconvenient, such as the
floor or the top of the sever closet. You can then return to your
comfy chair and continue your work over the network.
Stroller.
next prev parent reply other threads:[~2009-10-28 14:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 23:32 [gentoo-user] Ethernet card not working, tried tulip drivers Marcus Wanner
2009-10-27 23:38 ` Alan McKinnon
2009-10-28 1:32 ` Marcus Wanner
2009-10-28 10:38 ` Damien Sticklen
2009-10-28 14:53 ` Marcus Wanner
2009-10-28 0:36 ` [gentoo-user] " James
2009-10-28 1:22 ` Marcus Wanner
2009-10-28 1:28 ` Sebastian Beßler
2009-10-28 1:33 ` Marcus Wanner
2009-10-28 1:42 ` Dale
2009-10-28 14:56 ` Marcus Wanner
2009-10-28 7:41 ` [gentoo-user] " Mick
2009-10-28 8:01 ` Dale
2009-10-28 15:31 ` [gentoo-user] Ethernet card not working, tried tulip drivers... [resolved] Marcus Wanner
2009-10-28 21:39 ` Dale
2009-10-28 23:56 ` Marcus Wanner
2009-10-29 0:09 ` Dale
2009-10-29 16:18 ` Marcus Wanner
2009-10-28 14:01 ` Stroller [this message]
2009-10-28 17:56 ` [gentoo-user] Ethernet card not working, tried tulip drivers Dirk Heinrichs
2009-10-28 18:01 ` Dirk Heinrichs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=65A85796-2F1A-40CE-B640-1E190F548F92@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox