OK I had another go today and I thought I'd report to the list.
Basically, it didn't work again, although it didn't oops this time.

Here is some kernel output:

Aug 26 14:36:52 milton kernel: Linux version 2.4.21 (root@morrison) (gcc
version 2.95.4 20011002 (Debian prerelease)) #1 Mon Aug 25 17:14:52 NZST
2003
Aug 26 14:36:52 milton kernel: itexadsl: version= 2.2.7.ITEXPC86.0005 ,
built date= Thu Feb 7 11:16:17 PST 2002
Aug 26 14:36:52 milton kernel: itexadsl: card# 0, ix=0x0, bus=0x0,
fn=0x70, ven=0x1471, dev=0x188
Aug 26 14:36:52 milton kernel: itexadsl: total 1 card(s) found.
Aug 26 14:36:52 milton kernel: itexadsl: irq=0xa, ioaddr=0x6800,
membase=0xe4000000
Aug 26 14:36:52 milton kernel: itexadsl: card #0 - MAC:
00:01:a0:04:04:73 from eeprom.
Aug 26 14:36:52 milton kernel: itexadsl: ITeX i90134 chip.
Aug 26 14:36:52 milton kernel: init_module: cardcnt = 1
Aug 26 14:36:52 milton kernel: Into the GenCRC10Table
Aug 26 14:36:52 milton kernel: Finished the GenCRC10Table
Aug 26 14:36:52 milton kernel: itexadsl: modem line disconnected.
Aug 26 14:36:52 milton kernel: atm_connect (TX: cl 1,bw 0-0,sdu 16386;
RX: cl 1,bw 0-0,sdu 1502,AAL 5)
Aug 26 14:36:52 milton kernel: itex_open: opening vpi.vci 0.100 on 0 NIC
card
Aug 26 14:36:52 milton kernel: itex_open: tx and rx vci already in use
on 0 NIC
card.
Aug 26 14:36:54 milton kernel: card #0 - current modem state :
INITIALIZING.
Aug 26 14:37:02 milton kernel: itexadsl: modem line connected. (card_no:
0)
Aug 26 14:37:02 milton kernel: itexadsl: upstream latency - interleaved
Aug 26 14:37:02 milton kernel: itexadsl: downstream latency -
interleaved
Aug 26 14:37:02 milton kernel: itexadsl: card #0 - data rate: 736 / 6496
(line
rate: 896 / 7468) kbps
Aug 26 14:37:02 milton kernel: connect_bh:tx cell per msec 2
Aug 26 14:37:02 milton kernel: connect_bh: upstream rate 736
Aug 26 14:37:02 milton kernel: card #0 - current modem state :
SHOWTIME_L0.
Aug 26 14:39:11 milton kernel: atm_connect (TX: cl 1,bw 0-0,sdu 16386;
RX: cl 1,bw 0-0,sdu 1502,AAL 5)
Aug 26 14:39:11 milton kernel: itex_open: opening vpi.vci 0.100 on 0 NIC
card
Aug 26 14:39:11 milton kernel: itex_open: tx and rx vci already in use
on 0 NIC
card.

The kernel is compiled with ATM and PPP over ATM support.

The above seems to indicate that the modem is getting a signal on the
line ok (SHOWTIME_L0), but things aren't working when ppp starts and
tries to talk to th driver (itex_open: tx and rx vci already in use
on 0 NIC)

I suspect there were atm changes from 2.4.20 to 2.4.21? I will probably
look at the patch file and see what has changed and maybee try to reverse
some changes and see if i can get it going.

I would like to know how many people are using this type of modem with
linux, and if anyone has it working with 2.4.21 or later.

If others are interested in this, we could try asking itex to release
another driver.

Alex

On Fri, Jul 04, 2003 at 10:09:45AM +1200, Alex King wrote:
> Is anyone using this combination sucessfully? (ITEX chipset internal
> modem and 2.4.21 kernel?)
>
> I've been using the 2.4.16 drivers successfully with 2.4 kernels up to
> 2.4.20, but I get a kernel fault (oops I think) when loading it with a
> 2.4.21 kernel.
>
> Anyone else seeing this?
>
> I will do more testing when I get around to it.....
>
> Alex

-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message 
 
-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message