2005-03-04 04:26:18

by Marko Rebrina

[permalink] [raw]
Subject: Problem with w6692 & kernel >=2.6.10

I have problem with w6692 (mISDN-2005-02-25) & kernel >=2.6.10 (with
2.6.9 is OK!)

# lspci
0000:01:07.0 Network controller: Winbond Electronics Corp W6692 (rev 01)

# modprobe w6692pci protocol=2
FATAL: Error inserting w6692pci
(/lib/modules/2.6.11/kernel/drivers/isdn/hardware/mISDN/w6692pci.ko):
No such device

log:

CAPI Subsystem Rev 1.1.2.8
capi20: Rev 1.1.2.7: started up with major 68 (middleware+capifs)
Modular ISDN Stack core $Revision: 1.23 $
mISDNd: kernel daemon started
ISDN L1 driver version 1.11
ISDN L2 driver version 1.19
mISDN: DSS1 Rev. 1.26
Capi 2.0 driver file version 1.14
ISAC module $Revision: 1.16 $

Winbond W6692 PCI driver Rev. 1.12
ACPI: PCI interrupt 0000:01:07.0[A] -> GSI 19 (level, high) -> IRQ 19
mISDN_w6692: found adapter Winbond W6692 at 0000:01:07.0
W6692: Winbond W6692 version (0): W6692 V00
kcapi: Controller 1: mISDN1 attached
mISDNd: test event done
w6692: IRQ 19 count 4
kcapi: card 1 "mISDN1" ready.
w6692 1 cards installed
try_ok(13) try_wait(0) try_mult(0) try_inirq(0)
irq_ok(4) irq_fail(0)
release_l1 id 1
release_udss1 refcnt 1 l3(f39faa40) inst(f39faab8)
kcapi: card 1 down.
kcapi: Controller 1: mISDN1 unregistered


2005-03-21 22:35:40

by Andrew Morton

[permalink] [raw]
Subject: Re: Problem with w6692 & kernel >=2.6.10

Marko Rebrina <[email protected]> wrote:
>
> I have problem with w6692 (mISDN-2005-02-25) & kernel >=2.6.10 (with
> 2.6.9 is OK!)

There haven't been any changes in the w6692 driver for ages, so I'd be
suspecting PCI changes or something like that. Are you able to test
2.6.12-rc1?


> # lspci
> 0000:01:07.0 Network controller: Winbond Electronics Corp W6692 (rev 01)
>
> # modprobe w6692pci protocol=2
> FATAL: Error inserting w6692pci
> (/lib/modules/2.6.11/kernel/drivers/isdn/hardware/mISDN/w6692pci.ko):
> No such device
>
> log:
>
> CAPI Subsystem Rev 1.1.2.8
> capi20: Rev 1.1.2.7: started up with major 68 (middleware+capifs)
> Modular ISDN Stack core $Revision: 1.23 $
> mISDNd: kernel daemon started
> ISDN L1 driver version 1.11
> ISDN L2 driver version 1.19
> mISDN: DSS1 Rev. 1.26
> Capi 2.0 driver file version 1.14
> ISAC module $Revision: 1.16 $
>
> Winbond W6692 PCI driver Rev. 1.12
> ACPI: PCI interrupt 0000:01:07.0[A] -> GSI 19 (level, high) -> IRQ 19
> mISDN_w6692: found adapter Winbond W6692 at 0000:01:07.0
> W6692: Winbond W6692 version (0): W6692 V00
> kcapi: Controller 1: mISDN1 attached
> mISDNd: test event done
> w6692: IRQ 19 count 4
> kcapi: card 1 "mISDN1" ready.
> w6692 1 cards installed
> try_ok(13) try_wait(0) try_mult(0) try_inirq(0)
> irq_ok(4) irq_fail(0)
> release_l1 id 1
> release_udss1 refcnt 1 l3(f39faa40) inst(f39faab8)
> kcapi: card 1 down.
> kcapi: Controller 1: mISDN1 unregistered
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/

2005-03-22 07:00:01

by Karsten Keil

[permalink] [raw]
Subject: Re: Problem with w6692 & kernel >=2.6.10

On Mon, Mar 21, 2005 at 02:28:23PM -0800, Andrew Morton wrote:
> Marko Rebrina <[email protected]> wrote:
> >
> > I have problem with w6692 (mISDN-2005-02-25) & kernel >=2.6.10 (with
> > 2.6.9 is OK!)
>
> There haven't been any changes in the w6692 driver for ages, so I'd be
> suspecting PCI changes or something like that. Are you able to test
> 2.6.12-rc1?
>

Marko do not point to the in kernel w6692 driver, but to the (still ALPHA)
mISDN driver from cvs.isdn4linux.de.
This driver had a problem with the pci_register_driver return code changes
in 2.6.10, it now always returns 0 (if no error), but < 2.6.10 did return
the number of detected devices, which was tested in this driver.
This is fixed since last week in our CVS.

--
Karsten Keil
SuSE Labs
ISDN development

2005-05-25 22:20:04

by Andrew Morton

[permalink] [raw]
Subject: Re: Problem with w6692 & kernel >=2.6.10

Marko Rebrina <[email protected]> wrote:
>
> I have problem with w6692 (mISDN-2005-02-25) & kernel >=2.6.10 (with
> 2.6.9 is OK!)

It'd be nice to get regressions such as this fixed for 2.6.12. Could you
please retest 2.6.12-rc5?

> # lspci
> 0000:01:07.0 Network controller: Winbond Electronics Corp W6692 (rev 01)
>
> # modprobe w6692pci protocol=2
> FATAL: Error inserting w6692pci
> (/lib/modules/2.6.11/kernel/drivers/isdn/hardware/mISDN/w6692pci.ko):
> No such device
>
> log:
>
> CAPI Subsystem Rev 1.1.2.8
> capi20: Rev 1.1.2.7: started up with major 68 (middleware+capifs)
> Modular ISDN Stack core $Revision: 1.23 $
> mISDNd: kernel daemon started
> ISDN L1 driver version 1.11
> ISDN L2 driver version 1.19
> mISDN: DSS1 Rev. 1.26
> Capi 2.0 driver file version 1.14
> ISAC module $Revision: 1.16 $
>
> Winbond W6692 PCI driver Rev. 1.12
> ACPI: PCI interrupt 0000:01:07.0[A] -> GSI 19 (level, high) -> IRQ 19
> mISDN_w6692: found adapter Winbond W6692 at 0000:01:07.0
> W6692: Winbond W6692 version (0): W6692 V00
> kcapi: Controller 1: mISDN1 attached
> mISDNd: test event done
> w6692: IRQ 19 count 4
> kcapi: card 1 "mISDN1" ready.
> w6692 1 cards installed
> try_ok(13) try_wait(0) try_mult(0) try_inirq(0)
> irq_ok(4) irq_fail(0)
> release_l1 id 1
> release_udss1 refcnt 1 l3(f39faa40) inst(f39faab8)
> kcapi: card 1 down.
> kcapi: Controller 1: mISDN1 unregistered
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/