Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I got the same thing, open the Suse hardware tool, it should be the little motherboard looking icon on the right on the toolbar, to the left of the c.lock. Click the + next to USB controller. click on one of them that says USB UHCI and click details, then click the driver tab. if it says uhci-hcd go to your /etc/speedtouch.conf file and edit it so where it says DEFAULT_USBINTERFACE="usb - uhci" or whatever. change after the = to be "uhci - hcd". so it should look like DEFAULT_USBINTERFACE="uhci-hcd"
NOTE: before you edit this file back a backup or atleast remember what was in the " " before you mess anything up.
Thanks for your reply. It helped. I can now start the connection by '/etc/init.d/speedtouch start' but it wont automatically connect during startup - i get a 'FAILED'?
I dunno about all that starting at start-up. When I first had Suse 9.0 and used the script I chose the option to connect at start-up and it would do everything and connect, but then it wouldn't be connected once I logged in so I would have to manually connect with the /etc/init.d/speedtouch start. But after I upgraded to 9.1, I did the script again and didn't fool with the connecting and startup. But I thought from what I saw when you press F2 at startup is that it just runs the /etc/init.d/speedtouch start, so I dunno.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.