I think the inconsistency between your Arch u-boot and envs is too cumbersome to get it working. So the steps to do: - Boot with kwboot using the latest GoFlex Home u-boot from this tarball: uboot.2017.07-tld-1.goflexhome.bodhi.tar https://forum.doozan.com/read.php?3,12381 -The procedure is similar to this post (which use the NSA310S u-boot). https://forum.doozan.com/read.php?3,51739,519by bodhi - Debian
habibie Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > habibie Wrote: > > > ------------------------------------------------------- > > > My understanding is OP tried to use systemd to > boot a Pogoplug Pro using uEnv.txt. Can we do this > using the above approby bodhi - Debian
spindles7, > > U-Boot 2016.09.01-1 (Oct 10 2016 - 23:11:39 -0600) > Arch Linux ARM > Seagate GoFlex Home This Arch u-boot is older than your current envs. A few commands are not available in this u-boot version. Thay's why it had trouble booting. I'll be back and recommend the next step.by bodhi - Debian
habibie Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > habibie Wrote: > > > ------------------------------------------------------- > > > Bodhi, this just caught my attention. My > question is will this work on any device other > than a Pogoplug Pro? > >by bodhi - Debian
Perhaps not. I could not find the ID 818b in staging driver folder. Only 8192u driver.by bodhi - Debian
ElMariachi, > Hello Bodhi, yes it is an 8192eu for sure. It is already supported in the mainline kernel. Not sure which module you can load, though. I need to look at the source code to find out. Perhaps also I need to configure it in 4.17.2-kirkwood-tld-1.by bodhi - Debian
juandbotiva, Unknown command 'load' - try 'help' Your installed u-boot is 2014.07-tld-1, but your envs are from uboot.2016.05-tld-1.environment.img (load command is only available in my u-boot releases after 2014.07). How did that happen: at one point in time, you must have updated the u-boot envs without updating u-boot.by bodhi - Debian
Derek, The darn thing is, it doesn't always happens... I am sure the envs can be modify to skip IDE since I am pretty sure I don't see myself doing the SATA mods any time soon. Try using only mmc with setenv devices mmc for a while to see if it is consistently boot. If it happens again, insert a sleep period in bootcmd_uenv. setenv bootcmd_uenv 'run uenv_load; ifby bodhi - uBoot
Christopher, Your bootargs was messed up. It should have the console parameter in it. set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 $mtdparts $custom_paramsby bodhi - Debian
Derek, U-Boot 2017.07-tld-1 use an "improved" version of the MMC driver from mainline. And nobody has reported problem with it. So I suspect it might be that your envs have something that caused this flakiness. QuoteU-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700) Pogoplug V4 gcc (Debian 6.3.0-18) 6.3.0 20170516 GNU ld (GNU Binutils for Debian) 2.28 Hit any key to stop auby bodhi - uBoot
Christopher, > I noticed that the rootfs build boots up with > verbose console messages. This is helpful to me > because I can see issues during the boot and the > messages give me someplace to look. > > Your 4.17.2 build turns these off. That's incorrect. Serial console log should show everything from u-boot banner till Debian prompt. There should bby bodhi - Debian
habibie Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > Hi hkguy, > > > > Thanks for reporting this problem. It is indeed > there is a typo in the default envs (my mistake) > :) I'm surprised noboday has reported this before! > Apparently uEnv.txt was not useby bodhi - Debian
Laris, Please state your problem description, which u-boot version you have installed and what is the problem?by bodhi - Debian
ElMariachi, I am away from home so it’s hard to see your problem clearly. Which model of Realtek device is this, do you know for sure that is rtl8192eu?by bodhi - Debian
All, Here is the compiled DTB for the initial DTS. I'm going to add more nodes in this DTB in future posts.by bodhi - Debian
Derek, There is nothing wrong here. The kernel most likely has booted U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700) Pogoplug V4 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 unning scan_disk ... Scan device usb device usb 0:1 1 bytes read in 691 ms (0 Bytes/s) Found bootable drive on usb 0 loading uImage ...by bodhi - Debian
Hi Ray, > Looks like you're making good progress. Wish I > had time to jump in and help, but I'd first have > to locate the hardware in my todo pile. It would be good if you can start compiling the DTS I've posted and try it out. This box is relatively easy, so I can just add new nodes in as Koen discovered some new settings during reverse engineering. >by bodhi - Debian
ElMariachi Wrote: ------------------------------------------------------- > Hello Bodhi! > > Sorry, I confused this.. I had wrong information > from some website. > The driver I really need is rtl8xxxu (for the > rtl8192eu chipset). > I will see if I can compile this myself. But the > problem with the wrong header file pathes still > remains.. I forgot, whby bodhi - Debian
Koen, > One thing which shows that the ethernet is not > configured properly in the dts file yet is that it > now shows up as 100Mb/s while it used to be > 1000Mb/s Does this box really have 1Gbs? > This reverse engineering is quite addictive but it > will have to wait until I'm back home towards the > end of next week. Any tips on figuring out dts > fiby bodhi - Debian
[ 0.839866] pci_bus 0000:00: root bus resource [ 0.839904] pci_bus 0000:00: root bus resource [ 0.839943] pci_bus 0000:00: root bus resource [ 0.839978] pci_bus 0000:00: scanning bus [ 0.840009] pci 0000:00:01.0: [11ab:0510] type 01 class 0x060400 [ 0.840053] pci 0000:00:01.0: calling pci_fixup_ide_bases+0x0/0x3c [ 0.841885] pci_bus 0000:00: fixups for bus [ 0.by bodhi - Debian
Hi Giang, I think the module build procedures you and ayosher are using probably a little old. You should find out which kernel version the released module source was last built on and use that kernel.by bodhi - Debian
Hi Koen, QuoteI don't compile the file but use the following command: dtc -I dts -O dtb -o dove-T50.dtb dove-T50.dts Anyway I changed the values like your example in my dove-T50.dts file. I also had a quick search for the term 'eth' and this showed up in two sections / nodes which were both set to 'disabled'. So I took a gamble and set the status to 'okayby bodhi - Debian
ElMariachi, Yes I did. Try: modprobe r8152by bodhi - Debian
kartikayec, > Hello. > > After these steps the machine boots from hard disk > when both drives are present. > > In case I want to boot from USB, is there a method > ? If both have rootfs then it will be whichever drive is enumerated by u-boot first. So the rootfs should be on USB drive only to ensure that will happen. However, you can tell u-boot to boot kernby bodhi - Debian
Giang, I take it back. I recall this file is in the glibc. Is your build environment conformed to what the media_build required? Probably: apt-get install libc6-dev When in doubt, you can just install Debian build essentials to get all the necessary build components. Usually this will be enough for you to start building most modules. apt-get install build-essentialby bodhi - Debian
Giang, I am traveling, not near my development rig, so can’t give you hands on help. It might be you are using an older Make file that does not play well with new kernel. Can you find the include file sys/socket.h in the headers directory tree ?by bodhi - Debian
Hi Giang, Did you install the linux headers? apt-get install linux-headers-4.17.2-kirkwood-tld-1_1.0_armel.deb That's the first thing you need to do before compiling modules.by bodhi - Debian
Koen, Here is the initial version for Wyse T50. As we go along developing this DTS, we'll add more nodes. Use the DTC compiler to compile to DTB as you have done.by bodhi - Debian