Patches to support the dockstar (basically: machine ID and LEDs) were merged into the linux-2.6-stable tree at kernel.org recently.by ecc - Debian
I don't understand this either. I suggest posting to debian-arm@lists.debian.org, which should reach the maintainers of flash-kernel, as well as other knowledgeable people.by ecc - Debian
_Oscar_ Wrote: ------------------------------------------------------- > Maybe it would be better to tune apt somewhere to run flash-kernel like lilo after an kernel update The flash-kernel NEWS file says that it is called automatically by update-initramfs, so that should already happen.by ecc - Debian
paketecuento Wrote: ------------------------------------------------------- > The serial cable showed that my Iconnect is completely bricked!!! > no data at all when bootin...so I think it's time to JTAG I think it's more likely that your serial cable isn't connected correctly. I don't have an iConnect, but these pages seem to have a lot of useful information: hby ecc - Debian
DockstarPBX Wrote: ------------------------------------------------------- > I did a search of "TEXT_BASE", it didn't seem "TEXT_BASE" was used for "Marvell" or "sheevaplug" > in uboot source code. See arch/arm/cpu/arm926ejs/start.S and Makefile.by ecc - uBoot
naugtur Wrote: ------------------------------------------------------- > I wish you (or anybody) could tell me where to look for info on what I'm missing in uBoot. I can't tell you exactly what the environment variables should be, since I don't use that setup. But if you interrupt the u-boot sequence and do "printenv", you can compare the settings with those postby ecc - Debian
naugtur Wrote: ------------------------------------------------------- > I saw error messages about uBoot flashing and I would like someone to look at it and tell me if it > went ok or not before I reboot. The errors were about the u-boot environment settings. But the u-boot installation itself ("Writing data to block 0 .. 3") was successful, so it's safe to reboot.by ecc - Debian
ygator Wrote: ------------------------------------------------------- > I just git the latest uboot and did not patch anything. > [...] > It did not compile. It blew up trying to compile arch/arm/lib/board.c. > So the original source does not even clean compile. > > I use the git command Jeff posted in compiling u-boot. > git clone git://git.denx.de/u-boot.git u-booby ecc - uBoot
bandan Wrote: ------------------------------------------------------- > I've got one question, does the built in nand support wear leveling? No. > If not, wouldn't it make sense to use a filesystem designed for flash devices? jffs or somthing like that? That's why Jeff's recovery system, and the installation of Debian on internal NAND, use ubifs. Ubifs was deby ecc - Rescue System
How to specify your swap partition using a UUID: 1. Determine the UUID of your swap partition. Assuming it's on /dev/sda2 (check /proc/swaps to make sure): # blkid /dev/sda2 /dev/sda2: UUID="long-string-of-hex-digits" 2. Change the swap line in your /etc/fstab file to be: UUID=long-string-of-hex-digits none swap sw 3. Check that it works by doing: # swapoff -a # swby ecc - uBoot
I use this script to back up my dockstar to a fileserver, but it should work fine to a USB disk too: #!/bin/sh -e mountpoint /mnt/backup rsync -vax --delete / /mnt/backupby ecc - Debian
ayrlander Wrote: ------------------------------------------------------- > Question: any time the vmlinuz file or the initrd file get updated, should we run > these commands from the install script? > [...] Yes (as long as you have a fallback -- like Jeff's recovery system -- in case the new kernel doesn't boot). That should be all you need if you have u-boot reading theby ecc - Debian
DockstarPBX Wrote: ------------------------------------------------------- > Actually I' m trying to find out if it's possible to boot from network > every time without using external UBS drive or internal NAND flash. > Is it possible to run Openwrt on SDRAM without external USB or internal NAND flash? Yes, this is possible. You just need to set bootcmd to execute the aby ecc - uBoot
Max Wrote: ------------------------------------------------------- > To me it seems like uBoot doesn't support the ext4 fs, since it can't get the kernel from /boot. That's correct; there's no ext4 support in u-boot, just ext2. (Booting from ext3 also works because it's backwards-compatible.) So you'll need to load the kernel uImage from somewhere else: eby ecc - Debian
dinlaca Wrote: ------------------------------------------------------- > As far as additional steps I need to undertake (and please correct/add to what I list below): > 1. Install serial port on Dockstar (as described here: > http://www.yourwarrantyisvoid.com/2010/07/21/seagate-dockstar-add-an-accessible-serial-port/). > I will need to mod my serial cable as well (as described aby ecc - Debian
DockstarPBX Wrote: ------------------------------------------------------- > I have downloaded openwrt-kirkwood-uImage and openwrt-kirkwood-rootfs.tgz, > > I can load uImage using "tftpboot 0x800000 openwrt-uImage" > and load root-fs using "tftpboot 0x1100000 openwrt-rootfs.tgz". The openwrt-rootfs.tgz file is a tarball, not a ramdisk (initrd). Where dby ecc - uBoot
iceone Wrote: ------------------------------------------------------- > Additionally I noticed that there is an arm-linux-gnueabi-gcc compiler installed, > but there are no binutils for the platform. That does seem suspicious. Make sure you can at least compile and run a "hello world" program before trying a kernel. > What do I have to do, to compile a kernel moduleby ecc - Debian
DockstarPBX Wrote: ------------------------------------------------------- > If I want to boot your re-built Openwrt uImage and root-fs, what should I do from serial console? First of all, I'd suggest using the "official" dockstar images that are now built by the openwrt project, not my old ones. To netboot the dockstar: Put the kernel uImage on a TFTP server. Connecby ecc - uBoot
DockstarPBX Wrote: ------------------------------------------------------- > I'm wandering if it's possible to configure Jeff's U-boot to boot from network to Debian > or Openwrt or Pogolug Linux. Sure; even the factory-installed u-boot can do that, using the "tftpboot" command.by ecc - uBoot
yeshwenth Wrote: ------------------------------------------------------- > will this work > # dpkg -install --force-architecture zenoss-stack_3.0.2_i386.deb No. The i386 deb contains binary programs in x86 machine language. The DockStar uses an ARM CPU. It can only run ARM machine language. Once more: you'll have to recompile it from source if you want to run it on the DockStaby ecc - Debian
yeshwenth Wrote: ------------------------------------------------------- > root@debian:~# dpkg --install zenoss-stack_3.0.2_i386.deb The "i386" (and the dpkg error message) indicates this is a binary package for an x86 machine. You need a *_armel.deb package. There doesn't appear to be one on the zenoss site, so you'll have to (cross-)compile it yourself.by ecc - Debian
I like having my kernel and initrd in /boot on a single ubifs partition, rather than in a dedicated uImage partition. But since u-boot doesn't handle ubifs recovery, the system won't boot if it was powered off when the filesystem was dirty. Jeff's recovery partition can certainly handle this situation (and many others), but I found a very lightweight workaround -- just for thisby ecc - uBoot
Cyrrel Wrote: ------------------------------------------------------- > So, after manually starting an apt-get upgrade/update today, > I can see that there is a new Kernel available (inux-image-2.6.32-5-kirkwood) > Is it okay to install it out of the box? Or is there anything I have to check / do first? Currently, installing it won't do anything for you except waste space.by ecc - Debian
Fritz Wrote: ------------------------------------------------------- > doesn't rsync use an md4/md5 checksumming to compare files existing on both ends allready? No -- see "man rsync": Rsync finds files that need to be transferred using a "quick check" algorithm (by default) that looks for files that have changed in size or in last-modified time.by ecc - Debian
I did submit a patch upstream (see here and here). The duplication of code among all the Kirkwood variants seems to be the way the u-boot and linux kernel developers prefer it -- separate files rather than #ifdefs. I don't particularly like it either. But getting the basic support into the main tree is more important than the cleanup/consolidation, which could come later.by ecc - uBoot
Ultrazauberer Wrote: ------------------------------------------------------- > debian:~$ cat /etc/apt/sources.list > deb http://ftp.de.debian.org/debian squeeze main > > debian:~$ apt-cache policy dpkg > dpkg: > Installed: 1.15.7.2 > Candidate: 1.15.8.4 > Version table: > 1.15.8.4 0 > 500 http://ftp.de.debian.org squeeze/main > Packby ecc - Debian
Ultrazauberer Wrote: ------------------------------------------------------- > dpkg: warning: 'update-rc.d' not found in PATH or not executable. Are you mixing emdebian and debian sources in your /etc/apt/sources.list? I think embdebian doesn't require Perl at all, so it works around some standard Debian utilities. I suspect you are now running the regular Debian versionby ecc - Debian
I installed the package busybox-syslogd on my DockStar. It provides a very lightweight syslog built into busybox. It doesn't write to /var/log/syslog, just keeps the log in memory, which you can examine with the "logread" command.by ecc - Debian
ygator Wrote: ------------------------------------------------------- > The machine type for the dockstar was added to u-boot 6 hours ago. Cool. I'm currently hung up on making my patches work with the new ARM relocation stuff that's been pulled into the upcoming (2010.09) release. I just don't know enough about the low-level hardware to know how to adapt it. So I'm wby ecc - uBoot
ygator Wrote: ------------------------------------------------------- > What is the allow_dirty all about? > > I noticed in my build u-boot it shows U-Boot 2010.09-rc1-00010-ga12555c-dirty The local version string is automatically generated by the tools/setlocalversion script. If you're in a git tree with uncommitted changes, it will append "-dirty" to the string.by ecc - uBoot