the controller has no eeprom, so it has no subvendor/subdevice id. try this: (drivers/isdn/hardware/mISDN/hfcmulti.c)
{ PCI_VENDOR_ID_CCD, PCI_DEVICE_ID_CCD_HFCE1, PCI_ANY_ID, PCI_ANY_ID, - 0, 0, 0}, + 0, 0, H(19)},
the driver should now handle this card. try it.
what vendor is this? maybe they should register at cologne chip for subvendor IDs.
[ 796.302786] Unknown HFC multiport controller (vendor:1397
device:30b1
subvendor:ffffffff subdevice:ffffffff) [ 796.302891] Please contact the driver maintainer for support
Hi Andreas
the controller has no eeprom, so it has no subvendor/subdevice id. try this: (drivers/isdn/hardware/mISDN/hfcmulti.c)
{ PCI_VENDOR_ID_CCD, PCI_DEVICE_ID_CCD_HFCE1, PCI_ANY_ID,PCI_ANY_ID,
0, 0, 0},
0, 0, H(19)},the driver should now handle this card. try it.
Thanks - I will try it today.
what vendor is this? maybe they should register at cologne chip for subvendor IDs.
The vendor is junghanns.net I got the card directly from them.
You said that the controller has no eeprom. Or do you mean that it has an eeprom that is not programmed? (FFFFFFFF). If this is the case, someone at junghanns.net might have forgotten to program the eeprom?
regards. Philipp
Hi,
i am pretty sure that it's programmed. ;)
what does lspci -v say?
Hi!
i am pretty sure that it's programmed. ;)
what does lspci -v say?
Ok, Here is the output of lspci:
==My card:==
00:09.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-E1] (rev 01) Subsystem: Cologne Chip Designs GmbH Device b553 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 9 Region 0: I/O ports at cc00 [size=8] Region 1: Memory at dfffd000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel modules: hfcmulti
lspci -nn says:
00:09.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-E1] [1397:30b1] (rev 01)
lspci -vmm says:
Slot: 00:09.0 Class: ISDN controller Vendor: Cologne Chip Designs GmbH Device: ISDN network Controller [HFC-E1] SVendor: Cologne Chip Designs GmbH SDevice: Device b553 Rev: 01
==The other (working) card:==
lspci -vvv says:
00:09.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-E1] (rev 01) Subsystem: Cologne Chip Designs GmbH Device b523 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 17 Region 0: I/O ports at cc00 [disabled] [size=8] Region 1: Memory at dfffd000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: hfc_multi Kernel modules: hfcmulti
lspci -nn says:
00:09.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network Controller [HFC-E1] [1397:30b1] (rev 01)
lspci -vmm says:
Slot: 00:09.0 Class: ISDN controller Vendor: Cologne Chip Designs GmbH Device: ISDN network Controller [HFC-E1] SVendor: Cologne Chip Designs GmbH SDevice: Device b523 Rev: 01
Not really different ?!?
regards. Philipp
On Tue, 2009-08-18 at 16:28 +0200, dexter wrote:
Hi!
i am pretty sure that it's programmed. ;)
what does lspci -v say?
Ok, Here is the output of lspci:
lspci -vmm says:
Slot: 00:09.0 Class: ISDN controller Vendor: Cologne Chip Designs GmbH Device: ISDN network Controller [HFC-E1] SVendor: Cologne Chip Designs GmbH SDevice: Device b553 Rev: 01
==The other (working) card:==
lspci -vmm says:
Slot: 00:09.0 Class: ISDN controller Vendor: Cologne Chip Designs GmbH Device: ISDN network Controller [HFC-E1] SVendor: Cologne Chip Designs GmbH SDevice: Device b523 Rev: 01
Not really different ?!?
the differences are the PCI IDs from the cards..
The Junghanns IDs are b553 for single E1 and b554 for double E1
the other card has
E1 IOB1E1 $1397 $30B1 $1397 $B523
This is a reference card from a manufacturer... i have the same card.. i bought it from Comsat and they told me thats the ID from the manufacturer...
But your card with PCI ID b553 should work.
regards. Philipp
regards,
René
Like I said, the Junghanns card gets recognized correctly with kernel 2.6.30.4 or latest external mISDN package.
--j
Am 18.08.2009 um 16:41 schrieb Rene Stegmaier:
On Tue, 2009-08-18 at 16:28 +0200, dexter wrote:
Hi!
i am pretty sure that it's programmed. ;)
what does lspci -v say?
Ok, Here is the output of lspci:
lspci -vmm says:
Slot: 00:09.0 Class: ISDN controller Vendor: Cologne Chip Designs GmbH Device: ISDN network Controller [HFC-E1] SVendor: Cologne Chip Designs GmbH SDevice: Device b553 Rev: 01
==The other (working) card:==
lspci -vmm says:
Slot: 00:09.0 Class: ISDN controller Vendor: Cologne Chip Designs GmbH Device: ISDN network Controller [HFC-E1] SVendor: Cologne Chip Designs GmbH SDevice: Device b523 Rev: 01
Not really different ?!?
the differences are the PCI IDs from the cards..
The Junghanns IDs are b553 for single E1 and b554 for double E1
the other card has
E1 IOB1E1 $1397 $30B1 $1397 $B523
This is a reference card from a manufacturer... i have the same card.. i bought it from Comsat and they told me thats the ID from the manufacturer...
But your card with PCI ID b553 should work.
regards. Philipp
regards,
René
Rene Stegmaier rene@rr47.de LAN-TEX Schuberstr. 14 38518 Gifhorn Mobil: 01703183653
-- Jens David, DG1KJD jens.david@jens-david-consulting.com http://www.jens-david-consulting.com
-
Andreas.Eversberg -
dexter -
Jens David -
Klaus-Peter Junghanns -
Rene Stegmaier