On Wed, Aug 27, 2003 at 08:50:49AM +1200, Mark Evans wrote:
> > From: Alex King [mailto:alex@king.net.nz]
> > Subject: Re: ITEX chipset and linux 2.4.21
> >
> > 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
>
> promising
>
> > 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
>
> still promising
>
> > (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.
>
> i'll take a look at my config. i'm _not_ running 2.4.2x mind.
> but it may be of value?
>
> > If others are interested in this, we could try asking itex to
> > release another driver.
>
> last i looked itex had gone bust!?!
>
Yep, and their support address bounces. However there is still another
googleable email there I haven't tried. Also, products are still being
made with the ITEX chipsets afaik, so someone will/has bought the chip
designs and the rights to produce them, it would have been the primary
asset of the old company. Once we find out who has boutght it out, we
can get on to them for a driver.

Just to reiterate, I have the driver working 100% for 2.4.18 thru
2.4.20, it's only with 2.4.21 that I have these problems (I haven't
tried 2.4.22 yet but I suspect the problem will persist there too).

I looked at the changelogs and patches last night for 2.4.21, and there
were certainly changes to the ATM code, I suspect this is what is
causing the problem. I may have a go at reversing out the ATM changes
from 2.4.21 and 2.4.22 and see if I can get one of these kernels to
compile and take the ITEX driver. However I don't know how the changes
in the ATM code may be interdependant with other networking code
changes, and I'm not a kernel programmer :(

The other problem is that I don't have an itex card at home, so I have
to do my testing at clients' premises, which is an inconvinience to say
the least. I am tossing up buying another card, but I'm reluctant to
spend more money on getting _another_ card that may end up being
completely useless. I used to be happy to buy and recommend these
modems, at least they had some kind of linux driver, and it worked very
well. Now I'm up the creek without a paddle - I was a fool for relying
on binary drivers.....

Alex
>
> --
> me

-- 
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