Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: Pieter on January 17, 2003, 06:05:20 PM

Title: Internal ISND does not work in 5.6
Post by: Pieter on January 17, 2003, 06:05:20 PM

I try to get an internal ISDN adapter up and running in E-smith 5.6 but to no succes.

I tried two different Winbond 6692 based cards. They are correctly recognised in the setup.  

The card shows up nicely in lspci:
01:01.0 Network controller: Dynalink IS64PH ISDN Adapter

In te syslog I get:
connector: Can't open /dev/isdnctrl or /dev/isdn/isdnctrl.

With E-Smith 5.5 both cards work perfectly!

I think something (some symlink?) is broken in the ISDN subsystem.

Can anyone help me with this?

Title: Re: Internal ISND does not work in 5.6
Post by: Charlie Brady on January 27, 2003, 12:00:54 AM

Pieter wrote:

> I try to get an internal ISDN adapter up and running in
> E-smith 5.6 but to no succes.
>
> I tried two different Winbond 6692 based cards. They are
> correctly recognised in the setup.
>
> The card shows up nicely in lspci:
> 01:01.0 Network controller: Dynalink IS64PH ISDN Adapter
>
> In te syslog I get:
> connector: Can't open /dev/isdnctrl or /dev/isdn/isdnctrl.

Could you please see whether doing "/sbin/modprobe isdn" helps at all? Please report your results here and to bugs@e-smith.com.

Thanks

Charlie

Title: Re: Internal ISND does not work in 5.6
Post by: Derek Atkinson on January 29, 2003, 02:57:36 AM

Pieter wrote:
>
> I try to get an internal ISDN adapter up and running in
> E-smith 5.6 but to no succes.
>
> I tried two different Winbond 6692 based cards. They are
> correctly recognised in the setup.
>
> The card shows up nicely in lspci:
> 01:01.0 Network controller: Dynalink IS64PH ISDN Adapter
>
> In te syslog I get:
> connector: Can't open /dev/isdnctrl or /dev/isdn/isdnctrl.
>
> With E-Smith 5.5 both cards work perfectly!
>
> I think something (some symlink?) is broken in the ISDN
> subsystem.
>
> Can anyone help me with this?



I too have this problem with a Fritz! PCI Card (BT Speedway) which works just fine in SME 5.5. During the initial post-upgrade investigations I did find a BIOS conflict in that the PCI ISDN card and my second (ISA) printer port both wanted IRQ5 but moving the ISDN card to IRQ10 didn't change things.

Running "/sbin/modprobe isdn" doesn't help - nor does it generate any errors.

I've looked into the logfiles and found the following in /var/log/messages (and a similar entry in boot.log) which may be of use:

Jan 28 18:55:38 server kernel: ISDN subsystem Rev: 1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1 loaded
Jan 28 18:55:38 server kernel: HiSax: Linux Driver for passive ISDN cards
Jan 28 18:55:38 server kernel: HiSax: Version 3.5 (module)
Jan 28 18:55:38 server kernel: HiSax: Layer1 Revision 1.1.4.1
Jan 28 18:55:38 server kernel: HiSax: Layer2 Revision 1.1.4.1
Jan 28 18:55:38 server kernel: HiSax: TeiMgr Revision 1.1.4.1
Jan 28 18:55:38 server kernel: HiSax: Layer3 Revision 1.1.4.1
Jan 28 18:55:38 server kernel: HiSax: LinkLayer Revision 1.1.4.1
Jan 28 18:55:38 server kernel: HiSax: Approval certification failed because of
Jan 28 18:55:38 server kernel: HiSax: unauthorized source code changes
Jan 28 18:55:38 server kernel: PPP Deflate Compression module registered
Jan 28 18:55:38 server ippp: Configuring ippp interfaces: diald
Jan 28 18:55:39 server modprobe: modprobe: Can't locate module ippp0
Jan 28 18:55:40 server last message repeated 7 times
Jan 28 18:55:40 server modprobe: modprobe: Can't locate module
Jan 28 18:55:49 server ippp: Sorry - this system lacks PPP kernel support.
Jan 28 18:55:49 server ippp: Check whether you configured at least the ippp0 device!
Jan 28 18:55:49 server ippp:
Jan 28 18:55:49 server rc: Starting ippp:  succeeded

When I tried the Test Internet Access option on the Server Console, the following errors appeared:
Jan 28 19:26:37 server diald[1750]: Trigger: udp       192.168.168.1/1025      193.0.14.129/53  
Jan 28 19:26:37 server diald[1750]: Calling site 0.0.0.0
Jan 28 19:26:37 server diald[1750]: connector: Can't open /dev/isdnctrl or /dev/isdn/isdnctrl: No such device
Jan 28 19:26:38 server last message repeated 5 times
Jan 28 19:26:38 server diald[1750]: Connect script failed.
Jan 28 19:26:38 server diald[1750]: Delaying 10 seconds before clear to dial.
Jan 28 19:26:47 server console: Response to Internet test was: Can't connect to servertest.e-smith.com:80 (Bad hostname 'servertest.e-smith.com')

A look into /dev shows the following link for isdnctrl and ttyI0:

lrwxrwxrwx    1 root     root            9 Jan 28 18:37 isdnctrl -> isdnctrl0

crw-rw----    1 root     uucp      43,   0 Apr 11  2002 ttyI0

Hope this helps shed some light on the problem.

BTW, I was playing with RedHat Linux 8 at the weekend on the same machine and couldn't seem to get Internet access over ISDN on that either - maybe it's a RHL issue ?.

Derek.

Title: Re: Internal ISDN does not work in 5.6
Post by: Dave Clarke on February 15, 2003, 01:31:55 AM

I have upgraded from 5.1 to 5.6, have all of the symptoms listed in previous threads using an ASUS card. Connection works fine over USB.

Title: Re: Internal ISND does not work in 5.6
Post by: Stefan Braunstein on February 17, 2003, 12:31:36 PM

Hi!

i´m just installing a new SME 5.6 box and get the same error with a Fritz! PCI card. No output from /sbin/modprobe isdn   and the logs look similar to the one from Derek.

Is there any solution or workaround? Otherwise I´ll have to use SME 5.5.

Stefan

Title: Re: Internal ISDN does not work in 5.6 - Fixed mine
Post by: Dave Clarke on February 18, 2003, 03:12:06 AM

Well, I've fixed mine - albeit a temporary bodge. It looks as if the type parameter passed with the modprobe hisax command was incorrect when hisax was initialised. After doing some digging about, I found that that type=35 is correct for my Asus card (12 or 36 are also possible types for Asus). I added the following line: "options hisax type=35 protocol=2 irq=9 io=0x5420" in /etc/modules.conf and it now works a treat. You will, of course need to use lspci to find the irq and io parameters for your particular PCI card.

Now I've just got to work out how to implement this fix properly (unless someone beats me to it?). I'm a bit of a noob to this stuff, so any help much appreciated.

Hope this helps,

Dave.

Title: Re: Internal ISDN does not work in 5.6 - Fixed mine
Post by: Stefan Braunstein on February 18, 2003, 03:05:36 PM

Hi Dave,

> ... added the following line: "options hisax type=35 protocol=2 irq=9
> io=0x5420" in /etc/modules.conf

that worked also for me. Thanks!! But  when you  repeat the config, the  lines are lost again. So I looked at /etc/e-smith/templates/etc/modules.conf/

and changed:

    my $type = db_get_prop($confref, 'isdn', 'Type') || "";
    my $protocol = db_get_prop($confref, 'isdn', 'Protocol') || "";

to

    my $type = "27";
    my $protocol = "2";

very quick and very, very dirty, I know!

I found the right type  for my Fritz PCI card at  http://linux.hu.rulez.org/isdn.txt

Stefan

Title: Re: Internal ISDN does not work in 5.6 - Fixed mine
Post by: Dave Clarke on February 19, 2003, 12:56:07 AM

I realised later that (in my case at least) the correct parameters are actually stored in /home/e-smith/configuration, they just aren't used.

Title: Re: Internal ISDN does not work in 5.6 - Final Fix
Post by: Dave Clarke on March 11, 2003, 07:30:46 PM

Had a little time on my hands so came up with a proper fix..

In /etc/e-smith/templates/etc/modules.conf change all references to $conf to $confref   :

    my $hisax = db_get_prop($confref, 'isdn', 'HisaxOptions') || "";
    my $type = db_get_prop($confref, 'isdn', 'Type') || "";
    my $protocol = db_get_prop($confref, 'isdn', 'Protocol') || "";

Then expand the template:

    /sbin/e-smith/expand-template /etc/modules.conf