[SuSE Linux] [ISDN] How to add to Hisax / Dynalink support
Hi, I moved from Redhat to the new SuSE, mainly because I hoped that the ISDN support was completely up-to-date. First of all, in general : Good Job! SuSE appeared to be a pretty decent dist. (And what application is 1000erfect, right?) First of all, as described for SuSE 5.1, there is a hisax.o and a hisax.2.5.o in de /var/modules/etc. Does this mean that still the 'standard' version is 2.1, and one has to rename 2.5.o to get the 2.5 support? I figured 2.5 hsould have been stable enuff by now? I'm trying to get a Dynalink IS64PH+ ISDN card to function inder 5.3. Unfortunatly it is not standard supported by 5.3. What do I have to do, to get it functioning under 5.3? If I get just the simple steps explained would already be a big help. I'm a bit reluctant to make a whole new kernel just for this, Hisax is a module after all and I thought that that means that you don't need to do that? The driver information for this Dynalink IS available at <A HREF="http://www.2l.net/dynalink/linux/"><A HREF="http://www.2l.net/dynalink/linux/</A">http://www.2l.net/dynalink/linux/ there is a file <A HREF="http://www.2l.net/dynalink/linux/hisax.tar.gz"><A HREF="http://www.2l.net/dynalink/linux/hisax.tar.gz</A">http://www.2l.net/dynalink/linux/hisax.tar.gz that contains the sources for the hisax/isdn cards (similar to /usr/src/linux/modules/etc), including the .c and .h for the dynalink. You can't just replace this directory, with these files and do something like a 'make modules' right? Would it be to simple, to just replace one of the other card's source files, by the dynalink ones and rebuild hisax, and then start using the dynalink under the name of the other one? What if the hisax gets a new card added to it, do I: - change the Hisax source? - make modules? (/usr/src/linyx/modules/etc assume to have the needed .c and .h) - rebuild Hisax? - change the kernel? - rebuild the kernel? If I (by building it myself or getting it) have a Hisax module (.o) for my Dynalink, can it be interchanged with other SuSE 5.3 systems to have instant support without any rebuilding hassle? Can it be interchanged with RedHat 5.1 and others...? How does one make a as module? I have seen here and there that soemthing can be compiled as a module, but nowhere exactly HOW... If I would patch/build the kernel to 2.0.36 (which as I have been told has more ISDN support), would that mean that my kernel is no longer usable as SuSE kernel? This thing has got me busy, already for quite some time. And I still do not want to swap my Teles card from my other machine, with this one... and I know it must be possible somehow.. I just got back into the Linux game after a few years of denial; have to catch up a lot, like for the modules thing. I'm not a newbie in Unix though... Greetings, Frans - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
It seems there is no expertese available, about ISDN support and/or how to include new ISDN-interface support into SuSE... Frans Frans Stekelenburg wrote:
Hi,
I moved from Redhat to the new SuSE, mainly because I hoped that the ISDN support was completely up-to-date. First of all, in general : Good Job! SuSE appeared to be a pretty decent dist. (And what application is 1000erfect, right?)
First of all, as described for SuSE 5.1, there is a hisax.o and a hisax.2.5.o in de /var/modules/etc. Does this mean that still the 'standard' version is 2.1, and one has to rename 2.5.o to get the 2.5 support? I figured 2.5 hsould have been stable enuff by now?
I'm trying to get a Dynalink IS64PH+ ISDN card to function inder 5.3. Unfortunatly it is not standard supported by 5.3. What do I have to do, to get it functioning under 5.3?
If I get just the simple steps explained would already be a big help.
I'm a bit reluctant to make a whole new kernel just for this, Hisax is a module after all and I thought that that means that you don't need to do that?
The driver information for this Dynalink IS available at <A HREF="http://www.2l.net/dynalink/linux/"><A HREF="http://www.2l.net/dynalink/linux/</A">http://www.2l.net/dynalink/linux/
there is a file <A HREF="http://www.2l.net/dynalink/linux/hisax.tar.gz"><A HREF="http://www.2l.net/dynalink/linux/hisax.tar.gz</A">http://www.2l.net/dynalink/linux/hisax.tar.gz
that contains the sources for the hisax/isdn cards (similar to /usr/src/linux/modules/etc), including the .c and .h for the dynalink. You can't just replace this directory, with these files and do something like a 'make modules' right?
Would it be to simple, to just replace one of the other card's source files, by the dynalink ones and rebuild hisax, and then start using the dynalink under the name of the other one?
What if the hisax gets a new card added to it, do I: - change the Hisax source? - make modules? (/usr/src/linyx/modules/etc assume to have the needed .c and .h) - rebuild Hisax? - change the kernel? - rebuild the kernel?
If I (by building it myself or getting it) have a Hisax module (.o) for my Dynalink, can it be interchanged with other SuSE 5.3 systems to have instant support without any rebuilding hassle? Can it be interchanged with RedHat 5.1 and others...?
How does one make a as module? I have seen here and there that soemthing can be compiled as a module, but nowhere exactly HOW...
If I would patch/build the kernel to 2.0.36 (which as I have been told has more ISDN support), would that mean that my kernel is no longer usable as SuSE kernel?
This thing has got me busy, already for quite some time. And I still do not want to swap my Teles card from my other machine, with this one... and I know it must be possible somehow.. I just got back into the Linux game after a few years of denial; have to catch up a lot, like for the modules thing. I'm not a newbie in Unix though...
Greetings, Frans - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
It seems there is no expertese available, about ISDN support and/or how to include new ISDN-interface support into SuSE...
There is a suse-isdn mailing list. Perhaps you're better served there. The list is mostly in German, but when I had a problem and asked in English, there was a lot of help. I believe you can find the mailing list here: "<A HREF="http://www.suse.com/Mailinglists/index.html"><A HREF="http://www.suse.com/Mailinglists/index.html</A">http://www.suse.com/Mailinglists/index.html I've installed ISDN with success but not with a setup that looks like yours. I believe though that you'll have to make a new kernel, because you have to add ISDN support. But that's not a big issue; perhaps you'd like to use make menuconfig instead of plain make.
First of all, as described for SuSE 5.1, there is a hisax.o and a hisax.2.5.o in de /var/modules/etc. Does this mean that still the 'standard' version is 2.1, and one has to rename 2.5.o to get the 2.5 support? I figured 2.5 hsould have been stable enuff by now?
Seems so. 2.1 works for me though, so why not. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Kaare, thanks for your answer! Kaare Rasmussen wrote:
It seems there is no expertese available, about ISDN support and/or how to include new ISDN-interface support into SuSE...
There is a suse-isdn mailing list. Perhaps you're better served there. The list is mostly in German, but when I had a problem and asked in English, there was a lot of help.
Oke, although I can speak some german, I was not bold enough to do that:-) Anyway, I think now I came a lot further. Since I also heared that the 2.0.36 patch(es) included more support for ISDN cards, I stripped from the patch all the relevant diff's (as they were more or less also available in a patch for the 2.0.30A kernel). I was not yet willing enough to apply the whole patch. I checked all the files if they were oke for the changes (yes) and patched the /usr/src/linux hisax related files. Yhen indeed I had to make a new kernel. Indeed I found out to use make menuconfig (bit faster and more sure approach), and made a new kernel. (make dep; make clean; make zImage; make modules; make modules_install) This morning, so I have to test it first... (brrr...) :-) Anyone else around here who has patched SuSE with 2.0.36-7 ? Greetings, Frans
I believe you can find the mailing list here: "<A HREF="http://www.suse.com/Mailinglists/index.html"><A HREF="http://www.suse.com/Mailinglists/index.html</A">http://www.suse.com/Mailinglists/index.html
I've installed ISDN with success but not with a setup that looks like yours. I believe though that you'll have to make a new kernel, because you have to add ISDN support. But that's not a big issue; perhaps you'd like to use make menuconfig instead of plain make.
First of all, as described for SuSE 5.1, there is a hisax.o and a hisax.2.5.o in de /var/modules/etc. Does this mean that still the 'standard' version is 2.1, and one has to rename 2.5.o to get the 2.5 support? I figured 2.5 hsould have been stable enuff by now?
Seems so. 2.1 works for me though, so why not.
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (2)
-
i000372＠nl.cis.philips.com -
kar＠webline.dk