I have fixed this network problem in u-boot proper and released a new version U-Boot-2017.07-tld-1: https://forum.doozan.com/read.php?3,26562 The link speed 100Mbs is now set during u-boot booting. So we don't need to rely on Linux kernel to renegotiate the link.by bodhi - Debian
I've uploaded the HP Thin Client T5325 U-Boot-2017.07-tld-1. Please see 1st post for download link and installation instruction. The network problem in u-boot has been fixed in this release. The latest installation instruction has been revised to have 2 sections: A. Installation from stock OS B. Installation from the latest Debian rootfsby bodhi - uBoot
huge Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > huge, > > > > You have serial console, so there is no need to > > set up netconsole now. You can always wait > until > > after the system has been up and running well. > > > > Quote10. Set uby bodhi - uBoot
> Lastly and unrelated, can someone definitively > settle the question of whether, with a CP210x > adapter, you should connect RX->RX & TX->TX or > swap/cross them? I first heard they should be > swapped, then learned that with a CP210x they > should NOT be swapped, and then I've seen > conflicting claims. The most convincing > statements indicate Nby bodhi - Off-Topic
vertycall, > -sh-3.2# [ 18.790000] XCE: BLPARAMS: reading Right here. You are in stock OS. Try typing something here to see if serial console input is working. You can also do a quick loop back test to check your serial converter: disconnect the serial wire going to your GFNet, and connect your serial converter TX to RX, and type something to see if it echos back.by bodhi - uBoot
huge, You have serial console, so there is no need to set up netconsole now. You can always wait until after the system has been up and running well. Quote10. Set up netconsole. It's important to set up neconsole if you don't already have serial console connected. If you've flashed the default environments in step 8 then activate netconsole with the following envs:by bodhi - uBoot
stef34280 Wrote: ------------------------------------------------------- > Hi Bodhi, > > I went route n°2 and now everyhing is fine ! > > I thank you very much for your valuable help ! > > If I can do something for you one day, just ask, I > will ! Cool :)by bodhi - Debian
vertycall, 1. With serial console connected, when you let it boot all the way, do you see the stock OS login prompt? if yes, what happen when you try to enter "root" at the login prompt? Can you login? 2. If you can login or enter something at the stock login prompt, then your stock u-boot envs probably has something wrong in it that disabled the serial consol input. 3. If youby bodhi - uBoot
huge Wrote: ------------------------------------------------------- Quote> I'll list the steps as you have them numbered > under "Flashing Instruction"... > > 1. uBoot envs config and mtd partitions must be > defined as followed in your rootfs > > > cat /etc/fw_env.config > > # cat /etc/fw_env.config > /dev/mtd0 0x00100000 0x20000by bodhi - uBoot
The correct command to regenerate uImage is mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n Linux-4.4.54-oxnas-tld-1 -d vmlinuz-4.4.54-oxnas-tld-1 uImage Note: I forgot to revise the instruction for this OXNAS rootfs, step 4 should have included the command to save the original uImage: cd /media/sdb1/boot cp -a uImage uImage.orig cp -a zImage-4.4.54-oxnasby bodhi - uBoot
stef34280, Quote> Please post the log of your execution of step 6 > and 7 for review, before doing step 8. > > I understood from that to do all the steps from 1 > to 7 before rebooting so I did not made step 8 > (flashing default envs) You've misunderstood this. Step 8 must be done. Quote> The box boots fine but the envs seem messed. Because the defaulby bodhi - Debian
Quote- ------------------------------------------------------------------------- Debian Security Advisory DSA-4018-1 security@debian.org https://www.debian.org/security/ Salvatore Bonaccorso November 04, 2017 https://www.debian.org/security/faq - ------------------------------------------------------------------------- Packageby bodhi - Debian
huge, > # cat /proc/mtd > dev: size erasesize name > mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit" > mtd1: 00e00000 00020000 "boot" > mtd2: 07200000 00020000 "rootfs" This is stock mtds definition. It is basically the same layout. However, when you flash u-boot, you will need to use mtd1. The flashing instruction is written with mtdby bodhi - uBoot
Mike Wrote: ------------------------------------------------------- > A question, if I might, about the Uboot > requirements... > Can it be loaded in a stock Pogo-21 without > Ssh enabled. Without SSH enabled, the only way to flash new u-boot is to connect serial console.by bodhi - Debian
Stephen P Wrote: > The network lights work fine when u-boot is active > - they go out partway through the kernel init > process. That's interesting! meaning the kernel has reset the LEDs while it was already correct. This is going to be hairy! usually need some setting for some register values, which I don't have any info for the NSA310. But that might be found by readby bodhi - uBoot
Stephen P, > Why do I feel stupid? I could not get the other > LEDs to light up. This may have something to do > with the fact THERE ARE NO OTHER LEDS. The unit is > very deceptive; inside the case it has space for > five LEDS. The manual shows five LEDS. However, if > you look very, very closely at the front fascia, > there are actually only two symbols. Duh! :)by bodhi - uBoot
> Success, thank you! Actually that exact command > got me an error message, but that led me to a post > (from you, of course) telling another noob that > there were actually (at least) two > netconsole/netcat programs, which led me to the > magic combo that seems to work for me: > > nc.traditional -l -u -p 6666 & > nc.traditional -u -p 6666 192.168.222.1by bodhi - uBoot
stef34280, > Here is the output of steps 6 and 7: > > > root@debian:/tmp# flash_erase /dev/mtd0 0 4 > Erasing 128 Kibyte @ 7f5eaf5c00000064 -- 4 % > complete > > root@debian:/tmp# nandwrite /dev/mtd0 > uboot.2017.07-tld-1.pogo_v4.mtd0.kwb > Writing data to block 0 at offset 0x0 > Writing data to block 1 at offset 0x20000 > Writing data to blby bodhi - Debian
shv Wrote: ------------------------------------------------------- > bodhi, > > I found the solution within the following link: > https://unix.stackexchange.com/questions/78535/how-to-get-rid-of-the-scanning-for-btrfs-file-systems-at-start-up. > Maybe I had installed and tested some raid tools > some years ago. Even btrfs-tools wasn't installed > on my system anby bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > On Pogo V4 (must have IP 192.168.222.164), try > > > nc -lup 6666 192.168.222.168 6666 >by bodhi - uBoot
shv, btrfs 1003190 0 raid6_pq 87146 1 btrfs xor 4097 1 btrfs libcrc32c 845 0 Not sure. They were not loaded in my system (Stretch). This might be a difference between Squeeze and Stretch, where Squeeze has different modules dependencies running with newer kernel. How about checking /etc/modules-load.d ?by bodhi - Debian
huge, > I have an old Pogo-Classic (B01) running ArchLinux > that I installed years ago. It was my first > Pogoplug (almost my first linux experience) - I > # uname -a > Linux alarm 2.6.31.6_SMP_820 #6 SMP Thu Jun 14 > 19:49:57 CDT 2012 armv6l GNU/Linux > > > (No idea what version of U-Boot it's running) It is running stock u-boot. > Is this tby bodhi - uBoot
Last post moved here: https://forum.doozan.com/read.php?3,41109 It's always good to create a new thread for question. This thread is a release thread, and for questions pertaining to the released u-boot.by bodhi - uBoot
On Pogo V4 (must have IP 192.168.222.164), try nc -lup 6666 192.168.222.168 6666by bodhi - uBoot
huge, There should be no problem with Pogo E02 netconsole. You probably have some wrong envs.by bodhi - uBoot
> This interface is quite unusual to have > caused the same confusion twice :) I know :) especially with the search dialog, you have to remember to select All Dates, or else it is default to 30 days or so. But it is a simple and fast web interface.by bodhi - Off-Topic
Stephen P Wrote: ------------------------------------------------------- > I don't think mine has a red USB led but I did not > use the USB much before upgrading, so I am not > 100% certain. I have no easy way of telling; if I > could boot the stock firmware I could check but as > previously discussed the new u-boot won't boot the > old firmware. I tried the &quby bodhi - uBoot
stef34280, Indeed. That was my typo in the internal default envs :) usually we just flash the default envs image, which has the correct name for Pogo E02, so nobody noticed this yet. Thanks for reporting this. I will make a note and correct it. Yes, you have fixed it with setenv dtb_file kirkwood-pogo_v4.dtbby bodhi - Debian
haridsv, > I only see this current thread under there, but > before my first post here it was completely empty. > All my previous threads are still missing. That's strange. Probably just a coincidence. Try to resubscribe to threads and see if it works.by bodhi - Off-Topic
habibie Wrote: ------------------------------------------------------- > I can understand that. I used to moderate some > forums that was overwhelmed with spam post. The > only way to curb such spam posts is to block the > IP Address, unfortunately. Usually it is easy fo rme to delete the whole spam topic. This case is more severe, because I have to open each thread and remoby bodhi - Off-Topic