balanga Wrote: ------------------------------------------------------- > What I'm still unsure about after messing about > with u-boot for some time, is how the boot process > works...Is u-boot in NAND and it loads the OS > using bootcmd from fw_printenv? It helps to see Wiki thread. I described at the high level how the boot process works in "How to set up U-Boot foby bodhi - Rescue System
Looker, What you have right now is the latest u-boot and the correct u-boot envs. To install Debian, you just need to create the rootfs using Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from the release thread: https://forum.doozan.com/read.php?2,12096 QuoteUpdated 24 Jul 2017: Basic Debian stretch Kirkwood rootfs for most Kirwood plugs: - tarball size: 188M - instalby bodhi - uBoot
Looker, > sorry to be a pest, Not at all! this is a common problem when booting with my u-boot envs which was written to boot Debian. For Arch it is a little bit different due to the rootfs structure. > ## Booting kernel from Legacy Image at 00800000 > ... > Image Name: Linux-4.4.97-1-ARCH > Created: 2017-11-11 4:51:55 UTC > Image Type: ARM Liby bodhi - uBoot
shayan123 Wrote: ------------------------------------------------------- > > Write allocate disabled > > > Does this have anything to do with the GoFlex not > being able to accept input? > I can see U-boot outputting it’s banners and > all, but I can’t send commands to the device. > > I assume it’s either the “Write allocate > disabled” meby bodhi - uBoot
@habibie, QuoteFor a non-tech savvy, using an OB-200 device is the best option, AFAICT. For me, I would prefer to setup (install) a digital PBX system on my Linux embedded device to handle all my GV calls. In this cae, you probably want to use Asterisk, but my preference is FreeSWITCH. This way, I can use any SIP compliance ATA devices, i.e. HT-701, and a cordless phone as one of the extensionby bodhi - Off-Topic
musv, We are on 4.16.7 already: https://forum.doozan.com/read.php?2,32146 > CPU Power Management -> CPU frequency scaling -> > Armada 37xx CPUFreq support > Is this working for our Armada 380 too? It is not applicable to A38x.by bodhi - Debian
shayan123, QuoteSoc: 88F6281 A1 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz QuoteCPU : Marvell Feroceon (Rev 1) It is a Kirkwood. Either this stock u-boot has been replaced by somebody, or this is some newer version of stock that I vaguely remember seeing somewhere (but not sure). > Should I just ignore this and assume all Kirkwood > relby bodhi - uBoot
Looker, There are a few different ways to to stop netconsole from starting (permanently and temporarily). The easiest way to temporarily stop netconsole is to unplug the Ethernet cable from this Pogo (when you have serial console, you don't need network to troubleshoot booting problem). Another way is changing the netconsole server (where you would run nc) IP address 192.168.0.103by bodhi - uBoot
Looker, Like Ray suggested, the problem might be with the bootargs rootfs=LABEL=rootfs. My u-boot envs set that bootargs to look for the rootfs label rootfs. This is one of the possible reasons why you have rootfs mounting problem. Remember you are booting Arch kernel. So another possible major culprit here is the uInitrd. Arch does not provide uInitrd out of the box, you usually need to aby bodhi - uBoot
QuoteIt is all commented out, so do I simply uncomment the 'segate dockstar' entry? Correct. Quote# grep -a --null-data U-Boot /dev/mtd0ro Warning: U-Boot configured device %s at address %llx, but the device tree has it address %llx. U-Boot** Invalid partition type "%.32s" (expect "U-Boot") U-Boot BUG at %s:%d! U-Boot 2014.04.R2-1 (May 15 2014 - 14:36:05)by bodhi - Rescue System
Somewhere in this thread, arti mentioned how to upgrade Arch FDT kernel: https://forum.doozan.com/read.php?3,58144by bodhi - Rescue System
balanga, > > is a non-FDT kernel. To maximize the > potentials, > > you will need to upgrade this rootfs to FDT. > How do I do that? You need to ask this question at Arch site. We only deal with Debian here.by bodhi - Rescue System
QuoteLinux alarm 4.4.97-1-ARCH #1 PREEMPT Sat Nov 11 04:51:38 UTC 2017 armv5tel GNU/Linux is a non-FDT kernel. To maximize the potentials, you will need to upgrade this rootfs to FDT.by bodhi - Rescue System
balanga, > # fw_printenv > Cannot parse config file '/etc/fw_env.config': > Invalid argument > > Do I need to edit /etc/fw_env.config first? The fact that you are running Arch, then during installation, u-boot has been installed. And the content of the /etc/fw_env.config file should be: cat /etc/fw_env.config # MTD device name Device offset Env. size Flasby bodhi - Rescue System
shayan123, >"Please reboot the target into UART boot mode". Unplug power, start kwboot, and then power on the unit.by bodhi - uBoot
balanga, > > SoC: Kirkwood 88F6281_A1 > DRAM: 128 MiB > WARNING: Caches not enabled > NAND: 256 MiB > *** Warning - bad CRC, using default environment > > Do I need to take any notice of this? This CRC error is expected, when you kwboot the new u-boot (stock u-boot is still in NAND). The CRC error will go away after you flash the envs image during instalby bodhi - uBoot
balanga Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > jcconnell, > > > > This is a quite recent version of Arch u-boot. > > Just wondered how you could tell which u-boot was > being used... I didn't spot any version > information. Just curious... Thby bodhi - Rescue System
balanga Wrote: ------------------------------------------------------- > Do I need to use kwboot with > uboot.2017.07-tld-1.goflexhome.bodhi.tar ? Yes, you need to flash uboot.2017.07-tld-1.goflexhome.bodhi.tar as joerg's instruction stated. Basically, you would install new u-boot, and Debian rootfs. And then install LEDE using that instruction. And if something about installby bodhi - Rescue System
shayan123, > I have a GoFlex Home that won't boot. I've > connected it to a terminal via a USB to UART, but > I can't get any output from the device. > > (I've tested that the CP2102 interface works, > because messing with the TxD and RxD gives me junk > values on the screen. Also, all the indicators on > my CP2102 interface are active soby bodhi - uBoot
balanga, > Apparently OpenWrt can be installed on a GoFlex > Home unit.... > > Does anyone have experience of this and pointers > about how to do this? See the Wiki thread: https://forum.doozan.com/read.php?2,23630 QuoteRescue Systems Rescue System V2 (Original) MacPlug & SMBPLug Rescue System Pogo V3 Rescue System V4, using a custom LEDE firmware (BETby bodhi - Rescue System
balanga, > Just wondered if there was an update to > uboot.2017.05-tld-2.goflexhome.mtd0.kwb before I > proceed... No update to uboot.2017.05-tld-2.goflexhome. This is a special version that I built just for booting FreeBSD the modern way (with u-boot API), which made the image size too big. So there will not be update. Unless I can find a way to trim down the Kirkwood u-bootby bodhi - uBoot
15-Way Linux Distribution / Operating System Comparison, Including Windows 10 & WSL. https://www.phoronix.com/scan.php?page=article&item=linux-windows-15&num=1by bodhi - Off-Topic
Kernel linux-4.4.133-oxnas-tld-1 package was uploaded. Please see 1st post for download link.by bodhi - Debian
Realistically, I think the only SD card that might get you >= 40MB/s Write speed is the Sandisk Extreme. Other Sandisk modles have much slower Write speed (they might have very fast Read speed that exceeds 40MB/s).by bodhi - Off-Topic
ElMariachi, Jeff and davygravy has not been active in the forum for a long time. Their rescue systems work well, so you can use either one. However, these rescue system are basically frozen. If users need help booting them, I will help. But that's all the supports I can provide. Ie. They will not be updated.by bodhi - uBoot
ElMariachi, > I had to change the if statement for making it run > through. As that is why I started messing around > with UBoot before, maybe it would be a good idea > to provide a slightly modified script? Good to just make the script assumes that u-boot is good to go when it sees my released u-boot already installed. As I've mentioned, rescue systems v2 and v2.xby bodhi - uBoot
Quote bodhi, looks like you'd already found the "scsi init" vs "scsi reset" issue, in: ZyXEL nas326 installation problem, (Nov 21, 2017 post) . Too many topics/threads to dig through! :) Thanks wha! I'm glad you've found the confirmation :) I forgot about it completely after many posts and exchanges on different devices in the forum for almost a year. I guesby bodhi - Debian
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 used by a lot of users. To fix this problem, boot into Debian as normal with sysvinit, and then fw_setenv uenv_import 'echo importing envs ...; env import -t 0x60500000 $filesize' Afteby bodhi - Debian
ElMariachi, > Do you have a working link for davygravy's 2.8.2? > I don't use rescue system. I think you should stay with Jeff's V2. You can run that with my latest u-boot. As I recalled , davygravy rescue 2.8.x had some problem (being out of date), and he has been inactive, so no supports if you run into the same problem others have. I have one plug with Jeffby bodhi - uBoot
hkguy, Now we know it happened that nothing got loaded, even after it was reporting importing envs ... Let's debug it further. Interrup serial console at countdown Hit any key to stop autoboot: 0 and run bootcmd_uenv printenv filesize printenv See if the new definitions from uEnv.txt even got populated. And then we'll go to a deeper level in each action.by bodhi - Debian