El 19/8/21 a les 11:44, Luca Olivetti ha escrit:
El 19/8/21 a les 10:56, Luca Olivetti ha escrit:
El 19/8/21 a les 10:05, Arnd Bergmann ha escrit:
To confirm that this is the actual problem, can you try building the
package using '-O2 -march=armv4t' or '-O2 -march=armv5t&#
El 19/8/21 a les 10:56, Luca Olivetti ha escrit:
El 19/8/21 a les 10:05, Arnd Bergmann ha escrit:
To confirm that this is the actual problem, can you try building the
package using '-O2 -march=armv4t' or '-O2 -march=armv5t' to
override the default 'armv5te'?
El 19/8/21 a les 10:05, Arnd Bergmann ha escrit:
To confirm that this is the actual problem, can you try building the
package using '-O2 -march=armv4t' or '-O2 -march=armv5t' to
override the default 'armv5te'?
With -march=armv5t it doesn't work (same failure), I'll try with armv4t.
FWIW this
El 19/8/21 a les 9:03, Luca Olivetti ha escrit:
I then recompiled it with -O0 instead of the default -O2 and this time
it works (will try later with -O1).
Nope, with -O1 same failure.
Bye
--
Luca
Hello,
I upgraded a test machine (buffalo linkstation pro/Marvell Orion5x) from
buster to bullseye, then I rebuilt the dspam[*] deb (since it's been
dropped by debian since buster, I did the same there).
The newly built binary doesn't start, complaining of a configuration
error, the binary bui
El 26/11/20 a les 11:35, Arnd Bergmann ha escrit:
According to the arch/arm/boot/dts/kirkwood-laplug.dts file in the kernel
(if that is the right machine), it has 512MB NAND flash, with a 16MB
partition for the kernel, so that would still be sufficient for a while.
The dts is kirkwood-ns2, it
El 26/11/20 a les 11:33, Martin Michlmayr ha escrit:
* Luca Olivetti [2020-11-26 11:15]:
QNAP support won't be in Debian 11 (and probably the whole armel port
will be dropped). Support in the Debian kernel package was disabled
in August 2019 due to size issues.
So that's not QNA
El 20/11/20 a les 6:36, Martin Michlmayr ha escrit:
QNAP support won't be in Debian 11 (and probably the whole armel port
will be dropped). Support in the Debian kernel package was disabled
in August 2019 due to size issues.
So that's not QNAP specific, all kirkwood[*] based machines will b
El 14/8/20 a les 1:49, Daniel Gröber ha escrit:
Uff, yeah that's bad. I'd contact the ISP and ask them to fix this their
deployment is quite broken if they do things like this.
I think the problem is the bottom of the barrel router they're using
(zte, running linux 2.6.36, enough said, but
El 13/8/20 a les 22:23, Daniel Gröber ha escrit:
Hi Luca,
On Thu, Aug 13, 2020 at 07:02:21PM +0200, Luca Olivetti wrote:
I found out that, since the router has RA enabled, the boxes get an ipv6
globally routable address. The problem is, when the prefix changes
(unfortunately it's not s
Not strictly arm but this is the only debian list I'm subscribed too and
I see this on 2 arm boxes, so
I recently switched isp and this one has native ipv6 as well as ipv4. I
configured nothing on any of those boxes (one running stretch, the other
buster), just a static ipv4 address in /et
El 17/1/20 a les 19:31, Rogério Brito ha escrit:
Source: linux
Version: 4.19.67-2+deb10u2
Severity: important
X-Debbugs-CC: debian-arm@lists.debian.org
Hi, Ben and others.
I've been getting some OOM errors on my armel/kirkwood device running Debian
stable. One of the reasons for this is, accord
El 10/10/19 a les 21:06, Christoph Biedl ha escrit:
Hello,
This is an old Seagate Dockstar (Feroceon 88FR131, armv5tel CPU) running
Debian stretch. Then:
# lshw -xml
Segmentation fault
Since I'm procrastinating the upgrade to buster ;-) I can confirm that
it happens here with a lac
El 28/7/19 a les 14:09, Reco ha escrit:
Yes. No. Maybe. These things are called Predictable because they aren't.
A modern systemd paradox, if you will.
:-D
Btw,
ln -s /dev/null /etc/systemd/network/99-default.link [*]
worked, at least in stretch. I hope that it still works in buster.
[*]
El 27/7/19 a les 23:20, Reco ha escrit:
yet it always gets the name wlxe894f615307a.
What you're doing colud work.
The problem is - you have NIC that's attached via USB, so the usual
rules do not apply.
The reason of it - /lib/udev/rules.d/73-usb-net-by-mac.rules, that's
applied after your
Hello,
I'm preparing to upgrade my linkstation pro from stretch to buster.
I'm following the instructions here:
https://www.debian.org/releases/buster/armel/release-notes/ch-information.en.html#migrate-interface-names
and I'm trying to use .link files in /etc/systemd/network to rename the
int
El 22/9/15 a les 11:41, Simon Guinot ha escrit:
On Thu, Sep 17, 2015 at 01:24:32PM +0200, Luca Olivetti wrote:
El 17/09/15 a les 10:37, Simon Guinot ha escrit:
On Wed, Sep 16, 2015 at 08:11:10PM -0400, Martin Michlmayr wrote:
* Luca Olivetti [2015-09-13 19:32]:
apologies if this is the
El 17/4/19 a les 2:50, rajudev ha escrit:
Luca Olivetti writes:
El 10/4/19 a les 18:40, Luca Olivetti ha escrit:
Today I was home when it started beeping with a different pattern (long
beeps). I could login to the lspro and restart the micro-evtd daemon. That
fixed the problem (until next
El 10/4/19 a les 18:40, Luca Olivetti ha escrit:
Today I was home when it started beeping with a different pattern (long
beeps). I could login to the lspro and restart the micro-evtd daemon.
That fixed the problem (until next time).
Of course, right after hitting send, I found this message
Hello,
I have a linkstation pro v1 (marvell orion5x) with a broken disk that
has been sitting in a drawer for several years.
A couple of days ago I fitted a new disk, installed debian wheezy,
dist-upgraded to jessie, dist-upgraded to stretch.
I started from wheezy since I wanted to test the
El 17/09/15 a les 10:37, Simon Guinot ha escrit:
On Wed, Sep 16, 2015 at 08:11:10PM -0400, Martin Michlmayr wrote:
* Luca Olivetti [2015-09-13 19:32]:
apologies if this is the wrong list.
I'm currently running debian wheezy on a lacie network space v2.
I'd like to dist-upgrade it
El 13/09/15 a les 19:32, Luca Olivetti ha escrit:
Hello,
apologies if this is the wrong list.
I'm currently running debian wheezy on a lacie network space v2.
I'd like to dist-upgrade it to jessie. Is it reasonably safe to do so?
I can get access to a serial console, but I'd avo
Hello,
apologies if this is the wrong list.
I'm currently running debian wheezy on a lacie network space v2.
I'd like to dist-upgrade it to jessie. Is it reasonably safe to do so?
I can get access to a serial console, but I'd avoid it (IIRC the pins
are difficult to reach).
TIA
--
Luca
23 matches
Mail list logo
