Bob, I took a look. There is no envs in there that I can see.by bodhi - Debian
cdlenfert Wrote: ------------------------------------------------------- > One thing I caught in this thread is that you can > put rootfs on a USB, then clone that to and SD > card and swap them out? Is that correct? Yes. It is correct. Same for HDD. The u-boot env that make sure all 3 types of devices are scanned for booting is devices.by bodhi - Debian
AngryCoder, > Any chance you will ever take a look inside the > steam link anytime soon? If you don't plan to, I > might as well get rid of the 5 steam links I > stocked up. As usual, I don't really know when I will start looking at a new box.by bodhi - Off-Topic
Pickle Wrote: ------------------------------------------------------- > Yes that is basically the last line. In the dmesg > output i actually disconnected and reconnected. > > Actually i think might have misunderstood your > request. Did you want me to get the logs from NAS? Yes. > These were logs from attaching the drives to my > laptop. If you mount the driby bodhi - Debian
Bob, > I looked at the source code you mentioned a few > posts back and the mimas board .c file has offset > as 0 for the mtd device (if I'm reading that > right). That's incorrect. That code is the kernel code patch which does not have any info about boot loader. What we lack is the GPL for their boot loader version. And they also turned off input/ouput for this bby bodhi - Debian
Bob, Does your stock OS have the same /etc/fw_env.config as Koen’s?by bodhi - Debian
veriqster, > Now if someone could help me figure out how to > boot of SATA, .... > I've tried the instructions in the SATA thread, That's unescessary. What you saw in the SATA thread was a direct booting mechanism for Pogo V3. One we use for rescue purpose. Since you have installed new u-boot U-Boot 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700) The booting procesby bodhi - uBoot
Pickle, Is this the last line in the log? [ 1104.970564] sd 4:0:0:0: Attached SCSI disk I was hoping to see some errors in the log before Quote(issue is that drives seem to drop and the nsa iteself seems unresponsive. Light for hd1 turns orangeby bodhi - Debian
Bob Wrote: ------------------------------------------------------- > Hi bodhi > > I see. I guess I didn't edit the config properly. > It doesn't help that the format is different from > the old Ubuntu version. > > contents of original Ubuntu fw_env.config: > > # MTD device offset size erase_size > /dev/mtd0 0xc0000 0x10000 0x10000 This locaby bodhi - Debian
Bob, > It's unable to read the chip with fw_printenv > after editing fw_env.config. Gives a bad CRC > message. That CRC error does not mean the chip is inaccesible. It means the envs are either at wrong location, or it was not initialized. To determine if the SPI chip was OK, and mtd partition(s) is on it: cat /proc/mtdby bodhi - Debian
Pickle, > My NSA320 has been acting odd lately and before I > give up and get new hardware Id like to update it > to newer uboot/kernel. What is currently installed on this box? > (issue is that drives seem to drop and the nsa > iteself seems unresponsive. Light for hd1 turns > orange, but reboot clears it. Disk checks and > SMART info dont point out any issues.by bodhi - Debian
Kernel linux-4.18.4-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.by bodhi - Debian
Hi Bob, > Is it safe to use this dtb now? I'm just thinking > about your warning earlier about possible > corruption if the GPIO is not correct. Yes. It is safe to use. The behavior is exactly what I expected from reading the Dell patch. > P.S. it seems both of mine have a different spi > chip than Koens: > > > [ 0.683083] m25p80 spi0.0: found mx25by bodhi - Debian
Joey, Caig DeOxit ProGold sounds impressive indeed! thanks for the advice. It'll come in handy in many occasions. Perhaps even more when I retire and move to an ocean-view bungalow somewhere :)by bodhi - Off-Topic
Actually, that error should not be ignored. So I've checked the Linksys EA4500 which has 6171 switch chip. Try that definition :) switch@16,0 { #address-cells = <1>; #size-cells = <0>; reg = <16 0>; /* MDIO address 16, switch 0 in tree */ &mdio {by bodhi - uBoot
wacke, Try changing the compatible attribute to to 6171. They use common code, but there should be some differences.by bodhi - uBoot
Bob Wrote: ------------------------------------------------------- > Hi bodhi > > That one seems to works here. Booted into the > system fine and it shutdown fully when I sent a > poweroff command. Cool! I got it in reverse bfore (the Active Low state of this GPIO , meaning it should be high when the kernel started and we want to trigger it to be low when shutting down).by bodhi - Debian
Here is another version. Please try the shutdown.by bodhi - Debian
wacke Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > Is this the mv88e6085 switch, and do you know > if > > register 0x10 is correct? your dmesg showed no > > activity at all regarding DSA. > > The switch chip is 88E6171R,and the register 0x10 > was copied frby bodhi - uBoot
I think I need to see serial console output during shut down (with Aug 23 DTB). The Mimas kernel patch looks to be a correct one for Koen's dmesg. Update: Ah. Seems to be Active Low/High problem.by bodhi - Debian
Bob Wrote: ------------------------------------------------------- > Hi bodhi > > I tried this new dtb but the system shuts down > around where it would start booting the rootfs. Thanks Bob! So either GPIO 8 is not the right one or it is the Active High/Low problem! Please post your stock dmesg log. I'd like to check if it is the same as Koen's.by bodhi - Debian
All, Perhaps Monoprice in the US is a better place to buy these? it's not as a cheap/inexpensive as HDMI switchers from Aliexpress. But Monoprice's price is usually lowest for good audio/video components, and quite reliable, as far as I can tell (I bought cable/charger/ethernet-switch/... stuff for many years from Monoprice). Of course Joey is the authority here regarding audio/vby bodhi - Off-Topic
Hi wacke, > Any update for your Armada based board? As you can see, there always seems to be some new and interesting boards requests for kernel supports in the forum, so I can't find free time to work on u-boot :)) switch0@10 { compatible = "marvell,mv88e6085"; #address-cells = <1>; #size-cells = <0>; reg = <0x10>; Is this the mv88eby bodhi - uBoot
Here is another DTB version. This one has GPIO power-off node to shutdown the box properly. Warning: there is a small risk in testing GPIO, I would caution that you back up your stock rootfs and envs, just in case. Usually I do these tests myself before publishing it, but I have not received my eBay box yet, so I can't test the HW to be sure, that I will brick my box first if I made a misby bodhi - Debian
@Koen, > I did have the same issue > with shutdown not working properly and ended up > just pulling the power cable. Thanks! good to hear that confirmation. @Bob, [ 0.414602] dove-pinctrl f10d0200.pin-ctrl: falling back to hardcoded PMU resource [ 0.414774] dove-pinctrl f10d0200.pin-ctrl: : Missing pinctrl regs in DTB. Please update your firmware. [ 0.415501]by bodhi - Debian
ElMariachi, Please post the link for the driver source code or kernel patch (preferred). Perhaps I could try to include this in the kernel 4.18.4 that I am starting to build to see if I get these errors (I can't promise that I will spend lot of time, but my build environment should be a good test for this).by bodhi - Debian
Quotebodhi What Bob saw was probably the lack of T50/T10 poweroff (GPIO or what not) driver hook in new kernel. This can be found in GPL. Yes. There is a GPIO power off in there.by bodhi - Debian
Quotebodhi All, Perhaps the Wyse T50/T10 patches can be found in the hedley repo as Koen reported: https://forum.doozan.com/read.php?2,63499,65094#msg-65094 Yes it is. The kernel patches is in http://oem.archive.canonical.com/updates/pool/public/l/linux-mvl-dove/linux-mvl-dove_2.6.32-212.28hedley14.tar.gzby bodhi - Debian
All, Perhaps the Wyse T50/T10 patches can be found in the hedley repo as Koen reported: https://forum.doozan.com/read.php?2,63499,65094#msg-65094 What Bob saw was probably the lack of T50/T10 poweroff (GPIO or what not) driver hook in new kernel. This can be found in GPL. @Koen, what do you see when power off in Debian? shutdown -h nowby bodhi - Debian
Bob, > One issue I'm finding with the new kernel is that > I can't shutdown the unit over ssh. It seems to > hang somewhere so I have to hold in the power > button to get it to power off. This is where a serial console will help seeing the exact behavior. I'll take a look at the DTS to see if I can find some hint.by bodhi - Debian