LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   intel 536ep modem with suse 9.3 pro (https://www.linuxquestions.org/questions/linux-newbie-8/intel-536ep-modem-with-suse-9-3-pro-323265/)

pcandpc 09-11-2005 02:09 PM

Hi Emmanuel_uk,

It's nice talking to you again :)

By the way, I tried to look at /etc/modprobe.preload,
but no where could I see this file.

Just for your reference here, since I'd have to reinstall
the modem driver after each reboot for the modem to
work, I thought is the driver somehow missing and tried
to just uninstall the driver.

Well, the error message I got was the driver was not found.

This tells me that the installed driver is somehow gone
mysteriously on each reboot.

I came across reading somewhere that this is due to SuSE 9.3
keeping the driver in RAM ... Could this be the very reason?

If so, how can I have the driver in some non-volatile area even
after reboots?

As a side note, the same new driver is somewhat weirdly acting
in the other distro such as CentOS 4.1 I'm using.

The installation was successful but when KPPP tried to detect
the modem, the keyboard's Caps and Scrool Locks were blinking
and the entire system got frozen.

But that's another issue on this new driver.

I just want to get this SuSE 9.3 get going ...

Any idea, my friend? :)

Thanks.

Emmanuel_uk 09-12-2005 02:14 AM

Hi,

There is no reason why you should need to reinstall the driver everytime you reboot.
The driver should just need loading
Try in a terminal
insmod 536ep (you may need to be root)
if this does not work try
modprobe 536ep

if it does not work, then find where the 536ep driver lives (use the locate function, or find with konqueror)
and add the path like
insmod /path/to/536ep

Otherwise, well this would be really weird

sorry about modprobe.preload this must be mandrake specific
You might have a modprobe.conf, or something of the like

Otherwise, a dirty way to start the driver is to add the modprobe line
to you bashrc file

I have got old of suse 9.3 pro. Might give it a go at some point

pcandpc 09-13-2005 01:35 AM

Hi Emmanuel_uk,

I tried insmod /dev/modem (as well as /dev/536ep)
as root, but the reply was that this driver was not
found.

But, I see both modem and 536ep under /etc with
modem linked to 536ep. However, the size of each
file is reported as 0.

What does this tell you?

Thanks.

Emmanuel_uk 09-13-2005 02:16 AM

module (drivers) is a file called 536ep.ko
most module I understand can be loaded in addition to the kernel (they are drivers)
and finish in ko for kernel above 2.6 (they were .o before I think)
Find where it leaves (to be sure it is there)

the command to load the driver is
insmod 536ep
nothing else, no ko at the end, usually path not needed

If this works from command line (as root) after reboot, then next will be automation

if it does not work then add the path to
insmod /path/to/536ep (that is 536ep.ko)

pcandpc 09-13-2005 02:28 AM

Hi Emmanuel_uk,

Yes, I understood that well.

But what I meant was what do you think happened when
I ran insmod /etc/536ep and received an error that says
there's no module for 536ep when, in fact, I see it residing
under the /etc?

Bottom line is that the insmod 536ep or /etc/536ep doesn't
work.

Any further suggestions?

Thanks.

Emmanuel_uk 09-13-2005 02:40 AM

You mean 536ep.ko lives in /etc ?
Try modprob (or modprobe) instead of insmod
No other idea for now. I am away from my linux machine

pcandpc 09-14-2005 02:08 AM

Hi Emmanuel_uk,

What I meant to say was /dev/536ep ...

By the way, I tried the modprobe on
/dev/536ep but the result came up to
be not found even though there is
/dev/536ep.

Isn't this weird?

I also looked at /etc/init.d/ to see if I can
find something that's related to this Intel
modem, and I found /etc/init.d/S99_Intel536
that's linked to /dev/modem, which, in turn,
is linked to /dev/536ep.

This looks very sane to me, but it's weird that
I have /dev/536ep reporting as 0-byte sized
file. But then again, I think that I also saw this
0-byte size just after the driver installation and
before the reboot.

So, I don't think the size of /dev/536ep doesn't
really matter, or does it in relation to the probelm
I'm having on each reboot?

Thanks.

Emmanuel_uk 09-14-2005 02:23 AM

/dev/536ep is the device. The same way /dev/hda would be a hard drive device for example.
You cannot load /dev/536ep bec it is not a driver. /dev/536ep is a character device I believe,
so it is normal that /dev/536ep is 0 or 1 byte (size does not matter).

What is the output of
lsmod | grep 536
dmesg | grep 536
after reboot

Hoopps I said bashrc in a previous post, I really meant /etc/rc.local

S99 looks wrong, it should not be a link but a script (i.e. a text file)

What's S99 like after a .configure make etc
what is the output of
lsmod | grep 536
dmesg | grep 536
cat /var/log/syslog | grep -i '536ep|modem' (the bar is supposed to be working like a or, no linux machine to check syntax here)

[Added
On my PC
/lib/modules/2.6.8.1-10mdk/kernel/drivers/char/Intel536.ko

and S99_Intel536ep reads

Code:

#!/bin/sh
#**********************************************************************************
# Copyright (c) 1999-2004, Intel Corporation
#
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are met:
#
# 1. Redistributions of source code must retain the above copyright notice,
# this list of conditions and the following disclaimer.
#
# 2. Redistributions in binary form must reproduce the above copyright notice,
# this list of conditions and the following disclaimer in the documentation
# and/or other materials provided with the distribution.
#
# 3. Neither the name of Intel Corporation nor the names of its contributors
# may be used to endorse or promote products derived from this software
# without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS''
# AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
# DISCLAIMED. IN NO EVENT SHALL CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
# PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
# LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
# NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
# EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
#***********************************************************************************
# 13-6-2002:  A few hacks by Diego Iastrubni <dgi_il@hotmail.com>

serial="Intel536"
devnode="/dev/536ep"
device="536ep"
registry="hamregistry"
group="root"
mode="664"


if [ -a /etc/SuSE-release ]; then
{
  group="dialout"
}
fi

case "$1" in
  start | b)
      if ! ( modprobe -f $serial 1>/dev/null 2>/dev/null ); then
      {
        if ! ( insmod -f $serial 1>/dev/null 2>/dev/null ); then
        {
          echo error loading $serial
          rmmod $serial
          exit 1
        }
      fi
      }
      fi
      major=`cat /proc/devices | awk "\\$2==\"$device\" {print \\$1}"`
      rm -f $devnode
      mknod $devnode c $major 1 2> /dev/null 1> /dev/null
      chgrp $group $devnode
      chmod $mode  $devnode
      ln -sf $devnode /dev/modem 1> /dev/null 2> /dev/null
      if ! ps -C $registry 1> /dev/null 2> /dev/null; then
      {
        if ! ( /usr/sbin/$registry  2> /dev/null 1> /dev/null & ); then
        {
            echo "Modem registry ($registry) could not start."
            echo "Please see international users secion in readme.txt for more info."
        }
        fi
      }
      fi
      exit 0
      ;;
  stop)
      rmmod $serial 1> /dev/null 2> /dev/null
      ;;
  restart | reload)
    /bin/bash "$0" stop
    /bin/bash "$0" start
    exit 0
    ;;
  status)
    if lsmod | grep "$serial " >/dev/null; then
    {
      lsmod | grep "$serial " > /dev/null
    }
    else
    {
      echo "$serial NOT loaded"
    }
    fi
   
    if  ps -C $registry 1> /dev/null 2> /dev/null; then
    {
        ps -C $registry
    }
    else
    {
        echo "$registry NOT running"
    }
    fi

    exit 0
    ;;
  *)
    echo unknown $serial script parameter
    exit 1
esac

exit 0


pcandpc 09-17-2005 03:14 PM

Hi Emmanuel_uk,

Thanks for your consistent help out on this issue.

Actually, the /etc/init.d/boot.d/S99_Intel536 is linked
to the /etc/init.d/Intel536.boot, which looks exactly
as your S99... file.

I tried lsmod command and received nothing as a result,
and received the following from dmesg command:

PID hash table entries: 4096 (order: 12, 65536 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
vesafb: framebuffer at 0xc8000000, mapped to 0xf8880000, using
6144k, total 65536k
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP Hash tables configured (established 131072 bind 65536)

And, as with your the other cat command, I see the result of no
such file or directory.

Now, do you think you can help? :)

Emmanuel_uk 09-18-2005 04:59 AM

Lets go back one step

if lsmod | 536 gave nothing that means the driver is not loaded
(does lsmod on its own give a long list)

Have you located, after doing .config, install, make
the file Intel536.ko

pcandpc 09-18-2005 01:47 PM

Hi Emmanuel_uk,

Yes, I see /lib/modules/2.6.11.4-21.9-default/kernel/drivers/char/Intel536.ko.

So, the issue is that this is not loaded during each reboot, huh?

pcandpc 09-18-2005 10:53 PM

Hi all,

I found a solution to this issue as shown in the following link:

www.suseforums.net/index.php?showtopic=15652

Basically, one has to make sure the module Intel536 is listed
in the lsmod output first.

Please reinstall the driver if there's no Intel536 in the lsmod
output.

And, edit /etc/init.d/boot.local as root such that the following
is added to the file:

modprobe Intel536

Then, reboot.

I don't know if this is a temporary workaround but this works
nicely for now :)

Emmanuel_uk 09-19-2005 02:05 AM

PCandPC ,

I am glad this is sorted

Indeed the issue was that this
/lib/modules/2.6.11.4-21.9-default/kernel/drivers/char/Intel536.ko
was not loaded at boot

I did not know about the boot.local (possibly distro specific)
I was going to suggest to add
modprobe /lib/modules/2.6.11.4-21.9-default/kernel/drivers/char/Intel536.ko
into the rc.local

If you to fiddle to learn something by hand (and convince yourself of what
is going on I suggest these commands as root

lsmod | grep 536 (check the module is there)
modprobe -r Intel536.ko (remove it from memory)
lsmod | grep 536
modprobe /lib/modules/2.6.11.4-21.9-default/kernel/drivers/char/Intel536.ko
lsmod | grep 536
dmesg | grep -i taint
(the kernel is tainted, it is ok, because the driver is not an open source binary)

pcandpc 09-19-2005 12:00 PM

Hi Emmanuel_uk,

Just a quick comment.

I tried putting the following line in the boot.local file:

modprobe /lib/modules/2.6.11.4-21.9-default/kernel/drivers/char/Intel536.ko

But this didn't work when the system is already rebooted and
you don't have this Intel536 module available via the lsmod even
if you have the Intel536.ko available in the above path.

Thanks.

Emmanuel_uk 09-19-2005 03:08 PM

Not sure I understand. Your PC works ok now?


All times are GMT -5. The time now is 03:20 AM.