adsl daemon not starting

innn · 2011-07-23 19:27:05

I have pppoe connection, in the past worked very well, I 've recently replaced an antique motherboard 10 years old with a 775 socket Asrock, chipset G41 that has Realtek 8102E/8103E on-board lan and I have since then always had to manually do sudo /etc/rc.d/adsl start
That's when I have adsl backgrounded in rc.conf. I mention that pppoe is configured correctly like always did for some years now. It's a real pain starting system and when someone in the family wants to surf the web I have to come and put a daemon to work.
Can anybody help me?

Last edited by innn (2011-07-23 19:27:52)

karol · 2011-07-23 19:54:23

So adsl doesn't start at all and you have to manually start it? Backgrounding it means it can take some time to start, the removing the '@' and see if it start on its own.

innn · 2011-07-23 20:25:39

hi, I've also tried starting it without the @ and it takes its time to start eventually failing. All daemons are Done this one FAIL. I looked up the web for any driver issues with that realtek and found some debian user that removed the kernel compiled driver r6189 (this one appears in my system also) and installed another driver r8101 ( one that apparently comes from the realtek site), I tried that also but it sucks cause I dont know what to blacklist how to do it etc. After restart I had to manually start the adsl daemon too. So , the net is working only if someone starts that daemon, but why it doesn't start automatically ?

karol · 2011-07-23 20:30:16

http://mailman.archlinux.org/pipermail/ … 20411.html - but it's fixed already and if it weren't, the network wouldn't start at all.

Can you post your rc.conf?

Last edited by karol (2011-07-23 20:33:32)

innn · 2011-07-24 06:27:13

ok, here's my rc.conf:

#
# /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"
DAEMON_LOCALE="no"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Bucharest"
KEYMAP="us"
CONSOLEFONT=
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=(r8101)

# 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="x"
# 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=
address=
netmask=
gateway=

# 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 !acpid !network !netfs crond !dbus !ppp @adsl @alsa)

karol · 2011-07-24 06:36:17

Just a quick question: why did you did you disable dbus?

DAEMONS=(!hwclock syslog-ng !acpid !network !netfs crond !dbus !ppp @adsl @alsa)

innn · 2011-07-24 06:58:02

sorry , I've just noticed too, corrected.

innn · 2011-07-26 08:25:29

no other suggestion, please?

SanskritFritz · 2011-07-26 08:52:16

You have to look in the logfiles and dmesg, maybe there is a hint.

innn · 2011-07-26 16:06:34

ok, this is from /var/log/daemon.log

Jul 26 18:41:46 localhost [    1.090100] udevd[48]: starting version 171
Jul 26 18:41:46 localhost [    3.435828] udevd[235]: starting version 171
Jul 26 18:41:48 localhost pppd[679]: pppd 2.4.5 started by root, uid 0
Jul 26 18:41:48 localhost pppd[679]: Using interface ppp0
Jul 26 18:41:48 localhost pppd[679]: Connect: ppp0 <--> /dev/pts/0
Jul 26 18:41:49 localhost dbus[630]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Jul 26 18:41:50 localhost dbus[630]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Jul 26 18:41:50 localhost polkitd[798]: started daemon version 0.101 using authority implementation `local' version `0.101'
Jul 26 18:41:50 localhost dbus[630]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jul 26 18:41:50 localhost dbus[630]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Jul 26 18:42:19 localhost pppd[679]: LCP: timeout sending Config-Requests
Jul 26 18:42:19 localhost pppd[679]: Connection terminated.
Jul 26 18:42:19 localhost pppd[679]: Modem hangup
Jul 26 18:42:21 localhost pppd[1184]: pppd 2.4.5 started by root, uid 0
Jul 26 18:42:21 localhost pppd[1184]: Using interface ppp0
Jul 26 18:42:21 localhost pppd[1184]: Connect: ppp0 <--> /dev/pts/2
Jul 26 18:42:21 localhost pppoe[1187]: PADS: Service-Name: 'ftth'
Jul 26 18:42:21 localhost pppoe[1187]: PPP session is 115 (0x73)
Jul 26 18:42:21 localhost pppd[1184]: PAP authentication succeeded
Jul 26 18:42:21 localhost pppd[1184]: Cannot determine ethernet address for proxy ARP
Jul 26 18:42:21 localhost pppd[1184]: local  IP address 79.114.206.165
Jul 26 18:42:21 localhost pppd[1184]: remote IP address 10.0.0.1
Jul 26 18:42:21 localhost pppd[1184]: primary   DNS address 213.154.124.1
Jul 26 18:42:21 localhost pppd[1184]: secondary DNS address 193.231.252.1
Jul 26 18:42:23 localhost pppoe[689]: Timeout waiting for PADO packets
Jul 26 18:42:23 localhost pppd[679]: Exit.

messages.log

Jul 26 18:41:47 localhost kernel: [   10.999453] r8101: eth0: link up
Jul 26 18:41:47 localhost kernel: [   11.065529] PPP generic driver version 2.4.2
Jul 26 18:41:48 localhost pppd[679]: pppd 2.4.5 started by root, uid 0
Jul 26 18:41:48 localhost pppd[679]: Using interface ppp0
Jul 26 18:41:48 localhost pppd[679]: Connect: ppp0 <--> /dev/pts/0
Jul 26 18:41:49 localhost dbus[630]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Jul 26 18:41:50 localhost dbus[630]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Jul 26 18:41:50 localhost polkitd[798]: started daemon version 0.101 using authority implementation `local' version `0.101'
Jul 26 18:41:50 localhost dbus[630]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jul 26 18:41:50 localhost dbus[630]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Jul 26 18:41:58 localhost kernel: [   21.941423] chromium-sandbo (894): /proc/892/oom_adj is deprecated, please use /proc/892/oom_score_adj instead.
Jul 26 18:42:19 localhost pppd[679]: LCP: timeout sending Config-Requests
Jul 26 18:42:19 localhost pppd[679]: Connection terminated.
Jul 26 18:42:19 localhost pppd[679]: Modem hangup
Jul 26 18:42:21 localhost pppd[1184]: pppd 2.4.5 started by root, uid 0
Jul 26 18:42:21 localhost pppd[1184]: Using interface ppp0
Jul 26 18:42:21 localhost pppd[1184]: Connect: ppp0 <--> /dev/pts/2
Jul 26 18:42:21 localhost pppoe[1187]: PPP session is 115 (0x73)
Jul 26 18:42:21 localhost pppd[1184]: PAP authentication succeeded
Jul 26 18:42:21 localhost kernel: [   44.479616] PPP BSD Compression module registered
Jul 26 18:42:21 localhost pppd[1184]: local  IP address 79.114.206.165
Jul 26 18:42:21 localhost pppd[1184]: remote IP address 10.0.0.1
Jul 26 18:42:21 localhost pppd[1184]: primary   DNS address 213.154.124.1
Jul 26 18:42:21 localhost pppd[1184]: secondary DNS address 193.231.252.1
Jul 26 18:42:23 localhost pppd[679]: Exit.

errors.log

Jul 26 18:42:21 localhost pppd[1184]: Cannot determine ethernet address for proxy ARP
Jul 26 18:42:23 localhost pppoe[689]: Timeout waiting for PADO packets

kernel.log

Jul 26 18:41:47 localhost kernel: [   10.999443] r8101 0000:01:00.0: Not Support EEE
Jul 26 18:41:47 localhost kernel: [   10.999453] r8101: eth0: link up
Jul 26 18:41:47 localhost kernel: [   11.065529] PPP generic driver version 2.4.2
Jul 26 18:41:58 localhost kernel: [   21.941423] chromium-sandbo (894): /proc/892/oom_adj is deprecated, please use /proc/892/oom_score_adj instead.
Jul 26 18:42:21 localhost kernel: [   44.479616] PPP BSD Compression module registered

basically these 3 or 4 lines I found in dmesg also

innn · 2011-07-29 18:09:17

no one else has any idea ?

MoonSwan · 2011-07-29 19:53:38

OK maybe I'm seeing things but your rc.conf contains no line that refers to your NIC at all. And I don't see netcfg in your daemons line...soooo...uh you might try to set that up. Netcfg has support for ppoe too. Wiki has good instructions to use it but I'll nutshell it for you.

1. Get netcfg from repos. (No brainer I know)
2. Copy the profile you wish to use from /etc/network.d/example to /etc/network.d/.
3. Configure the profile to meet your needs.
4. Run "netcfg -u profile-name-that you edited earlier.
5. Have a large beer for being so clever to solve this!

I'm going to apologise in advance if this fails or isn't useful (I'm canadian so I kind of have to apologise before-hand...we have a reputation to keep up you know!)

innn · 2011-08-06 05:32:54

it's ok canadian man
it works, I've done steps 1-4 and left 5 out 'cause I don't like beers
now the thing is having the same weird behaviour of not starting automatically and very hard starting manually
so, I looked for realtek 8139d network pci card put that in the computer blacklist in teh bios the onboard lan , also clean installed arch and pppoe-setup and put adsl daemon to start at boot (the old way without messing with netcfg again) , all that again and no internet yesterday whenever doing "adsl start" or "pppoe-start" , but today it works , so for a while I'll just wait for it to manifest and be back when I'll encounter another anomaly,
thank you
and this is not Solved yet, no, no

innn · 2011-08-10 12:00:00

something crossed my mind, is it possible this is because I dual boot with windows and shutdown windows by means of hibernating it, I just tried to shut it down normally and booting linux the network connection worked, but is it normal ?
I will stop doing it , even using windows for that matter, but every time something bothering appears, thank you anyway

innn · 2011-08-11 08:22:07

this is a hell for me, pppoe connection used to be easy in the past, to recap, what I used to do was

pppoe-setup

and have this line of daemons in rc.conf :

syslog-ng dbus crond adsl alsa

and it worked now the same thing does not work at all, the adsl daemon I suspect is the major culprit here , I somehow guess no longer is in charge of connecting ppp because I try manually starting it tens of times and no longer connects anything.
Today I got rid of that and tried once again netcfg the way MoonSwan described , so I have these in /etc/network.d/ppp:

CONNECTION='ppp'
INTERFACE='eth0'
PEER='rds'
PPP_TIMEOUT='10'

and /etc/rc.conf looks like this:

syslog-ng dbus crond network net-profiles alsa

and what I get at boot is

Aug 11 11:02:03 localhost kernel: [    9.070754] 8139too 0000:03:01.0: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Aug 11 11:02:03 localhost dhcpcd[654]: version 5.2.12 starting
Aug 11 11:02:03 localhost dhcpcd[654]: eth0: broadcasting for a lease
Aug 11 11:02:33 localhost pppd[746]: Plugin rp-pppoe.so loaded.
Aug 11 11:02:33 localhost pppd[746]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.5
Aug 11 11:02:34 localhost pppd[746]: pppd 2.4.5 started by root, uid 0
Aug 11 11:02:34 localhost kernel: [   39.553958] IPv6: Loaded, but administratively disabled, reboot required to enable
Aug 11 11:02:34 localhost pppd[746]: PPP session is 542
Aug 11 11:02:34 localhost kernel: [   39.573808] NET: Registered protocol family 24
Aug 11 11:02:34 localhost pppd[746]: Connected to 00:14:5e:95:fb:cd via interface eth0
Aug 11 11:02:34 localhost pppd[746]: Using interface ppp0
Aug 11 11:02:34 localhost pppd[746]: Connect: ppp0 <--> eth0
Aug 11 11:02:57 localhost pppd[746]: Connection terminated.

Please, someone tell me what am I doing wrong or not doing right, what is a proper way to have pppoe connection done?

So this is a call to all pppoe users that have a working pppoe solution and kindly want to share it, thank you

bernarcher · 2011-08-11 12:01:30

innn wrote:

something crossed my mind, is it possible this is because I dual boot with windows and shutdown windows by means of hibernating it, I just tried to shut it down normally and booting linux the network connection worked, but is it normal ?

Just a shot in the dark:

Do you keep the DSL connection open when you hibernate Windows? This might keep the pppoe interface connection settings set by windows active, even if not really used, which then conflict with the interface initialization the linux driver attempts.

So, does shutting down your DSL connection before hibernating Windows help?

Last edited by bernarcher (2011-08-11 12:02:32)

innn · 2011-08-11 14:18:49

I renounced the habit to hibernate windows , now turning it off normally and still get the troubles.

innn · 2011-08-12 08:43:11

now it works with netcfg, but does someone know how to make it use opendns nameservers, I guess I have to put them inside same file /etc/network.d/ppp as a line but not know exact syntax
right now the said nameservers are in resolv.conf but not used at all

Last edited by innn (2011-08-13 05:13:30)

Arch Linux

#1 2011-07-23 19:27:05

adsl daemon not starting

#2 2011-07-23 19:54:23

Re: adsl daemon not starting

#3 2011-07-23 20:25:39

Re: adsl daemon not starting

#4 2011-07-23 20:30:16

Re: adsl daemon not starting

#5 2011-07-24 06:27:13

Re: adsl daemon not starting

#6 2011-07-24 06:36:17

Re: adsl daemon not starting

#7 2011-07-24 06:58:02

Re: adsl daemon not starting

#8 2011-07-26 08:25:29

Re: adsl daemon not starting

#9 2011-07-26 08:52:16

Re: adsl daemon not starting

#10 2011-07-26 16:06:34

Re: adsl daemon not starting

#11 2011-07-29 18:09:17

Re: adsl daemon not starting

#12 2011-07-29 19:53:38

Re: adsl daemon not starting

#13 2011-08-06 05:32:54

Re: adsl daemon not starting

#14 2011-08-10 12:00:00

Re: adsl daemon not starting

#15 2011-08-11 08:22:07

Re: adsl daemon not starting

#16 2011-08-11 12:01:30

Re: adsl daemon not starting

#17 2011-08-11 14:18:49

Re: adsl daemon not starting

#18 2011-08-12 08:43:11

Re: adsl daemon not starting

Board footer