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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have the same problem, the modem worked well on SuSe 9.1 with intel driver ver:4.69 (which is the latest). now SuSe 9.3 already comes with the same driver but it's not working. -frustrating
no, you're not only facing this problem, it looks like a common problem, I know a couple of freinds having the same problem too.
The current driver doesn't work with linux kernel ver 2.6.11.* , I hope someone finds a way to hack around it or make a patch to the driver.
I don't really count on Intel to update their driver, because they're very lazy in this area, it took them a really long time (something like a year) before they updated the driver to the current one to make it work with linux 2.6.*
Although I'm new here, but I was wondering whether this is the proper forum to place this thread, isn't the Hardware forum more suitable for such topics? (Admins?)
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
but by then,
I would not count on this for now. Personal opinion here, but
from what I read "modem companies" do not keep up very well
with Kernel updates. So if I were you I would not wait,
I would try asap. Personally, my 536ep board has a physical defect,
it is still under guarantee, that is nothing to say about any other 536ep,
it is just a random thing I suppose,
and yes it was great to learn a bit about drivers and patches,
and help other people, but as soon as I can I will buy a hardware modem.
Following your patch 1 and 2, I changed the ".../coredrv/softserial.h"
and ".../coredrv/softserial_io.c" files accordingly but during the "make
install" stage where the Intel driver is supposed get installed, I get
the following script errors:
chgrp: cannot access `/dev/536ep`: No such file or directory
chmod: cannot access `/dev/536ep`: No such file or directory
But, the /dev/536ep has been created and exists properly. So, I went
ahead and tried to initiate the dial-up account but the connection failed.
Yes, of course! If the scripting process went successful,
one'll have a clean "done" script response at the end of
And surely, I've run the make scripts as "root", but it's
a puzzle to you and me why I'm getting "chgrp" and "chmod"
access errors on /dev/536ep.
I think the /dev/536ep is the result from compiling the Intel's
driver where as /dev/536ep0 is SuSE's default pre-compiled
module. And, the /dev/modem is a symbolic link that points
to the /dev/536ep, and this link is the result from the driver
So, it appears important to figure out the access errors first
in solving this issue, Emmanuel_uk.
Do you know of anyone who successfully compiled the patches
on SuSE 9.3? I thought you stated in your previous replies that
you know of someone who made the 9.3 working.
Posting the whole make session is just too long. Perhaps, you
should just look at it yourself from your own compiling.