Package: initramfs-tools
Version: 0.140
Severity: normal
X-Debbugs-Cc: peter.na...@kit.edu
Dear Maintainer,
when using uboot ... update-initramfs triggers flash-kernel to _always_
write latest kernel version into flash-memory.
Even if this might be helpful in many cases ... there are situations
I also tried a newer kernel version e.g.
* 5.19.0-0.deb11.2-marvell
* 6.0.0-0.deb11.6-marvell
which does not solve the problem - kernel Warning during boot is still
there.
I found that the kernel warning disappears when I prevent the modules
*xhci_pci* and *xhci_hcd* from being loaded during boot.
Package: src:linux
Version: 5.10.162-1
Severity: normal
Dear Maintainer,
after installtion of Debian bullsey on QNAP TS-420U the server is
booting with a strange warning:
WARNING: CPU: 0 PID: 230 at include/linux/msi.h:219 (see output of
dmesg below).
It looks like the system is runnin
The problem doesn't show up when I use another USB-Stick.
So it looks like the problem is solved.
Package: installation-reports
Boot method: USB stick
Image version:
https://cdimage.debian.org/cdimage/bookworm_di_alpha1/amd64/iso-cd/debian-bookworm-DI-alpha1-amd64-netinst.iso
Date: 03.11.2022
Machine: Standard PC
Processor: Core i7-11700 @ 2.50 GHz
Memory: 64 GB
Partitions:
/sda: 931.5 GiB
Package: request-tracker4
Version: 4.4.3-2
Severity: normal
Dear Maintainer,
When installing request-tracker4 (mariadb-server and rt4-db-mysql are already
installed)
I see (during installation) the following output:
...
populating database via scriptfile... Working with:
Type:m
process starts.
However, it looks like that the message (shown above) is missing for the
QNAP (armel) installation.
On 24.02.2016 21:12, Martin Michlmayr wrote:
* Peter Nagel [2016-02-24 13:47]:
The debian installer (within expert mode) does not ask for the (new)
hostname but just takes th
Package: debian-installer
Boot method: network
Image version: debian-installer_20150422+deb8u3_armel.deb
Date: January 18, 2016
Machine: QNAP TS-420U
Processor: Marvell 1.6 GHz
Memory: 1GB DDR3
Severity: normal
Partitions:
Filesystem Type 1K-blocks Used Available Use% Mounted on
When all disks are available during boot the system is starting without
problems:
> ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Jul 13 18:15
2138f67e-7b9e-4960-80d3-2ac2ce31d882 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Jul 13 18:15
21a660eb-729d-48fe-b9e3-140ae0ee7
... I have the same problem on an ARM system (QNAP TS-420U) where the
root-partition is installed on GPT-RAID1 (3 active disks and one spare)
and started via uboot from flash memory.
(see installation-report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791794)
smime.p7s
Description: S/
Am 11.07.2015 18:40, schrieb Philip Hands:
... which is what suggests to me that it's been broken by other
means -- the fact that one can apparently start it by hand tells you
that it's basically working, so I'd think the described symptoms point
strongly towards duff mdadm.conf in the initramfs
Package: installation-reports
Boot method: network
Image version:
http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/network-console/qnap/ts-41x/
Date: June 7, 2015
Machine: QNAP TS-420U
Processor: Marvell 1.6 GHz
Memory: 1GB DDR3
Partitions:
Filesyste
Package: installation-reports
Boot method: network
Image version:
http://ftp.debian.org/debian/dists/Debian7.8/main/installer-armel/current/images/kirkwood/network-console/qnap/ts-41x/
Date: June 7, 2015
Machine: QNAP TS-420U
Processor: Marvell 1.6 GHz
Memory:1GB DDR3
Partitions:
File
14 matches
Mail list logo
