You are not logged in.

#1 2011-07-28 17:02:48

flamelab
Member
From: Athens, Hellas (Greece)
Registered: 2007-12-26
Posts: 2,160

[SOLVED] The r8169 is not loaded through rc.conf with Linux 3.0 kernel

Well, i have added r8169 in rc.conf MODULES array, but it isn't loaded with Linux 3 kernel.

I'm forced to add a modprobe line AND an to restart the network daemon through rc.local. What the...........

Last edited by flamelab (2011-08-01 20:22:22)

Offline

#2 2011-07-28 17:44:56

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819
Website

Re: [SOLVED] The r8169 is not loaded through rc.conf with Linux 3.0 kernel

What feedback do you get when you load it manually?


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#3 2011-07-28 20:49:48

flamelab
Member
From: Athens, Hellas (Greece)
Registered: 2007-12-26
Posts: 2,160

Re: [SOLVED] The r8169 is not loaded through rc.conf with Linux 3.0 kernel

This is from the dmesg log, the output is from the rc.local command. The exact same message is printed if I do this manually.

[   16.416603] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[   16.416625] r8169 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   16.416743] r8169 0000:04:00.0: setting latency timer to 64
[   16.416799] r8169 0000:04:00.0: irq 46 for MSI/MSI-X
[   16.417069] r8169 0000:04:00.0: eth0: RTL8168d/8111d at 0xffffc90000656000, 00:24:1d:d3:aa:63, XID 083000c0 IRQ 46

Offline

#4 2011-07-28 22:24:33

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819
Website

Re: [SOLVED] The r8169 is not loaded through rc.conf with Linux 3.0 kernel

How does your rc.conf look?


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#5 2011-07-28 22:27:57

flamelab
Member
From: Athens, Hellas (Greece)
Registered: 2007-12-26
Posts: 2,160

Re: [SOLVED] The r8169 is not loaded through rc.conf with Linux 3.0 kernel

Here it is:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
#   Note: Using "localtime" is discouraged.
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
# VERBOSE: Verbose level (from 1 to 8). man 3 syslog for level info
#
LOCALE="en_US.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Athens"
KEYMAP="us"
CONSOLEFONT=iso07u-16.psfu.gz
CONSOLEMAP=
USECOLOR="yes"
VERBOSE="3"
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
#   Replace every !module by an entry as on the following line in a file in
#   /etc/modprobe.d:
#     blacklist module
#   See "man modprobe.conf" for details.
#
MODULES=(r8169 mii !pcspkr snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-codec snd-hda-intel soundcore acpi-cpufreq cpufreq_ondemand cpufreq_powersave cpufreq_conservative cpufreq-userspace coretemp it87)

# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30

# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"

# Scan for BTRFS volumes at startup
USEBTRFS="no"

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="kobol"

# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
#   - interface: name of device (required)
#   - address: IP address (leave blank for DHCP)
#   - netmask: subnet mask (ignored for DHCP)
#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=eth0
address=192.168.0.2
netmask=255.255.255.0
gateway=192.168.0.1

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
#
DAEMONS=(hwclock syslog-ng network @sensors @dbus @openntpd @acpid @cpufreq @crond)

Offline

#6 2011-07-28 23:20:40

Inxsible
Forum Fellow
From: Chicago
Registered: 2008-06-09
Posts: 9,183

Re: [SOLVED] The r8169 is not loaded through rc.conf with Linux 3.0 kernel

This might not be related to your issue but I see that you are still blacklisting modules in rc.conf. This is not supported any longer. also why are you explicitly loading all modules? Most are auto loaded anyway.

Finally, as an aside, you should pay attention to the comments in the rc.conf file as well, especially this one :

If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.


Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

Offline

#7 2011-07-29 14:00:08

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] The r8169 is not loaded through rc.conf with Linux 3.0 kernel

Check what modules have you blacklisted https://wiki.archlinux.org/index.php/Ke … acklisting

Offline

#8 2011-07-31 02:48:05

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] The r8169 is not loaded through rc.conf with Linux 3.0 kernel

https://bbs.archlinux.org/viewtopic.php … 29#p967829 seems like the issue you're having.

Offline

#9 2011-08-01 15:16:32

flamelab
Member
From: Athens, Hellas (Greece)
Registered: 2007-12-26
Posts: 2,160

Re: [SOLVED] The r8169 is not loaded through rc.conf with Linux 3.0 kernel

Yes, that was the issue, some "phantom" modprobe files that blacklisted all the modules I needed.

Offline

#10 2011-08-01 15:27:20

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] The r8169 is not loaded through rc.conf with Linux 3.0 kernel

Please mark as solved :-)

Offline

Board footer

Powered by FluxBB