Show all posts by user
Add a display to your device
Re: Install readonly embdebian on NAND - 14 years ago
I don't have access to a Pogo, so I can't say for sure that it will work. I would guess that some of the mtd settings would need to be adjusted. If anyone has a spare pogo they'd like to donate to the cause, I'll be happy to take on the challenge. -- Jeffby Jeff - Debian
Re: Environment CRC error with fw_set/printenv utilities - 14 years ago
Using a serial cable or netconsole, connect to the first uBoot and run 'saveenv'.by Jeff - uBoot
Re: Environment CRC error with fw_set/printenv utilities - 14 years ago
When you install uBoot to mtd3, you are creating a system with two bootloaders (Pogoplug on mtd0 and mine on mtd3). Each bootloader has its own environment and separate command line utilities for altering that environment. The Pogoplug bootloader is on mtd0. Its environment is saved to NAND at 0xa0000. The blparam utility will read and write to its environment. The new bootloader isby Jeff - uBoot
Re: Use netconsole to interact with uBoot without needing a USB cable - 14 years ago
You've somehow erased the area where mtd0 stores its environment. If you have a serial cable, you can connect to the old uBoot and run 'saveenv' to re-write the environment area. -- Jeffby Jeff - uBoot
Re: Use netconsole to interact with uBoot without needing a USB cable - 14 years ago
It looks like you're using an old version of the fw_printenv utility. It also appears that the uBoot environment has either been erased or didn't get installed. I suggest deleting /usr/bin/fw_printenv and /usr/bin/fw_setenv. Then re-download and re-run the uBoot installer. -- Jeffby Jeff - uBoot
Re: Possible fix for 'dual boot' problem with chained bootloaders - 14 years ago
blparam is in /usr/local/cloudengines/bin on your Pogoplug install. It configures the boot options for the Pogoplug uBoot on mtd0 fw_setenv configures the boot options for the new uBoot on mtd3 They are NOT interchangeable. -- Jeffby Jeff - uBoot
Re: embdebian - smaller Debian install - 14 years ago
Instructions for installing this to the NAND are available here. -- Jeffby Jeff - Debian
Howto: Install readonly emdebian on NAND - 14 years ago
I've done some preliminary work getting debian installed to the NAND: The installation is, by default, readonly. The installer includes a few workarounds to make everything work from the readonly filesystem. It creates a /sbin/init-ro script to mount and initialize a few tmpfs mount points. My goal is to keep the root system readonly, with all read-write parts located on tmpfs, NFS, orby Jeff - Debian
Re: debootstrap installer - 14 years ago
You can copy those files to your own server and change the variables in the script and the installer will still work.by Jeff - Debian
Re: fw_setenv and saveenv don't work? - 14 years ago
It looks like you're using an old version of the fw_printenv utility. I would start with deleting /usr/bin/fw_printenv and /usr/bin/fw_setenv and /etc/fw_env.config Then re-download and re-run the uBoot installer and try again. Quote[ 54.290000] nand_write: Attempt to write not page aligned data CRC write error on /dev/mtd0: Invalid argument Error: can't write fw_env to flashby Jeff - uBoot
Re: debootstrap installer - 14 years ago
The link to the lenny installer is at the top of the debian page. I'm not sure what "list of files" you mean. Lenny just uses the tarball from Martin's site plus the sheeva-with-linux kernel. Squeeze only contains files from the official repository plus a few manually generated config files that are included in the installer source. For the serial connection, I use a Nby Jeff - Debian
Re: Debian boot - 14 years ago
The 'dual boot' issue is a limitation with the Pogoplug uBoot. There are a few possible workarounds: 1) Configure the Pogoplug uBoot to always boot Debian. Advantage: it's easy. Just run 'blparam bootcmd=run bootcmd_usb' Disadvantage: If you screw up your Debian install, and you haven't configured the uBoot netconsole, you'll have to connect a serial cablby Jeff - Debian
Re: NTFS Files over 2GB - 14 years ago
I think this is more of a debian/package problem rather than something specific to the Dockstar. You may want to ask the Debian ARM mailing list. -- Jeffby Jeff - Debian
Re: Clarification on New Uboot - 14 years ago
Johns, I have a couple of questions about your setup: Are you on a Dockstar? What uBoot are you using? Have you reflashed mtd1 or mtd2 with custom images? I ask because the Pogoplug uBoot doesn't support the usb commands, and the new uBoot that I posted fails when reading the Pogoplug uImage from mtd1. -- Jeffby Jeff - uBoot
Re: Script dies. Failure trying to run: chroot ... - 14 years ago
chroot isn't in your PATH variable. You need to run: export PATH=$PATH:/usr/sbin:/sbin before running the script. -- Jeffby Jeff - Debian
Re: embdebian - smaller Debian install - 14 years ago
If you install uBoot on mtd0, yes.by Jeff - Debian
Re: Debian install after OpenWRT install - 14 years ago
That specific error is caused because your OpenWRT environment doesn't have the 'ar' command. It looks like your shell is a bit limited, as well. I would guess that there are enough differences that the script won't work without quite a bit of work. There's another reason it won't work: OpenWRT uses mtd3 as a jffs2 overlay filesystem and my bootloader script willby Jeff - Debian
Possible fix for 'dual boot' problem with chained bootloaders - 14 years ago
Update: An even better solution is to install my new mtd0 uBoot. Original Message: ------ I've come up with a possible workaround to fix the 'dual boot' issue affecting chained bootloaders. The trick is to boot from USB when a normal network connection is detected and boot from the Pogoplug install when the network is disconnected. The setup below assumes that 192.168by Jeff - uBoot
Re: chroot & mkimage fails - 14 years ago
I think it's an issue with /usr/sbin not being in the PATH when you connect via SSH. When you connect over serial, it's in the path: serial: -sh-3.2# printenv PATH /sbin:/usr/sbin:/bin:/usr/bin ssh: Pogoplug:~$ printenv PATH /usr/bin:/bin:/sbin so run 'export PATH=$PATH:/usr/sbin' before running the installer and you should be all set. I've updated the inby Jeff - Debian
Re: chroot & mkimage fails - 14 years ago
John, That's very odd. I'm not seeing that on any of the devices I've tried installing this on. There should be a debootstrap log in /tmp/debian/debootstrap. Can you please post that here and I'll take a look at it. Thanks, -- Jeffby Jeff - Debian
Re: Getting official Debian support for the Dockstar - 14 years ago
I think we have a pretty solid chance of getting support. We can flash a new uBoot to mtd0 and be pretty darn close to a sheevaplug, as far as the Debian installer is concerned. It would be great to get the LED patches applied to the kernel. If you want to work up a cleaner kernel patch and get Martin Michlmayr in on this, please go for it. I'll be happy to help in any way I can. --by Jeff - Debian
Re: chroot & mkimage fails - 14 years ago
It sounds like the debootstrap command may be failing. What size is your partition on sda1? I've updated the installer to print out an error if debootstrap fails. -- Jeffby Jeff - Debian
Re: chroot & mkimage fails - 14 years ago
There was a bug in the emdebian install script. It's fixed now. Just run the installer again and you'll be all set. -- Jeffby Jeff - Debian
Re: Clarification on New Uboot - 14 years ago
If USB dies, you have to connect a serial cable to get into the original uBoot. Or, before it dies, you could configure the original uBoot to use netconsole (see other forum post). To switch back to the "back and forth" booting, do: blparam 'bootcmd=run bootcmd1' To switch to 'always boot from NAND': blparam 'bootcmd=run bootcmd_original' --by Jeff - uBoot
Re: Use netconsole to interact with uBoot without needing an USB cable - 14 years ago
Link fixed. Thanks!by Jeff - uBoot
Re: doimage source code - 14 years ago
doimage is part of the old uBoot. The sources are in the links to the old uBoot at the bottom of the uBoot page. If you follow the instructions for building the old uBoot, you'll get a compiled doimage in the tools/ directory. -- Jeffby Jeff - uBoot
Re: Scan all USB devices and boot from the first bootable drive. - 14 years ago
Edit: Yes, use the new mtd0 uBoot. -------- Not that I know of. We can't load the old pogoplug files in the new uBoot because the ecc is different so it won't load anything larger than 0x7ff from mtd1: Marvell>> nand read.e 0x900000 0x100000 0x07ff NAND read: device 0 offset 0x100000, size 0x7ff 2047 bytes read: OK Marvell>> nand read.e 0x900000 0x100000 0xby Jeff - uBoot
Use netconsole to troubleshoot uBoot without a serial cable - 14 years ago
This assumes that your desktop machine has an ip address of 192.168.1.2 and that the Dockstar is okay to use IP address 192.168.1.100. You'll probably need to adjust these to something appropriate for your network. On the Dockstar: fw_setenv serverip 192.168.1.2 fw_setenv ipaddr 192.168.1.100 fw_setenv if_netconsole 'ping $serverip' fw_setenv start_netconsole 'setenby Jeff - uBoot
Scan all USB devices and boot from the first bootable drive. - 14 years ago
The new uBoot installer (since 10/3/2010) will configure USB scanning automatically. The following script is a more configurable method of scanning for USB drives: usb_scan_list='1 2 3 4' usb_scan_1='usb=0:1 dev=sda1' usb_scan_2='usb=1:1 dev=sdb1' usb_scan_3='usb=2:1 dev=sdc1' usb_scan_4='usb=3:1 dev=sdd1' usb_scan_done=0; for scanby Jeff - uBoot
Re: Clarification on New Uboot - 14 years ago
1) Yes. The pogoplug uBoot on mtd0 will "cycle" between booting from the pogoplug install and the new bootloader. You can fix this by using blparam and configuring it to always boot to the new bootloader: blparam "bootcmd=run bootcmd_usb" and then it will never try to boot the internal pogoplug install -- not even if you have a problem with your plugbox or debian instalby Jeff - uBoot