It seems that message from Karsten Sperling never made it to
debian-arm.
* Karsten Sperling [2020-12-30 13:33]:
> Thanks,
>
> turns out overriding the MTD layout via the kernel command line works. In
> case anyone else finds this useful, these are the U-Boot environment
> settings I'm using to
Am 09.01.21 um 06:10 schrieb Martin Michlmayr:
> * basti [2021-01-08 19:31]:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976723
>>
>> I have no TS-209 for testing. At the moment it only work on kirkwood.
> Does USB work reliably?
Works for me on 2 devices (TS-219p / TS-219p+), since I
* basti [2021-01-08 19:31]:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976723
>
> I have no TS-209 for testing. At the moment it only work on kirkwood.
Does USB work reliably?
--
Martin Michlmayr
https://www.cyrius.com/
* Karsten Sperling [2020-12-16 12:06]:
> I've recently (attempted to) upgrade my TS-209 to buster and the
> issue that I ran into is not the size of the kernel but the size of
> the initrd, which on my system has blown out from just under 4MB to
> over 6 (with xz compression). The main culprits
* Karsten Sperling [2020-12-16 12:06]:
> I've recently (attempted to) upgrade my TS-209 to buster and the
> issue that I ran into is not the size of the kernel but the size of
> the initrd, which on my system has blown out from just under 4MB to
> over 6 (with xz compression). The main culprits
* Karsten Sperling [2020-12-16 12:06]:
> By pinning lvm to the stretch version I got the initrd to just below 5M, so
> it would fit into a combined RootFS1+RootFS2 partition. It looks like on
> the u-boot side I would just need to bump the initrd size from 0x3f
> to 0x4f in the cp command
I've recently (attempted to) upgrade my TS-209 to buster and the issue that
I ran into is not the size of the kernel but the size of the initrd, which
on my system has blown out from just under 4MB to over 6 (with xz
compression). The main culprits seem to be the lvm binary (1.6M in stretch,
2.6M
* basti [2020-12-06 23:02]:
> Sorry for any inconvenience to write is message to you.
> Can you please help to set the boot args to load usb in the uboot-config?
>
> fw_printenv show
> bootargs=console=ttyS0,115200 root=/dev/ram initrd=0xa0,0x90
> ramdisk=34816
> bootcmd=uart1 0x68;cp.l
# Kirkwood
* There were some reports that Wake-on-LAN (WOL) stopped working in
Debian 10 (buster). I'm not sure if it stopped working for
everyone or what the circumstances are. Nobody looked into it.
WOL work for me in buster and still in testing/bullseye on TS-219P+.
My installation is
Hello,
I get my TS-219 boot from USB with kernel 5.9.0-4-marvell.
setenv bootargs console=ttyS0,115200n8 root=/dev/ram rw
initrd=0xc0,0x150 ramdisk=34816
usb start
fatload usb 0:1 0xc0 initrd
fatload usb 0:1 0x80 kernel
bootm 0x80
root@qnap:/home/adminuser# cat /proc/cpuinfo
Hello, any news there?
I come from https://lists.debian.org/debian-arm/2020/11/msg00056.html
and read nearly the complete Topic.
I have the same Problem with my TS-219PII.
I would done some of the work, I administrate Linux/Debian for more them
13 years but have no skills with MTD or u-boot
* Martin Michlmayr [2020-11-26 17:23]:
> (Maybe I'm missing other problems. I haven't fully thought about it.)
Of course I missed something. ;-)
If the flash layout is changed in the kernel, you also need to change
the load addresses / size in u-boot. Our philosophy so far has been
not to
On Thu, Nov 26, 2020 at 11:33 AM Martin Michlmayr wrote:
>
> * 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.
> >
> >
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 QNAP specific,
* 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 QNAP specific, all kirkwood[*] based machines will be
>
On Thu, Nov 26, 2020 at 10:23 AM Martin Michlmayr wrote:
>
> > Possibly the three partitions could be combined into one partition
> > for kernel+initramfs
>
> When you say one partition, I guess you suggest appending the
> initramfs to the kernel? Is there a script that combines them?
> I
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
* Arnd Bergmann [2020-11-26 09:14]:
> partition@c {
> reg = <0x000c 0x0014>;
> label = "NAS Config";
> };
>
Paul Wise writes:
> On Fri, Nov 20, 2020 at 1:36 PM Arnd Bergmann wrote:
>
>> The main question for what would happen with the armel port
>> I think is what kernel to ship. When the marvell kernel gets
>> retired, the only kernel package left would be the raspberrypi
>> variant, and that is a
On Thu, Nov 26, 2020 at 4:34 AM Paul Wise wrote:
>
> On Fri, Nov 20, 2020 at 1:36 PM Arnd Bergmann wrote:
>
> > The main question for what would happen with the armel port
> > I think is what kernel to ship. When the marvell kernel gets
> > retired, the only kernel package left would be the
On Wed, Nov 25, 2020 at 1:56 PM wrote:
> other than open'n the door for folks what is involved in be'n a porter
Basically, take care of keeping the port useful for Debian users.
The following is advice for ports in general, I guess Adrian can
provide some info for armel in particular and the
On Fri, Nov 20, 2020 at 1:36 PM Arnd Bergmann wrote:
> The main question for what would happen with the armel port
> I think is what kernel to ship. When the marvell kernel gets
> retired, the only kernel package left would be the raspberrypi
> variant, and that is a bit silly given that it has
On Wed, 25 Nov 2020, Adrian Bunk wrote:
On Fri, Nov 20, 2020 at 02:20:12PM +0100, Arnd Bergmann wrote:
...
The main question for what would happen with the armel port
I think is what kernel to ship.
The main question is whether anyone in addition to me will sign up
as armel porter for
On Fri, Nov 20, 2020 at 02:20:12PM +0100, Arnd Bergmann wrote:
>...
> The main question for what would happen with the armel port
> I think is what kernel to ship.
The main question is whether anyone in addition to me will sign up
as armel porter for bullseye.
> When the marvell kernel gets
>
On Fri, Nov 20, 2020 at 5:54 AM Martin Michlmayr wrote:
> I wanted to capture the status of Debian on QNAP. These devices are
> slowly reaching end of life but there are still users.
It seems worth mentioning this on DevNews and or micronews:
https://wiki.debian.org/DeveloperNews
On Fri, Nov 20, 2020 at 1:36 PM Arnd Bergmann wrote:
> I would hope that the armel port can be kept as an official release
> for longer.
The DSA concerns about armel are the same for armhf, so either armel
will stay or armhf will also go. Of course if there are no porters for
armel (see the
I totally agree with Arnd. We have a bizillion boards based on iMX28,
iMX27 and S3c24xx and S3x64xx out there. And actually they are running
buster.
Please do not drop their support!
On 11/20/20 2:20 PM, Arnd Bergmann wrote:
On Fri, Nov 20, 2020 at 6:36 AM Martin Michlmayr wrote:
QNAP
On Fri, Nov 20, 2020 at 6:36 AM Martin Michlmayr wrote:
>
> 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.
>
> While I still get emails about Debian on QNAP, the
29 matches
Mail list logo
