Two years later, and another Debian release. After updating my NFS server to Debian Bookworm (Debian 12), I noticed my dockstars wouldn't boot up anymore from nfs. A quick lookup with Wireshark gave this network trace: No. Time L3Proto Source SrcPort Destination DstPort Protocol Len Info 3 0.177599 UDP 0.0.0.0 68 255.255.255.255by tsunulukai - uBoot
Hi Bodhi, I run a custom de-bootstrapped Debian where the the DTB is not appended to the kernel file but loaded separately. Replacing Debian's native DTB with yours in my /boot/dts/kirkwood-dockstar.dtb did the trick ! Many thanks for your (as always) helpful insight ! Happy New Year !by tsunulukai - Debian
Hello there. I must be blind, it's probably right in front of my eyes, but I can't figure it out... # fw_setenv test test Can't open /dev/mtd0: Permission denied Error: can't write fw_env to flash # uname -a Linux dockstar-multimedia 5.10.0-8-marvell #1 Debian 5.10.46-3 (2021-07-28) armv5tel GNU/Linux # cat /proc/cmdline console=ttyS0,115200 root=/dev/nfs rwby tsunulukai - Debian
Hi there ! Just updated to Debian Bullseye on my dockstar. The update process seemed to go nice and well, until the moment came to reboot: It wouln't boot anymore in NFS. Hooking up a cable on the serial header, I could see it was stuck during the boot process trying to mount the NFS root mount without success: Begin: Retrying nfs mount ... mount: Invalid argument done. Begin: Rby tsunulukai - uBoot
Bodhi, Exactly what I answered on the debian mailing list : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933971#15 It is indeed the same bug and the proposed workaround works fine. Still, I think that the choice of compiling the corresponding driver as a module instead of embedding it in the kernel is a decision that will impact many users when they upgrade their plug device froby tsunulukai - uBoot
Ref: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931852 The mtdparts definition syntax differs when the corresponding driver is loaded as a module instead of being directly embedded in the kernel. When updating to buster with the debian vanilla kernel, the corresponding is not embedded in the kernel anymore, but loaded as a module. As a consequence you must update your uboot mtdparts varby tsunulukai - uBoot
Tried it already, doesn't change a thing. Rebuilding the initramsfs after changing the /etc/modules file to ensure the modules are loaded as early as possible didn't help either: # cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "by tsunulukai - uBoot
@1000001101000, nope, no luck... :( The cmdlinepart module is already loaded by default without being specified in /etc/modules.... # lsmod | grep mtd mtd 44525 9 nand_bch,ofpart,nand,cmdlinepart,orion_nand # cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot timby tsunulukai - uBoot
@1000001101000: I'm using Debian vanilla kernel AND DTB files in both the Squeeze and Buster distro I used while performing the tests to isolate the issue. @bodhi: I was not using your DTB files with the debian Kernels The DTB file provided by the Debian package are located in /usr/lib/linux-image-${LINUXVER}/kirkwood-dockstar.dtb or /usr/lib/linux-image-${LINUXVER}/kirkwood-goflby tsunulukai - uBoot
Bodhi, just as a confirmation that it's a kernel issue, I upgraded my Buster image with your kernel package (https://forum.doozan.com/read.php?2,12096) and, sure enough, the problem is then solved... Still, I'd like to figure out a way to have it work with the mainline debian kernel because I don't want to loose automatic security updates for it... I tried using the busterby tsunulukai - uBoot
*** SOLVED *** --> See https://forum.doozan.com/read.php?3,87849,87959#msg-87959 The mtdparts definition syntax differs when the corresponding driver is loaded as a module instead of being directly embedded in the kernel. When updating to buster with the debian vanilla kernel, the corresponding is not embedded in the kernel anymore, but loaded as a module. As a consequence you must update yby tsunulukai - uBoot
When upgrading to Debian Buster, the initrd is ~2Mb bigger than for Stretch: -rw-r--r-- 1 root root 15163991 2019-07-25 14:04 initrd.img-4.19.0-5-marvell (Buster) -rw-r--r-- 1 root root 13500968 2019-07-25 10:28 initrd.img-4.9.0-8-marvell (Stretch) So you might need to update the load_dtb_addr again to avoid any issue at nfs boot time. Minimum value is 0x02000000. setenv loby tsunulukai - uBoot
Hi there ! Just a small update in case anyone encouters the same issue as I have... After a kernel update on my Dockstar, I couldn't boot anymore by NFS... There seemed to be an issue with my initramfs... ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-4.9.0-8-marvell Created: 2018-11-26 18:33:47 UTC Image Type: ARM Linux Kernel Image (uncby tsunulukai - uBoot
Hello there ! I finally updated my Dockstars to uBoot 2017-07 by bodhi, so I thought I might as well provide you with the updated procedure to NFS boot. It concerns the section #7 of my initial guide, which should be replaced with the following after having update to the latest uBoot and reset the uboot environment to uboot.2016.05-tld-1.environment.bodhi.tar. This update also only relies on Nby tsunulukai - uBoot
Hi there ! First of all, many thanks for your positive feedback :) Just a quick update for those of you who run debian as their NFS server to boot their dockstar. When updating to Debian 9 Stretch, the nfs-kernel-server packages disables NFSv2 by default. This broke my NFS setup with the dockstars, which, although configured to use NFSv3, seems to initialize their boot using NFSv2. (It mighby tsunulukai - uBoot
Thanks for you input ! I guess it would not be very handy to retrieve the state of the a button at regular intervals... with all the clocking issues it would imply to retrieve correcly all the keypresses live... Would it not be better if the DPF would store the numer of keypresses for each buttons in registers that would then be read by the dpflib/dpfcore4driver ? The driver could reset theby tsunulukai - Displays
Do you think it would be possible to alter the DPF firmware to return information about the state of those buttons ? From my understanding, the left/right arrows are not triggering anything while outside the dpf menu. It could therefore be usefull to allow their use for interacting with the host. Greetz,by tsunulukai - Displays
Hi folks, I've been playing a little with LCD4Linux and MPD and was disappointed to see the date, track number or disc of a song couldn't be extracted with the last official revision of the plugin. I've patched it to add this possibility. Here's the diff for anyone wishing to add this functionnality too: --- plugin_mpd.c 2011-07-27 02:53:04.000000000 +0000by tsunulukai - Displays
Hi ! It's been quite a long time since I had last played with those nice little displays. The new firmware for the DPF rocks and embedded support from the last revision of lcd4linux is a real breeze, thanks ! While looking at the source of the lcd4linux plugin for MPD, I noticed there are functions available to control the volume or change track from lcd4linux. Is there a way to maby tsunulukai - Displays
Hi ! The file gpxelinux.0 is NOT necessary here. It only appears in my output because I have network boot enabled on my network for x86/64 computers. As the Dockstar initiates its DHCP request during the boot sequence, it also receives from my DHCP server the boot server and file (DHCP options 66 & 67) for x86/64 machines, and tries, unsuccessfully, to boot from it.... which is useless forby tsunulukai - uBoot
Hi there! A few month ago, I was trying to boot my dockstar by TFTP & NFS... but did not succeed. I've left my dockstar on the side for a time, and I recently tried again successfully ! My deep gratitude to this fellow community who made it all possible by their numerous contributions ! Here's my modest contribution... I tried this with a newly-installed debian wheezy dby tsunulukai - uBoot
Yes, it does.by tsunulukai - Debian
Then you have to enter one of the following commands before "bootm" : setenv arcNumber 2097 setenv arcNumber 2998 setenv arcNumber 3089 Those 3 arc numbers are respectively the "Generic Pogoplug ID", which doesn't support the dockstar led, the "Dockstar ID" and the "Goflex Net ID". The last two only works with newer kernels that now have suppoby tsunulukai - Rescue System
To start this rescue system from a tftp server, here are the commands to execute from uboot, assuming your tftp server is hosting both uinitrd & uImage and is accessible @192.168.1.1 setenv ipaddr 192.168.1.50 setenv netmask 255.255.255.0 setenv serverip 192.168.1.1 tftp 0x800000 uImage-rescue tftp 0xe00000 uInitrd-rescue setenv bootargs console=$console $mtdparts bootm 0x800000by tsunulukai - Rescue System
After searching a bit for compiling myself the udlfb kernel driver (Display Link devices), I realized that I was missing the kernel headers for the kernel I had compiled. It could be useful to add in your tutorial on the first post that one can add "kernel_headers" to the make-kpkg command to build a package containing the kernel headers, required to compile external kernel drivers..by tsunulukai - Debian
Hello everyone, First of all, I'd like to thank you for the wonderful information provided here ! I made the acquisition of a USB DisplayLink adapter like this one I had Jeff's 2.6.32-5-kirkwood kernel installed. When I plugged the adapter, I directly got the famous green screen showing off that the display adapter was correctly detected. I installed the xorg video server aby tsunulukai - Debian