« previous next »
Pages: [1]   Go Down

Author Topic: Boot order on start-up.  (Read 1389 times)

Offline BJF

  • Hero Member
  • *****
  • Posts: 591
Boot order on start-up.
« on: June 24, 2011, 05:03:05 PM »
Forgive my ignorance, but can the order that things commence loading onto the Desktop at boot be changed?
My workhorse HP NX9005 lappy uses a wifi dongle, and leaving it permanently plugged in is the norm. This produces an early initiation of loading of the wifi following reinstalls, and by the time the Desktop is fully established the connection to the router is up and running. However, having booted up without the dongle plugged in recently I broke it and had to uninstall the thing and reinstall it (Look, Joble! After all our drama and testing your patience those years ago, I can do it myself now!  :D). Now it is the last thing on the list and delays the Desktop noticeably.
Can I move it up the list somehow, and what things should I leave above it if I do.

Thanks Team.
Logged
J.G. Gone but never forgotten.


Monsters are real. Ghosts are real too. They live inside us, and sometimes they win.  -Stephen King.

To activate container, saturate contents with cider or single malt.

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11546
  • ----IOFLU----
Re: Boot order on start-up.
« Reply #1 on: June 24, 2011, 07:13:46 PM »
Quote from: BJF on June 24, 2011, 05:03:05 PM
Forgive my ignorance, but can the order that things commence loading onto the Desktop at boot be changed?
My workhorse HP NX9005 lappy uses a wifi dongle, and leaving it permanently plugged in is the norm. This produces an early initiation of loading of the wifi following reinstalls, and by the time the Desktop is fully established the connection to the router is up and running. However, having booted up without the dongle plugged in recently I broke it and had to uninstall the thing and reinstall it (Look, Joble! After all our drama and testing your patience those years ago, I can do it myself now!  :D). Now it is the last thing on the list and delays the Desktop noticeably.
Can I move it up the list somehow, and what things should I leave above it if I do.

Thanks Team.

if you enter the command

[root@fatman ~]# ls -l /etc/rc5.d/
total 0
lrwxrwxrwx 1 root root 13 Jun 23 16:27 K01apt -> ../init.d/apt*
lrwxrwxrwx 1 root root 14 May  9  2010 K10pptp -> ../init.d/pptp*
lrwxrwxrwx 1 root root 16 Jun 23 16:27 K49mtinkd -> ../init.d/mtinkd*
lrwxrwxrwx 1 root root 20 Jun 23 16:27 K49netconsole -> ../init.d/netconsole*
lrwxrwxrwx 1 root root 20 Jun  9  2010 K59oki4daemon -> ../init.d/oki4daemon*
lrwxrwxrwx 1 root root 19 Dec 11  2010 S03ip6tables -> ../init.d/ip6tables*
lrwxrwxrwx 1 root root 18 Dec 11  2010 S03iptables -> ../init.d/iptables*
lrwxrwxrwx 1 root root 20 May  9  2010 S09resolvconf -> ../init.d/resolvconf*
lrwxrwxrwx 1 root root 17 Jun 23 16:27 S10network -> ../init.d/network*
lrwxrwxrwx 1 root root 16 Sep 24  2010 S11auditd -> ../init.d/auditd*
lrwxrwxrwx 1 root root 16 May  9  2010 S12syslog -> ../init.d/syslog*
lrwxrwxrwx 1 root root 20 May  9  2010 S13irqbalance -> ../init.d/irqbalance*
lrwxrwxrwx 1 root root 15 Jun 23 15:42 S14acpid -> ../init.d/acpid*
lrwxrwxrwx 1 root root 14 May  9  2010 S17alsa -> ../init.d/alsa*
lrwxrwxrwx 1 root root 15 May  9  2010 S18sound -> ../init.d/sound*
lrwxrwxrwx 1 root root 17 May  9  2010 S29numlock -> ../init.d/numlock*
lrwxrwxrwx 1 root root 17 Mar 29 04:47 S30vboxdrv -> ../init.d/vboxdrv*
lrwxrwxrwx 1 root root 25 Mar 29 04:47 S35vboxweb-service -> ../init.d/vboxweb-service*
lrwxrwxrwx 1 root root 13 May  9  2010 S40atd -> ../init.d/atd*
lrwxrwxrwx 1 root root 20 Jun 23 16:27 S50network-up -> ../init.d/network-up*
lrwxrwxrwx 1 root root 14 Jun 23 16:27 S51cups -> ../init.d/cups*
lrwxrwxrwx 1 root root 13 Jun 23 16:27 S51xfs -> ../init.d/xfs*
lrwxrwxrwx 1 root root 20 Jun 23 16:27 S55nfs-common -> ../init.d/nfs-common*
lrwxrwxrwx 1 root root 14 May 17  2010 S56ntpd -> ../init.d/ntpd*
lrwxrwxrwx 1 root root 17 May  9  2010 S56pktcdvd -> ../init.d/pktcdvd*
lrwxrwxrwx 1 root root 16 May  9  2010 S56xinetd -> ../init.d/xinetd*
lrwxrwxrwx 1 root root 16 Jun 23 16:27 S57mysqld -> ../init.d/mysqld*
lrwxrwxrwx 1 root root 19 Jun 23 16:27 S57saslauthd -> ../init.d/saslauthd*
lrwxrwxrwx 1 root root 15 Jun 23 16:27 S57snmpd -> ../init.d/snmpd*
lrwxrwxrwx 1 root root 14 Jun 23 16:27 S57sshd -> ../init.d/sshd*
lrwxrwxrwx 1 root root 20 Jun 23 15:42 S60nfs-server -> ../init.d/nfs-server*
lrwxrwxrwx 1 root root 15 May  9  2010 S60uuidd -> ../init.d/uuidd*
lrwxrwxrwx 1 root root 20 Jun 23 16:27 S83messagebus -> ../init.d/messagebus*
lrwxrwxrwx 1 root root 22 Jun 23 16:27 S84avahi-daemon -> ../init.d/avahi-daemon*
lrwxrwxrwx 1 root root 19 Jun 23 16:27 S84haldaemon -> ../init.d/haldaemon*
lrwxrwxrwx 1 root root 19 Jun 23 16:27 S84udev-post -> ../init.d/udev-post*
lrwxrwxrwx 1 root root 12 Jun 23 16:27 S85dm -> ../init.d/dm*
lrwxrwxrwx 1 root root 20 Jun 23 16:27 S86atieventsd -> ../init.d/atieventsd*
lrwxrwxrwx 1 root root 15 Mar 28 20:13 S90crond -> ../init.d/crond*
lrwxrwxrwx 1 root root 20 Jun 23 16:27 S90partimaged -> ../init.d/partimaged*
lrwxrwxrwx 1 root root 15 Sep 24  2010 S90squid -> ../init.d/squid*
lrwxrwxrwx 1 root root 17 May  9  2010 S95kheader -> ../init.d/kheader*
lrwxrwxrwx 1 root root 11 Jun  5  2010 S99local -> ../rc.local*

The numbers following the S indicate the start order of each service. To make your wifi start earlier give it a lower number.
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline BJF

  • Hero Member
  • *****
  • Posts: 591
Re: Boot order on start-up.
« Reply #2 on: June 24, 2011, 07:56:44 PM »
Bless you, OP. I'll give it a go when the dark turns on.
Any cautions for elevating the load point? How soon? After (something else)? Not before (something)?
Logged
J.G. Gone but never forgotten.


Monsters are real. Ghosts are real too. They live inside us, and sometimes they win.  -Stephen King.

To activate container, saturate contents with cider or single malt.

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11546
  • ----IOFLU----
Re: Boot order on start-up.
« Reply #3 on: June 24, 2011, 08:17:02 PM »
Quote from: BJF on June 24, 2011, 07:56:44 PM
Bless you, OP. I'll give it a go when the dark turns on.
Any cautions for elevating the load point? How soon? After (something else)? Not before (something)?

Don't have wifi myself, but would think somewhere about right after the network kicks in, which is S10 on my machine. For all I know about it it could be part of the network start itself.

Edit: Doing a cat on /etc/rc5.d/S10network it does check for, and initiate the wifi within the script.
« Last Edit: June 24, 2011, 08:24:31 PM by old-polack »
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline BJF

  • Hero Member
  • *****
  • Posts: 591
Re: Boot order on start-up.
« Reply #4 on: June 24, 2011, 11:03:14 PM »
OP: I have this. Note S82.
[mdm@localhost ~]$ su root
Password:
[root@localhost mdm]# ls -l /etc/rc5.d/
total 0
lrwxrwxrwx 1 root root 14 Dec 17  2010 K10pptp -> ../init.d/pptp*
lrwxrwxrwx 1 root root 16 Jun 10 17:34 K49mtinkd -> ../init.d/mtinkd*
lrwxrwxrwx 1 root root 20 Jun 10 17:34 K49netconsole -> ../init.d/netconsole*
lrwxrwxrwx 1 root root 18 Dec 17  2010 S03iptables -> ../init.d/iptables*
lrwxrwxrwx 1 root root 20 Dec 17  2010 S09resolvconf -> ../init.d/resolvconf*
lrwxrwxrwx 1 root root 14 May 20 08:12 S09wlan -> ../init.d/wlan*
lrwxrwxrwx 1 root root 17 Jun 10 17:34 S10network -> ../init.d/network*
lrwxrwxrwx 1 root root 16 May 15 10:21 S12syslog -> ../init.d/syslog*
lrwxrwxrwx 1 root root 20 Dec 17  2010 S13irqbalance -> ../init.d/irqbalance*
lrwxrwxrwx 1 root root 15 May 31 14:19 S14acpid -> ../init.d/acpid*
lrwxrwxrwx 1 root root 14 Dec 17  2010 S17alsa -> ../init.d/alsa*
lrwxrwxrwx 1 root root 15 Dec 17  2010 S18sound -> ../init.d/sound*
lrwxrwxrwx 1 root root 14 May 15 10:07 S26apmd -> ../init.d/apmd*
lrwxrwxrwx 1 root root 13 May 15 10:21 S40atd -> ../init.d/atd*
lrwxrwxrwx 1 root root 20 Jun 10 17:34 S50network-up -> ../init.d/network-up*
lrwxrwxrwx 1 root root 14 Jun 10 17:34 S51cups -> ../init.d/cups*
lrwxrwxrwx 1 root root 17 Jun 10 17:34 S51rpcbind -> ../init.d/rpcbind*
lrwxrwxrwx 1 root root 13 Jun 10 17:34 S51xfs -> ../init.d/xfs*
lrwxrwxrwx 1 root root 20 Jun 10 17:34 S55nfs-common -> ../init.d/nfs-common*
lrwxrwxrwx 1 root root 15 Jun 10 17:34 S56netfs -> ../init.d/netfs*
lrwxrwxrwx 1 root root 14 Jun 10 17:30 S56ntpd -> ../init.d/ntpd*
lrwxrwxrwx 1 root root 16 May 15 10:21 S56xinetd -> ../init.d/xinetd*
lrwxrwxrwx 1 root root 19 Jun 10 17:34 S57saslauthd -> ../init.d/saslauthd*
lrwxrwxrwx 1 root root 19 Jun 10 17:34 S57shorewall -> ../init.d/shorewall*
lrwxrwxrwx 1 root root 15 Jun 10 17:34 S57snmpd -> ../init.d/snmpd*
lrwxrwxrwx 1 root root 14 Jun 10 17:34 S57sshd -> ../init.d/sshd*
lrwxrwxrwx 1 root root 20 Jun 10 17:34 S60nfs-server -> ../init.d/nfs-server*
lrwxrwxrwx 1 root root 15 Dec 17  2010 S60uuidd -> ../init.d/uuidd*
lrwxrwxrwx 1 root root 22 Jun 10 17:34 S82network-auth -> ../init.d/network-auth*
lrwxrwxrwx 1 root root 20 Jun 10 17:34 S83messagebus -> ../init.d/messagebus*
lrwxrwxrwx 1 root root 22 Jun 10 17:34 S84avahi-daemon -> ../init.d/avahi-daemon*
lrwxrwxrwx 1 root root 19 Jun 10 17:34 S84haldaemon -> ../init.d/haldaemon*
lrwxrwxrwx 1 root root 19 Jun 10 17:34 S84udev-post -> ../init.d/udev-post*
lrwxrwxrwx 1 root root 12 Jun 10 17:34 S85dm -> ../init.d/dm*
lrwxrwxrwx 1 root root 15 May 15 11:19 S90crond -> ../init.d/crond*
lrwxrwxrwx 1 root root 17 May 15 10:21 S95kheader -> ../init.d/kheader*
lrwxrwxrwx 1 root root 21 May 15 10:07 S99laptop-mode -> ../init.d/laptop-mode*
lrwxrwxrwx 1 root root 11 Dec 17  2010 S99local -> ../rc.local*
[root@localhost mdm]#

I won't change anything yet because of the S09 and S10 being where they ought, but have you an idea what part S82 might play in this?

Thanks,
John.
Logged
J.G. Gone but never forgotten.


Monsters are real. Ghosts are real too. They live inside us, and sometimes they win.  -Stephen King.

To activate container, saturate contents with cider or single malt.

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11546
  • ----IOFLU----
Re: Boot order on start-up.
« Reply #5 on: June 24, 2011, 11:47:09 PM »
Quote from: BJF on June 24, 2011, 11:03:14 PM
OP: I have this. Note S82.
[mdm@localhost ~]$ su root
Password:
[root@localhost mdm]# ls -l /etc/rc5.d/
total 0
lrwxrwxrwx 1 root root 14 Dec 17  2010 K10pptp -> ../init.d/pptp*
lrwxrwxrwx 1 root root 16 Jun 10 17:34 K49mtinkd -> ../init.d/mtinkd*
lrwxrwxrwx 1 root root 20 Jun 10 17:34 K49netconsole -> ../init.d/netconsole*
lrwxrwxrwx 1 root root 18 Dec 17  2010 S03iptables -> ../init.d/iptables*
lrwxrwxrwx 1 root root 20 Dec 17  2010 S09resolvconf -> ../init.d/resolvconf*
lrwxrwxrwx 1 root root 14 May 20 08:12 S09wlan -> ../init.d/wlan*
lrwxrwxrwx 1 root root 17 Jun 10 17:34 S10network -> ../init.d/network*
lrwxrwxrwx 1 root root 16 May 15 10:21 S12syslog -> ../init.d/syslog*
lrwxrwxrwx 1 root root 20 Dec 17  2010 S13irqbalance -> ../init.d/irqbalance*
lrwxrwxrwx 1 root root 15 May 31 14:19 S14acpid -> ../init.d/acpid*
lrwxrwxrwx 1 root root 14 Dec 17  2010 S17alsa -> ../init.d/alsa*
lrwxrwxrwx 1 root root 15 Dec 17  2010 S18sound -> ../init.d/sound*
lrwxrwxrwx 1 root root 14 May 15 10:07 S26apmd -> ../init.d/apmd*
lrwxrwxrwx 1 root root 13 May 15 10:21 S40atd -> ../init.d/atd*
lrwxrwxrwx 1 root root 20 Jun 10 17:34 S50network-up -> ../init.d/network-up*
lrwxrwxrwx 1 root root 14 Jun 10 17:34 S51cups -> ../init.d/cups*
lrwxrwxrwx 1 root root 17 Jun 10 17:34 S51rpcbind -> ../init.d/rpcbind*
lrwxrwxrwx 1 root root 13 Jun 10 17:34 S51xfs -> ../init.d/xfs*
lrwxrwxrwx 1 root root 20 Jun 10 17:34 S55nfs-common -> ../init.d/nfs-common*
lrwxrwxrwx 1 root root 15 Jun 10 17:34 S56netfs -> ../init.d/netfs*
lrwxrwxrwx 1 root root 14 Jun 10 17:30 S56ntpd -> ../init.d/ntpd*
lrwxrwxrwx 1 root root 16 May 15 10:21 S56xinetd -> ../init.d/xinetd*
lrwxrwxrwx 1 root root 19 Jun 10 17:34 S57saslauthd -> ../init.d/saslauthd*
lrwxrwxrwx 1 root root 19 Jun 10 17:34 S57shorewall -> ../init.d/shorewall*
lrwxrwxrwx 1 root root 15 Jun 10 17:34 S57snmpd -> ../init.d/snmpd*
lrwxrwxrwx 1 root root 14 Jun 10 17:34 S57sshd -> ../init.d/sshd*
lrwxrwxrwx 1 root root 20 Jun 10 17:34 S60nfs-server -> ../init.d/nfs-server*
lrwxrwxrwx 1 root root 15 Dec 17  2010 S60uuidd -> ../init.d/uuidd*
lrwxrwxrwx 1 root root 22 Jun 10 17:34 S82network-auth -> ../init.d/network-auth*
lrwxrwxrwx 1 root root 20 Jun 10 17:34 S83messagebus -> ../init.d/messagebus*
lrwxrwxrwx 1 root root 22 Jun 10 17:34 S84avahi-daemon -> ../init.d/avahi-daemon*
lrwxrwxrwx 1 root root 19 Jun 10 17:34 S84haldaemon -> ../init.d/haldaemon*
lrwxrwxrwx 1 root root 19 Jun 10 17:34 S84udev-post -> ../init.d/udev-post*
lrwxrwxrwx 1 root root 12 Jun 10 17:34 S85dm -> ../init.d/dm*
lrwxrwxrwx 1 root root 15 May 15 11:19 S90crond -> ../init.d/crond*
lrwxrwxrwx 1 root root 17 May 15 10:21 S95kheader -> ../init.d/kheader*
lrwxrwxrwx 1 root root 21 May 15 10:07 S99laptop-mode -> ../init.d/laptop-mode*
lrwxrwxrwx 1 root root 11 Dec 17  2010 S99local -> ../rc.local*
[root@localhost mdm]#

I won't change anything yet because of the S09 and S10 being where they ought, but have you an idea what part S82 might play in this?

Thanks,
John.


Well, it and S09wlan are the two I don't have, so would guess it has something to do with it, and it is loaded rather late. Someone that actually has wifi could also check to see where it is in their start up order. If anyone has it starting earlier, and has no delay or problems with their wifi, I'd go with what they show.

Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline ThirdOfSix

  • Hero Member
  • *****
  • Posts: 745
Re: Boot order on start-up.
« Reply #6 on: June 25, 2011, 12:42:23 AM »
I don't mean to intrude here.

But is there any chance that you have  a remaster created on that machine before the recent change?

If so, boot from it and see what the order used to be.

This situation illustrates one of the really powerful benefits of having the remaster mechanism and using it.

It makes troubleshooting when things seem to have changed so much easier.

God luck.
Logged

Offline BJF

  • Hero Member
  • *****
  • Posts: 591
Re: Boot order on start-up.
« Reply #7 on: June 25, 2011, 02:21:00 AM »
Sorry, but no remaster. I haven't found the time to try and make one with only CD's to write to optically and it sounds a bit daunting from down here on the learning curve.
In this case it may just be a case of slow recognition of the dongle which uses an unwrapped AR5523 ndiswrapper as a driver and lives on a bit of a knife-edge for stability. What I will probably do without better advice is to wait for LXDE 2011.6 and do a fresh install with the thing in place and see what happens.
Logged
J.G. Gone but never forgotten.


Monsters are real. Ghosts are real too. They live inside us, and sometimes they win.  -Stephen King.

To activate container, saturate contents with cider or single malt.

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: Boot order on start-up.
« Reply #8 on: June 25, 2011, 06:44:09 AM »
Hi BJF,

There is flag, in network card configuration, about to activate the card on boot or not.  Did you tried to turn the flag off ?

AS
Logged

tedlane

  • Guest
Re: Boot order on start-up.
« Reply #9 on: June 26, 2011, 07:06:33 PM »
Not an expert but you have two S09's.
It might be better to delay S09wlan until after resolveconf. IOW issue the following as root to change the two network connection scripts to run after the resolveconf script has finished:
mv /etc/rc5.d/S09wlan S10wlan
mv /etc/rc5.d/S10network S11network

I'm not sure that it will make a difference but from memory startup scripts that rely on others should be "later" in the order. I don't know whether wlan has a specific reliance on resolveconf being complete, but you never know.

This change should not affect anything else in the boot order and does not affect anything within the startup scripts, so should be safe.

ted

Logged

Online kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3982
Re: Boot order on start-up.
« Reply #10 on: June 27, 2011, 04:44:53 AM »
wlan should be started before network in order for network to recognise it, and it starts after resolveconf because S09w is after S09r. There is therefore no need to change the order of those entries, and it will upset the system when other things are added or removed if you do.

Read man chkconfig to learn what options you have. chkconfig network-auth resetpriorities or chkconfig network-auth off followed by chkconfig network-auth on look like good bets.

Far better than messing things up by manual renaming.
Logged
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf
Pages: [1]   Go Up
« previous next »