> I already obtained the error message, and it is the one which Shaul Karl
> shows in the following (or substantially equivalent thereof). The error
> message is self-explanatory.
>
> So it seems that I have to either replace my ISDN card or wait for a
> certified version of the driver to come along.
>
I am not sure about it:
(1) Facts:
[21:24:53 tmp]$ zgrep -A19 '25.2. c' /usr/share/doc/isdnutils-doc/FAQ/i
4lfaq.txt.gz
25.2. country_certified: Is isdn4linux approved for use by the
telecommunications authorities?
That depends on the driver used, and your country. We only have
information about Germany (send me information if you have information
about other countries). However, that covers most other European
countries as well, since a certification in one EC country has to be
accepted in all others. These drivers are certified for use in
Germany:
o Active cards: the approval covers the entire card including its
firmware. Thus the approval also covers the use of these cards with
isdn4linux.
o Elsa Quickstep series cards (new name Microlink PCI)
o Eicon Diva 2.01 PCI
o Passive cards: all cards based on the HFC-S chipset.
[21:25:03 tmp]$
[19:26:52 tmp]$ zgrep -A10 '7.26. ' /usr/share/doc/isdnutils-doc/FAQ/i4
lfaq.txt.gz
7.26. trouble_unauthorizedcodechange: When HiSax starts, I get the
error messages 'Approval certification failed, unauthorized source
code changes'?
Since the certification of the HiSax driver is only valid for
unchanged source code, the source code is protected by a checksum.
When you get this message, then either you have changed the source
code yourself, or the author did not update the checksum when changing
the source code (reason could be that the complete certification tests
have not yet been run on the changed code).
/usr/share/doc/kernel-doc-2.2.20/Documentation/isdn/HiSax.cert which is
too long to quote here.
(2) My interpretation:
The certification only certifies that the combination of software and
hardware for which it was tested with is working according to the ISDN
protocol. Therefore, the fact that your software version is not
certified is not necessarily the reason for which your machine get
stuck. Further more, assuming that neither the ISDN protocol nor the
card interface were changed between 2.0.36 and present time, I would
say that this is either a bug in the ISDN software or a configuration
problem. Yet if the problem persists although it worked in the past and
you have tried a few versions of a newer ISDN software then it looks as
if there is a higher probability that there is a configuration problem.
(3) Some suggestions:
* Modify the source code so that the procedure that tests for the
certification will return a certified response. Easier said then done.
Looks like /usr/local/src/linux/kernel-source-2.2.20/drivers/isdn/hisax/
hisax.h is where to start looking as it has int certification_check(int
output) line. In addition, /usr/local/src/linux/kernel-source-2.2.20/Doc
umentation/isdn/HiSax.cert has a list of affected files. I have not
read the details.
* Script started on Mon Jan 21 21:20:02 2002
[21:20:03 tmp]$ zgrep -A60 'At the moment, debugging'
/usr/share/doc/isdnutils-base/README.HiSax.gz
At the moment, debugging messages are enabled with the hisaxctrl tool:
hisaxctrl <DriverId> DebugCmd <debugging_flags>
<DriverId> default is HiSax, if you didn't specify one.
DebugCmd is 1 for generic debugging
11 for layer 1 development debugging
13 for layer 3 development debugging
where <debugging_flags> is the integer sum of the following debugging
options you wish enabled:
With DebugCmd set to 1:
0x0001 Link-level <--> hardware-level communication
0x0002 Top state machine
0x0004 D-Channel Frames for isdnlog
0x0008 D-Channel Q.921
0x0010 B-Channel X.75
0x0020 D-Channel l2
0x0040 B-Channel l2
0x0080 D-Channel link state debugging
0x0100 B-Channel link state debugging
0x0200 TEI debug
0x0400 LOCK debug in callc.c
0x0800 More paranoid debug in callc.c (not for normal use)
0x1000 D-Channel l1 state debugging
0x2000 B-Channel l1 state debugging
With DebugCmd set to 11:
0x0001 Warnings (default: on)
0x0002 IRQ status
0x0004 ISAC
0x0008 ISAC FIFO
0x0010 HSCX
0x0020 HSCX FIFO (attention: full B-Channel output!)
0x0040 D-Channel LAPD frame types
0x0080 IPAC debug
0x0100 HFC receive debug
0x0200 ISAC monitor debug
0x0400 D-Channel frames for isdnlog (set with 1 0x4 too)
0x0800 D-Channel message verbose
With DebugCmd set to 13:
1 Warnings (default: on)
2 l3 protocol descriptor errors
4 l3 state machine
8 charge info debugging (1TR6)
For example, 'hisaxctrl HiSax 1 0x3ff' enables full generic debugging.
Because of some obscure problems with some switch equipment, the delay
between the CONNECT message and sending the first data on the B-channel
is now
configurable with
hisaxctrl <DriverId> 2 <delay>
<delay> in ms Value between 50 and 800 ms is recommended.
* Ah ... well, a new card?
>
> On Mon, 21 Jan 2002, Shaul Karl wrote:
>
> > Can you follow the following procedure
> >
> > (1) Have the system boot with the ISDN utilities disabled.
> > (2) Manually issue the commands that the start up scripts would issue
> > the concern the ISDN card and ISDN configuration.
> >
> > Now what are the error messages that you get? It might help if you run
> > the above procedure with the script command and post the typescript
> > file.
> >
> > [19:26:52 tmp]$ zgrep -A10 '7.26. ' /usr/share/doc/isdnutils-doc/FAQ/i4
> > lfaq.txt.gz
> > 7.26. trouble_unauthorizedcodechange: When HiSax starts, I get the
> > error messages 'Approval certification failed, unauthorized source
> > code changes'?
> >
> > Since the certification of the HiSax driver is only valid for
> > unchanged source code, the source code is protected by a checksum.
> > When you get this message, then either you have changed the source
> > code yourself, or the author did not update the checksum when changing
> > the source code (reason could be that the complete certification tests
> > have not yet been run on the changed code).
> >
> > [19:27:03 tmp]$
>
> --- Omer
> There is no IGLU Cabal. No one legally, properly and
> bureaucratically certified the IGLU Cabal, and the prospective
> participants used up all their lawbreaking karmas.
> WARNING TO SPAMMERS: see at http://www.zak.co.il/spamwarning.html
>
>
> =================================================================
> To unsubscribe, send mail to [EMAIL PROTECTED] with
> the word "unsubscribe" in the message body, e.g., run the command
> echo unsubscribe | mail [EMAIL PROTECTED]
>
--
Shaul Karl
email: shaulka(at-no-spam)bezeqint.net
Please substitute (at-no-spam) with an at - @ - character.
(at-no-spam) is meant for unsolicitate mail senders only.
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
