Request for weblate usage in d-i Japanese translation
Dear d-i l10n coordinator, I am trying to update ja translation for d-i, while the previous translator kmuto is no longer active. He used to commit all the ja translation things from himself and other translators. Instead I would like to use weblate for possible reviews. So I request for d-i weblate to enable Japanese: https://hosted.weblate.org/projects/debian-installer/#languages Thanks in advance, -- YOSHINO Yoshihito
Re: [AMD/ATI graphics] Missing firmware not declared / kernel modules not included in initrd
Holger Wansing 于2021年4月25日周日 上午5:27写道： > > Hi, > > Holger Wansing wrote (Sat, 24 Apr 2021 21:59:44 +0200): > > Hi, > > > > Lucas Nussbaum wrote (Sat, 24 Apr 2021 16:44:58 +0200): > > > Would you be in a position to check a debian 10 install on the same > > > hardware, and fetch the dmesg output and /var/log/Xorg.0.log after > > > installation, as well as the list of installed packages (to understand > > > if firmware packages were installed somehow)? > > > > Yes. > > > > > And then maybe do the same with the bullseye RC1 image? > > > > > > Also can you confirm that just switching to another console and > > > installing the firmware package there was enough to fix the issue? > > > > > > I don't understand whether this is a regression from Debian 10 or not. > > > For example, > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931436 > > > was about the RC2 for the buster installer. > > > > I'm just installing Buster on that machine. > > Will collect data after that, and try Bullseye next. > > Results: > > Installing Buster (with GNOME DE) lead to a system failing to start X, > system hangs on the console, latest entry is "Starting GNOME Display Manager". > The needed firmware package (firmware-amd-graphics) was NOT installed. > Installing it makes GNOME UI start fine. > > Installation of Bullseye was basically the same (installation completed > successfully, amd firmware package was NOT installed). > The difference: there was a small delay while starting up (~ 10 sec.), but > after that X and GNOME were starting fine. > > So, on this hardware and with 'radeon' kernel module, everything would be > fine for Bullseye. No need for further action. > (I can deliver installation logs or whatever information, if needed, feel > free to ask.) > However, it's somewhat older hardware with 'radeon' module. > Thus it does not stand for the "amdgpu firmware problem", I fear. > For us (mips port), it is a long history of problem. The problem is that: the older version of GNOME, or Mate, can work with vesa driver, while current GNOME cannot. Without amd/ati non-free firmware, radeon/amdgpu cannot work at all. So on mips platform with AMDGPU (aka, Loongson-3), it has nothing on display at all, even console. The reason is that there are no vesa driver on MIPS. > > Holger > > > > -- > Holger Wansing > PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 > -- YunQiang Su
Bug#987449: [rc-1 graphical d-i] graphical installer hangs at language chooser step for several languages
Hello, * Holger Wansing [210424 21:42]: > While trying to debug another problem yesterday, I found that the RC1 > graphical > installer fails to go forward, when selecting one of these languages: > - Kannada > - Marathi > - Persian > - Sinhala I spent a few hours today on this issue, but did not get very far. Not totally unexpected if you know nothing about the installer. I have, however, a perf top output to share. I believe this more or less means the font rendering (pango, fontconfig) is stuck somehow? Good luck, Chris Samples: 82K of event 'cpu-clock:pppH', 4000 Hz, Event count (approx.): 4370334125 lost: 0/0 drop: 0/0 Overhead Shared ObjectSymbol 5.29% /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.4600.2 0x13010 d [.] pango_default_break 1.44% /lib/libharfbuzz.so.0.20704.00x769b0 ! [.] 0x000769b0 1.17% /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.80x8487e B [.] g_utf8_get_char 1.05% /lib/libharfbuzz.so.0.20704.00x57448 ! [.] 0x00057448 1.04% /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.4600.2 0x1fff2 d [.] 0x0001fff2 1.02% /lib/libharfbuzz.so.0.20704.00x8eff5 ! [.] 0x0008eff5 0.88% /lib/libharfbuzz.so.0.20704.00x611d0 ! [.] 0x000611d0 0.83% /lib/libharfbuzz.so.0.20704.00x5741e ! [.] 0x0005741e 0.81% /lib/x86_64-linux-gnu/libc-2.31.so 0x88bbd D [.] _int_malloc 0.80% /lib/libharfbuzz.so.0.20704.00x5a9f7 ! [.] 0x0005a9f7 0.79% /lib/libharfbuzz.so.0.20704.00x573d9 ! [.] 0x000573d9 0.71% /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.80x3edd8 B [.] g_hash_table_lookup 0.70% /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.4600.2 0xf5a0 d [.] g_utf8_get_char@plt 0.68% /lib/libharfbuzz.so.0.20704.00x573ee ! [.] 0x000573ee 0.60% /lib/libharfbuzz.so.0.20704.00x5a830 ! [.] 0x0005a830 0.57% /lib/libharfbuzz.so.0.20704.00x71730 ! [.] 0x00071730 0.57% /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.80x70590 B [.] g_slice_free1 0.56% /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.330x1e7883 d [.] gtk_text_layout_get_line_display 0.55% /lib/libharfbuzz.so.0.20704.00x6a190 ! [.] 0x0006a190 0.52% /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0.4600.2 0x34977 d [.] pango_shape_with_flags 0.51% /lib/libharfbuzz.so.0.20704.00xc210 ! [.] 0xc210 0.51% /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6600.8 0x18fff B [.] g_object_unref 0.46% /lib/libharfbuzz.so.0.20704.00x578b2 ! [.] 0x000578b2 0.44% /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.80x6ff70 B [.] g_slice_alloc 0.43% /lib/x86_64-linux-gnu/libc-2.31.so 0x86b1d D [.] _int_free 0.41% /lib/libharfbuzz.so.0.20704.00x5a8a4 ! [.] 0x0005a8a4 0.40% /lib/libharfbuzz.so.0.20704.00x612b0 ! [.] 0x000612b0 0.39% /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6600.8 0x2bbe8 B [.] g_signal_emit_valist 0.39% /lib/libharfbuzz.so.0.20704.00x717e0 ! [.] 0x000717e0 0.39% /lib/libharfbuzz.so.0.20704.00x5a86b ! [.] 0x0005a86b 0.38% /lib/x86_64-linux-gnu/libc-2.31.so 0x95760 D [.] __strcmp_sse2 0.38% /lib/libharfbuzz.so.0.20704.00x612d2 ! [.] 0x00061
Re: [AMD/ATI graphics] Missing firmware not declared / kernel modules not included in initrd
Hi, Holger Wansing wrote (Sat, 24 Apr 2021 21:59:44 +0200): > Hi, > > Lucas Nussbaum wrote (Sat, 24 Apr 2021 16:44:58 +0200): > > Would you be in a position to check a debian 10 install on the same > > hardware, and fetch the dmesg output and /var/log/Xorg.0.log after > > installation, as well as the list of installed packages (to understand > > if firmware packages were installed somehow)? > > Yes. > > > And then maybe do the same with the bullseye RC1 image? > > > > Also can you confirm that just switching to another console and > > installing the firmware package there was enough to fix the issue? > > > > I don't understand whether this is a regression from Debian 10 or not. > > For example, > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931436 > > was about the RC2 for the buster installer. > > I'm just installing Buster on that machine. > Will collect data after that, and try Bullseye next. Results: Installing Buster (with GNOME DE) lead to a system failing to start X, system hangs on the console, latest entry is "Starting GNOME Display Manager". The needed firmware package (firmware-amd-graphics) was NOT installed. Installing it makes GNOME UI start fine. Installation of Bullseye was basically the same (installation completed successfully, amd firmware package was NOT installed). The difference: there was a small delay while starting up (~ 10 sec.), but after that X and GNOME were starting fine. So, on this hardware and with 'radeon' kernel module, everything would be fine for Bullseye. No need for further action. (I can deliver installation logs or whatever information, if needed, feel free to ask.) However, it's somewhat older hardware with 'radeon' module. Thus it does not stand for the "amdgpu firmware problem", I fear. Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Processed: Re: Bug#987503: swap partition only 1 GB instead of at least 1 x RAM size
Processing control commands: > severity -1 wishlist Bug #987503 [debian-installer] swap partition only 1 GB instead of at least 1 x RAM size Severity set to 'wishlist' from 'important' -- 987503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987503: swap partition only 1 GB instead of at least 1 x RAM size
Control: severity -1 wishlist Hi Martin! On Sat, Apr 24, 2021 at 04:14:16PM -0400, Martin wrote: >Package: debian-installer >Version: bullseye-rc1 >Severity: important >Tags: d-i > >I installed using the graphical UI and selected automatic >partitioning with encrypted LVM, with all files in '/'. >RAM size is 16 GB, SSD has 1 TB. > >To be able to hibernate the system, a swap partition of at least >1 x RAM size is necessary. d-i did this correctly since many >releases, but in bullseye it is broken at the moment. > >Please restore the correct formula, thank you! (Or even allow >users to chose a swap size for the auto-partioner (e.g. if a >users already plans to upgrade the RAM, see #780208). There is no such thing as a "correct" formula, though. The old formula was similarly causing lots of hassle for people installing on servers who didn't want to waste hundreds of gigabytes on swap space. We could probably do with an "is this a server or a desktop" up-front, but we don't have that yet. -- Steve McIntyre, Cambridge, UK.st...@einval.com Mature Sporty Personal More Innovation More Adult A Man in Dandism Powered Midship Specialty
Bug#987503: swap partition only 1 GB instead of at least 1 x RAM size
Package: debian-installer Version: bullseye-rc1 Severity: important Tags: d-i I installed using the graphical UI and selected automatic partitioning with encrypted LVM, with all files in '/'. RAM size is 16 GB, SSD has 1 TB. To be able to hibernate the system, a swap partition of at least 1 x RAM size is necessary. d-i did this correctly since many releases, but in bullseye it is broken at the moment. Please restore the correct formula, thank you! (Or even allow users to chose a swap size for the auto-partioner (e.g. if a users already plans to upgrade the RAM, see #780208).
Re: [AMD/ATI graphics] Missing firmware not declared / kernel modules not included in initrd
Hi, Lucas Nussbaum wrote (Sat, 24 Apr 2021 16:44:58 +0200): > Would you be in a position to check a debian 10 install on the same > hardware, and fetch the dmesg output and /var/log/Xorg.0.log after > installation, as well as the list of installed packages (to understand > if firmware packages were installed somehow)? Yes. > And then maybe do the same with the bullseye RC1 image? > > Also can you confirm that just switching to another console and > installing the firmware package there was enough to fix the issue? > > I don't understand whether this is a regression from Debian 10 or not. > For example, > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931436 > was about the RC2 for the buster installer. I'm just installing Buster on that machine. Will collect data after that, and try Bullseye next. Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#987377: rescue-mode: when in graphical mode, locks up one prompt before the shell
Cyril Brulebois, on 2021-04-24 07:22:57 +0200: > FWIW: I plan to debug (likely starting by bisecting) this somewhen > during the week-end or next week. Hi Cyril, if that helps, I tried to reproduce the bug on real hardware and virtual machine. The virtual machine was within Qemu, version available in Sid. The real hardware is an HP Zbook 15 G6, involving an uneven pair of NVMe SSD drives, 1T and 512G respectively. Here are my observations so far: * in any case the rescue mode works when run from within the environment of the USB thumb; * Qemu Bios: the blank page appears and the GUI is stuck; * Qemu EFI: the blank page appears and the GUI is stuck; * Zbook EFI: the intro page appears properly and I can get to the shell using the installed system root; * I never managed to Bios boot any USB thumb on the Zbook, so couldn't test that configuration unfortunately. I'm not sure whether the use of NVMes affects some branching in scripts, or if this is due to a completely unrelated and different hardware parameter; but I thought it would be worth mentioning. Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/3, please excuse my verbosity. signature.asc Description: PGP signature
Bug#987492: installation-reports: Successful upgrade of Bullseye from Buster
Package: installation-reports Severity: normal (Please provide enough information to help the Debian maintainers evaluate the report efficiently - e.g., by filling in the sections below.) Boot method: Upgrade from buster Image version: Date: Machine: Thinkpad T470 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: Upgrade from Buster -> Bullseye - all successful with no particular problems. Used apt-get to do the upgrade and apt-get autoremove after reboot. Please make sure that any installation logs that you think would be useful are attached to this report. Please compress large files using gzip. -- Package-specific info: == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u4" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux T470 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:1904] (rev 08) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: Kernel modules: xhci_pci lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation Device [8086:9d3d] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: Kernel driver in use: serial lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9d10] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.6 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #7 [8086:9d16] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 [8086:9d18] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.2 PCI bridge [0604]: Intel Corporation Device [8086:9d1a] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-LP LPC Controller [8086:9d48] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d70] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection I219-LM [8086:156f] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: Kernel driver in use: e1000e lspci -knn: Kernel modules: e1000e lspci -knn: 04:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) lspci -knn: Subsystem: Intel Corporation Device [8086:0010] lspci -knn: Kernel driver in use: iwlwifi lspci -knn: Kernel modules: iwlwifi lspci -knn: 3e:00.0 Non-Volatile memory controller [0108]: Lenovo Device [17aa:0003] lspci -knn: Subsystem: Lenovo Device [17aa:1003] lspci -knn: Kernel driver in use: nvme lspci -knn: Kernel modules: nvme usb-list: usb-list: Bus 01 Device 01: xHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01 usb-list:Manufacturer: Linux 4.19.0-9-amd64 xhci-hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub u
Bug#987491: installation-reports: Successful install AMD A6 - nonfree AMD Radeon firmware needed
Package: installation-reports Severity: normal (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: https://cdimage.debian.org/cdimage/bullseye_di_rc1/amd64/iso-cd/debian-bullseye-DI-rc1-amd64-netinst.iso Date: Machine: Zoostorm MSI Motherboard AMD A6-3670 APU 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: Requires non-free Radeon drivers for r600 - firmware-amd-graphics Please make sure that any installation logs that you think would be useful are attached to this report. Please compress large files using gzip. -- Package-specific info: == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u4" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux T470 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:1904] (rev 08) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: Kernel modules: xhci_pci lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation Device [8086:9d3d] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: Kernel driver in use: serial lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9d10] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.6 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #7 [8086:9d16] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 [8086:9d18] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.2 PCI bridge [0604]: Intel Corporation Device [8086:9d1a] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-LP LPC Controller [8086:9d48] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d70] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection I219-LM [8086:156f] (rev 21) lspci -knn: Subsystem: Lenovo Device [17aa:2245] lspci -knn: Kernel driver in use: e1000e lspci -knn: Kernel modules: e1000e lspci -knn: 04:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) lspci -knn: Subsystem: Intel Corporation Device [8086:0010] lspci -knn: Kernel driver in use: iwlwifi lspci -knn: Kernel modules: iwlwifi lspci -knn: 3e:00.0 Non-Volatile memory controller [0108]: Lenovo Device [17aa:0003] lspci -knn: Subsystem: Lenovo Device [17aa:1003] lspci -knn: Kernel driver in use: nvme lspci -knn: Kernel modules: nvme usb-list: usb-list: Bus 01 Device 01: xHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01 usb-list:Manufacturer: Linux 4.19.0-9-amd64 xhci-hcd usb-list:Interface 00: Class 09(hub )
Bug#987449: debian-installer: #987449 seems likely to share the cause with #987377
Package: debian-installer Followup-For: Bug #987449 Dear Maintainer, Having tested this with both the alpha2 and alpha3 netinst ISOs, I find that the bug does not exist in alpha2 and does exist in alpha3, which is the same as #987377. Also, the lock-up points are visually similar, and in both cases some process makes the CPU very busy, so I would guess they are actually both symptoms of the same bug. BTW Since the behaviour in _this_ bug is apparent within a few keystrokes of starting d-i, this is the better one to use for testing. Cheers, Phil.
Re: [AMD/ATI graphics] Missing firmware not declared / kernel modules not included in initrd
Hi Holger, On 04/12/20 at 22:08 +0100, Holger Wansing wrote: > Hi all, > > after a test installation on an IBM thinkpad with radeon RV515/M52 graphics, > I ended up with a "broken" system (Gnome login screen was not shown, instead > there was the "boot-up screen" showing the starting services like > > [ OK ] Started User Login Management. > [ OK ] Started Bluetooth service. > ... > [ OK ] Started Network Manager. > ... > [ OK ] Started Accounts Service. > ... > [ OK ] Reached target sound card. >Starting GNOME Display Manager ... > > and somewhere at that point it hangs. > No login possible from there! > > > Problem was the missing firmware for the Radeon graphics card (package > "firmware-amd-graphics"), similar to several other bugreports we had here in > the > past: Would you be in a position to check a debian 10 install on the same hardware, and fetch the dmesg output and /var/log/Xorg.0.log after installation, as well as the list of installed packages (to understand if firmware packages were installed somehow)? And then maybe do the same with the bullseye RC1 image? Also can you confirm that just switching to another console and installing the firmware package there was enough to fix the issue? I don't understand whether this is a regression from Debian 10 or not. For example, > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931436 was about the RC2 for the buster installer. Thanks Lucas
Bug#987441: debian-installer: D-I must get ready for Bullseye
Hi, Cyril Brulebois wrote (Fri, 23 Apr 2021 22:57:40 +0200): > Let's keep track of things that need to be looked at before D-I is > considered ready for the initial Bullseye release (11.0). > > Carried over from D-I Bullseye RC 1 errata: > - amdgpu firmware > - broken rescue mode Maybe add #987449: [rc-1 graphical d-i] graphical installer hangs at language chooser step for several languages here? Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#987449: [rc-1 graphical d-i] graphical installer hangs at language chooser step for several languages
Package: debian-installer Version: bullseye-rc1 Severity: grave While trying to debug another problem yesterday, I found that the RC1 graphical installer fails to go forward, when selecting one of these languages: - Kannada - Marathi - Persian - Sinhala (tested with rc1-netinst and -netboot image, on an amd64 qemu machine with 1G RAM) Installer hangs, with only displaying a headline and nothing more, eating up all CPU time. Interestingly, yesterday's daily does not have this problem, while RC1 has!!! And sadly it has not been discovered, that alpha3 is also affected, while alpha2 is fine! Yet another problem which started to appear with alpha3, just like "Bug#987377: rescue-mode: when in graphical mode, locks up one prompt before the shell" !!! The commit https://salsa.debian.org/installer-team/debian-installer/-/commit/95fdc73ca8cde8d7a360fd3d742fc947a045ec0f "Drop fontconfig tweaks introduced in version 20170828 (See: #873462)" comes to my mind, also included in alpha3 ... ??? The text installer seems to be not affected (well, only Persian from the langs above is available in text installer, and Persian works there). We already have "Bug#983897: installation-reports: Installation in Uyghur hangs" where the installer hangs at some later steps - noticed for Uyghur and Kannada so far... Uyghur is however not affected by this language chooser fail bug. As already mentioned by Samuel, this may be another resurgence - in a tightened form - of "#929877: installation-reports: Buster installer hangs at hard disk step with arabic language" from 2019, where the real reason has not been found... -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Re: Tentative summary of the AMD/ATI/NVidia issue
Lucas Nussbaum writes: > It looks like the three open paths for resolution are: > > A) understand and restore the behaviour from Debian 10, that is, get X > to work in a degraded mode after installation. How it worked with Debian > 10 (and why it doesn't with Debian 11) is unknown. > > B) In the installer, detect that firmware-amd-graphics or > firmware-misc-nonfree should be installed, and either install it (?), > or redirect the user to the unofficial installer that includes them. > > C) Do nothing and document this in the release notes There is at least also D) Install (non-free) firmware and include it in official install media. I don't think degraded operation (just vesa, no sound, no wifi, known issues in microcode, ...) will continue to be an attractive option. So maybe we should revisit whether we should just include firmware; I wanted to suggest so at least for Bookworm. Ansgar
Bug#987441: debian-installer: D-I must get ready for Bullseye
On Fri, Apr 23, 2021 at 11:16:45PM +0200, Cyril Brulebois wrote: > Cyril Brulebois (2021-04-23): > > Carried over from D-I Bullseye RC 1 errata: > > - amdgpu firmware > There's no “umbrella bug report” for it at the moment, but here's a > thread and pointers to various bug reports: > https://lists.debian.org/debian-boot/2020/12/msg00026.html https://lists.debian.org/debian-release/2021/04/msg00646.html is a tentative summary of that AMD/ATI/NVidia issue by Lucas Nussbaum. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ „If you don't like vaccination, try the disease.“ (Herwig Kollaritsch) signature.asc Description: PGP signature
Tentative summary of the AMD/ATI/NVidia issue (was: Finding a tentative bullseye release date)
On 24/04/21 at 09:25 +0200, Holger Wansing wrote: > Hi, > > Cyril Brulebois wrote (Fri, 23 Apr 2021 15:13:15 +0200): > > D-I Bullseye RC 1 was published a few hours ago. And at the risk of > > sounding like a broken record: I have *absolutely no guarantee* to > > have a fix or workaround for the amdgpu issue in less than a month, > > that would be tested somewhat. > > > > Can we please *not* release with black screens for AMD users? > > Moreover, it's not just an AMD issue. > We got a confirmation just now on debian-boot, that also NVIDIA users can > get affected by this: > https://lists.debian.org/debian-boot/2021/04/msg00225.html > Some months ago, I have confirmed with that user, that missing firmware > is indeed the issue there! Hi, Disclaimer: I read the "[AMD/ATI graphics] Missing firmware not declared / kernel modules not included in initrd" thread. While my understanding of the issue is not complete, I'm trying to summarize what I undertood so far in the hope that others can jump in and fill in the blanks or correct me. There are graphic cards whose in-kernel drivers require non-free firmwares. Typically AMD/ATI cards that require firmware-amd-graphics[1] to work with the radeon, amdgpu and r128 drivers; or NVIDIA cards that require firmware-misc-nonfree to work with the nouveau driver. [1] https://packages.debian.org/unstable/firmware-amd-graphics With Debian 10, the behaviour was that the installation succeeded without installing firmware-* packages, and then, and the first boot, X would start in a "degraded" mode (using, for example, the vesa driver). The user would generally then install the firmware package (or, in the case of NVidia, switch to the proprietary drivers). With Debian 11, the installation also succeeds, but then at first boot, X fails to work correctly. What happens here is unclear: reports vary between "black screen" (but does the system works if the user switches to console mode?), "garbled screen", "system crash" (but maybe the user did not notice that the system works in console mode). It looks like the three open paths for resolution are: A) understand and restore the behaviour from Debian 10, that is, get X to work in a degraded mode after installation. How it worked with Debian 10 (and why it doesn't with Debian 11) is unknown. B) In the installer, detect that firmware-amd-graphics or firmware-misc-nonfree should be installed, and either install it (?), or redirect the user to the unofficial installer that includes them. C) Do nothing and document this in the release notes The main blocking factor for progress seems to be that not enough people have both hardware that is not supported (laptops/desktops with AMD or NVidia graphic cards), and the knowledge and time to investigate this. Lucas
Re: Finding a tentative bullseye release date
Hi, Cyril Brulebois wrote (Fri, 23 Apr 2021 15:13:15 +0200): > D-I Bullseye RC 1 was published a few hours ago. And at the risk of > sounding like a broken record: I have *absolutely no guarantee* to > have a fix or workaround for the amdgpu issue in less than a month, > that would be tested somewhat. > > Can we please *not* release with black screens for AMD users? Moreover, it's not just an AMD issue. We got a confirmation just now on debian-boot, that also NVIDIA users can get affected by this: https://lists.debian.org/debian-boot/2021/04/msg00225.html Some months ago, I have confirmed with that user, that missing firmware is indeed the issue there! Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Re: [AMD/ATI graphics] Missing firmware not declared / kernel modules not included in initrd
Am 24.04.21 um 05:13 schrieb peter green: Adding debian-x to CC. On 01/01/2021 16:52, Karl-Heinz Künzel wrote: For a crosscheck I installed 'debian-10.7.0-amd64-netinst.iso' Xfce. System working! sources.list buster -> bullseye, update, upgrade, dist-upgrade, reboot and after grub system crashes 'black screen'. Restart again, now with kernel 4.19.0-13. System working! br KH It strikes me that there are two parts to this issue. 1. How to make the installer find/install the firmware? 2. Why does X work without firmware on the buster kernel but not on the bullseye kernel? did the buster kernel accidentally include firmware that it should not have done? when running on the buster kernel is X and/or the kernel using a generic driver rather than a GPU specific driver? I think, Holger Wansing made things quite clear, but what puzzles me is, that only a very few people (if any at all) do have this issue. I asked in the both DEBIAN forums, no confirmation. And I have the issue with Nvidia. I filled a bug report #984518 on this and did another try as Debian GNU/Linux bullseye-DI-rc1 "Bullseye" - Official Snapshot amd64 NETINST 20210415-20:25 just was released. Same! If I see it right 'Kernel not loading, nv, nouveau, vesa'. Maybe we will see a reaction, when Bullseye is finally released and this issue affects more users?? br Karl
