![](https://seccdn.libravatar.org/avatar/0e9cdb37ec7f648122bcf5fd256d31e3.jpg?s=120&d=mm&r=g)
[Zusammenfassung auf Deutsch am ende] After having had used a Fritz!Classic for a long time when I had ISDN I though I do a friend of mine here a favor and bought him a Fritz!PCI The hardware support list says this is supported in the kernel (he is running SuSE 7.0/ 2.2.16), but things did not work. I traced it down (using lspci -v) to the fact that the linux sources for hisax only know about a device with device ID 0a00, which is marked in /usr/share/pci.ids as 1244 0a00 A1 ISDN [Fritz] I called AVM and got confirmed that they recently changed to new hardware. Then I found some messages on this list from March, reporting similar problems, which unfortunately did not result in an update of the supported hardware list. (someone even suggested that since this is a revision 1 board it is older than his revision 2 board, probably also recommends people that 2.2.19 is newer than 2.4.5-pre1 :) I tried the obvious: change the #define in drivers/isdn/hisax/avm_pci.c (on the 2.2.16 sources), recompile and install, reboot. But then the system hangs. I will ask my friend to look at the board next time he opens the machine to look at the chipset, but it might not be so compatable as the support guy at AVM said it would be. I was reluctant to try the binary stuff from capi4linux that AVM provides and when I did, I got a protocol error when trying the local provider here ( terra.es ) connecting to the AVM server seemed to work, so at least the board is working. (Which we new, since it works under Win98, the whole idea however was to stimulate my friend to use Linux) Does anybody has this board (not the old 0a00 PCI one) running? Anybody got a clue why the hardware support database was not updated when people started complaining on this list? Regards Anthon van der Neut Las Palmas de Gran Canaria Da die liste mich auf Englisch begruesst hat nehme ich mahl an das das die sprache ist, aber ich habe bisher nuer deutsche emails gesehen. Kurzgefasst: AVM hat eine neue PCI karte heraus ( id 0e00 statt 0a00 fuer die alte) und die sources kennen nur die 0a00 id code zum checken des PCI geraets. Dadurch wird diese karte nicht erkannt. Ich habe versucht die #define fuer die ID zu aenderen auf 0e00 da mann mir bei AVM gesacht hat das die hardware compatible ist. Nach herkompilieren, installieren und rebooten des kernels. Hangt die installation von hisax.o mit id=27 das ganze system. Soviel zum thema hardware kompatibel. AVM's capi4linux ist eine binary distro (Not A Good Thing(R)), und hat problemen mit provider hier (Las Palmas), mit eine protocol error. Gibts dan leute die das zum laufen haben (den NEUE PCI nicht die alte).