For giggles, did you test your netconsole configuration with netcat on windows with your working pogo? If that works, you're going to have to just build a serial cable to diagnose the bad one.by kraqh3d - uBoot
Don't worry about the version of nc on the non-working pogo. It's just busybox's "slim" version. It doesn't matter. The uboot itself is what's sending the netconsole udp messages, not nc, when the device boots up. You're other pogoplug is running debian and you installed the full version of netcat, right? You can try listening with tcpdump or wireshby kraqh3d - uBoot
Squeeze uses a dependency based boot system. update-rc is sort of deprecated. inssrv is the new version. but the start up script in /etc/init.d needs to be formatted properly. just copy the starting bit from /etc/init.d/ssh into top of /etc/init.d/webmin.by kraqh3d - Debian
I've never attempted to use a cygwin or native win32 version of netcat. Try using your working debian dockstar as your netconsole listener, just "apt-get install netcat"by kraqh3d - uBoot
First and foremost, you need to set up serial or network console acces and post the uBoot output so we can see what's really happening. Second, you try to use your known good USB boot disk. But since it won't work without a modification though, and to prevent leaving you without a working device, I suggest you clone it to another disk using Clonezilla Live. Once you have a copy oby kraqh3d - uBoot
I know, but I'm not going to take my linux system offline just for that. :) After some googling yesterday I found there doesn't be a way to make it output to both at the same time so I added a little work around to change it back. I simply "run serialout" from the Marvell>> prompt to change the output back to serial. (This is from memory. I don't have accessby kraqh3d - uBoot
Update... Yesterday I got serial access setup, and the kernel just doesn't boot. It may be because I'm using generic Sheeva one which the lenny install script loads on top of the default one. I'm going to try the default lenny one tonight and see what happens. I'm also going to attempt to debootstrap an ARM build from my Linux PC but may be not until the weekend.by kraqh3d - Debian
I was using netconsole to catch the uBoot startup, but now I have a serial cable. My setup is below. It works, but it redirects all output to netconsole. Is there anyway for uBoot to output both to serial and netconsole? preboot=run if_netconsole start_netconsole if_netconsole=ping $serverip start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc;by kraqh3d - uBoot
I'm kind of glad that you bumped this thread back up. I never did get around to experimenting with aufs to merge my filesystems together for easier export through samba. I also want to do some testing to time file copies. I'm currently not running anything on my dockstar other than nfs and samba to export filesystems. I can mount a disk with sync and async and copy a large file oveby kraqh3d - Debian
You shouldn't get LED support with that base Lenny installation as it based off the generic Sheeva plug. And the same thing happens to me with a Dockstar. I've watched the uboot start up with netconsole. It successfully finds the kernel and loads it, but then it doesn't get an IP address, so I can't get back into it. I have a CA-42 cable sitting next to me to turn into aby kraqh3d - Debian
Nice enhancement. I may borrow this.by kraqh3d - Debian
I'm curious to know what error you made as I haven't installed the rescue system yet. Why couldn't you boot from usb after installing the rescue system? Looking at your output above, it looked like your usb stick was faulty.by kraqh3d - Rescue System
Sorry I wasn't paying attention. I didn't realize the thread sort of changed topics. I don't have a GoFlex but I've read here that it has issues loading the original firmware. I think someone said it needed to be loaded to a different memory location than 0x800000. And it looks like U-bit might overwrite the original pogo portion of the mtd but I haven't looked into iby kraqh3d - Debian
Wait a sec.... You shouldn't have to revert your uboot to boot into the original Pogo environment UNLESS you installed the rescue system or you mucked around with the bootcmds in uboot. Did you do either of those? If not, the original Pogo environment should load when the uboot cannot find anything to boot on usb.by kraqh3d - Debian
Heh, you're welcome. To your comment, all the major Linux distro's include auto mounting functionality but it's built on top of a full desktop environment. And there are some smaller foot print simple server based tools which do most of this already (usbmount for instance) but they all seemed to have something I didn't like. In the end, I decided to piece it to together myby kraqh3d - Debian
I dont think so, but you can enable other forms of file sharing with nfs, ftp, samba, http, upnp. It depends on what the consumer is.by kraqh3d - Debian
Well that script is meant to be run directly from the Pogo device. To run it on another system just to build the stick requires a little tweaking to the script. I wasn't sure of the users linux comfort level so I didnt even want to bring that up. But yeah it'll work. That script basically just downloads and decompresses that tar to a stick and then overwrites the kernel. But I donby kraqh3d - Debian
Yeah you know I just noticed that. I downloaded and uncompressed it, and ran a tar tf on it without a problem. I just untarred it. While I got some errors, I think its still ok. Give it a try anyway. It's not going to make anything worse, that's for sure. If it boots, you can do a dist-upgrade to squeeze.by kraqh3d - Debian
Ah! You started ntpd manually so the init script (/etc/init.d/ntp) didn't run. The debian init script allows ntpd to update the clock the first time regardless of the time difference by using the -g option.by kraqh3d - Debian
You can't use hwclock. That's trying to update the rtc. Just use "date --set". And are you sure ntp isn't working? What's the output of just "date"? Maybe you don't have the correct timezone? Use "dpkg-reconfigure tzdata" to fix it.by kraqh3d - Debian
There is no "list-upgrade". I think you meant "dist-upgrade" ?by kraqh3d - Debian
There's a tar image of Jeff's original Lenny system here: http://jeff.doozan.com/debian/lenny/base.tar.bz2 I think you should be able to decompress and untar it to an ext2 formatted USB stick (you only need about 512M), and boot it if you have the U-boot installed.by kraqh3d - Debian
All uboot images are located here: http://jeff.doozan.com/debian/uboot/files/uboot/ The original dockstar one is: wget http://jeff.doozan.com/debian/uboot/files/uboot/uboot.mtd0.dockstar.original.kwbby kraqh3d - uBoot
Quote scanning bus for devices... 3 USB Device(s) found scanning bus for storage devices... error in inquiry 0 Storage Device(s) found ** Block device usb 0 not supported I can see what's wrong, but I don't know why. I assume it's a compatibility issue. U-boot doesn't like your USB devices. Did you look at the thread of working USB sticks?by kraqh3d - Debian
Fred... The difference between booting and not booting rests on how the kernel enumerates the disks and assigns them device names. It really doesn't matter which disks may be bootable or not. The U-boot passes a root parameter to the kernel. But since U-boot doesn't have devices, it tries to assume what linux will call the device that it determines is the boot disk (by looking forby kraqh3d - Debian
You you give my suggestion a try? It can tested without making any permanent changes. The U-boot environment has setenv and saveenv. Setenv is transient. Saveenv is permanent like fw_setenv from the linux shell. First, set the label of your root stick. From the linux shell: tune2fs -L ROOTFS /dev/sda1 (Make sure you use the right device. It should be sda1 if you don't have anythiby kraqh3d - Debian
I'm using Jeff's standard U-boot on an original Dockstar. I was just testing it for giggles as I had expected it to work but was curious to find out. U-Boot 2010.09 (Oct 23 2010 - 11:49:22) Marvell-Dockstar/Pogoplug by Jeff Doozan root@debian:~# cat /proc/cmdline console=ttyS0,115200 root=LABEL=ROOTFS rootdelay=10 rootfstype=ext3 mtdparts=orion_nand:1M(u-boot),4M(uImage)by kraqh3d - Debian
You're in the the wrong place. You should probably ask in the Nook forum on xda-developers or open a bug on the calibre bug tracker.by kraqh3d - Debian
There's a few ways to skin this cat. I've honestly never had to swap my usb boot stick between my devices but its nice to have the option if something happens. I did run into the issue though. I cloned my original stick to hack a second device. It's much faster. But when it wouldn't come up on the network, I remembered this. My fix was to modify /lib/udev/rules.d/75-pby kraqh3d - Debian
Thanks! I made the change this evening. I definitely would've forgotten to change the usb_rootfstype parameter in uboot. It would've driven me crazy trying to find out why it was still mounting as ext2. Question... What happens now when the startup check determines there's a problem with the filesystem, or it hits the 180 day forced check, and something is wrong? I suspectby kraqh3d - Debian