Bug#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash
* Mike Miller [2013-06-27 09:15]: > FWIW, I successfully installed on this QNAP using a daily installer [1] > running 3.9-1-kirkwood. Here is the dmesg snippet probing the flash, > looks exactly like what you describe: Ben, can you please add the git comments listed here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714092#12 Thanks! -- 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#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash
On Thu, 2013-07-18 at 20:50 +0100, Martin Michlmayr wrote: > * Mike Miller [2013-06-27 09:15]: > > FWIW, I successfully installed on this QNAP using a daily installer [1] > > running 3.9-1-kirkwood. Here is the dmesg snippet probing the flash, > > looks exactly like what you describe: > > Ben, can you please add the git comments listed here: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714092#12 > > Thanks! I've added the N25Q128 IDs but didn't bother with the 256 Mbit part (not needed for this system). So this should be fixed in Debian 7.2. Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings. signature.asc Description: This is a digitally signed message part
Bug#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash
* Ben Hutchings [2013-07-20 22:40]: > > I've added the N25Q128 IDs but didn't bother with the 256 Mbit part (not > needed for this system). > > So this should be fixed in Debian 7.2. Thanks! -- 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#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash
On Sat, Jul 20, 2013 at 20:03:14 -0700, Martin Michlmayr wrote: > * Ben Hutchings [2013-07-20 22:40]: >> >> I've added the N25Q128 IDs but didn't bother with the 256 Mbit part (not >> needed for this system). >> >> So this should be fixed in Debian 7.2. > > Thanks! Yes, thanks very much Ben! -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash
* Mike Miller [2013-06-27 09:15]: > FWIW, I successfully installed on this QNAP using a daily installer [1] > running 3.9-1-kirkwood. Here is the dmesg snippet probing the flash, > looks exactly like what you describe: Ok, great! Ben, can you add the relevant patches? Thanks. -- 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#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash
Package: installation-reports Boot method: network-console Image version: ftp://ftp.debian.org/debian/dists/stable/main/installer-armel/current/images/kirkwood/network-console/qnap/ts-219 Date: 2013-06-25T12:16:57-0400 Machine: QNAP TS-212 Partitions: N/A Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[E] Overall install:[ ] Comments/Problems: I followed the instructions for installing Debian wheezy on the QNAP TS-212 at http://www.cyrius.com/debian/kirkwood/qnap/ts-219/install/. The installation failed at the last step, installing the kernel to the flash. I contacted Martin directly for help, and we (mostly he) concluded that the wheezy kernel does not have support for the flash chip in this particular model. The relevant line from the installer syslog Jun 25 15:35:14 kernel: [8.570234] m25p80 spi0.0: unrecognized JEDEC id 20ba18 shows that the wheezy kernel cannot read the flash. This results in the later error that terminates the install Jun 25 16:14:58 in-target: update-initramfs: Generating /boot/initrd.img-3.2.0-4-kirkwood Jun 25 16:15:06 in-target: flash-kernel: installing version 3.2.0-4-kirkwood Jun 25 16:15:07 in-target: Cannot find mtd partition 'Kernel' Jun 25 16:15:07 flash-kernel-installer: error: flash-kernel failed I see that support for this flash ID has been added in to the kernel as of 3.7. I plan to test one of the daily d-i images next with the jessie 3.9 kernel to verify that the problem is fixed there and that I can do a complete install on the TS-212. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7 (wheezy) - installer build 20130613" X_INSTALLATION_MEDIUM=network-console == Installer hardware-summary: == uname -a: Linux NASD65DC4 3.2.0-4-kirkwood #1 Debian 3.2.46-1 armv5tel GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Marvell Technology Group Ltd. Device [11ab:6282] (rev 01) lspci -knn: Subsystem: Marvell Technology Group Ltd. Device [11ab:11ab] lspci -knn: 00:01.0 USB controller [0c03]: Etron Technology, Inc. EJ168 USB 3.0 Host Controller [1b6f:7023] (rev 01) lspci -knn: Subsystem: Etron Technology, Inc. EJ168 USB 3.0 Host Controller [1b6f:7023] lspci -knn: Kernel driver in use: xhci_hcd usb-list: usb-list: Bus 01 Device 01: Marvell Orion EHCI [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01 usb-list:Manufacturer: Linux 3.2.0-4-kirkwood ehci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 01 Device 02: DS Pro [111d:] usb-list:Level 01 Parent 01 Port 00 Class 00(>ifc ) Subclass 00 Protocol 00 usb-list:Manufacturer: CENTON usb-list:Interface 00: Class 08(mstor) Subclass 06 Protocol 50 Driver usb-storage usb-list: usb-list: Bus 02 Device 01: xHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01 usb-list:Manufacturer: Linux 3.2.0-4-kirkwood xhci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 03 Device 01: xHCI Host Controller [1d6b:0003] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 03 usb-list:Manufacturer: Linux 3.2.0-4-kirkwood xhci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub lsmod: Module Size Used by lsmod: dm_mod 63295 0 lsmod: md_mod 94820 0 lsmod: jfs 152857 0 lsmod: ext4 376605 2 lsmod: jbd2 65925 1 ext4 lsmod: ext3 163387 0 lsmod: jbd57469 1 ext3 lsmod: btrfs 705618 0 lsmod: crc32c 2534 1 lsmod: libcrc32c876 1 btrfs lsmod: vfat8381 0 lsmod: fat42333 1 vfat lsmod: usb_storage35017 1 lsmod: ext2 54836 1 lsmod: mbcache 4464 3 ext2,ext3,ext4 lsmod: sd_mod 30976 6 lsmod: crc_t10dif 1110 1 sd_mod lsmod: evdev 7372 0 lsmod: sata_mv23583 3 lsmod: libata138944 1 sata_mv lsmod: xhci_hcd 68686 0 lsmod: ehci_hcd 37177 0 lsmod: scsi_mod 149345 3 libata,sd_mod,usb_sto
Bug#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash
* Mike Miller [2013-06-25 12:54]: > The relevant line from the installer syslog > Jun 25 15:35:14 kernel: [8.570234] m25p80 spi0.0: unrecognized JEDEC id > 20ba18 This ID was added in: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/mtd/devices/m25p80.c?id=98a9e2450667e497246449f96eab06eb3fb4d24b which depends on: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/mtd/devices/m25p80.c?id=3105875f6b8902628caee2fd7821af43707c6bde and http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/mtd/devices/m25p80.c?id=8da28681eb1430fb6715c7aef67001acfbbbcba5 The other problem is that arch/arm/mach-kirkwood/tsx1x-common.c contains: static const struct flash_platform_data qnap_tsx1x_flash = { .type = "m25p128", .name = "spi_flash", .parts = qnap_tsx1x_partitions, .nr_parts = ARRAY_SIZE(qnap_tsx1x_partitions), }; I'm not sure if .type is optional or if we have to create another flash_platform_data structure and initialize both (and then one will fail). Ben, do you know what the best solution would be for this? -- 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#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash
On Tue, 2013-06-25 at 20:10 +0100, Martin Michlmayr wrote: > * Mike Miller [2013-06-25 12:54]: > > The relevant line from the installer syslog > > Jun 25 15:35:14 kernel: [8.570234] m25p80 spi0.0: unrecognized JEDEC > > id 20ba18 > > This ID was added in: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/mtd/devices/m25p80.c?id=98a9e2450667e497246449f96eab06eb3fb4d24b > > which depends on: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/mtd/devices/m25p80.c?id=3105875f6b8902628caee2fd7821af43707c6bde > and > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/mtd/devices/m25p80.c?id=8da28681eb1430fb6715c7aef67001acfbbbcba5 > > The other problem is that arch/arm/mach-kirkwood/tsx1x-common.c > contains: > > static const struct flash_platform_data qnap_tsx1x_flash = { > .type = "m25p128", > .name = "spi_flash", > .parts = qnap_tsx1x_partitions, > .nr_parts = ARRAY_SIZE(qnap_tsx1x_partitions), > }; > > I'm not sure if .type is optional or if we have to create another > flash_platform_data structure and initialize both (and then one will > fail). Ben, do you know what the best solution would be for this? My reading of the m25p_probe() function is that if the named chip has a JEDEC ID, and the chip it finds has a different JEDEC ID that's also in the device ID table, it will then automatically adapt (but will warn). So long as the same partition map is used for the two chips, I think the platform code should just probe once as now, though the warning is annoying. It seems like there ought to be a way to tell m25p80 to auto-detect and warn only if the size doesn't match the partition map. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Bug#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash
On Wed, Jun 26, 2013 at 01:13:58 +0100, Ben Hutchings wrote: > My reading of the m25p_probe() function is that if the named chip has a > JEDEC ID, and the chip it finds has a different JEDEC ID that's also in > the device ID table, it will then automatically adapt (but will warn). > > So long as the same partition map is used for the two chips, I think the > platform code should just probe once as now, though the warning is > annoying. It seems like there ought to be a way to tell m25p80 to > auto-detect and warn only if the size doesn't match the partition map. FWIW, I successfully installed on this QNAP using a daily installer [1] running 3.9-1-kirkwood. Here is the dmesg snippet probing the flash, looks exactly like what you describe: [8.328203] m25p80 spi0.0: found n25q128a13, expected m25p128 [8.334003] m25p80 spi0.0: n25q128a13 (16384 Kbytes) [8.338989] Creating 6 MTD partitions on "spi_flash": [8.344074] 0x-0x0008 : "U-Boot" [8.349708] 0x0020-0x0040 : "Kernel" [8.355309] 0x0040-0x00d0 : "RootFS1" [8.360987] 0x00d0-0x0100 : "RootFS2" [8.366689] 0x0008-0x000c : "U-Boot Config" [8.372895] 0x000c-0x0020 : "NAS Config" [1] http://d-i.debian.org/daily-images/armel/20130625-08:44/kirkwood/network-console/qnap/ts-219/ -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org