Re: Cubox-i bullseye -> bookworm Upgrade failure

2023-08-04 Thread RobJE Debian ARM
Hi, On 04-08-2023 08:55, Rainer Dorsch wrote: Hi, I did a test installation with a bullseye installer on a cubox-i and then upgraded to bookworm. After the upgrade the network was gone. Even booting with the previous kernel 5.10.0-23-armmp does not bring the network back. Any hints and ideas a

Using Raspberry POE+ hat with bullseye

2021-11-28 Thread kl+debian-arm
Hi, I am using Debian Bullseye on a Raspberry PI 4 with a POE+ hat. So far I am unable to get the fan on the POE+ hat working. Setting dtparam=poe_fan_temp0=65000,poe_fan_temp0_hyst=5000 dtparam=poe_fan_temp1=67000,poe_fan_temp1_hyst=2000 in /boot/config.txt did not work. Tested with #uname

sun4i_codec kernel warnings due to missing card->owner

2021-03-25 Thread RobJE Debian ARM
Hi list, What is needed to get the patch from #980539 included? Looking at the source for 5.10.24 the problem still exists and is limited to sun4i_codec and (potentially) rk3288_hdmi_analog modules. These modules have a "stuct snd_soc_card" with no "owner" set, which triggers kernel warnings

Re: help

2020-02-17 Thread RobJE Debian ARM
n, open a shell and then look at > /var/log/syslog to see what's going on. How much RAM does the TS-221 have. When its 1GB this could be the cause of the issues. There is a known issue with devices that have more than 768M of RAM. See [1] [1] <https://lists.debian.org/debian-arm/2018/05/msg00028.html> GRTNX, RobJE

Re: "external abort on linefetch (0x814)" on Kirkwood 6282 SoC

2018-06-05 Thread RobJE Debian ARM
On 02-06-18 21:31, Andrew Lunn wrote: > On Sat, Jun 02, 2018 at 09:48:47PM +0300, Timo Jyrinki wrote: >> 2018-06-02 18:55 GMT+03:00 Ian Campbell : >>> You need to append a dtb and then encode in u-boot's uImage format. >>> e.g. >>> >>>cat arch/arm/boot/zImage arch/arm/boot/dts/kirkwood-ts419-62

Re: "external abort on linefetch (0x814)" on Kirkwood 6282 SoC

2018-05-27 Thread RobJE Debian ARM
On 24-05-18 14:30, Andrew Lunn wrote: > On Thu, May 24, 2018 at 12:40:06PM +0300, Timo Jyrinki wrote: >> 2018-04-25 14:16 GMT+03:00 Martin Michlmayr : >>> Timo Jyrinki is happy to run some tests. He's affected and has a >>> serial console. The bug is still there in the 4.9 kernel we're >>> shippi

Re: "external abort on linefetch (0x814)" on Kirkwood 6282 SoC

2017-07-31 Thread RobJE Debian ARM
On 29-07-17 17:50, Andrew Lunn wrote: > So i'm thinking this has to be related to bits of hardware i'm not > using. I don't have anything on the PCIe bus, i don't have any USB > devices plugged in, i don't use the mtd devices, etc. > > Could somebody who does have the issue describe their system?

error since moving to marvell kernel - BUG: Bad rss-counter state

2016-10-23 Thread R Epping - debian-arm
Hello All, Today I tried again to run linux-image-marvell (4.7.0-0.bpo.1 in this case) on my QNAP TS-221. I had issues with it in the past but did not get around to file a bug. I have the same version on a TS-219 which is running fine. Booting the TS-221 generates two types of error messages. --

Qnap TS-421: GPIOs (for qcontrol and ethernet) not working

2016-08-17 Thread debian-arm
Hi, I'm running Debian on my TS-421 and recently switched to stretch, with the most recent kernel: "Linux TS-421 4.6.0-1-marvell #1 Debian 4.6.4-1 (2016-07-18) armv5tel GNU/Linux" Since then some features of qcontrol are not working anymore, like controlling the LCD and Backlight, turning th

Re: Page allocation failures and lockups since Jessie on QNAP kirkwood NASes, even with 5gb swap-on-md-raid1 free

2015-08-26 Thread debian . arm . nospam . again
On Mon, Jul 27, 2015 at 15:39:53 +0200, debian.arm.nospam.ag...@sub.noloop.net wrote: > Hi. Since upgrading to Jessie, I've been experiencing frequent lockups on my > QNAP NASes (TS-419P+ and TS-219P) particularly under heavy I/O. Usually the > devices just drop dead (not even answering to ping),

QNAP: Booting with an incomplete mdadm raid (bug 784070)

2015-08-26 Thread debian . arm . nospam . again
Hi, on one of my QNAP TS-419P+ NASes running Debian 8.x stable, I started getting smart errors on one out of the four SATA drives, so I pulled the drive and swapped it for a brand new one. The system didn't boot any more. I found bug 784070 and particularly message 109 https://bugs.debian.org

Page allocation failures and lockups since Jessie on QNAP kirkwood NASes, even with 5gb swap-on-md-raid1 free

2015-07-27 Thread debian . arm . nospam . again
lab pages Jul 27 13:13:33 hostname kernel: 163382 pages shared Jul 27 13:13:33 hostname kernel: 0 pages swap cached -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150727133952.ga1...@noloop.net

QNAP TS-419 and TS-219P troubles during today's jessie updates: Massive kernel oopses + no boot

2015-04-05 Thread debian . arm . list . nospam . jessie . upgrade
, it pours :-/ Would be grateful for any input, and hoping this can be of help to the people preparing the jessie release as well. And sorry for the wall of text. Thanks. -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150405194547.ga7...@noloop.net

Re: Information needed from owners/users of Debian on ARM/kirkwood base QNAP devices (should take < 1min to gather)

2014-06-17 Thread debian . arm . kirkwood . survey
: Marvell Kirkwood (Flattened Device Tree) > dt model: QNAP TS419 family > > PCI devices: > 00:01.0 0604: 11ab:6281 (rev 02) > 01:00.0 0100: 11ab:7042 (rev 02) > > PHY devices (/sys/bus/mdio_bus/devices/): > f1072004.mdio-bu:00 f1072004.mdio-bu:08 > > Soc Bus:

Re: New kernel not fully installed on Sheevaplug

2009-10-11 Thread debian . arm . nospam
x27;m still running on the previous > kernel. I've noticed this as well, try manually running "flash-kernel" as root to regenerate uImage + uInitrd from the /boot/vmlinuz symlink. Seems like there's a missing hook somewhere so this step is left out? -- To UNSUBSCRIBE,

Re: Sheevaplug Kernel packages - backports.org vs people.debian.org/~tbm/orion vs tbm snapshots

2009-10-10 Thread debian . arm . nospam
bpo packages configured and patched identically? Finally, regarding stable vs unstable, personally it doesn't matter but if there's a difference in gcc versions used, then I guess maybe the unstable kernels may cause trouble if there is a need to compile 3rd party kernel modules

Sheevaplug Kernel packages - backports.org vs people.debian.org/~tbm/orion vs tbm snapshots

2009-10-09 Thread debian . arm . nospam
.30-6~bpo50+1" which ~tbm has "2.6.30-8". Thanks! -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: ARM kernel snapshots - 2.6.31

2009-09-27 Thread debian . arm . nospam
nk-kirkwood (Debian 2.6.31-1~experimental.1) (m...@debian.org) (gcc version 4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 Sat Sep 26 13:47:12 UTC 2009 -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Sheevaplug linux headers

2009-09-21 Thread debian . arm . nospam
nny-backports&keywords=kirkwood Try adding to /etc/apt/sources.list: deb http://www.backports.org/debian lenny-backports main -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: ARM kernel snapshots - 2.6.31

2009-09-21 Thread debian . arm . nospam
4:41:37 entropy kernel: [171529.951829] [] (cpu_idle+0x74/0xa4) from [] (start_kernel+0x27c/0x2e8) Sep 21 14:41:37 entropy kernel: [171529.960253] [] (start_kernel+0x27c/0x2e8) from [<8034>] (0x8034) Sep 21 14:41:37 entropy kernel: [171529.967639] ---[ end trace 8a9a2ad1dc3e040b ]---

Re: Upgrading kernel on a NSLU2

2008-01-09 Thread debian-arm
[EMAIL PROTECTED] wrote: I am really worried on using apt-get to upgrade the kernel. Can somebody guide me on how to upgrade the kernel. More specifically the following are my concerns. (I am referring to Installing Debian on the Linksys NSLU2 g

Virus intercepted

2004-10-06 Thread debian-arm
A message you sent to <[EMAIL PROTECTED]> contained Worm.SomeFool.AB and has not been delivered.