View previous topic :: View next topic |
Author |
Message |
rkfsm Tux's lil' helper
Joined: 03 Jun 2005 Posts: 100 Location: Charleston, SC, USA
|
Posted: Thu Apr 18, 2013 10:43 pm Post subject: [Solved] Network devices not recognized |
|
|
This is a brand new install and the livecd had issues with the adapters, but it worked well enough. My compiled kernel cannot find the devices even when using genkernel. When I boot the livecd, lspci -v gives me this about them:
Quote: | 00:11.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2)
Subsystem: ASUSTeK Computer Inc. Device cb84
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22
Memory at fe02a000 (32-bit, non-prefetchable) [size=4K]
I/O ports at b000 [size=8]
Memory at fe029000 (32-bit, non-prefetchable) [size=256]
Memory at fe028000 (32-bit, non-prefetchable) [size=16]
Capabilities: [44] Power Management version 2
Capabilities: [70] MSI-X: Enable- Count=8 Masked-
Capabilities: [50] MSI: Enable- Count=1/8 Maskable+ 64bit+
Capabilities: [6c] HyperTransport: MSI Mapping Enable- Fixed+
Kernel driver in use: forcedeth
00:12.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2)
Subsystem: ASUSTeK Computer Inc. Device cb84
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21
Memory at fe027000 (32-bit, non-prefetchable) [size=4K]
I/O ports at ac00 [size=8]
Memory at fe026000 (32-bit, non-prefetchable) [size=256]
Memory at fe025000 (32-bit, non-prefetchable) [size=16]
Capabilities: [44] Power Management version 2
Capabilities: [70] MSI-X: Enable- Count=8 Masked-
Capabilities: [50] MSI: Enable- Count=1/8 Maskable+ 64bit+
Capabilities: [6c] HyperTransport: MSI Mapping Enable- Fixed+
Kernel driver in use: forcedeth |
My kernel config has:
Quote: | livecd linux # cat .config | grep FORCEDETH
CONFIG_FORCEDETH=y
|
edit: oops - hit submit instead of preview.
Thank you in advance for any help
edit: More info
Loading the forcedeth module with the msi=0 and msix=0 stwitches has no joy. I noticed that both the driver and udev are changing the name of the interfaces. Both interfaces are being given the same name and, no, the odd named interface doesn't work.
Last edited by rkfsm on Sat Apr 20, 2013 4:36 pm; edited 1 time in total |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Fri Apr 19, 2013 5:04 am Post subject: |
|
|
either
read news (eselect news read all) and create: If /etc/udev/rules.d/80-net-name-slot.rules is an empty file or a
symlink to /dev/null, the new names will be disabled and the kernel will
do all the interface naming, and the resulting names may vary by kernel
configuration, hardware configuration and kernel version. After which you can use etho and eth1
or
run which should give the device names that udev has assigned
create symlinks, add to run level, start, check on them
cd /etc/init.d
ln -s net.lo net.device name that udev has assigned
ln -s net.lo net.other device name that udev has assigned
rc-update add net.device name that udev has assigned default
rc-update add net.device other name that udev has assigned default
/etc/init.d/net.device name that udev has assigned restart
/etc/init.d/net.other device name that udev has assigned restart
ifconfig _________________ Defund the FCC. |
|
Back to top |
|
|
rkfsm Tux's lil' helper
Joined: 03 Jun 2005 Posts: 100 Location: Charleston, SC, USA
|
Posted: Fri Apr 19, 2013 9:00 pm Post subject: |
|
|
Eliminating the msi=0 and msix=0 switches resulted in two odd named interfaces that, when substituted for eth0 and eth1, work fine. Thank you. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|