Bug#806926: Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report

[Martin Michlmayr]

Hi Uwe,

Can you review your old Netgear ReadyNAS 102/104 patch for
flash-kernel and apply them?

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#806926: Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report

[Martin Michlmayr]

* Uwe Kleine-König  [2016-02-18 20:47]:
> Do we need "Bootloader-Sets-Incorrect-Root: yes"? I modified the u-boot
> env to pass the right root= and rootflags= parameter.

Right, that's requrired, too.

> Gijs uses
> 
>   U-Boot-Initrd-Address: 0x0
> 
> on a rn102, but I think this is not optimal.

I cannot remember for sure but I thought there was an issue with the
numbers you picked.  I'd have to check my mails with Gijs if you
cannot remember.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#806926: Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report

[Uwe Kleine-König]

Hi Martin,

On 02/18/2016 08:36 PM, Martin Michlmayr wrote:
> Uwe, does that look ok?

Yes, the rn104 entry is what I'm using, I'm just missing the
Kernel-Flavors line, which looks ok, too.

Do we need "Bootloader-Sets-Incorrect-Root: yes"? I modified the u-boot
env to pass the right root= and rootflags= parameter.

Gijs uses

U-Boot-Initrd-Address: 0x0

on a rn102, but I think this is not optimal.

Best regards
Uwe

Bug#806926: Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report

[Martin Michlmayr]

Uwe, does that look ok?

diff --git a/README b/README
index 1774af6..d354c87 100644
--- a/README
+++ b/README
@@ -46,6 +46,8 @@ The following systems are supported:
  - Marvell OpenRD-Client
  - Marvell OpenRD-Ultimate
  - Neo FreeRunner (GTA02)
+ - NETGEAR ReadyNAS 102
+ - NETGEAR ReadyNAS 104
  - PlatHome OpenBlocks AX3-4 board
  - Plat'Home OpenBlocks A6
  - QNAP TS-109
diff --git a/db/all.db b/db/all.db
index 38241ce..057031f 100644
--- a/db/all.db
+++ b/db/all.db
@@ -820,6 +820,26 @@ DTB-Id: sun6i-a31s-primo81.dtb
 U-Boot-Script-Name: bootscr.sunxi
 Required-Packages: u-boot-tools
 
+Machine: NETGEAR ReadyNAS 102
+Kernel-Flavors: armmp armmp-lpae
+DTB-Id: armada-370-netgear-rn102.dtb
+DTB-Append: yes
+Mtd-Kernel: uImage
+Mtd-Initrd: minirootfs
+U-Boot-Kernel-Address: 0x0400
+U-Boot-Initrd-Address: 0x0500
+Required-Packages: u-boot-tools
+
+Machine: NETGEAR ReadyNAS 104
+Kernel-Flavors: armmp armmp-lpae
+DTB-Id: armada-370-netgear-rn104.dtb
+DTB-Append: yes
+Mtd-Kernel: uImage
+Mtd-Initrd: minirootfs
+U-Boot-Kernel-Address: 0x0400
+U-Boot-Initrd-Address: 0x0500
+Required-Packages: u-boot-tools
+
 Machine: NVIDIA Tegra124 Jetson TK1
 Kernel-Flavors: armmp armmp-lpae
 DTB-Id: tegra124-jetson-tk1.dtb

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report

[Martin Michlmayr]

* Ian Campbell  [2014-10-23 08:47]:
> > One of the last messages from the installer is:
> > 
> > You will need to boot manually with the /boot/vmlinuz kernel on
> > partition /dev/sda1 and root=/dev/sda1 passed as a kernel argument.
> 
> Which bootloader does the system have? This could possibly be resolved
> by adding the system to the flash-kernel database? (nb f-k is no longer
> only about booting from flash...)

Uwe posted a flash-kernel stanza to his blog:
http://blog.kleine-koenig.org/ukl/installing-debian-jessie-on-a-netgear-readynas-104.html

The same would have to be added for the ReadyNAS 102.

Machine: NETGEAR ReadyNAS 102
DTB-Id: armada-370-netgear-rn102.dtb

Plus presumably Kernel-Flavors: armmp.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report

[Martin Michlmayr]

clone 766400 -1 -2
reassign -1 nobootloader
severity -1 wishlist
retitle -1 Please mention root=UUID=... and initrd location
reassign -2 flash-kernel
severity -2 wishlist
retitle -2 Please add support for Netgear Ready NAS102 and NAS104
thanks

* Uwe Kleine-Koenig  [2014-10-22 22:16]:
> One of the last messages from the installer is:
> 
>   You will need to boot manually with the /boot/vmlinuz kernel on
>   partition /dev/sda1 and root=/dev/sda1 passed as a kernel argument.
> 
> It would be nice to mention that also using
> /boot/initrd.img-3.16-3-armmp is necessary. Also it could suggest
> root=UUID=3d8bbd9f... as is used in /etc/fstab (for good reasons).

I guess few people see nobootloader these days, so it was never
updated to display the UUID and mention the initrd.

> RTC doesn't work:
> 
> $ dmesg | grep rtc
> [2.782368] rtc-mv d0010300.rtc: internal RTC not ticking
> [2.862432] /home/uwe/linux/drivers/rtc/hctosys.c: unable to open rtc 
> device (rtc0)

This was fixed in kernel.org in commit 784693def2d36f525d2d259394fd39ac87fc4449

> I think this is a hardware problem, as there is also an Intersil
> ISL12057 assembled, but
> 
> $ grep ISL12057 /boot/config-3.16-3-armmp 
> # CONFIG_RTC_DRV_ISL12057 is not set

This is built into the jessie kernel now.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report

[Ian Campbell]

On Wed, 2014-10-22 at 22:16 +0200, Uwe Kleine-Koenig wrote:
 
 One of the last messages from the installer is:
 
 You will need to boot manually with the /boot/vmlinuz kernel on
 partition /dev/sda1 and root=/dev/sda1 passed as a kernel argument.

Which bootloader does the system have? This could possibly be resolved
by adding the system to the flash-kernel database? (nb f-k is no longer
only about booting from flash...)

Ian.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report

[Uwe Kleine-Koenig]

Package: installation-reports
Severity: normal
Tags: d-i



-- Package-specific info:

Boot method: network
Image version: self built kernel image from sid@21966 + d-i@4e5cbb3 + 
armada-370-netgear-rn104.dtb
Date: 2014-10-22

Machine: Netgear ReadyNAS 104
Partitions: 1.8T btrfs for /, 200G swap (planned: use sibling disk for
btrfs raid1 which is not supported by the installer)

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:[ ]
Overall install:[O]

Comments/Problems:

At least linux-image-3.16-3-armmp_3.16.5-2 is needed to be able to
access the hard disks (CONFIG_PCI_MVEBU=y). (That didn't enter sid up to
now, that's why I need to build from kernel/trunk myself.)

Boot setup needs more work, currently I boot via tftp.

One of the last messages from the installer is:

You will need to boot manually with the /boot/vmlinuz kernel on
partition /dev/sda1 and root=/dev/sda1 passed as a kernel argument.

It would be nice to mention that also using
/boot/initrd.img-3.16-3-armmp is necessary. Also it could suggest
root=UUID=3d8bbd9f... as is used in /etc/fstab (for good reasons).

RTC doesn't work:

$ dmesg | grep rtc
[2.782368] rtc-mv d0010300.rtc: internal RTC not ticking
[2.862432] /home/uwe/linux/drivers/rtc/hctosys.c: unable to open rtc device 
(rtc0)

I think this is a hardware problem, as there is also an Intersil
ISL12057 assembled, but

$ grep ISL12057 /boot/config-3.16-3-armmp 
# CONFIG_RTC_DRV_ISL12057 is not set

-- 

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=8 (jessie) - installer build 20141022-18:01
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux crater 3.16-3-armmp #1 SMP Debian 3.16.5-1ukl0 (2014-10-21) 
armv7l GNU/Linux
lspci -knn: 00:01.0 PCI bridge [0604]: Marvell Technology Group Ltd. Device 
[11ab:6710] (rev 01)
lspci -knn: 00:02.0 PCI bridge [0604]: Marvell Technology Group Ltd. Device 
[11ab:6710] (rev 01)
lspci -knn: 01:00.0 USB controller [0c03]: Fresco Logic FL1009 USB 3.0 Host 
Controller [1b73:1009] (rev 02)
lspci -knn: Subsystem: Fresco Logic Device [1b73:]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 02:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 
Device [1b4b:9215] (rev 11)
lspci -knn: Subsystem: Marvell Technology Group Ltd. Device [1b4b:9215]
lspci -knn: Kernel driver in use: ahci
usb-list: 
usb-list: Bus 01 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.16-3-armmp xhci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 02 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.16-3-armmp xhci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
lsmod: Module  Size  Used by
lsmod: dm_mod 87334  0 
lsmod: md_mod110729  0 
lsmod: jfs   169319  0 
lsmod: crc32c_generic  1598  1 
lsmod: btrfs 953065  1 
lsmod: xor 5226  1 btrfs
lsmod: zlib_deflate   20524  1 btrfs
lsmod: raid6_pq   83885  1 btrfs
lsmod: vfat9621  0 
lsmod: fat52693  1 vfat
lsmod: ext4  485433  0 
lsmod: crc16   1146  1 ext4
lsmod: mbcache 8210  1 ext4
lsmod: jbd2   88199  1 ext4
lsmod: usb_storage41751  0 
lsmod: sg 20824  0 
lsmod: sd_mod 38535  3 
lsmod: crc_t10dif  1041  1 sd_mod
lsmod: crct10dif_common1159  1 crc_t10dif
lsmod: ahci   12890  2 
lsmod: libahci23069  1 ahci
lsmod: libata161761  2 ahci,libahci
lsmod: scsi_mod  175644  4 sg,usb_storage,libata,sd_mod
lsmod: marvell 6838  0 
lsmod: xhci_hcd  146485  0 
lsmod: mvmdio  3245  0