> 
> The firmware reports identical:
> DSL_CPE#>vig
> nReturn=0 DSL_DriverVersionApi=3.24.4.4 DSL_ChipSetFWVersion=2.4.4.0.0.1 
> DSL_ChipSetHWVersion=1.5 DSL_ChipSetType=Ifx-Danube 
> DSL_DriverVersionMeiBsp=5.0.0
> nReturn=0 DSL_DriverVersionApi=3.24.4.4 DSL_ChipSetFWVersion=2.4.4.0.0.1 
> DSL_ChipSetHWVersion=1.5 DSL_ChipSetType=Ifx-Danube 
> DSL_DriverVersionMeiBsp=5.0.0
> 
> The control app behaves rather differently, spawning a number of
> processes on backfire, but only one on trunk. Plus the changes to the
> params.
> 
> Backfire
> 1021 root      1204 S    /sbin/dsl_cpe_control -i -f /lib/firmware/ModemHWE.bi
> 1027 root      1204 S    /sbin/dsl_cpe_control -i -f /lib/firmware/ModemHWE.bi
> 1028 root      1204 S    /sbin/dsl_cpe_control -i -f /lib/firmware/ModemHWE.bi
> 1029 root      1204 S    /sbin/dsl_cpe_control -i -f /lib/firmware/ModemHWE.bi
> 1030 root      1204 S    /sbin/dsl_cpe_control -i -f /lib/firmware/ModemHWE.bi
> 
> Trunk
> 1304 root      7408 S    /sbin/dsl_cpe_control -i00_00_00_00_00_01_00_00 -n /

these are the xtu bits.

in trunk you need to tell the network scripts what annex you are using.

this is handled by
target/linux/lantiq/base-files/etc/uci-defaults/network

please make sure you set the correct annex in uci before starting dsl


> Apologies if this is just noise.
> 

lol... no really ...
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to