Much valued debian people!
iam trying with an debian installation@qnap ts-109...
I already had a running jessie installation, but the
dist moved to archived and therefore the possibility to
run this working setting is past hence, or gone.
Now... I retried with the currently stretch installer,
and the routine is running proper, but without leaving
a bootable uboot setting to myself@ nonvolatile ram
The installer rejected the uuid for the root device
within /var/log/syslog, but i fixed it and then
not anymore an error message. Kernel and initrd got flashed
to device like the installer told me...
Resetting the qnap ends in the uboot loader screen
(through serial tty). At within the uboot shell i realized
debian bootcmd arguments were not set-up.
Searching pages was not effective at all. Maybe someone
can give me a hard or softlink to some good documentation,
or code examples... OR still has an answer to my
problem.
- thx and sincerely
kefko
Any reason for installing Stretch?
In case you want to try with something more recent, Buster is the latest Debian to support these QNAP.
Bullseye is also possible (although not officially supported) but
only as upgrade from Buster and after some manual fiddling (see
* Domenico Andreoli <cavok@debian.org> [2022-01-23 11:45]:
Any reason for installing Stretch?
In case you want to try with something more recent, Buster is the latest Debian to support these QNAP.
The installer isn't available for buster on Orion devices (only
Kirkwood); stretch is the latest.
Bullseye is also possible (although not officially supported) but
only as upgrade from Buster and after some manual fiddling (see
The manual fiddling only works on Kirkwood, not Orion. With the Kirkwood-devices, there's enough MTD flash (the problem is the
partition layout). The Orion-based devices only have 8 MB flash,
which isn't enough.
The manual fiddling only works on Kirkwood, not Orion. With the Kirkwood-devices, there's enough MTD flash (the problem is the
partition layout). The Orion-based devices only have 8 MB flash,
which isn't enough.
If I read this paragraph correctly, the implication is that the flash device partitioning can be changed to accommodate the larger kernels. Presumably from uboot....
Are there any instructions, guides or other documentation for how to get it done?
* Philippe Clérié <philippe@gcal.net> [2022-02-10 17:45]:
If I read this paragraph correctly, the implication is that the flash device >> partitioning can be changed to accommodate the larger kernels. Presumably...
from uboot.
Are there any instructions, guides or other documentation for how to get it >> done?
Arnaud Mouiche, who created a script that re-configures the partition layout on QNAP, also wrote excellent documentation about the whole thing:
https://github.com/amouiche/qnap_mtd_resize_for_bullseye
The summary is that you can pass "mtdparts" as a kernel parameter to
set the partition layout.
I think *armel* may get another few
years reprieve since Debian based its Pi OS on *armel* instead of *armhf*.
(A rather surprising decision!)
On Jo, 10 feb 22, 17:45:27, Philippe Clérié wrote:
I think *armel* may get another few
years reprieve since Debian based its Pi OS on *armel* instead of *armhf*. >> (A rather surprising decision!)
Might there be some confusion here?
Debian doesn't have a "Pi OS" and it was rather unfortunate the first Raspberry Pi was launched *after* the baseline for Debian's armhf was
already decided. The only pure Debian that would work on the Raspberry
Pi was armel.
That is why Raspbian (the predecessor of Raspberry Pi OS from the
Raspberry Pi Foundation) was born, it was basically Debian's armhf
recompiled for the first Raspberry Pi.
You can follow the state of Debian architectures at https://release.debian.org/bookworm/arch_qualify.html.
At the moment it looks good for bookworm, though it's still early in the release cycle and even so, support for specific hardware might be
dropped for independent reasons.
Kind regards,
Andrei
My apologies for the confusion. *Pi OS* here was meant as a shortcut for
the *official* distribution of Debian for the Raspberry Pi. Which I am
using by the way.
My apologies for the confusion. *Pi OS* here was meant as a shortcut for the *official* distribution of Debian for the Raspberry Pi. Which I am using by the way.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 343 |
Nodes: | 16 (3 / 13) |
Uptime: | 30:42:39 |
Calls: | 7,557 |
Calls today: | 1 |
Files: | 12,733 |
Messages: | 5,655,647 |