How to stop long hardware scans on boot up
After getting my 2nd parport card to work, and installing the 2nd printer, I keep getting long hardware scans on bootup, and the 2nd printer gets checked out, and I half to clear the printers buffer before using. How do I fix this under Suse 8.0? TIA Harry G
On Mon, 2002-11-04 at 17:49, Harry G wrote:
After getting my 2nd parport card to work, and installing the 2nd printer, I keep getting long hardware scans on bootup, and the 2nd printer gets checked out, and I half to clear the printers buffer before using.
How do I fix this under Suse 8.0?
in 8.1 it is under yast2>system>runlevel editor. just uncheck hardware scan from the init's that apply (i think it is listed as 'hwscan' or something) or remove the S and K values of hardware scan from the /etc/init.d/rc[#].d
I don't need to stop it completly, but it appears to think there is additional hardware not installed, probably the 2nd parport or the printer, but both are working. Isn't that what your suggestion do, or am I not understanding it properly? I just need to have it stop snaggging. Harry G On Mon November 4 2002 10:19 pm, Jeric wrote:
On Mon, 2002-11-04 at 17:49, Harry G wrote:
After getting my 2nd parport card to work, and installing the 2nd printer, I keep getting long hardware scans on bootup, and the 2nd printer gets checked out, and I half to clear the printers buffer before using.
How do I fix this under Suse 8.0?
in 8.1 it is under yast2>system>runlevel editor. just uncheck hardware scan from the init's that apply (i think it is listed as 'hwscan' or something)
or remove the S and K values of hardware scan from the /etc/init.d/rc[#].d
On Tue, 2002-11-05 at 06:24, Harry G wrote:
I don't need to stop it completly, but it appears to think there is additional hardware not installed, probably the 2nd parport or the printer, but both are working. Isn't that what your suggestion do, or am I not understanding it properly?
I just need to have it stop snaggging.
I believe it is an all or nothing approach. It just takes a really long time to scan the hardware, it's not actually gettng hung up or anything...it just takes that long normally. What I did was to disable it on the init that I use the most, and left it enabled on the other inits. THat way I can boot to another init if I add/remove new hardware. I also disabled it on my laptop and have found no issues when changing devices like swapping the floppy/cdrom, as that is under the hotplug module. -jeric
Jeric
or remove the S and K values of hardware scan from the /etc/init.d/rc[#].d
That won't help for long, because they'll be recreated by the next run
of SuSEConfig. The only ways to disable a service is either using YaST2
runlevel editor or issuing 'insserv -r
On Tue, 2002-11-05 at 18:39, Philipp Thomas wrote:
Jeric
[04 Nov 2002 21:19:35 -0600]: or remove the S and K values of hardware scan from the /etc/init.d/rc[#].d
That won't help for long, because they'll be recreated by the next run of SuSEConfig. The only ways to disable a service is either using YaST2 runlevel editor or issuing 'insserv -r
', i.e. in this case 'insserv -r hwscan'. You may use 'chkconfig -l ' to see in which runlevels (if any) it's active. Philipp
Sorry, I was unaware of that. Thanks for catching it, though. -Jeric
participants (3)
-
Harry G
-
Jeric
-
Philipp Thomas