Show all posts by user
Discuss all things Debian on your device
Page 1 of 2 Pages: 12
Results 1 — 30 of 54
Re: Upgrading Debian Distribution - 1 year ago
Okay I will checked it in the evening.by droidbox - Debian
Re: Upgrading Debian Distribution - 1 year ago
bodhi Wrote: ------------------------------------------------------- > > e. Usually a distribution upgrade like this > would result in a new initramfs. So regenerate the > uInitrd boot file. See section 4 in my > kernel/rootfs installation for how to recreate > uInitrd. It should look like this example: > > cd /boot > mkimage -A arm -O linux -T ramdisk -C gby droidbox - Debian
Re: Upgrading Debian Distribution - 1 year ago
bodhi Wrote: ------------------------------------------------------- > > cd /boot > ls -lart > root@pogoplug-dev:/boot# ls -lart total 64124 -rwxr-xr-x 1 root root 5435824 Aug 1 2021 vmlinuz-5.13.6-kirkwood-tld-1 -rw-r--r-- 1 root root 183927 Aug 1 2021 config-5.13.6-kirkwood-tld-1 -rw-r--r-- 1 root root 4403336 Aug 1 2021 System.map-5.13.6-kirkwood-tld-1by droidbox - Debian
Re: Upgrading Debian Distribution - 1 year ago
No, that does not seem to be my problem, since everything is correct with me. root@pogoplug-dev:~# ls -la / total 64 drwxr-xr-x 18 root root 4096 May 2 12:10 . drwxr-xr-x 18 root root 4096 May 2 12:10 .. lrwxrwxrwx 1 root root 7 May 2 12:10 bin -> usr/bin drwxr-xr-x 3 root root 4096 May 13 23:01 boot drwxr-xr-x 13 root root 2900 Jan 1 1970 dev drwxr-xr-x 76 roby droidbox - Debian
Re: Upgrading Debian Distribution - 1 year ago
It looks fine :-( root@pogoplug-dev:~# dpkg -l | grep udev ii libudev0:armel 200-1 armel compatibility wrapper for libudev version 0 ii libudev1:armel 252.6-1 armel libudev shared library ii udev 252.6-1 armel /dev/ and hotpby droidbox - Debian
Re: Upgrading Debian Distribution - 1 year ago
Hmmm. trd load_initrd_addr=0x1100000 load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage load_uimage_addr=0x800000 machid=0x831 mainlineLinux=yes mtdids=nand0=orion_nand mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) partition=nand0,2 preboot_nc=run if_netconsole start_netconsole scan_disk=echo running scan_disk ...; scaby droidbox - Debian
Re: Upgrading Debian Distribution - 1 year ago
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700) 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 PogoE02> printenv arcNumber=2097 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec bootcmd_exec=run load_uimage;by droidbox - Debian
Re: Upgrading Debian Distribution - 1 year ago
bodhi Wrote: ------------------------------------------------------- > > > > Please post the entire serial boot log. > > I might be able to see why if you post the log. sorry bodhi, but where can i find the serial log?by droidbox - Debian
Re: Upgrading Debian Distribution - 1 year ago
bodhi Wrote: ------------------------------------------------------- > There is something odd here: > > > [ 27.290781] random: crng init done > [ 147.297641] EXT4-fs (sda1): re-mounted. Opts: > (null). Quota mode: none. > > > That rootfs should not have been re-mounted. > Should be just mounted. > But how can I prevent this?by droidbox - Debian
Re: Upgrading Debian Distribution - 1 year ago
PogoE02> printenv arcNumber=2097 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec 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_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addrby droidbox - Debian
Re: Upgrading Debian Distribution - 1 year ago
root@pogoplug-dev:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.13.6-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1.0 PREEMPT Sat Jul 31 22:10:39 PDT 2021 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instructionby droidbox - Debian
Re: Upgrading Debian Distribution - 1 year ago
Hey, today I have upgrade my pogoplug from bullseye to bookworm, everything looks good so far. However, after a new start of the pogoplug, the startup takes very long, many times longer than under bullseye. After a short analysis I noticed that it is probably due to UDEV. Does anyone have a solution, how I get the start faster again? Thanks a lot. Starting hotplug events dispatcherby droidbox - Debian
Re: BootLoop after fresh install on Pogoplug E02 - 1 year ago
Machine is back in life. Thanks for your help.by droidbox - Debian
Re: BootLoop after fresh install on Pogoplug E02 - 1 year ago
Okay, one step more bootm 0x800000 0x2100000 but Loading, please wait... Starting version 247.3-6 [ 13.685807][ T7] scsi 0:0:0:0: Direct-Access SanDisk Cruzer Fit 1.26 PQ: 0 ANSI: 5 [ 13.713615][ T58] sd 0:0:0:0: 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB) [ 13.740484][ T58] sd 0:0:0:0: Write Protect is off [ 13.754730][ T58] sd 0:0:0:0: Write cby droidbox - Debian
Re: BootLoop after fresh install on Pogoplug E02 - 1 year ago
Okay, the tftp runs fine CE>> tftpboot 0x800000 uImage Using egiga0 device TFTP from server 10.10.172.223; our IP address is 10.10.172.10 Filename 'uImage'. Load address: 0x800000 Loading: ################################################################# ################################################################# ##################################by droidbox - Debian
Re: BootLoop after fresh install on Pogoplug E02 - 1 year ago
Oh shit, this is right. CE>> usb Unknown command 'usb' - try 'help' And now? Brick for ever ;-)by droidbox - Debian
BootLoop after fresh install on Pogoplug E02 - 1 year ago
Hello, I got a new pogoplug. Installed after "Basic Debian bullseye Kirkwood rootfs for most Kirwood plugs / Updated 26 Sept 2021" and created uImage after "Stock u-boot only". Now it unfortunately sticks after boot. U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16) U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00690D60 Soc: 88F6281 A0 (DDR2) Cby droidbox - Debian
Re: Dockstar Please check your kernel config and/or bootloader. - 2 years ago
I will give this howto next week a change https://forum.doozan.com/read.php?3,21789 I reported here ;-)by droidbox - Debian
Re: Dockstar Please check your kernel config and/or bootloader. - 2 years ago
I have this one found in my garage https://www.amazon.de/Paradisetronic-com-Programmierger%C3%A4t-ISP-Adapter-Programmer-Arduino/dp/B07Y3B8H91by droidbox - Debian
Re: Dockstar Please check your kernel config and/or bootloader. - 2 years ago
I have made this commands all, but now no LEDs blinking :( What is a jtag recovery?by droidbox - Debian
Re: Dockstar Please check your kernel config and/or bootloader. - 2 years ago
Hey. I have entered the commands. Unfortunately, it still gets stuck in a kernel error. Then I copied the "u-boot.kwb" to the USB stick and entered the following commands: DockStar> fatload usb 0:1 0x0800000 u-boot.kwb DockStar> nand erase 0x0 0x80000 DockStar> nand write 0x0800000 0x0 0x80000 DockStar> reset Now, unfortunately, nothing happens, and no LED flby droidbox - Debian
Re: Dockstar Please check your kernel config and/or bootloader. - 2 years ago
If you read my last command, I install a fresh usb stick with a new "Linux Kernel 5.15.5 Kirkwood package and Debian rootfs". I look on the stick and the /boot/dts/kirkwood-dockstar.dtb is present.by droidbox - Debian
Re: Dockstar Please check your kernel config and/or bootloader. - 2 years ago
Hi bodi. This morming, a collegue ou me bring me his bricked dockstar. I install a fresh USB stick with "Linux Kernel 5.15.5 Kirkwood package and Debian rootfs" and put it in the dockstar. It comes the same error as above Uncompressing Linux... done, booting the kernel. Error: invalid dtb and unrecognized/unsupported machine ID r1=0x00000bb6, r2=0x00000100 r2[]=05 00 00by droidbox - Debian
Re: Dockstar Please check your kernel config and/or bootloader. - 2 years ago
For me, booting ist faster and and the rootfs is only 200MBby droidbox - Debian
Re: Dockstar Please check your kernel config and/or bootloader. - 2 years ago
Hi bodhi. I have find an old dockstar on ebay for anly 5€. When I get the dockstar I will write a tutorial on how to get an Alpine installed.by droidbox - Debian
Re: Dockstar Please check your kernel config and/or bootloader. - 2 years ago
u-bootU-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700) uname -a Linux dockstar 5.13.6-kirkwood-tld-1 #1.0 PREEMPT Sat Jul 31 22:10:39 PDT 2021 armv5tel Linux cat /etc/os-release NAME="Alpine Linux" ID=alpine VERSION_ID=3.11.2 PRETTY_NAME="Alpine Linux v3.11" HOME_URL="https://alpinelinux.org/" BUG_REPORT_URL="https://bugs.alpinelinux.org/"by droidbox - Debian
Re: Dockstar Please check your kernel config and/or bootloader. - 2 years ago
Thank you very much. It rocks now perfect for me, with Alpine Linux on the dockstar. droidboxby droidbox - Debian
Re: Dockstar Please check your kernel config and/or bootloader. - 2 years ago
bodhi, it rocks perfect. Now I can boot into the Alpine Linux. Great. One more question ;-) How can I disable this message at the boot? 1 Storage Device(s) found Unknown command 'ide' - try 'help' Unknown command 'mmc' - try 'help' Partition Map for USB device 0 -- Partition Type: DOS Part Start Sector Num Sectors UUIDby droidbox - Debian
Re: Dockstar Please check your kernel config and/or bootloader. - 2 years ago
Hi bodi. Your tips above, I have already tried, but made no difference. Then I found the following while searching. After that, the system boots properly. But after a reboot it does not work again. run bootcmd_uenv DockStar> run bootcmd_uenv starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... Useby droidbox - Debian
Page 1 of 2 Pages: 12