velo, From your post I guess you don't have serial console. This is most likely problem with mounting rootfs, and there is no way we can see it in netconsole. Usually the pre-built rootfs has a default root device, and that is most likely /dev/sda1. Therefore you would have no problem with booting with USB. What you can try is put my Debian rootfs on the SD card. And be sure to labelby bodhi - uBoot
bodhi Wrote: ------------------------------------------------------- > @WarheadsSE, > > Perhaps I looked at the wrong tree, but could not > find any xce module! here is where I searched: > https://github.com/WarheadsSE/OX820-2.6-linux > > Do you remember the file name, by any chance? Nvm! I found a better way to implement the LED sequence.by bodhi - uBoot
bodhi Wrote: ------------------------------------------------------- > @WarheadsSE, > > Perhaps I looked at the wrong tree, but could not > find any xce module! here is where I searched: > https://github.com/WarheadsSE/OX820-2.6-linux > > Do you remember the file name, by any chance? How about these? is the CE bootled.c the one they used in stock u-boot? /OX82by bodhi - uBoot
@WarheadsSE, Perhaps I looked at the wrong tree, but could not find any xce module! here is where I searched: https://github.com/WarheadsSE/OX820-2.6-linux Do you remember the file name, by any chance?by bodhi - uBoot
tilator, See this post: http://forum.doozan.com/read.php?2,12096,15970#msg-15970 Perhaps it will help to look at Kurlon's example I mentioned in the post.by bodhi - uBoot
davidedg, Regarding FDT kernel, the kernel DTS is not difficult to build. However, it's a non-trivial task. Take time to code and test. I actually built one for GoFlex Home as an exercise, but have not tested it because the time I estimated it would take to spend on the whole process (and then have forgotten all about it :-). I used Kurlon example and tutorial. Kurlon did an excellent jobby bodhi - Debian
@davidedg, > - If I want to compile my own 3.14.2 kernel, should I apply bodhi's patch to vanilla sources as a starting point? Yes. > - Since there is still no .dts file in mainline kernel, does it mean that no FDT Kernel can actually be built ? True. You'll have to find the NSA325 dts or create one. > - Why bodhi's patches do not get applied to mainline kernel?by bodhi - Debian
chessplayer, The clue here is May 2 01:07:32 3.14.0-VDR user.debug vdr: [3552] found 0 locales in /usr/share/locale It seems to indicate that the locale on that 3.14.0-tld-2 system was not properly installed somehow. Because if you follow the standard procedure during installation then /usr/share/locale should have locales.by bodhi - Debian
@ingmar_k, I know you're not actively working on this plug :) but just a quick question since you've probably learned a lot about the new U-Boot already. What do you think about kref's U-Boot that can be improved? So far as I can tell, the NAND version is pretty solid. I added the pinmux calls to control the LEDs and it works well (currently I just turn it Orange while U-Boot isby bodhi - uBoot
Almaz, There is really no need to run the latest kernel, unless you want to try new features in 3.13 or 3.14. See LinuxChanges log for new features such as zram, zswap (relevant to memory constraint plug computers). The most important upgrade is security related upgrade, where you just do apt-get update apt-get upgrade to get the latest security patches or do apt-get upgrade openby bodhi - Debian
narddawg314 Wrote: ------------------------------------------------------- > > echo "0 0 0" > /sys/class/scsi_host/host0/scan > > returns nothing and I've rebooted with the drive > attached but nothing either. Should I format as > ext3? It's not relevant whether it's FAT/Ext2/Ex3/Ext4. In this situation, I'd look at dmesg output firstby bodhi - Debian
Hi chessplayer, It seems you don't have any locale in your new 3.14.0-tld-2 rootfs (kernel does not have any locale specific stuff). If locales was not installed, or has not been generated (I don't know if you had done this, so stating here for reference): apt-get install locales Check to see if your locale is in the file (my locale is US). And then edit this file locale.gen to unby bodhi - Debian
Ah, I remember that module. Yes, I've started browsing your 2.6.31 tree for clues :)by bodhi - uBoot
SPuntte, Must do this as root user: echo none > /sys/class/leds/nsa325\:orange\:sys/trigger So try to execute these at command line and see if it works. Please let me know if you still see ide-disk2 problem. echo ide-disk1 > /sys/class/leds/nsa325\:green\:hdd1/trigger echo ide-disk2 > /sys/class/leds/nsa325\:green\:hdd2/trigger And it does not have anything to do with theby bodhi - Debian
tilator, Glad I could answer some of your questions. Even though I have this plug for a long time, I lost interested in it after successfully getting Debian squeeze rootfs running with ALARM kernel. I have only recently started playing with it again upon learning of kref's works to get it running later u-boot and kernel. Let us know your progress.by bodhi - uBoot
narddawg314, Now that you can boot with the thumb drive, you should plug the HDD plug in before powering up. Although I've suggested to plug it in after, that was for troubleshooting purpose. The HDD should be in the SATA slot during booting. And watch your serial console or netconsole to capture the log if anything strange going on.by bodhi - Debian
I'm looking for the Oxnas source code where the LED blinking is controlled (low level stuff, e.g. GPIO ). Anybody happen to have it or can point me to the source? In U-Boot, during booting I can turn on the LED to Green, Orange (Blue by itself does not seem to work) . But can't find the setting to make it blinked! Thanks,by bodhi - uBoot
tilator, Look for the SATA driver in kernel drivers/ata. If number of ports is defined/hardcoded, it should be in there.by bodhi - uBoot
OK. So you're not running the version out of kref's source tree, you have patched it. Regarding this: sata@45900000 { compatible = "plxtech,nas782x-sata"; /* port sgdma core */ reg = <0x45900000 0x100>, <0x459B0000 0x10>, <0x459E0000 0x2000>, /* phy descriptors (optional) */ <0x44900000 0x0C>, <0x50000000 0x1000>; interrupts =by bodhi - uBoot
tilator, I already found out myself that uboot had only one SATAdevise set on and it needed to be changed I'm afraid you're confusing me :) the U-Boot 2013.10 that you've installed recognized both SATAs as you showed above.by bodhi - uBoot
Or this linux-oxnas-3.12-tld-2/arch/arm/boot/dts/ox820-pogoplug-pro.dts sata@45900000 { status = "okay"; nr-ports = <2>; }; The idea is just cloning the first SATA port, whatever definition that needs to be cloned. If you can't find any thing else related to SATA 1 in the kernel dts, then that's all you would need. Try both and see if yby bodhi - uBoot
You can use the oxnas kernel dts file as a base and clone the second SATA port from there. So whatever is needed in the kernel dts for SATA 1 entry, you would replicate that. If there is hardware specific info such as addresses, then you can find it in those 2 files. linux-oxnas-3.12-tld-2/arch/arm/boot/dts/ox820-pogoplug-pro.dts sata@45900000 { status = "okay"; };by bodhi - uBoot
Take a look at: u-boot-oxnas-oxnas/drivers/block/plxsata_ide.c and also: arch/arm/include/asm/arch-nas782x/hardware.h Everything you need is in there, I think.by bodhi - uBoot
tilator, > I ask it here since uBoot find both sata devices. Which U-Boot version did you see both SATA?by bodhi - uBoot
I've uploaded the latest version for linux_logo: Download at dropbox: linux_logo md5: fbbf949b21fbf6829a8f28edd24637abby bodhi - Debian
Hi chessplayer, Ah! it's explainable. I compiled the program, but did not install it. I ran the binary in the build directory, and also tried both the binary and Debian logo on the Pogo Pro (2 CPUs). ./linux_logo -D ./logos/distributions/debian.logo I think when you run it like I did, you have specify where the logo image is. Hopefully, when you put it in your standard installation dirby bodhi - Debian
I'm going to bed now :)) you won't hear from me for another 10 hours :)by bodhi - Debian
Hi chessplayer, Here is the patched linux_logo. md5: 7ae1817502a0246e49616d07e6df4e8c Run this on your boxes and let me know what you see :) if you see no problem with it, you can replace this binary where it is installed (e.g. usr/local or where you've defined it).by bodhi - Debian
That's not necessarily true. You can boot with uImage and uInitrd if booting Debian kernel. So I would change the bootcmd_usb to either: boot only with uImage setenv bootcmd_usb 'usb reset; run usb_scan; run make_usb_bootargs; ext2load usb $(usb_device) 0x40000 /boot/uImage; bootm 0x40000 or to boot with uInitrd setenv bootcmd_usb 'usb reset; run usb_scan; run make_usb_booby bodhi - Debian