From: James Ausmus <james.ausmus@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: device eth0 does not exist
Date: Sun, 4 Oct 2009 09:33:37 -0700 [thread overview]
Message-ID: <b79f23070910040933h2440ed46lda6a6f585399c1cf@mail.gmail.com> (raw)
In-Reply-To: <20091003031512.A664561E@resin17.mta.everyone.net>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
On Sat, Oct 3, 2009 at 3:15 AM, Cinder <cinder@linuxwaves.com> wrote:
> Thanks again. I was using the e1000 both compiled-in and as a module with
> previous posts. I just tried the e1000e out of desperation, but I haven't
> tried it as a module. I don't feel that it's the kernel driver but rather
> the correct ethernet inter-face is not being created. I'm reading about
> writing udev rules at the moment. The kenel configuration I had was working.
>
>
If you do "ifconfig -a" and it doesn't show any eth* interface, then it is a
kernel/driver/HW problem, not a udev problem - ifconfig gets the information
straight from the /proc (or is it /sys?) filesystem - direct from the
kernel, so udev is not involved - udev can only change the name of the
interface, not cause it to not show up.
Can you do a fresh boot, try modprobing e1000, and then send the output of
dmesg and uname -a?
-James
>
>
> _____________________________________________________________
> Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com
> Join Linux Discussions! --> http://Community.LinuxWaves.com
>
>
[-- Attachment #2: Type: text/html, Size: 1801 bytes --]
next prev parent reply other threads:[~2009-10-04 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 10:15 [gentoo-user] Re: device eth0 does not exist Cinder
2009-10-04 16:33 ` James Ausmus [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-02 9:40 Cinder
2009-10-02 17:51 ` James Ausmus
2009-10-01 8:49 [gentoo-user] " Cinder
2009-10-01 12:35 ` [gentoo-user] " walt
2009-09-30 10:58 Cinder
2009-09-30 12:46 ` Stroller
2009-09-30 12:46 ` Steffen Loos
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=b79f23070910040933h2440ed46lda6a6f585399c1cf@mail.gmail.com \
--to=james.ausmus@gmail.com \
--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