Topics created by luz

@luz 'MTD and eraseblocks'
I wanted to say: maybe you should calculate the lifetime with eraseblocks (xx KBytes) instead of flash pages (256 Bytes) and you should take into account only a part of the chip.

So at least at the mtd layer, it is operating with 64kB (0x10000) erase blocks.

Thanks! :-)
I've forgotten - I had already read this in the OpenWrt documentation. It seems I'm getting older... :( Maybe I should write everything down.

that is a beautiful piece of furniture. but, i'm kind surprised that google has not informed you to rename it. they can be jerks.

Hello @luz any further experience with mt76 driver? Disconnects, low-speed?

I really want to switch to a clean OpenWrt build to make use of kmods, but WiFi driver performance has not made it possible in the past.

Crickets and tumbleweed

@Nikolay-Vetrov Yes, upgrade to the very latest available firmware: oupgrade -l -f and the ledchain kernel module will work right away.

That's actually what controls the notification LED on the Omega2 Pro

@luz I'm still seeing it here with a pretty new Omega2+ and the latest firmware, although I'm not sure if the oupgrade process upgrades the boot loader or not.

Thanks mate! You just saved me a lot of debugging time

@fossette said in Any omega hackers at 33C3?:

PS: 6809 is a nice number. My preference is 6502...
I guess it depends on personal experience back in the old days :-) I never had a 6502 based machine, but built a few 6809 ones

@Iker this time the malaware just was a popup ... now i got it.

Reviving an old thread to post what I found:

On my Omega 2+, the uboot environment seems to start at 0x2000 in /dev/mtd1, and runs to 0x5fff, thus my /etc/fw_env.config files looks like:

# Configuration file for fw_(printenv/saveenv) utility. # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x2000 0x4000 0x1000

@Alexander-Pitzer A docker image would be most convenient! But that's something the community could do, once the .config is known (plus maybe some stuff for /files).

Figuring out the right .config by reverse engineering however would be really tedious and completely redundant work, because that .config already does exist - only it's not available! So I still hope Onion will decide to publish it! Any chances for that, @Lazar-Demin?