Modem : Intel 536EP V.92 'Driver' for Redhat 8
Ian Hamilton
references to a file called Intel-536ep-451.tar and am wondering if this
is likely to be the answer.
1) Is Intel-536ep-451.tar likely to help me?
2) Where do I get the file from?
3) When I get it, what do I do with it?
4) Why won't my old external Pace 33.6 work either?
Ian Hamilton (Newbie)
Douglas Mayne
> I have one of these modems and cannot get it to work. I have seen
> references to a file called Intel-536ep-451.tar and am wondering if this
> is likely to be the answer.
>
> 1) Is Intel-536ep-451.tar likely to help me?
>
> 2) Where do I get the file from?
Web Page:
http://www.intel.com/design/modems/support/drivers_linux.htm
File:
Intel-536ep-451.tgz
>
> 3) When I get it, what do I do with it?
>
Follow instructions to create a compiled module for your kernel (see below).
> 4) Why won't my old external Pace 33.6 work either?
Possibly that modem is a winmodem. Check for compatibility at
www.linmodems.org
>
> Ian Hamilton (Newbie)
>
More information:
I have the Intel modem working under RedHat 7.3. Setting up for RedHat 8.0 is
similar. But since you are claiming newbie status, I will advise up
front that setting up this modem requires the compiler and other tools
necessary to work with source code. If you can follow instructions
closely, then you'll be fine.
I have written about this topic before. Read this answer and see if this
applies to you:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=pan.2003.01.08.09.47.42.115666.3218%40worldnet.att.net&rnum=2
Also, the "README" file in the source package (Intel-536ep-451.tgz)
contains the instructions for compiling the package.
-Douglas Mayne
Ian Hamilton
something to get started with.
By the way, the PACE, so far as I know is a bog-standard normal-modem
and did previously work on my old Mandrake RH6 system!!
Thanks again
Ian
Ian Hamilton
I followed the destructions and the modem now almost works. I can get
it to dial and croak, but it seams to give up too quickly and redial
again before I get a result.
I am also getting the following boot messages:
etc
Mar 11 19:25:12 localhost depmod: depmod: *** Unresolved symbols in
/lib/modules/2.4.18-14/kernel/drivers/char/536ep.o
Mar 11 19:25:12 localhost depmod: depmod: *** Unresolved symbols in
/lib/modules/2.4.18-14/kernel/drivers/char/536epcore.o
etc
etc
Mar 11 20:22:23 localhost rc: Starting 536ep-boot: succeeded
Obviously the last one is good, but the others I am a bit concerned
about. Perhaps I didn't quite follow the destructions closely enough...
Any offers?
Ian
PS Where do I find out about NewsGroup etiquette etc??
Douglas Mayne wrote:
Douglas Mayne
> Douglas, thanks for your help. I feel like I am getting somewhere at
> last!!
>
> I followed the destructions and the modem now almost works. I can get
> it to dial and croak, but it seams to give up too quickly and redial
> again before I get a result.
>
> I am also getting the following boot messages:
>
> etc
> Mar 11 19:25:12 localhost depmod: depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-14/kernel/drivers/char/536ep.o Mar 11 19:25:12
> localhost depmod: depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-14/kernel/drivers/char/536epcore.o etc etc Mar 11
> 20:22:23 localhost rc: Starting 536ep-boot: succeeded
>
> Obviously the last one is good, but the others I am a bit concerned
> about. Perhaps I didn't quite follow the destructions closely enough...
>
> Any offers?
>
> Ian
> PS Where do I find out about NewsGroup etiquette etc??
>
> <snip>
>
First, regarding your PS: The comp.os.linux.setup group has a recurring
post: "A newbie? Welcome to comp.os.linux.setup, read this first if you're
new here (FAQ)"
This FAQ has excellent information about netiquette (how and why's).
For this thread, please do not top post. This makes it easier to follow
as the thread develops-- the FAQ has more information.
Regarding the modem problem, I have a /*new*/ RedHat 8.0 setup. (My primary
machine is RedHat 7.3, however.) I tested the Intel modem on the RedHat
8.0 setup (with stock kernel 2.4.18-14). I duplicated the problem you are
having- the fast dial timeout problem.
I also see the messages about "unresolved symbols" when I issue the
command:
#depmod -a
I don't know what it means exactly, because the modem still works. This
message is present on RedHat 7.3 with kernel 2.4.20 and RH 8.0 with
kernel 2.4.20.
I used minicom to try to connect and to check the value of "Wait Time for
Carrier" (S7=45). 45 seconds seems adequate, but it would disconnect much
earlier than that.
I checked if this problem was also present using a non-stock kernel-
version 2.4.20. I tested the combination of RedHat 8.0 and kernel 2.4.20
by first compiling the kernel, rebooting with the new kernel, and then
recompiling the Intel modem package. This combination connects correctly
using PPP for me. I looked at the RedHat site and there are several
bug-fix, security vulnerability fixes for the kernel you are using. Even
if the modem isn't fixed under the latest RedHat kernel, you should still
download their latest fix (unless you plan on compiling your own kernel).
Depending on your experience level, maybe you could compile the kernel
also. However, I have been accused recently of "prescribing open heart
surgery for a possible hangnail," so I won't make that leap until I test
the latest RedHat kernel for RedHat 8.0 myself.
Maybe someone else will see this message in the forum and will contribute
the correct answer.
-Douglas Mayne
Douglas Mayne
> On Wed, 12 Mar 2003 02:38:39 -0700, Ian Hamilton wrote:
>
>> Douglas, thanks for your help. I feel like I am getting somewhere at
>> last!!
>>
>> I followed the destructions and the modem now almost works. I can get
>> it to dial and croak, but it seams to give up too quickly and redial
>> again before I get a result.
>>
>> I am also getting the following boot messages:
>>
>> etc
>> Mar 11 19:25:12 localhost depmod: depmod: *** Unresolved symbols in
>> /lib/modules/2.4.18-14/kernel/drivers/char/536ep.o Mar 11 19:25:12
>> localhost depmod: depmod: *** Unresolved symbols in
>> /lib/modules/2.4.18-14/kernel/drivers/char/536epcore.o etc etc Mar 11
>> 20:22:23 localhost rc: Starting 536ep-boot: succeeded
>>
>> Obviously the last one is good, but the others I am a bit concerned
>> about. Perhaps I didn't quite follow the destructions closely
>> enough...
>>
>> Any offers?
>
> <snip>
>
> I checked if this problem was also present using a non-stock kernel-
> version 2.4.20. I tested the combination of RedHat 8.0 and kernel
> 2.4.20 by first compiling the kernel, rebooting with the new kernel, and
> then recompiling the Intel modem package. This combination connects
> correctly using PPP for me. I looked at the RedHat site and there are
> several bug-fix, security vulnerability fixes for the kernel you are
> using. Even if the modem isn't fixed under the latest RedHat kernel,
> you should still download their latest fix (unless you plan on compiling
> your own kernel). Depending on your experience level, maybe you could
> compile the kernel also. However, I have been accused recently of
> "prescribing open heart surgery for a possible hangnail," so I won't
> make that leap until I test the latest RedHat kernel for RedHat 8.0
> myself.
>
> Maybe someone else will see this message in the forum and will
> contribute the correct answer.
>
> -Douglas Mayne
>
I checked RedHat 8.0 with RedHat's latest kernel, version 2.4.18-26.8.0.
The fast dial timeout problem still exists with that kernel.
Offtopic: The anti-aliased fonts look spectacular on RedHat 8.0! Wow!
-Douglas Mayne