BTW, I checked dmesg BEFORE running the configure script:

...
visdn: loading
hfc-4s: HFC-4S HFC-8S Driver loading
ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
GSI 20 sharing vector 0x3A and IRQ 20
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC4] -> GSI 19 (level,
low) -> IRQ 58
PCI: Setting latency timer of device 0000:01:07.0 to 64
hfc-4s: pci-0000:01:07.0 HFC-4S chip rev. 01 detected, using quartz=24
MHz, doubleclock=0
hfc-4s: pci-0000:01:07.0 resetting
NUM CHANS: 0
hfc-4s: pci-0000:01:07.0 configured at mem 0xea006000
(0xffffc20000064000) IRQ 58
...

And AFTER:
...
visdn: loading
hfc-4s: HFC-4S HFC-8S Driver loading
ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
GSI 20 sharing vector 0x3A and IRQ 20
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC4] -> GSI 19 (level,
low) -> IRQ 58
PCI: Setting latency timer of device 0000:01:07.0 to 64
hfc-4s: pci-0000:01:07.0 HFC-4S chip rev. 01 detected, using quartz=24
MHz, doubleclock=0
hfc-4s: pci-0000:01:07.0 resetting
NUM CHANS: 0
hfc-4s: pci-0000:01:07.0 configured at mem 0xea006000
(0xffffc20000064000) IRQ 58
...
hald-probe-smbi[2719] trap stack segment rip:4010d0 rsp:7fffffc5d3c0
error:0
visdn-netdev: Netdevice gateway loading
visdn-streamport: vISDN streamport module loading
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
visdn-ppp: vISDN ppp gateway module loading
vts_timer_open()
visdn-ec-kb:  echo canceller module for vISDN loading
hfc-pci: HFC-S PCI A Driver loading
hfc-usb: HFC-USB Driver loading
usbcore: registered new driver hfc-usb
NET: Registered protocol family 30

lapd: NETDEV_UP visdn1.0


lapd: NETDEV_UP visdn1.1


lapd: NETDEV_UP visdn1.2


lapd: NETDEV_UP visdn1.3

[EMAIL PROTECTED] ~]#

How the hell is a PCI card configured at IRQ 58??? I'm not really into
interrupts, but I thought at IRQ 15 or so the numbers end... Also the
output of NUM CHANS: 0 bothers me a bit.
Don't get me wrong, but I don't know HOW a computer works in detail, nor
am I understanding what all the files are good for on Linux machines,
but my gut-feeling tells me there's something wrong with the integration
of the card in the first place.
Should I be wrong or proven wrong, I'm eager to learn ;-)

_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers

Reply via email to