I only get this at boot time, so it isn't a big deal, but this is reminding me of that Microsoft "New Hardware Hell" we used to see in '98 and '95. I have my mouse connected to my computers using a Linksys 4 way switch, the kind that allows a person to switch back and forth between different computers with the same keyboard, monitor and mouse. I use it in my day-to-day without a glitch, except for when I install or update SuSE. When I install or update SuSE the install program never finds the mouse, and I have to do the install with a substitute, bypassing the switch, snaked around back. When things are up and running I go into YaST and update the mouse. I've been doing this little workaround since SuSE 5.2 or thereabouts. With 8.1, though, things didn't go so well. The install was normal, but now every time I boot the text based YaST2 pops up, asking me to supply mouse information. Is there a way around this? -- Prof: So the American government went to IBM to come up with a data encryption standard and they came up with ... Student: EBCDIC!"
Hi, Disable the Hardware Scanning script: /etc/rc.d/hwscan Use the RunLevel Editor in YAST or manually remove the S**hwscan and K**hwscan scripts from the various /etc/rc.d/rc*.d/ directories. This will prevent SuSE from scanning for new hardware when you boot the machine. Regards Q On Tue, 2002-10-15 at 07:30, Tim Hanson wrote:
I only get this at boot time, so it isn't a big deal, but this is reminding me of that Microsoft "New Hardware Hell" we used to see in '98 and '95.
I have my mouse connected to my computers using a Linksys 4 way switch, the kind that allows a person to switch back and forth between different computers with the same keyboard, monitor and mouse.
I use it in my day-to-day without a glitch, except for when I install or update SuSE. When I install or update SuSE the install program never finds the mouse, and I have to do the install with a substitute, bypassing the switch, snaked around back. When things are up and running I go into YaST and update the mouse. I've been doing this little workaround since SuSE 5.2 or thereabouts.
With 8.1, though, things didn't go so well. The install was normal, but now every time I boot the text based YaST2 pops up, asking me to supply mouse information. Is there a way around this?
-- Prof: So the American government went to IBM to come up with a data encryption standard and they came up with ... Student: EBCDIC!"
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Got it to stop on my server that only used a mouse during install, the command you want to try is: insserv -r hwscan Matt On Mon, 2002-10-14 at 22:38, Quinton Delpeche wrote:
Hi,
Disable the Hardware Scanning script: /etc/rc.d/hwscan
Use the RunLevel Editor in YAST or manually remove the S**hwscan and K**hwscan scripts from the various /etc/rc.d/rc*.d/ directories.
This will prevent SuSE from scanning for new hardware when you boot the machine.
Regards Q
On Tue, 2002-10-15 at 07:30, Tim Hanson wrote:
I only get this at boot time, so it isn't a big deal, but this is reminding me of that Microsoft "New Hardware Hell" we used to see in '98 and '95.
I have my mouse connected to my computers using a Linksys 4 way switch, the kind that allows a person to switch back and forth between different computers with the same keyboard, monitor and mouse.
I use it in my day-to-day without a glitch, except for when I install or update SuSE. When I install or update SuSE the install program never finds the mouse, and I have to do the install with a substitute, bypassing the switch, snaked around back. When things are up and running I go into YaST and update the mouse. I've been doing this little workaround since SuSE 5.2 or thereabouts.
With 8.1, though, things didn't go so well. The install was normal, but now every time I boot the text based YaST2 pops up, asking me to supply mouse information. Is there a way around this?
-- Prof: So the American government went to IBM to come up with a data encryption standard and they came up with ... Student: EBCDIC!"
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Thanks for the tips, everyone. I took the lazy way out and: chmod u=rw-x,g=-r-w-x,o=-r-w-x ./hwscan That way it's there if I need it. Quinton Delpeche wrote:
Hi,
Disable the Hardware Scanning script: /etc/rc.d/hwscan
Use the RunLevel Editor in YAST or manually remove the S**hwscan and K**hwscan scripts from the various /etc/rc.d/rc*.d/ directories.
This will prevent SuSE from scanning for new hardware when you boot the machine.
Regards Q
On Tue, 2002-10-15 at 07:30, Tim Hanson wrote:
I only get this at boot time, so it isn't a big deal, but this is reminding me of that Microsoft "New Hardware Hell" we used to see in '98 and '95.
I have my mouse connected to my computers using a Linksys 4 way switch, the kind that allows a person to switch back and forth between different computers with the same keyboard, monitor and mouse.
I use it in my day-to-day without a glitch, except for when I install or update SuSE. When I install or update SuSE the install program never finds the mouse, and I have to do the install with a substitute, bypassing the switch, snaked around back. When things are up and running I go into YaST and update the mouse. I've been doing this little workaround since SuSE 5.2 or thereabouts.
With 8.1, though, things didn't go so well. The install was normal, but now every time I boot the text based YaST2 pops up, asking me to supply mouse information. Is there a way around this?
-- Prof: So the American government went to IBM to come up with a data encryption standard and they came up with ... Student: EBCDIC!"
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- "A radioactive cat has eighteen half-lives."
On Tuesday 15 October 2002 01:30, Tim Hanson wrote: [...]
I have my mouse connected to my computers using a Linksys 4 way switch, the kind that allows a person to switch back and forth between different computers with the same keyboard, monitor and mouse.
I use it in my day-to-day without a glitch, except for when I install or update SuSE. When I install or update SuSE the install program never finds the mouse, and I have to do the install with a substitute, bypassing the switch, snaked around back.
I use a different brand of KVM switch, and have not had the problem... except one time. I forgot to set the switch to the machine I was loading. Actually, I had it set to the right machine while first loading with YaST, but when I rebooted to complete the install, I suffered a brain-fart and switched to do something on my other machine. By the time I remembered to switch back, the newly installed machine had come up and failed to find the expected keyboard and mouse. That, apparently, screwed up the install. I re-did, being careful to let the machine have uninterrupted access to the peripherals until it had re-booted and settled down. After that, no problem. I know this is a stretch, but if it's possible... Also, on the same basis, you *could* try moving your SuSE machine to a different port on the KVM switch. On some KVMs, all ports are not created equal -- they sometimes have imperfect isolation between channels, or else they overdo the attenuation in order to ensure that they DO have sufficicient attentuation. If that applies, then your problem might have been a signal-level issue that could improve on a different port. Good luck. /kevin
participants (4)
-
Kevin McLauchlan -
Matthew Johnson -
Quinton Delpeche -
Tim Hanson