Here is the thread: http://forum.doozan.com/read.php?3,7477,10982#msg-10982 Look for this section: - Flash uboot.environment to 0xC0000by bodhi - uBoot
jadefalcon100 Wrote: ------------------------------------------------------- > Hi Bodhi, > > I had Jeff's original uboot installed (the one > from the script on > http://pro > jects.doozan.com/debian/) > Don't ask me about the Version Number. ;-) > > NetConsole worked fine before flashing, I haven't > tried booting after flashing because oby bodhi - uBoot
Currently, Arch and Debian are different in systemd vs. sysvinit, i.e startup and shutdown, among other things. Debian will switch to systemd in jessie as a stable release. Definitely, 1 second is just too short when the drive is sleeping. My modification will let the users adjusted the time period for USB drive using a U-Boot env. I've rebuilt 2014.01 U-Boot for all the boxes with this nby bodhi - uBoot
t3ch42, > The problem I find now is my SD card is not > recognized every so often or displays corruption. > I have net console installed, so its only a matter > of resetting the loader, but it takes a few times > to catch it just right. > Any insight on this issue? If I understand correctly, the problem is during booting? if that's true, then we can't do muby bodhi - uBoot
jadefalcon100, The installation assumes the current U-Boot on your Pogoplug is what Jeff's script installed.That has the U-Boot env already at 0xC0000. So there would be no CRC error. - Which U-Boot version did you have before the installation? - Can you connect with netconsole or serial console before, and now? EDITED: typo.by bodhi - uBoot
YodaJM, I'm not familiar with Arch Linux (using systemd), so afraid I can't help you there. It was just a thought to some possible tweaks to see if it helps. Perhaps the ALARM guys know whether it is possible to do this. What you can do now is: interrupt netconsole, and at the prompt, run a few "usb start" commands to see if it eventually detected. And note how many timeby bodhi - uBoot
YodaJM, My guess is it could be that either : Arch (I meant your system specifically, not in general) shutdown process is a little bit too quick, or the 4TB WD Mybook powerdown takes a little too long. Or a combination of these 2 factors. I'm guessing this because I never have reboot problem like your experience (one of my NASs is running this U-Boot and 3.13.1 Debian rootfs on a 4TB Seagby bodhi - uBoot
Ornella, No problem :) Just plug in the USB rootfs that you've created above Using this post: http://forum.doozan.com/read.php?2,12096 i have DEBIAN runing, reinstaled uBOOT with this commands: and boot with it. Rescue system is installed in NAND, for rescue purpose. But it's not a full Debian system in the sense that you want to use it day-to-day. The rootfs that yby bodhi - uBoot
You have not completed booting yet: scanning bus for devices... 2 USB Device(s) found scanning bus for storage devices... 0 Storage Device(s) found ** Block device usb 0 not supported Make sure the Debian rootfs USB is plugged in!by bodhi - uBoot
You probably need to: - label your rootfs - set your u-Boot envs to look for it See here: http://forum.doozan.com/read.php?3,8044,8152#msg-8152by bodhi - Debian
lewy1, - Make sure to extract the rootfs as root user. - If you have netconsole log, please post. Your U-Boot envs look OK. - The prompt seems to indicate that you've booted into Pogo OS?by bodhi - Debian
elbric0, Did you extract the rootfs as root user?by bodhi - Debian
Looks like it is already supported by the kernel. dvb_usb_v2 12048 1 dvb_usb_it913x dvb_core 75539 1 dvb_usb_v2 rc_core 12580 2 dvb_usb_v2,dvb_usb_it913x Like I've said, you can find a configuration tool or some software to control it. Google will give answers :)by bodhi - Debian
PlanetEater Wrote: ------------------------------------------------------- > Just don't forget to salvage ethaddr. Right! either document that in the installation steps, do it the script, or generate a local ethaddr automatically for booting temporarily.by bodhi - uBoot
Cool! Reminder: t's more convenient to *not* saveenv in UBoot until after you can boot with that default envs.by bodhi - uBoot
Could somebody who has the NSA325 post a complete U-Boot boot log? I could help trying to find more info on the SoC to see if there are different ways to run U-Boot. For example, the SoC for iConnect is 88F6281_A0: U-Boot 2013.10 (Feb 21 2014 - 20:02:23)-tld-2 Iomega iConnect SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 512 MiBby bodhi - uBoot
@BigRon, I took a look. And unfortunately I'm not familiar with I2S so I can't figure out exactly what config switches should be included. Perhaps you can find out the information, and I'll be glad to include them later. http://forum.doozan.com/read.php?2,12096,15042#msg-15042 @lome, Regarding the CONFIG_PM. I don't think I will include this, because it will probably mby bodhi - Debian
I meant just plug it in. Check dmesg to see if your DVB-T USB is detected. Is this what showed in dmesg? Bus 002 Device 005: ID 048d:9135 Integrated Technology Express, Inc. Zolid Mini DVB-T Stick Then check the modules running: lsmod If the module(s) is on the list, then perhaps it was already supported in the running kernel. You can look for information about the modules where youby bodhi - Debian
Go head and install it. It might already had support in the kernel in the latest rootfs that I've uploaded.by bodhi - Debian
msanad, 1. A correct system date and time is a must before you do anything else. 2. Looks like the script is trying to patch and recompile the kernel. It is not possible, since you don't have the source. I'd suggest you look for modules sources and compile that. If that's not feasible then you could learn to compile your own kernel. And then run the script.by bodhi - Debian
What's your date? is ntp running?by bodhi - Debian
msanad, tar xfj linux-media.tar.bz2 tar (child): bzip2: Cannot exec: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now make: *** Error 2 apt-get install bzip2 And then run through the installation again.by bodhi - Debian
marcint43, Congrats! Concur. I think this exportfs error message was a terrible error message, a lazy way to report a warning :))by bodhi - Debian
I agreed. It seems to be a power issue, because leaving it in the slot while booting UART, it does not spin at all. And I also did try (once), to plug the GoFlex drive in while at U-Boot prompt, and it hung. I had to recycle the power. I'm gonna try the bare SATA II drive to see if it behaves differently.by bodhi - uBoot
Hi ebbes, > Sorry, I don't quite understand what's exactly > going on: Does your drive work in external drive > but not when plugged in directly or does it work > either way? I did the reversed test. The drive inside the 2.5" enclosure works fine with ide reset. So I took it out and plug it in the SATA slot, and ide reset failed. This also proved that SATAby bodhi - uBoot
ebbes, > u32 timeleft = 10000; /* wait at most 10 ms for SATA reset to complete */ I've tried different numbers from 25 to 100ms. It had no effect. > then some GPIO would have to be written to in > order to start the drive This would be very nasty to hunt for this in Marvell U-Boot! > Looking into the (horrible) Marvell U-Boot Could not agree more! I'd brieflyby bodhi - uBoot
marcint43, Reboot. Check if NFS share is visible from another box.by bodhi - Debian
markweng Wrote: ------------------------------------------------------- > When I tried another uboot from Malc > http > ://forum.doozan.com/read.php?3,15091 > > Ide reset is OK. so should not be the power > problem. > Hope this help. Agreed. But you are running modified stock Marvell uBoot from Malc. Not the latest from mainline u-Boot source tree. It's mostby bodhi - uBoot
marcint43 Wrote: ------------------------------------------------------- > > Marvell>> printenv > bootargs=console=ttyS0,115200 > mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_en > v),0x80000(key_store),0x80000(info),0xA00000(etc), > 0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(ker > nel_2),0x2FC0000(rootfs2) root=/dev/nfs rw > init=/init > bootdelby bodhi - Debian