Re: [Linux-ATM-General] Due for a new release?

[Guy E. <gu...@tr...>]

What makes you think you are using ADSL2+???

<snip>
solos 0000:00:0c.0: Port 0: Showtime @1536/896 kb/s, SNR 29.5 dB, Attn 
27.5 dB
</snip>

That looks like ADSL1 to me.

To disable ADSL1 support..

ActivateLine Abort
AnnexACapability Disable
ActivateLine Start

Cheers,

  - Guy.


On 29/12/2010 8:27 AM, Philip Prindeville wrote:
> I'm using ADSL2+, just not the G.DMT stuff which is what I'm guessing 
> it tries to train up with first.
>
>
> On 12/28/10 1:21 PM, Guy Ellis wrote:
>> Hi Philip,
>>
>> I'm just working on a new manual, and trying to build a full list of 
>> usefull ADSL parameters.
>> If this trick works let me know and I'll include it in the manual.
>>
>> You could try turning off ADSL2/2+ support, that might speedup training.
>> Try setting these parameters in this order...
>>
>> ActivateLine Abort
>> BisACapability Disable {disable Annex A ADSL2 and ADSL2+}
>> BisMCapability Disable {disable Annex M ADSL2 and ADSL2+}
>> ActivateLine Start
>>
>> To set ADSL parameters use soloscli...
>>
>> <snip>
>> Included in the driver tarball on SourceForge is a simple CLI utility 
>> to allow access to the ADSL
>> parameters for each port. Usage...
>> $soloscli -g Port Parameter
>> $soloscli -s Port Parameter Value
>> Notes :
>> g = get
>> s = set
>> Port is the ADSL port number with a value of 0 or 1
>> </snip>
>>
>> Cheers,
>>
>>  - Guy.
>>
>>
>>
>>
>> On 29/12/2010 7:18 AM, Philip Prindeville wrote:
>>> On 12/28/10 11:20 AM, Philip Prindeville wrote:
>>>> On 12/28/10 9:31 AM, Philip Prindeville wrote:
>>>>> On 12/28/10 8:40 AM, chas williams - CONTRACTOR wrote:
>>>>>> i have released 2.5.2
>>>>> Awesome.  B
>>
>>>>> uilding now.
>>>>>
>>>> Well, with:
>>>>
>>>> astlinux, unmodified other than bumping linux-atm to 2.5.2
>>>> keeping the experimental firmware on the solos PCI card
>>>> and using the solos-0.11 download with the same patches as before
>>>>
>>>> it fails to train up.
>>>>
>>>> ...
>>>> NET: Registered protocol family 8
>>>> NET: Registered protocol family 20
>>>> Solos PCI Driver Version 0.11 svn-25
>>>> solos 0000:00:0c.0: Solos FPGA Version 0.03 svn-38
>>>> solos 0000:00:0c.0: Registered ATM device 0
>>>> solos 0000:00:0c.0: Registered ATM device 1
>>>> solos 0000:00:0c.0: Port 0: HandShake
>>>> Bridge firewalling registered
>>>> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
>>>> device eth0 entered promiscuous mode
>>>> eth1: link down
>>>> device eth1 entered promiscuous mode
>>>> Bringing up br1 as 192.168.0.2
>>>> br1: topology change detected, propagating
>>>> br1: port 1(eth0) entering forwarding state
>>>> Sleeping for 30 seconds before I bring up ppp0...
>>>> Attempting to bring up PPPoA on atm0
>>>> This could take some time...
>>>> PPP generic driver version 2.4.2
>>>> NET: Registered protocol family 24
>>>> Starting ppp.............................. timeout!
>>>> Pppd timed out waiting for negotiation!
>>>>
>>>>
>>>> not sure why this would fail.  I'm using PPPoA.  From dmesg:
>>>>
>>>> Device: 0 Vpi: 0 Vci: 32
>>>> ip_tables: (C) 2000-2006 Netfilter Core Team
>>>> nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
>>>> solos 0000:00:0c.0: Port 1: Idle
>>>> solos 0000:00:0c.0: Port 1: HandShake
>>>> Device: 0 Vpi: 0 Vci: 32
>>>> Device: 0 Vpi: 0 Vci: 32
>>>> solos 0000:00:0c.0: Port 1: Idle
>>>> solos 0000:00:0c.0: Port 0: Idle
>>>> solos 0000:00:0c.0: Port 1: HandShake
>>>> solos 0000:00:0c.0: Port 0: HandShake
>>>> Device: 0 Vpi: 0 Vci: 32
>>>> solos 0000:00:0c.0: Port 0: Training
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Port 0: Showtime @1536/896 kb/s, SNR 29.5 dB, 
>>>> Attn 27.5 dB
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.32 on port 0
>>>> Device: 0 Vpi: 0 Vci: 32
>>>>
>>>>
>>>> If I kill and restart pppd it works.
>>>>
>>>
>>> Not sure what might have changed, but the link is taking longer to 
>>> come up than before.
>>>
>>> Would be nice to be able to limit the profile (Annex A/T1.413) that 
>>> it tries to train up as, but that's not an option.
>>>
>>> If I bump the "sleep 30" to "sleep 90" then it works.
>>>
>>> -Philip
>
>


-- 
Guy Ellis
gu...@tr...
http://www.traverse.com.au
Skype: guy.ellis1
Tel:  +613 9386 4430
Fax:  +613 9386 4435