PhantomsDad Wrote: ------------------------------------------------------- > To reply to my own question.. > > The solution apparently had nothing to do with > "kernel flash". I had formatted the rootfs as > ext2 and my sata_rootfstype was ext3. Changed the > rootfs type to ext3 and edited /etc/fstab. All is > well now. Sorry for the noise. Thanks foby bodhi - Debian
enki, With the GoFlex Net, it is pretty safe to mess with uBoot, because you have UART booting: http://forum.doozan.com/read.php?3,7852,7852 What I would do is: 1. Try to run the Squeeze installation again (see http://projects.doozan.com/debian/) and see if it will flash uBoot for you from the script. If it does, then you can use the new Squeeze rootfs, or your exiting rootfs to try booby bodhi - uBoot
Hi restamp, The 3V+ should not be connected (the serial module converter uses power from USB). About the direct connection, I had the same thought, but I've found that the connectors on the wires were too big for the Pogo serial pins! I thought there must be a smaller connector out there that we can crimp on the 3 wires so that the header is not necessary, but so far I could not findby bodhi - Off-Topic
restamp, I use this JST header, come with 4 wires attached. http://www.ebay.com/itm/Micro-Mini-JST-2-0-PH-4-Pin-Connector-w-Wire-x-10-Sets-/171042546645? and this serial module converter: http://www.ebay.com/itm/USB-2-0-to-TTL-UART-6PIN-Module-Serial-Converter-CP2102-STC-PRGMR-Free-cable-/170895253016?pt=LH_DefaultDomain_0&hash=item27ca269e18by bodhi - Off-Topic
I don't think the serial wires would cause this type of problem. You've bought it from somebody? perhaps the USB port has problem. Does it work with a thumb drive?by bodhi - Debian
Hi Goetz, The tarball has everything you need (the patch file, config file, kernel deb package, kernel headers). So you can get the 3.9.11 source from the kernel source tree and apply the patch to it.by bodhi - Debian
Here is my cleaned up log when I did the flash around the bad block (the 2nd time to update uBoot). I have one bad block. The uBoot image was built by Davygravy. And by the way, restamp gave me the guidance way back when I did this the first time! and I updated this Pogo E02 the 2nd time with the new uBoot the same way we did before. Thanks again restamp! Flashing uBoot on Pogoplug E02 wiby bodhi - Debian
You can try this rootfs to see if it gets any better: http://forum.doozan.com/read.php?2,12096by bodhi - Debian
mindm49907, Since you got 2 bad blocks in the middle of uBoot image, you will need to verify them to see if it was flashed OK. I did the same thing a while back. Let me see if I can get my old log out and work out the steps for you, perhaps tomorrow :) once you've verified a good flash around the bad blocks, uBoot will be bootsstrapped OK. IIRC my experience with it, in your case you willby bodhi - Debian
Hi Chessplayer, Probably because you need to set /sys/class/leds/xxx/trigger to the correct value at the end of /etc/rc.local to turn it green. It's in /etc/rc.local in my rootfs. AFAIK, the NSA320 patch should allow the HDD (ide) trigger to be set and the HDD LED will automatically flash whenever disk access occur. This works on Goflex Net.by bodhi - Debian
oakle470, You don't need to reflash uBoot again! it should be fine as it is. 1. The first thing to do is to get uBoot envs printed out: interrupt uBoot and post the output of printenv here: > printenv 2. Make sure the USB drive format matches usb_rootfstype, and it's labeled rootfs. 3. To ensure uBoot will find this rootfs, some uBoot envs need to be changed. But letby bodhi - uBoot
chessplayer Wrote: ------------------------------------------------------- > Hi, > > I know for a fact (learned the hard way) that if > the server is not reachable (in your case > 192.168.11.149), it will seem as if the thing does > not boot. After over an hour, it might actually > relent and boot ... > > So, for some reason, the ZyXel does not just skip &gby bodhi - Debian
It turned out to be a configuration problem with distcc. My hunch was this problem has to do with the IP mask (why IPv6?). After checking the ports on both server and client I noticed that on the remote box, distcc was listening on port 3632 with tcp6. On the compiling box, distcc was listening on port 3632 with tcp. netstat -an | grep 3632 tcp 0 0 0.0.0.0:3632 0.0by bodhi - Debian
I'm setting up distcc and kept getting this denied by access list error. Could not fingure out why. The compiling host is 192.168.0.224, the remote host (volunteer) is 192.168.0.228. I've turned on debug in /etc/init.d/distcc and got these error info on 192.168.0.228: Remote host denied access log: distccd[26818] (dcc_check_client) connection from ::ffff:192.168.0.224:40342 diby bodhi - Debian
ingmar_k Wrote: ------------------------------------------------------- > If I am not mistaking, the udev problem could be > solved by porting OXNAS support to kernel version > 2.6.32, right? > > If that is correct, I might try to do that. With > the emphasis on "try", because I never did > something comparable before. But, as 2.6.31-14 to > 2.6.32-61 dby bodhi - uBoot
There is no other way other than JTAG (i.e. hardware to get the console output). With this Pogo, you don't need to do any soldering. The JST header would be all you need to connect the wires out to serial converter module.by bodhi - uBoot
You can try either: 1) - The quickest way to get it boot into Debian is to use this rootfs: http://forum.doozan.com/read.php?2,12096 - Next, you can print out uBoot envs while in Debian and we can take a look to see if they are all OK. fw_printenv - Set up netconsole while in Debian (there is no file to be added, just environment variables, and using another PC to connect) http://forum.by bodhi - Debian
oakley470 Wrote: ------------------------------------------------------- > Ohhh, ok I had thought any linux package just used > the same commands. Thanks you did answer my > question, I'll see how it goes to modify > the commands. In the event I just decide to > install arch and follow that guide I would have to > put in a second flash drive and modify the mount >by bodhi - uBoot
kuleszdl Wrote: ------------------------------------------------------- > @shv: No I',m not getting any of these "fail" > messages.I looked in dmesg, syslog and > log/messages, is there supposed to be something > extra on the serial console only? Serial console gives you lot of output, some problem can't be solved without serial console. Output such as in sby bodhi - uBoot
mindm49907, After UART booted and you've interrupted uBoot, please get the list of envs and post here > printenvby bodhi - Debian
@shv , > It seams that rc.local is stopped after the > execution of the line > > /sbin/proled green > > with the FAIL message even proled is available and > the LED is lighted up. It might be that because devmem was not loaded before proled.by bodhi - uBoot
I've updated the first post to include the warning about flash-kernel. Thanks eas. Sorry I also forgot the md5 for the 3.9.11 rootfs :) it's included now.by bodhi - Debian
@eas, Yes. I thought about putting a warning in the first post, but forgot to do it. Sometimes, dpkg -i command executes flash-kernel and does not deal with the error successfully, so it messes up initrd.img, but not always. Normally, people don't install flash-kernel so never have this problem. I recall that it did not cause problem for me in before 3.1.x kernel, perhaps something has chby bodhi - Debian
Oakley, Arch package management commands are different. Pacman is package manager on Arch, apt or dpkg is Debian package manager. For installation purpose, that guide can not be used as is on Debian. So if you want to follow that guide, you will have to rework it to use Debian dialect. For example, pacman -Syu samba in Debian it is: apt-get install samba so on so forth. Hoby bodhi - uBoot
syro Wrote: ------------------------------------------------------- > Hey i have a serial cable (ca42) and i have get an > output. but the problem is i cant send any key to > the device to interrupt the auto boot. > > i have used minicom and putty on two different > laptops but no luck :-( any advice for me? > > thank you very much! Try connecting the TX wireby bodhi - uBoot
toomyzoom, try: fw_setenv bootcmd 'run usb_bootcmd; run bootcmd_ubi; run bootcmd_pogo; reset'by bodhi - Debian
mindm49907, You can use UART booting to boot and then flash a known good uBoot for the NSA320: http://forum.doozan.com/read.php?3,7852,7852by bodhi - Debian
oakley470 Wrote: ------------------------------------------------------- > I guess it'd help if i could spell. :)) Thank you i am > booted back into debian now. So i think i have > given up on restoring the pogo since the last > attempt failed. With my current state of boot am i > pretty much just back at the begining of > installing linux? You can keep usinby bodhi - uBoot
@kuleszdl , Great works :) I wish WarheadsSE would give us some hints about flashing new kernel to NAND. That would be fantastic.by bodhi - uBoot
I think you have mispelled the variable, should be serverip. And yes you are right, don't do saveenv until after you can tftp and boot.by bodhi - uBoot