Bug#272523: Not really fixed
Hello,
well in further tests I had two more cases where it didn't boot like
described before. During my last tests where 4-5 boots with version
2.6.8-4 worked flawlessly I had no AVM PCMCIA ISDN Fritzcard in my
laptop. In the two cases where it didn't work again I had the AVM PCMCIA
ISDN Fritzcard back in. But in a third case - directly afterwards - it
still did work with the card plugged into the PCMCIA slot.
So this does not seem to be fixed completely.
Its difficult to find a pattern in all of this.
This how the AVM card is detected:
Oct 15 21:59:11 localhost kernel: HiSax: Card 1 Protocol EDSS1 Id=HiSax
(0)
Oct 15 21:59:11 localhost kernel: HiSax: AVM A1 PCMCIA driver Rev. 2.9.2.5
Oct 15 21:59:11 localhost kernel: AVM A1 PCMCIA: io 0x140 irq 3 model 1
version 2
Oct 15 21:59:11 localhost kernel: AVM A1 PCMCIA: ISAC version (0):
2086/2186 V1.1
Oct 15 21:59:11 localhost kernel: AVM A1 PCMCIA: HSCX version A: V2.1 B:
V2.1
Oct 15 21:59:11 localhost kernel: AVM A1 (PCMCIA): IRQ 3 count 2
Oct 15 21:59:11 localhost kernel: AVM A1 (PCMCIA): IRQ 3 count 6
Oct 15 21:59:11 localhost kernel: HiSax: DSS1 Rev. 2.32.2.3
Oct 15 21:59:11 localhost kernel: HiSax: 2 channels added
Oct 15 21:59:11 localhost kernel: HiSax: MAX_WAITING_CALLS added
Oct 15 21:59:11 localhost kernel: HiSax: if_command 6 called with invalid
driverId 0!
Oct 15 21:59:11 localhost kernel: HiSax: if_command 6 called with invalid
driverId 0!
Regards,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
Reply to: