bodhi, I'm going to be traveling for the next few weeks and will resume this when I get back. Thanks for all your help.by unmesh - Debian
So I installed the latest u-boot but am still not able to boot either 5.2.9 or 4.4.0. In the latter case, /etc/fstab was showing '/dev/root ext2' so I used a USB stick formatted with ext2. I'm not doing a mkimage since it is a new bootloader Since the activity light does not flash with either of the two rootfs's, there must be something more basic that I'm doing wrong.by unmesh - Debian
It does boot to stock OS. In fact, it was the first thing I checked when I powered it up!by unmesh - Debian
I decided to limit my ambition to an upgrade to only Jessie and was continuing to get errors including one for a java upgrade from a non-existent repository. I finally figured out where this was being requested and deleted it. '/etc/apt/sources.list.d/webupd8team-java.list' It started doing the install without errors and I left it doing so while I attended to other things for a coby unmesh - Debian
'ls -lart' total 55988 drwxr-xr-x 21 root root 4096 Feb 17 2015 .. drwxr-xr-x 2 root root 4096 Aug 16 19:01 dts -rwxr-xr-x 1 root root 4963616 Aug 17 22:43 zImage-5.2.9-kirkwood-tld-1 -rw-r--r-- 1 root root 165790 Aug 18 00:24 config-5.2.9-kirkwood-tld-1 -rw------- 1 root root 4963616 Aug 18 00:27 vmlinuz-5.2.9-kirkwood-tld-1 -rw------- 1 root root 3101889 Aug 18 0by unmesh - Debian
I tried a new buster rootfs install on a SDHC card and it didn't boot, even after the modifying the fstab file to use /dev/sda1 instead of the rootfs label The LED is a steady orange instead of green with Wheezyby unmesh - Debian
Didn't boot. Does it matter which Dockstar USB port I use?by unmesh - Debian
'apt-get -y install debian-keyring debian-archive-keyring' Get:1 http://ftp.us.debian.org/debian/ buster/main debian-archive-keyring all 2019.1 [75.1 kB] Get:2 http://ftp.us.debian.org/debian/ buster/main debian-keyring all 2019.02.25 [32.4 MB] Fetched 32.4 MB in 19s (1689 kB/s) E: /var/cache/apt/archives/debian-archive-keyring_2019.1_all.deb not a valid DEB package. E: Prior errby unmesh - Debian
It is davygravy's bootloader! The prepared USB stick activity light blinks momentarily when plugged into the Dockstar and its LED stays a solid orange. It is not on the network. The instructions said to do everything as root but I did this by booting an Ubuntu Live USB and using 'sudo su' in a Terminal Also used 'e2label /dev/sdc1 rootfs' for the purpose of labelby unmesh - Debian
'apt update' gave the following messages W: GPG error: http://ftp.us.debian.org buster Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY DCC9EFBF77E11517 W: GPG error: http://security.debian.org buster/updates Release: The following signatures couldn't be verifiedby unmesh - Debian
I dusted off my old Dockstar and can't find the USB stick that had Debian installed on it. The box boots into the Pogoplug OS and gets on the network but does not have the capability to install Debian on an attached USB stick that I could figure out. Is there a way to create a bootable USB for it? The output of fw_printenv is: ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=by unmesh - Debian
root@DebianPlugMobile:~# cat /etc/debian_version 7.9 By upgrade, you mean using apt-get update apt-get upgrade Thanksby unmesh - Debian
Currently running 4.2.0 on latest uboot. When trying to upgrade to 5.3.2, I get the following error message # dpkg -i linux-image-5.3.2-kirkwood-tld-1_1.0_armel.deb dpkg-deb: error: archive 'linux-image-5.3.2-kirkwood-tld-1_1.0_armel.deb' contains not understood data member control.tar.xz, giving up dpkg: error processing linux-image-5.3.2-kirkwood-tld-1_1.0_armel.deb (--install)by unmesh - Debian
bodhi Wrote: ------------------------------------------------------- > unmesh, > > Booting Debian looks good, and you've confirmed > it. You can't boot into Pogo OS (when there is no > USB plugged in) because the mtd partiton that > houses the orginal u-boot has error. > > If you want to do boot Pogo OS, you have to find a > original copy of the mby unmesh - uBoot
Here is the log U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52) Pogo E02 SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboot: 0 (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices.by unmesh - uBoot
I think I followed the instructions in the first post carefully to install the new U-Boot in my E02 running Debian but it won't boot either the PogoOS or Debian from my USB stick so I must have done something wrong. I have a serial port and the console shows a string of the following error message get_fl_mem: unknown device type; using raw offset! (this one repeats a bunchby unmesh - uBoot