@Lazar-Demin Thanks!

Verified working with b145.

@Mikael-Djurfeldt said in Zile:

@Luciano-S. BTW, is it possible to use any other OpenWRT repo:s for Omega2? Are there mips_24KEc packages out there which fit?

Found zile here:

https://downloads.lede-project.org/snapshots/packages/mipsel_24kc/packages/

I could just download and install using:

opkg install zile_2.3.24-4_mipsel_24kc.ipk

@Luciano-S. said in Zile:

@Mikael-Djurfeldt ,yea ... you are a beta tester and it is great that you inform us.

You can go back any time to any version ... check out pls:
http://community.onion.io/topic/1208/do_page_fault-sending-sigsegv-to-fast-gpio-for-invalid-read-access-from-00000600/5

Thanks

@Luciano-S. said in Can't switch off AP mode:

@Mikael-Djurfeldt , there are issues with some browsers and the web-interface ...at least with omega1 was it so when it came out. And that's why Maksim also gave you the link for manual configuration in the terminal ... the script does the same ... just through the Web-app.

If manually not works check your firmware and bring it up to date. You are not the first one with this problem.

Well, as I write already in my first post above, I know that I, in principle, could solve the problem by changing /etc/config/{wireless,network}. However, my problem is that I don't know how they should look like to get just a simple Wifi client on my WLAN. I could of course experiment after having read the OpenWRT docs, but want to have a solution which both fits the Omega2 hardware well and also doesn't mess up the Omega Console or other Omega specific software. So, I would really appreciate if anyone who has succeeded in just having a simple WLAN client setup could post the config files for this.

I'm examining to what extent Omega2 can be used as a wifi range extender. Now there seems to be some confusion about what a range extender is. Some "range extenders" use the same channel as the router and re-transmits on a different SSID. In my view, a range extender is rather a device which receives packets from the wireless router and re-transmits them using the same SSID, preferably on a different radio channel.

I have three questions. I'm interested in the answers to all independently:

1. Can Omega2 receive on one wireless channel and transmit on another? More specifically, can the two virtual wifi interfaces (AP + STA) operate on different channels?

2. I tried to set my "option channel" to a specific channel rather than 'auto'. This didn't change anything. Is it not possible to choose on which channel the Omega2 AP is operating?

3. If operating on the same channel, is it possible to configure both AP and client to use the same SSID? Some "range extenders" seem to cope with this.

Best regards,
Mikael D.

I'm examining to what extent Omega2 can be used as a wifi range extender. Now there seems to be some confusion about what a range extender is. Some "range extenders" use the same channel as the router and re-transmits on a different SSID. In my view, a range extender is rather a device which receives packets from the wireless router and re-transmits them using the same SSID, preferably on a different radio channel.

I have three questions. I'm interested in the answers to all independently:

1. Can Omega2 receive on one wireless channel and transmit on another? More specifically, can the two virtual wifi interfaces (AP + STA) operate on different channels?

2. I tried to set my "option channel" to a specific channel rather than 'auto'. This didn't change anything. Is it not possible to choose on which channel the Omega2 AP is operating?

3. If operating on the same channel, is it possible to configure both AP and client to use the same SSID? Some "range extenders" seem to cope with this.

Best regards,
Mikael D.

I just upgraded from b157 to b163 on my Omega2+.

I get multiple stack traces during boot, which ends with a kernel panic and attempt to reboot (which fails).

Here's the log of the boot process.

What is wrong?

@Chris-Stratton @Theodore-Borromeo Right, it is Omega2 (or any mipsel_24kc based on the musl libc).

For those of you who have a root fs larger than 128M, for example through putting it on the sdcard or a USB stick, this package might be interesting:

emacs_25.1_mipsel_24kc.ipk

It requires around 10-12 MB of RAM initially when running.

Best regards,
Mikael

@Luciano-S. said in sdcard pivot overlay no longer working:

@Mikael-Djurfeldt said in sdcard pivot overlay no longer working:

Frankly, I also don't understand the logic behind that procedure: How, exactly, is the file /etc/config/fstab even read? It belongs to the overlayfs which should not be mounted. There must be some script magic involved here, but without an understanding of where the pivot overlay is checked and mounted, I cannot debug it.

Did you do a factory reset or a firmware downgrade ? Then you loose your config "/etc " folder. I'm not sure if you loose it also with a normal update ?!

Going thru the tutoria againl would help ... so you create your new config in /etc again.

I both copied the internal flash overlay using tar and made sure there was a correct /etc/config/fstab before doing reboot.

I'm in the position that I cannot get the Omega2+ to do the alternative overlayfs mount. It just mounts the internal flash overlay.

@Luciano-S. said in Writing to /proc:

you my have to do a space before the path ?!:

No, that doesn't matter.

echo 0 > /proc/sys/kernel/randomize_va_space

Is /proc not just mounted as read only?

Well, I tried mount -o remount,rw /proc but that didn't help.

The problem I reported was under b145. Now I run b150 and the problem has disappeared. No idea of what is going on...

For a while, I could use the setup described here to get the sdcard on my omega2+ mounted as overlay instead of /dev/mtdblock6 (that was with b145). But the procedure no longer works (now on b150).

Frankly, I also don't understand the logic behind that procedure: How, exactly, is the file /etc/config/fstab even read? It belongs to the overlayfs which should not be mounted. There must be some script magic involved here, but without an understanding of where the pivot overlay is checked and mounted, I cannot debug it.

@administrators Could we have a description of how the overlayfs is checked and mounted at boot, and by what scripts?

Please help!

I've now encountered a couple of situations where I've tried to change kernel settings by writing to /proc and where this fails. Example:

root@Omega-xxxx:/home/x/emacs-25.1# echo 0 >/proc/sys/kernel/randomize_va_space
bash: echo: write error: Invalid argument

Why is this?

Does it have something to do with Strip non-essential functionality from /proc filesystem being enabled?

@Adrian-Rix Sure---I built using the "image" branch of https://github.com/WereCatf/source.git on a Debian stretch system.

Basically, once you have checked that out, you can do just

make

to get the image, however you might want to select things using

make menuconfig

first.