[gentoo-user] Re: device eth0 does not exist

[gentoo-user] Re: device eth0 does not exist

[Cinder]

>What is the NIC in the box where eth0 isn't showing up?
Intel Corporation 82547EI Gigabit Ethernet Controller
>Is the driver in your kernel?
No. It's a module (e1000) and I watched it compile. I tried a static driver as well.

lspci say's http://pastebin.com/md3578a6

I deleted etc/udev/rules.d/70-persistent-net.rules and rebooted. Now there's a message that loading module e1000 failed, and still device eth0 does not exist as well as device eth1 does not exits, but there are symlinks in /etc/init.d for both.

Thank you:)

_____________________________________________________________
Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com
Join Linux Discussions! --> http://Community.LinuxWaves.com

Re: [gentoo-user] Re: device eth0 does not exist

[Stroller]

On 30 Sep 2009, at 11:58, Cinder wrote:

>> What is the NIC in the box where eth0 isn't showing up?
> Intel Corporation 82547EI Gigabit Ethernet Controller
>> Is the driver in your kernel?
> No. It's a module (e1000) and I watched it compile. I tried a static  
> driver as well.
>
> lspci say's http://pastebin.com/md3578a6
>
> I deleted etc/udev/rules.d/70-persistent-net.rules and rebooted. Now  
> there's a message that loading module e1000 failed, and still device  
> eth0 does not exist as well as device eth1 does not exits, but there  
> are symlinks in /etc/init.d for both.

Just seen this, following my other reply.

`tail -f /var/log/messages` in one window whilst running the `modprobe  
-v e1000` in another.

`dmesg` should show the same stuff as /var/log/messages (in this  
instance, at least), but using `tail -f /var/log/messages` it's easy  
to hit enter a few times (to clear some space on the screen) and then  
see what's happening in real-time. Although there's probably a very  
good reason for it, it's sometimes frustrating that `dmesg` isn't time  
stamped.

Stroller.

Re: [gentoo-user] Re: device eth0 does not exist

[Steffen Loos]

Cinder schrieb:
>> What is the NIC in the box where eth0 isn't showing up?
> Intel Corporation 82547EI Gigabit Ethernet Controller
>> Is the driver in your kernel?
> No. It's a module (e1000) and I watched it compile. I tried a static driver as well.
> 
> lspci say's http://pastebin.com/md3578a6
> 
> I deleted etc/udev/rules.d/70-persistent-net.rules and rebooted. Now there's a message that loading module e1000 failed, and still device eth0 does not exist as well as device eth1 does not exits, but there are symlinks in /etc/init.d for both.
> 
Hm, is it a pci-express device? - then just try to use e1000e module.

If the driver loads w/o problems you should see the device after:
/sbin/ifconfig -a


Steffen

[gentoo-user] Re: device eth0 does not exist

[walt]

On 10/01/2009 01:49 AM, Cinder wrote:
>> Can you show the results of `modprobe -v e1000` please?
> Code:
> # modprobe -v e1000
> FATAL: Module e1000 not found.
>

Try running 'depmod'.

[gentoo-user] Re: device eth0 does not exist

[Cinder]

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

  Thanks. Depmod yielded no results. At least as far as I can tell. I tried with ...

Code:
# depmod -a ; depmod -e -F

 As I recall "Note: the kernel developers warn that you should not configure or compile your kernel as root." >->http://forums.gentoo.org/viewtopic-t-539024.html And that "that there have been bugs in the build process which caused files in the /dev tree to be deleted if run as root"

  I remember distinctly configuring and compiling my kernels as root, but ...

Code:
$ make && make modules_install
snip< (verbos output attached)
rm: cannot remove `include/config/kernel.release': Permission denied
make: *** [include/config/kernel.release] Error 1
... always failed. You always install as root right?

  So I just carried on compiling as root. Could this be part of the problem?
Do I need to compile as user? I don't seem to be able.

_____________________________________________________________
Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com
Join Linux Discussions! --> http://Community.LinuxWaves.com

[-- Attachment #2: make-debugg-user --]
[-- Type: application/octet-stream, Size: 3266 bytes --]

GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for i686-pc-linux-gnu
Reading makefiles...
Reading makefile `Makefile'...
Reading makefile `/usr/src/linux-2.6.30-gentoo-r6/scripts/Kbuild.include' (search path) (no ~ expansion)...
Reading makefile `include/config/auto.conf' (search path) (don't care) (no ~ expansion)...
Reading makefile `include/config/auto.conf.cmd' (search path) (don't care) (no ~ expansion)...
Reading makefile `/usr/src/linux-2.6.30-gentoo-r6/arch/x86/Makefile' (search path) (no ~ expansion)...
Reading makefile `/usr/src/linux-2.6.30-gentoo-r6/arch/x86/Makefile_32.cpu' (search path) (no ~ expansion)...
Reading makefile `..tmp_kallsyms1.o.cmd' (search path) (no ~ expansion)...
Reading makefile `..tmp_kallsyms2.o.cmd' (search path) (no ~ expansion)...
Reading makefile `..tmp_kallsyms3.o.cmd' (search path) (no ~ expansion)...
Reading makefile `..tmp_vmlinux1.cmd' (search path) (no ~ expansion)...
Reading makefile `..tmp_vmlinux2.cmd' (search path) (no ~ expansion)...
Reading makefile `..tmp_vmlinux3.cmd' (search path) (no ~ expansion)...
Reading makefile `.vmlinux.cmd' (search path) (no ~ expansion)...
Reading makefile `.vmlinux.o.cmd' (search path) (no ~ expansion)...
Updating goal targets....
Considering target file `_all'.
 File `_all' does not exist.
  Considering target file `all'.
   File `all' does not exist.
    Considering target file `vmlinux'.
      Considering target file `arch/x86/kernel/vmlinux.lds'.
        Considering target file `init'.
         File `init' does not exist.
          Considering target file `prepare'.
           File `prepare' does not exist.
            Considering target file `prepare0'.
             File `prepare0' does not exist.
              Considering target file `archprepare'.
               File `archprepare' does not exist.
                Considering target file `prepare1'.
                 File `prepare1' does not exist.
                  Considering target file `prepare2'.
                   File `prepare2' does not exist.
                    Considering target file `prepare3'.
                     File `prepare3' does not exist.
                      Considering target file `include/config/kernel.release'.
                        Pruning file `include/config/auto.conf'.
                        Considering target file `FORCE'.
                         File `FORCE' does not exist.
                         Finished prerequisites of target file `FORCE'.
                        Must remake target `FORCE'.
                        Successfully remade target file `FORCE'.
                       Finished prerequisites of target file `include/config/kernel.release'.
                       Prerequisite `include/config/auto.conf' is older than target `include/config/kernel.release'.
                       Prerequisite `FORCE' of target `include/config/kernel.release' does not exist.
                      Must remake target `include/config/kernel.release'.
rm: cannot remove `include/config/kernel.release': Permission denied
make: *** [include/config/kernel.release] Error 1

Re: [gentoo-user] Re: device eth0 does not exist

[James Ausmus]

[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]

On Fri, Oct 2, 2009 at 2:40 AM, Cinder <cinder@linuxwaves.com> wrote:

>  Thanks. Depmod yielded no results. At least as far as I can tell. I tried
> with ...
>
> Code:
> # depmod -a ; depmod -e -F
>
>  As I recall "Note: the kernel developers warn that you should not
> configure or compile your kernel as root." >->
> http://forums.gentoo.org/viewtopic-t-539024.html And that "that there have
> been bugs in the build process which caused files in the /dev tree to be
> deleted if run as root"
>
>  I remember distinctly configuring and compiling my kernels as root, but
> ...
>
> Code:
> $ make && make modules_install
> snip< (verbos output attached)
> rm: cannot remove `include/config/kernel.release': Permission denied
> make: *** [include/config/kernel.release] Error 1
> ... always failed. You always install as root right?
>
>  So I just carried on compiling as root. Could this be part of the problem?
> Do I need to compile as user? I don't seem to be able.
>

No, the kernel should be configured/compiled as root. What is the output of:

uname -a



Thanks!

-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: 2143 bytes --]

[gentoo-user] Re: device eth0 does not exist

[Cinder]

  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.



_____________________________________________________________
Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com
Join Linux Discussions! --> http://Community.LinuxWaves.com

Re: [gentoo-user] Re: device eth0 does not exist

[James Ausmus]

[-- 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 --]