elcaramba, bootargs env looks wrong. Substitue $(bootargs_console) then you got only console=ttyS0,115200 bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfs=ext2 bootargs_console=console=ttyS0,115200 bootcmd=setenv bootargs $(bootargs_console); run bootcmd_usb; bootm 0x00800000 0x01100000by bodhi - Debian
Val532, It is in the mainline U-Boot, so it is possible: Active arm arm926ejs kirkwood LaCie net2big_v2 d2net_v2 lacie_kw:D2NET_V2 1. Is it the correct one, i.e. d2net v2 ? probably is the same. However, V2 might indicate some memory differences. 2. Do you have serial console and can you boot with UART (kwboot)? 3. What isby bodhi - uBoot
elcaramba, Do these 2 things: 1. Make sure you have extracted the rootfs to a USB drive as root user, as stated in the instruction (sudo won't work). If you did not, then redo the rootfs. 2. Take your rootfs drive to anothe Linux box and fsck it for errors.by bodhi - Debian
sambul14 Wrote: ------------------------------------------------------- > I mean make it scripted in env plus a single > interaction with Netconsole to select a number > corresponding to the OS chosen by a user at boot > time. Yes. But with a caveat. The normal way is to to run a pre-scripted environment variable to boot an OS on a particular disk. So several variables neededby bodhi - uBoot
narddawg314 Wrote: ------------------------------------------------------- > I'll report back ASAP. Thank you very very very > much!! > > EDIT: No such luck. I think the USB is being > read briefly because the light will flicker a few > times but then the red flashing light comes back. Did you change anything related to U-Boot? if you did not, keep trying theby bodhi - Debian
sambul14, > Is there a way to automatically stop the boot > process and show Marvell>> prompt in Netconsole > without pressing any keys? Not without adding this function to U-Boot. > How to proceed the boot process after it was > stopped after a certain parameter was selected out > of several options available without doing Uboot > Reset? Not sure whatby bodhi - uBoot
johnklos, > People say there's "absolutely no point" in keeping a modern operating system running on VAXhardware, but that's demonstrably not true. Well said :)by bodhi - uBoot
There are several options to install Debian in that thread! which approach did you take?by bodhi - Debian
NobuoT, > Kernel 3.12.0-5 on the other hand boots up without > problems from bootcmd whithout having to interfere > in uboot. What is the difference between your rootf and this? > > My bootcmd looks like this: > bootcmd=ide reset; ext2load ide 0:1 $(loadaddr) > /uImage-3.13.1-2; ext2load ide 0:1 0x01100000 > /uInitrd-3.13.1-2; bootm $(loadaddr) 0x01100000by bodhi - Debian
Kernel 3.14.0-kirkwood-tld-1 package was uploaded. Please see 1st post for download link.by bodhi - Debian
NobuoT, > I also didn't use your rootfs but took an image of > a debian installation that ran on my plug computer > and installed your kernel in this image (by chroot > from stock firmware on nsa325v2), but didn't > modify the init scripts or anything. Could > anything go wrong there? See if the persistent net rules is the problem (one of typical problems whby bodhi - Debian
WarheadsSE Wrote: ------------------------------------------------------- > Has anyone made an effort to pull from 2013.10 to > 2014.1? I'm going to try that in the next few days.by bodhi - uBoot
Flooreus, First thing is U-Boot can't find any kernel (uImage) on your 2nd HDD. So it can't boot the kernel. I'm not familiar with davygravy's U-Boot build so I can't say why it enumerated your HDDs as hdxx. And this will come into play in the bootcmd. > Under which environment variable is this set? I assumed having boot_sata1 set to look at /dev/sda1would be enoby bodhi - Debian
narddawg314, If you have not installed anything (e.g. changing U-Boot) in NAND mtd partitions, and have only messed with your stock HDD, then you can do a factory recovery: http://support.goflexhome.hipserv.com/en/reflash/index.html But if you can't do factory recovery then you will need serial console. Most GoFlex Home have serial header, but some don't, so you need to open it tby bodhi - Debian
I've uploaded 2014.01-tld-1 u-Boot images for GoFlexNet, GoFlex Home, Pogo E02, Dockstar, iConnect, and Netgear Stora. Please see 1st post for download links.by bodhi - uBoot
There are quite a few things that are wrong. Are you booting the original NSA320 U-Boot (much older U-Boot version)? The info that raises attention right away is: Loading file "/boot/uImage" from ide device 1:1 (hdb1) meaning U-Boot looks for /boot/uImage from the second hard disk. And your boot_sata1 boot_sata1=mw 0x800000 0 1; setenv bootargs console=ttyS0,115200 root=/dev/sby bodhi - Debian
Hi NobuoT, If you look back a few post, Buttzy started out with 3.13.1-kirkwood-tld-2. And later compiled his own kernel 3.13.2-nsa-325. And perhaps you 100MBit Ethernet has something to do with the problem. I recalled some people has problem running 100Mbit network with some Kirkwood boxes (don't remember which one). Are you connecting with serial console? it would be helpful to poby bodhi - Debian
Arch Linux instruction http://archlinuxarm.org/platforms/armv5/seagate-goflex-home Once you get in, just run Jeff script to install U-Boot and Debian (run the squeeze script, not the wheezy script), and upgrade to wheezy. Or use this rootfs: http://forum.doozan.com/read.php?2,12096by bodhi - Debian
Take a look at Buttzy's dmesg, perhaps you can spot where the problem. Looks like hwmon failed, and that was the last line in dmesg? http://forum.doozan.com/read.php?2,14351,15284#msg-15284by bodhi - Debian
Yes, certified repair means stock, so you will need to register online to get access to SSH.by bodhi - Debian
Here is what I did: http://forum.doozan.com/read.php?2,13702,13704#msg-13704by bodhi - Debian
fw_setenv will save it immediately. To verify if netconsole setup correctly, post the output of fw_printenv here (no automatic way to check).by bodhi - uBoot
You can interrupt netconsole, and execute printenv post the out put here, and we'll take a look if anything missing!by bodhi - uBoot
When you see this: OK Starting kernel ... and then it stuck there, most likely the problem is with either the bootargs or the rootfs on the USB stick.by bodhi - Debian
Lallo, It booted in to Pogo OS in NAND. Looks like your Debian USB rootfs is bad (not the drive, the rootf itself): Loading file "/boot/uImage" from usb device 0:1 (usbda1) ** File not found /boot/uImage ** Block device usb 1 not supported ** Block device usb 2 not supported ** Block device usb 3 not supported Loading file "/boot/uImage" from usb device 0:1 (usbdaby bodhi - Debian
schumischumi, Your U-Boot envs look OK. Have you tried checking your USB rootfs for error ? (using a different Linux box and fsck it).by bodhi - Debian
JohnXX, If you have not changed any of U-Boot envs (you have only played with rootfs), then it does not hurt to try these first: - On a different Linux box, fsck your rootfs to see if there is any error. Cold boot after the check. If this did not boot then, - Make a basic fresh rootfs on a different USB stick, and try to boot with that. The LED should be green after the U-Boot has loadeby bodhi - Debian
This needs to be fixed: fw_setenv=serverip 192.168.1.204 This is OK: usb_set_bootargs=setenv bootargs console=$console root=UUID=$usb_root_uuid rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params usb_root_uuid=846f98f1-d318-436f-b860-78f77d80f635 But a better approach is using rootfs label: http://forum.doozan.com/read.php?3,8044,8152#msg-8152by bodhi - Debian
WarheadsSE, Sure. I was hoping to get confirmation from YodaJM, or somebody before doing that. But it should not impact any thing to include it.by bodhi - uBoot
YodaJM, See this post: http://forum.doozan.com/read.php?3,12381,15608#msg-15608by bodhi - uBoot