Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
tags 670530 + pending thanks Hello, On Mon, Apr 30, 2012 at 05:49:04PM +0200, Simon Guinot wrote: You will find in attachment an updated patch. The netboot image is no longer generated. Applied to GIT (including typo fix), thanks. f6aad66f9798289f870a9724eb3dd761dfc900ad Cheers, -- Hector Oron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
Hello, On Wed, May 02, 2012 at 03:00:20PM +0200, Simon Guinot wrote: Additionally, here is a patch to add LEDs modules for LaCie device to the network-console installer. Please consider submitting a new bug report for such change once #671200 is clarified. Thanks. Cheers, -- Hector Oron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
* Simon Guinot si...@sequanux.org [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-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 si...@sequanux.org [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#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
Additionally, here is a patch to add LEDs modules for LaCie device to
the network-console installer.
Note that this patch depends from the one provided with the wishlist
bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671200
Simon
From ef77263de7b6aaa4402cc0801390ea7d6df32f86 Mon Sep 17 00:00:00 2001
From: Simon Guinot simon.gui...@sequanux.org
Date: Fri, 27 Apr 2012 01:21:15 +
Subject: [PATCH] Include LED modules for LaCie devices
---
.../netboot/network-console/armel/kirkwood.cfg |2 ++
1 file changed, 2 insertions(+)
diff --git a/build/pkg-lists/netboot/network-console/armel/kirkwood.cfg b/build/pkg-lists/netboot/network-console/armel/kirkwood.cfg
index e1e7f2d..bcf3b35 100644
--- a/build/pkg-lists/netboot/network-console/armel/kirkwood.cfg
+++ b/build/pkg-lists/netboot/network-console/armel/kirkwood.cfg
@@ -5,4 +5,6 @@ ext2-modules-${kernel:Version}
ext3-modules-${kernel:Version}
# To control the LED and beeper on QNAP devices
event-modules-${kernel:Version}
+# LED modules for LaCie devices
+leds-modules-${kernel:Version}
qcontrol-udeb
--
1.7.9.5
signature.asc
Description: Digital signature
Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
On Fri, Apr 27, 2012 at 10:25:50AM +0100, Martin Michlmayr wrote: * Simon Guinot si...@sequanux.org [2012-04-26 16:09]: I understand that creating the netboot image is wrong because the network-console image already includes the same installer (plus the network console). Isn't it ? It's not wrong per so but I think it doesn't make sense to generate the netboot image when the majority of users will use network-console. Those with a serial console can always use the network-console image and then perform the installation on serial rather than via SSH. You will find in attachment an updated patch. The netboot image is no longer generated. From 05fe3a472afb0959ebf97af95408699240c885c9 Mon Sep 17 00:00:00 2001 From: Simon Guinot simon.gui...@sequanux.org Date: Wed, 25 Apr 2012 04:15:12 + Subject: [PATCH] Generate image for LaCie Kirkwood NASes This patch allows to generate a network-console image 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 --- build/config/armel/kirkwood/network-console.cfg |9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/build/config/armel/kirkwood/network-console.cfg b/build/config/armel/kirkwood/network-console.cfg index 28b8e30..253916a 100644 --- a/build/config/armel/kirkwood/network-console.cfg +++ b/build/config/armel/kirkwood/network-console.cfg @@ -1,6 +1,6 @@ MEDIA_TYPE = netboot image (SSH) -TARGET = $(TEMP_INITRD) $(TEMP_KERNEL) ts219 ts41x +TARGET = $(TEMP_INITRD) $(TEMP_KERNEL) ts219 ts41x lacie EXTRANAME = $(MEDIUM) TYPE = netboot/network-console @@ -40,3 +40,10 @@ ts41x: update-manifest $(SOME_DEST)/$(EXTRANAME)/qnap/ts-41x/kernel Linux kernel for QNAP TS-41x update-manifest $(SOME_DEST)/$(EXTRANAME)/qnap/ts-41x/initrd.gz initrd for QNAP TS-41x +# LaCie NAS series: Network Space v2 (and parents), d2 Network v2 and *Big Network v2 +lacie: + mkdir -p $(SOME_DEST)/$(EXTRANAME)/lacie + 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 + update-manifest $(SOME_DEST)/$(EXTRANAME)/lacie/uInitrd initrd for LaCie NAS -- 1.7.9.5 signature.asc Description: Digital signature
Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
* Simon Guinot si...@sequanux.org [2012-04-26 16:09]: I understand that creating the netboot image is wrong because the network-console image already includes the same installer (plus the network console). Isn't it ? It's not wrong per so but I think it doesn't make sense to generate the netboot image when the majority of users will use network-console. Those with a serial console can always use the network-console image and then perform the installation on serial rather than via SSH. There is no recovery mode available on the Kirkwood LaCie devices. If the Debian system breaks, a recovery system must be loaded from the U-Boot console (serial or network). Is there a page describing how to use the u-boot console via the network? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
On Fri, Apr 27, 2012 at 10:25:50AM +0100, Martin Michlmayr wrote: * Simon Guinot si...@sequanux.org [2012-04-26 16:09]: I understand that creating the netboot image is wrong because the network-console image already includes the same installer (plus the network console). Isn't it ? It's not wrong per so but I think it doesn't make sense to generate the netboot image when the majority of users will use network-console. Those with a serial console can always use the network-console image and then perform the installation on serial rather than via SSH. There is no recovery mode available on the Kirkwood LaCie devices. If the Debian system breaks, a recovery system must be loaded from the U-Boot console (serial or network). Is there a page describing how to use the u-boot console via the network? There is some informations at http://lacie-nas.org/doku.php?id=uboot in the subsection Connect to U-Boot via netconsole. It is quite thin but I will write a full documentation on how installing/rescuing Debian on a LaCie NAS. Else, there is http://git.denx.de/?p=u-boot.git;a=blob_plain;f=doc/README.NetConsole;hb=HEAD Simon signature.asc Description: Digital signature
Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
Package: debian-installer-6.0-netboot-armel Version: 20110106.squeeze4 Severity: normal Tags: d-i patch Dear Maintainer, Actually no Debian installer images are provided for LaCie NASes based on Kirkwood SoC. Please, consider applying the attached patch. Note that this patch rely on the one provided with the bug report #670527. 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 debian-installer-6.0-netboot-armel depends on no packages. debian-installer-6.0-netboot-armel recommends no packages. Versions of packages debian-installer-6.0-netboot-armel suggests: pn tftpd-hpa none -- no debconf information diff --git a/build/config/armel/kirkwood/netboot.cfg b/build/config/armel/kirkwood/netboot.cfg index 1fc5eeb..903d9cf 100644 --- a/build/config/armel/kirkwood/netboot.cfg +++ b/build/config/armel/kirkwood/netboot.cfg @@ -1,6 +1,6 @@ MEDIA_TYPE = netboot image -TARGET = $(TEMP_INITRD) $(TEMP_KERNEL) openrd sheevaplug +TARGET = $(TEMP_INITRD) $(TEMP_KERNEL) openrd sheevaplug lacie EXTRANAME = $(MEDIUM) # OpenRD @@ -22,3 +22,10 @@ sheevaplug: update-manifest $(SOME_DEST)/$(EXTRANAME)/marvell/guruplug/uImage Linux kernel for GuruPlug update-manifest $(SOME_DEST)/$(EXTRANAME)/marvell/guruplug/uInitrd initrd for GuruPlug +# LaCie NAS series: Network Space v2 (and parents), d2 Network v2 and *Big Network v2 +lacie: + mkdir -p $(SOME_DEST)/$(EXTRANAME)/lacie + 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 + update-manifest $(SOME_DEST)/$(EXTRANAME)/lacie/uInitrd initrd for LaCie NAS diff --git a/build/config/armel/kirkwood/network-console.cfg b/build/config/armel/kirkwood/network-console.cfg index 28b8e30..253916a 100644 --- a/build/config/armel/kirkwood/network-console.cfg +++ b/build/config/armel/kirkwood/network-console.cfg @@ -1,6 +1,6 @@ MEDIA_TYPE = netboot image (SSH) -TARGET = $(TEMP_INITRD) $(TEMP_KERNEL) ts219 ts41x +TARGET = $(TEMP_INITRD) $(TEMP_KERNEL) ts219 ts41x lacie EXTRANAME = $(MEDIUM) TYPE = netboot/network-console @@ -40,3 +40,10 @@ ts41x: update-manifest $(SOME_DEST)/$(EXTRANAME)/qnap/ts-41x/kernel Linux kernel for QNAP TS-41x update-manifest $(SOME_DEST)/$(EXTRANAME)/qnap/ts-41x/initrd.gz initrd for QNAP TS-41x +# LaCie NAS series: Network Space v2 (and parents), d2 Network v2 and *Big Network v2 +lacie: + mkdir -p $(SOME_DEST)/$(EXTRANAME)/lacie + 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 + update-manifest $(SOME_DEST)/$(EXTRANAME)/lacie/uInitrd initrd for LaCie NAS
Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
* Simon Guinot si...@sequanux.org [2012-04-26 12:41]: Actually no Debian installer images are provided for LaCie NASes based on Kirkwood SoC. Can you explain why you're creating both netboot and network-console images? How would a normal user install Debian on LaCie devices? Also, do LaCie devices have some kind of recovery mode or do users need a serial console if Debian stops working? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670530: debian-installer-6.0-netboot-armel: missing support for LaCie NASes (Kirkwood)
Hi Martin, On Thu, Apr 26, 2012 at 02:23:56PM +0100, Martin Michlmayr wrote: * Simon Guinot si...@sequanux.org [2012-04-26 12:41]: Actually no Debian installer images are provided for LaCie NASes based on Kirkwood SoC. Can you explain why you're creating both netboot and network-console images? How would a normal user install Debian on LaCie devices? A normal user would install Debian over ssh, using network-console and preseeding. Installing over the serial console is also possible but it is not very user friendly. One needs to open the case (voiding the warranty), to figure out the serial pineout and to connect an adapter as a max3232... I understand that creating the netboot image is wrong because the network-console image already includes the same installer (plus the network console). Isn't it ? Also, do LaCie devices have some kind of recovery mode or do users need a serial console if Debian stops working? There is no recovery mode available on the Kirkwood LaCie devices. If the Debian system breaks, a recovery system must be loaded from the U-Boot console (serial or network). Simon signature.asc Description: Digital signature
