Good idea. See here: http://forum.doozan.com/read.php?2,12096,24034#msg-24034by bodhi - Debian
pengu, So far everything is working? uptime dmesg -Tby bodhi - Debian
> know what is the default kernel Image name to put > in /boot for a Seagate GoFLEX Home/Net stock uboot > to grab. The default name is whatever you want it to be. u-boot envs determine that, not stock u-boot.by bodhi - uBoot
notoneofmyseeds Wrote: ------------------------------------------------------- > And oh, I forgot to ask, can I go ahead and delete > the tars from the USB stick, to save space. > Namely, > Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > and > Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2? > > Thanks a lot! Yes, remove it after installation to save spacby bodhi - Debian
notoneofmyseeds, > What would you have folks do; stick with syninit > or make the changes and move to systemd? OK so I am on the spot, that's fine :) I would stick with sysvinit. For Linux headless embedded devices, systemd is way overkilled for these. OTOH, on a Linux laptop/desktop, systemd is OK and I would not go out of my way to remove it there. > > And clby bodhi - Debian
notoneofmyseeds, > Now I can proceed to installing Jessie? We're done > with all the configurations that will accommodate > future kernel changes, and for systemd? Remember to backup your rootfs before any upgrading. However, your rootfs 4.4 is already jessie. To verify: cat /etc/apt/sources.list This rootfs runs syvinit. Look in the kernel/rootfs thread for insby bodhi - Debian
Quotehabibie Here is the idea why. With a Seagate GoFlex Home/NET still configured to use its original/stock uboot+firmware, I want it to be able to boot off other OS, i.e. LEDE, OpenWRT, etc., when a SATA HDD (installed with either OSes) is inserted. This way, I don't have to replace its original/stock uboot. You can do all that even with stock u-boot, as long as you keep the HDD formattby bodhi - uBoot
I've maded a separate subject for this Kirkwood SATA booting: http://forum.doozan.com/read.php?3,28224 Please continue posting on that thread if it is not related to the Pogo Pro/Classic V3.by bodhi - uBoot
xssa Wrote: ------------------------------------------------------- > Cool! Will try it soon If it possible to boot > stock os from it. > Is there any changelog? It is the same one that I uploaded before for testing (there was no change). I just made it an official release, with the installation instruction from stock. It is no longer in testing phase. I would like to hear froby bodhi - uBoot
pengu Wrote: ------------------------------------------------------- > it seems that wie do not need all the patches in > future. > The Oxnas target is now available in Kernel 4.7 It's for a different OXNAS SoC, and it's ARM9. We have ARM11.by bodhi - Debian
> wouldn't > hesitate to run XP in a lot of circumstances if > the drivers are better developed for hardware. Actually, the most supported platform and easiest to get good peformance out of Kodi is Win 7. The second easiest is Linux OpenELEC. No matter which OS and which hardware, you'll need to make sure it can run with video acceleration.by bodhi - Off-Topic
> Use bootcmd_usb after scan_disk Wrong boot device. Reason: bootcmd still tried to scandisk and found the kernel uImage in the attached USB drive. Do either: 1. Boot without the USB drive attached. or 2. Make sure the rootfs has only OpenWrt kernel files, not Debian kernel files. WTH are you mixing kernels in this rootfs? :)) a. Mount the USB on another Linux box and removeby bodhi - uBoot
> I think that the rootfs (kirkwood and > oxnas) is just the same except the kernel, I'm > using this now. That's right. The rootfs should stay the same, no need to update it. Sure, any time at your convenience. We are not in any hurry! by running "couple days" I meant that would prove the patches work well. If there are lots of activities with samba then it eby bodhi - Debian
mxhdrm, > What I did was simply place the fw_setenv in front > of the first command in section A.1 and that's one > of the errors I've received. Am I missing > something? Note these syntax. There is no equal sign in setting the variable, and the content is placed inside single quotes (in it, there might be embdded equal sign, but it means different thing). In Linby bodhi - Debian
And thanks for the OXNAS patch files. Did you use their config, mine, or your own?by bodhi - Debian
habibie Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > And here shv's post showing how it was done > with > > Debian rootfs: > > > http://forum.doozan.com/read.php?3,16017,17297#msg > > > -17297 > > > > I will have to peruse thby bodhi - uBoot
Joey No standard distro has Kodi by default. Except for specialized distro such as OpenELEC. But you can always install Kodi on Mint.by bodhi - Off-Topic
I've released HP Thin Client T5325 u-boot-2015.10-tld-2. Please see 1st post for installation instruction.by bodhi - uBoot
pengu Wrote: ------------------------------------------------------- > > > > Mostly, not possible. Recent mainline u-boot > does > > not support chainloading a substantially > different > > u-boot from itself. > > I think the problem is, that most U-Boot builds > use the same memory. > Memory footprint (i.e. size) are different. >by bodhi - uBoot
pengu Wrote: ------------------------------------------------------- > news news .. after booting the 4.4.11 kernel, I > could build this kernel without gcc confusion. > The mentioned hung between the two bootloader > stages is also gone (till now) > > > the shutdown: > > in ZyXEL OS, the device reboots, wenn issuing a > poweroff or halt .. > withby bodhi - Debian
I've released this HP Thin Client T5325 u-boot-2015.10-tld-2. Please see 1st post for new installation instruction. Please post questions as you wish in this thread.by bodhi - uBoot
pengu , > I remember that is was possible to start another > U-Boot from stock U-Boot (Cloud Engines) > Is it possible to create a super small U-Boot > binary (no shell, no env, no filesystems, no EFI, > ...) > (<256k) with the ability to start another U-Boot? Mostly, not possible. Recent mainline u-boot does not support chainloading a substantially different u-booby bodhi - uBoot
mxhdrm, You got everything pretty much figured out already. I'll annotate a few points. > I’ve followed Qui’s guides before, but I note > here that the uboot file that he is using (Which I > used) is that of 2013.10-tld-4. I know this is > beyond the scope of my original question, but do I > (or should I, and can I) change the uboot that I > was using to be tby bodhi - Debian
habibie, Yes it does. The Kirkwood SoC 6281 can boot SATA theorically. But GF Home/Net also has UART booting. So SATA is not considered necessary for recovery purpose. For 6281 devices that don't have UART booting, such as Dockstar or Pogo E02, they don't have SATA but they do have JTAG. So SATA booting was never a subject that worth looking into for those. SATA booting requirby bodhi - uBoot
> coherency: ok > [ 0.202457] DMA: preallocated 256 KiB pool for > atomic coherent allocations > ... Ah! that looks new to me.by bodhi - Debian
mxhdrm Wrote: ------------------------------------------------------- > Hello bodhi, > > When I originally started to look for what drive > boots at boot up, I had (incorrectly) assumed I > should do it through fstab. > > But anyway, contained below is the output for the > specified commands. > > > > > Output for : > > >by bodhi - Debian
Looks like you're missing the fw blob in the new kernel. Try reinstall the device, or find where the file is and copy it over.by bodhi - Debian
pengu, > how can I evoke this reproducable? Start with OpenWrt 4.4 patches for Oxnas, and then try both my 4.1 config and OpenWrt's config.by bodhi - Debian
Yes. That's the problem the OpenWrt patch addressed for ARM11 MPCore. They used option d. Quoted) Broadcast of cache maintenance operationsby bodhi - Debian
Ok so here is how to enable serial ttyS0 (which we need to use serial console). diff -Naur /etc/inittab.hptc.orig /etc/inittab.hptc --- /etc/inittab.hptc.orig 2011-09-02 18:32:38.000000000 -0400 +++ /etc/inittab.hptc 2016-05-28 17:44:07.000000000 -0400 @@ -62,6 +62,7 @@ # Example how to put a getty on a serial line (for a terminal) # #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 +by bodhi - Debian