ext3 should have a better chance to survive from power failure than a ext2 file system, fsck the rootfs by connect the USB stick to other machine should able to fix the problems in most of the cases.by sluk - Debian
physis Wrote: ------------------------------------------------------- > but there is no such module in Gorgone's > /lib/modules/2.6.35.7-dockstar/kernel/fs/ > > Did I miss something ? It mean Gorgone's kernel did not compiled with XFS support.by sluk - Debian
Yes... log_action_msg "Will now halt" halt -d -f $netdown $poweroff $hddown echo none > /sys/class/leds/dockstar:green:health/trigger } Looks to me the "halt" command is not execute /etc/init.d/halt, cannot see the message "Will now halt", instead: root@debian:/etc# halt Broadcast message from root@debian (pts/0) (Mon Janby sluk - Debian
gorgone Wrote: ------------------------------------------------------- > add this line > > echo none > > /sys/class/leds/dockstar\:green\:health/trigger > > under > > log_action_msg "Will now halt" > halt -d -f $netdown $poweroff $hddown > > in /etc/init.d/halt > this shows u when it is safe to remove disks and > power cableby sluk - Debian
compcache package is not required for kernel 2.6.37, just need to have CONFIG_ZRAM=m in .config Below are steps required to create the compressed RAM based block device and use it as swap space: root@debian:~# modprobe zram root@debian:~# ls -l /dev/zram* brw-rw---- 1 root disk 254, 0 Jan 21 11:42 /dev/zram0 root@debian:~# cat /sys/block/zram0/disksize 0 # Create a 40MB RAM disk root@by sluk - Debian
May need CONFIG_ZRAM=m and CONFIG_ZRAM_STATS=y in kernel configuration and re-compile, I will take a look later today...by sluk - Debian
John Doe Wrote: ------------------------------------------------------- > the scripts chainload a backup > copy of the original boot loader which then > executes the original boot parameters which still > reside in a part of mtd0 that isn't overwritten by > the new boot loader. 1) Size of the stock U-Boot and Jeff U-Boot are both 512KBytes. 2) The first 512KBytes weby sluk - Debian
@ingmar_k, already tried, I don't think procedures in this link are applicable to 2.6.37. Maybe what we need is updated initramfs-tools...by sluk - Debian
kraqh3d Wrote: ------------------------------------------------------- > Hey thanks for the reply. So the new uBoot chain > loads a copy of the old uBoot if it can't find a > root file system on /dev/sda1? If I remove my > boot /dev/sda flash drive, will the system boot > back into Pogoplug or is this just a fallback > during the installation? The original U-Bby sluk - Debian
ingmar_k Wrote: ------------------------------------------------------- > Just had a look and it seems that the compcache > kernel patch is already included in kernel 2.6.37 > sources. Anyone already using that kernel with > compcache? How to enable? I can give it a test...by sluk - Debian
StefanV3 Wrote: > the path for the ornage led has been changed from > > /sys/class/leds/dockstar\:orange\:misc (old) > > to > > /sys/class/leds/dockstar\:orange\:health (new) Really? I found it still in /sys/class/leds/dockstar:orange:misc while booting from the vanilla kernel.by sluk - Debian
@gorgone, my apology... 2.6.37 kernel unable to recognize the correct board type was due to I forgot to "saveenv" after changing the arcNumber to 2998 in uBoot. After done that and "reset" to reboot everything detected correctly now. So confirmed, no patch is required for compile the latest vanilla kernel for DockStar! Linux version 2.6.37-dockstar (samson@ubutuvm1004)by sluk - Debian
gorgone Wrote: ------------------------------------------------------- > @sluk > nice ... > if all OK be happy :-) but as you mentioned, the kernel cannot recognize the board correctly: Machine: Marvell SheevaPlug Reference Board Registered led device: plug:green:health Could you post your patches on 2.6.37?by sluk - Debian
gorgone Wrote: ------------------------------------------------------- > the default dockstar config from the orginal > 2.6.37 not work very well > wrong cpu detect on my dockstar !!!!! so i patch > it again Could you show your dmesg output? I compiled 2.6.37 without any patch seems ok: root@debian:~# dmesg [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000]by sluk - Debian
Just complied 2.6.37 with Codesourcery 2010q1 crosstool under Ubuntu (tried without apply any patch): dpkg-deb: building package `linux-image-2.6.37-dockstar' in `../linux-image-2.6.37-dockstar_1.1_armel.deb'. Will see if it works and get back...by sluk - Debian
By analysis Jeff's install_uboot_mtd0.sh you need a flash_erase before you can nandwrite, also the input image to be used by nandwrite should be generated by "nanddupm -nof" but NOT "nanddupm -nf": I have construct the following procedures to restore mtd1-2 (NOT TESTED USE IT AS YOUR OWN RISK!!!): # Erase the full 4MBytes of mtd1 flash_erase /dev/mtd1 0 20 # Restoby sluk - Debian
kultex Wrote: ------------------------------------------------------- > Second - googeling the dockstar I found the hint - > http://mein.homelinux.com/wiki/dockstar:installati > onsanleitung_debian the above guide mentioned a wrong method to backup the NAND: dd if=/dev/mtd0 of=mtd0.img ... ... Jeff mentioned: QuoteJeff To create an image of mtd0, you need to dump theby sluk - Debian
I would like to know Gorgone's previous post dockstarpatchfiles_2.6.35.4.zip can be applied to the current 2.6.35.7 source? Do we still need apply patches for current latest 2.6.37 kernel to get DockStar LED support?by sluk - Debian