Hi; When my SuSE 8.1 box boots, It gets to "starting hardware scan on boot" and it takes a very long time to slog through this (several minutes) and earlier today, it never made it through. The only solution I found was to "reload" SuSE (do an update of all packages). So my questions are a) why do I need the "hardware scan"? I have other distros that clearly do not do this. b) which script does this? c) where in /etc might I find a script that lists the overall order of boot scripts particular to SuSE? Thanks for help! -- Tony Alfrey tonyalfrey@earthlink.net "I'd rather be sailing"
On Tue December 2 2003 08:08 pm, Tony Alfrey wrote:
Hi;
When my SuSE 8.1 box boots, It gets to "starting hardware scan on boot" and it takes a very long time to slog through this (several minutes) and earlier today, it never made it through. The only solution I found was to "reload" SuSE (do an update of all packages). So my questions are a) why do I need the "hardware scan"? I have other distros that clearly do not do this. b) which script does this? c) where in /etc might I find a script that lists the overall order of boot scripts particular to SuSE?
Thanks for help!
I believe you can go to YAST --> SYSTEM --> Runlevel editor and disable hardware scan.
-- Tony Alfrey tonyalfrey@earthlink.net "I'd rather be sailing"
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 12/02/03 20:12 + +----------------------------------------------------------------------------+ "If it ain't broke, don't step on it." --ALF
Tony Alfrey <tonyalfrey@earthlink.net> [2 Dec 2003 17:08:23 -0800]:
a) why do I need the "hardware scan"? I have other distros that clearly do not do this.
Many users want the automatic detection of new hardware like they're used to under Win*.
b) which script does this?
/etc/init.d/hwscan. If you want to disable the scan at boot-up, just issue an 'insserv -r hwscan'.
c) where in /etc might I find a script that lists the overall order of boot scripts particular to SuSE?
I know of none. Philipp -- Philipp Thomas work: pthomas AT suse DOT de SUSE LINUX AG private: philipp DOT thomas AT t-link DOT de
Le mercredi 03 décembre 2003, 02:30:28 ou environ Philipp Thomas <philipp.thomas@t-link.de> a écrit:
Tony Alfrey <tonyalfrey@earthlink.net> [2 Dec 2003 17:08:23 -0800]:
a) why do I need the "hardware scan"? I have other distros that clearly do not do this.
Many users want the automatic detection of new hardware like they're used to under Win*.
Now I know what's the use of that damned "hardware scan". It is what we can call the "gameboy syndrom". Now I'll type use 'hwinfo --short --usb' if I want to know on which /dev/sd* my usb storage disk is linked.
b) which script does this?
/etc/init.d/hwscan. If you want to disable the scan at boot-up, just issue an 'insserv -r hwscan'.
c) where in /etc might I find a script that lists the overall order of boot scripts particular to SuSE?
I know of none.
Philipp
-- Philipp Thomas work: pthomas AT suse DOT de SUSE LINUX AG private: philipp DOT thomas AT t-link DOT de
A practical question. I have a "USB Flash-Disk". I can mount it without problem on all stations I know but my Dell Latitude laptop boot-up (SuSE-8.2) gets completely stucked during the "hardware scan" (and also if I type 'hwinfo -usb' of course). The only way out is a hard reboot (fortunately I have journaling file-system now). If it happens with 'hwinfo --usb' or with mount '/media/sda1' I can't event stop the process with a 'kill' instruction (strange isn't it Watson)?. I don't have that problem with the same USB-Disk on other posts with SuSE-8.2 too, SuSE-8.1 or redHat-7.1. Thus it looks like it is a problem of detection of a particular USB device (on the Dell laptop I have a one port USB1). Somebody recommended me SuSE-9.0 but it is like replacing Windows-200* with Windows-2010. -- Alain Barthélemy cassandre@bartydeux.be http://bartydeux.be Linux User #315631
On Tuesday 02 December 2003 18:08, Tony Alfrey wrote:
) where in /etc might I find a script that lists the overall order of boot scripts particular to SuSE?
In /etc/init.d/rc5.d (for instance) the boot scripts are numbered in Start order and Kill order. -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- SuSE linux 8.2, 2.4.20-4GB, KMail 1.5.1 -- 6:59pm up 6 days 14:50, 5 users, load average: 1.08, 1.02, 1.01
Thanks Bruce, Phillip and jim for your help with this! Nice to clean out slow stuff! -- Tony Alfrey tonyalfrey@earthlink.net "I'd rather be sailing"
On Wednesday 03 December 2003 01:08 am, Tony Alfrey wrote:
When my SuSE 8.1 box boots, It gets to "starting hardware scan on boot" and it takes a very long time to slog through this (several minutes)
Dear Mr Alfrey, My box running SuSE 8.0 behaves exactly the same BUT, if I un-plug USB cable from usb socket in my ISDN Modem, then, booting loads perfectly. -- best wishes ____________ sent on Linux ____________
On Tuesday 02 December 2003 10:37 pm, pinto wrote:
On Wednesday 03 December 2003 01:08 am, Tony Alfrey wrote:
When my SuSE 8.1 box boots, It gets to "starting hardware scan on boot" and it takes a very long time to slog through this (several minutes)
Dear Mr Alfrey,
My box running SuSE 8.0 behaves exactly the same BUT, if I un-plug USB cable from usb socket in my ISDN Modem, then, booting loads perfectly.
Frankly, I suspected that such a thing might be the culprit, but I see that usb hotplug services load OK in the boot messages. But that may be different than a subsequent device scan. However, Bruce's suggestion about using the runlevel editor to just throw out anything that I really don't use has been a big help in speeding things up and making boot-up foolproof. Thanks! -- Tony Alfrey tonyalfrey@earthlink.net "I'd rather be sailing"
The Tuesday 2003-12-02 at 17:08 -0800, Tony Alfrey wrote:
When my SuSE 8.1 box boots, It gets to "starting hardware scan on boot" and it takes a very long time to slog through this (several minutes) and earlier today, it never made it through. The only solution I found was to "reload" SuSE (do an update of all packages).
Ah, the "windows" solution. An absolute overkill... You could have started the rescue system, mounted the root partition, and erase the link to hwscan. Then, after booting, remove the service with yast or chkconfig.
So my questions are a) why do I need the "hardware scan"? I have other distros that clearly do not do this.
A convenience... I disabled it time ago.
b) which script does this?
The names are listed as they execute. hwscan or similar.
c) where in /etc might I find a script that lists the overall order of boot scripts particular to SuSE?
No such list, the order may change. Read "man init.d" and the SuSE boot concept in the SuSE administration manual. -- Cheers, Carlos Robinson
participants (7)
-
Alain Barthélemy -
Bruce Marshall -
Carlos E. R. -
jim barnes -
Philipp Thomas -
pinto -
Tony Alfrey