[SOLVED] internal nics +fb not working after recompile with kernel 3.3.3
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: -- Slackware for servers -- Debian for desktops --
Posts: 124
Rep:
internal nics +fb not working after recompile with kernel 3.3.3
Hi,
My default debian install is working ok.
Recompiled my kernel with a 3.3.3 kernel and have the following issues :
- framebuffer is not working
(seems like update-initramfs -c -k 3.3.3 did not include it in the image ? )
- internal nics not detected, ifconfig only show "lo"
no messages in dmesg about my internal nics whatsoever.
lsmod does not show e1000e loaded as opposed to the default debian kernel.
If I manually modprobe e1000e, dmesg shows he found both nics eth0 & eth1 but no success when issueing lspci -v or ifconfig... only have "lo" available :-/
Hope you guys can give me some advice
Just installed the latest debianAMD64.
Here some info :
root@jaffa:/# more /etc/debian_version
6.0.4
default debian kernel :
# uname -a
Linux jaffa 2.6.32-5-amd64 #1 SMP Thu Mar 22 17:26:33 UTC 2012 x86_64 GNU/Linux
note : I have the same server with an older setup and kernel 2.6.22.24.02.08 that is using e1000 instead of e1000e as a driver... :
# lspci -v
05:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
Subsystem: Intel Corporation Device 346c
Flags: bus master, fast devsel, latency 0, IRQ 57
Memory at b8c20000 (32-bit, non-prefetchable) [size=128K]
Memory at b8800000 (32-bit, non-prefetchable) [size=4M]
I/O ports at 2020 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-04-23-ff-ff-dd-65-46
Kernel driver in use: e1000e
05:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
Subsystem: Intel Corporation Device 346c
Flags: bus master, fast devsel, latency 0, IRQ 58
Memory at b8c00000 (32-bit, non-prefetchable) [size=128K]
Memory at b8400000 (32-bit, non-prefetchable) [size=4M]
I/O ports at 2000 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-04-23-ff-ff-dd-65-46
Kernel driver in use: e1000e
----------
# grep -ie "e1000\|intel" /boot/config-3.3.3
CONFIG_NET_VENDOR_INTEL=y
# CONFIG_E1000 is not set
CONFIG_E1000E=m
Now you would figure eth0 comes up automatically and takes his config from /etc/networking/interfaces...
No such thing :-(
/etc/init.d/networking restart or # services networking restart doesn't make my interface come up...
The culprit seems to be in /etc/init.d/networking:
If I change the -a to the name of the interface, being eth0 , and I reload the script everything starts to work as a charm !!!
log_warning_msg "Running $0 $1 is deprecated because it may not enable again some interfaces"
log_action_begin_msg "Reconfiguring network interfaces"
#ifdown -a --exclude=lo || true ifdown eth0 --exclude=lo || true
#if ifup -a --exclude=lo; then if ifup eth0 --exclude=lo; then
log_action_end_msg $?
else
log_action_end_msg $?
fi
;;
-------
man ifup/ifdown shows the following for -a
-a, --all
If given to ifup, affect all interfaces marked auto. <-- what the hell is auto ?
so checked my /etc/networking/interfaces :
root@jaffa:/home/ben# more /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.