hyena Wrote: ------------------------------------------------------- > Bodhi, > > hi > > thx for this, > > my /boot on the iconnect flash drive consists of > : > > config-3.2.0-4-kirkwood > System.map-3.2.0-4-kirkwood > initrd.img > uImage > initrd.img-3.2.0-4-kirkwood > vmlinuzby bodhi - Debian
After you compiled the kernel, it should give you a .deb file? In any case, I think if you look somewhere in post install for initramfs (I don't remmeber where, if I can find it in the log, I'll post here), I recall there is a file where the kernel name is written in during dpkg installation. P.S. -You can see the old kernel still installed with apt-cache search linux-imageby bodhi - Debian
Ian, I think because you did not run dpkg -i your-new-kernel-name.deb. Because dpkg modifies the hooks in initramfs to use the new kernel, IIRC. So somewhere in there the hooks still point to the old kernel. So rather finding the hooks files and manually change it, you can just run cd /boot dpkg -i your-new-kernel-name.deb to install everything into the correct location. -bodhiby bodhi - Debian
Twinclouds, As long as you get uBoot flashed to mtd0 successfully with commands: # flash_erase /dev/mtd0 0 4 Erase Total 4 Units Performing Flash Erase of length 131072 at offset 0x60000 done # nandwrite /dev/mtd0 uboot.nandpogoV4-MMC-mtdparts-noSATA.kwb Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x20000 Writing data to block 2 at offset 0x40000 Writinby bodhi - Debian
Hi twinclouds, Yes, commenting out "/etc/init.d/hbmgr.sh start" in '/etc/init.d/rcS" is a common mistake for those of us who have been familiar with the Dockstar procedure (we do that and it works fine). What we should do here is to just kill Pogoplug processes every time you ssh into the box before doing any installation. The Pogo Mobile original uBoot does not have neby bodhi - Debian
shv Wrote: ------------------------------------------------------- > How to prevent that a NAND > kernel boots the rootfs from the NAND partition? > Maybe it works just to change the partition label > from rootfs to anything else. Hi shv, It's much easier to change bootcmd env to give USB a higher priority: from bootcmd=usb start; run force_rescue_bootcmd; run ubby bodhi - Debian
ingmar_k, Thanks for sharing your script! I always wanted to run Emdebian on my PogoPro :) never got the time to do it. Will definitely try this. -bodhiby bodhi - uBoot
With this vanilla Squeeze kernel, I don't think arcNumber and machid for Pogoplug E02 will work. You can interrupt uBoot using netconsole and set arcNumber back to 2097: setenv arcNumber 2097 - and if machid is set to dd6, then remove it setenv machid After you've booted into Debian, you can upgrade to Wheezy, and then later use a patched kernel for Pogoplug E02 to update itby bodhi - Debian
lincomatic, It's in the kernel already, you can try to load it at command line: modprobe rtl8192cu See if it's loaded (in dmesg).by bodhi - Debian
You're almost there! the debootstrap installation has been glitchy lately. But since you got to the installation basically done, you can generate uImage and uInitrd manually. You can use mkimage to do that, similar to the description this post: http://forum.doozan.com/read.php?2,11601,11627#msg-11627by bodhi - Debian
@Tom The procedure for Debian as we've been using is Jeff's installer scripts. These meant to be run on a stock Pogoplug OS. After you've installed Arch, you have new uBoot and everything is working, but you can't run either scripts from your current Arch booting USB because the script needs to wipe out the disk. So you could either remove the USB drive and boot back to Pogby bodhi - Debian
@chessplayer, I think shv wants to flash the kernel to NAND and put rootfs on a SD or USB drive, so the rootfs label solution will work consistently. Also, regarding to 2 partitions on a drive (or 2 drives). I think you can make sure that the kernel is always loaded correctly from /boot, and then with rootfs label for / , you can make it consistent, too. I used to use 2 partitions, but since I&by bodhi - Debian
Cool! See if you can use the 2nd SATA port by plugging in another SATA disk. I think the sheevaplug patch has 2 SATA ports already, but it's good to confirm it. If you can access it, then perhaps there is no need to update kernel (you will only gain the LEDs control). You can make it a bit better by using an updated kernel with the GoFlex Net archNumber 3089. I've posted one here:by bodhi - Debian
Yes, it is OK to do apt-get upgrade. But as restamp said, should backup your system first. You can also change apt sources list to use wheezy before apt-get upgrade. But prepare for a massive amount of updates! a lot of packages will be kept at older version, because the kernel is still 2.6.x.by bodhi - uBoot
tmm68 Wrote: ------------------------------------------------------- > I took the disk out of the SATA-bay and connected > it to the USB-port. > After the restart, i entered the wheezy system > with succsess. > > A dmesg did not show me the SATA device. At this point, does dmesg show the SATA ports? since you're connecting the HDD to USB adapter, it mounts the diby bodhi - Debian
Hi restamp, Yes, this hobby is addictive :) I'm fortunate that it also helps me in my works. What I think will happen when you boot up with the serial console attached is you will see the uBoot count down, and you can interrupt it. Recently I had to do a somewhat similar hack for a Pogo Mobile. I think chances are the original uBoot on the Pogo E02 will have a count down (even if it isby bodhi - Off-Topic
Very nice :) Thanks for sharing!by bodhi - Debian
shv Wrote: ------------------------------------------------------- > Hello bodhi, > > Your kernel is working fine on Pogoplug E02 and > Pogoplug Series 4, thanks. > > I was not successful with building a working > kernel. I get a .deb file but the kernel doesn't > get access to /dev/root. How can I setup a working > cross toolchain on debian or ubuntu?by bodhi - Debian
beta Wrote: ------------------------------------------------------- > Hi there, > > Think my GFN is finally bricked. > Here is what I did, from scratch: > Main reason to order this device was to build a > SqueezePlug, so I followed the SqueezeboxWiki > instruction > SqueezeBoxWiki. Preparing the USB stick > was easy, the bootloader has been replaced > folby bodhi - Debian
Hi restamp, If you buy it on eBay, you could ask the seller could go to my.pogoplug.com and de-register the device, and then you can register it again. But if the seller does not do that (either unwilling or bought the device from somebody else in the first place) then it's a big hassle. I don't know if you call Pogoplug they will be willing to de-register the device, I'd doubtby bodhi - Off-Topic
@chessplayer, I've suspected that davy's rootfs (Linux version 3.3.2-kirkwide ) does not have E02 support. When I looked at that rootfs config file I did not see Pogoplug E02 or V4. But it was on the Dropbox so I can't be sure. So I guess you can do these: 1. Use netconsole to remove machid (use command setenv machid) so that you're back to old settings. 2. Afterby bodhi - Debian
thespacepope Wrote: ------------------------------------------------------- Quote> 1. Rather than copying over the > /etc/Wireless/RT2860STA/RTA2860STA.dat file, I did > this: > mkdir -p /etc/Wireless/RT2860STA > > then > touch /etc/Wireless/RT2860STA/RT2860STA.dat > I left the file empty, that's right no > values in the file. Cool. I guess there weby bodhi - uBoot
Twinclouds, You can download these tools from Jeff's site: cd /tmp wget http://download.doozan.com/uboot/nanddump wget http://download.doozan.com/uboot/nandwrite wget http://download.doozan.com/uboot/flash_erase wget http://download.doozan.com/uboot/fw_printenv wget http://download.doozan.com/uboot/fw_env.config wget http://download.doozan.com/uboot/files/environment/uboot.enviby bodhi - Debian
Sure, updated 1st post to attach config file.by bodhi - Debian
I don't think the revert will work once Davy's uBoot is installed. It does not hurt to try, though.by bodhi - uBoot
chackoc Wrote: ------------------------------------------------------- > Another thought I had was get a small usb thumb > drive just for swap and consider replacing it from > time to time as an operating cost. At least that > way I don't kill the entire OS if the drive dies > prematurely. Of course it's best to have HDD for swap, but this is a good approach,by bodhi - Debian
Hi chessplayer, The reason is the current uBoot has a glitch that it will ignore arcNumber 3542, and not passing it to the kernel. So we need to also set machid to dd6 using "fw_setenv machid dd6". I've posted it here: http://forum.doozan.com/read.php?2,11601,11637#msg-11637. And I really defer to davygravy for the effort to have a "universal kernel" :) I only wantby bodhi - Debian
chessplayer, you're not really running Pogo E02! it is running as a 2097 reference board. [ 0.000000] Machine: Marvell SheevaPlug Reference Board This is probably because of the machid env was not set to dd6.by bodhi - Debian