Well, about a week ago I plugged in 2nd cdrom drive. Upon booting it was detected and then after I logged into KDE it announced it had found new hardware and if I would like to install/config it. I did, it worked, brought up YaST2 and then popped up the new hardware module. Just like it's supposed to, YMMV depending on the hardware your trying to install. Cheers, Curtis. On Sunday 10 November 2002 23:46, DJ wrote:
DI> SuSE was installed and running fine, but then I decided to run SAX DI> to see what is was all about. I know, it's a bad idea to run a DI> program when you don't know exactly what it does, but I couldn't
I know if I go to Yast2 | Hardware, the message says probing, but I think this only builds an informational list.
I noticed some interesting items in the online suse database.
"X Server Configuration with SaX2" http://sdb.suse.de/en/sdb/html/wessels_sax2.html
sax2 -f = Makes sure that the hardware is checked even if hardware data is already available. This -f option has been already implemented in the sax2 command in SuSE Linux 7.2 or higher. If you want to disable the hardware detection, please use the -q option
http://sdb.suse.de/cgi-bin/sdbsearch_en.cgi?stichwort=sax2+mouse Checkout, "X Server Configuration with SaX2 (8.1 or higher) (07.11.2002)".
You can find additional information on sax2 in the Administration manual, do a "man sax2", or in /usr/share/doc/packages/. sax2 can be run from the console. If it were me, I'd try to run sax2 again and then I think I would really study the database entry above and start applying some of their solutions for known problems.
Good luck.
-- Billboard Writer vs. Literature = Micorsoft vs. Computing,