Bug#756841: Seeing this in bullseye, bookworm, and trixie.
Seeing this in bullseye, bookworm, and trixie. And other problems as well. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Testing CD preseed oops: regression
I have the latest testing netinst (20240722-03:17), and would like to install it on a virtual machine. I have a preseed file on a USB stick. As this is a virtual machine, the virtual hard drive is at vda, and the USB stick shows up at sda. When I go to load the debconf file, the installer doesn't find it. I then go to a console and manually mount the USB stick on /media. I can then ls the stick, more the preseed file, etc. When I then go back to the installer, it still cannot find the preseed file, and the USB stick has been unmounted. This has worked in the past. I boot from the help screen with the command line: expert auto file=/media/preseed.cfg I notice that the error message indicates that the installer failed to process "file:///media/preseed.cfg" (note the three slashes). -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Bug#1057237: debian-installer: Debian 12 (Bookworm) on Ace Magic T8Plus: Installation Report
Package: debian-installer Severity: normal X-Debbugs-Cc: charlescur...@charlescurley.com Dear Maintainer, I took delivery of two Ace Magic T8+ computers recently. https://www.acemagic.com/products/t8plus I am bringing one up as a router running Debian 12.2 (Bookworm). A full hardware probe of the machine is at Linux Hardware. https://linux-hardware.org/?probe=d0bbc73e29 Note that this was run over SSH, so any monitor information is incorrect. However, it does work with an NEC EA244WMi connected directly. I first used a live CD to test the machine. I then used gparted to shrink the Windows partition to 60 G, giving me 177G for Linux, plenty for this application. I then booted to Windows so that it would do any necessary fixup on its partition. I then installed using a netinst image (debian-12.2.0-amd64-netinst.iso) on a USB stick, and a second USB stick for my preseed file and some post-installation scripts. All has gone well, with one glitch. The glitch was that after the installation the T8+ refused to boot to Linux, going directly into Windows. To make the grub bootloader active after installing Linux and GRUB, in the firmware: During boot, hit escape or delete to get into the firmware. Security -> Secure Boot -> Enabled Boot -> UEFI BBS Priorities -> Debian boot option Save & Exit -> Save Changes and Exit Note: Memtest86 does not appear to work. I believe this is a problem with Memtest86, per emails on the Debian User list. Power use: 5 watts when idle, .28 KWH. -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1032852: Error message clue:
On Wed, 29 Mar 2023 08:41:43 +0200 Pascal Hambourg wrote: > Hello, > > > Already fixed in hw-detect 1.155: > * Fix files removal for non-accepted firmware packages (See: > #1032377). > > I can confirm that, when running with no preseed, I now see the license agreement and can accept it. My preseed file has the following: # https://preseed.debian.net/debian-preseed/bookworm/amd64-non-free-firmware-full.txt d-i firmware-ipw2x00/license/accepted boolean true so I would not expect to see the license agreement. If I read the syslog correctly, the preseeded license agreement accepted was handled correctly: May 22 18:16:52 debconf: --> SET firmware-ipw2x00/license/accepted true May 22 18:16:52 debconf: <-- 10 firmware-ipw2x00/license/accepted doesn't exist May 22 18:16:52 debconf: --> REGISTER debian-installer/dummy firmware-ipw2x00/license/accepted May 22 18:16:52 debconf: <-- 0 May 22 18:16:52 debconf: --> SET firmware-ipw2x00/license/accepted true May 22 18:16:52 debconf: <-- 0 value set May 22 18:16:52 debconf: --> SUBST firmware-ipw2x00/license/accepted ID firmware-ipw2x00/license/accepted May 22 18:16:52 debconf: Adding [ID] -> [firmware-ipw2x00/license/accepted] May 22 18:16:52 debconf: <-- 0 May 22 18:16:52 debconf: --> FSET firmware-ipw2x00/license/accepted seen true I did three installations at least as far as the WiFi business and have the logs from them should anyone wish to see them. Alas, there are other problems, but this seems to be fixed. Thank you. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: d-i bug: spurious checksum error?
On Wed, 19 Apr 2023 12:20:56 +0200 Philip Hands wrote: > According to the log, you actually invoked it with file=preseed.cfg: > > Kernel command line: BOOT_IMAGE=/install.386/vmlinuz priority=low > vga=788 initrd=/install.386/gtk/initrd.gz --- auto file=preseed.cfg > DEBCONF_DEBUG=developer Aha! Thank you for that catch. I re-ran the installation, double checking my command line, and did not get that error. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/ pgpuqOBX6eGC_.pgp Description: OpenPGP digital signature
Bug#1033921: debian-installer: Weekly build of d-i fails to find ipw2x00 firmware package
On Tue, 4 Apr 2023 07:57:34 +0200 Pascal Hambourg wrote: > On 04/04/2023 at 01:46, Cyril Brulebois wrote: > > > > Everything seems to be working as intended… > > Yes. The package is found but rejected because of licence issue. This > is the expected effect of "Fix files removal for non-accepted > firmware packages (#1032377)", although it might be seen by users as > a regression. I agree, it is a regression, and silently eliding over the problem is an unacceptable way to handle it. I believe that this approach contravenes the spirit if not the letter of the vote to include proprietary blobs in the Debian Installer. It used to be possible to accept the license, use the firmware, and continue. That should now be the approach. > > > Arguably check-missing-firmware could be more verbose about what > > happens around license accepting. > > Yes, at the least. Agreed. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Debian Installer Bookworm RC 1 release
On Mon, 3 Apr 2023 23:31:42 +0200 Cyril Brulebois wrote: > The Debian Installer team[1] is pleased to announce the first release > candidate of the installer for Debian 12 "Bookworm". Hmm. On https://www.debian.org/devel/debian-installer, there are two news items at the top. Both are dated 19 Feb 2023. Is that correct? The RC1 release (https://www.debian.org/devel/debian-installer/News/2023/20230403) is also dated February 19th, 2023. Otherwise, thank you. I look forward to testing this release candidate. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/ pgpqFZsUjtZXr.pgp Description: OpenPGP digital signature
Bug#1032964: Enhancement: Option to have d-i install a connection for Network Manager
Package: debian-installer
Severity: wishlist
Tags: d-i
X-Debbugs-Cc: charlescur...@charlescurley.com
Dear Maintainer,
Users can currently preseed wireless connections. A possible enhancement is: if
preseeding included installing Network Manager (NM), to optionally provide the
AP credentials to NM via nmcli. E.g. (for shell scripting):
nmcli con add con-name "${essid}" ifname "${wif}" type wifi ssid "${essid}"
nmcli con modify "${essid}" wifi-sec.key-mgmt wpa-psk
nmcli con modify "${essid}" wifi-sec.psk ''
Bug#1032963: debian-installer: Option to encrypt wireless passwords in preseed file, please.
Package: debian-installer Severity: wishlist Tags: d-i X-Debbugs-Cc: charlescur...@charlescurley.com Dear Maintainer, When using a preseed file to configure one's wireless interface, one usually needs a password for the access point. Currently, as far as I know, the only option is to use "d-i netcfg/wireless_wpa" or "d-i netcfg/wireless_wep", as appropriate. Would it be possible to encrypt those in the preseed file, as we currently can do for root's password, the optional grub password, etc.? This would allow better security in preseed file.
Bug#1032852: Partial preseed: no netcfg entries.
On the T520, I tried again. This time I had the preseed file (attached) with all netcfg entries commented out. I got as far as the network setup stuff. When I told it to try the wireless, it replied that the passphrase was too short. Well, of course it was too short: d-i never prompted for a passphrase. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/ preseed.cfg.redacted Description: Binary data
Bug#1032852: debian-installer: Intel Corporation PRO/Wireless 2200BG doen't work for d-i, does work on installed Bookworm
On Mon, 13 Mar 2023 11:31:39 +0100 Pascal Hambourg wrote: > Really ? I had the license agreement screen during the package > selection and installation step. Yup. In neither of the two experiments I ran this morning did any license prompt show up. One was preseeded, the other not. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Bug#1032852: debian-installer: Intel Corporation PRO/Wireless 2200BG doen't work for d-i, does work on installed Bookworm
On Sun, 12 Mar 2023 21:39:17 + Steve McIntyre wrote: > Hi Charles > > Thanks for the bug! Inline are a few questions / things I've seen from > the log: > > On Sun, Mar 12, 2023 at 03:13:34PM -0600, Charles Curley wrote: > [...] > > I can see that d-i's firmware detection stuff worked just fine for the > ipw2200 hardware (yay!): OK. > > wlp2s2 is the wireless interface name, Correct. > and the installer is trying to > use it: > > Then I can see lots of errors around running wpasupplicant: > > Mar 12 20:54:18 netcfg[5996]: WARNING **: Couldn't read Wpasupplicant > pid file, not trying to kill. ... > Mar 12 20:54:24 netcfg[5996]: INFO: Activating interface wlp2s2 > Mar 12 20:54:25 netcfg[5996]: INFO: Scan of wireless interface wlp2s2 > succeeded. Mar 12 20:54:25 netcfg[5996]: INFO: Network chosen: . > Proceeding to connect. Mar 12 20:54:25 netcfg[5996]: INFO: Couldn't > connect to wpasupplicant Mar 12 20:54:25 netcfg[5996]: INFO: > Activating interface wlp2s2 Mar 12 20:54:25 netcfg[5996]: INFO: Scan > of wireless interface wlp2s2 succeeded. Mar 12 20:54:25 netcfg[5996]: > > and these errors go on for a long time :-( Yes. I eventually hit control-C or otherwise stopped d-i, which is probably when the log stopped. > > You say that you're preseeding things. Could you also please share > your preseed file in case that is relevant? Well, drat. I've tried several things in the preseed file, and did not preserve exactly what I used for wireless in the run that produced this log file. I will try it again, this time preserving the preseed file. I also just looked at the templates.dat file from a previous installation, and compared that with my preseed file. I have no entry for "netcfg/wireless_adhoc_managed", so that could be my problem. For the last run today (not the run that produced the attached syslog), I have the following: root@dragon:/media/disk# grep netcfg preseed.cfg | grep -v '^#' d-i netcfg/link_wait_timeout string 4 d-i netcfg/hostname string dragon d-i netcfg/wireless_show_essids select manual d-i netcfg/wireless_essid string Curleynet2 d-i netcfg/wireless_essid_again string Curleynet2 d-i netcfg/wireless_security_type select WPA/WPA2 PSK d-i netcfg/wireless_wpa string root@dragon:/media/disk# One other thought: shouldn't there be an option to hash the AP password (netcfg/wireless_wpa), same as there is to hash the root and user passwords? > > Could you run the installation without preseeding and confirm if the > wireless works that way please? > I have run it with the preseed, but with no "d-i netcfg/wireless" options enabled. No joy. I will try that, probably tomorrow. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Bug#1032852: debian-installer: Intel Corporation PRO/Wireless 2200BG doen't work for d-i, does work on installed Bookworm
On Sun, 12 Mar 2023 23:23:56 +0100 Pascal Hambourg wrote: > On 12/03/2023 at 22:39, Steve McIntyre wrote: > [...] > [...] > [...] > > Warning: as described in bug #1032377, the firmware package > firmware-ipw2x00 should be reject for requiring license approval. > Kibi fixed the typo in commit > 22f23968338e82e2ac5d943cf8035e5096f230d4. > > The weird part is that IIUC the package should not have been > installed in the target system because it was removed from the > installer's cache, so the wifi should not work in the target system > either. It wound up in the installed system. I don't recall seeing the license prompt during any of my various Bookworm installations, complete or partial. Indeed, the only prompts I got related to network setup were to announce failures. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Bug#1032473: debian-installer: Put the Show Password in Clear prompt above the Password prompt
Package: debian-installer Severity: normal Tags: d-i X-Debbugs-Cc: charlescur...@charlescurley.com Dear Maintainer, In a normal installation, one is prompted for information that is highly confidential, such as passwords and encrypted partitions. In the regular (non-GUI) installer one moves from field to field with the tab key, tab to go forward, shift tab to go backward. Similarly in the GUI, except that one can also use the mouse. In the current password prompt, to show the password in clear, one must tab to that prompt, hit the space bar to activate showing the password in clear, then shift tab back to enter the password itself. If the Show Password in Clear prompt were above the password prompt, it would be faster: space bar to show the password in clear, then tab to enter the password. The downside is for those users who do not want to show the password in clear: it adds an extra tab keystroke for them. How often does one really need that obfuscation? Request: put the Show Password in Clear prompt above the password prompt. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 6.1.0-5-686 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#592834: Seeing this under bookworm/sid
The unattended upgrade of grub failed (due to the fact that I had replaced the hard drive and used dd to copy sector for sector from the old one to the new, and that changed the identity of the hard drive). Per the instructions in the unattended upgrade message, I ran the following: root@white:~# DEBIAN_FRONTEND=dialog dpkg --configure grub-pc Setting up grub-pc (2.06-8) ... grub-pc: Running grub-install ... Installing for i386-pc platform. File descriptor 3 (pipe:[225467]) leaked on vgs invocation. Parent PID 3611: grub-install File descriptor 3 (pipe:[225467]) leaked on vgs invocation. Parent PID 3611: grub-install File descriptor 3 (pipe:[225467]) leaked on vgs invocation. Parent PID 3611: grub-install Installation finished. No error reported. grub-install success for /dev/sda Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.1.0-3-686 Found initrd image: /boot/initrd.img-6.1.0-3-686 Found linux image: /boot/vmlinuz-6.1.0-2-686 Found initrd image: /boot/initrd.img-6.1.0-2-686 Found memtest86+ image: /boot/memtest86+x32.bin Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. done root@white:~# cat /etc/debian_version bookworm/sid root@white:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux bookworm/sid Release:n/a Codename: bookworm root@white:~# pre grub grub2-common2.06-8 i386 grub-common 2.06-8 i386 grub-pc 2.06-8 i386 grub-pc-bin 2.06-8 i386 root@white:~# This machine is identical to the one on which I encountered this bug in January. Both are Compulab Fit-PCs. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Bug#592834: Seeing the same thing.
root@grissom:~# cat /etc/debian_version 11.6 root@grissom:~# uname -a Linux grissom 5.10.0-20-686 #1 SMP Debian 5.10.158-2 (2022-12-13) i586 GNU/Linux root@grissom:~# free totalusedfree shared buff/cache available Mem: 228Mi43Mi63Mi 0.0Ki 121Mi 175Mi Swap: 487Mi14Mi 473Mi Total: 716Mi58Mi 536Mi root@grissom:~# Yes, I know Bullseye doesn't officially support so little memory. However, I installed Bullseye fresh over a year and have been running unattended-upgrades ever since, and not seen this until just now. I left the machine off for about 6 months, so the last upgrade, on January 3, ran a lot of updates. One of them was grub itself: grub-pc (2.06-3~deb11u5) over (2.04-20). Possible regression? root@grissom:~# apt install memtest86 memtest86+ Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: hwtools memtester kernel-patch-badram grub2 | grub mtools The following NEW packages will be installed: memtest86 memtest86+ 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 125 kB of archives. After this operation, 2,697 kB of additional disk space will be used. Get:1 http://deb.debian.org/debian bullseye/main i386 memtest86 i386 4.3.7-3+b1 [47.7 kB] Get:2 http://deb.debian.org/debian bullseye/main i386 memtest86+ i386 5.01-3.1 [77.6 kB] Fetched 125 kB in 1s (123 kB/s) Preconfiguring packages ... Selecting previously unselected package memtest86. (Reading database ... 46032 files and directories currently installed.) Preparing to unpack .../memtest86_4.3.7-3+b1_i386.deb ... Unpacking memtest86 (4.3.7-3+b1) ... Selecting previously unselected package memtest86+. Preparing to unpack .../memtest86+_5.01-3.1_i386.deb ... Unpacking memtest86+ (5.01-3.1) ... Setting up memtest86+ (5.01-3.1) ... Generating grub configuration file ... File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6180: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6180: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6188: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6188: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6196: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6196: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6204: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6204: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6250: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6250: /usr/sbin/grub-probe Found linux image: /boot/vmlinuz-5.10.0-20-686 Found initrd image: /boot/initrd.img-5.10.0-20-686 File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6323: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6323: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6331: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6331: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6339: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6339: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6347: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6347: /usr/sbin/grub-probe Found linux image: /boot/vmlinuz-5.10.0-16-686 Found initrd image: /boot/initrd.img-5.10.0-16-686 File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6596: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6596: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6622: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6622: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6630: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6630: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6638: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6638: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6646: /usr/sbin/grub-probe File descriptor 3 (pipe:[47062]) leaked on vgs invocation. Parent PID 6646: /usr/sbin/grub-probe Found memtest86+ image: /boot/memtest86+.bin Found memtest86+ multiboot image:
Bug#992034: installation-guide: Include a note on how to change init system during install
On Thu, 26 Aug 2021 22:45:17 +0200 Holger Wansing wrote: > I wonder if "the easiest time to select an alternative init system is > during the installation process" is correct English. > > Maybe better "the best time ... " ? Much better, although both are literally true. From an native American speaker. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Addition to release-notes?
A bit of wordsmithing, if I may, from a native Engish (US) speaker... I did a bit of re-arranging, mostly putting the explanation at the beginning. I also changed some working to make it flow a bit better. On Tue, 3 Aug 2021 21:11:07 +0200 Holger Wansing wrote: > > Help with installation of firmware > > > Since chances are getting higher, that users might need device > firmware installed to get their hardware running properly, the > installer has been improved to help with that. More and more, peripheral devices require firmware to be loaded as part of the hardware initialization. The firmware is usually not DFSG compliant, so it is not distributed in Debian's main repositories. To help deal with this problem, the installer has been improved. > A new mechanism has been implemented, which tries to detect - based > on a hardware ID -> firmware file mapping - if some of the installed > hardware needs firmware files to be installed, and installs them > automatically in such case. Based on a hardware ID to firmware file mapping, if some of the installed hardware requires firmware files to be installed, the code installs them automatically. > This works out of the box, if you are using an inofficial installer This works out of the box, if you are using an unofficial installer ^^^ > image with firmware included (see > url="https://www.debian.org/releases/stable/debian-installer/#firmware_nonfree;>https://www.debian.org/releases/stable/debian-installer/#firmware_nonfree). > When using an official installer image, you will most likely need to > enable the non-free component of the archive, when asked for that, > since most firmware packages are not DFSG-free and therefore not > distributable via main. When using an official installer image, you will most likely need to enable the non-free component of the archive, when asked for that. > > -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Speed up installation: activate eatmydata-udeb by default and include eatmydata package in /pool
On Fri, 16 Apr 2021 08:49:34 +0100 Ian Campbell wrote: > > > > Please do not confuse "ignore" with "terribly understaffed". > > I wonder if there is anything which a 3rd party could be found to do > via the Freexian project thing[0] which would reduce the overall > burden and free up some of the limited time contributors (of which I > am long lapsed :-() have? e.g. automate some time consuming manual > work, setup automated testing infra, that sort of thing? Thanks for bringing this up. I am a long time Debian user (Linux since 1993, Debian only for the last decade or so). I have had little idea how things work in the Debian community and am just beginning to explore it. Along with Freexian, perhaps the occasional Call for Volunteers to get specific things done would shake loose some volunteers? These could go out on the various user-level mailing lists such as debian-user. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Bug#985853: debian-installer: Whitespace before a commented line in preseed file causes line to be parsed
On Thu, 25 Mar 2021 10:49:06 -0400
lsore...@csclub.uwaterloo.ca (Lennart Sorensen) wrote:
> Well none of the examples ever have spaces before # for comments.
> The documentation page you linked to doesn't even mention comments at
> all. I would agree that perhaps it should. I have certainly
> encountered file types before where comments had to have # at the
> start of the line.
May I suggest inserting the following as the last bullet point item at
the top of "B.3. Creating a preconfiguration file" the following:
A comment consist of a line which *starts* with a sharp character ("#")
and extends the length of that line.
https://www.debian.org/releases/stable/i386/apbs03.en.html
The emphasis on the word "starts" should probably be italics, or, in
HTML, .
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Bug#985755: Similar situation: IBM Thinkpad R51
I am seeing a similar situation on an IBM Thinkpad R51 with Bullseye. root@dragon:/media/disk/dragon# uname -a Linux dragon 5.10.0-4-686 #1 SMP Debian 5.10.19-1 (2021-03-02) i686 GNU/Linux root@dragon:/media/disk/dragon# lspci -s 2:2 02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05) Extracts from installation syslog: Mar 15 19:59:33 cdrom-detect: Detected CD 'Debian GNU/Linux testing "Bullseye" - Unofficial i386 NETINST with firmware 20210315-03:00' Mar 15 19:59:34 cdrom-detect: Detected CD with 'testing' (bullseye) distribution Mar 15 20:00:16 kernel: [ 97.408403] libipw: 802.11 data/management/control stack, git-1.1.13 Mar 15 20:00:16 kernel: [ 97.408406] libipw: Copyright (C) 2004-2005 Intel Corporation Mar 15 20:00:16 kernel: [ 97.419730] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq Mar 15 20:00:16 kernel: [ 97.419733] ipw2200: Copyright(c) 2003-2006 Intel Corporation Mar 15 20:00:16 kernel: [ 97.419998] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection Mar 15 20:00:16 kernel: [ 97.420069] ipw2200 :02:02.0: firmware: failed to load ipw2200-bss.fw (-2) Mar 15 20:00:16 kernel: [ 97.420071] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware Mar 15 20:00:16 kernel: [ 97.420074] ipw2200 :02:02.0: Direct firmware load for ipw2200-bss.fw failed with error -2 Mar 15 20:00:16 kernel: [ 97.420077] ipw2200: Unable to load firmware: -2 Mar 15 20:00:16 kernel: [ 97.420186] ipw2200: probe of :02:02.0 failed with error -5 Mar 15 20:00:18 check-missing-firmware: looking at dmesg again, restarting from \[ 49.154404\] Mar 15 20:00:18 check-missing-firmware: timestamp found, truncating dmesg accordingly Mar 15 20:00:18 check-missing-firmware: saving timestamp for a later use: [ 97.420186] Mar 15 20:00:18 check-missing-firmware: looking for firmware file ipw2200-bss.fw requested by ipw2200 Mar 15 20:00:18 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping Mar 15 20:00:18 check-missing-firmware: /run/udev/firmware-missing does not exist, skipping Mar 15 20:00:18 check-missing-firmware: missing firmware files (ipw2200-bss.fw) for ipw2200 Mar 15 20:00:28 check-missing-firmware: installing firmware package /cdrom/firmware/firmware-ipw2x00_20210208-3_all.deb Mar 15 20:01:28 kernel: [ 169.610175] isofs_fill_super: bread failed, dev=sda2, iso_blknum=16, block=32 Mar 15 20:01:28 kernel: [ 169.612641] isofs_fill_super: bread failed, dev=sda2, iso_blknum=16, block=32 Mar 15 20:01:43 check-missing-firmware: removing and loading kernel module ipw2200 Mar 15 20:01:43 kernel: [ 185.293199] lib80211_crypt: unregistered algorithm 'NULL' Mar 15 20:01:43 kernel: [ 185.351541] cfg80211: Loading compiled-in X.509 certificates for regulatory database Mar 15 20:01:43 kernel: [ 185.353663] cfg80211: Loaded X.509 cert 'b...@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf' Mar 15 20:01:43 kernel: [ 185.35] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328' Mar 15 20:01:43 kernel: [ 185.357545] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Mar 15 20:01:43 kernel: [ 185.357620] platform regulatory.0: firmware: direct-loading firmware regulatory.db Mar 15 20:01:43 kernel: [ 185.357654] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s Mar 15 20:01:43 kernel: [ 185.366797] lib80211: common routines for IEEE802.11 drivers Mar 15 20:01:43 kernel: [ 185.366802] lib80211_crypt: registered algorithm 'NULL' Mar 15 20:01:43 kernel: [ 185.371378] libipw: 802.11 data/management/control stack, git-1.1.13 Mar 15 20:01:43 kernel: [ 185.371380] libipw: Copyright (C) 2004-2005 Intel Corporation Mar 15 20:01:44 kernel: [ 185.382653] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq Mar 15 20:01:44 kernel: [ 185.382656] ipw2200: Copyright(c) 2003-2006 Intel Corporation Mar 15 20:01:44 kernel: [ 185.382937] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection Mar 15 20:01:44 kernel: [ 185.383337] ipw2200 :02:02.0: firmware: direct-loading firmware ipw2200-bss.fw Mar 15 20:01:44 kernel: [ 185.509084] ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels) Mar 15 20:01:44 kernel: [ 185.511325] ipw2200 :02:02.0 wlp2s2: renamed from eth0 Mar 15 20:01:44 net/hw-detect.hotplug: Detected hotpluggable network interface wlp2s2 Mar 15 20:01:47 main-menu[237]: INFO: Menu item 'netcfg' selected Mar 15 20:01:47 netcfg[5289]: INFO: Starting netcfg v.1.171 Mar 15 20:01:47 netcfg[5289]: WARNING **: Couldn't read Wpasupplicant pid file, not trying to kill. Mar 15 20:01:47 netcfg[5289]: INFO: Activating interface enp2s8 Mar 15 20:01:47 netcfg[5289]: INFO: Waiting time set to 4 Mar 15 20:01:51 netcfg[5289]: INFO: Reached timeout for link detection on enp2s8 Mar 15 20:01:51
Re: Bug#985755: debian-installer: Bullseye netinst Installer doesn't find RTL8723DE Network Hardware
On Mon, 22 Mar 2021 18:02:25 -0400 Kenneth Parker wrote: > Package: debian-installer > Severity: important > X-Debbugs-Cc: sea7k...@gmail.com There is a lengthy discussion of the problem on the Debian User list, starting at https://lists.debian.org/debian-user/2021/03/msg01089.html -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Fw: Bug#985463: debian-installer: kernel complains about /boot partition in LVM install (ext2 filesystem being mounted at /boot supports timestamps until 2038)
Forgot to hit "Reply All".
Begin forwarded message:
Date: Fri, 19 Mar 2021 09:23:53 -0600
From: Charles Curley
To: Laurent Bonnaud
Subject: Re: Bug#985463: debian-installer: kernel complains about /boot
partition in LVM install (ext2 filesystem being mounted at /boot
supports timestamps until 2038)
On Fri, 19 Mar 2021 15:43:14 +0100
Laurent Bonnaud wrote:
> On 3/18/21 9:08 PM, Charles Curley wrote:
>
> > How much memory does the computer have?
>
> It is a VM with 1GB of RAM.
OK, then my hypothesis is probably wrong.
>
> > On my FIT-PCs, using the same
> > installer (but with firmware), I see that debian installer (d-i)
> > goes to ext2 rather than ext4. They have 228Mi of physical memory.
> > On my IBM R51, with 1.2Gi of physical memory, I do not see this; I
> > get ext4.
>
> It is strange that the choice of FS depends on the amount of RAM.
I believe it depends on the amount of RAM at installation time. If I
set up my partitions manually, on the 1.2Gi R51 I see ext4 as an option
for formatting. I do not see it on the FIT-PCs (228Mi).
However, if you have 1GB of RAM, your problem is likely something else.
> Did you use LVM on both systems?
Usually, yes. At the moment, I do not have LVM on the R51.
>
> > [...] and I don't know how to check the size of my inodes.
>
> You can see it with tune2fs, for instance:
>
> # tune2fs -l /dev/sda1
> [...]
> Inode size: 256
Thanks. Both machines show 256 byte inodes. In the case of the FIT-PC,
after running the tune2fs below.
>
> > But my work-around is to upgrade from ext2 to ext4, like so:
> >
> > tune2fs -O
> > extent,huge_file,flex_bg,dir_nlink,extra_isize,has_journal\
> > ${dev}
>
> I think that changing inode sizes can only be done by recreating the
> FS.
>
> > N.b.: Apparently on an upgrade like this, we can't do metadata_csum
> > or 64bit.
>
> 32->64 bits can be done, but that's another story...
>
> > I don't know if it will solve your problem, but you are welcome to
> > try
>
> Thanks, but what I usually do is to get rid of the /boot partition.
> However that leaves a small unused disk space at the beginning of the
> disk.
>
Ah. I tried at installation time not creating a separate boot partition
and instead putting /boot inside the / LVM partition. Grub seems to
handle it. Doing so should save you that small unused disk space.
Many early BIOSes have limitations such that the boot code must be
within the first X cylinders. I conjecture that as long as Grub is
entirely within the first X cylinders, it can handle any disk size you
are likely to use with a machine that old as long as the boot files are
in an LVM partition. However, if you are running a virtual machine, I
doubt you are hitting that limitation.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Re: Bug#985463: debian-installer: kernel complains about /boot partition in LVM install (ext2 filesystem being mounted at /boot supports timestamps until 2038)
On Thu, 18 Mar 2021 17:10:45 +0100
Laurent Bonnaud wrote:
> I did a test installation using debian-testing-amd64-netinst.iso from
> 2021-03-15 (Debian bullseye/11), chose the LVM option, and noticed
> that once the system is installed and boots, the kernel complains
> with this message:
>
>ext2 filesystem being mounted at /boot supports timestamps until
> 2038 (0x7fff)
>
> This is not fatal, but is ugly and most people would prefer a system
> without this message.
>
> The problem comes from the fact that the boot partition is created as
> ext2 with 128 bytes inodes.
How much memory does the computer have? On my FIT-PCs, using the same
installer (but with firmware), I see that debian installer (d-i) goes
to ext2 rather than ext4. They have 228Mi of physical memory. On my IBM
R51, with 1.2Gi of physical memory, I do not see this; I get ext4.
I do not see anything like the timestamps error message you showed
above, and I don't know how to check the size of my inodes.
But my work-around is to upgrade from ext2 to ext4, like so:
tune2fs -O extent,huge_file,flex_bg,dir_nlink,extra_isize,has_journal\
${dev}
N.b.: Apparently on an upgrade like this, we can't do metadata_csum or
64bit.
I don't know if it will solve your problem, but you are welcome to try
it.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Re: Speed up installation: activate eatmydata-udeb by default and include eatmydata package in /pool
On Sun, 14 Mar 2021 03:18:12 +0300 ValdikSS wrote: > 1. eatmydata-udeb should be enabled by default, to speed up the > installation process. It should not require to be enabled from > preseed file or bootloader cmdline. It's pointless to use fsync() > in installation process, the user won't attempt to fix partially > installed system due to power loss, it only slows it down. I am concerned with low memory installations. I suggest that under low memory conditions eatmydata-udeb should be optional. Do you have any data that would help a low memory installer decide whether to use it or not? -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/ pgpVjkRnkRCcw.pgp Description: OpenPGP digital signature
FIT-PC: Fails to find driver for Ethernet, Realtek Semiconductor Co., Ltd. 8139too
This is to follow up on bug 980777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980777 In brief, I am trying to install Bullseye Alpha on a FIT-PC, https://en.wikipedia.org/wiki/Fit-PC#fit-PC_1.0. The installer does not find the NICs, and does not offer the correct driver if I try to select a driver manually. I am not presently subscribed to this list; the list server seems to think I am a source of spam. Please CC me, at least for the nonce. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Bug#980777: FIT-PC: Fails to find driver for Ethernet, Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI
On Sun, 24 Jan 2021 21:28:26 +0100 John Paul Adrian Glaubitz wrote: > Hi! > > On 1/24/21 4:50 PM, Andrew M.A. Cater wrote: > > OK. This might be a bug in the i386 iso - as you've seen, we can't > > test all i386 easily. This might just be a regression. Given that > > we're about to release 10.8 on Feb 6th, can I suggest that you send > > a mail into debian-boot (or debian cd) referencing the bug number > > and including the syslog entries above. > > FWIW, I recently installed the 10.7 i386 non-free netinst ISO on an > old JVC sub-notebook with a Pentium M CPU and Realtek 8139 ethernet > card and had no issues with that card during installation. > > What actually caused problems was establishing a WiFi connection > during installation with the Intel 2200BG wireless adapter - which is > why I used the ethernet network connection during install. > > After installation, everything worked correctly out of the box, > however (lspci below). Thanks for the report. I hit a similar situation with a Thinkpad R51. Same WiFi, different Ethernet NIC. See below. Even with the firmware-ipw2x00 package, I could not get a connection during installation either. We seem to have the same version of the Realtek (rev 10). Did you end up using firmware for the Realtek? There has been some question on that in the course of this bug. 02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05) 02:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (MOB) Ethernet Controller (rev 81) Your report and some other things I have seen lead me to wonder if I am simply running out of memory on the FIT-PC and d-i is not telling me. A quick search of two syslogs didn't turn anything up. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Bug#980777: FIT-PC: Fails to find driver for Ethernet, Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI
On Sun, 24 Jan 2021 15:50:54 + "Andrew M.A. Cater" wrote: > These are the machines with Geode but limited to 256M memory? As a > matter of interest, what are you using them for - what's the use case > - because 256M is marginal now, I think. It's actually 223M, the remainder used for the video memory. Use case is that I have four of them. Two, grissom and white, are for testing. I have a SOHO network here, with three computers that get daily use, and a few others, older ones, as spares. chaffee: apcupsd server for several computers, local mail collector for logwatch and other admin emails, gitolite server, apt-cacher-ng for ubuntu, dns (bind9) and dhcp server. freeman: firewall/router, apt-cacher-ng for debian, ntp server, openvpn server, failover DNS and DHCP servers. The gitolite server could be faster, otherwise they do just fine, and have been since 2007 or so. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Bug#980777: FIT-PC: Fails to find driver for Ethernet, Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI
On Sat, 23 Jan 2021 20:07:22 + "Andrew M.A. Cater" wrote: > > > 8.6 is old - I'd be surprised that 10.7 firmware iso wouldn't > > > work. > > > > I didn't try 10.x. 8.6 was what I had handy, i.e. it came up first > > in the midden. However, debian-10.4.0-i386-netinst.iso also fails > > to detect the NIC and gives the shortened menu of drivers to try. > > > > -- > > Does anybody read signatures any more? > > > > https://charlescurley.com > > https://charlescurley.com/blog/ > > Firmware-linux-free is usually installed by default. I would > sincerely suggest that you try 10.7 unless you want to wait until > 10.8 comes out (scheduled for the weekend of 6th February 2021. > > I think you just hit a problematic install - I've had laptops with > that particular Realtek Ethernet and they're normally just found. > > All best, as ever, > > Andy C. I tried 10.7. Same problem. This time I am attaching the syslog to this email. I then did a search on the syslog, and got this: root@hawk:/media/disk# grep 8139 syslog Jan 23 23:11:36 kernel: [0.416093] pci :00:0d.0: [10ec:8139] type 00 class 0x02 Jan 23 23:11:36 kernel: [0.416722] pci :00:0e.0: [10ec:8139] type 00 class 0x02 Jan 23 23:11:36 kernel: [ 22.813925] usb 1-1.2: Product: DataTraveler 2.0 root@hawk:/media/disk# On another FIT-PC which is running Bullseye: root@white:/var/log/apt# dmesg | grep 8139 [ 10.897167] pci :00:0d.0: [10ec:8139] type 00 class 0x02 [ 10.898147] pci :00:0e.0: [10ec:8139] type 00 class 0x02 [ 44.971388] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [ 44.979230] 8139cp :00:0d.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too [ 45.141373] 8139cp :00:0e.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too [ 45.438841] 8139too: 8139too Fast Ethernet driver 0.9.28 [ 45.534101] 8139too :00:0d.0 eth0: RealTek RTL8139 at 0xccfc2a96, 00:01:c0:03:f4:11, IRQ 10 [ 45.729725] 8139too :00:0e.0 eth1: RealTek RTL8139 at 0x2e6d8dc8, 00:01:c0:03:d8:78, IRQ 5 [ 48.858651] 8139too :00:0e.0 enp0s14: renamed from eth1 [ 48.960869] 8139too :00:0d.0 enp0s13: renamed from eth0 [ 56.400301] 8139too :00:0d.0 enp0s13: link up, 100Mbps, full-duplex, lpa 0xC5E1 root@white:/var/log/apt# Considerably different. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/ syslog Description: Binary data
Bug#980777: FIT-PC: Fails to find driver for Ethernet, Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI
On Sat, 23 Jan 2021 17:53:30 + "Andrew M.A. Cater" wrote: > > > > * The NIC finding software failed to detect the two NICs. This has > > worked in the past. > > > You'll likely need the firmware .iso including the non-free firmwares > - though I'm surprised that itr doesn't find the Ethernet devices, > they're common. > I don't think I need any firmware. On the working boxes, the only firmware package present is firmware-linux-free, which does not include any Realtek firmware. I don't know why it is present; it has nothing depending on it. It was installed with the kernel. firmware-realtek is absent from working boxes, and in any case does not include firmware for these devices. 00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10) > > > > The first two problems are not new. I got the same with a Buster > > 10.4 netinst CD. I then fell back to a Debian 8.6 netinst CD. That > > correctly found and set up the two NICs. > > > 8.6 is old - I'd be surprised that 10.7 firmware iso wouldn't work. I didn't try 10.x. 8.6 was what I had handy, i.e. it came up first in the midden. However, debian-10.4.0-i386-netinst.iso also fails to detect the NIC and gives the shortened menu of drivers to try. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Bug#980777: FIT-PC: Fails to find driver for Ethernet, Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI
Package: installation-reports Severity: normal X-Debbugs-Cc: charlescur...@charlescurley.com Dear Maintainer, Please see Comments/Problems below. -- Package-specific info: Boot method: DVD Image version: debian-bullseye-DI-alpha3-i386-DVD-1.iso Date: Jan 20 2021 16:36 MST Machine: FIT-PC 1 https://en.wikipedia.org/wiki/Fit-PC#fit-PC_1.0 Partitions: root@white:~# df -Tl Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 108M 0 108M 0% /dev tmpfs tmpfs 23M 560K 22M 3% /run /dev/sda6 ext2 55G 1.1G 51G 3% / tmpfs tmpfs 111M 0 111M 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup /dev/sda1 ext2 236M 20M 204M 9% /boot tmpfs tmpfs 23M 0 23M 0% /run/user/0 /dev/sdb vfat 1.4M 209K 1.2M 15% /media/disk /dev/sdc1 vfat 2.0G 1.2G 748M 62% /mnt root@white:~# fdisk -l /dev/sda Disk /dev/sda: 55.89 GiB, 60011642880 bytes, 117210240 sectors Disk model: Hitachi HTS54166 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x0005c92c Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048499711497664 243M 83 Linux /dev/sda2501758 117209087 116707330 55.7G 5 Extended /dev/sda5501760 1445887944128 461M 82 Linux swap / Solaris /dev/sda6 1447936 117209087 115761152 55.2G 83 Linux root@white:~# Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [ ] Detect media: [O] Load installer modules: [O] Clock/timezone setup: [ ] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[O] Install tasks: [ ] Install boot loader:[O] Overall install:[ ] Comments/Problems: I own three FIT-PC 1s, two of which provide network services. https://en.wikipedia.org/wiki/Fit-PC#fit-PC_1.0 I'd like to keep them running for a few more years yet. So I tried the alpha 3 installer. In the process, I hit several problems. * The NIC finding software failed to detect the two NICs. This has worked in the past. * When I tried to select the driver manually, I was given a list of two NICs, neither one of them appropriate. On other hardware, a much longer list, including the ones I need (8139.*), appears. * When I tried to read the drivers from a USB floppy device, the software did not find the floppy. This, in spite of the fact that I could mount the floppy manually and read the preseed file from it. The floppy drive should be /dev/sdb or sdc, depending on what else I have on the USB bus. * When putting file systems on the hard drive, ext4 and ext3 were absent from the menu of possible file systems. ext2 was there, and that's what I selected and got. Is something eating my menus? The first two problems are not new. I got the same with a Buster 10.4 netinst CD. I then fell back to a Debian 8.6 netinst CD. That correctly found and set up the two NICs. Just in case I had hardware issues, I have tried this on two machines, one of which has been in continuous service since I bought them. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="11 (bullseye) - installer build 20201202" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux (none) 5.9.0-4-686 #1 SMP Debian 5.9.11-1 (2020-11-27) i586 GNU/Linux lspci -knn: 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] Host Bridge [1022:2080] (rev 33) lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] Host Bridge [1022:2080] lspci -knn: 00:01.1 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD] Geode LX Video [1022:2081] lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Geode LX Video [1022:2081] lspci -knn: 00:01.2 Entertainment encryption device [1010]: Advanced Micro Devices, Inc. [AMD] Geode LX AES Security Block [1022:2082] lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD] Geode LX AES Security Block [1022:2082] lspci -knn: Kernel modules: geode_rng lspci -knn: 00:0d.0 Ethernet controller [0200]:
Bug#892082: Related bug??
I wonder if this is related to a bug I hit -- and I may have solved. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980271#15 for the details and a workaround. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Bug#980271: More network issues, cardbus issue??
I tried a Xircom CreditCard Ethernet adapter, CE38-100BTX, which uses the xirc2ps_cs driver. It runs, if slowly, on an installed system. But on installation, the software fails to detect it also. I noticed in the log on console F4 a message: pcmcia-socket-startup: chdir to /etc/pcmcia failed: no such file or directory. Possibly this is because the directory actually is /etc/pcmciautils on the installer. It is /etc/pcmcia on the installed system. I then made a symlink, rmmod yenta_socket, modprobe yenta_socket. Messages indicate that yenta_socket picked up the configuration file. I then inserted the card. Messages indicate that the card was detected and set up. I then went back to the installatio software, had it detect the network. It detected it correctly, and auto-configuration worked correctly. I think that's your bug, and you should be able to verify that on any PCMCIA system. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Bug#980271: Addendum: network issues
I fixed (?) the network issues by putting a 10MB hub between the Tecra and the rest of the network. Other than the collision light lighting up the night, it works fine with a data rate of about 1 MB/sec. That, however, did not fix the detection issue. I still get no network during installation. Once installation is done, and I can bring up the computer, I added eth0 to /etc/network/interfaces, and I could bring it up and run it. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Bug#980271: installation-reports: Toshiba Tecra 8000 Installation report Bullseye
Package: installation-reports Severity: normal Tags: d-i X-Debbugs-Cc: charlescur...@charlescurley.com Dear Maintainer, -- Package-specific info: Boot method: CD-ROM Image version: debian-bullseye-DI-alpha3-i386-netinst.iso Date: 14 January 2021 Machine: Toshiba Tecra 8000 Partitions: Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 110M 0 110M 0% /dev tmpfs tmpfs 25M 560K 24M 3% /run /dev/sda6 ext4 6.8G 1.1G 5.4G 17% / tmpfs tmpfs 121M 0 121M 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup /dev/sda2 ext4 95M 35M 53M 40% /boot tmpfs tmpfs 25M 0 25M 0% /run/user/1000 tmpfs tmpfs 25M 0 25M 0% /run/user/0 Disk /dev/sda: 7.63 GiB, 8195604480 bytes, 16007040 sectors Disk model: IBM-DYLA-28100 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000ce2ac Device Boot Start End Sectors Size Id Type /dev/sda1 * 63 208844 208782 101.9M b W95 FAT32 /dev/sda2208845 417689 208845 102M 83 Linux /dev/sda3417751 16000739 15582989 7.4G 5 Extended /dev/sda5417753 1461914 1044162 509.8M 82 Linux swap / Solaris /dev/sda6 1461978 16000739 14538762 6.9G 83 Linux Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [E] 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: [ ] Install boot loader:[O] Overall install:[O] Comments/Problems: Installed via debian-bullseye-DI-alpha3-i386-netinst.iso. Expert install via text using a RW-CD. Due to low memory, language and keyboard are US English, which is fine for me. The d-i kernel gets hung up for a while on "probing EDD". I haven't tried adding "edd=off" to the command line yet. For obvious reasons, d-i used low memory mode. Also, the installer is *slow*. If you must install on this machine, have patience. d-i does not detect the Ethernet card. This machine has a Netgear FA411 Ethernet card in a PCMCIA; it seems to like the axnet_cs driver. Even after I selected it in the menu, d-i didn't use it. It worked in Stretch. Once the installation was complete, all I had to do was add it to /etc/network/interfaces, and run "ifup eth0". However, it does not continue to work smoothly, so it may be a a hardware issue. I get a lot of dropped packets, frame errors, and errors on RX; none on TX. Misconfiguration of the Ethernet configuration??? I got an entirely bogus question about installing GRUB in the EFI fallback. Would a machine this old have EFI on it? According to d-i, the BIOS has corrupted hw-PMU resources (MSR-186 is 40002e). Whatever that means. The graphical installer bombed. I don't think it could launch X. I did not investigate. fdisk seems to think it has a floppy disk at fd0. It doesn't. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="11 (bullseye) - installer build 20201202" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux (none) 5.9.0-4-686 #1 SMP Debian 5.9.11-1 (2020-11-27) i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) [8086:7192] (rev 02) lspci -knn: Subsystem: Toshiba Corporation Satellite 4010 [1179:0001] lspci -knn: 00:04.0 VGA compatible controller [0300]: Neomagic Corporation NM2200 [MagicGraph 256AV] [10c8:0005] (rev 20) lspci -knn: Subsystem: Toshiba Corporation Device [1179:0001] lspci -knn: 00:05.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 02) lspci -knn: 00:05.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) lspci -knn: Kernel driver in use: ata_piix lspci -knn: Kernel modules: ata_piix, ata_generic lspci -knn: 00:05.2 USB controller [0c03]: Intel Corporation 82371AB/EB/MB PIIX4 USB [8086:7112] (rev 01) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:05.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB
