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.
Hi,
Sorry for being late to respond, <I am actually busy with me exams currently>.
Here's what happend with me.
I Applied the patch . then I did the "make" steps (clean, 536, install).
Something was wrong during the install, similar to what happened with pcandpc. I found out later that there was some confusion in that there was something called /dev/536ep0 while it was supposed to be /dev/536ep .
So I did some manual steps described in that readme file that came with the driver, something like:
That made the /dev/536ep driver and /dev/modem linking to it. I felt that I acheived something at that point, so I started the kppp, used /dev/modem device, when I tried to connect, the kppp crashed (it started alocating huge amounts of memory endlessly). I also remember that there was a "Query" button in kppp configuration, when I pressed that butten it walked through several steps "succesfully apparently", then displayed a dialog box showing 7 empty strings. (AT1,AT2,...etc).
PS: I tried doing all the steps twice, with and with out commenting the line pm_access(power_dev). I got the same results in both cases.
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606
Rep:
PcandPC
A user on kernel-devel-2.6.11-1.1366_FC4.i686
has commented on linmodem having to comment
out pm_access as well, so "my fix" is necessary.
I am keeping en eye on the list so if anything props up about suse
I will let you know.
You know that group error, I do not if it matters or if this
can be resolve by changing permissions? Did you look
if /dev/536ep was part of the dial group (or whichever group is needed)?
>>So, I went ahead and tried to initiate the dial-up account but the connection failed
Can you post the error messages?
I suggest you use wvdial rather than kppp, if you can, it is easier to diagnose
problems during dial-up. Mave be nothing is wrong with the driver,
but still you could have a problem with the setup of kppp.
Do the ATI command works (in Kppp)?
You may need to trick wvdialconfig if you want to use it by
creating a few symbolics link to ttyS0 (???) because that the
only ports wvdialconfig can scan.
Actually, the /dev/536ep was never created in my case.
I was misled by not correctly reading the directory listing.
As far as my comment on "connection failed", I simply meant
that the connection was never successfully made by observing
the icon on the panel.
I've used the KPPP since 8.2 Pro and quite familiar with its GUI
configuration than any other dial-up utility, but I'll consider the
wvdial per your suggestion.
As it stands now, the ATIs do not matter because my modem is
never detected by 9.3 Pro to begin with.
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606
Rep:
PcandPc, did you try Nawwar manual method, i.e.
mknod /dev/536ep c 240 1
before or after the make install (try both?)
A shot in the dark, to see if that changes the error message
I'm so impressed! By the way, I'm in the middle of communication with Klaus.
Basically, he suggested the same methods as in Emmanuel_uk's patch link.
This took care of my previous script errors, but still my modem connection is
not made at all, and I conveyed this information to Klaus, and currently, I'm
awaiting for his feedback.
So, Emmanul_uk, you've made the patch working under Mandriva 2005 LE?
Lucky for you!
Besides this modem connection, I'm having other issues here and there on
SuSE 9.3 Pro. And, perhaps, I'll switch to other distro eventually if this modem
connection is not resolved. You know, I can't just try this and that indefinitely.
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606
Rep:
Hi you two,
All I know about segmentation fault is that it _may_ be
a sign of the driver being unsuitable (i.e. code wrong or unsuitable).
Those bl..y patch are a pain when they come to line wrapping.
Can you try to patch by hand and see what the make steps give then?
(one of my mail explain how you can do the patch by hand)
I am sorry this 536ep is causing you so much trouble. As Klaus
had no problem, I assumed it would be the same for you two...
It seems the problem is out of my league.
Unless you can find what is different between Klaus system and yours,
I suggest
- you download scanmodem
- make uninstall (remove the /dev/536* if still there
then "record" all the steps (I mean the command line you used + 1 or 2
output lines if informative, you know what I mean)
- which intel file you are using
- state if you had error or not during the patch
(maybe best you take the patch from the ubuntu website and
disable the pm_access by hand)
- the exact errors with a few context lines during compilation
- the errors using wvdial
- make ref to http://linmodems.technion.ac.il/arc...h/msg02026.html
- make ref to linmodem email dated 04/06/05
"RE: Problem with Intel 536EP and Fedora Core 4 (RC3): Working! (Sort of)"
stating that it is the third confirmation that pm_access needs disabling
with 2.6.11 kernel for the 536ep
These guys there are fantastic, they surely will have further suggestions.
On top it is two of you with the same chip, same distro,
so it should make their life easier
I am looking forward to see what they suggest
If this fail (I do not think so), then this will go direct to
the intel developer
It'd be nice if Intel promptly updates their Linux drivers, but
then being Linux issues, I assume that they're under no obligation
at all other than their "voluntary" commitment, which is still appreciative.
By the way, I'm in the middle of communication with Klaus as I stated
in one of my previous posts. Hopefully, things iron out smoothly. His
suggestion is no different from what you, Emmanuel_uk, suggested in
the patch 1 link.
After all, he appears to be the one who made this modem work under
SuSE 9.3 Pro, and I'm diligently following up with him.
I'll certainly update this thread whether the result is successful or otherwise.
As a last resort, I'll consider working with the Linmodem.org guys. But then,
if I decide to switch over to the other distros, this is it for me.
So, the whole deal here is the kernel 2.6.10 and later with Intel 536EP modem
driver on SuSE 9.3 Pro, huh? Well, I don't have this issue at all under FC3 with
the same latest Intel driver. I suppose this is because FC3's kernel version is
2.6.9-something.
Hopefully, things work out for good with Intel drivers for kernels 2.6.10 and later
sooner or later.
I've been working with Klaus on this modem issue
since he appears to have made the modem working
on SuSE 9.3.
He was very helpful, and I made my modem working
the first time ever after reinstalling SuSE and carefully
following his suggestions.
His suggestions were no different from the earlier ones
by Emmanuel_uk on applying the patch.
However, my working with the modem didn't last long.
After having made work the first time, restarting the
modem conncetion failed. Since then, the modem hasn't
worked at all -- back to square one.
Now, I've decided to replace this SuSE with another
distro and sadly given up on this issue.
Hopefully, there'll be newer, officialy driver by Intel soon.
Thanks all for your efforts and helpful suggestions.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.