TOLiS_GR, > 1. Is it possible to do this procedure in a > windows environment? I have some experience with > linux, but I'm currently on a laptop without > direct access to a linux pc. Not possible. u-boot installation must be done on the GFNet itself. However, linux rootfs can be preprared on a Windows PC running Linux Live CD. > 2. Is it possible to install the kby bodhi - Debian
Frederick Grayson, > Y:\Downloads\FTP http\NetCat for > Windows\nc111nt_rodneybeede>nc -l -u -p 6666 Perhaps the flakiness is on the netconsole server side. Try to make sure you can interrupt it and execute commands. Or use a different nc. Better yet, since you can boot the Pogo V4, use that for netconsole server. Don't use Windows netcat, you will have better luck with Linuxby bodhi - uBoot
Frederick Grayson Wrote: ------------------------------------------------------- > I guess I'll have to wait for the serial cable > parts I ordered. I'm glad I don't need the > capability right now, I'm just curious. Hopefully > the PL2303HX chip won't be a counterfeit :) You could update to the newer u-boot. Although I recognized your installed u-bootby bodhi - uBoot
h1ro Wrote: ------------------------------------------------------- > bodhi Wrote: > > I've only briefly looked at the Sata-only > booting. > > To me it's good for recovery purpose, not much > > else. Booting with a modern u-boot in NAND is > much > > more flexible. > > But your u-boot in NAND can also boot kernel and > rootfs from Sby bodhi - Debian
NTFS is slow. If you must use it, use big_writes. For example: mount -L $disk_label -o noatime,big_writes /media/$disk_label Google it and you will find may different tweaks to improve the speed.by bodhi - Debian
rasto, > EDIT: it appears, that going from stock uboot I > have to do section B: in order to write default > envs to new MTD location to have succesfull read You got it! the stock envs location is different. That's the reason for the CRC error.by bodhi - uBoot
@WarheadsSE, Do you have the DTS for the NSA325? I'm starting to build kernel 3.17 and I realized that we need NSA325, Pogo V4, and Netgear Stora DTS to build the common Kirkwood armv5 kernel. Between mainline and ALARM, the other boxes DTS are already available.by bodhi - uBoot
monkmandolins, > If it is still showing up on my network, is there > hope? Yes! usually it means that, without the USB, the plug has booted into the stock OS in NAND. 1. Usually stock Pogo OS has these root user/password: root, ceadmin root, stxadmin So these and see if you can log in with ssh. 2. Another thing worth to try is to create a Debian rootfs. Download my rootby bodhi - uBoot
Ian, If you've done what I suggested above, try looking for the plug in the network. Netconsole does not display more output than "Starting Kernel ….". If no sight of the plug, your last resort is serial console: http://forum.doozan.com/read.php?8,13263by bodhi - Debian
Hi hepi, If you are using my rootfs, then there is no extra udev rules in the rootfs except for network device. It's up to the users to add udev rules to /etc/udev/rules.d/ to automount USB drives or any other devices. It is bare minimum rootfs.by bodhi - Debian
vaidyasr Wrote: ------------------------------------------------------- > bodhi, > When I am moving a file from a networked device to > the HDD's connected to the Pogoplug v4 (formatted > as NTFS), I got the following results > 441 be/4 root 0.00 B/s 4.12 M/s 0.00 > % 0.00 % mount.ntfs /dev/sdb1 /share/My_Book -o > rw > 441 be/4 root 0.by bodhi - Debian
monkmandolins, Do this on a different Linux box: wget http://archlinuxarm.org/os/ArchLinuxARM-kirkwood-latest.tar.gz - Format a USB drive with Ext3. - And then as root user extract it (assuming the USB is mounted as sdb1) cd /media/sdb1 tar -xf ArchLinuxARM-kirkwood-latest.tar.gz sync - connect serial console terminal - plug the USB in and power up. If you can't boot, copby bodhi - uBoot
Ian, Did you run everything, especiall the tar command, as root user? Must be root. This is actually GFNet u-boot , but should work fine for GFHome.by bodhi - Debian
hepi, Sure, I'm about to build 3.17. But I thought these modules are alrealy included. Have you tried: modprobe snd-usb-caiaq modprobe snd-pcm-oss modprobe snd-mixer-oss modprobe snd-seq-ossby bodhi - Debian
IanD QuoteAny last thoughts before I rip this thing apart and use it as a spare hard drive ? Don't :) Your problem is simple to fix. It is a rootfs mounting problem. Since you already have the new rootfs on the Cruzer Blade, do these: - label the rootfs partition rootfs, using tune2fs -L on another Linux box (assuming the Cruzer Blade was mounted as sdb1): tune2fs -L rootfs /dby bodhi - Debian
Your u-boot has support for netconsole. It's the latest installed by this script. Boot up the Pogo E02, log in to Linux and ping 192.168.1.50, do you see the response? and does your /etc/resolve.config has any domain in it? if there is, try clearing everything in it and replace with nameserver 8.8.8.8 I think it might be your network. Netconsole is not a sure thing, and it is affectby bodhi - uBoot
Quotefrozenrhino > Calibre (the GUI version, not just calibre-server) > runs (albeit very, very slowly) on a pogoplug > through VNC. > > It's not something I'd recommend to anyone unless > you really like pain. > > When Calibre is actually doing anything, the > memory use spikes on my pogoplug, according to > Top. > > Calibre-server oby bodhi - Debian
Frederick Grayson, > If I boot my Pogoplug V4 which is set up the same > way, I do get netconsole output from it. > > Both plugs were modded with the same Uboot shell > script from > http://projects.doozan.com/uboot/install_uboot_mtd > 0.sh > Your env looks good, so hard to tell what is wrong. What you can do is open a second terminal and try start pinging 1by bodhi - uBoot
Peacemaker Wrote: ------------------------------------------------------- > I already tried this and then I get a kernel > panic. (posted it earlyer). > > Maybe I had the wrong syntax in the dts(i), but I > don't even see how the driver read the dts and > switches between ports like the vendors driver. > So there might be more to do. I guess this driver > isby bodhi - Debian
QuoteGravelrash> What you are experiencing is because the load > order of the network is eth0 then wlan0. I managed > to replicate your situation by having the eth0 and > wlan0 on the same network segment. the result of > which (caused by binding order of the network > interfaces) was for the routing table to > preference eth0 over wlan0 and build the routing > tablby bodhi - Debian
Ah! I forgot ingmar also has SATA disk installation documented. Good choice.by bodhi - Debian
It stuck there because of the bootargs when you run the command like above. Go ahead and boot to see where it was stuck at booting the kernel: > boot Once you've booted into Linux, remember to set stdin, stdout, stderr back to serial. And remove the preboot env.by bodhi - uBoot
twinclouds, I meant simply that you can log in with serial console and look at the problem live, even though you can't ssh in. You can try setting routes, up/down the wlan, … so on. It is easier to see it that way.by bodhi - Debian
I thought I already hit the "Post Message" button early today :) when I meant to post this: The new driver is robust enough that it seems the necessary change might be as simple as this: drivers/ata/sata_oxnas.c SATA_OXNAS_MAX_PORTS = 2,by bodhi - Debian
Here is the updated image. Try kwboot with this attached GFH uart image (use without -p option).by bodhi - uBoot
vaidyasr, The rootfs has little to do with it, unless your'e swaping to a swap file or partition on the drive that the rootfs is on while copying. If you're copying from USB-to-USB, then it has a lot to do with those drives speeds, and how they are formatted. So even if the rootfs is on the SD card, it should not be a factor. You can verify it by running iotop on a different teby bodhi - Debian
@twinclouds, Do you have serial console? this is where serial console will make troubleshooting much easier. I had this problem long ago on the Pogo Pro. IIRC, the solution was with routing table (gateway). If I can find my note, I'll post the settings.by bodhi - Debian
:) your u-boot envs were messed up so much more than I've expected. I guess the rescue u-boot must ignore all of them (not just preboot) to get it to the prompt. I'll be back later today.by bodhi - uBoot
egon0, Try kwboot with this attached GFH uart image (use without -p option).by bodhi - uBoot
morph027, You must have started out with Arch kernel uImage in NAND first, and then made a SATA disk with everything on disk using WarheadsSE procedure, and then replace rootfs with one of the rootfs from Varkey or Shv. The last time it ran, it was using Debian Squeezy completely from SATA disk.by bodhi - Debian