[Espressobin support development efforts]

Well, it says "prefixes", plural, so why shouldn't that variable contain both / and /boot/? The former for when you have a dedicated boot partition, the latter if you don't.

[Espressobin support development efforts]

To be fair, I have three, from the first series. With identical settings, one is definitely unstable (dunno how they got it to pass what Globalscale considers testing, let alone what I would do), one is 100% stable and working as my main router, and one is in my "TODO try with current mainline" pile. We'll see whether I can get the thing to work without much hassle; if not, it'll be replaced with a Raspberry Pi 4 and two USB3 Ethernet dongles.

 

NB: Recycling, not trash, please. (Yes I know that electronics recycling is far from optimal.)

[Espressobin support development efforts]

Yet another reason not to buy one of those things.

[Espressobin support development efforts]

54 minutes ago, FlashBurn said:

So, maybe some people can tell which firmware and which kernel version they use running at 1000 MHz that works for them (board revision just for the record). I want to find out if it maybe could be that the newer kernels are not working at 1000 MHz anymore.

Or maybe only some boards don't. Reports of people sending back 6 of 8 boards because they can't run 24h before going belly-up kindof point towards that cause.

[Espressobin support development efforts]

14 hours ago, danglin said:

       {.cpu_freq_max = 800*1000*1000,  .divider = {1, 2, 3, 4} },

       {.cpu_freq_max = 600*1000*1000,  .divider = {1, 2, 3, 4} },

That doesn't look right. You can't use the same divider values for two different max frequencies.

[Espressobin support development efforts]

On 7/14/2018 at 8:50 PM, y52 said:

 

I suggest modifying as follows the

/lib/systemd/system/systemd-networkd.service

 

 

 

I suggest doing no such thing.  Files in /lib don't belong to you and will be overwritten by the next random update of the package they belong to.

 

Instead, copy this file to /etc/systemd/system/ and edit it there. Alternately, systemd has a well-documented mechanism to override things like ExecStartPre= entries.

[Espressobin support development efforts]

10 hours ago, y52 said:

Execute after changes:

systemctl daemon-reload

 

Reboot.

 

This may be a stupid question, but why would you do a daemon-reload if you're going to immediately reboot anyway?

 

I

[Espressobin Debian testing]

There is no physical interface named "eth0" you could talk on.

There are interfaces named "lan1", "lan0" and "wan". However, eth0 is what the CPU uses to multiplex these, so you need to set that to "up" too.

I do it with this simple systemd-networkd rule:
 

# cat /etc/systemd/network/49-switch.network
[Match]
Name=eth0

[Network]
DHCP=no

Then you can access the three real interfaces normally.

[Espressobin support development efforts]

8 hours ago, chrisf said:

I decided not to waste any more time and money in it.

Same here. Of three boards, one is used for routing and seems stable. The other two can't run an hour without ugly memory errors. Like, bash doesn't dynamically link because a symbol name got corrupted. "Reliably". OWCH. I was trying to run a database on that thing??

[Espressobin support development efforts]

If you use systemd-resolved, you need to disable resolvconf.

 

[Espressobin support development efforts]

9 minutes ago, y52 said:

Has anybody managed preventing the NetworkManager from launching at startup ?

What's wrong with

systemctl mask NetworkManager.servce

?

[Espressobin support development efforts]

Ah. Found it. The package requires a "make scripts" to be executed in /usr/src/linux-headers-*, which should be done in postinst but isn't (or dies silently).

Issue #830 filed.

[Espressobin support development efforts]

I do not want to know how to build my own kernel inside a virtualbox or whatever.
I want the kernel packages thus built to be usable for everything they're supposed to be usable.

This means that the generated kernel-headers package is required to contain a couple of binaries which are required to build new modules on the target. Specifically:

/usr/src/linux-headers-4.14.2-mvebu64/scripts/basic/bin2c
/usr/src/linux-headers-4.14.2-mvebu64/scripts/basic/fixdep
/usr/src/linux-headers-4.14.2-mvebu64/scripts/mod/modpost

need to be present for dkms (and other methods to build modules out of tree) to work.

[Espressobin support development efforts]

NB: Building modules on the target doesn't work because some programs in kernel_headers/scripts/simple and …/mod need to be compiled (for the target) and included in the kernel-headers package.

[Espressobin support development efforts]

The current -next version works for me. Lots of thanks, everybody.

 

One problem, however: no CONFIG_REGULATOR_ARMADA3700 option in the kernel, hence (I assume) no cpufreq support. Which is not cool – literally, as some of the ICs get quite hot.

 

Is it possible to change that? I'd be OK with lowering the frequency permanently at u-boot time.