rayknight Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > Anybody who has connected serial console, > please > > post pintouts. > > J4 J6 3.3V | RXD | TXD | > GND > JTAG X|X|X|X|X|X|X|X|X|X| JP1 > X|by bodhi - Debian
Try both cases: 2. Power up, interrupt serial console setenv bootcmd 'run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset' boot 2. Power up, interrupt serial console setenv bootcmd 'run bootcmd_uenv; sleep 15; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset' bootby bodhi - uBoot
armless, > (1) the Debian USB stick is ext3 but there's such > module in the initrd and the ext3 fsck failed, but > it managed to mount the rootfs using ext4's > backward compatibility, and to fsck it then: This is normal. Ext3 has been deprecated. Ext4 module is always used whether the rootfs is Ext3 or Ext4. > (2) some kernel error about the Kirkwood hardwarby bodhi - uBoot
> Where would I need to store these commands for > making this work for booting? Ah. So now you know it does work, but need some extra period to settle down. You can change your bootcmd to take out the uenv loading, just leaving the scandisk in: setenv sleep_period 15 setenv bootcmd 'run scan_disk; sleep $sleep_period; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; resby bodhi - uBoot
ElMariachi, > I am using screen in mint 17.3 MATE. Don't use screen. Install picocom and use that. Screen is the worst to use with serial console.by bodhi - uBoot
Laris Wrote: ------------------------------------------------------- > it's appreciated! > > I was struggling with the egg-chicken problems for > many days and cannot found the valid Arch Arm URL > int the stick list. > I already flashed the latest Uboot according > bodhi's post in offical openwrt, but cannot boot > any debian system to install latest kby bodhi - Debian
Try in serial console setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x800000 /boot/uImage; ext2load usb 0:1 0x1100000 /boot/uInitrd setenv bootcmd 'setenv bootargs $(console) root=LABEL=rootfs rootdelay=10; run bootcmd_usb; bootm 0x800000 0x1100000; reset' boot And pls post the log here. There is more to do in your u-boot envs. But let's get you boot the rootfs iby bodhi - Debian
Boot, Interrupt serial console and ide reset sleep 15 ext2ls ide 1:1 /by bodhi - uBoot
Use root=LABEL=rootfs in bootargs, dont use the drive letlter sda1,sdb1....by bodhi - Debian
ElMariachi Wrote: ------------------------------------------------------- > By extra steps you mean the workaround using USB > flash? The SSD was initialized OK in u-boot. So to use it, probably a longer sleep period is needed. To test that, do everything manually at u-boot console. For example, wait longer after "ide reset".by bodhi - uBoot
freestyle, Please always post a completed bootlog, don't excerpt. There are very relevant info to troubleshoot in the entire log. Let's go back to when you prepare the rootfs Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2. Were you root user the whole time? is the rootfs type ext3? is there a single partition? is the rootfs labeled rootfs?by bodhi - Debian
> All set now. Awesome! It's not necessary to, but if you'd like, visit bodhi's corner for info: https://mibodhi.blogspot.com/by bodhi - uBoot
feas Wrote: ------------------------------------------------------- > Had to play with the setenv variables as I got > various errors but I am in as root now. > > So do I redo your uboot > http://forum.doozan.com/read.php?3,12381 again? Cool! Yes, redo uboot and adjust envs as you did before. If no error occurs then you will be back in business.by bodhi - uBoot
I was too lazy to open up my multimeter :)) on the shelf somewhere.by bodhi - Debian
You already have the Debian 4.4 rootfs. You can try tftp the kernel files. - Copy the uImage and uInitrd from that rootfs to the tftproot (of the one executing serial console). Setenv ipaddr and serverip (to your local network specifics), and load the images. setenv ipaddr 192.168.0.xxx setenv serverip 192.168.0.yyy setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 rootdelay=10by bodhi - uBoot
Ok. Let's power up with a USB drive attached (any drive that was formatted as Ext2/Ext3), interrupt serial console, and printenv usb start If you can see the USB drive here from the "usb start" above, then do ext2ls usb 0:1 / If you can see the directory listing, then you can boot the new Debian 4.4 rootfs. And once you are in Debian, you can reflash the new u-bootby bodhi - uBoot
freestyle Wrote: ------------------------------------------------------- > Hello, > > I have a Netgear Stora and i try to run > Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > > what is the u-boot env vars to the version "U-Boot > 1.1.4 (Jul 31 2009 - 10:33:00) Marvell version: > 3.4.14" for run USB rootfs? > > Thankz If you have seriaby bodhi - Debian
Last post moved to its own thread.by bodhi - Debian
Ok so do you have a log of what you did? Was some nand.e and/or nand.w commands executed, and the stock u-boot was written back to mtd0 by mistake?by bodhi - uBoot
You need to slow down a bit. Hacking should be done leisurely :) Rescue system is not important when you have serial console.by bodhi - uBoot
feas Wrote: ------------------------------------------------------- > What I posted is what I get usb or not. So I think > I need to tftpboot the files to nand from uboot to > fix the corrupt image. I do not get a shell or > login prompt. You meant now it boots into the stock u-boot right away without you doing anything?by bodhi - uBoot
This is common. Not all SSDs work with u-boot. But the Transcend SSD seems to be working. Reset IDE: Bus 0: not available Bus 1: OK Device 1: Model: TS32GSSD25S-M Firm: 101028 Ser#: 20110414418743075560 Type: Hard Disk Supports 48-bit addressing Capacity: 30533.8 MB = 29.8 GB (62533296 x 512) It just need to be handled with extra steps, sinby bodhi - uBoot
Now, if you still have problem booting with the new u-boot and USB, then power up, capture serial console and post the log here.by bodhi - uBoot
feas, I would suggest that you use Jeff's V2 rescue system. You're trying to make something works, but the author is no longer supporting it. It will be more works than really neccessary. Rescue system is something you would expect it to be rarely used. The best use for it if it would never run at all :)by bodhi - uBoot
bobafetthotmail Wrote: ------------------------------------------------------- > rayknight Wrote: > -------------------------------------------------- > ----- > > The file is 276MB. Where would you like me to > > upload it? > > > > Ray > > Google Drive (if you have a gmail account)? > Sky Drive (if you have a microsoft/hotmail/outlook >by bodhi - Debian
Anybody who has connected serial console, please post pintouts.by bodhi - Debian
habibie, > I gathered this scripts will overwrite the stock > firmware with Debian Linux. No, it does not.by bodhi - Off-Topic
I've updated the first post to include description and links to binaries.by bodhi - uBoot
Also see: http://forum.doozan.com/read.php?3,16017by bodhi - Debian
habibie Wrote: ------------------------------------------------------- > bobafetthotmail Wrote: > -------------------------------------------------- > ----- > > I'm developing a installer script to install > uboot and rootfs in kirkwood devices (and anywhere > else we get uboots for, anyway). here > http://forum.doozan.com/read.php?3,28966 > > > Doby bodhi - Off-Topic