pld, > But, I did test the ArchLinux. Both, marvell_cesa > and crypotodev load cleanly and marvell_cesa shows > in /proc/crypto. Kernel version 4.4.1-1-ARCH. > Maybe we should steal some patches from there? Sure, can you extract the patches? I'll take a look.by bodhi - Debian
@All, There are a few things need to be fixed in the mainline kernel 4.4 DTS. I've fixed most and will post a new DTB later today. - Power off (try to do shutdown and watch serial console) - No LED control (also is there other LED besides the power button?). - Also WOL does not work yet. I'm not sure if DTS is a culprit. Other non-DTS-related issue: I can't chainload bby bodhi - Debian
Thanks for sharing pld! There is a 3rd method, which I like the most: using the esekeyd. It's cleaner, and out of the box from Debian. My NSA325 config for testing (the NSA310S has similar config). cat /etc/esekeyd.conf #POWER:/sbin/shutdown -h now #RESTART:/sbin/shutdown -r now POWER:/usr/bin/logger -s -i "POWER button pushed" RESTART:/usr/bin/logger -s -i "RESby bodhi - Debian
sLOID, For now use the kwboot to set the clock. I wonder if stock u-boot has any command to set RTC. Did we get the commands available in serial console? help I promise :) I will come back to this when I have time to look at the code to set up flash properly. We need to do that to write new u-boot to SPI flash.by bodhi - Debian
bobafetthotmail, > I finally got the cables. I see the party isn't > over yet, can I come in? :) welcome to the party. It's not late, as there are many things we have not figured out yet. > > It seems these boxes try to use WoL and/or some > kind of auto-resume from powerloss and they do so > in a way that prevents kwboot. Shutting them down > by pullby bodhi - Debian
To set the mtdparts and envs location so that Debian recognizes the correct layout. In Debian rootfs cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors # HP T5325 Thin Client /dev/mtd2 0x00000 0x10000 0x10000 And then adjust the u-boot envs for it. 1. If booting with stock u-boot In serial console setenv bootargs_usb 'cby bodhi - Debian
sLOID, I wonder if the box battery is dead.by bodhi - Debian
Thanks Gravelrash, I will try the recovery when I got home today. I want to make sure that the stock OS can be used as a rescue system. Otherwise we will need to use part or whole of that 512MB and install a new one.by bodhi - Debian
sLOID, > it's so frustrating. hope you have just another > few things to try out to get it working. and yes, > i would like to flash your uboot version and would > like to know how. Did you do SNTP and got the clock corrected back? Let me see if this u-boot build is good enough. There are a few more things to work on. As you can see the envs are not working properly.by bodhi - Debian
I have this recovery disk extracted: HPTC Imgr.tar.gz ./boot: . .. uImage.dove.usb uImage.usb uInitrd.dove.usb uInitrd.usb ./images: . .. ThinPro-T5A32014-2016-01-28.dd.gz ./uboot: . .. u-boot-3.4.19_V16.bin .: . .. boot images init.sh settings.ini uboot ./boot: . .. uImage.dove.usb uImage.usb uInitrd.dove.usb uInitrd.usb ./images: . .. ThinPro-by bodhi - Debian
It's a box from an East Coast USA eBay seller. It has the header installed (looks like manufactered). I believe has been modded or the OS damaged because I could not boot into the stock OS. I connected 3 wires, just barely enough for serial console :). The microJST headers will also arrive soon in a few days (eBay seller but shipping is from SanFrancisco US, only cost a buck more than shippiby bodhi - Debian
./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-2-rc2.t5325.mtd0.kwb -p Sending boot message. Please reboot the target.../ Sending boot image... 0 % [......................................................................] 2 % [......................................................................] ....] 95 % [................................................................by bodhi - Debian
Here is a rc2 test version. Please try with kwboot. ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-2-rc2.t5325.mtd0.kwb -p Interrupt serial console after u-boot was loaded. And Check out USB and SATA usb start ide reset Setup for booting Debian USB rootfs setenv usb_root 'LABEL=rootfs' setenv rootfstype ext3 And bootby bodhi - Debian
The DTS GPIO Power off looks suspect. That's why I wonder if it would cause problem.by bodhi - Debian
@ flyyboyy At this point you have 3 steps to try. If one fails try the next. 1. Try to get back in with SSH. 2. Prepare the Debian 3.16 rootfs on USB and reboot with it. 3. Connect serial console. If you decide on serial console then do that and not worrying about 1 or 2.by bodhi - uBoot
Micky Wicky, When I have time, I will build another version to try so we don't have to do the poke.by bodhi - uBoot
flyyboyy, > You indicate that I was following an old procedure > to install ALARM. It's kinda funny, because in > preparing to do it, I came across and studied MANY > sites/pages that all follow pretty much the same > procedure, using the same file downloads, and all > from about the same time (2014 or so). I assumed > that these were still valid since I had notby bodhi - uBoot
Another test with stock u-boot and new Debian. - boot the box into Debian. - Watch the serial console. And shutdown: shutdown -h now or poweroff Did it shutdown cleanly?by bodhi - Debian
pld, > True. If I'm not wrong then, in case of separate > images, you still need to upgrade uInitrd. True, either cases will need to regenerate something.by bodhi - Debian
All, I am still a little bit unsure about the SATA/USB issue. The stock u-boot GPL is a mess to read. But it should be clear up soon that later today I will pick up my T5325 :) and that will help me solve the last puzzle about USB/SATA.by bodhi - Debian
@CV, > Saving Environment to SPI Flash... > SF: Detected M25P80 with page size 256 Bytes, > erase size 64 KiB, total 1 MiB > Erasing SPI flash...Writing to SPI flash...done > You are an adventurous person :) this could potentially mess up your u-boot envs. Since you have serial console and can kwboot, it's can be fixed if need be. Tryby bodhi - Debian
To restore the default envs as it were flashed to NAND initially. I've created a script for this purpose. 1 .Download the attached script: uboot.2014.07-tld-3.environment.scr. 2. Copy it to the USB Debian rootfs /boot folder. 3. Plug in the USB Debian rootfs to the GFHome, power up, interrupt serial console and then execute these commands: usb start ext2load usb 0:1 0x80000by bodhi - uBoot
> definitely the hardware (Prolific clone). The > result is consistent with the x64 system when > using it on an orangepi Could be the hardware. I always have 2 serial converters, one Sililconlabs CP2xxx and one Prolific PL3xxx. When in doubt, I would swap the converter to make sure I'm not screwed by a $3 board :) And I really like the Nokia cable (Prolific) with the plastic sby bodhi - Debian
hachigo, > Oh ok. Before I was able to ssh into it and also > use the netconsole, but now I can't. I guess now I > can only get into the stock OS with serial cable? > Not true. It only means that your setup has some errors. Check the error about ethaddr above at the end of your log. If the installation in the 1st post was OK, then you can ssh into Pogo OS. Again, thatby bodhi - Rescue System
Gravelrash, > root@orangepi:/scripts# ./kw > Sending boot message. Please reboot the > target...\^Z > [1]+ Stopped ./kw > root@orangepi:/scripts# ./kw > > I've just noticed this. How come you have a Control-Z above? was that entered by you after waiting a while and saw nothing?by bodhi - Debian
hachigo, > I was wondering if there was a Rescue System like > Rescue v.2.8.2 for the pro. My pogo pro doesn't > boot into the stock pogo OS anymore. Is there a > replacement that has more features than the stock > I could just flash over? Thanks again. It did. That was the purpose of this thread. You see a lot of errors during boot, but it did not prevent the stockby bodhi - Rescue System
hachigo, > What does " ## Error: "dt_bootcmd_usb" not > defined" mean? I'm not sure what I'm doing wrong. > Also I didn't mean to steal the thread. Should I > post in another post? Ah! I see, I've missed that :). This is what was wrong. In serial console: setenv bootcmd 'run scan_disk; run set_bootargs; run bootcmd_exec; rby bodhi - Rescue System
Gravelrash, It is in the first post of the u-boot thread: http://forum.doozan.com/read.php?3,12381 Quote======================================================= Last Updated 13 Nov 2015 I've uploaded 2015.10-tld-1 U-Boot images for Pogo E02, GoFlexNet, GoFlex Home, Dockstar, Pogo V4/Mobile, iConnect, Netgear Stora, Sheevaplug, NSA320, NSA325, NSA310S/320S (same image), and NSA31by bodhi - Debian
hachigo, The envs look fine. You can create the 3.17 Debian rootfs without changing anything (just tar it). Follow the instruction (extract it to a single partition type Ext3, as root user, and label it rootfs). That's it, no further change (don't embed the DTB).by bodhi - Rescue System