Posts made by Paolo Ciuffetti

Yes @luz, we are working on the same project. I'm using informations taken from this thread and this link. I'm rebuilding a new firmware with modifications on sd.c (like /sza2 wrote in this thread) and 02.network (see the linked link) to enable 2 lans (1 wan, 1 lan) and see what happens.

On very first message you wrote that the address modification (devmem 0x1000003C 32 0x00E001FF) worked for you, but super ugly. It's not working for us, so I asked on this thread more informations on how to make it works for us too..

I'll post my results on this topic when the new firmware will be ready and installed on my omega2s

@luz Hello! This topic is very interesting for me! I'm using an omega2s and I wanted to use eth0 and eth1 (with a custom board). I've recompiled the official firmware adding devmem, installed it and ran:

devmem 0x1000003C 32 0x00E001FF

Now, the registry has the 'correct' value but the switch isn't working. I've ran:

root@Omega-89C9:~# swconfig dev switch0 show
Global attributes:
	enable_vlan: 0
	alternate_vlan_disable: 0
	bc_storm_protect: 0
	led_frequency: 0
Port 0:
	disable: 0
	doubletag: 1
	untag: 1
	led: 5
	lan: 1
	recv_bad: 0
	recv_good: 845
	tr_bad: 0
	tr_good: 816
	pvid: 0
	link: port:0 link:up speed:100baseT full-duplex 
Port 1:
	disable: 0
	doubletag: 1
	untag: 1
	led: 5
	lan: 1
	recv_bad: 0
	recv_good: 0
	tr_bad: 0
	tr_good: 0
	pvid: 0
	link: port:1 link:down
Port 2:
	disable: 0
	doubletag: 1
	untag: 1
	led: 5
	lan: 1
	recv_bad: 0
	recv_good: 0
	tr_bad: 0
	tr_good: 0
	pvid: 0
	link: port:2 link:down
Port 3:
	disable: 0
	doubletag: 1
	untag: 1
	led: 5
	lan: 1
	recv_bad: 0
	recv_good: 0
	tr_bad: 0
	tr_good: 0
	pvid: 0
	link: port:3 link:down
Port 4:
	disable: 0
	doubletag: 1
	untag: 1
	led: 5
	lan: 1
	recv_bad: 0
	recv_good: 0
	tr_bad: 0
	tr_good: 0
	pvid: 0
	link: port:4 link:down
Port 5:
	disable: 1
	doubletag: 1
	untag: 1
	led: ???
	lan: 1
	recv_bad: 0
	recv_good: 0
	tr_bad: 0
	tr_good: 0
	pvid: 0
	link: port:5 link:down
Port 6:
	disable: 0
	doubletag: 1
	untag: 1
	led: ???
	lan: ???
	recv_bad: ???
	recv_good: ???
	tr_bad: ???
	tr_good: ???
	pvid: 0
	link: port:6 link:up speed:1000baseT full-duplex 
VLAN 0:
	ports: 0 1 2 3 4 5 6 
root@Omega-89C9:~#

but the output is the same as before running devmem and if I connect an ethernet cable on the second port, I don't see any link. What am I missing? Maybe the custom board is not working properly? Or Do I have to configure something in /etc/config/network? Or with swconfig? Sorry for all these questions but I'm relatively new to omega2 and swconfig

Thank you so much for your support,
Paolo

Sorry, my fault 194 is ok!

Hello. Like the title says, why has this image disappeared from omega2 repo? I need i2c for my project... Thank you for any information you can give me.

Hello,
from the output of opkg --help you can see this information:

-d <dest_name>
Use <dest_name> as the the root directory for package installation, removal, upgrading. <dest_name> should be a defined dest name from the configuration file, (but can also be a directory name in a pinch).

So, I edited my /etc/opkg.conf adding a dest name called opkg_test for /tmp folder; My etc/opkg.conf now is:

dest root /
dest ram /tmp
dest opkg_test /tmp
lists_dir ext /var/opkg-lists
option overlay_root /overlay
option check_signature 1

Then, I've copied a package (transmission-web_2.92+git-4_mipsel_24kc.ipk) in /tmp/ to make a test, and launched opkg this way:

opkg install -d opkg_test /tmp/transmission-web_2.92\+git-4_mipsel_24kc.ipk
Installing transmission-web (2.92+git-4) to opkg_test...
Configuring transmission-web.

and if you make a find of "transmission*" on /, you can see that it's installed under /tmp/:

root@Omega-D339:/# find / -name "transmission*"
/tmp/transmission-web_2.92+git-4_mipsel_24kc.ipk
/tmp/usr/share/transmission
/tmp/usr/share/transmission/web/style/transmission
/tmp/usr/share/transmission/web/javascript/transmission.js
/tmp/usr/lib/opkg/info/transmission-web.list
/tmp/usr/lib/opkg/info/transmission-web.prerm
/tmp/usr/lib/opkg/info/transmission-web.postinst
/tmp/usr/lib/opkg/info/transmission-web.control
root@Omega-D339:/#

To remove the package, simply run: opkg remove -d opkg_test transmission-web (it prints an error because it's looking for a file in /usr/lib/opkg/info/... but the package is correclty removed)

Hope this helps,
Paolo

Update 2:

I've found this topic from @Maximilian-Gerhardt (Thank you for your excellent guide), explaining how to build kernel module for Omega2. I've found this in his topic:

...
It conveniently compiled the hello-world.ko file and even created an ipk package.
Unfortunetly, trying to installing that package will give you a kernel mismatch error
because the kernel hashes differ (see this link). Loading the .ko file directly will still work though.
...

So, I'm able to compile the kernel modules I need (copying the .ko files in /lib/modules/4.4.74/, but the ipk still does not match.

Any suggestions to compile ipk kernel modules for official firmware?

Update:
I've found that the compiling process inside my docker has created a kernel_4.4.74-1-8274f1be988bfc7fa195bc75194d9e87_mipsel_24kc.ipk

So, I installed this package on my onion2, rebooted (no dmesg errors) and now I can correctly install my kernel modules without errors.

The question remain, because I don't want to use a custom kernel. I want to use the official omega2 firmware and then install my kernel module for the official kernel.

How can I obtain this?

Thanks again,
Paolo

Hello,
I'm new here and I'm working on a project using omega2.

I'm trying to build some kernel module (kmod-batman-adv, kmod-i2c-algo-bit, ...) using the cross-compiling docker prepared from onion (https://hub.docker.com/r/onion/omega2-source/). I've followed the tutorial (https://onion.io/2bt-cross-compiling-c-programs-part-1/) and other useful links but the result is that the modules compiled inside the docker are compiled for kernel 4.4.74-1, while the omega 0.2.0 b194 has kernel 4.4.74.

When I try to install the compiled ipk on my omega, this is what I get:

root@Omega-D339:/tmp# opkg install ./kmod-i2c-algo-bit_4.4.74-1_mipsel_24kc.ipk
Installing kmod-i2c-algo-bit (4.4.74-1) to root...
Collected errors:

• satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-i2c-algo-bit:
• kernel (= 4.4.74-1-8274f1be988bfc7fa195bc75194d9e87) *
• opkg_install_cmd: Cannot install package kmod-i2c-algo-bit.

If I run uname -a, what I see is:

root@Omega-D339:/tmp# uname -a
Linux Omega-D339 4.4.74 #0 Tue Jul 31 16:32:08 2018 mips GNU/Linux

So, my question is: How can I cross compile kernel modules for omega2 official firmware?

Thank you for your help,
Paolo