Re: Bootloader udeb selection for specific platform
Another suggest is that, the boot loaders udebs, provide the virtual udeb package "bootable-system" Your udeb must install the boot loader, and when the udeb is done, the main-menu will choose finish-install automatically. 2012/5/3 Joey Hess : > Gerhard Pircher wrote: >> Hi, >> >> I'm looking into building a custom Debian install CD for a non-supported >> PowerPC platform. The platform doesn't work with any of the available >> bootloaders in Debian. Therefore I would like to create my own bootloader >> udeb package. While I can use one of the available bootloader udebs as >> a base for my work, I didn't find out yet how the installer selects the >> right bootloader for a platform (it seems to load several bootloader >> udebs during an installation). Is this done by preseeding (though I >> could only find preseeding options for grub and lilo) or by some check >> of the architecture/platform string in /etc/cpuinfo? > > This is usually done with isinstallable scripts in the udebs's > control.tar.gz. > > -- > see shy jo -- Atte. Félix Arreola Rodríguez, «Sin firma GPG» -- 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/CAMxC6PLoGUOrOWxhLR+Ym6hAaaGHaDRq0F=HMjuDz=qbjxg...@mail.gmail.com
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: armel May 03 08:09 buildd@ancina build_iop32x_network-console_glantank http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_glantank.log * OLD BUILD:kfreebsd-amd64 Apr 05 00:32 buildd@fano build_cdrom_grub http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_grub.log * OLD BUILD:kfreebsd-amd64 Apr 05 00:32 buildd@fano build_cdrom_gtk http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_gtk.log * OLD BUILD:kfreebsd-amd64 Apr 05 00:37 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * OLD BUILD:kfreebsd-amd64 Apr 05 00:42 buildd@fano build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-9.log * OLD BUILD:kfreebsd-amd64 Apr 05 00:49 buildd@fano build_netboot-gtk http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk.log * OLD BUILD:kfreebsd-amd64 Apr 05 00:54 buildd@fano build_netboot-gtk-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk-9.log * OLD BUILD:kfreebsd-i386 Apr 05 00:17 buildd@finzi build_cdrom_grub http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_cdrom_grub.log * OLD BUILD:kfreebsd-i386 Apr 05 00:21 buildd@finzi build_netboot http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot.log * OLD BUILD:kfreebsd-i386 Apr 05 00:25 buildd@finzi build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot-9.log * OLD BUILD:mipsel Apr 19 00:11 buildd@rem build_cobalt_netboot-2.6_serial http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_serial.log * OLD BUILD:mipsel Apr 19 00:14 buildd@rem build_cobalt_netboot-2.6_ssh http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_ssh.log * OLD BUILD:mipsel Apr 19 00:16 buildd@rem build_cobalt_netboot-2.6_common http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_common.log * OLD BUILD:mipsel Apr 19 00:19 buildd@rem build_malta_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_malta_netboot-2.6.log * OLD BUILD:mipsel Apr 19 00:22 buildd@rem build_sb1-bcm91250a_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_sb1-bcm91250a_netboot-2.6.log * OLD BUILD:mipsel Apr 19 00:26 buildd@rem build_loongson-2f_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_loongson-2f_netboot-2.6.log Totals: 105 builds (1 failed, 15 old) -- 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/e1sq6sn-0007f1...@ravel.debian.org
Re: [RFH] Release of D-I Alpha1
On Sun, 2012-04-29 at 17:36 +0100, Adam D. Barratt wrote: > On Sun, 2012-04-29 at 16:54 +0100, Steve McIntyre wrote: > > I can do an alpha build of CDs whenever they're desired, just let me > > know when things are looking ready. > > Ah, I'd somewhat assumed that Otavio's "Steve, yey!" above meant that > he'd already talked to you about that. :-/ > > From the -release side, I think we should get on with producing and > testing images asap. Forgive my ignorance on the d-i side, but is there > an easily accessible / parseable list of reported issues with the > dailies which might be considered "show stoppers"? I guess they'd have > to be fairly severe to be blockers for an alpha though. Any hints? Regards, Adam -- 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/1336082991.1724.27.ca...@jacala.jungle.funky-badger.org
Re: Bootloader udeb selection for specific platform
Gerhard Pircher wrote: > Hi, > > I'm looking into building a custom Debian install CD for a non-supported > PowerPC platform. The platform doesn't work with any of the available > bootloaders in Debian. Therefore I would like to create my own bootloader > udeb package. While I can use one of the available bootloader udebs as > a base for my work, I didn't find out yet how the installer selects the > right bootloader for a platform (it seems to load several bootloader > udebs during an installation). Is this done by preseeding (though I > could only find preseeding options for grub and lilo) or by some check > of the architecture/platform string in /etc/cpuinfo? This is usually done with isinstallable scripts in the udebs's control.tar.gz. -- see shy jo signature.asc Description: Digital signature
Bootloader udeb selection for specific platform
Hi, I'm looking into building a custom Debian install CD for a non-supported PowerPC platform. The platform doesn't work with any of the available bootloaders in Debian. Therefore I would like to create my own bootloader udeb package. While I can use one of the available bootloader udebs as a base for my work, I didn't find out yet how the installer selects the right bootloader for a platform (it seems to load several bootloader udebs during an installation). Is this done by preseeding (though I could only find preseeding options for grub and lilo) or by some check of the architecture/platform string in /etc/cpuinfo? regards, Gerhard PS: Please keep me on CC:, as I'm not subscribed to this mailing list. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a -- 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/20120503164609.267...@gmx.net
Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
On Thu, May 03, 2012 at 11:25:50AM +0100, Martin Michlmayr wrote: > * Simon Guinot [2012-04-30 17:49]: > > You will find in attachment an updated patch. The netboot image is no > > longer generated. > > Sorry, I should have asked this before: do the LaCie devices set the > correct machine ID in u-boot? > > If yes, I'm happy to apply this patch, but only after the one for > flash-kernel has been accepted. Yes, the LaCie stock U-Boot provides the correct machine ID. > > > + mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 > > -n "Debian kernel" -d $(TEMP_KERNEL) $(SOME_DEST)/$(EXTRANAME)/lacie/uImage > > + mkimage -A arm -O linux -T ramdisk -C gzip -a 0x0 -e 0x0 -n > > "debian-installer ramdisk" -d $(TEMP_INITRD) > > $(SOME_DEST)/$(EXTRANAME)/lacie/uInitrd > > + update-manifest $(SOME_DEST)/$(EXTRANAME)/Lacie/uImage "Linux kernel > > for LaCie NAS" > ^ > This should be lower-case but I can make that change when applying the > patch. Argh, it is a typo. Thanks for doing that change. Simon signature.asc Description: Digital signature
Bug#670941: network-console: set LED signal on LaCie Kirkwood NASes when SSH is ready
* Simon Guinot [2012-04-25 04:07]: > Please consider applying the attached patch. Applied, thanks! -- Martin Michlmayr http://www.cyrius.com/ -- 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/20120503103444.ge17...@jirafa.cyrius.com
Bug#670938: flash-kernel: support is missing for LaCie Kirkwood NASes
Loïc, can you please review/apply. * Simon Guinot [2012-04-25 03:42]: > Package: flash-kernel > Version: 3.0~rc.4 > Severity: normal > Tags: patch > > Dear Maintainer, > > uImage et uInitrd files are not generated for LaCie Kirkwood NASes. > Please, consider applying the attached patch. > > Regards, > > Simon > > -- System Information: > Debian Release: wheezy/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: armel (armv5tel) > > Kernel: Linux 3.2.0-00010-g0a7ba17 (PREEMPT) > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > Shell: /bin/sh linked to /bin/dash > > Versions of packages flash-kernel depends on: > ii devio1.2-1+b1 > ii initramfs-tools 0.102 > ii linux-base 3.5 > > flash-kernel recommends no packages. > > Versions of packages flash-kernel suggests: > ii u-boot-tools 2011.12-3 > > -- no debconf information > >From 3d9c8dc8e5719d2dbf22da4fecb3005e8dc620fb Mon Sep 17 00:00:00 2001 > From: Simon Guinot > Date: Thu, 26 Apr 2012 19:16:27 +0200 > Subject: [PATCH] Add support for LaCie Kirkwood NASes > > This patch provides support for the following LaCie boards: > > - LaCie 2Big Network v2 > - LaCie 5Big Network v2 > - LaCie Internet Space v2 > - LaCie Network Space v2 > - LaCie Network Space Max v2 > - LaCie d2 Network v2 > --- > README|6 ++ > db/all.db | 54 ++ > 2 files changed, 60 insertions(+) > > diff --git a/README b/README > index 4eb4f35..1d2c600 100644 > --- a/README > +++ b/README > @@ -25,6 +25,12 @@ The following systems are supported: > - HP t5325 Thin Client > - HP Media Vault mv2120 > - Intel SS4000-E > + - LaCie 2Big Network v2 > + - LaCie 5Big Network v2 > + - LaCie Internet Space v2 > + - LaCie Network Space v2 > + - LaCie Network Space Max v2 > + - LaCie d2 Network v2 > - Linksys NSLU2 > - Marvell DB-78x00-BP Development Board > - Marvell OpenRD-Base > diff --git a/db/all.db b/db/all.db > index 2ce4645..b7f7caa 100644 > --- a/db/all.db > +++ b/db/all.db > @@ -116,6 +116,60 @@ Boot-Multi-Path: /boot/uImage > Required-packages: u-boot-tools > Bootloader-sets-root: yes > > +Machine: LaCie 2Big Network v2 > +Kernel-Flavors: kirkwood > +U-Boot-Kernel-Address: 0x8000 > +U-Boot-Initrd-Address: 0x0 > +Boot-Kernel-Path: /boot/uImage > +Boot-Initrd-Path: /boot/uInitrd > +Required-Packages: u-boot-tools > +Bootloader-sets-root: no > + > +Machine: LaCie 5Big Network v2 > +Kernel-Flavors: kirkwood > +U-Boot-Kernel-Address: 0x8000 > +U-Boot-Initrd-Address: 0x0 > +Boot-Kernel-Path: /boot/uImage > +Boot-Initrd-Path: /boot/uInitrd > +Required-Packages: u-boot-tools > +Bootloader-sets-root: no > + > +Machine: LaCie Internet Space v2 > +Kernel-Flavors: kirkwood > +U-Boot-Kernel-Address: 0x8000 > +U-Boot-Initrd-Address: 0x0 > +Boot-Kernel-Path: /boot/uImage > +Boot-Initrd-Path: /boot/uInitrd > +Required-Packages: u-boot-tools > +Bootloader-sets-root: no > + > +Machine: LaCie Network Space v2 > +Kernel-Flavors: kirkwood > +U-Boot-Kernel-Address: 0x8000 > +U-Boot-Initrd-Address: 0x0 > +Boot-Kernel-Path: /boot/uImage > +Boot-Initrd-Path: /boot/uInitrd > +Required-Packages: u-boot-tools > +Bootloader-sets-root: no > + > +Machine: LaCie Network Space Max v2 > +Kernel-Flavors: kirkwood > +U-Boot-Kernel-Address: 0x8000 > +U-Boot-Initrd-Address: 0x0 > +Boot-Kernel-Path: /boot/uImage > +Boot-Initrd-Path: /boot/uInitrd > +Required-Packages: u-boot-tools > +Bootloader-sets-root: no > + > +Machine: LaCie d2 Network v2 > +Kernel-Flavors: kirkwood > +U-Boot-Kernel-Address: 0x8000 > +U-Boot-Initrd-Address: 0x0 > +Boot-Kernel-Path: /boot/uImage > +Boot-Initrd-Path: /boot/uInitrd > +Required-Packages: u-boot-tools > +Bootloader-sets-root: no > + > # Really: Intel SS4000-e and compatibles > Machine: Lanner EM7210 > Method: redboot > -- > 1.7.9.5 > -- Martin Michlmayr http://www.cyrius.com/ -- 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/20120503103616.gf17...@jirafa.cyrius.com
Bug#670527: libdebian-installer4: missing support for LaCie NASes (Kirkwood)
* Simon Guinot [2012-04-26 12:04]: > Support for LaCie Kirkwood machines is missing from map_hardware. This > prevents from using Debian installer with the LaCie NASes (based on > Kirkwood SoC). Applied, thank you! -- Martin Michlmayr http://www.cyrius.com/ -- 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/20120503103031.gd17...@jirafa.cyrius.com
Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
* Simon Guinot [2012-04-30 17:49]: > You will find in attachment an updated patch. The netboot image is no > longer generated. Sorry, I should have asked this before: do the LaCie devices set the correct machine ID in u-boot? If yes, I'm happy to apply this patch, but only after the one for flash-kernel has been accepted. > + mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 > -n "Debian kernel" -d $(TEMP_KERNEL) $(SOME_DEST)/$(EXTRANAME)/lacie/uImage > + mkimage -A arm -O linux -T ramdisk -C gzip -a 0x0 -e 0x0 -n > "debian-installer ramdisk" -d $(TEMP_INITRD) > $(SOME_DEST)/$(EXTRANAME)/lacie/uInitrd > + update-manifest $(SOME_DEST)/$(EXTRANAME)/Lacie/uImage "Linux kernel > for LaCie NAS" ^ This should be lower-case but I can make that change when applying the patch. -- Martin Michlmayr http://www.cyrius.com/ -- 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/20120503102549.gc17...@jirafa.cyrius.com
netinstall via PXE
Dear Sir or Madam, yesterday I have managed to install Debian/Squeeze on a rather old computer via PXE using "tftp-hpa" and "dhcp3". The procedure you provide at ".../manual/xx.i386/ch04s05.html" (chapter 4.5 pp.) did not work. PXE stopped with a "directory" error, resulting in "boot file not found". So please allow me to explain the necessary differences to get the installation started: In chapter 4.5.1.1: The line in "/etc/dhcp3/dhcp.conf" regarding the filename should read ' filename "pxelinux.0";' (instead of ' filename "/pxelinux.0";' Note: This might not be the main change.) In chapter 4.5.4: Uncompressing "netboot/netboot.tar.gz" into the tftp boot image directory leaves "pxelinux.cfg" as a link to the directory "debian-installer/i386/pxelinux.cfg". Setting this link to "debian-installer/i386/pxelinux.cfg/default" resolves the "directory error" of PXE, but doesn't start the installation. This is only achieved by copying the configuration file "debian-installer/i386/boot-screens/syslinux.cfg" to "pxelinux.cfg/". In my example the client-IP was "192.168.1.2", so the files name had to be "C0A80102". This did the trick ! It might be that this renamed config file is necessary only for old PXE cards, but a hint on your site might help others with the same problem. Please feel free to add this information to the installation procedure. Yours sincerely, Ulrich Krause <>
