Bug#766400: installation-reports: [armhf] Netgear ReadyNAS104 report
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 <uwe+debian@kleine-koenig.org> [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/
Reply to: