Opened 10 years ago
Last modified 10 years ago
#601 assigned comment
Driver for ISDN card Eicon/Diehl doesn't load during boot
| Reported by: | haraldkamm | Owned by: | David Azarewicz |
|---|---|---|---|
| Priority: | major | Milestone: | Feedback pending |
| Component: | ACPI PSD | Version: | 3.22.03 |
| Keywords: | Cc: |
Description
Using recent versions of ACPI the driver for an ISDN card Eicon/Diehl doesn't load any more during boot process. I fileattach a screenshot of the boot process and the testlog.cmd output. Any hint would be very appreciated. Thanks so much, Harald
Attachments (4)
Change History (14)
by , 10 years ago
| Attachment: | HAL-20140818-acpi-3.22.03.zip added |
|---|
by , 10 years ago
| Attachment: | IMG_0612.JPG added |
|---|
comment:1 by , 10 years ago
| Milestone: | → Feedback pending |
|---|---|
| Owner: | set to |
| Status: | new → assigned |
| Type: | defect → comment |
Why do you think this has something to do with ACPI? You didn't say what led you to that conclusion.
I would be happy to look at the log file, however the one you uploaded does not contain useful information. Probably because you ran the testlog program more than once. You should only run it once after booting since it clears all the data when it is run. Also your PCI.EXE is extremely out of date. You should update it, or use the one that comes in the ACPI distribution.
comment:2 by , 10 years ago
I thought that this might be related with ACPI as the driver loaded fine before using more recent ACPI releases (up to now I didn't worry about the problem still running eCS 1.2 with ACPI 3.18): for example it still works perfectly with the outdated ACPI 3.18 on the same system. The pci.exe is the one coming with ACPI i. e. dated 13.10.2005. I updated the pcidevs.txt using the one dated 22.04.2014. I cleaned the %temp% directory and ran testlog.cmd again. The result is fileattached. Thanks so much, Harald
by , 10 years ago
| Attachment: | HAL-20140821-acpi-3.22.03.zip added |
|---|
Updated output of "testlog.cmd acpi"
comment:3 by , 10 years ago
I'm sorry I didn't see this before but it seams that in your acpid.cfg file you have the following option set:
AcpiLog = h:\AcpiCA.log
You must remove this line or comment it out in order for the testlog program to extract all the necessary data. Last time I assumed it was because you ran the testlog command more than once, but this is probably the reason.
Please remove or comment that line, reboot, and re-run the testlog and attach the new log to this ticket. Also, if you have a file named acpi.cfg (not acpid.cfg) somewhere on your system, please attach that file, too.
(I updated the the testlog.cmd program to check for this setting in the acpid.cfg file. You can re-download that if you like.)
comment:4 by , 10 years ago
I commented the acpilog line out and reran the updated testlog command. According to the documentation there isn't any acpi.cfg on this system.
by , 10 years ago
| Attachment: | HAL-20140822-acpi-3.22.03.zip added |
|---|
Updated output of "testlog.cmd acpi" without acpiCA.log
comment:5 by , 10 years ago
I don't see anything in the log files that would indicate any problems in the PSD. There are numerous bugs in your ACPI but the PSD appears to be handling them OK. Your problem does not appear to be a problem with the PSD. Since everything from the hardware and PSD point of view seems to be OK, the only way to know what the problem is is to determine what the driver is doing that is failing. Since I can't do that without the harware and drivers, the only thing left to do is guess.
- The old 3.18 PSD used a acpi.cfg file. It doesn't matter what any documentation says. I would like to see that file if it is on your system. It is probably in your /OS2/BOOT directory.
- Your CONFIG.SYS is very disorganized. It is difficult to tell what is loaded and in what order. There are likely load order violations. This may or may not be contributing to your problem. Check out cfgsort. Backup first.
- The GenMac driver has a known memory corruption issue in certain situations. This may or may not be happening on your system and may or may not be contributing to your problem. You could try commenting it out and see what happens.
- You could look in the ISDN driver documentation to see exacly what the error message from the driver means.
comment:6 by , 10 years ago
As said before, there currently is no evidence that shows that this issue is a problem with the ACPI.PSD. Even so, I am willing to help resolve your issue. However, there is nothing more I can do without further information about the driver you are using.
follow-up: 8 comment:7 by , 10 years ago
In case it helps, the Eicon ISDN adapter source code (obviously, the Linux driver) can be found here:
http://www.tsri.com/jeneral/drivers/drivers/isdn/hardware/eicon/diva_didd.c/pm/PM-PROC_READ.html
Maybe that gives a clue why "connecting to the DIDD registry" fails.
comment:8 by , 10 years ago
Replying to erdmann:
In case it helps, the Eicon ISDN adapter source code (obviously, the Linux driver) can be found here:
http://www.tsri.com/jeneral/drivers/drivers/isdn/hardware/eicon/diva_didd.c/pm/PM-PROC_READ.htmlMaybe that gives a clue why "writing to the DIDD registry" fails.
No, that did not provide any useful information.
comment:9 by , 10 years ago
Perhaps the DIDD.OS2 driver did not load. Unfortunately, there was not enough information provided to determine that. You should make sure that ALL drivers loaded successfully prior to the ones shown in your screen shot.
comment:10 by , 10 years ago
The driver software is here: http://hobbes.nmsu.edu/download/pub/os2/system/drivers/network/diva.zip
after reading through the PDF documentation contained in the driver package and looking at the config.sys and assuming that a PCI card is used I suggest to specify this in config.sys: DEVICE=h:\ISDN\DIDD.OS2 DEVICE=h:\ISDN\DIMAINT.OS2 DEVICE=h:\ISDN\TEDETSI.OS2 -a$ DEVICE=h:\ISDN\DIAPIS.OS2 DEVICE=h:\ISDN\CAPI20.OS2
Specifying -a$ will use the PCI related parameters (the card's IRQ, memory window etc.) as the BIOS has set them up.
testlog.cmd output