* russell--
encountered a boot failure of the 23.05.2 release initramfs binary on a mediatek mt7688 (also seen similar on locally built images, which is why i was trying the release version):
<russell-->
0.000000] Kernel panic - not syncing: unable to get CPU clock, err=-517
<russell-->
[ 0.000000] Rebooting in 1 seconds..
<russell-->
[ 0.000000] Reboot failed -- System halted
<KanjiMonster>
russell--: have you ever created an issue about this on github?
goliath has joined #openwrt-devel
lmahmutov has quit [Ping timeout: 480 seconds]
rua has quit [Quit: Leaving.]
rua has joined #openwrt-devel
Tapper has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
minimal has joined #openwrt-devel
shibboleth has joined #openwrt-devel
gladiac is now known as Guest11792
gladiac has joined #openwrt-devel
Guest11792 has quit [Ping timeout: 480 seconds]
<mirko>
what is the proper way for wanting to trigger a factory-reset when being on squashfs and using ext4 as overly? firstboot triggers jffs2reset which tells me no MTD part named "rootfs_data" found, which isn't surprising, as my underlying NVS is an eMMC with a MBR partition table
<mirko>
it feels like i have to override volume_find() however not quire sure and hoping for an already existing method
<mirko>
my squashfs + ext4-overly are on the same MBR partition btw, so i have to deal with the end-of-suqashfs / 0xdeadc0de marker
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #openwrt-devel
goliath has joined #openwrt-devel
<russell-->
KanjiMonster: nein, not yet.
nixuser has quit [Ping timeout: 480 seconds]
nixuser has joined #openwrt-devel
shibboleth has quit [Quit: shibboleth]
<Habbie>
Please press Enter to activate this console.
<Habbie>
yessssssssssss
Tapper has quit [Ping timeout: 480 seconds]
<colo>
Habbie, merry christmas! :D
<Habbie>
thank you!
<dwfreed>
Habbie: on the juniper?
<Habbie>
yes
<dwfreed>
nice!
<Habbie>
four hours of poking, one small step made it all work: usbcore.nousb
<dwfreed>
heh
<Habbie>
relevant note, similar to the previous night
<Habbie>
`81635880`, also spotted in a log above, is inside `octeon_usb_probe`.
<Habbie>
now ethernet is unhappy (and i guess i don't have USB :D) but at least i have a shell to poke at things
<dwfreed>
yeah, a lot easier to poke things once you've got a shell
<Habbie>
as unhappy, and loud in dmesg, as ethernet is, tcpdump shows me reasonable looking multicast content from another box on the network
<Habbie>
so this should be 'small things'
aiyion has quit [Remote host closed the connection]
aiyion has joined #openwrt-devel
Mangix has quit [Read error: Connection reset by peer]
mrkiko has joined #openwrt-devel
<mrkiko>
Hi all!!
<Habbie>
hi!
<mrkiko>
How can I discover if a mediatek device using mt76 wi-fi driver has DBDC hardware or not? Wondering about GL-MT6000. Is there any shell command or place in the system where I can look?
<mrkiko>
Habbie: hi!!
<mrkiko>
marry christmas! Even tough little bit late
<slh>
there must be a better way, but there are basically two hints - number of antennas (four per radio, with DBDC you'd only have 4 instead of 8), and "mt7915e 0000:02:00.0: registering led 'mt76-phy0'" && mt7915e 0000:02:00.0: registering led 'mt76-phy1'", so two phy LEDs on the same radio