musselmanb, Sorry, I was posting from my phone and text got cut off! There is no real mount command for jffs2. I meant it seems the original kernel uImage and rootfs were written to NAND in jffs2. That's why you have successfully mounted the rootfs in Linux with mount -t jffs2 /dev/mtdblock2 command. This command was the correct one to run to boot back to stock. pogo_bootcmd=if fsloby bodhi - uBoot
musselmanb Wrote: ------------------------------------------------------- > bodhi, > > Thanks for your guide from your old post. I am > able to get usb to boot. It is nice to be able to > use the stock OS to troubleshoot failed to boot > thumb drive > > 1. fw_printenv output > > > # fw_printenv > ethact=egiga0 > bootdelay=3 > baudrateby bodhi - uBoot
Hi musselmanb, I was hoping to see some error when you mount it, but it looks like your mtd2 is good! how about get back to netconsole and try both: > ubi part rootfs > ubifsmount ubi0:rootfsby bodhi - uBoot
musselmanb, Yours is no longer a bad block problem. This ubi error is typical, i.e. after the Pogo E02 installation we all have this error. Booting with USB is never a problem, but to try booting back to stock Pogo OS is problematic because of this (there had been frequent postings about this issue). 1. Please stop your netconsole and print out your envs. And I'll take a look. > pby bodhi - uBoot
@Geo, I'm also having problem with a Sandisk microSDHC 16GB (with Sandisk adapter). It was not recognized by this uBoot. Debian was fine with it after boot.by bodhi - uBoot
Kernel 3.12.0-kirkwood-tld-3 package was uploaded. Please see 1st post for download link.by bodhi - Debian
Geo, I did not see anything peculiar other than the read errors. Have you tried to reformat the 16GB card? (ie. on Windows or Mac).by bodhi - uBoot
fma965 Wrote: ------------------------------------------------------- > how can i get the hdd led's working on the nsa320, > ide-trigger doesn't seem to work any more. There is so little info in your post so we have no way to know how help. What kernel you're using? what do you boot with (USB, HDD)…., what did you see before updating …..and any log file.by bodhi - Debian
Geo, Quoteboot the kernel and or ramdisk. The MMC driver in uBoot seems to have problem with some SD cards. Might be the timing setings was too short and it's timed out too quickly. Exactly what point did the block read error occurred? Did you mean during loading either one of the images? But once both were loaded, then it is OK? Do you still have the log or can recreate it? Iby bodhi - uBoot
That should work. But cost a lot more than one without the cover on eBay. They all come from China so it will take the same amount of time to get to where you are!by bodhi - Off-Topic
dinjo Wrote: ------------------------------------------------------- > Little off topic but why doesn't /var/log/messages > gets updated with any actions ? It's in the instruction in first post. syslogd logs to RAM.by bodhi - Debian
SOL, No, currently your bootcmd boot Archlinux but not Debian. This needs to be changed bootcmd_linux=setenv bootargs $(bootargs_linux); ide reset; ext2load ide 0:1 $(loadaddr) /uImage; bootm $(loadaddr) to something like this: bootcmd_linux=setenv bootargs $(bootargs_linux); ide reset; ext2load ide 0:1 $(loadaddr2) /uInitrd; ext2load ide 0:1 $(loadaddr) /uImage; bootm $(loadaddr) $by bodhi - Debian
@eas, Sure, will add zswap to the next update. I think it is a little more flexible than zram in that it can age out the pages to disk.by bodhi - Debian
SOL, IIRC, WarheadsSE said the NSA325 stock uBoot does not support netconsole (it is very limited). You will need to have a newer uBoot such as Davy's NSA320 uBoot to provide that. However, I'm not 100% sure if it boots the NSA325 (but my guess is very probably it does). Your best approach is to get serial console working. It is quite easy to do that for the NSA3xxx boxes, all theby bodhi - Debian
Hi Davy, Welcome back! hope the life gear has shifted into a happier and better times for you! -bodhiby bodhi - Debian
Right! Don't mess with uBoot envs. Best if you print out uBoot envs while in Arch Linux so that we can check if they are set to boot both Debian and Arch. fw_printenv The uBoot bootcmd env might have been set to boot Arch only. So if that's the case, it will need to change to boot Debian. It's all depending on the current uBoot settings, so we need to verify that. If netconsby bodhi - Debian
Thanks for the info ricke.by bodhi - Debian
SOL, See this thread for the latest Debian rootfs and instruction: http://forum.doozan.com/read.php?2,12096 After you created the rootfs USB stick and booted into Debian, install this kernel (instruction also in that thread). The current rootfs has kernel linux-3.12.0-kirkwood-tld-1.by bodhi - Debian
Sheman, Which port did you plug in the USB thumb? Have you tried the back port next to the Ethernet? Also, if trying different port did not wok, then try this: reboot, interrupt netconsole, and manuall run "usb start" a few times to see how many tries you need before it is successfuly started.by bodhi - uBoot
ricke Wrote: ------------------------------------------------------- > Is it possible to add ZRAM module to next kernel > release, iv used it in arch arm on low memory > devices. Otherwise kernel is working great on my > goflex home. Please try this and let me know if zRAM works for you in this kernel: http://forum.doozan.com/read.php?2,14188,14233#msg-14233 And also, pleaby bodhi - Debian
For the Dockstar top mini USB plug, this adapter works great: http://dx.com/p/usb-a-female-to-mini-usb-5-pin-female-adapter-26780by bodhi - Debian
I've uploaded an update for Kirkwood linux-3.12 for testing: added supports for Zyxel NSA325 and NSA310. For those who have the NSA325 and NSA310, and perhaps NSA320 also, please try this kernel and let me know if it works for you or there is any problem. If every thing goes well, I will update the main thread to include this deb package, along with the patch and headers. This tarballby bodhi - Debian
Andi, I'm regression testing with other plugs, and will upload it today or tomorrow.by bodhi - Debian
Cool! Glad it works well for you.by bodhi - Debian
GeorgeRosar, Your uBoot envs for bootargs were not setup correctly. alarm_args=setenv $boot_args_console root /dev/mmcblk0p1 rootwait rootfstype ext3 alarm_boot=ide reset alarm_mmc=mmc init; mmc init; ext2load mmc 0:1 0x800000 /boot/uImage; ext2load mmc 0:1 0x1100000 /boot/uInitrd; setenv device /dev/mmcblk0p1; run alarm_args; bootm 0x800000 0x1100000 arcNumber=2097 baudrate=115by bodhi - uBoot
ingmar_k, This is a very exciting development :) it is Debian right? did you cross compile or native? so we will just flash it in the same NAND partition and use Arch or stock uBoot?by bodhi - Debian
dinjo, What is you /etc/fstab looks like?by bodhi - Debian
SOL, I'll extract the patch and build it in the new kernel release and you can test it!by bodhi - Debian
Tommes, Indeed, you are running the GoFlex Net as the Referrence Board. Meaning it runs as a Sheeva Plug. This is needed because you're running Kirkwood kernel from mainline. So after you've installed my kernel 3.12 or davy's 3.3.2, you can change the uBoot env arcNumber to the correct one. But before changing any uBoot env, make sure the new kernel is running, and set up neby bodhi - Debian
Hi Mark, I forgot :) I've already uploaded kernel 3.2.28 back in March. Try this and see if it has what you need. http://forum.doozan.com/read.php?2,11601,11601#msg-11601by bodhi - Debian