There is an interessting discussion about flash memory wear out of SD cards with RaspberryPi: Link.. They recommend to use the fstrim command so that unused blocks become available for wear leveling. It seams that there might be USB3.0 sticks available which support trim: Link. With the tool TRIMcheck it can be tested if a drive supports trim: Link. If you have a Windows PC where you know thatby shv - Debian
Maybe a flash stick with SLC flash cells is recommended even it is more expensive. Some additional hints need to be regarded. It is more or less the same as for SSD usage. To prevent wear out of certain flash areas only one partition over the complete Flash memory shall be used. The partition shall be aligned to the Flash sectors. I don't know how to find out the right alignment for Flash stby shv - Debian
I was able to compile the kernel. But to test it with the old uboot I had to set an option (CONFIG_ARM_APPENDED_DTB) and concatenate uImage and dtb file. Becase navym already provided such uImage I tested navyms kernel. The read performance is at maximum (80MB/s) but the write performance is just half of the performance of the 2.6.31.6 kernel (35MB/s). I compiled the kernel on Ubuntu with Linaby shv - uBoot
The WarheadsSE SATA initialization script does the following: #!/bin/sh # uncomment line below and set to the correct disk disk=/dev/sdb if [ -z "${disk}" ] ; then echo "You must uncomment/set the 'disk' variable" exit -1 fi workarea="." stage1File=$workarea/stage1.wrapped ubootFile=$workarea/u-boot.wrapped kernelFile=$workarea/uIby shv - uBoot
I want to try it but I don't know how to get the new uboot and FDT kernel onto my SATA disk. What kernel option must be changed to build a non-FDT kernel? Such kernel I could boot with the old uboot. Or I could wait until you will find a way how to load the new uboot and FDT-kernel.by shv - uBoot
see: http://archlinuxarm.org/forum/viewtopic.php?f=55&t=6193 - shvby shv - uBoot
OpenWRT is just another OS. Therefore I would expect that booting from IDE can also be used with it. The command setenv usb_root LABEL=rootfs is used for USB booting to indicate which partition shall be used for booting. It is not really necessary for booting from IDE.by shv - uBoot
What programs did you plan to install on the device to serve as an audio streamer?by shv - Debian
I think that the driver which is contained in the kernel doesn't work (with your device). At least something seams to be wrong. If you compare it to my lsmod listing below you can see that modules are missing which depend from snd_page_alloc and this is the module which produces the pci... error messages in your case. snd_usb_audio 83544 0 snd_pcm 69796 1 snd_by shv - Debian
Depmod -a just registers available kernel modules. Reboot afterwards and check with dmesg if pci messages are still there and with lsmod which modules were loaded.by shv - Debian
Did you execute the command depmod -a? Do you still have the other messages? [ 122.830000] snd_page_alloc: Unknown symbol pci_set_consistent_dma_mask [ 122.830000] snd_page_alloc: Unknown symbol pci_dev_put [ 122.840000] snd_page_alloc: Unknown symbol pci_get_device [ 122.850000] snd_page_alloc: Unknown symbol pci_set_dma_maskby shv - Debian
NonPCI modules: http://clz.to/o6xaagr2by shv - Debian
The sound driver are not fully working (see snd_page_alloc messages)! Maybe the kernel don't support your specific device. Currently you have a non PCI uImage but modules which are compiled for PCI. This normally works well. If I have time I will provide you a module package which is completely compiled for Non-PCI. If this doesn't work the only way is to compile the driver for your souby shv - Debian
You should extract my kernel package in the root folder of varkey's debian rootfs. You might need to install the mtd-utils package if this is not yet available in varkey's rootfs. Afterwards you should execute the two commands to flash the new uImage into the NAND flash. If everything is OK reboot the device.by shv - Debian
The package from the 2nd post just contains the uImage for the Pro. The package from the 8th post contains both uImages. Everything else is the same.by shv - Debian
The file update-kernel.sh is part of the ALARM kernel update package. You should use the flashing commands after you made sure that they are the same as in update-kernel.sh script. You should use the uImage which is contained in my kernal package.by shv - Debian
It might be recommended to use ext3 instead of ext2 for the rootfs. usb_rootfstype=ext3 In case you wan't to boot from SATA drive you could try this: fw_setenv arcNumber 3089 fw_setenv usb_init 'run usb_scan; setenv usb_root LABEL=rootfs' fw_setenv ide_scan 'ide_scan_done=0;for scan in $ide_scan_list; do run ide_scan_$scan; if test $ide_scan_done -eq 0 && ext2lby shv - uBoot
You can take the same commands from the ALARM kernel updater package (http://archlinuxarm.org/forum/viewtopic.php?f=55&t=2453) but use my kernel instead. You might need to install the mtd-utils package to flash the right uImage to the flash. Just unpack the archive in your root folder. For B04 you must flash the NonPCI uImage.P21. You don't need to copy or move the old kernel modules toby shv - Debian
I want to export the drives if they are switched on after booting the device. But it can also occure that they are already up and running during the startup and this caused the problem. How can I reexport them without a restart of nfs-kernel-server?by shv - Debian
I think I found already something about activation of netconsole logging after the kernel was stared here in this forum. But these recommendations didn't work form me. Can someone explain how to do this? I think I just find something which I didn't try yet: http://forum.doozan.com/read.php?2,9522,9713by shv - Debian
I wouldn't recommend you to compile the modules your own because you need some experience how to do this. It is not so easy to compile modules which fit to the kernel. You need the right source files (from WarheadsSE git) and right configuration file (I don't know where to get it for the older kernel). There are several problems with the ALARM kernel which can not be resolved even wiby shv - Debian
I use "usb reset; usb start;" once. Do you think it could help to put "usb start" as first option in "preboot" before the neconsole part?by shv - uBoot
It doesn't solve the problem while scanning of USB devices: scanning usb for storage devices... EHCI timed out on TD - token=0x82008d80 EHCI timed out on TD - token=0x1f8c80 EHCI timed out on TD - token=0x1f8c80 ...by shv - uBoot
I am using an udev configuration which restarts the nfs-kernel-server after disks are mounted. Now I got a problem that this stops the system startup. Synthesizing the initial hotplug events...done. Waiting for /dev to be fully populated...[ 39.464422] EXT4-fs (sdb1): Ignoring deprecated nobh option [ 40.050294] EXT4-fs (sdb1): barriers disabled [ 40.148387] EXT4-fs (sdb1): mounted fiby shv - Debian
Isn't definition of ide_root_label is missing? ide_root_label=rootfsby shv - Debian
Please check first if the partition name is "rootfs". If it doesn't boot you might have the latest kernel of WarheadsSE. In this case you could try my Debian rootfs which fits to that kernel: Link. You should install the resolvconf package if it is running to prevent problems with DNS configuration if DHCP is used. If you can login to the Pogoplug but don't have access to theby shv - uBoot
I tried UART booting but it doesn't work. Later I found out that my device has a BootROM version 1.11 so that I can't use UART booting with it.by shv - Debian
My Goflex Net device has a BootROM version 1.11. So I can't use kwboot. -shvby shv - uBoot
Booting is not the main problem because I can set priority to boot from SATA disk. The main problem is that the harddisks behind the USB Hub are not working stable. With the Pogoplug Pro this is working well. I've bought a new Goflex Net and get the same problems while booting from USB stick which is connected together with some harddisks to a USB hub. I didn't try to boot from SATAby shv - Debian
Can you please provide the patch files for your changes to the Medion/Zyxel sources?by shv - uBoot