Just want to comment that finally I bought a cable Usb Ttl Ftdi Ft232rl locally and once have it installing the new images was a piece of cake.
As I said previously. How thoughtful of them to not mention that a serial cable was a must-have accessory and bought everithing in the same package.
Now I have the latest snapshot running from eMMC and some new problems arises (ETH ports stoped working, filesystem do not use all the eMMC space, ssh connection randomly gets disconnected, etc) But I will investigate and ask in another specific threads if needed.
Thanks by your support
You seem to have completely forgotten one thing: It is and remains a developer and tinkering board. This means that various things can be assumed to be known and available. I hate people who don’t take the trouble to inform themselves in advance and think that they are getting a completely finished and ready-to-use product. People like that should just stick with the Fritzbox. It’s for end users, ready for immediate use and requires little or no knowledge.
Is it possible that my WIFI card was burned with the latest sysupgrade?
I applied the latest sysupgrade and after the reboot it worked correctly for a few minutes and then hung.
I connected via console and found that the boot (from eMMC) was interrupted.
Assuming that there had been a problem with the upgrade I inserted the SD card with which I had installed the system and found that it hung at the same point.
I tried other images and found that they all interrupt the boot at the same point with the only exception of ubuntu but I could not find in the instructions the password with which the root user is configured.
This is the point at which the boot is interrupted. Can you think of something?
[ 13.331854] sfp sfp2: Host maximum power 3.0W
[ 13.350917] mt7996e_hif 0001:01:00.0: assign IRQ: got 118
[ 13.356350] mt7996e_hif 0001:01:00.0: enabling device (0000 → 0002)
[ 13.362727] mt7996e_hif 0001:01:00.0: enabling bus mastering
[ 13.368534] mt7996e 0000:01:00.0: assign IRQ: got 115
[ 13.373595] mt7996e 0000:01:00.0: enabling device (0000 → 0002)
[ 13.379609] mt7996e 0000:01:00.0: enabling bus mastering
[ 13.462436] mtk-pcie-gen3 11300000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11300c00 data 1
[ 13.470950] mtk-pcie-gen3 11310000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11310c00 data 1
[ 13.525317] mt7996e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20240809122254a
[ 13.525317]
[ 13.736609] mt7996e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20240809122249
[ 13.785651] mt7996e 0000:01:00.0: DSP Firmware Version: ____000000, Build Time: 20240809121650
[ 13.839000] mt7996e 0000:01:00.0: WA Firmware Version: ____000000, Build Time: 20240809122214
[ 14.241162] PPP generic driver version 2.4.2
[ 14.246017] NET: Registered PF_PPPOX protocol family
[ 14.252492] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 19.181729] mtk_soc_eth 15100000.ethernet eth0: Link is Down
[ 19.205059] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/internal link mode
[ 19.213309] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 10Gbps/Full - flow control rx/tx
[ 19.215290] mt7530-mmio 15020000.switch lan1: configuring for phy/internal link mode
[ 19.230383] br-lan: port 1(lan1) entered blocking state
[ 19.235653] br-lan: port 1(lan1) entered disabled state
[ 19.240897] mt7530-mmio 15020000.switch lan1: entered allmulticast mode
[ 19.247534] mtk_soc_eth 15100000.ethernet eth0: entered allmulticast mode
[ 19.254513] mt7530-mmio 15020000.switch lan1: entered promiscuous mode
[ 19.265666] mt7530-mmio 15020000.switch lan2: configuring for phy/internal link mode
[ 19.274458] br-lan: port 2(lan2) entered blocking state
[ 19.279699] br-lan: port 2(lan2) entered disabled state
[ 19.284981] mt7530-mmio 15020000.switch lan2: entered allmulticast mode
[ 19.291790] mt7530-mmio 15020000.switch lan2: entered promiscuous mode
[ 19.301244] mt7530-mmio 15020000.switch lan3: configuring for phy/internal link mode
[ 19.310027] br-lan: port 3(lan3) entered blocking state
[ 19.315309] br-lan: port 3(lan3) entered disabled state
[ 19.320563] mt7530-mmio 15020000.switch lan3: entered allmulticast mode
[ 19.327433] mt7530-mmio 15020000.switch lan3: entered promiscuous mode
[ 19.336104] mtk_soc_eth 15100000.ethernet eth1: configuring for inband/10gbase-r link mode
[ 19.368442] br-lan: port 4(eth1) entered blocking state
[ 19.373733] br-lan: port 4(eth1) entered disabled state
[ 19.378993] mtk_soc_eth 15100000.ethernet eth1: entered allmulticast mode
[ 19.386184] mtk_soc_eth 15100000.ethernet eth1: entered promiscuous mode
[ 19.395684] mt7530-mmio 15020000.switch wan: configuring for phy/internal link mode
[ 19.404187] br-wan: port 1(wan) entered blocking state
[ 19.409328] br-wan: port 1(wan) entered disabled state
[ 19.414507] mt7530-mmio 15020000.switch wan: entered allmulticast mode
[ 19.421219] mt7530-mmio 15020000.switch wan: entered promiscuous mode
[ 19.429861] mtk_soc_eth 15100000.ethernet eth2: configuring for inband/10gbase-r link mode
[ 19.462145] br-wan: port 2(eth2) entered blocking state
[ 19.467452] br-wan: port 2(eth2) entered disabled state
[ 19.472715] mtk_soc_eth 15100000.ethernet eth2: entered allmulticast mode
[ 19.479647] mtk_soc_eth 15100000.ethernet eth2: entered promiscuous mode
You can format log output using the “preformatted text” feature of editor here. That makes it much easier to read.
Also, did you press enter after connecting the console? This looks like the normal boot output on console. A login prompt only appears after you press enter.
This is the point where I feel extremely stupid
Yes that was the problem about the boot stuck
Even that wifi still not starting and when I plug the eth cable from a laptop to get access to it ETH connection never starts
Yes that was the problem about the boot stuck
Even that wifi still not starting and when I plug the eth cable from a laptop to get access to it ETH connection never starts