Bodhi, Thank you again. This project is de-prioritized for now. There is one puzzling area that I plan to take a closer look at: [ 14.925325] usb usb2-port1: over-current condition [ 15.005331] usb usb3-port1: over-current condition [ 15.165337] usb usb2-port2: over-current condition [ 15.245331] usb usb3-port2: over-current condition Take care!by Olek - Debian
Bodhi, Mint on laptop reports the USB stick as: Bus 002 Device 004: ID 058f:6387 Alcor Micro Corp. Flash Drive Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x05by Olek - Debian
Bodhi, With the USB stick plugged in the top, here is the output of the lsusb -vvv command: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 1 Single TT bMaxPacketSize0by Olek - Debian
Bodhi, Thanks for a quick response. Unfortunately, there is no activity (dmesg) when the USB pendrive is plugged in, not even a brief flash of light from its internal LED. I verified that the drive is good by plugging it in laptop with Mint running - LED flashes and the OS reports the pendrive as an ext4 one labeled 'rootfs'. My pogo boots up from an SD card, btw. For clarity, SAby Olek - Debian
Hello gents, First off, happy New Year 2020 to everyone and their families. May it bring joy and happiness. I am puzzled by this issue: whenever a USB or a SATA drive is plugged in, nothing happens. There are no messages on the screen, the Pogo seems to be unaware of any devices plugged in. I tried two known working USB sticks and two SATA drives, one spinner (ext4) and one SSD (this one hby Olek - Debian
Bodhi, A quick heads-up before you spend any more time on this - I went ahead and restored uboot's 's envs from the default ones per instructions in the Uboot section and voila, the system booted up. The working envs: bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addby Olek - uBoot
Bodhi, Managed to boot the system with pristine Debian (5.2.9) per this post, thank you very much: https://forum.doozan.com/read.php?3,28772,29034#msg-29034 Sadly, the 5.4.2 installation no longer exist - I wiped it out. Now I need to figure out how to clean up the envs. Thanks! O.by Olek - uBoot
Hi there, first time poster on this forum. I can no longer boot my pogoplug V4 (pink logo) to Debian after an unsuccessful upgrade to kernel 5.4.2. Probably took the wrong turn somewhere in Step 4 (4b I guess). Uboot messages: U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB MMC:by Olek - uBoot