Bug#950587: rootskel: kernel argument parsing in S02module-params ignores quoting
Package: rootskel Severity: normal Dear Maintainer, If I preseed multiple nameservers on the kernel command line, like for example netcfg/get_nameservers="193.225.12.63 193.225.14.58", in the installed system the following /etc/modprobe.d/local.conf appears: --8<-- # Local module settings # Created by the Debian installer options 193.225.14 225.14.58"=193.225.14.58" --8<-- Indeed, if I pass a="b c.d" on the kernel command line, the misunderstanding is already present in the installer environment: --8<-- ~ # cat /var/lib/register-module/c.params options:d"=c.d" --8<-- The problematic code is S02module-params in rootskel. Proper and secure quote handling is indeed pretty hard in shell programming, but security isn't relevant in the Debian Installer context, so using shell eval seems acceptable and probably provides the easiest solution. Please consider fixing this some way. -- Thanks, Feri.
Bug#1034041: Should firmware-amd-graphics be automatically installed?
Hi, I had a similar experience with a desktop system containing a Radeon RX470 graphics card. The text-based installation went all right and then even the Gnome desktop opened after reboot, but it ran in a low-resolution mode until I manually installed firmware-amd-graphics (the non-free-firmware archive component was already enabled). Is this the intended behaviour? -- Thanks, Feri.
Bug#1034041: Should firmware-amd-graphics be automatically installed?
Cyril Brulebois writes: > Ferenc Wágner (2023-05-22): > >> I had a similar experience with a desktop system containing a Radeon >> RX470 graphics card. The text-based installation went all right and >> then even the Gnome desktop opened after reboot, but it ran in a >> low-resolution mode until I manually installed firmware-amd-graphics >> (the non-free-firmware archive component was already enabled). >> >> Is this the intended behaviour? > > Which installer did you use? Its lsb-release says: DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="12 (bookworm) - installer build 20230401" X_INSTALLATION_MEDIUM=netboot so it must have been bookworm RC 1. The date was 22nd of April. I started the kernel+initrd.gz from GRUB. -- Feri.
Bug#1034041: Should firmware-amd-graphics be automatically installed?
Cyril Brulebois writes: > Ferenc Wágner (2023-05-22): >> Cyril Brulebois writes: >> > Which installer did you use? >> >> Its lsb-release says: >> >> DISTRIB_ID=Debian >> DISTRIB_DESCRIPTION="Debian GNU/Linux installer" >> DISTRIB_RELEASE="12 (bookworm) - installer build 20230401" >> X_INSTALLATION_MEDIUM=netboot >> >> so it must have been bookworm RC 1. The date was 22nd of April. I >> started the kernel+initrd.gz from GRUB. > > In other words you were also using netboot. > > https://wiki.debian.org/DebianInstaller/NetbootFirmware should have > details about how to deal with firmware when netbooting. It's been there > since ~ forever, and has been updated for Bookworm. Thanks for the pointer. Are you implying that if some firmware isn't loaded during installation, it isn't expected to be present on the installed system either? If so, then it worked for me as intended. (Actually, my Ethernet driver also tries to load some Realtek firmware, but apparenetly works just fine without it, so I only installed it later to reduce warnings from update-initramfs. The graphics firmware was a must for desktop usage, though.) -- Thanks, Feri.
Bug#1034041: Should firmware-amd-graphics be automatically installed?
Cyril Brulebois writes: > I'm implying that installation images produced by debian-cd (and available > on cdimage.d.o) should have firmware packages available and ready to deploy, > and should do that automatically; while netboot images (produced by the > debian-installer build system) don't, and won't be able to deploy firmware > packages unless tweaked beforehand via the procedure documented on that > page. Yes, that'f perfectly fine. My question was whether the relavant firmware packages should be present on the installed system even if the installer itself did not use/load them. The netboot installer installs everything from the network after all, so it could install firmware packages just as it installs desktop packages for example. Apparently it does not, which is fine again, but I wasn't certain of the intent. -- Cheers, Feri.
Bug#848972: Fixed in Ubuntu
Control: tag + patch Hi, This issue was fixed in 1.178ubuntu12, as detailed at https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227 Please consider taking over the fix. -- Thanks, Feri.
Bug#848972: Fixed in Ubuntu
On Sun, 11 Feb 2024 13:11:51 +0100 Holger Wansing wrote: > Ferenc Wágner wrote (Mon, 26 Jun 2023 12:27:49 +0200): > >> This issue was fixed in 1.178ubuntu12, as detailed at >> https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227 >> Please consider taking over the fix. > > I have grabbed the changings from > https://git.launchpad.net/ubuntu/+source/console-setup/commit/?h=applied/ubuntu/disco&id=dc3395232928c2a3f53c7e5e29ad25a2638ddcae > Patch attached. Any objections? Hi Holger, None from my part, FWIW (very little). I'd thank the original author in the changelog entry, though. -- Thanks for you work, Feri.
Bug#709436: debian-installer: too low memory requirement documented on the F2 boot screen
Package: debian-installer Version: wheezy Severity: minor Hi, Booting the Wheezy mini.iso, choosing Help from the menu, pressing F2 says: You must have at least 44 megabytes of RAM to use this Debian installer. Starting the installer with 64 MB of memory enters low memory mode, and reports insufficient memory: [...] At least 86 megabytes of memory are required. Continuing the installation then runs into OOM situation. The two memory requirement statements should be synchronized, 44 (or even 64) MB is clearly not enough. Thanks, Feri. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130523102537.32127.97533.report...@lant.ki.iif.hu
Bug#716710: debian-installer: keymap is not an alias of keyboard-configuration/xkb-keymap in a preseed file
Package: debian-installer Version: 20130613 Severity: minor Hi, Quoting http://www.debian.org/releases/wheezy/amd64/apbs04.html.en: # keymap is an alias for keyboard-configuration/xkb-keymap d-i keymap select us But this form does not actually work (for me at least): one has to use the long form: d-i keyboard-configuration/xkb-keymap select us Please fix either the documentation or the implementation; the alias already works on the command line, which is very useful, but I personally do not mind using the long form in the preseed file. -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130711152740.31694.3210.report...@lant.ki.iif.hu
Bug#439512: debian-installer: doubled serial console lines in /etc/securetty
Package: debian-installer Severity: minor Hi, After serial console netboot Etch installation /etc/securetty ends like this: # serial console added by debian-installer tts/0 ttyS0 However, those entries are already present in the file, at the very top. It doesn't seem to cause a problem in itself, but can become dangerous if the administrator removes only one (pair) of the entries and thinks s/he disabled root login over the serial console. I think it's better to remove this append from the installer. Thanks, Feri. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
