HOW TO install BOINC with Fedora 9 ?

Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4 · 5

AuthorMessage
Metod, S56RKO

Send message
Joined: 9 Sep 05
Posts: 128
Slovenia
Message 19663 - Posted: 21 Aug 2008, 15:16:08 UTC - in response to Message 19517.  

PS: The following is from /var/log/messages


I've deleted a couple of lines from your messages, but please note time stamps ...

Probably booting kernel and loading network interface driver:

Aug 14 07:26:24 localhost kernel: sis190 Gigabit Ethernet driver 1.2 loaded.
Aug 14 07:26:24 localhost kernel: ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 19 (level, low) -> IRQ 19
Aug 14 07:26:24 localhost kernel: 0000:00:04.0: Read MAC address from EEPROM
Aug 14 07:26:24 localhost kernel: 0000:00:04.0: Unknown PHY transceiver at address 1.
...
Aug 14 07:26:24 localhost kernel: 0000:00:04.0: Using transceiver at address 1 as default.
Aug 14 07:26:24 localhost kernel: 0000:00:04.0: SiS 191 PCI Gigabit Ethernet adapter at f88bc000 (IRQ: 19), 00:1e:33:03:02:ae
Aug 14 07:26:24 localhost kernel: eth0: RGMII mode.
Aug 14 07:26:24 localhost kernel: eth0: Enabling Auto-negotiation.


Then, probably early during initialization, NetworkManager gets started:

Aug 14 07:26:28 localhost NetworkManager: <info>  starting...
Aug 14 07:26:28 localhost NetworkManager: <info>  eth0: Device is fully-supported using driver 'sis190'.


Then something strange: kernel driver declares ethernet link not ready and notifies NetworkManager of it:

Aug 14 07:26:32 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 14 07:26:32 localhost NetworkManager: <info>  (eth0): device state change: 1 -> 2
Aug 14 07:26:32 localhost NetworkManager: <info>  (eth0): bringing up device.
Aug 14 07:26:32 localhost NetworkManager: <info>  (eth0): preparing device.
Aug 14 07:26:32 localhost NetworkManager: <info>  (eth0): deactivating device


And then, after a while, voilá, kernel driver finds ethernet link alive:

Aug 14 07:26:42 localhost kernel: eth0: mii ext = 0000.
Aug 14 07:26:42 localhost NetworkManager: <info>  (eth0): carrier now ON (device state 2)


Then it takes a short while to get network interface configured:

Aug 14 07:26:44 localhost NetworkManager: <info>    address 192.168.11.2
Aug 14 07:26:44 localhost NetworkManager: <info>    netmask 255.255.255.0
Aug 14 07:26:44 localhost NetworkManager: <info>    gateway 192.168.11.1
Aug 14 07:26:44 localhost NetworkManager: <info>    nameserver '192.168.11.1'


If you observe time stamps carefully you can see that it takes 16 seconds between starting network configuration (NetworkManager in your case) and finishing it (marked by LAN connectivity ready).

The most disturbing period of time is those 10 seconds when ethernet link is considered not ready. There are a couple of reasons for that. One is delay caused by peer device (ethernet switch / router) during which some kind of auto-negotiation can take place. This was not so uncommon years ago, but should be almost instant these days. The other possibility is that this is caused by kernel driver and/or userland software (NetworkManager) if parts of network interface (MII transciever in particular) gets reset during some stage of initialization. Some time is then needed to recover.
There are many other possibilities as to why there's a 10 second delay.

As I already wrote in my post, the root of your problems is the fact that network gets configured in background (to speed-up the booting procedure). I also described a good cure: make a sleep-loop until default route gets configured.

Metod ...
ID: 19663 · Report as offensive
Profile MEX
Avatar

Send message
Joined: 23 Sep 05
Posts: 54
Austria
Message 19839 - Posted: 30 Aug 2008, 2:38:37 UTC - in response to Message 19663.  

...
Aug 14 07:26:45 localhost NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Aug 14 07:26:48 localhost boinc_client: Starting Boinc-Daemon, listening on port 31416.
Aug 14 07:26:51 localhost gconfd (gdm-2139): Beenden
Aug 14 07:26:51 localhost gconfd (mex-2281): starting (version 2.22.0), pid 2281 user 'mex'
...


If you observe time stamps carefully you can see that it takes 16 seconds between starting network configuration (NetworkManager in your case) and finishing it (marked by LAN connectivity ready).

The most disturbing period of time is those 10 seconds when ethernet link is considered not ready. There are a couple of reasons for that. One is delay caused by peer device (ethernet switch / router) during which some kind of auto-negotiation can take place. This was not so uncommon years ago, but should be almost instant these days. The other possibility is that this is caused by kernel driver and/or userland software (NetworkManager) if parts of network interface (MII transciever in particular) gets reset during some stage of initialization. Some time is then needed to recover.
There are many other possibilities as to why there's a 10 second delay.

As I already wrote in my post, the root of your problems is the fact that network gets configured in background (to speed-up the booting procedure). I also described a good cure: make a sleep-loop until default route gets configured.
I already have a 15 second sleep-loop in the script starting my BOINC client since a long time, and as the NetworkManager is the source of the problems on my V5535 I will either remove the NetworkManager in the long run or try to solve this problem in a topic in the Fedora community.

But I think something about the problems the NetworkManager is causing should be written in the WIKI and/or the next version of BOINC for f9 should do something to avoid this problem to make it easier for new linux users to use BOINC with startup during boot with f9.

MfG, MEX

0xFF
ID: 19839 · Report as offensive
Milos Jakubicek

Send message
Joined: 19 Feb 08
Posts: 23
Czech Republic
Message 19840 - Posted: 30 Aug 2008, 7:22:49 UTC - in response to Message 19839.  


But I think something about the problems the NetworkManager is causing should be written in the WIKI and/or the next version of BOINC for f9 should do something to avoid this problem to make it easier for new linux users to use BOINC with startup during boot with f9.


Please keep in mind that as far you're the only one experiencing such problems and that we still do not know very much about why it takes so long to bring up your network (...have you at least already test the DHCP response as I suggested?). And that the very reason of this problem is on BOINC side being not capable to use newly available connections, hopefully _this_ will be fixed soon (6.4).

Milos Jakubicek
ID: 19840 · Report as offensive
Profile MEX
Avatar

Send message
Joined: 23 Sep 05
Posts: 54
Austria
Message 20025 - Posted: 7 Sep 2008, 13:55:55 UTC - in response to Message 19840.  

Please keep in mind that as far you're the only one experiencing such problems and that we still do not know very much about why it takes so long to bring up your network (...have you at least already test the DHCP response as I suggested?). And that the very reason of this problem is on BOINC side being not capable to use newly available connections, hopefully _this_ will be fixed soon (6.4).
As far as I know I am not the only one having problems with the new NetworkManager in f9, although most deinstall NetworkManager as soon as they have problems with it and use the old ways of connecting to the Internet.

For me knowing the source ( NetworkManager) of my problems and a way to circumvent ( sleep for at least 12 seconds ) them is good enough.

MfG, MEX

PS: If someone wants to use NetworkManger he should take care of this problems, I dont care about NetworkManager and will deinstall it as soon as it will cause me more problems than now.

0xFF
ID: 20025 · Report as offensive
Bill

Send message
Joined: 2 Oct 08
Posts: 2
Message 20642 - Posted: 2 Oct 2008, 19:48:01 UTC

I received this advice from Fedora Bugzilla.

https://bugzilla.redhat.com/show_bug.cgi?id=453317

"Boinc is probably starting so soon after NetworkManager that the network is not
up yet. It's technically a bug in Boinc that it doesn't wait for a network
connection and periodically re-try to send/grab the data. But for the moment,
you can add the line:

NETWORKWAIT=yes

to /etc/sysconfig/network and startup will block for 10 seconds or until a
network connection is up, whichever is sooner."


It fixed it for me!
ID: 20642 · Report as offensive
Bill

Send message
Joined: 2 Oct 08
Posts: 2
Message 20643 - Posted: 2 Oct 2008, 20:11:13 UTC

Hi;

I am trying to configure the boincmgr display. These are minor display problems. I have boinc-client and boincmgr starting and running successfully on Fedora 9.

I have tried to set the display using ~/.Boinc Manager, but nothing seems to stick.

Some things I would like to set:

1. The hostname. Choices used to drop down in the Advanced Tab; now they are blank and I am unable to figure out where to reconfigure.

2. I would like to configure the overall geometry; size and screen position

3. I would like to set boincmgr to open in workspace 4 when I login. I have sessions set to open boincmgr but it always opens in workspace 1 and I can't find how to change to another workspace.

4. I was playing around and lost my boincmgr automatic connection to boinc client. It should be a simple command to re-configure but I can't find out where and how.

5. If I remember correctly earlier versions of .Boinc Manager had more configuration options. If so, how can I get just a new configuration file?
ID: 20643 · Report as offensive
Previous · 1 · 2 · 3 · 4 · 5

Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?

Copyright © 2022 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.