http://forum.doozan.com/read.php?2,524,627#msg-627by Jeff - Debian
You have to build any lirc modules yourself. I built mceusb2 and atiusb on my dockstar using the following commands. The module sources provided by debian are a bit stale, so I also grabbed some updated code from the LIRC source tree. These notes are several months old. Some of the package names may have changed, however, it should be enough to get you started. apt-get install \ lirby Jeff - Debian
It seems that my webhost (Dreamhost) has implemented some sort of malware pattern matching that's choking on some of the pastes here. I've had to delete the offending posts just to get this tread back on the air. Until I can get things fixed , please 'preview' your post before submitting it. If it previews okay, you should be safe to post it. For dumps of more than 10-by Jeff - Displays
Thanks for the well-written overview and the script, Peter. This looks like a great hack! -- Jeffby Jeff - Displays
You've redirected the output to a netconsole 10.0.0.5. If you want to access it via serial, just disconnect your dockstar from the network and reboot. It won't find the server at 10.0.0.5 and should continue sending messages to the console. -- Jeffby Jeff - uBoot
The uBoot binaries haven't really changed over the last revision. Instead, the environment settings have been adjusted slightly. The old environment started usb, then stopped it, and then started it again. This caused some USB devices to stop functioning. You can restore the older behavior with the following command: fw_setenv usb_init 'usb stop; usb start; run usb_scan'by Jeff - Debian
Here is a list of the default environment settings that are configured when you use the uBoot installer. This is, of course, subject to change with future releases. -- Jeffby Jeff - uBoot
Sorry, I misread your original post. I thought you were referring to the GoFlex NET. The current uBoot installer does NOT natively support the GoFlex home. And it doesn't really need to. It comes unlocked. The GoFlex Home does not use the Pogoplug software. Instead, it ships out-of-the-box with a bootloader capable of booting from attached USB and SATA drives. If you attach a seby Jeff - Debian
The bootloader supports it natively, but the default Debian kernel doesn't support the SATA drives. If you want SATA, you can compile your own kernel with the peaslaker's patches here. -- Jeffby Jeff - Debian
0xc0000 is the default. 0xe0000 is also okay.by Jeff - uBoot
Quote MTD Erase failure: Input/output error Writing data to block 6 at offset 0xc0000 Bad block at c0000, 1 block(s) from c0000 will be skipped That looks like a bad block to me. Luckily the default uBoot has enough built-in environment variables to do a pretty good job of booting. If you're just looking to boot from USB, you can just let it use the built-in environment. If you reaby Jeff - uBoot
Did you forget a nand erase command before your write attempt? You can pad the file to the aligned size with the following command: dd if=ce_kernel_redstone_v63.img of=ce_kernel_redstone_v63.img.aligned bs=256k conv=sync -- Jeffby Jeff - uBoot
The GoFlex NET is supported by the latest uBoot installer. The GoFlex HOME doesn't need an updated uBoot -- it ships with a version that supports USB out of the box. -- Jeffby Jeff - Debian
Hi, Shawn, What does the light on front do when you try to boot without any USB drive attached? You may also want to try creating a file called 'rescueme' in the root directory of an ext formatted flash drive and then boot with that drive attached. It will force uBoot to boot from the rescue image. -- Jeffby Jeff - uBoot
Shawn, are you really in the same situation? Did you add a 'dhcp' command to your preboot string? According to your earlier post it does not sound like you're in the same situation and the above solution will not be of any help to you.by Jeff - uBoot
Did you have multiple devices plugged in when you tried to boot? Sometimes the kernel will detect USB devices that uBoot doesn't and the sda/b/c enumeration gets messed up. If you even get a serial cable connected, I'd be curious to see what the bootlog looks like with your bad drives. -- Jeffby Jeff - Debian
Yes, all you have to do is download and run the installer. It works fine in Debian.by Jeff - Debian
Yes. Only the newest uBoot has support for the arcNumber variable.by Jeff - Debian
After you install the new kernel package, make sure you update the arcNumber variable in uBoot. By default, it will use the overloaded Sheevaplug ID. To use a kernel with official Dockstar support, you need to have the latest uBoot and then run fw_setenv arcNumber 2998 -- Jeffby Jeff - Debian
I just added a new '--force-platform=XXX" parameter to the uBoot install script. Re-download the script and run install_uboot_mtd0.sh --force-platform=pinkpogo -- Jeffby Jeff - uBoot
Your Dockstar may have a different IP address after installing Debian. Check your DHCP logs. -- Jeffby Jeff - Debian
Great work, Eric! Even better is the fact that Dockstar support is already included in the latest Debian kernels. -- Jeffby Jeff - Debian
I use: tar \ --exclude=/lost+found \ --exclude=/tmp \ --exclude=/sys \ --exclude=/proc \ -zcf /tmp/backup.tgz Just remember to re-create the tmp, sys, and proc directories if you ever extract it to an empty drive.by Jeff - Debian
bootcmd is a uBoot environment variable. Don't mess with it unless you have netconsole or serial access and understand what you're doing. Let's try to keep this thread on topic. Having a list of known good/bad devices is valuable for new users. -- Jeffby Jeff - Debian
I'm glad you got it fixed. Out of curiosity, did you figure out what was wrong with your nand partition? Or did you just switch to USB booting?by Jeff - Debian
Yes, this includes support for the Pink Pogo with 256M RAM. If your Pink Pogo still has the original uBoot, or if you've installed a custom uBoot from elsewhere, it should detect this (or prompt you) and work just fine. If you've installed one of my Dockstar uBoots on your Pink Pogo, the installer will assume that your device is actually a Dockstar and install a new Dockstar uBoot (by Jeff - uBoot
Looks like you'll have to manually create the ubi_ctrl device. Try this mount -o remount,rw / mknod /dev/ubi_ctrl c 10 62 mount -o remount,ro / ubiattach /dev/ubi_ctrl -m 3 mkdir /tmp/ubifs mount -t ubifs ubi1:rootfs /tmp/ubifs -- Jeffby Jeff - Debian
The 'dhcp' command is poorly named, it should really be 'bootp'. Instead of just getting an IP from a DHCP server, it also tries to download a boot image from the DHCP server using TFTP. Since you put this in the preboot command, a serial cable will not be enough to recovery your Dockstar because preboot commands run *before* you have access to the serial console. Yourby Jeff - uBoot
This is pretty much how the Lenny install script works: it just grabs a big pre-configured image and dumps that to your flash drive. You can use the following command to create an image of an existing system: tar \ --exclude=/lost+found \ --exclude=/tmp \ --exclude=/sys \ --exclude=/proc \ -zcf /tmp/backup.tgz (don't forget to create empty /tmp, /sys, and /proc folders when extrby Jeff - Debian
It doesn't look like you have any problems with your uBoot config. It's loading and booting the system on nand just fine. The lineStarting kernel ... is where the kernel takes over and stops sending netconsole messages. Unfortunately, something happens after the kernel takes over. The default kernel doesn't support netconsole, so unless you attach a serial cable it's goby Jeff - Debian