Nice one!!
If im understanding the changes - this will remove the dual kernel boot structure that oem has.
If someone wanted to restore back to oem firmware, what would the process be?
I did it because there's no simple way to switch images anyway.
Simply run recovery app from AVM to flash FRITZ!OS. Original partition table is hardcoded in EVA (urlader partition) so it will always work.
1 Like
Awesome. I’ll use this approach for 7490 too then.
Hi Daniel, I would like to try this latest snapshot image on a 7362sl, but having hard time finding appropriate file *initramfs-kernel.bin, mentioned in installation instructions in your commit:
Installation via FTP:
- Use scripts/flashing/eva_ramboot.py to send initramfs-kernel.bin
to the device when powering on.
...
There is no such file on xrx200 snapshot path on download servers, only sysupgrade one.
I admit there are great chance I am missing something obvious how stuff works in openwrt
Thank you for all!
Yes, for some reason snapshot builds for xrx200 don't include initramfs images. You should build one yourself, either from scratch or with the image builder in xrx200 directory.
I bumped into the same thing when compiling master for my second hand 7362 SL last night. I'll send in a patch soon so the initramfs gets built.
Thanks for your work @danijeltudek!
Edit: turns out it's not so simple to enable it by default, I've opened a topic for it.
Hi,
at first, thx for your work! I have to admit, that I'm a total noob, so if my post here is displaced, feel free to remove or relocate it.
The problem: I can't connect to the internet. DSL connection says its up but in WAN it says connection failed.
dsl connection:
Line State: UP [0x0]
Line Mode: G.993.2 (VDSL2)
Line Uptime: 1m 46s
Annex: B
Profile: 17a
Data Rate: 15.471 Mb/s / 1.119 Mb/s
Max. Attainable Data Rate (ATTNDR): 15.530 Mb/s / 1.193 Mb/s
Latency: 0.90 ms / 11.0 ms
Line Attenuation (LATN): 3.4 dB / 1.3 dB
Signal Attenuation (SATN): 3.4 dB / 1.3 dB
Noise Margin (SNR): 6.1 dB / 7.9 dB
Aggregate Transmit Power(ACTATP): 13.7 dB / 5.9 dB
Forward Error Correction Seconds (FECS): 0 / 36703
Errored seconds (ES): 0 / 10
Severely Errored Seconds (SES): 0 / 0
Loss of Signal Seconds (LOSS): 0 / 0
Unavailable Seconds (UAS): 157 / 157
Header Error Code Errors (HEC): 0 / 0
Non Pre-emtive CRC errors (CRC_P): 0 / 0
Pre-emtive CRC errors (CRCP_P): 0 / 0
ATU-C System Vendor ID: Broadcom 177.191
Power Management Mode: L0 - Synchronized
dsl and wan configuration:
config dsl 'dsl'
option annex 'b'
option tone 'a'
config interface 'wan'
option ifname 'dsl0.101'
option proto 'pppoe'
option username 'vodafone-vdsl.komplett/xxxxxxxxxxxx'
option password 'xxxxxxxx'
I tried with default settings and with the settings from here: https://openwrt.org/docs/guide-user/network/wan/isp-configurations
Looking forward
Are you sure about VLAN tag 101? The information I can find would be VLAN tag 7, if vodafone relies on Telekom infrastructure underneath - and VLAN tag 132 if they own the cables themselves.
Another issue seems to be "Line Mode: G.993.2 (VDSL2)" combined with "Data Rate: 15.471 Mb/s / 1.119 Mb/s", this looks an awful lot like you'd be using a non-vectoring fallback profile on a connection that would require a vectoring capable modem. Keep in mind that OpenWrt is only allowed to ship non-vectoring enabled xDSL firmware blobs, if you do want a vectoring enabled one, you do have supply a firmware file with vectoring support yourself.
Additionally to the advice from @slh regarding the VLAN tag - Vodafone has also different prefixes depending on your contract. To add insult to injury, the username written to you might not be the one you need.
Back when i was using them, i had to use the "arcor.komplet/abxxxxx" prefix, but there are also "vodafone.komplett/xxxxxxxxx" around. So this might also need additional trial-and error from your side.
Hey thanks for the fast answers! I also seeked helped in the irc channel and I changed the line
option ifname'dsl0.101'
to
option ifname'dsl0.7'
and tadaa it works.
Also I followed the instrucitons here (https://openwrt.org/toh/avm/fritz.box.wlan.7360) to get 993.5 vectoring working and it works like a charm.
Thank you a lot =)
ps.: please consider to add the extracting of the firmware etc. like explained in the link above to the wiki.
AVM does not freely distribute that firmware AFAIK. Having it in the wiki is already a bit of a grey area probably; providing a script that comes with OpenWrt to just extract it might be even more so.
Hy,
You used the firmware of the FB 7360?
I tried to extract the 7362SL blob of the 7.10 but it failed.
Also with the firmware file from the 7360 my modem doesn't work
1 Like
Do the Lan Ports 3+4, which only support 100 Mbit/s, work for you? I have a Fritz!Box 7262 SL 1&1 branded.
If I try to apply vlan config on them, there's a good chance the device freezes. It recognizes the connections as gigabit although my Zyxel switch says it's only 100. And the ports are dead on layer 2 and higher levels. Packages don't go through.
Jep, there definitly is a regression with the xrx200 switch.
OpenWrt 19.07.7 Kernel 4.14.221 supports ports 3 + 4
Openwrt 21.02.0-rc1 Kernel 5.4.111 ports 3 + 4 are dead
root@OpenWrt:~# dmesg|grep -A5 -B5 PHY
[ 0.163028] pinctrl core: initialized pinctrl subsystem
[ 0.170653] NET: Registered protocol family 16
[ 0.183980] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV
[ 0.198588] pinctrl-xway 1e100b10.pinmux: Init done
[ 0.205140] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7, channels: 28
[ 0.216895] pcie-xrx200 1d900000.pcie: failed to get the PCIe PHY
[ 0.265910] usbcore: registered new interface driver usbfs
[ 0.271499] usbcore: registered new interface driver hub
[ 0.276869] usbcore: registered new device driver usb
[ 0.282522] workqueue: max_active 576 requested for napi_workq is out of range, clamping between 1 and 512
[ 0.294467] clocksource: Switched to clocksource MIPS
--
[ 0.708199] NET: Registered protocol family 10
[ 0.715876] Segment Routing with IPv6
[ 0.718218] NET: Registered protocol family 17
[ 0.722769] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 0.735555] 8021q: 802.1Q VLAN Support v1.8
[ 0.746142] pcie-xrx200 1d900000.pcie: failed to get the PCIe PHY
[ 0.859313] libphy: lantiq,xrx200-mdio: probed
[ 0.869051] net-xrx200: invalid MAC, using random
[ 0.872575] Atheros 8030 ethernet 0:00: attached PHY driver [Atheros 8030 ethernet] (mii_bus:phy_addr=0:00, irq=POLL)
[ 0.883256] Atheros 8030 ethernet 0:01: attached PHY driver [Atheros 8030 ethernet] (mii_bus:phy_addr=0:01, irq=POLL)
[ 0.894242] Intel XWAY PHY11G (xRX v1.2 integrated) 0:11: attached PHY driver [Intel XWAY PHY11G (xRX v1.2 integrated)] (mii_bus:phy_addr=0:11, irq=POLL)
[ 0.907971] Intel XWAY PHY11G (xRX v1.2 integrated) 0:13: attached PHY driver [Intel XWAY PHY11G (xRX v1.2 integrated)] (mii_bus:phy_addr=0:13, irq=POLL)
[ 1.046546] PCI host bridge /fpi@10000000/pcie@d900000 ranges:
[ 1.051221] PCI host bridge to bus 0000:00
[ 1.055083] pci_bus 0000:00: root bus resource [mem 0x1c000000-0x1cffffff]
[ 1.061969] pci_bus 0000:00: root bus resource [io 0x1d800000-0x1d8fffff]
[ 1.068840] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
Notably might be the line ”failed to get the PCIe PHY“ which does not appear in 19.07.7.
Same at the 3390, 3+4 not working
| Model | AVM FRITZ!Box 3390 |
|---|---|
| Architecture | xRX200 rev 1.2 |
| Firmware Version | OpenWrt SNAPSHOT r16833-962d530dea / LuCI Master git-21.147.31971-74be304 |
| Kernel Version | 5.4.121 |
root@OpenWrt3390:~# dmesg|grep failed
[ 0.286747] pcie-xrx200 1d900000.pcie: failed to get the PCIe PHY
[ 0.814252] pcie-xrx200 1d900000.pcie: failed to get the PCIe PHY
Worth noting, I think it might be because of this commit:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=f8ea7c53fd227a9c21f0ca45a2c3345312ea54b5
Is this still true for the final 21.02.0 release? I plan to openwrtize one of this devices but need all of the ethernet ports 
Use 19.07, for me the don't work
Perhaps give a current OpenWrt/ master snapshot a try, lantiq has moved to DSA there, which re-shuffles the cards (won't help 21.02.x by itself, but it would be interesting to evaluate the current status for the next release after it).