iw utility missing

Andrea Benini — Thu, 09 Feb 2017 07:49:04 -0000

iw tools & utils are still missing , that's why you're facing those troubles with the wlan config. I haven't touched the wireless part yet (same goes for the BT) and I'm planning to do that real soon. I'm now focused on compatibility tests because the OS boots fine on RPi3 but not on RPi1 and I guess I have optimized too much the kernel config, that's why it's still a beta. Inner tests are now on wired eth board and that part is fine. please also see yesterday post (http://moebiuslinux.sourceforge.net/general/beta-goes-on-and-hw-tests-too/) for further details. stdout messages are there but since it's still a beta you may see them on serial console only even if I have already changed that.

iw utility missing

Andrea Benini — Wed, 08 Feb 2017 21:59:49 -0000

Hi!

First of all thank you for this work, it is wonderful to have an OS that small.
But I'm having troubles in configuring wifi...... :(

this is the result from lsusb command, I also already checked with lsmod to see if the correct module is loaded on the kernel, and so it is;

Bus 001 Device 004: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter

Also with ifconfig I can see wlan0, but I can't get no IP address, and I don't know how to do it....searching the web i found those iw utilities, so that I could list available wifi networks, and maybe connect to them.....for sure I'm missing something very stupid, please help me!! :)

ifconfig result:
wlan0 Link encap:Ethernet HWaddr 00:13:EF:6B:11:FE
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Again, thanks for the good work you're doing!
Alessandro

Packages on build/wish list

CarlGB — Thu, 17 Nov 2016 01:15:22 -0000

openVPN still be very useful or do you have any documentation on building packages/containers for Moebius? Thanks

Forum Rules

Andrea Benini — Thu, 03 Nov 2016 08:26:23 -0000

I have stopped its development for a while due to timings constraints but I'm rebuilding it with newer drivers (rpi2, 3, Zero) and newer package versions. I have experimented some of my PIs in heavy duty environments and I'm really upset with systemd and SD card corruptions on raspbian so I'm giving back some time to this project again. It might take a while because my previous setup was a pure cross compiling pain with some manual patches on the source tree, I guess it might take some time but obviously the new work is based on Rpi3 and Zero because I need them in robotics and opencv. Give me a while but it's on the way.

Forum Rules

Andrea Benini — Thu, 03 Nov 2016 00:01:33 -0000

Hi unfortunately not working with RP 3 either , but well done if you got more help it would take you less time , bare bones o.s. is a great idea for headless stuff , i will donate once working pi 2 and 3 is ready !

Packages on build/wish list

Andrea Benini — Thu, 17 Mar 2016 08:11:57 -0000

I'm now working on a special build (not published, it's just an early beta now) with a robot of mine. I dont' know ROS and I'm a totally newbie with opencv as well. It works but I didn't get any benchmarks.
I'll put fortran on my wishlist and see how it goes

Packages on build/wish list

Andrea Benini — Wed, 16 Mar 2016 21:50:36 -0000

opencv? Seriously? That's impressive. Did you include
libatlas-base-dev gfortran
for faster matrix calculations? I can't wait to try it out...it took HOURS to set it up on my B+...the compilation time alone was 10 hours. Brutal.

Moving log files to RAM Using Ramlog

Andrea Benini — Tue, 23 Feb 2016 14:28:32 -0000

You may use these two options:
1) Do not use the cross compile tools at all. Just pickup your favorite Raspberry, install the gcc toolchain there ("moebius container install lang.gcc", "apt-get install gcc ...") and install gcc compiler and utils on the same machine. Decompress the .tar.gz file with your sources and compile them directly on the same machine so you can have binary compatible executables for the platform

2) I use Linux machines on a daily basis, at home and at work as well. My personal choice goes to Gentoo and I mainly use it on my workstations (always) and servers (where possible); with Gentoo you're familiar with cross-compile toolchains because you see some of them even during the installation process. Here are few links from my browser.
Gentoo specific)
- https://wiki.gentoo.org/wiki/Distcc/Cross-Compiling, this is where I started
- https://wiki.gentoo.org/wiki/Raspberry_Pi/Cross_building, Raspberry Pi specific. From here take a look at the links on the page as well
General purpose)
- http://wiki.osdev.org/GCC_Cross-Compiler, nice guide as usual on osdev.org
- http://preshing.com/20141119/how-to-build-a-gcc-cross-compiler/, a nice intro
- http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/, one of the first guides related to the Pi itself

I don't have .SPEC files or other packages built just for the distro, I'm just working with a toolchain for Broadcom ARM 2835.
Option (2) is tough but it's a nice challenge

Moving log files to RAM Using Ramlog

Andrea Benini — Tue, 23 Feb 2016 13:57:25 -0000

All right... this makes sense.

However, I'm not feeling confortable with the compilation from source.
Could you please give some advice how to compile the program using moebius toolchain in a test environment (= LXC container on host running 32-bit Debian)?
I'm a noobie here, means I don't know how to setup the ARM-HF environment in the container.
Any advice, links, etc. are highly appreciated.
Creating LXC is no issue.

THX

Moving log files to RAM Using Ramlog

Andrea Benini — Thu, 18 Feb 2016 09:55:35 -0000

There's no stupid questions, just unasked ones.
If you have a binary executable build of your program, even if it's for the right platform (arm-hf) it's not probably right for this distro because I'm not using glibc. If this executable is dynamically using the glibc (syscall or whatever) you might need to have the same lib compiled as well. A possible solution might be to recompile the program with the right toolchain (gcc+binutils+libc+...) for this distro, but you need to recompile with moebius toolchain.
Pratically speaking when you handle with a device and you use it as a real embedded device you always prefer to strip unused pieces of code, you create your own versions of binaries without the frills of a general purpose distribution. I have worked with several embedded platforms (mostly ARM and MIPS) and the first thing you do is to create a toolchain for that architecture. When you want to save space or optimize it better you always skip glibc because it's too fat (consider a linux port for a wireless router for example) and you tend to use uglibc, eglibc or something like that. uGlibC it's probably the best choice for an embedded device but it's too radical for me because you have tons of problems (and patches as well) when you'd like to have a large package base, eglibc is a good balance between space, optimizations, speed and sw compatibility.

Recent posts to Support

iw utility missing

iw utility missing

Packages on build/wish list

Forum Rules

Forum Rules

Packages on build/wish list

Packages on build/wish list

Moving log files to RAM Using Ramlog

Moving log files to RAM Using Ramlog

Moving log files to RAM Using Ramlog