Bug#655344: linux-image-3.1.0-1-kirkwood: Missing support for LaCie machines
Simon Guinot si...@sequanux.org writes: Hi, Hi, On Thu, Jan 12, 2012 at 12:08:06PM +0100, Arnaud Patard wrote: Simon Guinot si...@sequanux.org writes: Hi, Package: linux-2.6 Version: 3.1.6-1 Severity: important Dear Maintainer, The kernel image provided by package linux-image-3.1.0-1-kirkwood don't support the LaCie Kirkwood boards. Please, consider applying the following patch: diff --git a/config/armel/config.kirkwood b/config/armel/config.kirkwood index 1eae313..85b0c64 100644 --- a/config/armel/config.kirkwood +++ b/config/armel/config.kirkwood @@ -63,6 +63,12 @@ CONFIG_MACH_DOCKSTAR=y CONFIG_MACH_OPENRD_BASE=y CONFIG_MACH_OPENRD_CLIENT=y CONFIG_MACH_OPENRD_ULTIMATE=y +CONFIG_MACH_NETSPACE_V2=y +CONFIG_MACH_INETSPACE_V2=y +CONFIG_MACH_NETSPACE_MAX_V2=y +CONFIG_MACH_D2NET_V2=y +CONFIG_MACH_NET2BIG_V2=y +CONFIG_MACH_NET5BIG_V2=y CONFIG_MACH_T5325=y ## @@ -172,6 +178,11 @@ CONFIG_GPIO_SYSFS=y # CONFIG_DRM is not set ## +## file: drivers/hwmon/Kconfig +## +CONFIG_SENSORS_GPIO_FAN=m + +## ## file: drivers/i2c/Kconfig ## CONFIG_I2C=y @@ -244,6 +255,8 @@ CONFIG_ISDN_DIVAS_MAINT=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y CONFIG_LEDS_GPIO=y +CONFIG_LEDS_NS2=y +CONFIG_LEDS_NETXBIG=y CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_DEFAULT_ON=y Does this really need to be built-in ? (side note: if it can't work as module, why is it a tristate and not a boolean in kernel config ?) No it doesn't. I should have configured them as modules. ok. I've enabled the devices in svn for 3.2. By the way, why is the driver leds-gpio built-in ? There may be various reason, but I've no idea why. Also, do you plan to add support for them into d-i (unless it's already done) ? Note that the having d-i support is not mandatory to run Debian on a LaCie NAS. Please, let's fix the kernel support. On my side, I will have a look at the Debian installer as quickly as possible (knowing that I am quite busy this days). I didn't want to imply that d-i support was needed to enable the devices. I was thinking it would be a nice addition to this change in the kernel package. Thanks, Arnaud -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87vcofop6n@lebrac.rtp-net.org
Bug#655344: linux-image-3.1.0-1-kirkwood: Missing support for LaCie machines
Hi, On Fri, Jan 13, 2012 at 11:46:23AM +0100, Arnaud Patard wrote: Simon Guinot si...@sequanux.org writes: Hi, Hi, On Thu, Jan 12, 2012 at 12:08:06PM +0100, Arnaud Patard wrote: Simon Guinot si...@sequanux.org writes: Hi, Package: linux-2.6 Version: 3.1.6-1 Severity: important Dear Maintainer, The kernel image provided by package linux-image-3.1.0-1-kirkwood don't support the LaCie Kirkwood boards. Please, consider applying the following patch: diff --git a/config/armel/config.kirkwood b/config/armel/config.kirkwood index 1eae313..85b0c64 100644 --- a/config/armel/config.kirkwood +++ b/config/armel/config.kirkwood @@ -63,6 +63,12 @@ CONFIG_MACH_DOCKSTAR=y CONFIG_MACH_OPENRD_BASE=y CONFIG_MACH_OPENRD_CLIENT=y CONFIG_MACH_OPENRD_ULTIMATE=y +CONFIG_MACH_NETSPACE_V2=y +CONFIG_MACH_INETSPACE_V2=y +CONFIG_MACH_NETSPACE_MAX_V2=y +CONFIG_MACH_D2NET_V2=y +CONFIG_MACH_NET2BIG_V2=y +CONFIG_MACH_NET5BIG_V2=y CONFIG_MACH_T5325=y ## @@ -172,6 +178,11 @@ CONFIG_GPIO_SYSFS=y # CONFIG_DRM is not set ## +## file: drivers/hwmon/Kconfig +## +CONFIG_SENSORS_GPIO_FAN=m + +## ## file: drivers/i2c/Kconfig ## CONFIG_I2C=y @@ -244,6 +255,8 @@ CONFIG_ISDN_DIVAS_MAINT=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y CONFIG_LEDS_GPIO=y +CONFIG_LEDS_NS2=y +CONFIG_LEDS_NETXBIG=y CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_DEFAULT_ON=y Does this really need to be built-in ? (side note: if it can't work as module, why is it a tristate and not a boolean in kernel config ?) No it doesn't. I should have configured them as modules. ok. I've enabled the devices in svn for 3.2. Thanks. By the way, why is the driver leds-gpio built-in ? There may be various reason, but I've no idea why. Also, do you plan to add support for them into d-i (unless it's already done) ? Note that the having d-i support is not mandatory to run Debian on a LaCie NAS. Please, let's fix the kernel support. On my side, I will have a look at the Debian installer as quickly as possible (knowing that I am quite busy this days). I didn't want to imply that d-i support was needed to enable the devices. I was thinking it would be a nice addition to this change in the kernel package. Indeed and I will take care of this. Simon signature.asc Description: Digital signature
Bug#655344: linux-image-3.1.0-1-kirkwood: Missing support for LaCie machines
Simon Guinot si...@sequanux.org writes: Hi, Package: linux-2.6 Version: 3.1.6-1 Severity: important Dear Maintainer, The kernel image provided by package linux-image-3.1.0-1-kirkwood don't support the LaCie Kirkwood boards. Please, consider applying the following patch: diff --git a/config/armel/config.kirkwood b/config/armel/config.kirkwood index 1eae313..85b0c64 100644 --- a/config/armel/config.kirkwood +++ b/config/armel/config.kirkwood @@ -63,6 +63,12 @@ CONFIG_MACH_DOCKSTAR=y CONFIG_MACH_OPENRD_BASE=y CONFIG_MACH_OPENRD_CLIENT=y CONFIG_MACH_OPENRD_ULTIMATE=y +CONFIG_MACH_NETSPACE_V2=y +CONFIG_MACH_INETSPACE_V2=y +CONFIG_MACH_NETSPACE_MAX_V2=y +CONFIG_MACH_D2NET_V2=y +CONFIG_MACH_NET2BIG_V2=y +CONFIG_MACH_NET5BIG_V2=y CONFIG_MACH_T5325=y ## @@ -172,6 +178,11 @@ CONFIG_GPIO_SYSFS=y # CONFIG_DRM is not set ## +## file: drivers/hwmon/Kconfig +## +CONFIG_SENSORS_GPIO_FAN=m + +## ## file: drivers/i2c/Kconfig ## CONFIG_I2C=y @@ -244,6 +255,8 @@ CONFIG_ISDN_DIVAS_MAINT=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y CONFIG_LEDS_GPIO=y +CONFIG_LEDS_NS2=y +CONFIG_LEDS_NETXBIG=y CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_DEFAULT_ON=y Does this really need to be built-in ? (side note: if it can't work as module, why is it a tristate and not a boolean in kernel config ?) Also, do you plan to add support for them into d-i (unless it's already done) ? Thanks, Arnaud -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/877h0xp4a1@lebrac.rtp-net.org
Bug#655344: linux-image-3.1.0-1-kirkwood: Missing support for LaCie machines
On Thu, Jan 12, 2012 at 12:08, Arnaud Patard arnaud.pat...@rtp-net.org wrote: Simon Guinot si...@sequanux.org writes: Hi, Package: linux-2.6 Version: 3.1.6-1 Severity: important Dear Maintainer, The kernel image provided by package linux-image-3.1.0-1-kirkwood don't support the LaCie Kirkwood boards. Please, consider applying the following patch: diff --git a/config/armel/config.kirkwood b/config/armel/config.kirkwood index 1eae313..85b0c64 100644 --- a/config/armel/config.kirkwood +++ b/config/armel/config.kirkwood @@ -63,6 +63,12 @@ CONFIG_MACH_DOCKSTAR=y CONFIG_MACH_OPENRD_BASE=y CONFIG_MACH_OPENRD_CLIENT=y CONFIG_MACH_OPENRD_ULTIMATE=y +CONFIG_MACH_NETSPACE_V2=y +CONFIG_MACH_INETSPACE_V2=y +CONFIG_MACH_NETSPACE_MAX_V2=y +CONFIG_MACH_D2NET_V2=y +CONFIG_MACH_NET2BIG_V2=y +CONFIG_MACH_NET5BIG_V2=y CONFIG_MACH_T5325=y ## @@ -172,6 +178,11 @@ CONFIG_GPIO_SYSFS=y # CONFIG_DRM is not set ## +## file: drivers/hwmon/Kconfig +## +CONFIG_SENSORS_GPIO_FAN=m + +## ## file: drivers/i2c/Kconfig ## CONFIG_I2C=y @@ -244,6 +255,8 @@ CONFIG_ISDN_DIVAS_MAINT=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y CONFIG_LEDS_GPIO=y +CONFIG_LEDS_NS2=y +CONFIG_LEDS_NETXBIG=y CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_DEFAULT_ON=y Does this really need to be built-in ? (side note: if it can't work as module, why is it a tristate and not a boolean in kernel config ?) It seems a bit odd that Sheeva plug, Guru plug, Dockstar, OpenRD, Qnap and others(?) support is built-in, but support for Lacie is not. I'm not a (kernel)developer, so I don't know what problems this will bring up. But as a user I would appreciate it if Lacie support was in the standard kernel. If there is any reason this is not possible, I'll accept that off course. regards, Tjalling Also, do you plan to add support for them into d-i (unless it's already done) ? Thanks, Arnaud -- To unsubscribe, send mail to 655344-unsubscr...@bugs.debian.org. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAK864mMp_7VpmKBi3_-BLZ0-c8ixreE16-N+8J2v3ya=nlq...@mail.gmail.com
Bug#655344: linux-image-3.1.0-1-kirkwood: Missing support for LaCie machines
Hi Tjalling, On Thu, Jan 12, 2012 at 04:39:28PM +0100, Tjalling wrote: On Thu, Jan 12, 2012 at 12:08, Arnaud Patard arnaud.pat...@rtp-net.org wrote: Simon Guinot si...@sequanux.org writes: Hi, Package: linux-2.6 Version: 3.1.6-1 Severity: important Dear Maintainer, The kernel image provided by package linux-image-3.1.0-1-kirkwood don't support the LaCie Kirkwood boards. Please, consider applying the following patch: diff --git a/config/armel/config.kirkwood b/config/armel/config.kirkwood index 1eae313..85b0c64 100644 --- a/config/armel/config.kirkwood +++ b/config/armel/config.kirkwood @@ -63,6 +63,12 @@ CONFIG_MACH_DOCKSTAR=y CONFIG_MACH_OPENRD_BASE=y CONFIG_MACH_OPENRD_CLIENT=y CONFIG_MACH_OPENRD_ULTIMATE=y +CONFIG_MACH_NETSPACE_V2=y +CONFIG_MACH_INETSPACE_V2=y +CONFIG_MACH_NETSPACE_MAX_V2=y +CONFIG_MACH_D2NET_V2=y +CONFIG_MACH_NET2BIG_V2=y +CONFIG_MACH_NET5BIG_V2=y CONFIG_MACH_T5325=y ## @@ -172,6 +178,11 @@ CONFIG_GPIO_SYSFS=y # CONFIG_DRM is not set ## +## file: drivers/hwmon/Kconfig +## +CONFIG_SENSORS_GPIO_FAN=m + +## ## file: drivers/i2c/Kconfig ## CONFIG_I2C=y @@ -244,6 +255,8 @@ CONFIG_ISDN_DIVAS_MAINT=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y CONFIG_LEDS_GPIO=y +CONFIG_LEDS_NS2=y +CONFIG_LEDS_NETXBIG=y CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_DEFAULT_ON=y Does this really need to be built-in ? (side note: if it can't work as module, why is it a tristate and not a boolean in kernel config ?) It seems a bit odd that Sheeva plug, Guru plug, Dockstar, OpenRD, Qnap and others(?) support is built-in, but support for Lacie is not. I'm not a (kernel)developer, so I don't know what problems this will bring up. But as a user I would appreciate it if Lacie support was in the standard kernel. If there is any reason this is not possible, I'll accept that off course. I think there is a misunderstanding here. Arnaud is speaking about the LED support. Build the LEDs drivers as modules is correct. Simon signature.asc Description: Digital signature
Bug#655344: linux-image-3.1.0-1-kirkwood: Missing support for LaCie machines
On Thu, Jan 12, 2012 at 17:49, Simon Guinot si...@sequanux.org wrote: Hi Tjalling, On Thu, Jan 12, 2012 at 04:39:28PM +0100, Tjalling wrote: On Thu, Jan 12, 2012 at 12:08, Arnaud Patard arnaud.pat...@rtp-net.org wrote: Simon Guinot si...@sequanux.org writes: Hi, Package: linux-2.6 Version: 3.1.6-1 Severity: important Dear Maintainer, The kernel image provided by package linux-image-3.1.0-1-kirkwood don't support the LaCie Kirkwood boards. Please, consider applying the following patch: diff --git a/config/armel/config.kirkwood b/config/armel/config.kirkwood index 1eae313..85b0c64 100644 --- a/config/armel/config.kirkwood +++ b/config/armel/config.kirkwood @@ -63,6 +63,12 @@ CONFIG_MACH_DOCKSTAR=y CONFIG_MACH_OPENRD_BASE=y CONFIG_MACH_OPENRD_CLIENT=y CONFIG_MACH_OPENRD_ULTIMATE=y +CONFIG_MACH_NETSPACE_V2=y +CONFIG_MACH_INETSPACE_V2=y +CONFIG_MACH_NETSPACE_MAX_V2=y +CONFIG_MACH_D2NET_V2=y +CONFIG_MACH_NET2BIG_V2=y +CONFIG_MACH_NET5BIG_V2=y CONFIG_MACH_T5325=y ## @@ -172,6 +178,11 @@ CONFIG_GPIO_SYSFS=y # CONFIG_DRM is not set ## +## file: drivers/hwmon/Kconfig +## +CONFIG_SENSORS_GPIO_FAN=m + +## ## file: drivers/i2c/Kconfig ## CONFIG_I2C=y @@ -244,6 +255,8 @@ CONFIG_ISDN_DIVAS_MAINT=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y CONFIG_LEDS_GPIO=y +CONFIG_LEDS_NS2=y +CONFIG_LEDS_NETXBIG=y CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_DEFAULT_ON=y Does this really need to be built-in ? (side note: if it can't work as module, why is it a tristate and not a boolean in kernel config ?) It seems a bit odd that Sheeva plug, Guru plug, Dockstar, OpenRD, Qnap and others(?) support is built-in, but support for Lacie is not. I'm not a (kernel)developer, so I don't know what problems this will bring up. But as a user I would appreciate it if Lacie support was in the standard kernel. If there is any reason this is not possible, I'll accept that off course. I think there is a misunderstanding here. Arnaud is speaking about the LED support. Build the LEDs drivers as modules is correct. Ah, I misunderstood. Excuse me. regards, Tjalling Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk8PDv0ACgkQgtp0PDeOcDo8mACcD+EeLxTxfRUS4KlXZ98ll7r2 YxsAoJJBRJ19FZ07W8o6rdhSwEhKbquJ =gv6E -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cak864mox2xzbbhy-ewpru2t-fhrxhdrq526hdkbbjcnkr9b...@mail.gmail.com
Bug#655344: linux-image-3.1.0-1-kirkwood: Missing support for LaCie machines
Package: linux-2.6 Version: 3.1.6-1 Severity: important Dear Maintainer, The kernel image provided by package linux-image-3.1.0-1-kirkwood don't support the LaCie Kirkwood boards. Please, consider applying the following patch: diff --git a/config/armel/config.kirkwood b/config/armel/config.kirkwood index 1eae313..85b0c64 100644 --- a/config/armel/config.kirkwood +++ b/config/armel/config.kirkwood @@ -63,6 +63,12 @@ CONFIG_MACH_DOCKSTAR=y CONFIG_MACH_OPENRD_BASE=y CONFIG_MACH_OPENRD_CLIENT=y CONFIG_MACH_OPENRD_ULTIMATE=y +CONFIG_MACH_NETSPACE_V2=y +CONFIG_MACH_INETSPACE_V2=y +CONFIG_MACH_NETSPACE_MAX_V2=y +CONFIG_MACH_D2NET_V2=y +CONFIG_MACH_NET2BIG_V2=y +CONFIG_MACH_NET5BIG_V2=y CONFIG_MACH_T5325=y ## @@ -172,6 +178,11 @@ CONFIG_GPIO_SYSFS=y # CONFIG_DRM is not set ## +## file: drivers/hwmon/Kconfig +## +CONFIG_SENSORS_GPIO_FAN=m + +## ## file: drivers/i2c/Kconfig ## CONFIG_I2C=y @@ -244,6 +255,8 @@ CONFIG_ISDN_DIVAS_MAINT=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y CONFIG_LEDS_GPIO=y +CONFIG_LEDS_NS2=y +CONFIG_LEDS_NETXBIG=y CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_DEFAULT_ON=y Regards, Simon -- Package-specific info: Here are the boot logs: Marvell set bootcmd ext2load ide 0:1 0x80 /boot/uImage-3.1.0-1-kirkwood; ext2load ide 0:1 0x120 /boot/initrd.img-3.1.0-1-kirkwood; setenv bootargs console=ttyS0,115200 initrd=0x120 root=/dev/sda1; bootm 0x80 Marvell saveenv Marvell run bootcmd ## Valid DOS partition found ## ## Valid DOS partition found ## 1577596 bytes read ## Valid DOS partition found ## ## Valid DOS partition found ## 6559762 bytes read ## Booting image at 0080 ... Image Name: linux-3.1 Created: 2011-11-19 5:20:45 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1577532 Bytes = 1.5 MB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK OK bootargs from environment variables : console=ttyS0,115200 initrd=0x120 root=/dev/sda1 cap=gpt,lba64 Starting kernel ... Uncompressing Linux... done, booting the kernel. Error: unrecognized/unsupported machine ID (r1 = 0x0899). Available machine support: ID (hex)NAME 0690Marvell DB-88F6281-BP Development Board 0691Marvell RD-88F6192-NAS Development Board 0692Marvell RD-88F6281 Reference Board 078cMarvell 88F6281 GTW GE Board 0a76Marvell eSATA SheevaPlug Reference Board 0831Marvell SheevaPlug Reference Board 0a63Marvell GuruPlug Reference Board 0bb6Seagate FreeAgent DockStar 085bQNAP TS-119/TS-219 09c6QNAP TS-41x 0b44Marvell OpenRD Ultimate Board 0939Marvell OpenRD Client Board 0915Marvell OpenRD Base Board 0b1eHP t5325 Thin Client Please check your kernel config and/or bootloader. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: armel (armv5tel) Kernel: Linux 2.6.31.14-g2d85800-dirty Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.1.0-1-kirkwood depends on: ii debconf [debconf-2.0] 1.5.28 ii initramfs-tools [linux-initramfs-tool] 0.99 ii linux-base 3.4 ii module-init-tools 3.12~pre1-1 Versions of packages linux-image-3.1.0-1-kirkwood recommends: ii firmware-linux-free 3 ii uboot-mkimage2011.12-2 Versions of packages linux-image-3.1.0-1-kirkwood suggests: pn fdutilsnone pn linux-doc-3.1 none Versions of packages linux-image-3.1.0-1-kirkwood is related to: pn firmware-bnx2 none pn firmware-bnx2x none pn firmware-ipw2x00none pn firmware-ivtv none pn firmware-iwlwifinone pn firmware-linux none pn firmware-linux-nonfree none pn firmware-qlogic none pn firmware-ralink none pn xen-hypervisor none -- debconf information excluded signature.asc Description: Digital signature
