Bug#804351: installation-reports: Stretch installer-armel (2015-10-23) does not see storage devices on Dreamplug
Package: installation-reports Severity: important When I run Jessie installer, I can see the USB stick (which the installer was loaded from), and the internal microSD. With current Stretch installer, neither storage device is visible. I'm attaching screen and installer logs for both cases. The installers were downloaded from: http://ftp.debian.org/debian/dists/stable/main/installer-armel/current/images/kirkwood/netboot/marvell/dreamplug/ http://ftp.debian.org/debian/dists/stretch/main/installer-armel/current/images/kirkwood/netboot/marvell/dreamplug/ Marvell>> version U-Boot 2014.10+dfsg1-5 (Apr 07 2015 - 21:53:14) Marvell-DreamPlug gcc (Debian 4.9.2-10) 4.9.2 GNU ld (GNU Binutils for Debian) 2.25 -- James jessie-install-dreamplug.tar.gz Description: application/gzip stretch-install-dreamplug.tar.gz Description: application/gzip signature.asc Description: OpenPGP digital signature
Bug#804351: installation-reports: Stretch installer-armel (2015-10-23) does not see storage devices on Dreamplug
On 11/11/2015 03:43 PM, Ian Campbell wrote: > Perhaps you could drop to a shell and try manually loading those > modules and see what, if anything, it says? Modules seem to load ok: ~ # lsmod Module Size Used by ~ # modprobe ehci_hcd ~ # lsmod Module Size Used by ehci_hcd 50075 0 usbcore 141043 1 ehci_hcd usb_common 2533 1 usbcore ~ # modprobe ehci_orion ~ # lsmod Module Size Used by ehci_orion 2986 0 ehci_hcd 50075 1 ehci_orion usbcore 141043 2 ehci_hcd,ehci_orion usb_common 2533 1 usbcore After a reboot, I saw different modules loaded (randomly?): ~ # lsmod Module Size Used by mvmdio 3100 0 of_mdio 2677 1 mvmdio libphy 23336 2 mvmdio,of_mdio ~ # modprobe ehci_hcd ~ # lsmod Module Size Used by ehci_hcd 50075 0 usbcore 141043 1 ehci_hcd usb_common 2533 1 usbcore mvmdio 3100 0 of_mdio 2677 1 mvmdio libphy 23336 2 mvmdio,of_mdio ~ # modprobe ehci_orion ~ # lsmod Module Size Used by ehci_orion 2986 0 ehci_hcd 50075 1 ehci_orion usbcore 141043 2 ehci_hcd,ehci_orion usb_common 2533 1 usbcore mvmdio 3100 0 of_mdio 2677 1 mvmdio libphy 23336 2 mvmdio,of_mdio Strangely, my Dreamplug is also hanging at hw-detect step now. (I didn't see this previously.) -- James signature.asc Description: OpenPGP digital signature
Bug#804351: installation-reports: Stretch installer-armel (2015-10-23) does not see storage devices on Dreamplug
On 11/12/2015 05:19 AM, Ian Campbell wrote: > On Wed, 2015-11-11 at 19:13 -0500, James Valleroy wrote: >> On 11/11/2015 03:43 PM, Ian Campbell wrote: >>> Perhaps you could drop to a shell and try manually loading those >>> modules and see what, if anything, it says? >> Modules seem to load ok: > Did lsusb (or maybe usb-list in d-i env) then start showing the devices? > Alternatively I think they appear under /proc somewhere and I would expect > some stuff in dmesg too. > > You could also try load usb-storage and/or sd_mod to see if the disks are > then found. > > [...] I've attached a log. The devices were shown under usb-list. But usb-storage and sd_mod modules are not available. >> After a reboot, I saw different modules loaded (randomly?): > Might just be to do with how far through d-i you go before dropping to a > shell? > Nope...I get different results even if I drop to a shell immediately. > >> Strangely, my Dreamplug is also hanging at hw-detect step now. (I didn't >> see this previously.) > It's not impossible that this is related, since I would expect hw-detect to > responsible in some way for loading some of this stuff (although I would > expect it primarily to happen via udev once the modules were actually > available, which they seem to be). > > Perhaps a "udevadm trigger" would be interesting to try? > > Ian. Sorry, it's not hw-detect that hangs actually. I can run that from the shell without any issue. But the installer step for "hardware detection" hangs (even after loading the 2 modules and running udevadm trigger). -- James ~ # lsmod Module Size Used by mvsdio 9173 0 mmc_core 105606 1 mvsdio ~ # modprobe ehci_hcd ~ # modprobe ehci_orion ~ # lsmod Module Size Used by ehci_orion 2986 0 ehci_hcd 50075 1 ehci_orion usbcore 141043 2 ehci_hcd,ehci_orion usb_common 2533 1 usbcore mvsdio 9173 0 mmc_core 105606 1 mvsdio ~ # dmesg | tail [ 46.668250] usb 1-1.1.1: new high-speed USB device number 6 using orion-ehci [ 46.764183] usb 1-1.1.1: New USB device found, idVendor=05e3, idProduct=0723 [ 46.764199] usb 1-1.1.1: New USB device strings: Mfr=3, Product=4, SerialNumber=0 [ 46.764235] usb 1-1.1.1: Product: USB Storage [ 46.764245] usb 1-1.1.1: Manufacturer: Generic [ 46.840238] usb 1-1.1.2: new high-speed USB device number 7 using orion-ehci [ 46.936186] usb 1-1.1.2: New USB device found, idVendor=05e3, idProduct=0723 [ 46.936226] usb 1-1.1.2: New USB device strings: Mfr=3, Product=4, SerialNumber=0 [ 46.936237] usb 1-1.1.2: Product: USB Storage [ 46.936247] usb 1-1.1.2: Manufacturer: Generic ~ # usb-list Bus 01 Device 01: EHCI Host Controller [1d6b:0002] Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01 Manufacturer: Linux 4.2.0-1-kirkwood ehci_hcd Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub Bus 01 Device 02: USB 2.0 Hub [1a40:0101] Level 01 Parent 01 Port 00 Class 09(hub ) Subclass 00 Protocol 01 Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub Bus 01 Device 03: USB 2.0 Hub [1a40:0101] Level 02 Parent 02 Port 00 Class 09(hub ) Subclass 00 Protocol 01 Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub Bus 01 Device 06: USB Storage [05e3:0723] Level 03 Parent 03 Port 00 Class 00(>ifc ) Subclass 00 Protocol 00 Manufacturer: Generic Interface 00: Class 08(mstor) Subclass 06 Protocol 50 Driver Bus 01 Device 07: USB Storage [05e3:0723] Level 03 Parent 03 Port 01 Class 00(>ifc ) Subclass 00 Protocol 00 Manufacturer: Generic Interface 00: Class 08(mstor) Subclass 06 Protocol 50 Driver Bus 01 Device 04: Cruzer [0781:5530] Level 02 Parent 02 Port 02 Class 00(>ifc ) Subclass 00 Protocol 00 Manufacturer: SanDisk Interface 00: Class 08(mstor) Subclass 06 Protocol 50 Driver Bus 01 Device 05: C-Media USB Headphone Set [0d8c:000c] Level 02 Parent 02 Port 03 Class 00(>ifc ) Subclass 00 Protocol 00 Interface 00: Class 01(audio) Subclass 01 Protocol 00 Driver Interface 01: Class 01(audio) Subclass 02 Protocol 00 Driver Interface 02: Class 01(audio) Subclass 02 Protocol 00 Driver Interface 03: Class 03(HID ) Subclass 00 Protocol 00 Driver ~ # modprobe usb-storage modprobe: FATAL: Module usb-storage not found. ~ # modprobe sd_mod modprobe: FATAL: Module sd_mod not found. ~ # udevadm trigger ~ # hw-detect ... ~ # dmesg | tail [ 46.764199] usb 1-1.1.1: New USB device strings: Mfr=3, Product=4, SerialNumber=0 [ 46.764235] usb 1-1.1.1: Product: USB Storage [ 46.764245] usb 1-1.1.1: Manufacturer: Generic [ 46.840238] usb 1-1.1.2: new high-speed USB device number 7 using orion-ehci [ 46.936186] usb 1-1.1.2:
Bug#804351: installation-reports: Stretch installer-armel (2015-10-23) does not see storage devices on Dreamplug
On 11/28/2015 07:04 AM, Ian Campbell wrote: > On Thu, 2015-11-12 at 06:50 -0500, James Valleroy wrote: > > Hi James, > > I think this should be fixed in the latest dailies from > http://d-i.debian.org/daily-images/armel/daily/kirkwood/netboot/marvell/ > or at least my dreamplug is OK in recovery mode with the one from 2 days ago. > > This will then propagate to Stretch with the next d-i alpha/beta. > > Ian Hi Ian, Yes, it's working now with the daily image. I'm able to complete the install and boot into the system. Thanks for your help! James signature.asc Description: OpenPGP digital signature
Bug#869488: flash-kernel: Patch for Raspberry Pi 3 support
Package: flash-kernel Severity: wishlist Tags: patch Dear Maintainer, Please consider the attached patch which adds support for Raspberry Pi 3 Model B. I haven't been able to build a bootable image yet, but I have tested running flash-kernel with this entry added in a vmdebootstrap customize script. >From 78064bb4ff0b78bed7aefca489f6c6ee8d3bf42b Mon Sep 17 00:00:00 2001 From: James Valleroy Date: Sat, 22 Jul 2017 19:36:43 -0400 Subject: [PATCH] Add a machine db entry for the Raspberry Pi 3 Model B. --- db/all.db | 7 +++ 1 file changed, 7 insertions(+) diff --git a/db/all.db b/db/all.db index 5327882..427daf5 100644 --- a/db/all.db +++ b/db/all.db @@ -1312,6 +1312,13 @@ U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools Boot-Script-Path: /boot/boot.scr +Machine: Raspberry Pi 3 Model B +Kernel-Flavors: arm64 +DTB-Id: bcm2836-rpi-3-b.dtb +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools +Boot-Script-Path: /boot/boot.scr + Machine: Seagate FreeAgent Dockstar Machine: Seagate FreeAgent DockStar Kernel-Flavors: kirkwood marvell -- 2.11.0
Bug#869488: flash-kernel: Patch for Raspberry Pi 3 support
On 07/23/2017 01:23 PM, Vagrant Cascadian wrote: > On 2017-07-23, James Valleroy wrote: >> Please consider the attached patch which adds support for Raspberry Pi >> 3 Model B. > ... >> +Machine: Raspberry Pi 3 Model B >> +Kernel-Flavors: arm64 >> +DTB-Id: bcm2836-rpi-3-b.dtb >> +U-Boot-Script-Name: bootscr.uboot-generic >> +Required-Packages: u-boot-tools >> +Boot-Script-Path: /boot/boot.scr > > I think the .dtb you want is bcm2837-rpi-3-b.dtb. Oops, yeah. That is the dtb I tested with, but I forgot to update the patch. Corrected one is attached. From 7e75202ec71b024983b154e361f8b4d16dc0ebf5 Mon Sep 17 00:00:00 2001 From: James Valleroy Date: Sat, 22 Jul 2017 19:36:43 -0400 Subject: [PATCH] Add a machine db entry for the Raspberry Pi 3 Model B. --- db/all.db | 7 +++ 1 file changed, 7 insertions(+) diff --git a/db/all.db b/db/all.db index 5327882..3347506 100644 --- a/db/all.db +++ b/db/all.db @@ -1312,6 +1312,13 @@ U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools Boot-Script-Path: /boot/boot.scr +Machine: Raspberry Pi 3 Model B +Kernel-Flavors: arm64 +DTB-Id: bcm2837-rpi-3-b.dtb +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools +Boot-Script-Path: /boot/boot.scr + Machine: Seagate FreeAgent Dockstar Machine: Seagate FreeAgent DockStar Kernel-Flavors: kirkwood marvell -- 2.11.0 signature.asc Description: OpenPGP digital signature
Bug#916822: installation-reports: A20-OLinuXino-Lime2 Rev. K: Fails to boot installer from SD card
Package: installation-reports Severity: normal Dear Maintainer, I tried to run testing installer on A20-OLinuXino-Lime2 Rev. K board, and it failed to boot the installer. The same installer image works ok (with no issues) on a Lime2 Rev. C board. Serial console log: --- U-Boot SPL 2018.11+dfsg-1 (Nov 14 2018 - 21:32:35 +) DRAM: 1024 MiB CPU: 91200Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2018.11+dfsg-1 (Nov 14 2018 - 21:32:35 +) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-OLinuXino-LIME2 I2C: ready DRAM: 1 GiB Nothing else was shown on the serial console after this point. -- Package-specific info: Boot method: SD card Image version: https://get.debian.org/debian/dists/testing/main/installer-armhf/20181206/images/netboot/SD-card-images/ partition.img.gz and firmware.A20-OLinuXino-Lime2.img.gz from 2018-12-05 Date: 2018-12-18 Machine: A20-OLinuXino-Lime2 Rev. K Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] signature.asc Description: OpenPGP digital signature
Bug#916822: installation-reports: A20-OLinuXino-Lime2 Rev. K: Fails to boot installer from SD card
I'm now trying the testing-20190118 installer. Looks like it gets a bit further on the Rev. K board: U-Boot SPL 2019.01+dfsg-1 (Jan 15 2019 - 00:36:19 +) DRAM: 1024 MiB CPU: 91200Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2019.01+dfsg-1 (Jan 15 2019 - 00:36:19 +) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-OLinuXino-LIME2 I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 Loading Environment from FAT... *** Warning - bad CRC, using default environment In:serial Out: serial Err: serial Allwinner mUSB OTG (Peripheral) SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@1c5 Warning: usb_ether using MAC address from ROM , eth1: usb_ether starting USB... USB0: The Rev. C board is still working ok, and boots to the installer. signature.asc Description: OpenPGP digital signature
Bug#916822: installation-reports: A20-OLinuXino-Lime2 Rev. K: Fails to boot installer from SD card
Additional note: - The Rev. C board (working) does not have eMMC or NAND. - The Rev. K board (not working) has 16 GB eMMC. But I am trying to boot from micro SD card. signature.asc Description: OpenPGP digital signature
Bug#931195: flash-kernel: Add entry for Olimex A64-Olinuxino
Hello, Can this patch be merged? We would like to start building FreedomBox images for the A64 Olinuxino: https://salsa.debian.org/freedombox-team/freedom-maker/merge_requests/170 Regards, James signature.asc Description: OpenPGP digital signature
