letsjam1984, How did you back up your current USB rootfs? The error seems to indicate that the file system is Ext4. ** ext4fs_devread read error - block And your u-boot env is set to Ext3 usb_rootfstype=ext3 So if your rootfs was Ext4, then format a new USB drive as Ext4, and then restore it. Change the usbrootfs_type to ext4 in netconsole: setenv usb_rootfstype ext4 OTOH, ifby bodhi - Debian
Berryshake, Notice how this U-boot version detected your SD card: Loading file "/boot/uImage" from mmc device 0:1 (xxa1) and your usb_root is usb_root=/dev/sda1 To ensure that the rootfs is found by initrd regardless of the drive letter of the card, use the rootfs label approach: http://forum.doozan.com/read.php?3,8044,8152#msg-8152by bodhi - Debian
@velo, The Pogo Pro is similar to other plugs only after you've installed latest U-Boot and kernel. For other "legacy" installations, it is quite different. See the Requirements section in the Pogo V3 U-boot thread: http://forum.doozan.com/read.php?3,16017 @Maddy, So without describing what and how you have installed installed in details (dmesg, log,…everything you hadby bodhi - Debian
@Greg, Perhaps something in your local network/serial confiuration that has indirectly caused this reboot issue, as davidedg mentioned above? the basic rootfs is working without this problem, therefore the kernel is working fine.by bodhi - Debian
Thanks Davide, I did not realize you've updated your post until now :) Was that with the basic rootfs? Update: I recognized that this was with the basic rootfs, Thanks!by bodhi - Debian
gabor, add CONFIG_PM obj-$(CONFIG_PM) += pm.o to /usr/src/linux-3.14/arch/arm/mach-kirkwood/Makefile Then do make oldconfig to select it.by bodhi - Debian
Looker, > Can I use a USB stick from another working pogo > E02 with Archlinux up and working great or does it > need to be an stick dedicated to this box? > > Thank you That stick can be used on any Pogo E02. Settings need to change or match: 1. MAC address needs to macth this PogoE02: - look in Arch network interfaces, if it is defined (I recall it is) - that MACby bodhi - uBoot
@Looker You got it. The first = means "asign the entire string that appears after the = symbol to mtdparts variable". Any = symbol that appears in the string means a literal =, not an assignment. Regarding ippaddr and serverip, you can keep them like this (later when you get to know how to use them, they should be changed to conform to your local network): ipaddr=192.168.0.221by bodhi - uBoot
Davide & Greg, Perhaps you can try to put my basic roofts Debian-3.14.0-kirkwood-tld-1 on a stick, and boot it to see if the problem is the same?by bodhi - Debian
theliquid, TUN It is not included in the current config, and I could build a new version to include it. But I'm about to be on the road for a while, so probably about late next month is when I can test and release.by bodhi - Debian
Yes. When you reboot they will be gone. The idea is not to save the envs until after you have successfully booted into Debian. Just to avoid mistake in typos. However, you can save them in serial console, too, if you're sure that the envs were entered correctly. Given you have serial console, it's Ok to save ithem now with u-boot command: >> saveenv Just be careful not to exeby bodhi - uBoot
Yes, anything greater than 1.0.1e-2+deb7u6 is safe from Heartbleed... otoh, I think it's good to update to the latest openssl version whenever there is a security update for it.by bodhi - Debian
Yes, with a serial console. Info here: http://forum.doozan.com/read.php?8,13263 Download the latest U-Boot and kwboot: http://forum.doozan.com/read.php?3,12381 Then Boot with UART as instructed: http://forum.doozan.com/read.php?3,7852,7852by bodhi - uBoot
DavideDG, I was not sure. But when I looked at my .config in the build directory, the Sensors NSAxx was removed (accidentally) somehow. So I just want to make sure that people who uses the NSAxx don't run into problem. But you're right, the released kernel config was OK. I looked at what actually installed in /boot and saw the diff was exactly what you saw. But in any case, the chby bodhi - Debian
FYI I've removed kernel linux-3.14.0-kirkwood-tld-2 temporarily. If you have the NSAxxx then please use kernel linux-3.14.0-kirkwood-tld-1. If you're running kernel linux-3.14.0-kirkwood-tld-2 on other boxes then there is no need to downgrade.by bodhi - Debian
@Greg, Please try kernel 3.14.0-kirkwood-tld-1. Apparently, I've screwed up :) with kernel 3.14.0-kirkwood-tld-2 regarding the NSAxx sensors. Sorry about that, must have been a latenight :) I'll release kernel 3.14.x-kirkwood-tld-3 when I have time to do it.by bodhi - Debian
FYI, There are some bug fixes and added features in u-boot-2014.04 that I think eventually some of us will run into or need. So I plan to rebase u-boot-kirkwood to 2014.04. I think I will have time to do this about 4 weeks from now.by bodhi - uBoot
@WarheadsSE & Greg, I'll have to look at the patch/config. I don't recall my patch set changed at all in the first release 3.14.0-kirkwood-tld-1. However, I've added quite a bit more in 3.14.0-kirkwood-tld-2 for pbg4's DVB patch and other minor things. @Greg, did you try 3.14.0-kirkwood-tld-1 kernel? or just 3.14.0-kirkwood-tld-2? Update: Looks like I was wrongby bodhi - Debian
Yes, usb_rootfstype needs to macth the file system type of your rootfs. OTOH, with later kernel (don't remember when it's been possible), you can also obmit this variable altogether and initrd will figure out the file system type. So either matching the type, or don't define it in U-Boot env.by bodhi - uBoot
gabor , Yes. That was intentional. I did not include the PM option because most people running these plugs as NAS (where only the HDD sleeps), and some running RAIDs (where PM would potentially causes big problem). I'm not sure how many modules you will need to do this. But you could try to compile them using the kernel headers. I would compile new kernel to include this feature, ifby bodhi - Debian
Maddy, You did not give enough info for us to help you. How did you install Debian? Now I formatted new USB drive to install debian there are many different ways to do this for the Pogo Pro!by bodhi - Debian
Jeffy, Please post your output of dmesg. And also which slot (left/right) did you plug in the hard drive? which u-boot version do you have on the GF Net?by bodhi - Debian
Greg, Usually netconsole will give you lot of kernel messages, but not everything. So serial console is needed to troubleshoot problem like this. And also if you're running stock U-Boot, I don't recall if netconsole is availale either. The NSAxx series is quite easy to hook up serial console.by bodhi - Debian
theliquid, Yes, the latest Dockstar U-Boot one should work fine.by bodhi - uBoot
effendi, - Which U-Boot and kernel was you running on this Pogo before installing the new kernel? - Did you follow the instruction to set up U-Boot envs? This section: - Setup U-Boot envs: Disclaimer: The following U-Boot envs settings are recommendation only. If you don't have serial console connected, please do not attempt. Be aware that changing U-Boot env settings to the wrongby bodhi - Debian
Awesome! Note in booting multiple USB/SATA. If only one partition is labeled rootfs, then it will be found correctly. And it does not matter how many devices that contain Debian installation . But if more than one partition are labeled rootfs then you might run into the situation when the kernel uImage and uInitrd from one partition, but the actual rootfs is from another! In this situation, tby bodhi - Debian
theliquid, Yes, it should work fine. Your arcNumber is 2998 which is the Dockstar's. And that what's Jeff's script set to during installation. But as always, pls backup your kernel files or the rootfs before installing the kernel.by bodhi - Debian
Excellent! Thanks for testing it.by bodhi - Debian
Hi theliquid, Cool! so the classic DTB works fine after you've replaced it? I would like to include that fact in the 1st post.by bodhi - Debian
theliquid, It should work for the Pogo V1. But you should back up your rootfs before trying it. The archNumber should be set to 2097 to boot it. And as always, make sure you have serial console or netconsole connected before changing arcNumber. If you want to be extra careful, then list the V1 dmesg output and/or U-Boot boot log here so we can verify. EDIT: I believe arcNumber 2998 shoby bodhi - Debian