Bug#1042070: System Information: inxi -b Output

[Hammad Rauf]

root@peace-homes:~# inxi -b
System:
  Host: peace-homes Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64 Console:
pty pts/1 Distro: Debian
GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: HP product: HP t630 Thin Client v: N/A serial:
MXL906219W
  Mobo: HP model: 8158 v: A01 serial: MXL906219W UEFI: AMI v: M40 v01.14
date: 01/04/2023
CPU:
  Info: quad core AMD Embedded G-Series GX-420GI Radeon R7E [MT MCP] speed
(MHz): avg: 900
min/max: 900/2000
Graphics:
  Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] driver: amdgpu v: kernel
  Display: x11 server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver:
X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu tty: 209x51
  API: OpenGL Message: GL data unavailable in console for root.
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver:
r8169
Drives:
  Local Storage: total: 465.76 GiB used: 52.21 GiB (11.2%)
Info:
  Processes: 243 Uptime: 6h 49m Memory: 6.73 GiB used: 1.71 GiB (25.5%)
Init: systemd
  target: graphical (5) Shell: Bash inxi: 3.3.26
root@peace-homes:~#

Bug#1042070: installation-reports: on apt-get update; apt-get upgrade; errors appear about firmware /lib/firmware/amdgpu/ip_discovery.bin

[rauf.hammad]

Package: installation-reports
Severity: important
X-Debbugs-Cc: rauf.ham...@gmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: debian-live-12.0.0-amd64-cinnamon.iso 
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/
Date: 

Machine: HP Thin Client t630, cpu: AMD GX-420GI (SOC), Integrated GPU Radeon 
R7E, 8GB RAM, USB Attached 500GB Boot HDD
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

On doing apt-get update; apt-get upgrade; warnings about missing firmware 
/lib/firmware/amdgpu/* appeared.

Excrept from console messages during: apt install <>; is given below:

run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-6.1.0-10-amd64 (--configure):
 installed linux-image-6.1.0-10-amd64 package post-installation script 
subprocess returned error exit status 1
Setting up python3-pycurl (7.45.2-3) ...
Setting up python3-pysimplesoap (1.16.2-5) ...
Setting up python3-debianbts (4.0.1) ...
dpkg: dependency problems prevent configuration of linux-image-amd64:
 linux-image-amd64 depends on linux-image-6.1.0-10-amd64 (= 6.1.37-1); however:
  Package linux-image-6.1.0-10-amd64 is not configured yet.

dpkg: error processing package linux-image-amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up python3-reportbug (12.0.0) ...
Setting up reportbug (12.0.0) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-10-amd64
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for module 
amdgpu
I: The initramfs will attempt to resume from /dev/sda3
I: (UUID=b497c0e6-7e96-4da8-acf4-e86d985eebdb)
I: Set the RESUME variable to override this.
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return 
code 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 linux-image-6.1.0-10-amd64
 linux-image-amd64
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@peace-homes:~#


-- Package-specific info:

Bug#684128: src:debian-installer: allow use of binary units in disk partitioner

[Thorsten Glaser]

Cyril Brulebois dixit:

>https://www.debian.org/devel/debian-installer/News/2023/20230516.en.html
>documents a fix for #913431, which is a duplicate of this bug report.

Huh.

>> In bookworm d-i, entering 512 MiB seems to be using something
>> entirely different
>
>“Something entirely different” compared to what?

I was a few metres across the room, but I heard something around
twohundred-something, which was definitely no power of two either.

>The second syntax is indeed invalid.

OK, it was only tried as last resort anyway.

>> This still makes d-i unsuitable for most partitioning.
>
>Feel free to use a different tool.

Oh, I personally do, but not everyone is I.

bye,
//mirabilos
-- 
22:20⎜ The crazy that persists in his craziness becomes a master
22:21⎜ And the distance between the craziness and geniality is
only measured by the success 18:35⎜ "Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent

Bug#1042059: installation-reports: success

[Axel Stammler]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: a...@users.sourceforge.net

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: network
Image version: 
https://www.debian.org/releases/bookworm/amd64/ch05s01.en.html#boot-initrd
Date: 

Machine: Lenovo Think Pad X 230
Partitions: 
Filesystem Type 1K-blocks  Used Available Use% Mounted on
udev   devtmpfs   3878408 0   3878408   0% /dev
tmpfs  tmpfs   782380  1644780736   1% /run
/dev/sdd1  ext4   2808488127452   2518220   5% /
/dev/sdd6  ext4  19047080   4867716  13186496  27% /usr
tmpfs  tmpfs  3911880 0   3911880   0% /dev/shm
tmpfs  tmpfs 5120 8  5112   1% /run/lock
/dev/sdd5  ext4   1307744   228   1222832   1% /tmp
/dev/sdd9  ext4978972141860770040  16% /home
/dev/sdd7  ext4   4720160762808   3696900  18% /var
tmpfs  tmpfs   782376   148782228   1% /run/user/1001

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O] SD card
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems: boots & works correctly & very fast (on different machines, 
too), probably due to better firmware




Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/installer.) Please compress large files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230607"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux bookworm-sd 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.1.27-1 (2023-05-08) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core 
processor DRAM Controller [8086:0154] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen 
Core processor Graphics Controller [8086:0166] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 
Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 7 
Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 
Series Chipset Family KT Controller [8086:1e3d] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM 
Gigabit Network Connection (Lewisville) [8086:1502] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21f3]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel modules: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 
Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 
Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset 
Family PCI Express Root Port 1 [8086:1e10] (rev c4)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series 
Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
lspci -knn: Subsystem: Lenovo Device [17aa:21fa]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series 
Chipset Family PCI Express Root Port 3 [8086:1e14] (rev c4)
lspci -knn: Subsystem: Lenovo 

Processed: Re: Bug#684128: src:debian-installer: allow use of binary units in disk partitioner

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 226
Bug #684128 [partman-base] src:debian-installer: allow use of binary units in 
disk partitioner
No longer marked as found in versions partman-base/226.
> close -1 225
Bug #684128 [partman-base] src:debian-installer: allow use of binary units in 
disk partitioner
Marked as fixed in versions partman-base/225.
Bug #684128 [partman-base] src:debian-installer: allow use of binary units in 
disk partitioner
Marked Bug as done

-- 
684128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#684128: src:debian-installer: allow use of binary units in disk partitioner

[Cyril Brulebois]

Control: notfound -1 226
Control: close -1 225

Hi,

Thorsten Glaser  (2023-07-25):
> why is this bug still unfixed?

https://www.debian.org/devel/debian-installer/News/2023/20230516.en.html
documents a fix for #913431, which is a duplicate of this bug report.

Closing this one accordingly.

> In bookworm d-i, entering 512 MiB seems to be using something
> entirely different, and 512 Mi gives an error “invalid size”.

“Something entirely different” compared to what?

The second syntax is indeed invalid.

> This still makes d-i unsuitable for most partitioning.

Feel free to use a different tool.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: Re: src:debian-installer: allow use of binary units in disk partitioner

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 684128 226
Bug #684128 [partman-base] src:debian-installer: allow use of binary units in 
disk partitioner
Marked as found in versions partman-base/226.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
684128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#684128: src:debian-installer: allow use of binary units in disk partitioner

[Thorsten Glaser]

found 684128 226
thanks

Hi,

why is this bug still unfixed?

In bookworm d-i, entering 512 MiB seems to be using something
entirely different, and 512 Mi gives an error “invalid size”.

This still makes d-i unsuitable for most partitioning.

bye,
//mirabilos
-- 
[...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but
what about xfs, and if only i had waited until reiser4 was ready... in the be-
ginning, there was ffs, and in the middle, there was ffs, and at the end, there
was still ffs, and the sys admins knew it was good. :)  -- Ted Unangst über *fs

Bug#857132: console-setup (again) stopped to apply font at startup

[Pedro Dias]

Hi,

I have had this font loading problem with all versions of Debian since
version 9. I have seen the font selected in '/etc/default/console-setup'
be loaded on a very few system boots when using a normal kernel, but never
when using a PREEMPT_RT kernel [in real hardware, not VMs]. I have also
confirmed that whenever the plymouth package is installed and the system
is configured to boot with the graphical boot splash, the selected font
can not be loaded while the splash is visible, but can be loaded if the
splash is hidden for a small period of time (just enough for setfont to
work it's magic).

In my humble opinion, there are two main reasons that cause the font
loading problem:

1) The rules implemented in file '/lib/udev/rules.d/90-console-setup.rules'
   violate one of the udev conditions for the RUN assignment option as
   expressed in the udev manpage:

   --- content of file '/lib/udev/rules.d/90-console-setup.rules' ---
   ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*",
RUN+="/etc/console-setup/cached_setup_font.sh"
   ACTION=="add", SUBSYSTEM=="vc", KERNEL=="vcs[1-9]|vcs[1-9][0-9]",
TEST=="/run/console-setup/font-loaded",
RUN+="/etc/console-setup/cached_setup_terminal.sh %k"
   --- end of content ---

   --- extract from the udev manpage (Debian 9) ---
   (...)
   RUN{type}
   (...)
   This can only be used for very short-running foreground tasks.
   (...)
   Starting daemons or other long-running processes is not appropriate for udev;
   the forked processes, detached or not, will be unconditionally killed
   (...)
   --- end of extract ---

   --- extract from udev manpage (Debian 12) ---
   (...)
   RUN{type}
   (...)
   This can only be used for very short-running foreground tasks.
   (...)
   Starting daemons or other long-running processes is not allowed; the forked
   processes, detached or not, will be unconditionally killed
   (...)
   In order to activate long-running processes from udev rules,
provide a service unit
   (...)
   --- end of extract ---

   The usual solution for this is to create a systemd service to run
   the script.

2) The script that loads the font is started at inconvenient times, like
   when the plymouth daemon is showing the graphical boot splash. This
   can only be resolved with a dependency based solution like systemd
   provides, which would only load the font after the plymouth daemon
   finished (meaning after 'plymouth-quit-wait.service') and before the
   first instance of getty started (meaning before 'getty@tty1.service'
   started and 'getty.target' is reached). Such solution would not,
   however, be appropriate for people that have encrypted volumes,
   because the prompt for the encryption password is displayed early in
   the boot process, in the initramfs stage.


To attempt to solve these problems, I recently developed a solution based
on two initramfs-tools scripts, which I attached to this e-mail:


   - File 'etc-initramfs_tools-hooks-font.sh' contains the script to be
 executed in the hooks stage of the initramfs-tools, when doing an
 'update-initramfs';

   - File 'etc-initramfs_tools-scripts-font.sh' contains the script to
 be executed in the scripts stage of the initramfs image, when the
 system is booting.

==
Follow the steps below to install the scripts:
==

0) Download the scripts to a temp directory you have created. Lets assume
   it is '/tmp/scripts'. Make sure that the preferred font has been selected
   in file '/etc/default/console-setup'. For this example, lets assume
   it is the Terminus Bold 20x10 font. In this case, the contents of
   the file '/etc/default/console-setup' should look like:

   --- contents of file '/etc/default/console-setup' ---
   ACTIVE_CONSOLES="/dev/tty[1-6]"
   CHARMAP="UTF-8"
   CODESET="Lat15"
   FONTFACE="TerminusBold"
   FONTSIZE="20x10"
   VIDEOMODE=
   --- end of file contents ---

   IMPORTANT: Before changing the initramfs image that is used to boot
   the system, make sure you have an alternative way of booting the
   system, like a Debian Live CD/DVD or USB pen drive, or another
   kernel installed in the system.

1) Install first file 'etc-initramfs_tools-hooks-font.sh' to the 'hooks'
   directory of initramfs-tools:
$ sudo cp etc-initramfs_tools-hooks-font.sh /etc/initramfs-tools/hooks/font
$ sudo chmod 755 /etc/initramfs-tools/hooks/font

2) Install the second file 'etc-initramfs_tools-scripts-font.sh' to the
   'scripts/init-top' directory of initramfs-tools:
$ sudo cp etc-initramfs_tools-scripts-font.sh
/etc/initramfs-tools/scripts/init-top/font
$ sudo chmod 755 /etc/initramfs-tools/scripts/init-top/font

3) Update the initramfs image for your currently booted kernel:
$ sudo update-initramfs -u -k $(uname -r)

   --- example output 

Re: 11.8/12.2 planning

[Donald Norwood]

On 7/24/23 14:25, Jonathan Wiltshire wrote:

I think I confused matters with my messy thread; let's start again.

I originally suggested:

Jonathan Wiltshire  (2023-06-28):

The proper cadence for 11.8 and 12.2 is the weekend of 30th September
2023. Please indicate your availability for:

23 Sep
30 Sep (preferred)
7 Oct


Let's say 30 Sep is still preferred, 7th Oct or at a stretch 14th Oct are
options. Please indicate your availability for those three.

Thanks,



Publicity/Press:

23 Sep
7 Oct
14 Oct


Be well,

-Donald

--
-
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Donald Norwood
⢿⡄⠘⠷⠚⠋⠀ B7A1 5F45 5B28 7F38 4174
⠈⠳⣄ D5E9 E5EC 4AC9 BD62 7B05


OpenPGP_signature
Description: OpenPGP digital signature