Re: Bug#1056169: bookworm-pu: package di-netboot-assistant/0.78~deb12u1
Hi Kibi, thank you for your comment and explanation! On Sat, Nov 18, 2023 at 10:11:33AM +0100, Cyril Brulebois wrote: > > […] > > The versioning seems a little weird. > > Usually: > - either one cherry-picks stuff on top of the stable package, and uses >0.76+deb12u1; > - or one ships a rebuild of the testing/unstable into stable, and uses >0.78~deb12u1 (adding a changelog entry on top of unstable's, >similarly to what would be done for backports). > > Glancing very briefly at the patch and the git tree, it seems like > you're doing the latter but versioning it like the former. I'll let > others comment as to whether that's some nitpicking that should be > ignored, or something they'd like to see adjusted. Ah, you are absolutely right, makes sense. I started with a 0.76+deb12u1 package, realized that cherry-picking ended up at 0.78, adjusted the version number … but I wasn't aware that the changelog should also be 'reset' to the one from 0.78 (which, I agree, makes perfectly sense). If needed, I can provide another upload. Thanks and best regards, Andi
Bug#1056169: bookworm-pu: package di-netboot-assistant/0.78~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: di-netboot-assist...@packages.debian.org, a...@debian.org
Control: affects -1 + src:di-netboot-assistant
[ Reason ]
With Bookworm, a few modifications have happened to the Debian Live ISO
images' meta data [1]. These changes make di-netboot-assistant
partially fail when bookworm ISO images are in use (the menus for the
network boot loaders like grub and iPXE are not generated properly).
The Live ISO images side has improved and stabilized [2], and also
di-netboot-assistant has been made more robust to account for these
modifications. In addition a few minor fixes to documentation and
examples (bookworm, preseed file) have been applied.
[1] https://lists.debian.org/debian-live/2023/06/msg00023.html
[2] https://lists.debian.org/debian-live/2023/07/msg00030.html
[ Impact ]
The inclusion of bookworm live ISO images fails.
[ Tests ]
I tested the changes with the 12.2.0 gnome, kde and standard ISOs.
Grub and iPXE menu.
[ Risks ]
There are almost no risks involved.
[ Checklist ]
[X] *all* changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in (old)stable
[X] the issue is verified as fixed in unstable
[ Changes ]
Mostly parsing latest meta data from the live images and more robust
handling of kernel/initrd (with/without version number).
[ Other info ]
I'll already upload the updated package.
The release team is doing a great job, thank you!
diff -Nru di-netboot-assistant-0.76/config/grub.cfg.HEAD
di-netboot-assistant-0.78~deb12u1/config/grub.cfg.HEAD
--- di-netboot-assistant-0.76/config/grub.cfg.HEAD 2023-03-16
17:05:12.0 +0100
+++ di-netboot-assistant-0.78~deb12u1/config/grub.cfg.HEAD 2023-06-18
09:11:47.0 +0200
@@ -18,7 +18,7 @@
set default='Boot from local disk..'
#set timeout=10
-if background_image
/d-i/n-pkg/images/11/amd64/text/debian-installer/amd64/boot-screens/splash.png;
then
+if background_image
/d-i/n-pkg/images/12/amd64/text/debian-installer/amd64/boot-screens/splash.png;
then
set color_normal=light-gray/black
set color_highlight=white/black
elif background_image /d-i/n-a/stable/amd64/boot-screens/splash.png; then
diff -Nru di-netboot-assistant-0.76/debian/changelog
di-netboot-assistant-0.78~deb12u1/debian/changelog
--- di-netboot-assistant-0.76/debian/changelog 2023-03-16 17:05:12.0
+0100
+++ di-netboot-assistant-0.78~deb12u1/debian/changelog 2023-06-18
09:11:47.0 +0200
@@ -1,3 +1,10 @@
+di-netboot-assistant (0.78~deb12u1) bookworm; urgency=medium
+
+ * Fixes for bookworm live iso image inclusion.
+ * Update/add/fix preseed examples. Thanks to Holger Wansing.
+
+ -- Andreas B. Mundt Sun, 18 Jun 2023 09:11:47 +0200
+
di-netboot-assistant (0.76) unstable; urgency=medium
* Fix typo in preseeding example.
diff -Nru di-netboot-assistant-0.76/di-netboot-assistant
di-netboot-assistant-0.78~deb12u1/di-netboot-assistant
--- di-netboot-assistant-0.76/di-netboot-assistant 2023-03-16
17:05:12.0 +0100
+++ di-netboot-assistant-0.78~deb12u1/di-netboot-assistant 2023-06-18
09:11:47.0 +0200
@@ -26,7 +26,7 @@
# -- Declare the constants --- #
PACKAGE_NAME=di-netboot-assistant
-PACKAGE_VERSION=0.76
+PACKAGE_VERSION=0.78
# -- Initialize the global variables - #
OFFLINE=false
@@ -253,8 +253,8 @@
# Returns: (EXIT STATUS) 0=Success, 1=Error
# #
prepare_grub() {
-local v="" opt=$1 VERS V GRUB AR DIR
-
+local v="" opt=$1 VERS V GRUB AR DIR
+
$VERBOSE && v="-v"
[ -z "$opt" ] && [ -d $TFTP_ROOT/$N_A_DIR/grub ] && return 0
@@ -263,7 +263,7 @@
[ ! -e "$TFTP_ROOT/debian-installer" ] && \
ln -srv $TFTP_ROOT/$N_A_DIR/ $TFTP_ROOT/debian-installer
-for AR in x64 aa64 ; do
+for AR in x64 aa64 ; do
## We link bootnet*.efi and grub*.efi from the latest available image:
echo "I: Preparing EFI executables for '${AR}'."
GRUB=""
@@ -533,7 +533,7 @@
EOF
sed -i "s%\(\# END_PKG_LIVE_MENU.*\)%item $tag $title\n\1%" menu.ipxe
-
+
for AR in amd64 arm64 ; do
gcfg="${TFTP_ROOT}/${relpath}/debian-installer/${AR}/grub/grub.cfg"
if [ -f "$gcfg" ] ; then
@@ -560,7 +560,7 @@
relpath=$(dirname "$x" | sed -e "s#${TFTP_ROOT}##" -e "s#^/*##" -e
"s#\/.disk##")
# shellcheck disable=SC2034
ISO_NAME=$(basename "$relpath")
-title=$(sed -e "s#Official ##" -e "s#T.*\$##" "$x")
+title="$(sed -e "s#Official ##" -e
Bug#1031643: some tests …
Hi, after trying some installs with the provided initrd from pu/bug-1031643, I observed the following: • The patch seems to work fine with 'hostname=somename' or 'hostname?=somename' added to the boot parameters: The question is not asked respectively by default set to 'somename'. • However, I also ran an installation with the original, unpatched initrd and the boot parameters: 'auto=true priority=critical hostname=somename url=tftp://192.168.122.1 playbook=minimal.yml ---' That works fine too. The pressed file is [1] with minor, unrelated changes. So that's kind of confusing to me right now. Best regards, Andi [1] https://salsa.debian.org/installer-team/netboot-assistant/-/blob/master/examples/preseed.cfg
Bug#1031643: bring hostname variable back
Hi, perhaps something like the following in [1] could be a fix: diff --git a/env2debconf b/env2debconf index 3032235..80394a4 100755 --- a/env2debconf +++ b/env2debconf @@ -3,6 +3,12 @@ set -e export DEBIAN_FRONTEND=none . /usr/share/debconf/confmodule + +if [ "$(hostname)" != '(none)' ]; then + # the hostname has been set as boot param, bring it back here + hostname="$(hostname)" +fi + I am not familiar with the code, but from checking the installer console right at the beginning of the installation, this could work. Best regards, Andi [1] https://salsa.debian.org/installer-team/preseed/-/blob/master/env2debconf
Bug#1033108: unblock: di-netboot-assistant/0.76
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: di-netboot-assist...@packages.debian.org, a...@debian.org
Control: affects -1 + src:di-netboot-assistant
Hi Release Team!
Please unblock package di-netboot-assistant
[ Reason ]
This upload fixes a few issues in examples and the documentation
provided by the package as well as the Salsa CI autopkgtest.
[ Impact ]
Users will end up with examples that do not work with bookworm.
[ Tests ]
All changes have been tested by me in two unrelated environments.
[ Risks ]
Almost none.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
[ Other info ]
Especially the changes in the example preseed file are due to the
bookworm release and surfaced recently. Many thanks for all your work!
unblock di-netboot-assistant/0.76
diff -Nru di-netboot-assistant-0.75/config/ipxemenu.HEAD
di-netboot-assistant-0.76/config/ipxemenu.HEAD
--- di-netboot-assistant-0.75/config/ipxemenu.HEAD 2022-12-21
20:49:44.0 +0100
+++ di-netboot-assistant-0.76/config/ipxemenu.HEAD 2023-03-16
17:05:12.0 +0100
@@ -30,7 +30,7 @@
:customized
kernel ${210:string}d-i/n-a/stable/amd64/linux initrd=initrd.gz \
locale?=de_DE mirror/http/proxy?=http://192.168.122.1:3142/ \
- pkgsel/include=etckeeper preseed/late_command="rm -fv /target/etc/
apt/apt.conf" ---
+ pkgsel/include=etckeeper preseed/late_command="rm -fv
/target/etc/apt/apt.conf" ---
initrd ${210:string}d-i/n-a/stable/amd64/initrd.gz
boot
diff -Nru di-netboot-assistant-0.75/debian/changelog
di-netboot-assistant-0.76/debian/changelog
--- di-netboot-assistant-0.75/debian/changelog 2022-12-21 20:49:44.0
+0100
+++ di-netboot-assistant-0.76/debian/changelog 2023-03-16 17:05:12.0
+0100
@@ -1,3 +1,11 @@
+di-netboot-assistant (0.76) unstable; urgency=medium
+
+ * Fix typo in preseeding example.
+ * Fix salsa CI package version check.
+ * Update preseeding example for bookworm.
+
+ -- Andreas B. Mundt Thu, 16 Mar 2023 17:05:12 +0100
+
di-netboot-assistant (0.75) unstable; urgency=medium
* Bump Standards-Version to 4.6.2 (no changes needed).
diff -Nru di-netboot-assistant-0.75/debian/tests/std-run
di-netboot-assistant-0.76/debian/tests/std-run
--- di-netboot-assistant-0.75/debian/tests/std-run 2022-12-21
20:49:44.0 +0100
+++ di-netboot-assistant-0.76/debian/tests/std-run 2023-03-16
17:05:12.0 +0100
@@ -1,9 +1,9 @@
-#!/bin/sh
+#!/usr/bin/bash
## Make sure package and script version are identical:
PV="$(dpkg-query -f='${Version}\n' -W di-netboot-assistant)"
SV="$(di-netboot-assistant -V | cut -d' ' -f2)"
-if [ "${PV%%~*}" != "$SV" ] ; then
+if [ "${PV%%[^.0-9]*}" != "$SV" ] ; then
echo "E: Version of package ($PV) and script ($SV) do not match!"
exit 1
else
diff -Nru di-netboot-assistant-0.75/di-netboot-assistant
di-netboot-assistant-0.76/di-netboot-assistant
--- di-netboot-assistant-0.75/di-netboot-assistant 2022-12-21
20:49:44.0 +0100
+++ di-netboot-assistant-0.76/di-netboot-assistant 2023-03-16
17:05:12.0 +0100
@@ -26,7 +26,7 @@
# -- Declare the constants --- #
PACKAGE_NAME=di-netboot-assistant
-PACKAGE_VERSION=0.75
+PACKAGE_VERSION=0.76
# -- Initialize the global variables - #
OFFLINE=false
diff -Nru di-netboot-assistant-0.75/examples/preseed.cfg
di-netboot-assistant-0.76/examples/preseed.cfg
--- di-netboot-assistant-0.75/examples/preseed.cfg 2022-12-21
20:49:44.0 +0100
+++ di-netboot-assistant-0.76/examples/preseed.cfg 2023-03-16
17:05:12.0 +0100
@@ -30,6 +30,10 @@
d-i debian-installer/locale string en_US
d-i keyboard-configuration/xkb-keymap select us
+## netcfg will choose an interface that has link if possible. This makes it
+## skip displaying a list if there is more than one interface:
+#d-i netcfg/choose_interface select auto
+
## Use hostname assigned by DHCP:
d-i netcfg/get_hostname string unassigned-hostname
d-i netcfg/get_domain string unassigned-domain
@@ -37,7 +41,13 @@
## Skip root account:
d-i passwd/root-login boolean false
+## If non-free firmware is needed for the network or other hardware, you can
+## configure the installer to always try to load it, without prompting. Or
+## change to false to disable asking.
+d-i hw-detect/load_firmware boolean true
+
### Apt setup
+d-i apt-setup/non-free-firmware boolean true
d-i apt-setup/non-free boolean true
d-i apt-setup/contrib boolean true
@@ -111,6 +121,8 @@
echo "ssh-rsa
B3NzaC1yc2EDAQABAAABAQC6tlRPOPBdxAJKLCNH+7S3fHhxzu64HViJQDFZbbI+Mbd+wwx6fe7ba1XZ8TXcFGmipHBYiOVaGMXIeJvGsEK3P1ULXNcNygrXl6HzjKDyL+iX3e7pls
Re: Re: Shim and secure boot status, leading up to bookworm
Hi Steve, On Wed, 25 Jan 2023 20:27:20 +, Steve McIntyre wrote: > On Wed, Jan 25, 2023 at 12:40:07PM -0700, Jeremy Hall wrote: > > > >When things get built, will there be a path forward for people who > >might need grub modules like serial console for accessibility reasons? > > The serial module has already been added to the signed grub binary a > while back (2.06-4). If you need anything else, please ask or file > bugs. I would like to draw your attention to: https://salsa.debian.org/grub-team/grub/-/merge_requests/14 https://bugs.debian.org/920610 For my use case, the inclusion of the http module would be appreciated. Thanks for all your work and looking forward to bookworm, Andi
Bug#1015203: can't reproduce issue
Control: tags -1 unreproducible Hi Martin-Éric, thanks for your bug report. I tried to reproduce your issue, but it works fine in my test setup. I installed di-netboot-assistant and created '/var/lib/tftpboot/'. Then I ran: 'di-netboot-assistant install stable' and finally removed the package with: 'apt purge di-netboot-assistant'. No errors, an empty '/var/lib/tftpboot/d-i/' remains, all other stuff (i.e. the n-a directory) is removed. Can you test again and provide more details about your scenario? Is there anything special in your setup? Thanks, Andi
Bug#949655: Solved: not a bug, just a wrong iPXE usage
Hi Yvan,
On Fri, Jan 24, 2020 at 09:49:06AM +0100, Yvan Masson wrote:
>
> I finally found on iPXE website[1] a link to detailed examples, including
> one[2] to boot pxelinux. It works perfectly with di-netboot-assistant:
>
> #!ipxe
> dhcp
> set 210:string tftp://my_server/d-i/n-a/
> chain ${210:string}pxelinux.0
>
> For those who did not know (like me :-)), 210 is a standard DHCP option
> called "path prefix"[3].
>
> I still believe it would be interesting to add this simple example to the
> di-netboot-assistant.
>
Many thanks for your report! I implemented something along your
suggestion in the latest di-netboot-assistant package. Just let me
know if you have other suggestions and/or something works not as
expected. (I am not regularly using iPXE).
Best regards,
Andi
Re: FTBFS on armhf
Hi Kibi,
sorry for answering so late: Your eMail ended up here in my
mailing-lists-foulder which I did not follow/read lately. (I have to
fix my sieve, probably. I justs found it more or less by accident,
but already commited a fix (hopefully) now.
Thanks and best regards,
Andi
On Mon, Oct 07, 2019 at 08:27:49AM +0200, Cyril Brulebois wrote:
> Hi Andreas,
>
> This seems buggy:
> | commit 0ec980b6ad0111da4e43935c069b378529d8fba1
> | Author: Andreas B. Mundt
> | Date: Sun Oct 6 17:38:53 2019 +0200
> |
> | Add support for Olimex A20-OLinuXino-Lime2-eMMC.
>
> as it duplicates an existing entry without changing its name, leading to
> an FTBFS in daily builds:
> | BUILDING IMAGE FOR build_u-boot
> |
> | debian-installer git tree head: 0ec980b6ad0111da4e43935c069b378529d8fba1
> | mkdir -p ./dest/u-boot//
> | set -e; while read LINE; \
> | do \
> | if [ -n "${LINE}" ] && ! echo ${LINE}|grep -q -e "^#"; then \
> | set -- ${LINE}; \
> | mkdir -p "./dest/u-boot//$1"; \
> | if [ -n "$2" ]; then \
> | echo "Providing u-boot binaries for $1 ..."; \
> | cp "$2" "./dest/u-boot//$1/"; \
> | dd 2>/dev/null if="$2" of="./dest/u-boot//$1/$1.sdcard.img" bs=512
> seek="$3"; \
> | gzip -9 -n "./dest/u-boot//$1/$(basename $2)"; \
> | fi; \
> | if [ -n "$4" ]; then \
> | cp "$4" "./dest/u-boot//$1/"; \
> | dd 2>/dev/null if="$4" of="./dest/u-boot//$1/$1.sdcard.img" bs=512
> seek="$5" conv=notrunc; \
> | gzip -9 -n "./dest/u-boot//$1/$(basename $4)"; \
> | fi; \
> | gzip -9 -n "./dest/u-boot//$1/$1.sdcard.img"; \
> | update-manifest "./dest/u-boot/$1" "u-boot image for $1"; \
> | fi ;\
> | done < boot/arm/u-boot-image-config
> | Providing u-boot binaries for MX53LOCO ...
> | Providing u-boot binaries for MX6_Cubox-i ...
> | Providing u-boot binaries for Wandboard ...
> | Providing u-boot binaries for Novena ...
> | Providing u-boot binaries for BeagleBoneBlack ...
> | Providing u-boot binaries for PandaBoard ...
> | Providing u-boot binaries for BeagleBoard-X15 ...
> | Providing u-boot binaries for A10-OLinuXino-Lime ...
> | Providing u-boot binaries for A20-Olimex-SOM-EVB ...
> | Providing u-boot binaries for A20-OLinuXino-Lime ...
> | Providing u-boot binaries for A20-OLinuXino-Lime2 ...
> | Providing u-boot binaries for A20-OLinuXino-Lime2 ...
> | gzip: ./dest/u-boot//A20-OLinuXino-Lime2/u-boot-sunxi-with-spl.bin.gz
> already exists; not overwritten
> | make[2]: *** [config/armhf//u-boot.cfg:9: u-boot-binaries] Error 2
> | make[1]: *** [Makefile:298: _build] Error 2
> | make: *** [Makefile:292: build_u-boot] Error 2
>
> (I'm not familiar with the whole u-boot thing though, so I might have
> missed something while glancing over the changes and log.)
>
> Full logs available as usual on d-i.d.o:
> https://d-i.debian.org/daily-images/daily-build-overview.html#armhf
>
>
> Cheers,
> --
> Cyril Brulebois (k...@debian.org)<https://debamax.com/>
> D-I release manager -- Release team member -- Freelance Consultant
--
GPG key: 4096R/617B586D 2010-03-22 Andreas B. Mundt--
Andreas B. Mundt--
Andreas B. Mundt--
Andreas B. Mundt--
938A 5CEE 1E29 0DE2 55D9 AC98 B01F EA84 617B 586D
signature.asc
Description: PGP signature
Bug#911560: possible fix / workaround
Control: tags -1 patch Hi all, I tried to boot a 'Olimex A20 Lime 2 Rev. K' too, and as reported, the ethernet PHY seems not to be initialized well and fails to work at all. Following the advice of the sunxi wiki [1], recompiling u-boot with the proposed patch [2] fixed this: Ethernet works in u-boot as well as in the installer with the patched u-boot. No idea if this patch spoils the other revisions. Best regards, Andi [1] https://linux-sunxi.org/Olimex_A20-OLinuXino-Lime2#GMAC_u-boot_config [2] diff --git a/configs/A20-OLinuXino-Lime2-eMMC_defconfig b/configs/A20-OLinuXino-Lime2-eMMC_defconfig index 7e48328290..08a7207652 100644 --- a/configs/A20-OLinuXino-Lime2-eMMC_defconfig +++ b/configs/A20-OLinuXino-Lime2-eMMC_defconfig @@ -38,3 +38,4 @@ CONFIG_USB_EHCI_HCD=y CONFIG_USB_OHCI_HCD=y CONFIG_USB_MUSB_GADGET=y CONFIG_SYS_USB_EVENT_POLL_VIA_INT_QUEUE=y +CONFIG_GMAC_TX_DELAY=3
Bug#926795: di-netboot-assistant: Unable to install Debian Buster amd64 from d-i n-a at 2019-04-10 generated boot-file
Control: reassign -1 debian-installer Control: forcemerge 749991 -1 Hi Ralf, many thanks for your report! On Wed, Apr 10, 2019 at 04:06:43PM +0200, Ralf Moll wrote: […] > the "Debian testing (amd64) image 20190410", generated by > > di-netboot-assistant install stable testing > > shows after answering a few installer querstions the following dialog: > > "[!!] Download installer components > > No kernel modules were found. This probably is due to a mismatch between > the kernel used by this version of the Installer and the kernel version > available in the archive. > >[…] > > No matter what I select, the installer will fail. > > Seems kernel and mirror are out of sycn... Yes, exactly. The issue is well-known, reported and discussed in bug #749991 [1]. There is nothing di-netboot-assistant can do about it. I recommend to try the daily image, for me that worked a few days ago (201904040, but that seems not always to be the case [2]) or to wait for an updated debian installer release. Best regards, Andi [1] https://bugs.debian.org/749991 [2] https://bugs.debian.org/749991#181
Bug#925084: di-netboot-assistant: debian-installer-xxx-netboot-yyy are wrongly configured
Control: tags + unreproducible moreinfo Hi Jérémy, On Tue, Mar 19, 2019 at 07:43:47PM +0100, Jérémy Viès wrote: […] > I get a "No DEFAULT or UI configuration directive found!" when the PXE client > boots on one of these installer. I cannot reproduce the problem you reported. It works fine here, also with the packaged installer. Can you check if the installer is available in '/var/lib/tftpboot/d-i/n-pkg/' (or your corresponding TFTP-root)? Thanks and best regards, Andi
Bug#925084: di-netboot-assistant: debian-installer-xxx-netboot-yyy are wrongly configured
Hi Jérémy, many thanks for your feedback! On Tue, Mar 19, 2019 at 07:43:47PM +0100, Jérémy Viès wrote: > > I've just discovered and then set-up di-netboot-assistant to manage several > debian netboot versions. > It works great when it manages setup di-netboot-assistant installed by itself, > but it fails to configure correctly already installed installers from official > packages. > I get a "No DEFAULT or UI configuration directive found!" when the PXE client > boots on one of these installer. I am just setting up an up-to-date test environment to reproduce the error. Just to make sure: Did you bind mount the packaged installer images as decribed in the README [1]: … Using packaged debian-installer images -- You can also use the images provided by the debian-installer-*-netboot-* packages. 1. Install the needed debian-installer-*-netboot-* packages. 2. Bind mount or copy '/usr/lib/debian-installer/' to your tftp root directory: mount --bind /usr/lib/debian-installer/ $TFTP_ROOT/d-i/n-pkg/ To make this persistent, add the following line to '/etc/fstab': /usr/lib/debian-installer/ $TFTP_ROOT/d-i/n-pkg/ none bind 0 0 3. Add the corresponding menu entries to the boot menu by running: di-netboot-assistant -v rebuild-menu Best regards, Andi [1] /usr/share/doc/di-netboot-assistant/README.gz
Bug#923460: di-netboot-assistant: selecting tftp folder from command line
Hi Yves-Alexis, On Thu, Feb 28, 2019 at 02:11:48PM +0100, Yves-Alexis Perez wrote: > > I'd like to setup some netboot images for serving over PXE, storing > stuff in /var/lib/tftp is not practical for me. I'd like to be able to > specify the target directory from the command line, but it's apparently > not possible for now so I'm opening a wishlist bug. I already draft-implemented this, seems to be pretty simple (and indeed usefull): https://salsa.debian.org/installer-team/netboot-assistant/commit/df7f7d6cb29add2f0f2d05800a19aaa76b95ca95 It needs some testing and I would like to do a bit general package polishing, but maybe we can still get this into buster (I have to check the deadlines). So, if you find time, please test and report back as soon as possible. Thanks and best regards, Andi
Bug#902423: debian-installer: clean up arm64/armhf configuration
Hi Karsten, many thanks for your thorough explanations. I got a bit further in my understandings, however the next days I am busy elsewhere, and I do not know if I find time to continue and present something more mature, perhaps during DebCamp. Anyway, just wanted to show my appreciation for your suggestions, tests and explanations. Thanks again and best regards, Andi
Bug#902423: debian-installer: clean up arm64/armhf configuration
Package: debian-installer Severity: wishlist Hi all, as a follow-up on #902020, I looked into the build process of armhf installation media. As I am not very familliar with the build process and the history of the different components, I would like to post some observations and a draft patch addressing some but not all issues here. It might perhaps be helpful for someone with more insight to clean up the code. The draft patch moves most of the stuff done from the armhf netboot configuration in 'build/config/armhf/netboot.cfg' to the more general 'build/config/arm.cfg'. However there are still some issues I do not understand: • Both 'build/config/armhf/netboot.cfg' and 'build/config/armhf/hd-media.cfg' contain the same recipe code in the 'netboot_images_concatenateable' and respectively the 'hd-media_images_concatenateable' target. • The use of GRUB and U-Boot is not clear to me. armhf seems to use GRUB for the miniiso but U-Boot for all other media. GRUB is referencing the kernel under '…/linux', U-BOOT prefers '…/vmlinuz'. Best regards, Andi diff --git a/build/config/arm.cfg b/build/config/arm.cfg index 28d81e37f..f687af48c 100644 --- a/build/config/arm.cfg +++ b/build/config/arm.cfg @@ -10,6 +10,13 @@ ifeq ($(GRUB_EFI),y) efi-image $(TEMP_GRUB_EFI) $(GRUB_PLATFORM) $(GRUB_EFI_NAME) $(NETBOOT_PATH) endif +.PHONY: netboot_ubootscript_tftp +netboot_ubootscript_tftp: +ifeq ($(UBOOT),y) + mkimage -T script -A arm -d boot/arm/bootscr.tftpboot $(SOME_DEST)/$(EXTRANAME)tftpboot.scr + update-manifest $(SOME_DEST)/$(EXTRANAME)tftpboot.scr "TFTP boot script for mainline u-boot (>= v2014.10)" +endif + # Supply GRUB EFI configuration. .PHONY: arch_cd_info_dir arch_cd_info_dir: arm_grub_efi @@ -54,9 +61,7 @@ arch_miniiso: arm_grub_efi cp -a $(GRUB_FONT) $(TEMP_CD_TREE)/boot/grub/font.pf2; \ cp -a $(TEMP_GRUB_EFI)/boot/grub/$(GRUB_PLATFORM)/* \ $(TEMP_CD_TREE)/boot/grub/$(GRUB_PLATFORM)/; \ - fi - - if [ "$(GRUB_EFI)" = y ]; then \ + \ xorriso -as mkisofs -r -J -c boot.cat \ -boot-load-size 4 -boot-info-table \ -eltorito-alt-boot \ @@ -65,14 +70,14 @@ arch_miniiso: arm_grub_efi fi .PHONY: arch_netboot_dir -arch_netboot_dir: arm_grub_efi +arch_netboot_dir: arm_grub_efi netboot_ubootscript_tftp -rm -f $(TEMP_NETBOOT_DIR) mkdir -p $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH) - cp $(TEMP_KERNEL) $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/linux cp $(TEMP_INITRD) $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/initrd.gz - if [ "$(GRUB_EFI)" = y ]; then \ + if [ "$(GRUB_EFI)" = y ] && [ "$(UBOOT)" = n ]; then \ set -e; \ + cp $(TEMP_KERNEL) $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/linux; \ mkdir -p $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/grub/$(GRUB_PLATFORM); \ cp -a $(TEMP_GRUB_EFI)/bootnet$(GRUB_EFI_NAME).efi $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH); \ cp -a $(GRUB_FONT) $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/grub/font.pf2; \ @@ -84,3 +89,11 @@ arch_netboot_dir: arm_grub_efi HEADER boot/$(ARCH)/grub/grub-efi.cfg \ > $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/grub/grub.cfg; \ fi + + if [ "$(UBOOT)" = y ]; then \ + set -e; \ + cp $(TEMP_KERNEL) $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/vmlinuz; \ + cp -r $(TEMP_DTBS) $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/dtbs/; \ + cp $(SOME_DEST)/$(EXTRANAME)tftpboot.scr $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH); \ + ( cd $(TEMP_NETBOOT_DIR); ln -s $(NETBOOT_PATH)/tftpboot.scr boot.scr.uimg ) \ + fi diff --git a/build/config/arm64.cfg b/build/config/arm64.cfg index d9e782df9..de4a89628 100644 --- a/build/config/arm64.cfg +++ b/build/config/arm64.cfg @@ -9,6 +9,8 @@ GRUB_EFI=y GRUB_PLATFORM=arm64-efi GRUB_EFI_NAME=aa64 +UBOOT=n + arch_boot_screens: arch_tree: diff --git a/build/config/armhf.cfg b/build/config/armhf.cfg index 598644460..d7a76debe 100644 --- a/build/config/armhf.cfg +++ b/build/config/armhf.cfg @@ -11,6 +11,8 @@ GRUB_EFI=y GRUB_PLATFORM=arm-efi GRUB_EFI_NAME=arm +UBOOT=y + arch_boot_screens: arch_tree: diff --git a/build/config/armhf/netboot.cfg b/build/config/armhf/netboot.cfg index 93ea03870..077df1ef4 100644 --- a/build/config/armhf/netboot.cfg +++ b/build/config/armhf/netboot.cfg @@ -1,60 +1,9 @@ MEDIA_TYPE = netboot image -CONCATENATEABLE_SUFFIX = -TFTP_INSTALLER_PATH = debian-installer/armhf/ - -TARGET = $(KERNEL) $(INITRD) $(MINIISO) netboot_bootscript_sd netboot_bootscript_tftp netboot_tarball netboot_images_concatenateable - +NETBOOT_DIR_TARGETS = $(TEMP_INITRD) $(TEMP_KERNEL) $(TEMP_DTBS) +TARGET = $(NETBOOT_DIR) $(NETBOOT_TAR) $(MINIISO) EXTRANAME = $(MEDIUM)/ -MANIFEST-INITRD = "netboot initrd" -MANIFEST-KERNEL = "kernel image to netboot"
Bug#902020: debian-installer: netboot.tar.gz archives should have identical structure, include version.info file
Control: tag -1 pending Hi Cyril, On Fri, Jun 22, 2018 at 04:50:28PM +0200, Cyril Brulebois wrote: > Andreas B. Mundt (2018-06-22): > > Thanks for pointing me in the right direction. I worked out a minimal > > patch that fixes the issue. > > From a quick look, that should be fine; feel free to push (with a > changelog entry), thanks! Done! […] > > Perhaps this can be unified, but I guess to do that, someone more > > familiar with the build system is needed. > > Possibly because we used to have several flavours (mx5, armmp, etc.), > until everything was moved to the top-level? See git log -M --follow for > earlier filenames. > > I think we should merge your minimal patch right away, and maybe think > about unifying as you suggested if someone has some time/interest. ;) Thanks for the suggestions, I'll explore a bit more and then let's see… Best regards, Andi
Bug#902020: debian-installer: netboot.tar.gz archives should have identical structure, include version.info file
Control: tag -1 patch Hi Cyril, On Thu, Jun 21, 2018 at 06:48:34PM +0200, Cyril Brulebois wrote: > > Severity: wishlist > > Tags: d-i > > (No need for this tag for d-i and debs/udebs maintained by debian-boot@; > we tend to use it for pieces not directly linked to us.) Ah, thanks for info and fix! > > > > Including the 'version.info' would ease handling all archives > > automatically in the same way (for example in 'di-netboot-assistant'). > > Right, it seems armhf has its particular way of generating the netboot > tarball (build/config/armhf/netboot.cfg) instead of using variables as > that seems to be done for other architectures. See its netboot_tarball > target. Thanks for pointing me in the right direction. I worked out a minimal patch that fixes the issue. However, it would be interesting to know why armhf uses its own individual way, no other architecture seems to do that: /debian-installer$ ls -l build/config/*/netboot.cfg -rw-r--r-- 1 ansible ansible 279 Jun 21 21:34 build/config/alpha/netboot.cfg -rw-r--r-- 1 ansible ansible 430 Jun 21 21:34 build/config/amd64/netboot.cfg -rw-r--r-- 1 ansible ansible 337 Jun 21 21:34 build/config/arm64/netboot.cfg -rw-r--r-- 1 ansible ansible 3369 Jun 21 23:13 build/config/armhf/netboot.cfg -rw-r--r-- 1 ansible ansible 238 Jun 21 21:34 build/config/hppa/netboot.cfg -rw-r--r-- 1 ansible ansible 367 Jun 21 21:34 build/config/hurd-i386/netboot.cfg -rw-r--r-- 1 ansible ansible 430 Jun 21 21:34 build/config/i386/netboot.cfg -rw-r--r-- 1 ansible ansible 369 Jun 21 21:34 build/config/ia64/netboot.cfg -rw-r--r-- 1 ansible ansible 919 Jun 21 21:34 build/config/m68k/netboot.cfg -rw-r--r-- 1 ansible ansible 261 Jun 21 21:34 build/config/ppc64el/netboot.cfg -rw-r--r-- 1 ansible ansible 545 Jun 21 21:34 build/config/sparc64/netboot.cfg -rw-r--r-- 1 ansible ansible 545 Jun 21 21:34 build/config/sparc/netboot.cfg Perhaps this can be unified, but I guess to do that, someone more familiar with the build system is needed. Best regards, Andi diff --git a/build/config/armhf/netboot.cfg b/build/config/armhf/netboot.cfg index fd5f6f3a2..93ea03870 100644 --- a/build/config/armhf/netboot.cfg +++ b/build/config/armhf/netboot.cfg @@ -29,12 +29,14 @@ netboot_bootscript_tftp: netboot_tarball: $(KERNEL) $(INITRD) $(TEMP_DTBS) netboot_bootscript_tftp rm -rf $(TEMP)/netboot_tarball mkdir -p $(TEMP)/netboot_tarball/$(TFTP_INSTALLER_PATH) + echo 'Debian version: $(DEBIAN_VERSION)' > $(TEMP)/netboot_tarball/version.info + echo 'Installer build: $(BUILD_DATE)' >> $(TEMP)/netboot_tarball/version.info cp $(KERNEL) $(TEMP)/netboot_tarball/$(TFTP_INSTALLER_PATH)vmlinuz cp $(INITRD) $(TEMP)/netboot_tarball/$(TFTP_INSTALLER_PATH)initrd.gz cp -r $(TEMP_DTBS) $(TEMP)/netboot_tarball/$(TFTP_INSTALLER_PATH)dtbs/ cp $(SOME_DEST)/$(EXTRANAME)tftpboot.scr $(TEMP)/netboot_tarball/$(TFTP_INSTALLER_PATH) ( cd $(TEMP)/netboot_tarball; ln -s $(TFTP_INSTALLER_PATH)tftpboot.scr boot.scr.uimg ) - tar -C $(TEMP)/netboot_tarball/ -zcf $(SOME_DEST)/$(EXTRANAME)netboot.tar.gz $(TFTP_INSTALLER_PATH)tftpboot.scr $(TFTP_INSTALLER_PATH)initrd.gz $(TFTP_INSTALLER_PATH)vmlinuz $(TFTP_INSTALLER_PATH)dtbs/ boot.scr.uimg + tar -C $(TEMP)/netboot_tarball/ -zcf $(SOME_DEST)/$(EXTRANAME)netboot.tar.gz ./$(TFTP_INSTALLER_PATH)tftpboot.scr ./$(TFTP_INSTALLER_PATH)initrd.gz ./$(TFTP_INSTALLER_PATH)vmlinuz ./$(TFTP_INSTALLER_PATH)dtbs/ ./boot.scr.uimg ./version.info .PHONY: netboot_images_concatenateable netboot_images_concatenateable: $(KERNEL) $(INITRD) $(TEMP_DTBS) netboot_bootscript_sd
Bug#902020: debian-installer: netboot.tar.gz archives should have identical structure, include version.info file
Package: debian-installer Severity: wishlist Tags: d-i Hi, when comparing netboot.tar.gz images for different architectures, I noticed a difference in the structure of the archives. For the armhf netboot archive [1], I get: $ tar tzf netboot_armhf.tar.gz debian-installer/armhf/tftpboot.scr debian-installer/armhf/initrd.gz debian-installer/armhf/vmlinuz debian-installer/armhf/dtbs/ […] debian-installer/armhf/dtbs/am335x-baltos-ir5221.dtb debian-installer/armhf/dtbs/am335x-baltos-ir3220.dtb debian-installer/armhf/dtbs/am335x-baltos-ir2110.dtb boot.scr.uimg For the amd64 achive [2] (the same for i386 with s/amd64/i386/, but also for arm64 with s/amd64/arm64/): $ tar tzf netboot_amd64.tar.gz ./ ./debian-installer/ ./debian-installer/amd64/ ./debian-installer/amd64/boot-screens/ ./debian-installer/amd64/boot-screens/adtxt.cfg […] ./debian-installer/amd64/initrd.gz ./debian-installer/amd64/linux ./debian-installer/amd64/pxelinux.0 ./debian-installer/amd64/pxelinux.cfg/ ./debian-installer/amd64/pxelinux.cfg/default ./ldlinux.c32 ./pxelinux.0 ./pxelinux.cfg ./version.info Note the absent './'-directory in the armhf archive paths as well as the missing 'version.info'. The first issue is relevant when unpacking the archives with '--strip-components=X', where armhf needs X-1 compared to amd64/arm64/i386. Including the 'version.info' would ease handling all archives automatically in the same way (for example in 'di-netboot-assistant'). Thanks and best regards, Andi [1] wget https://deb.debian.org/debian/dists/stable/main/installer-armhf/current/images/netboot/netboot.tar.gz -O netboot_armhf.tar.gz [2] wget https://cdn-aws.deb.debian.org/debian/dists/stable/main/installer-amd64/current/images/netboot/netboot.tar.gz -O netboot_amd64.tar.gz
Accepted di-netboot-assistant 0.52 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 18 Mar 2018 18:17:54 +0300 Source: di-netboot-assistant Binary: di-netboot-assistant Architecture: source all Version: 0.52 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team <debian-boot@lists.debian.org> Changed-By: Andreas B. Mundt <a...@debian.org> Description: di-netboot-assistant - Debian-Installer netboot assistant Closes: 789247 892800 892803 Changes: di-netboot-assistant (0.52) unstable; urgency=medium . * Fix di-netboot-assistant when '$HOME' is not set (closes: #892800). * Replace REGEX by correct URLs in the 'di-sources.list' file. (Closes: #789247). * Add option to ignore image signature check failures. (Closes: #892803). * Take new syntax for 'menu.c32' into account. * Bump dh compat level to 11 (no changes needed). Checksums-Sha1: 3fc57167e571d4397035dd33957a100ae3213d20 1896 di-netboot-assistant_0.52.dsc 6cc7865b220e0ba3ea10d6443c391fe680cdb55e 38656 di-netboot-assistant_0.52.tar.xz f0261799071c446716eff12de92b560673977494 40256 di-netboot-assistant_0.52_all.deb 9d94877f541e4d35980eb7044afd5df4301b4e1f 5421 di-netboot-assistant_0.52_amd64.buildinfo Checksums-Sha256: e132267db72809de31ea38a86e29b887ba29f26f4bb814f82e6efd321c6d15b8 1896 di-netboot-assistant_0.52.dsc 4d54325c641fa2d8ff5eab25438b50ce0a2eb027c1489a79c9efd3aba072cda8 38656 di-netboot-assistant_0.52.tar.xz bc6483c0575b1639a0483b3d23e79d94df2f2aa2b9f11cfb46894b6a3571d22f 40256 di-netboot-assistant_0.52_all.deb a342a54d43a1927e8dba59a2c8b26e74e91716cd21af8bde1bc5d37ec317f4eb 5421 di-netboot-assistant_0.52_amd64.buildinfo Files: 9f40cb2eccae8baff38c0918be98cdb2 1896 utils optional di-netboot-assistant_0.52.dsc 003df85e54980b4d5fc871e029cfadc1 38656 utils optional di-netboot-assistant_0.52.tar.xz c6e7969a453df85e01be4aca245952b4 40256 utils optional di-netboot-assistant_0.52_all.deb 78289253b160acd61ac1a6169fb87d27 5421 utils optional di-netboot-assistant_0.52_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEEk4pc7h4pDeJV2ayYsB/qhGF7WG0FAlquhBkQHGFuZGlAZGVi aWFuLm9yZwAKCRCwH+qEYXtYbW5UEACE8LtKNriQ/Dai9OuJ6EjbcumOrAtvRfX4 PGdEQunlAu8LGt7TAE3vHJz6rsVq3pLY0icSCylmtTbWNUQleL9UwrfCGfOUiqL2 5jm/zVdhYSjILNvUnyn1QpSml7MZTeFNHigzmxEnw36wUcjD6MQvn5jVsFJKzvV5 AEtpeSeUfoc3khYJ+zvBAmDtDCV1/VlXzPH9Iuk7QYBCnvxm/oHesShsfthyFIwT 7woeAn4grIanmB+qBIeo+ICKljFrEGnrHQS+/Ox1c7dYcazJ/+TiPTzyXAdZxF6x BRduWArsXJufg90DbcYxT2wNICUvHrO6fk6xnTg5B9Wh93ulQtxKVyAy/yAvk4mp eL3UIIfAxwVXFq6s868zlij3tRzsmy5cqrTBcdNtjxbggJ1JvqU4zUb4kRjoX/UV if9plyvKNyf1kxuhMhedHpDddN7KrIDJ0PCb+IxvksfAYcT0KEgVjpGPsy54Gpqv d/Qjdqn8aTaychMBSg/Xkjo2ar6EppZHDfYw+w/7WpaiserNP3CmgPKCBV1QvvFA 9ASzct7j4qXqiz/ZwGESgcyn6adpYMpb1e1HRmBE2XtaUMzNvFJAa0ytSLF/ATeC u1RbT+TaX4g5wBH8AbS0ny0WHGqC1BKew2I/NempXhfICmMh+kbklR1UyEMqEsvL GElmTB5jFg== =1yFr -END PGP SIGNATURE-
Bug#789247: di-netboot-assistant: broken deb.d.o urls
Hi, On Fri, Mar 09, 2018 at 01:20:14PM -0800, Matt Taggart wrote: > It looks like the deb.debian.org URLs in di-sources.list need to be updated > > E: Can't download 'stretch' for 'amd64' > (http://deb.debian.org/dists/stretch/main/installer-amd64/current/images/MD5SUMS). > > The URL should have a leading 'debian/' in the path, ie > > http://deb.debian.org/dists/stretch/main/installer... > > I don't know if this is just some mirrors or everywhere, but not having it > resulted in an error for me (it resolved to cdn-aws.deb.debian.org) Hm, the /debian/ should be inserted by the following in '/etc/di-netboot-assistant/di-netboot-assistant.conf' [1]: #Download Mirror # The variable MIRROR_REGEXPS contain a list of space separated sed # regular expression, to rewrite di-sources.list URLs, to match your # prefered mirror. For example: MIRROR_REGEXPS="s=://deb.debian.org/=://deb.debian.org/debian/=" I was already wondering why not to use the correct URL in 'di-sources.list', but kept that as it works fine for me. Can you check if you have the line in 'di-netboot-assistant.conf'? Perhaps it's there for historical reasons and we can/should remove it. Best regards, Andi [1] https://anonscm.debian.org/cgit/d-i/netboot-assistant.git/tree/config/di-netboot-assistant.conf
Re: Re: Changing di-netboot-assistants directory within the TFTP-root
Hello Hermann, On Tue, Dec 19, 2017 at 12:57:41PM +0100, Hermann Lauer wrote: > On Mon, Dec 18, 2017 at 04:21:05PM +0300, Andreas B. Mundt wrote: […] > > In di-netboot-assistant, a grub-EFI image is prepared which then > > includes the grub.conf files of the debian-installer images, with the > > correct paths. You get an idea in [3]. Perhaps you can follow this > > approach (or even better: use di-netboot-assistant) too. > > Thanks a lot, I was not aware of grub-mknetdir (and di-netboot-assistant's > menu building) so far. > OTOH, this still not answers the question if any functionality using paths > relative to the > bootnetx64.efi is available in grub. > > Should I open a bug report against grub or do you have another idea ? When I set up di-netboot-assistant to work for EFI installs, I also tried for some time to use the netboot image's grub, but, if I remember correctly, it only worked to some extent with the buster images, not with stretch. After that I went for the more flexible solution implemented now with an independent grub-EFI image. However, I am not sure if I saw the same issue you describe. I am not sure towards which package to report the bug. In my case I think it's the configuration of the grub-EFI image used in the netboot image, but I did not dive much into the issue. If nobody more familiar with the netboot-grub-EFI stuff replies here, you could either try to reach someone from the team setting up the netboot images directly (perhaps also on IRC). Maybe you could post your first mail (the one that did not make it to the list) with a good subject and as much details as possible again (it's not clear to me what exactly goes wrong, i.e. TFTP server layout/configuration would be helpful). Right now our involved discussion will not be recognized eventually. If you are sure that it's a bug in grub, it should be reported to the BTS. Unfortunately, I have now and also in the next weeks rather limited time to set up a test system and explore the issue further. Hmm, could you try with buster images and see if the problem persists? Best regards, Andi
Re: Changing di-netboot-assistants directory within the TFTP-root
Hello Hermann, On Mon, Dec 18, 2017 at 12:03:02PM +0100, Hermann Lauer wrote: > On Sun, Dec 17, 2017 at 05:22:57PM +0300, Andreas B. Mundt wrote: > > Hi everybody, > > > > I plan to move di-netboot-assistant's directory within the TFTP-root. > > > > Right now, '$TFTP_ROOT/debian-installer/' is used to set up and serve > > the netboot-images. If you also serve preseedings from the canonical > > just wondering if this is the default location or the only supported > location for network installs. > Please see also the email attached which seems not to have hit the list > about grub not obeying an initial path send with dhcp. > > Thanks and sorry if I misunderstood something here, > greetings Do you use di-netboot-assistant [1] or just the debian-installer netboot packages/images [2]? […] > > when doing network installation with the files from > debian/dists/stretch/main/installer-amd64/current/images/netboot/netboot.tar.gz > grub didn't find it's files if using a nonstandard tftp server layout: > > RRQ from 129.206.106.247 filename > /debian/amd64_stretch/debian-installer/amd64/bootnetx64.efi > tftp: client does not accept options > RRQ from 129.206.106.247 filename > /debian/amd64_stretch/debian-installer/amd64/bootnetx64.efi > RRQ from 129.206.106.247 filename > debian-installer/amd64/grub/x86_64-efi/command.lst > RRQ from 129.206.106.247 filename > debian-installer/amd64/grub/x86_64-efi/fs.lst > RRQ from 129.206.106.247 filename > debian-installer/amd64/grub/x86_64-efi/crypto.lst > RRQ from 129.206.106.247 filename > debian-installer/amd64/grub/x86_64-efi/terminal.lst > RRQ from 129.206.106.247 filename debian-installer/amd64/grub/grub.cfg > > PXE BIOS with pxelinux has no problems with finding it's files in such a > layout. > Is there any functionality in grub to enable relative pathes at that point of > the debian > installation ? If not, is that a bug/regression to report against grub ? In di-netboot-assistant, a grub-EFI image is prepared which then includes the grub.conf files of the debian-installer images, with the correct paths. You get an idea in [3]. Perhaps you can follow this approach (or even better: use di-netboot-assistant) too. On the other hand, if you are already talking about a problem with di-netboot-assistant, we should open a bug against di-netboot-assistant and take a closer look at what went wrong. I only tested the grub-EFI stuff in di-netboot-assistant within a virtual machine setup, as I currently have no EFI system around. Best regards, Andi [1] <URL:https://wiki.debian.org/DebianInstaller/NetbootAssistant> [2] <URL:https://packages.debian.org/stretch/debian-installer-9-netboot-amd64> [3] <URL:https://anonscm.debian.org/cgit/d-i/netboot-assistant.git/tree/di-netboot-assistant#n239>
Changing di-netboot-assistants directory within the TFTP-root
Hi everybody, I plan to move di-netboot-assistant's directory within the TFTP-root. Right now, '$TFTP_ROOT/debian-installer/' is used to set up and serve the netboot-images. If you also serve preseedings from the canonical location '$TFTP_ROOT/d-i/', you have a slightly confusing setup. The plan is to use 'd-i/n-a/' for di-netboot-assistant, to have all installer stuff within the common '$TFTP_ROOT/d-i/' directory. Any objections to move in that direction? Best Regards, Andi
Bug#776565: preparing nmu for di-netboot-assistant
Hi KiBi, On Tue, Feb 03, 2015 at 11:26:21AM +0100, Cyril Brulebois wrote: Andreas B. Mundt a...@debian.org (2015-02-03): OK, I'll keep that in mind. (Perhaps I should/could take care of di-netboot-assistant ...). Having an active maintainer for it would be super nice, yes. I've taken the liberty of adding you to the alioth d-i group; that doesn't mean that you *have* to be the d-i-n-a maintainer of course, it should just make it easy for you to push your changes to the d-i repositories, be it for NMUs or MUs. Thanks for adding me to the group! I thought a bit about taking caring about d-i-n-a, and I think I will do that indeed. :-) Best regards, Andi -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150205104845.GA2616@flashgordon
Bug#776565: preparing nmu for di-netboot-assistant
Hi, On Mon, Feb 02, 2015 at 10:38:57PM +0100, Cyril Brulebois wrote: Andreas B. Mundt a...@debian.org (2015-02-02): I have prepared a nmu which I plan to upload tomorrow after having tested the modification once more. (1-day notice is a short timeframe.) Yes, sorry, I planned to upload to DELAYED (as Holger suggested), but wanted to have this first 'go for it' to be able to re-adjust if necessary. [...] If you see any problems with the planned nmu, please rise your hand. It'd be nice to have some description of the changes in the changelog (that's what it's for! ;)) instead of pointers to a bug report thread/discussion. Right, I added some more details to the changelog now. Whatever gets uploaded, please make sure to get that pushed into the repository, or point to a branch/tag somewhere if you can't find anyone to push your changes there. OK, I'll keep that in mind. (Perhaps I should/could take care of di-netboot-assistant ...). The package has been uploaded to DELAYED/2 now. Thanks to everybody involved, Andi -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150203091844.GA17204@flashgordon
Bug#776565: preparing nmu for di-netboot-assistant
Hi,
I have prepared a nmu which I plan to upload tomorrow after having
tested the modification once more.
Please find the debdiff attached, it consists of Jonas' patch with my
modification as well as the activation of the jessie release.
If you see any problems with the planned nmu, please rise your hand.
Best regards,
Andi
diff -Nru -w di-netboot-assistant-0.38a/config/di-sources.list
di-netboot-assistant-0.38a+nmu1/config/di-sources.list
--- di-netboot-assistant-0.38a/config/di-sources.list 2013-07-13
10:31:11.0 +0200
+++ di-netboot-assistant-0.38a+nmu1/config/di-sources.list 2015-02-02
19:46:33.0 +0100
@@ -49,13 +49,13 @@
squeeze-gtki386
http://ftp.debian.org/dists/squeeze/main/installer-i386/current/images/
netboot/gtk/netboot.tar.gz
#Debian/Jessie (not released yet, As of writing this file)
-#jessieamd64
http://ftp.debian.org/dists/jessie/main/installer-amd64/current/images/
netboot/netboot.tar.gz
-#jessiei386
http://ftp.debian.org/dists/jessie/main/installer-i386/current/images/
netboot/netboot.tar.gz
+jessie amd64
http://ftp.debian.org/dists/jessie/main/installer-amd64/current/images/
netboot/netboot.tar.gz
+jessie i386
http://ftp.debian.org/dists/jessie/main/installer-i386/current/images/
netboot/netboot.tar.gz
#jessieia64
http://ftp.debian.org/dists/jessie/main/installer-ia64/current/images/
netboot/netboot.tar.gz
#jessiesparc
http://ftp.debian.org/dists/jessie/main/installer-sparc/current/images/
netboot/boot.img
##Graphical Installer (GTK)
-#jessie-gtkamd64
http://ftp.debian.org/dists/jessie/main/installer-amd64/current/images/
netboot/gtk/netboot.tar.gz
-#jessie-gtki386
http://ftp.debian.org/dists/jessie/main/installer-i386/current/images/
netboot/gtk/netboot.tar.gz
+jessie-gtk amd64
http://ftp.debian.org/dists/jessie/main/installer-amd64/current/images/
netboot/gtk/netboot.tar.gz
+jessie-gtk i386
http://ftp.debian.org/dists/jessie/main/installer-i386/current/images/
netboot/gtk/netboot.tar.gz
# DEVELOPMENT (( http://www.debian.org/devel/debian-installer/ ))
diff -Nru -w di-netboot-assistant-0.38a/debian/changelog
di-netboot-assistant-0.38a+nmu1/debian/changelog
--- di-netboot-assistant-0.38a/debian/changelog 2013-07-16 07:17:24.0
+0200
+++ di-netboot-assistant-0.38a+nmu1/debian/changelog2015-02-02
19:46:33.0 +0100
@@ -1,3 +1,12 @@
+di-netboot-assistant (0.38a+nmu1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix package for jessie. For details, see the discussion in the bugs
+closed. Thanks to Jonas Smedegaard and Martin F Krafft.
+(Closes: #759424, closes: #776565)
+
+ -- Andreas B. Mundt a...@debian.org Mon, 02 Feb 2015 19:46:08 +0100
+
di-netboot-assistant (0.38a) unstable; urgency=low
[ Frank Lin PIAT ]
diff -Nru -w di-netboot-assistant-0.38a/di-netboot-assistant
di-netboot-assistant-0.38a+nmu1/di-netboot-assistant
--- di-netboot-assistant-0.38a/di-netboot-assistant 2013-07-13
10:31:11.0 +0200
+++ di-netboot-assistant-0.38a+nmu1/di-netboot-assistant2015-02-02
19:46:33.0 +0100
@@ -200,12 +200,13 @@
# #
# find_file()
# Return the name of the first file matching criteria.
-# Parameters: dir name
+# Parameters: name dir [dir...]
# Returns: (STRING) file
# #
find_file() {
if [ $1 -a $2 ]; then
- find $2 -type f -name $1 | head -n 1
+ local name=$1; shift
+ find $@ -type f -name $name | head -n 1
else
echo
fi
@@ -241,7 +242,14 @@
[ ! $src -o ! $dst ] return 1
+ if [ $SYSLINUX = $src ]; then
+ # avoid recent SYSLINUX EFI binaries incompatible with PXELINUX
+ [ ! -d $src/modules/bios ] || src=$src/modules/bios
+ # recent SYSLINUX ships PXELINUX at separate location
+ newbin=$(find_file pxelinux.0 /usr/lib/PXELINUX $SYSLINUX
2/dev/null)
+ else
newbin=$(find_file pxelinux.0 $src 2/dev/null)
+ fi
[ ! -f $dst/pxelinux.0 -a ! -f $newbin ] return 1
pxe_new_ver=$(pxelinux_version $newbin)
@@ -253,7 +261,11 @@
echo I: Upgrading PXELinux ($pxe_cur_ver to $pxe_new_ver)
for f in pxelinux.0 menu.c32 vesamenu.c32; do
+ if [ pxelinux.0 = $f ]; then
+ srcf=$newbin
+ else
srcf=$(find_file $f $src)
+ fi
[ ${f#*c32} ] || f=pxelinux.cfg/$f
[ -L $dst/$f ] rm $dst/$f
if [ -f $srcf ]; then
@@ -264,6 +276,13 @@
done
# Smooth transition to vesamenu
[ ! -f $c32_dir/menu.c32 ] ln -s vesamenu.c32 $c32_dir/menu.c32
+ # Add core modules at root (see https://bugs.debian.org/756275#49
Bug#776565: Please verify which patch version is fine
Hi Martin, KiBi, On Thu, 29 Jan 2015 20:57:22 +0100 martin f krafft madd...@debian.org wrote: also sprach Cyril Brulebois k...@debian.org [2015-01-29 18:58 +0100]: I'm not sure it's reasonable to expect fixing di-n-a at this point of the release cycle, frankly. Of course, but maybe the fix is trivial⦠on the other hand, I looked and tried already⦠there is a patch. Lemme at least verify that one on the weekend. Summary concerning the patch: * Jonas provided patches in https://bugs.debian.org/759424#57 * I had to modify Jonas' patch slightly to make it work here: https://bugs.debian.org/759424#33 * Jonas disagrees with that modification, the diffence is diskussed in https://bugs.debian.org/759424#62 from my POV. * Discussion got stuck. * I sent some minor improvement patches in https://bugs.debian.org/759424#67 and https://bugs.debian.org/759424#72 So what's basically needed is someone who could test independently if either Jonas patch is fine as it is, or if my modifications are needed. As soon as it's clear which patch-version is fine, the patch should work. I use di-netboot-assistant in debian-lan, with a workaround applied [1] to compensate for the missing patch (my version, of course). If the package is removed, debian-lan would fail to work :-( So if possible, check if the patch works and then let's prepare the fixed package. Removing the package breaks debian-lan. I am happy to help, but for the time being someone independent is needed to verify which patch-version is fine. Best regards, Andi [1] https://anonscm.debian.org/cgit/collab-maint/debian-lan.git/tree/fai/config/scripts/FAISERVER/50-di-netboot especially line 9, 110-115 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150130174841.GA2369@flashgordon
Bug#759424: di-netboot-assistant: enabel jessie repositories
Package: di-netboot-assistant Followup-For: Bug #759424 Hi, one more change that should be applied: Currenty, jessie is commented in '/etc/di-netboot-assistant/di-sources.list'. Also, some architectures are missing. The attached patch enables at least the amd64 and i386 for jessie. Best regards, Andi diff --git a/config/di-sources.list b/config/di-sources.list index caeb5f8..209ef4e 100644 --- a/config/di-sources.list +++ b/config/di-sources.list @@ -48,14 +48,12 @@ squeeze sparc http://ftp.debian.org/dists/squeeze/main/installer-sparc/current/i squeeze-gtk amd64 http://ftp.debian.org/dists/squeeze/main/installer-amd64/current/images/ netboot/gtk/netboot.tar.gz squeeze-gtk i386 http://ftp.debian.org/dists/squeeze/main/installer-i386/current/images/ netboot/gtk/netboot.tar.gz -#Debian/Jessie (not released yet, As of writing this file) -#jessie amd64 http://ftp.debian.org/dists/jessie/main/installer-amd64/current/images/ netboot/netboot.tar.gz -#jessie i386 http://ftp.debian.org/dists/jessie/main/installer-i386/current/images/ netboot/netboot.tar.gz -#jessie ia64 http://ftp.debian.org/dists/jessie/main/installer-ia64/current/images/ netboot/netboot.tar.gz -#jessie sparc http://ftp.debian.org/dists/jessie/main/installer-sparc/current/images/ netboot/boot.img +#Debian/Jessie +jessie amd64 http://ftp.debian.org/dists/jessie/main/installer-amd64/current/images/ netboot/netboot.tar.gz +jessie i386 http://ftp.debian.org/dists/jessie/main/installer-i386/current/images/ netboot/netboot.tar.gz ##Graphical Installer (GTK) -#jessie-gtk amd64 http://ftp.debian.org/dists/jessie/main/installer-amd64/current/images/ netboot/gtk/netboot.tar.gz -#jessie-gtk i386 http://ftp.debian.org/dists/jessie/main/installer-i386/current/images/ netboot/gtk/netboot.tar.gz +jessie-gtk amd64 http://ftp.debian.org/dists/jessie/main/installer-amd64/current/images/ netboot/gtk/netboot.tar.gz +jessie-gtk i386 http://ftp.debian.org/dists/jessie/main/installer-i386/current/images/ netboot/gtk/netboot.tar.gz # DEVELOPMENT (( http://www.debian.org/devel/debian-installer/ ))
Bug#759424: di-netboot-assistant: please update package for jessie / new syslinux
Hi Jonas, On Sun, Nov 23, 2014 at 02:26:37PM +0100, Jonas Smedegaard wrote: Quoting Jonas Smedegaard (2014-11-23 13:05:36) Quoting Cyril Brulebois (2014-11-23 12:49:58) Jonas Smedegaard d...@jones.dk (2014-11-21): Attached is a patch believed to fix all issues related to new syslinux: [...] Of course I could try and split up your patches into atomic commits, but I guess it'd be better if knowledgeable could document patches. There's of course the part where Andreas had to patch a bit more what Jonas provided, so cross-checking each other would be nice. [...] I am puzzled why you needed that change, Andreas. Perhaps it depend on the versions of syslinux involved. I tested on Jessie, with stable, testing and daily for amd64 and i386 - what did you test? I used jessie as well, fresh debian-lan installation (which already uses di-netboot-assistant, the missing files are copied manually, and TFTP_ROOT=/srv/tftp in /etc/di-netboot-assistant/di-netboot-assistant.conf) But the problem is not with the different installer versions, the very first boot menu fails here without adding my modifcation. What I did: I removed the existing directory 'debian-installer', applied your patch and testet the new setup. The tftproot '/srv/tftp' contains now: debian-installer/ ldlinux.c32 libcom32.c32 libutil.c32 Booting a client via PXE fails with 'failed to load ldlinux.c32'. I move the directory to debian-installer-jonas, remove the .c32-files and use my version. Now only debian-installer/ has been created in '/srv/tftp' and PXE-booting works fine offering the installer menu. The directory trees are identical except that *.c32 ended in the debian-installer dir: diff -rq /srv/tftp/debian-installer-andi/ /srv/tftp/debian-installer-jonas/ Only in /srv/tftp/debian-installer-andi/: ldlinux.c32 Only in /srv/tftp/debian-installer-andi/: libcom32.c32 Only in /srv/tftp/debian-installer-andi/: libutil.c32 Or perhaps it is related to choice and configuration of tftpd. I use tftpd-hpa with TFTP_OPTIONS=--blocksize 1468 -v -v -v -v --secure and adapting di-netboot-assistant to use /srv/tftp. Same here :-/ @Andreas: If you configured your tftpd to treat debian-installer subdir as root dir for tftpd, then you should move/copy those three files yourself: This script currently has configurable TFTP_ROOT but hardcoded debian-installer subdir - making that configurable too is independent from this bug. No idea what's different in our setups/tests. Perhaps the above informations give some hint on that. Best regards, Andi -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141123164127.GA14677@fuzi
Bug#759424: di-netboot-assistant: please update package for jessie / new syslinux
Hi Jonas,
On Sun, Nov 23, 2014 at 04:56:16PM +0100, Jonas Smedegaard wrote:
Sure thing: I will prepare git commits.
I now have a fork of your git locally, and attached patches were
produced using git format-patch --minimal origin/master - not sure if
that's what you prefer, else please guide me.
You migth consider adding this improved warning to the patch set:
--- di-netboot-assistant.andi 2014-11-23 18:15:05.100283686 +0100
+++ di-netboot-assistant.jonas 2014-11-23 16:53:10.232629361 +0100
@@ -392,7 +392,7 @@
if [ -f pxelinux.cfg/default ]; then
for x in $(sed -n -e
s,^\s*KERNEL\s[\s:/]*\(.*menu.c32\).*,\1,p pxelinux.cfg/default | sort -u );
do
+ [ ! -f ../$x ] echo W: The binary '${TFTP_ROOT}/$x'
mentioned in the PXE boot menu is missing.
- [ ! -f ../$x ] echo W: Some menu binaries are
missing. Install the package syslinux
done
else
find pxelinux.cfg/ -iregex '.*\(\.c32\|\.bak.*\|~\)$' \
It pops up when removing the debian-installer directory and not all installer
images have been installed again with di-netboot-assistant install XXX, and
the current content is rather confusing.
Best regards,
Andi
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141123173321.GB14677@fuzi
Bug#759424: patch fix
Control: severity -1 important
(rising severity as without patch di-netboot-assistant is almost useless)
Hi,
I gave Jonas' patch a try (thanks!) and it works fine here after I
applied the following patch-to-the-pach:
@@ -53,7 +53,7 @@
+ if [ $TFTP_ROOT/debian-installer/ = $dst ]; then
+ for f in ldlinux.c32 libcom32.c32 libutil.c32; do
+ srcf=$(find_file $f $src)
-+ [ -z $srcf ] || cp -np $srcf $TFTP_ROOT/$f
++ [ -z $srcf ] || cp -np $srcf
$TFTP_ROOT/debian-installer/$f
+ done
+ fi
return 0
@@ -70,7 +70,7 @@
+ cp -pft $(dirname $f)
$TFTP_ROOT/debian-installer/pxelinux.cfg/$(basename $f)
+ ;;
+ldlinux.c32|libcom32.c32|libutil.c32)
-+ cp -pft $(dirname $f) $TFTP_ROOT/$(basename $f)
++ cp -pft $(dirname $f)
$TFTP_ROOT/debian-installer/$(basename $f)
+ ;;
+*)
+ echo W: Unusual PXELINUX module \$f\ may not work.
12g
I attach the modified patch.
Best regards,
Andi
--- /usr/bin/di-netboot-assistant 2013-07-13 10:31:11.0 +0200
+++ di-netboot-assistant.patched 2014-11-21 22:05:13.102987843 +0100
@@ -200,12 +200,13 @@
# #
# find_file()
# Return the name of the first file matching criteria.
-# Parameters: dir name
+# Parameters: name dir [dir...]
# Returns: (STRING) file
# #
find_file() {
if [ $1 -a $2 ]; then
- find $2 -type f -name $1 | head -n 1
+ local name=$1; shift
+ find $@ -type f -name $name | head -n 1
else
echo
fi
@@ -241,7 +242,14 @@
[ ! $src -o ! $dst ] return 1
- newbin=$(find_file pxelinux.0 $src 2/dev/null)
+ if [ $SYSLINUX = $src ]; then
+ # avoid recent SYSLINUX EFI binaries incompatible with PXELINUX
+ [ ! -d $src/modules/bios ] || src=$src/modules/bios
+ # recent SYSLINUX ships PXELINUX at separate location
+ newbin=$(find_file pxelinux.0 /usr/lib/PXELINUX $SYSLINUX 2/dev/null)
+ else
+ newbin=$(find_file pxelinux.0 $src 2/dev/null)
+ fi
[ ! -f $dst/pxelinux.0 -a ! -f $newbin ] return 1
pxe_new_ver=$(pxelinux_version $newbin)
@@ -253,7 +261,11 @@
echo I: Upgrading PXELinux ($pxe_cur_ver to $pxe_new_ver)
for f in pxelinux.0 menu.c32 vesamenu.c32; do
- srcf=$(find_file $f $src)
+ if [ pxelinux.0 = $f ]; then
+ srcf=$newbin
+ else
+ srcf=$(find_file $f $src)
+ fi
[ ${f#*c32} ] || f=pxelinux.cfg/$f
[ -L $dst/$f ] rm $dst/$f
if [ -f $srcf ]; then
@@ -264,6 +276,13 @@
done
# Smooth transition to vesamenu
[ ! -f $c32_dir/menu.c32 ] ln -s vesamenu.c32 $c32_dir/menu.c32
+ # Add core modules at root (see https://bugs.debian.org/756275#49)
+ if [ $TFTP_ROOT/debian-installer/ = $dst ]; then
+ for f in ldlinux.c32 libcom32.c32 libutil.c32; do
+ srcf=$(find_file $f $src)
+ [ -z $srcf ] || cp -np $srcf $TFTP_ROOT/debian-installer/$f
+ done
+ fi
return 0
}
@@ -907,6 +926,21 @@
if ! copy_syslinux_bin $expand_dir $TFTP_ROOT/debian-installer/ ; then
echo E: No PXELinux menu installed. Please file a bug. 12
fi
+ # ensure only a single PXELINUX version is used for all its modules
+ for f in $(find $expand_dir -type f -name '*.c32'); do
+ case $(basename $f) in
+ vesamenu.c32|menu.c32)
+ cp -pft $(dirname $f) $TFTP_ROOT/debian-installer/pxelinux.cfg/$(basename $f)
+ ;;
+ ldlinux.c32|libcom32.c32|libutil.c32)
+ cp -pft $(dirname $f) $TFTP_ROOT/debian-installer/$(basename $f)
+ ;;
+ *)
+ echo W: Unusual PXELINUX module \$f\ may not work. 12
+ continue
+ ;;
+ esac
+ done
for f in $(find $expand_dir -type f -a \( -name default -o -name boot.txt -o -name '*.cfg' \) ); do
mv $f $f.ORIG
Bug#759737: confirmed here
Hi, I am biten by exactly the same issue here. I need a way to preseed that the 'default' disk (there is only one in my case, network install) which is obviously detected correctly, is used for physical as well as virtual hardware (/dev/sda respectively /dev/vda). Best regards, Andi -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140910124753.GA14197@flashgordon
Bug#759290: debian-installer: 'Automated install' does not delay the locale and keyboard questions
Control: retitle -1 debian-installer: 'Auto install' does not delay questions when DHCP sends preseeding url Control: tag -1 - unreproducible Control: severity -1 wishlist Hi Samuel, thanks for your quick reply! On Tue, Aug 26, 2014 at 01:52:17AM +0200, Samuel Thibault wrote: Andreas B. Mundt, le Mon 25 Aug 2014 23:19:03 +0200, a écrit : when experimenting with unattended installations using PXE-boot and preseeding d-i, I did not find the 'Automated install' (auto mode) working as described in [1]: The auto kernel parameter is an alias for auto-install/enable and setting it to true delays the locale and keyboard questions until after there has been a chance to preseed them ... When I choose 'Automated install' from the 'Advanced options' menu, the first questions show up nevertheless (before setting up the network) and I have to answer them or preseed them on the kernel boot line. Could it be that the delaying functionality got lost? No, it is still there, but only if you provide some preseeding URL on the boot line or CD image etc. Otherwise it will prompt for the URL, and I guess that while at it, there's no point in not configuring the keyboard before that. At any rate, booting jessie b1 with the Automated install boot entry and passing url=http://dept-info.labri.fr/~thibault/preseed-jessie.txt on the kernel command line does install a Debian system without any prompt. You are right, it works indeed when providing a url, just tested it here. Before, I was using the method B.2.5. Using a DHCP server to specify preconfiguration files described in [1]. Is there a reason not to delay the questions with that method? Perhaps it could be mentioned in [1], but feel free to close this bug if you think it's inappropriate. Best regards, Andi [1] https://www.debian.org/releases/stable/i386/apbs02.html.en#preseed-dhcp -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140826061601.GA3568@flashgordon
Bug#759290: debian-installer: 'Automated install' does not delay the locale and keyboard questions
Package: debian-installer Severity: minor Tags: d-i Hello, when experimenting with unattended installations using PXE-boot and preseeding d-i, I did not find the 'Automated install' (auto mode) working as described in [1]: The auto kernel parameter is an alias for auto-install/enable and setting it to true delays the locale and keyboard questions until after there has been a chance to preseed them ... When I choose 'Automated install' from the 'Advanced options' menu, the first questions show up nevertheless (before setting up the network) and I have to answer them or preseed them on the kernel boot line. Could it be that the delaying functionality got lost? Best regards, Andi [1] https://www.debian.org/releases/stable/i386/apbs02.html.en#preseed-auto -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140825211903.23640.55094.reportbug@flashgordon
Bug#690586: installation-reports: NVIDIA GF108 [Quadro 1000M] 10de:0dfa (rev a1) X fails with nouveau/linux-3.2
Hi Sven, On Tue, Nov 20, 2012 at 05:57:27PM +0100, Sven Joachim wrote: [...] Could you please try a 3.3 kernel from snapshot.debian.org¹? There were various i2c related nouveau commits in that version, so maybe it would be sufficient to backport them. ¹ http://snapshot.debian.org/archive/debian/20120322T225438Z/pool/main/l/linux-2.6/linux-image-3.3.0-trunk-amd64_3.3-1%7Eexperimental.1_amd64.deb This kernel works fine without any special handling, just installing and rebooting is sufficient. $ uname -a Linux lmz 3.3.0-trunk-amd64 #1 SMP Thu Mar 22 18:02:10 UTC 2012 x86_64 GNU/Linux Thanks! Andi -- 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/20121120182922.GA4561@lmz
Bug#690586: installation-reports: NVIDIA GF108 [Quadro 1000M] 10de:0dfa (rev a1) X fails with nouveau/linux-3.2
Hi Sven, On Mon, Nov 19, 2012 at 06:59:12PM +0100, Sven Joachim wrote: Am 15.10.2012 um 22:42 schrieb Andreas B. Mundt: Package: installation-reports Severity: normal the wheezy default kernel 3.2 does not provide an appropriate nouveau driver to start X on this machine. It is certainly supposed to do that, however. How exactly does it fail? Perhaps I should be more accurate. The machine freezes when booting and I have to power off (Sys-Rq and other key combinations do not help). The last line shown on the screen (with quiet removed from the kernel boot stanza) differs. If it helps I can run a series and report the final lines. However, I am able to boot with nomodeset added to the boot parameters. I have to use linux-image-3.5-trunk-amd64 to be able to start X. Can you please boot the 3.2 kernel, try to start X and send the output of /usr/share/bug/xserver-xorg-core/script 31 ? I attached the output when started with nomodeset as kernel boot parameter. The screen resolution is pretty bad (1024x768) compared to the resolution when running kernel 3.5. Please let me know if you need any other information, I am happy to provide what's needed. Best regards, Andi -- 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/20121119203856.GA4388@lmz
Bug#690586: installation-reports: NVIDIA GF108 [Quadro 1000M] 10de:0dfa (rev a1) X fails with nouveau/linux-3.2
Hi Sven, On Mon, Nov 19, 2012 at 10:01:05PM +0100, Sven Joachim wrote: Am 19.11.2012 um 21:38 schrieb Andreas B. Mundt: On Mon, Nov 19, 2012 at 06:59:12PM +0100, Sven Joachim wrote: Am 15.10.2012 um 22:42 schrieb Andreas B. Mundt: The machine freezes when booting and I have to power off (Sys-Rq and other key combinations do not help). The last line shown on the screen (with quiet removed from the kernel boot stanza) differs. If it helps I can run a series and report the final lines. However, I am able to boot with nomodeset added to the boot parameters. Well, the problem is indeed in the graphics driver then, since nomodeset effectively disables it. Does it work with nouveau.noaccel=1 instead of nomodeset? No, it freezes again with nouveau.noaccel=1. I attached the output when started with nomodeset as kernel boot parameter. The screen resolution is pretty bad (1024x768) compared to the resolution when running kernel 3.5. Yes, because you then get to use the vesa driver for X which does not support modern wide screens. OK Do you have another computer where you can capture kernel messages via netconsole? A short HOWTO for netconsole is on http://blog.mraw.org/2010/11/08/Debugging_using_netconsole, also see Documentation/networking/netconsole.txt in the kernel source. OK, I will look into that tomorrow and report back. Good night, Andi -- 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/20121119212639.GA2540@fuzi
Bug#690586: installation-reports: NVIDIA GF108 [Quadro 1000M] 10de:0dfa (rev a1) X fails with nouveau/linux-3.2
On Mon, Nov 19, 2012 at 10:01:05PM +0100, Sven Joachim wrote: [...] Do you have another computer where you can capture kernel messages via netconsole? A short HOWTO for netconsole is on http://blog.mraw.org/2010/11/08/Debugging_using_netconsole, also see Documentation/networking/netconsole.txt in the kernel source. It's attached. Cheers, Andi [0.007880] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [0.007881] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) [0.008158] mce: CPU supports 9 MCE banks [0.008290] CPU0: Thermal monitoring enabled (TM1) [0.008418] using mwait in idle threads. [0.008992] ACPI: Core revision 20110623 [0.030623] DMAR: Host address width 36 [0.030742] DMAR: DRHD base: 0x00fed91000 flags: 0x1 [0.030871] IOMMU 0: reg_base_addr fed91000 ver 1:0 cap c9008020660262 ecap f0105a [0.031038] DMAR: RMRR base: 0x00bf69a000 end: 0x00bf6b9fff [0.031235] IOAPIC id 0 under DRHD base 0xfed91000 IOMMU 0 [0.031361] HPET id 0 under DRHD base 0xfed91000 [0.031482] HPET id 0 under DRHD base 0xfed91000 [0.031603] HPET id 0 under DRHD base 0xfed91000 [0.031725] HPET id 0 under DRHD base 0xfed91000 [0.031846] HPET id 0 under DRHD base 0xfed91000 [0.031968] HPET id 0 under DRHD base 0xfed91000 [0.032088] HPET id 0 under DRHD base 0xfed91000 [0.032209] HPET id 0 under DRHD base 0xfed91000 [0.032417] Enabled IRQ remapping in x2apic mode [0.032538] Enabling x2apic [0.032652] Enabled x2apic [0.032777] Switched APIC routing to cluster x2apic. [0.033340] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [0.073088] CPU0: Intel(R) Core(TM) i7-2760QM CPU @ 2.40GHz stepping 07 [0.179657] Performance Events: PEBS fmt1+, SandyBridge events, Intel PMU driver. [0.180034] PEBS disabled due to CPU errata. [0.187430] ... version:3 [0.187549] ... bit width: 48 [0.187669] ... generic registers: 4 [0.187788] ... value mask: [0.187911] ... max period: 7fff [0.188035] ... fixed-purpose events: 3 [0.188154] ... event mask: 0007000f [0.188410] NMI watchdog enabled, takes one hw-pmu counter. [0.188623] Booting Node 0, Processors #1 [0.299552] NMI watchdog enabled, takes one hw-pmu counter. [0.299778] #2 [0.407466] NMI watchdog enabled, takes one hw-pmu counter. [0.407686] #3 [0.515272] NMI watchdog enabled, takes one hw-pmu counter. [0.515488] #4 [0.623076] NMI watchdog enabled, takes one hw-pmu counter. [0.623294] #5 [0.730988] NMI watchdog enabled, takes one hw-pmu counter. [0.731207] #6 [0.838793] NMI watchdog enabled, takes one hw-pmu counter. [0.839011] #7 Ok. [0.946630] NMI watchdog enabled, takes one hw-pmu counter. [0.946782] Brought up 8 CPUs [0.946896] Total of 8 processors activated (38312.50 BogoMIPS). [0.954270] devtmpfs: initialized [0.957684] PM: Registering ACPI NVS region at bf6bd000 (1048576 bytes) [0.957981] print_constraints: dummy: [0.958151] NET: Registered protocol family 16 [0.958354] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [0.958524] ACPI: bus type pci registered [0.958720] PCI: MMCONFIG for domain [bus 00-ff] at [mem 0xe000-0xefff] (base 0xe000) [0.958894] PCI: MMCONFIG at [mem 0xe000-0xefff] reserved in E820 [0.978885] PCI: Using configuration type 1 for base access [0.979971] bio: create slab bio-0 at 0 [0.980181] ACPI: Added _OSI(Module Device) [0.980301] ACPI: Added _OSI(Processor Device) [0.980421] ACPI: Added _OSI(3.0 _SCP Extensions) [0.980544] ACPI: Added _OSI(Processor Aggregator Device) [2.957185] ACPI: Interpreter enabled [3.307695] VFS: Disk quotas dquot_6.5.2 [3.307837] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [3.315327] msgmni has been set to 32073 [3.315578] alg: No test for stdrng (krng) [3.315722] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [3.315882] io scheduler noop registered [3.315994] io scheduler deadline registered [3.316133] io scheduler cfq registered (default) [ 38.356750] EXT4-fs (dm-1): INFO: recovery required on readonly filesystem [ 38.356885] EXT4-fs (dm-1): write access will be enabled during recovery [ 40.886481] iTCO_vendor_support: vendor-support=0 [ 40.891634] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [ 40.891835] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460) [ 40.892047] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 40.904133] parport_pc 00:09: reported by Plug and Play ACPI [ 40.904351] parport0: PC-style at 0x378 (0x778), irq 5 [PCSPP,TRISTATE] [ 40.939369] [drm] Initialized drm 1.1.0 20060810 [ 40.982166] wmi: Mapper loaded [ 41.025398]
Bug#690586: Installation from USB stick: fstab entries should be removed
Hi, when installing from an USB stick prepared following the instructions in URL:http://www.debian.org/releases/wheezy/amd64/ch04s03.html.en, the stick will cause entries in fstab. I had the same problem with a friend's squeeze installation, where mounting another usb stick after installation did not work, because the fstab entries did not match that stick. Best regards, Andi -- 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/20121027164400.GA24867@fuzi
Bug#690586: installation-reports: NVIDIA GF108 [Quadro 1000M] 10de:0dfa (rev a1) X fails with nouveau/linux-3.2
Package: installation-reports Severity: normal Hi, the wheezy default kernel 3.2 does not provide an appropriate nouveau driver to start X on this machine. I have to use linux-image-3.5-trunk-amd64 to be able to start X. Best regards, Andi -- Package-specific info: Boot method: netinstall from CD-image on USB-stick Image version: Debian 7.0 wheezy installation CD-ROM 20121013-03:10; d-i 20120930+b1 Date: Sat Oct 13 Machine: HP EliteBook 8560w Partitions: df -Tl will do; the raw partition table is preferred Disk /dev/sda: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x000e3ae3 Device Boot Start End Blocks Id System /dev/sda1 *2048 499711 248832 83 Linux /dev/sda2 501758 1465147391 7323228175 Extended Partition 2 does not start on physical sector boundary. /dev/sda5 501760 1465147391 732322816 83 Linux 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 CD: [ ] 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: When using LVM on an encrypted partion, the screen shows something like removing all data from ... and a progress bar that does not change (in a reasonable time (~30s)). After Cancel the installation continues without problems.. -- 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=7.0 (wheezy) - installer build 20120930+b1 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux lmz 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1631] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1631] lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1631] lspci -knn: Kernel driver in use: e1000e lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1631] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1631] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b4) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 [8086:1c14] (rev b4) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b4) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.7 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 [8086:1c1e] (rev b4) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host
debian installer options
Hi, I've got a problem installing debian (squeeze 'netinst' installer rc2) on an old laptop. The machine has (and had) always problems freezing when probing some pcmcia 0x100-0x3af stuff. Usually I could add (by pressing F4 or something like that) exclude=0x100,0x2af to the installer options which skipped probing the nasty address space. This seems not to be possible in the squeeze installer, is there a workaround available? Thanks, Andi -- 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/20110201103358.GA4542@flashgordon
images should be available in squeeze
Hi, [...] the Debian Edu Lenny release currently sets up PXE booting out of the box, by making use of a d-i-bootimages package, which is not available in Debian. This is annoying as PXE booting is a quite a nice feature and having the d-i bootimages on the DVD is needed as we want to fully support DVD installations without network. [...] according to Otavio from the installer project, the solution to this issue is already on its way. If nothing goes wrong, the images will be available in squeeze. (cc debian-installer to make them shout out loud if I got something wrong ...) Thanks, Andi -- 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/20100802211520.ga4...@siddhartha.sunshine
access the cleartext root password during installation
Hi, one of the goals for debian-edu/skolelinux is to provide an easy installation with as little user interaction as possible. To achieve this, we use the root password hash (from the shadow file) for authentication in several places, for example as ldap administrator. There is no need to ask the user for any password a second time. (We keep the burden of memorizing passwords for the teachers as low as possible ;-) ). As we consider moving to kerberos as authentication method with the squeeze release, I run into a problem when creating some kerberos principals and the master key for the KDC: As the kerberos principals' keys are used for encryption over the network too, the hashed password is of no use (correct me if I am wrong), and the clear text root password (if you want to have a single password for everything) is needed. So my question is: Can I, by any means, access the root password entered at the beginning of the installation at a later stage of the installation process in clear text? Alternative ideas or solutions are of course welcome. Thanks and best regards, Andi -- 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/20100515154342.ga11...@flashgordon
