I'm new here.
And I try to get OpenWRT running on my Fritzbox 7362 SL.
Software is running, but DSL not: **Error:** Network device is not present.
After now 2 hours of searching and reading forum:
I know that I need the DSL-Modem-Driver from the original firmware.
But freetz is too old for my Ubuntu 22.04. Cannot make it.
ERROR: The program python was not found in path.
Makefile:128: *** Some build prerequisites are missing! Please install the missing packages before trying again. See http://freetz.github.io/wiki/help/howtos/common/install#NotwendigePakete for installation hints. Stop.
I have found a download in the forum for unsquashfs4-avm-be, but it can not read the file filesystem.image:
Found TI checksum (0x4308DBD5) at the end of the image.
Reading a different endian SQUASHFS filesystem on filesystem.image
Filesystem on filesystem.image is (0:0), which is a later filesystem version than I support!
Can anybody upload the dsl-modem-file for (Annex B + Vectoring) or a new unsquashfs4-avm-be.
Freetz-NG is the continuation of Freetz. I suggest that you refer to the extensive list of VRX200 xDSL versions at https://xdarklight.github.io/lantiq-xdsl-firmware-info/, which has maintained instructions for extraction of each specific version. For AVM firmwares I think the instructions you should be using are those for version 5.9.0.C.1.7-5.9.0.A.0.2 even if that isn't the version in your firmware (other AVM sourced versions have the same instructions, that's just the first AVM sourced version I looked at).
You don't necessarily need the exact version used by AVM for your device - these files aren't specific to individual router models, just to the xDSL chipset and the functional requirements of the line. Some files definitely work better in some environments than others so it can sometimes be useful to trial other versions.
The dsl0 interface won't appear until the modem has synced with the DSLAM. If there are sync issues you will have to peruse the system log - any errors that the drivers report will show there. The OpenWrt status display will report the ADSL connection stats once sync has been achieved; it will also report the line state (e.g. "showtime" once synced, "full init" during sync if I recall correctly).
I don't know what the vr9-B-dsl-new.bin file is as that file size (908916 bytes) is not in the xdarklight list - where did you extract it from?
The vr9-B-dsl.bin file would appear to be version 5.9.1.4.0.7-5.9.0.D.0.2 based on file size (908888 bytes) which seems to meet your requirements so I would specify that as the firmware file and reboot.
For debugging adding the following to /etc/rc.local might or might not help:
# check with cat /proc/driver/mei_cpe/config
# default is 4, 1 and 2 are a firehose, 3 spits out something at retrains
echo "LOG 3" > /proc/driver/mei_cpe/config
echo "TRACE 3" > /proc/driver/mei_cpe/config
Glad to hear that you now have a working connection.
For some reason I had inferred you were on ADSL rather than VDSL - my bad. For a VDSL connection, I would have expected that you could leave Tone and Encapsulation both at auto as that is what works for myself and others - but the VDSL network I'm on is likely has some differences from yours.
The problem was most likely the tone option. For VR9 modems, the supported carrier sets are different for the Annex A and Annex B firmware files (even though the annex itself refers only to ADSL). So one of the B43 options (or the auto option) needs to be used with an Annex B firmware.
By the way, only the carrier sets B43 and B43c are actually allowed to be used in the network of Deutsche Telekom (which is most likely being used by o2 in this case). V43 is explicitly disallowed, even though it seems to work as well in practice (at least on some lines).
