Thanks! It worked :-) - now I can use the dockstar(s) for another decade... best, lcgby lcg - Debian
Thanks again bodhi, worked pretty well :-) and booted into the rootfs. However, for the rescue system, using the previous variables does not work and the rescue system does not boot: # nc -lu 6666 U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700) Seagate FreeAgent DockStar gcc (Debian 6.3.0-18) 6.3.0 20170516 GNU ld (GNU Binutils for Debian) 2.28 Hit any key to stop autoboot: 0 sby lcg - Debian
Thanks bodhi, so I will prepare a new rootfs to match the new handling of the DTB file, try the reboot, and add the rescue variables. Thanks for pointing out the proper package for the utilities. best, lcgby lcg - Debian
Dear bodhi, I am in the same position (ie. Dockstar) and followed the steps in the uboot-tutorial and compared the output to this thread. Flashing etc. seemed to work fine (no reboot yet), my new uboot envs looks like: # fw_printenv 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_uimagby lcg - Debian
...ok I found out reading old German postings that it is "usb0" if the display is in developer mode and not a sgX device or anything like that. Maybe this can be added to the readme, that an already hacked display can be accessed via usb0. Then, flashing the new firmware was straightforward. What does not work is flashing a splashscreen: ./setsplash.sh ./newpicture_320x240.jpg 320by lcg - Displays
bodhi Wrote: ------------------------------------------------------- thanks bodhi... so I will check first whether the kernel module is present or where to get the sources for it. I was a little bit surprised about the fact that bilibop did not show *any* error or log-entry, maybe I misconfigured it. It should be exactly such an overlayfs implementation as you pointed it out. However, I trby lcg - Debian
Dear all, I wanted to update the hackfin firmware (flashed some years ago). However,I find no option for "usb connect". The display is recognized under Linux as well as Windows but without assigning a driver/letter: Jul 17 10:39:20 karuna kernel: [14710.879019] usb 1-1.2: new full-speed USB device number 13 using ehci-pci Jul 17 10:39:21 karuna kernel: [14711.008597] usb 1-1.2:by lcg - Displays
bodhi Wrote: ------------------------------------------------------- > No, IIRC, you dont need to change u-boot envs or b > ootcmd. Look for overlayfs as keyword. thanks, overlayfs is not available as a package, but a package called bilibop: # dpkg -l|fgrep bilibop ii bilibop-common 0.4.23 armel shell functions for bilibop sby lcg - Debian
Dear all, has anybody successfully installed a Debian system (>jessie) with read-only rootfilesystem (on USB stick)? I read guides on how to do that on non-ARM platforms. What are the steps in detail? - new kernel necessary? or build at least a kernel-module? - install overlayroot package and configure it with "tmpfs" like: apt-get install overlayroot echo 'overlayrby lcg - Debian
Thanks - I managed to get it working: In another thread on http://forum.doozan.com/read.php?2,26114 I found # ln -s /usr/src/linux-headers-4.4.0-kirkwood-tld-1/ /lib/modules/4.4.0-kirkwood-tld-1/build ie. it is not sufficient to just create the directory. Then take from http://www.realtek.com.tw/Downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=56&Level=5&Conn=4&Doby lcg - Debian
...yes yes that's clear, but kernel-headers are installed. So what is missing? LCG renojim Wrote: ------------------------------------------------------- > I can't really tell you what you need, but the > error message is telling you that the > '/lib/modules/4.4.0-kirkwood-tld-1/build' > directory doesn't exist. > > -JTby lcg - Debian
Dear all, can someone be so kind to enlighten me what I need to build kernel modules? I use the jessie rootfs along with # uname -r 4.4.0-kirkwood-tld-1 and I need a realtek r8153 kernel module (actually it is a r8152) for a usb-to-ethernet adapter which is recognized but the kernel module is missing. # lsusb Bus 001 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. ... [by lcg - Debian
Thanks Bodhi, worked with systemd out-of-the-box. best, leoby lcg - uBoot
Dear all, I use a Dockstar with U-Boot 2011.12 (Feb 12 2012) and want to try out the latest rootfs for jessie along with systemd instead of sysv. In another thread of Bodhi (http://forum.doozan.com/read.php?2,12096) it was pointed out to add 'init=/bin/systemd' to 'usb_set_bootargs'. Before writing this permanently to NAND, it is safe to - use netconsole to stop thby lcg - uBoot
Dear all, context: PEARL Display at Dockstar on Debian Wheezy I have problems with udev while connecting the PEARL display to a dockstar. The problem is not lcd4linux, that works and the display is immediately in hack-mode after connecting via usb. So a "/usr/local/bin/lcd4linux" on the commandline works out of the box. The 70-dpf.rules in /etc/udev/rules.d that was written shoby lcg - Displays
@Bodhi - thanks, worked out of the box. I chose option 2 and deleted the old entry (eth0) and renamed the new eth1 to eth0. Good to know that udev "remembers" hardware.by lcg - Debian
Dear all, it does not seem possible to use a working rootfs from one dockstar on another (rootfs is Debian Wheezy installed by Jeff's script). However, on the second dockstar it is possible to install Debian via the script too, so it is not a problem of the Dockstar or installing Debian per se. But just copying the rootfs to another stick (or using the same stick on another dockstar) doesby lcg - Debian
@E41 It is still true that RescueV2 cannot be installed from RescueV3 (USB). The script complains about a "not up to date uboot". If one ignores that, the NAND is flashed without any error message, but after reboot it does not start. At the same time the original uboot install script clearly states that the uboot is "up to date". So it is probably not an issue of uboot. Howby lcg - Rescue System
@bodhi - pretty cool. Yes, that worked for Squeeze as well as for Wheezy. Thanks! Is the correct explanation the read-only part or did the 'uboot reset' more?by lcg - Debian
Thanks, after enabling netconsole and struggling with nc netconsole works very well (concretely: using 'nc -klup 6666 &' and 'socat STDIO UDP-SENDTO:192.168.1.14:6666', everything else failed). I don't want to do double-postings, so if anyone can help me to get Wheezy or Squeeze to work/ boot, please answer here: http://forum.doozan.com/read.php?2,9256,10757#msg-10757by lcg - uBoot
ok, arcNumber changed, but no success - boot hangs, here fw_printenv: rescue:~# fw_printenv ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) mtdids=nand0=orion_nand partition=nand0,2 stdin=serial stdout=seriaby lcg - Debian
ARJunior Wrote: ------------------------------------------------------- > Don't you forget to change arcNumber to 2998 ? Thanks for the hint. After checking with RescueV2 -> arcNumber=2097. One question before applying a new arcNumber: - Why does RescueV2/ RescueV3 (USB) boot without any problem but neither squeeze or wheezy? -> Update: netconsole works now while using tby lcg - Debian
Dear all, after following this and other threads - and struggling for days now - the wheezy install-script did not report any errors, but does not boot afterwards. What I did: - fresh dockstar - installed latest uboot via uboot script (Jeff) - installed RescueV2 from debian embed-install (i.e. Jeffs NAND Debian on USB http://forum.doozan.com/read.php?2,72, it was not possible to install tby lcg - Debian
Hello, is it possible and safe to enable netconsole directly after installing uboot BUT BEFORE doing a reboot? Problem is that (see thread under "Debian" but unfortunately unanswered, maybe my question was seen as too easy) the Debian Wheezy install script from Jeff failed with "kernel too old" error AFTER uboot was already installed by the script. I used a clean new Dockstby lcg - uBoot
Dear all, the install script for Debian Wheezy (http://projects.doozan.com/debian/) fails with: --- I: Extracting zlib1g... W: Failure trying to run: chroot /tmp/debian mount -t proc proc /proc W: See /tmp/debian/debootstrap/debootstrap.log for details debootstrap failed. See /tmp/debian/debootstrap/debootstrap.log for more information. --- It is a brand-new dockstar, nothing changby lcg - Debian