GL.iNET Flint 2 (GL-MT6000) discussions

I downloaded a snapshot last night and it still doesn’t have LuCi installed? Am I missing something?

I think so, it's listed on the base packages. I'll pull a clean snapshot later and check to be sure.

1 Like

Hi can someone help me please i'll be so grateful. so I just upgraded to latest firmware and am having alot of difficulties with snapshot.

I somehow dont have ANY wifi drivers, they fail to load and have tried everything from resetting, flashing completely new firmware, i am currently using pesa's firmware build hoping that would help but nothing. I see two issues in the logs and ill show:

t798x-wmac 18000000.wifi: HW/SW Version: 0x8a108a10, Build Time: 20240507160301a
[   14.116865] 
[   14.221487] mt798x-wmac 18000000.wifi: WM Firmware Version: ____000000, Build Time: 20240507160318
[   14.306095] mt798x-wmac 18000000.wifi: WA Firmware Version: DEV_000000, Build Time: 20240507160509
[   14.412192] mt798x-wmac 18000000.wifi: eeprom load fail, use default bin
[   14.418952] mt798x-wmac 18000000.wifi: Direct firmware load for mediatek/mt7986_eeprom_mt7976_dual.bin failed with error -2
[   14.430063] mt798x-wmac 18000000.wifi: Falling back to sysfs fallback for: mediatek/mt7986_eeprom_mt7976_dual.bin
[   14.466687] mt798x-wmac: probe of 18000000.wifi failed with error -12
loop0: detected capacity change from 0 to 15178752
[    5.470356] loop0: detected capacity change from 15178752 to 15149696
[    5.477300] mount_root: overlay filesystem in /dev/loop0 has not been formatted yet
[    8.171848] F2FS-fs (loop0): Found nat_bits in checkpoint
[    8.216060] F2FS-fs (loop0): Mounted with checkpoint version = 8f5dc87
[    8.222970] mount_root: overlay filesystem has not been fully initialized yet
[    8.230355] mount_root: switching to f2fs overlay
[    8.237475] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
[    8.248432] urandom-seed: Seed file not found (/etc/urandom.seed)

I have been using snapshots for months with no issues at all, but literally unable to load any drivers, i've spent two days trying different drivers, firmwares, ive deleted wifi and ran cmds wifi config, copied working config... nothing.

I am definitely not nearly as competent as you all, and have never compiled firmware from source myself. This issue is kind of game breaking though because i have NO wifi whatsoever... however ethernet works.

i have no ieee80211 in /sys/devices either. im truly stumped :frowning:

if someone can be so kind as to guide me to what to do i'll be forever grateful

thanks!

ain't found. does it exist

wow thanks for quick reply !

I believe so, i downloaded pesa's latest release and didnt change anything. still on just generic default install.

installed is:
kmod-mac80211 kmod-mt76-connac kmod-mt76-core kmod-mt7915e kmod-mt7986-firmware kmod-rtlwifi among others. if theres more info you need let me know. im way out of my league at this point

here is /lib/firmware/mediatek

ls /lib/firmware/mediatek
mt7986_rom_patch.bin         mt7986_wm.bin                mt7986_wo_1.bin
mt7986_rom_patch_mt7975.bin  mt7986_wm_mt7975.bin
mt7986_wa.bin                mt7986_wo_0.bin

I have no wireless tab in luci either.

i've read through quite possibly every thread on github, openwrt forums and gl... never applied a patch before and dont want to go hard bricking thats why i posted i need expert advice. my first mt-6000 was defect and so they sent me a new one. my luck isnt good :frowning:

so after reading some more i copied the bins from https://anduin.linuxfromscratch.org/sources/linux-firmware/mediatek/ into /lib/firmware/mediatek and i think i got it to work but still weird!

   14.135662] mt798x-wmac 18000000.wifi: HW/SW Version: 0x8a108a10, Build Time: 20221012174648a
[   14.135662] 
[   14.170784] mt798x-wmac 18000000.wifi: WM Firmware Version: ____000000, Build Time: 20221012174725
[   14.213140] mt798x-wmac 18000000.wifi: WA Firmware Version: DEV_000000, Build Time: 20221012174937
[   14.319184] mt798x-wmac 18000000.wifi: eeprom load fail, use default bin
[   14.328153] mt798x-wmac 18000000.wifi: registering led 'mt76-phy0'
[   14.335876] mt798x-wmac 18000000.wifi: registering led 'mt76-phy1'

idk whats going on why its not downloading that from source when installing? i still dont know what is wrong with /dev/loop0 because when i gdisk it tells me that rootfs /dev/mmcblk0p7 is overlapping, and theres no free space at the end of device

/dev/mmcblk0p7 is also .2gb larger than /dev/loop0. ive only found few posts about it and no one seems to know lol

edit:
so 5G works but i cannot get 2.4 to associate with radio0. it also added 2 more "generic unknown" radios. this is baffling >.<

Wed Jul 10 19:18:20 2024 daemon.err hostapd: Could not set interface phy0-ap0 flags (UP): Address not available
Wed Jul 10 19:18:20 2024 daemon.err hostapd: nl80211: Could not set interface 'phy0-ap0' UP
Wed Jul 10 19:18:20 2024 daemon.notice hostapd: nl80211: deinit ifname=phy0-ap0 disabled_11b_rates=0
Wed Jul 10 19:18:20 2024 daemon.err hostapd: nl80211 driver initialization failed.
Wed Jul 10 19:18:20 2024 daemon.notice hostapd: phy0-ap0: CTRL-EVENT-TERMINATING
Wed Jul 10 19:18:20 2024 daemon.err hostapd: hostapd_free_hapd_data: Interface phy0-ap0 wasn't started
Wed Jul 10 19:18:20 2024 daemon.notice hostapd: hostapd.add_iface failed for phy phy0 ifname=phy0-ap0
Wed Jul 10 19:18:20 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Wed Jul 10 19:18:20 2024 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=US ieee80211d=1 ieee80211h=1 hw_mode=a supported_rates=120 180 240 360 480 540 basic_rates=120 240 beacon_int=100 tx_queue_data2_burst=2.0 lpi_enable=0 sku_idx=0 beacon_dup=1 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935] ieee80211ac=1 vht_oper_chwidth=2 vht_oper_centr_freq_seg0_idx=acs_survey vht_capab=[RXLDPC][SHORT-GI-80][SHORT-GI-160][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-4][BF-ANTENNA-4][VHT160][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] ieee80211ax=1 he_oper_chwidth=2 he_oper_centr_freq_seg0_idx=acs_survey he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_twt_responder=0 he_bss_color=128 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023
Wed Jul 10 19:18:20 2024 daemon.notice netifd: Wireless device 'radio1' is now up

yeahhhhhhh wifi still doesnt work the macaddress is just 00:00:00:00:00 and if i change it from back of the router does nothing

Hmm, its hard to know what exactly happened in this case.

Though i have seen some cases also i have seen it on my own router, that on a very early boot sometimes the logs also state something going on with re-partitioning/restoring, however the router stayed fully functional for me.

my guess but maybe im wrong, is that something on a very early build mismatched the partition sizes, i no longer get these messages anymore so i assume its fixed for me, its also possible it fixed itself when i was using u-boot to test oem firmware again and went back to OpenWrt snapshots, but it makes me wonder in your case:

  • is u-boot still functional?, what if you flash back the oem version and then flash back the OpenWrt version again, would that fix the partition issues you have?

yeah i actually just ubooted and switched to gl stable, but the router was even more f'd and ethernet didnt work either. so i switched back to snapshot, and after too many hours of troubleshooting i was able to get 5ghz working.

I had to generate new macs and tweak many files for wifi to work the odd thing is eth0 shows mac addr: 00:00:00:00:02 and im unable to change it without locking myself out. the router works for now so ill just leave it semi functioning until i hear back from support

i also still get alot of errors with overlayfs:

block: attempting to load /tmp/overlay/upper/etc/config/fstab
Wed Jul 10 23:39:50 2024 user.err kernel: [    5.833342] block: unable to load configuration (fstab: Entry not found)
Wed Jul 10 23:39:50 2024 user.info kernel: [    5.840065] block: attempting to load /tmp/overlay/etc/config/fstab
Wed Jul 10 23:39:50 2024 user.err kernel: [    5.846346] block: unable to load configuration (fstab: Entry not found)
Wed Jul 10 23:39:50 2024 user.info kernel: [    5.853056] block: attempting to load /etc/config/fstab
Wed Jul 10 23:39:50 2024 user.err kernel: [    5.858990] block: unable to load configuration (fstab: Entry not found)
Wed Jul 10 23:39:50 2024 user.err kernel: [    5.865702] block: no usable configuration
Wed Jul 10 23:39:50 2024 user.info kernel: [    5.870618] block: attempting to load /etc/config/fstab
Wed Jul 10 23:39:50 2024 user.err kernel: [    5.875865] block: unable to load configuration (fstab: Entry not found)
Wed Jul 10 23:39:50 2024 user.err kernel: [    5.882577] block: no usable configuration
Wed Jul 10 23:39:50 2024 kern.info kernel: [    5.887156] loop0: detected capacity change from 0 to 15178752
Wed Jul 10 23:39:50 2024 kern.info kernel: [    5.969499] loop0: detected capacity change from 15178752 to 14992000
Wed Jul 10 23:39:50 2024 kern.notice kernel: [    6.053950] F2FS-fs (loop0): Mounted with checkpoint version = 351ed6f7
Wed Jul 10 23:39:50 2024 user.info kernel: [    6.060933] mount_root: loading kmods from internal overlay
Wed Jul 10 23:39:50 2024 user.err kernel: [    6.068615] kmodloader: failed to open /tmp/overlay/upper/lib/modules/6.6.36/e1000e.ko
Wed Jul 10 23:39:50 2024 user.err kernel: [    6.095829] mount_root: failed to launch kmodloader from internal overlay
Wed Jul 10 23:39:50 2024 user.info kernel: [    6.143238] block: attempting to load /tmp/overlay/upper/etc/config/fstab
Wed Jul 10 23:39:50 2024 user.info kernel: [    6.150609] block: extroot: not configured
Wed Jul 10 23:39:50 2024 user.info kernel: [    6.154847] block: attempting to load /etc/config/fstab
Wed Jul 10 23:39:50 2024 user.err kernel: [    6.160109] block: unable to load configuration (fstab: Entry not found)
Wed Jul 10 23:39:50 2024 user.err kernel: [    6.166815] block: no usable configuration
Wed Jul 10 23:39:50 2024 user.info kernel: [    6.171545] mount_root: switching to f2fs overlay
Wed Jul 10 23:39:50 2024 kern.warn kernel: [    6.178300] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
Wed Jul 10 23:39:50 2024 user.debug kernel: [    6.189400] urandom-seed: Seeding with /etc/urandom.seed
Wed Jul 10 23:39:50 2024 kern.notice kernel: [    6.219587] random: procd: uninitialized urandom read (4 bytes read)

and for wifi:

Wed Jul 10 23:39:54 2024 daemon.notice netifd: radio1 (2957): WARNING: Variable 'data' does not exist or is not an array/object
Wed Jul 10 23:39:54 2024 daemon.notice netifd: radio0 (2956): WARNING: Variable 'data' does not exist or is not an array/object

i can live without the full functional, though 2.4gz is nice for when outside. i contacted glinet and hoping they will exchange it i've had too many headaches from this device, though it is really nice when functioning.

Hmm :thinking:

I do see fstab here, could it be you use some type of storage device?

Though i don't think it would mess with your partitioning because its likely not ext4.

But about ext4 i learned something ugly, when you attach storage to ext4 through /overlay, and then install new firmware, it tries to install it on the attached storage, but then tries to load aswell with old transient packages from the original disk, with other words it takes it literally and overlays, which cause all sorts of issues, i learned the hard way with my Mochabin to always wipe and unmount the attached storage before doing any upgrades to avoid this specific problem.

I wonder could it be something like this happening on your flint 2 ?

hmm well i use no extroot or storage at all, and makes sense because the one time i tried on other router it failed and borked. i definitely have an /etc/config/fstab and its configured with block detect correct UUID's so idk i think the main issue is the overlapping and no space at end.

my /etc/fstab is blank though

# <file system> <mount point> <type> <options> <dump> <pass>

but i thought that was normal

/etc/config/fstab

config global
        option anon_swap '0'
        option anon_mount '0'
        option auto_swap '1'
        option auto_mount '1'
        option delay_root '5'
        option check_fs '1'

config mount
        option target '/overlay'
        option uuid '1846ddac-1dd2-11b2-92ec-000000000002'
        option enabled '0'

config mount
        option target '/rom'
        option uuid '7aa7b6aa-dbd30aa9-932911d1-b4e47b2e'
        option enabled '0'

config swap
        option enabled '0'
        option device '/dev/zram0'

the partition is really confusing for me on this device its not ext4 its like f2fs with squashfs and i dont know where to start trying to resize or fix it.

gdisk /dev/mmcblk0

GPT fdisk (gdisk) version 1.0.10

Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.

Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.

Warning! One or more CRCs don't match. You should repair the disk!
Main header: OK
Backup header: ERROR
Main partition table: OK
Backup partition table: ERROR

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: damaged

****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************

Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.

lsblk

NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
loop0          7:0    0  7.1G  0 loop /overlay
mmcblk0      179:0    0  7.3G  0 disk
├─mmcblk0p1  179:1    0  512K  0 part
├─mmcblk0p2  179:2    0    2M  0 part
├─mmcblk0p3  179:3    0    2M  0 part
├─mmcblk0p4  179:4    0    2M  0 part
├─mmcblk0p5  179:5    0    2M  0 part
├─mmcblk0p6  179:6    0   32M  0 part
└─mmcblk0p7  179:7    0  7.2G  0 part /rom
mmcblk0boot0 179:8    0    4M  1 disk
mmcblk0boot1 179:16   0    4M  1 disk
zram0        253:0    0  200M  0 disk [SWAP]

/etc/mtab

/dev/root /rom squashfs ro,relatime,errors=continue 0 0
proc /proc proc rw,nosuid,nodev,noexec,noatime 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,noatime 0 0
cgroup2 /sys/fs/cgroup cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0
tmpfs /tmp tmpfs rw,nosuid,nodev,noatime 0 0
/dev/loop0 /overlay f2fs rw,lazytime,noatime,background_gc=on,nogc_merge,discard,discard_unit=block,user_xattr,inline_xattr,inline_data,inline_dentry,flush_merge,barrier,extent_cache,mode=adaptive,active_logs=6,alloc_mode=reuse,checkpoint_merge,fsync_mode=posix,memory=normal,errors=continue 0 0
overlayfs:/overlay / overlay rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work,xino=off 0 0
tmpfs /dev tmpfs rw,nosuid,noexec,noatime,size=512k,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,noatime,mode=600,ptmxmode=000 0 0
debugfs /sys/kernel/debug debugfs rw,noatime 0 0
bpffs /sys/fs/bpf bpf rw,nosuid,nodev,noexec,noatime,mode=700 0 0
pstore /sys/fs/pstore pstore rw,noatime 0 0

fw_printenv

Warning: Bad CRC, using default environment
bootcmd=run distro_bootcmd
bootdelay=2
baudrate=115200
loadaddr=0x0
mtdids=
mtdparts=
bootm_size=0x10000000
eth6addr=02:00:strip
ethaddr=02:00:strip
fdt_addr_r=0xc00000
ipaddr=192.0.2.1
kernel_addr_r=0x1000000
pxefile_addr_r=0x2000
ramdisk_addr_r=0x2000000
scriptaddr=0x1000
stderr=serial,vidconsole
stdin=serial
stdout=serial,vidconsole

fdisk -l

Disk /dev/loop0: 7.15 GiB, 7675904000 bytes, 14992000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
The backup GPT table is corrupt, but the primary appears OK, so that will be used.


Disk /dev/mmcblk0: 7.28 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2BD17853-102B-4500-AA1A-8A21D4D7984D

Device         Start      End  Sectors  Size Type
/dev/mmcblk0p1  8192     9215     1024  512K Linux filesystem
/dev/mmcblk0p2  9216    13311     4096    2M Linux filesystem
/dev/mmcblk0p3 13312    17407     4096    2M Linux filesystem
/dev/mmcblk0p4 17408    21503     4096    2M Linux filesystem
/dev/mmcblk0p5 21504    25599     4096    2M Linux filesystem
/dev/mmcblk0p6 25600    91135    65536   32M Linux filesystem
/dev/mmcblk0p7 91136 15269887 15178752  7.2G Linux filesystem


Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/zram0: 200 MiB, 209715200 bytes, 51200 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

/dev/loop0 is 7.2G but /dev/mmcblk0p7 is 7.4G something is def f'd and ive only found two threads with similar issue on mt6000 and everyone is too scared to try anything lmao:

man there's just so many issues and i'm not a good enough nerd to know where to start. so many things off. not sure if you can spot anything from this info but yeah i feel this device is hanging by a thread LOL

thanks either way for help

1 Like

Well the loop device is virtual, so actually a mirror of something in /dev/mmcblk0p7 the fstab looks fine i have compared my own configuration, only the zram looks strange.

Heres my fdisk config:

config 'global'
        option  anon_swap       '0'
        option  anon_mount      '0'
        option  auto_swap       '1'
        option  auto_mount      '1'
        option  delay_root      '5'
        option  check_fs        '0'
config 'mount'
        option  target  '/overlay'
        option  uuid    '1808b3d8-1dd2-11b2-90cd-9483c4a037fc'
        option  enabled '0'
config 'mount'
        option  target  '/rom'
        option  uuid    '2e97cb39-8e7c4220-2a33af26-9ace43aa'
        option  enabled '0'

Fdisk:

root@MT6000:/dev# fdisk -l
Disk /dev/loop0: 7.22 GiB, 7757299712 bytes, 15150976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
The backup GPT table is not on the end of the device.
Disk /dev/mmcblk0: 7.28 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2BD17853-102B-4500-AA1A-8A21D4D7984D
Device         Start      End  Sectors  Size Type
/dev/mmcblk0p1  8192     9215     1024  512K Linux filesystem
/dev/mmcblk0p2  9216    13311     4096    2M Linux filesystem
/dev/mmcblk0p3 13312    17407     4096    2M Linux filesystem
/dev/mmcblk0p4 17408    21503     4096    2M Linux filesystem
/dev/mmcblk0p5 21504    25599     4096    2M Linux filesystem
/dev/mmcblk0p6 25600    91135    65536   32M Linux filesystem
/dev/mmcblk0p7 91136 15269887 15178752  7.2G Linux filesystem
Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

This fdisk result show similarities but i think the loop device error is not a real issue, it might be a issue how native support is with the loop kmod and how fdisk reads it that might be the problem, but the issue might be somewhere else, can you show a output of lsmod and also hwinfo (you may need to install it), i want to get a clue if the drivers are loaded :+1:

Also the fw env is different no error:

//There was also a bunch of code here but i did not copy it over here.
bootm_size=0x10000000
eth6addr=02:00:<strip>
ethaddr=02:00:<strip>
fdt_addr_r=0xc00000
ipaddr=192.0.2.1
kernel_addr_r=0x1000000
pxefile_addr_r=0x2000
ramdisk_addr_r=0x2000000
scriptaddr=0x1000
stderr=serial,vidconsole
stdin=serial
stdout=serial,vidconsole
1 Like

thanks man yea this is a nightmare atm. still cant load eeprom which results in wed issue i think and im too dumb to diagnose. surprised im even up and running lol

1 Like

im not sure if the eeprom is required, from my foundings it seemed the files in /lib/firmware/mediatek has to match the exact namings, but on the mtk git, there are indeed a couple of more bin files for mt7986, but if you put those extra ones you might get also errors like these.

What does ls /rom/lib/firmware/mediatek/ reflect vs what you have in ls /lib/firmware/mediatek ?

Agree about eeprom. Here are the files needed to my knowledge.
Screenshot 2024-07-11 at 6.00.03 AM

1 Like

You have the full and proper list :1st_place_medal:

That said, the wo firmware files are only needed if using WED. Those will be loaded in addition to WM and WA during boot when WED is enabled.

hi guys! sorry for late reply.. so when i initially flash it looks similar to that amount but following advice of few other forums i cloned the mediatek firmware dir from source and copied them all in....

root@openwrt ~ $  ls /lib/firmware/mediatek
mt7925/                         mt7663pr2h_rebb.bin                WIFI_RAM_CODE_MT7922_1.bin
mt7988/                         mt7668pr2h.bin                     WIFI_RAM_CODE_MT7961_1.bin
mt7996/                         mt7915_eeprom.bin
mt8173/                         mt7915_eeprom_dbdc.bin
mt8183/                         mt7915_rom_patch.bin
mt8186/                         mt7915_wa.bin
mt8192/                         mt7915_wm.bin
mt8195/                         mt7916_eeprom.bin
sof/                            mt7916_rom_patch.bin
sof-tplg/                       mt7916_wa.bin
BT_RAM_CODE_MT7922_1_1_hdr.bin  mt7916_wm.bin
BT_RAM_CODE_MT7961_1_2_hdr.bin  mt7981_eeprom_mt7976_dbdc.bin
mt7601u.bin                     mt7981_rom_patch.bin
mt7610e.bin                     mt7981_wa.bin
mt7610u.bin                     mt7981_wm.bin
mt7615_cr4.bin                  mt7981_wo.bin
mt7615_n9.bin                   mt7986_eeprom_mt7975.bin
mt7615_rom_patch.bin            mt7986_eeprom_mt7975_dual.bin
mt7622_n9.bin                   mt7986_eeprom_mt7976.bin
mt7622_rom_patch.bin            mt7986_eeprom_mt7976_dbdc.bin
mt7622pr2h.bin                  mt7986_eeprom_mt7976_dual.bin
mt7650.bin                      mt7986_rom_patch.bin
mt7650e.bin                     mt7986_rom_patch_mt7975.bin
mt7662.bin                      mt7986_wa.bin
mt7662_rom_patch.bin            mt7986_wm.bin
mt7662u.bin                     mt7986_wm_mt7975.bin
mt7662u_rom_patch.bin           mt7986_wo_0.bin
mt7663_n9_rebb.bin              mt7986_wo_1.bin
mt7663_n9_v3.bin                WIFI_MT7922_patch_mcu_1_1_hdr.bin
mt7663pr2h.bin                  WIFI_MT7961_patch_mcu_1_2_hdr.bin

this was the only way i could even get wifi to show tab on luci or connect at all. illl attach a couple more things i see each reboot that are odd.

193	Thu Jul 11 17:18:25 2024	kern	warn	kernel: [   17.573295] bridger[2008]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
192	Thu Jul 11 17:18:25 2024	daemon	warn	chronyd[1921]: Timezone right/UTC failed leap second check, ignoring
----------------
vvvv this is the main one im concerned with as it never showed before and likely why WED doesnt work or 2.4 maybe?
*******
kernel: [   12.665955] mt798x-wmac 18000000.wifi: eeprom load fail, use default bin

------------------------------

128	Thu Jul 11 17:18:25 2024	kern	warn	kernel: [    6.178979] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
127	Thu Jul 11 17:18:25 2024	user	info	kernel: [    6.172224] mount_root: switching to f2fs overlay
126	Thu Jul 11 17:18:25 2024	user	err	kernel: [    6.167249] block: no usable configuration
125	Thu Jul 11 17:18:25 2024	user	err	kernel: [    6.160545] block: unable to load configuration (fstab: Entry not found)
124	Thu Jul 11 17:18:25 2024	user	info	kernel: [    6.155286] block: attempting to load /etc/config/fstab
123	Thu Jul 11 17:18:25 2024	user	info	kernel: [    6.151049] block: extroot: not configured
122	Thu Jul 11 17:18:25 2024	user	info	kernel: [    6.143167] block: attempting to load /tmp/overlay/upper/etc/config/fstab
121	Thu Jul 11 17:18:25 2024	user	err	kernel: [    6.095989] mount_root: failed to launch kmodloader from internal overlay
120	Thu Jul 11 17:18:25 2024	user	err	kernel: [    6.068977] kmodloader: failed to open /tmp/overlay/upper/lib/modules/6.6.36/e1000e.ko
119	Thu Jul 11 17:18:25 2024	user	info	kernel: [    6.061064] mount_root: loading kmods from internal overlay
118	Thu Jul 11 17:18:25 2024	kern	notice	kernel: [    6.053684] F2FS-fs (loop0): Mounted with checkpoint version = 351ed797
117	Thu Jul 11 17:18:25 2024	kern	info	kernel: [    5.969513] loop0: detected capacity change from 15178752 to 14992000
116	Thu Jul 11 17:18:25 2024	kern	info	kernel: [    5.917843] loop0: detected capacity change from 0 to 15178752
115	Thu Jul 11 17:18:25 2024	user	err	kernel: [    5.913242] block: no usable configuration
114	Thu Jul 11 17:18:25 2024	user	err	kernel: [    5.906477] block: unable to load configuration (fstab: Entry not found)
113	Thu Jul 11 17:18:25 2024	user	info	kernel: [    5.901226] block: attempting to load /etc/config/fstab
112	Thu Jul 11 17:18:25 2024	user	err	kernel: [    5.895964] block: no usable configuration
111	Thu Jul 11 17:18:25 2024	user	err	kernel: [    5.889242] block: unable to load configuration (fstab: Entry not found)
110	Thu Jul 11 17:18:25 2024	user	info	kernel: [    5.883316] block: attempting to load /etc/config/fstab
109	Thu Jul 11 17:18:25 2024	user	err	kernel: [    5.876605] block: unable to load configuration (fstab: Entry not found)
108	Thu Jul 11 17:18:25 2024	user	info	kernel: [    5.870323] block: attempting to load /tmp/overlay/etc/config/fstab
107	Thu Jul 11 17:18:25 2024	user	err	kernel: [    5.863575] block: unable to load configuration (fstab: Entry not found)
106	Thu Jul 11 17:18:25 2024	user	info	kernel: [    5.856723] block: attempting to load /tmp/overlay/upper/etc/config/fstab
---------------------

kernel: [    3.020671] gpio_button_hotplug: loading out-of-tree module taints kernel.
----------------
kernel: [    1.171089] mtk_soc_eth 15100000.ethernet: generated random MAC address 65:74:68:25:64:00

---------------------

50	Thu Jul 11 17:18:24 2024	kern	info	kernel: [    1.126921] mmcblk0rpmb: mmc0:0001 8GTF4R 512 KiB, chardev (250:0)
49	Thu Jul 11 17:18:24 2024	kern	info	kernel: [    1.121791] mmcblk0boot1: mmc0:0001 8GTF4R 4.00 MiB
48	Thu Jul 11 17:18:24 2024	kern	info	kernel: [    1.116068] mmcblk0boot0: mmc0:0001 8GTF4R 4.00 MiB
47	Thu Jul 11 17:18:24 2024	kern	info	kernel: [    1.110646]  mmcblk0: p1 p2 p3 p4 p5 p6 p7
46	Thu Jul 11 17:18:24 2024	kern	warn	kernel: [    1.105319] Alternate GPT is invalid, using primary GPT.

--------------------------

unable to even access wifi tab or attach device to radio without doing this. im baffled lol.

when i follow gl flint2 on openwrt wiki and do

cat /sys/kernel/debug/ppe0/bind

i get nothing even though its enabled and i dont use sqm

root@openwrt ~ $ gdisk /dev/mmcblk0

GPT fdisk (gdisk) version 1.0.10

Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.

Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.

Warning! One or more CRCs don't match. You should repair the disk!
Main header: OK
Backup header: ERROR
Main partition table: OK
Backup partition table: ERROR

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: damaged

****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************

Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.

also another note is /overlay/fs.state symlink is null and empty and i believe this is caused by some overlay issue where it doesnt detach? again, way over my dumby knowledge.
once again THANK YOU for taking time to help :slight_smile:

Now I'm wondering if its failing to load the main drivers so it defaults to the mt798x because the log shows it's 18000000wifi(+1) eeprom which matches that is what device is shown in wireless config for the radios. I've tried just about everything I could find and spent wayyy too many hours troubleshooting. At least I learned a lot ha. Hopefully GL support will exchange for me as no one here or on pesas thread knows. Thx again

At this point, I would suggest opening a new thread specific to your issue. This is getting to be very specific to your issue and less about the overall theme of this thread.

7 Likes

I am running SNAPSHOT, r26912 for this device with a somewhat complex mesh setup with B.A.T.M.A.N adv and all, no issues here.

These did not increase my speeds and using the most current snapshot. Im still under 300 for the upload.