SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
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.
Unfortunatly I also have problem using Intel modem with intel-536ep chipset with Suse 9.3
Its problem in detail is:
This modem can be detected and its module( Intel-536ep.ko) will be loaded with insmod command and with opening the its device( /dev/536ep0 ) no error occured but no input and output through this device node can be done; for example you can see this with minicom or kppp's query modem option. Thus in Suse-9.3 it totally is useless.
Can anyone help us for solving it?
any aomment appretiated.
And is there anyone that are using that modem with debian 2.6.11 kernel, successfully ?
Maybe the permissions are set wrong on the modem device? Or it may be that the user needs to be in a special "group" (such as "dialout") to use it.
Can you send the output of this:
ls -l /dev/536ep0
and also:
ls -l /dev/modem
if it exists.
Also check to see (under Yast) if the user is in group "dialout".
One easy way to check all of this is to run as root. If it works, you probably have a permission problem for the user. If not, you have something more complicated going on.
Please do not post the same thread in more than one forum. Picking the most relevant forum and posting it once there makes it easier for other members to help you and keeps the discussion all in one place.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.