Hi, when upgrading to Wheezy from Squeeze based on Davy's kernel, everything went fine until [ ok ] Setting up LVM Volume Groups...done. update-initramfs: deferring update (trigger activated) insserv: warning: current stop runlevel(s) (0 6) of script `lvm2' overrides LSB defaults (empty). Setting up parted (2.3-12) ... Processing triggers for initramfs-tools ... update-initby chessplayer - Debian
shyd, thanks for sharing, but I believe that your solution is inferior to the one using LABEL which has been discussed all over the place here in this forum (for a complete printenv of the uBoot with usb_scan see, e.g, my post). The LABEL solution as well as yours (I believe) both come with a price tag: since this relies on Initrd and not just uImage, you cannot boot Archlinux with it (see herby chessplayer - uBoot
Hi guys, just a brief warning: do NOT use the procedure on the NSA325! Unless I did something completely strange, I managed to brick the NSA325 that way. I do not get any output over the serial connection any more and it is going into an endless boot attempt cycle. Stiil, I cannot quite believe it, since the original uBoot of the two devices and in particular the mtdparts are so much alike,by chessplayer - Debian
@bodhi, that's ok, I will just wait for when you have found time for this.by chessplayer - Debian
bodhi, I would be interested and I would also be willing to do the test.by chessplayer - Debian
Just for the sake of completeness: the answer is "recoverable". The idea I had in my original post actually did work. So, if anybody else is interested, this is what can be done, if need be: 1. Extract images of /dev/mtd1 and /dev/mtd2 from another NSA320 via dd if=/dev/mtdx of=nsa320_mtdx.img 2. Flash those images to the one needing re-construction via flash_eraseall /deby chessplayer - Rescue System
WarheadsSE, ok, thanks, but: this means ??? What I have done meanwhile is create images of mtd0 - mtd8 (using dd) from the second NSA320 I am currently fiddling with. Is that about the same you were suggesting?by chessplayer - Rescue System
bodhi, unfortunately, your package does not boot on the Zyxel NSA320, as it does not recognize the machine id (arcNumber = 3956; machid=f74). What must be done to remedy this? Like davy's 3.3.2 kernel, it should not really be a problem to use your's, I think.by chessplayer - Debian
Hi guys, unbelievable, but in spite of the red alert text in the first post, i managed to erase mtd1 and mtd2 on one of my Zyxel NSA320s when trying to install the rescue system (wanted to do everything quickly, since I need to go out for a while in a minute and copy and pasted the wrong commands ...). Now the machine is still running and I have others with which I could try to remedy the sby chessplayer - Rescue System
Hi guys, has anybody been able to use the uBoot/rootfs from the first post with the NSA325? It does seem to offer quite a bit more bang and is currently available for 99,90€ ... Cheers, chessplayerby chessplayer - Debian
HellG, as you can see, my stupid entry has gone and I have apologized for the confusion. Now, I also apologize for stealing your time ... Sorry and thanks for taking the time. However, I believe the uBoot-environment can be much improved so as to be able to boot from either one of the USB-ports, use a separate boot-partition and so on (see my post here). I was just being stupid here, butby chessplayer - Debian
Having finally given the disk an msdos partition table (and, if I had a 3TB disk, I would give it a hybrid one like for the GoFlex Home ...), this post has become obsolete ... Sorry for the confusion ... Cheers, chessplayerby chessplayer - Debian
Hi guys, by 'his method', davy is referring to this post, but seeing how old this post is, you probably know that already. Myself, I am at the point where I can boot from a USB-drive (but not just any drive; one is working, another isn't; furthermore, it does not seem to want to acquire an ip address all the time ...). Booting the exact same image from HDD is not possible thoby chessplayer - Rescue System
Der Freibeuter Wrote: ------------------------------------------------------- ... snip ... > 3. Whe i got both files i should download > flash_erase and nandwrite: > > wget > http://download.doozan.com/uboot/flash_erase > wget > http://download.doozan.com/uboot/nandwrite No, this is not necessary, since flash_erase and nandwrite are already available > ...by chessplayer - Rescue System
@HellG: Sorry if I was not clear. I take it as a given that everything described in this thread's first post was done (as I did). So, if I understand you correctly, all you did was follow the first post and afterwards you were able to boot from disk? And, what I meant by updating uBoot is whether you followed Jeff's official script, which he updated due to davy's work. Appareby chessplayer - Debian
@HellG Did you update your uBoot before you were able to boot from SATA (see my question here)? Cheers, chessplayerby chessplayer - Debian
Hi guys, I am currently trying to get a Zyxel NSA320 up and running. Using davy's basic setup, I am able to boot from a USB-drive, but the exact same rootfs on the first SATA drive gives: U-Boot 2011.12 (May 03 2012 - 17:04:23) ZyXEL NSA320 2-Bay Power Media Server arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1 GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709by chessplayer - uBoot
Hi HellG, I would say that you can go ahead. I was in much the same situation as you are in (MAC-address like yours) and just got my NSA320 up and running with a USB-drive after flashing the new uboot. It seems like there is an issue with the network cable plugged in at boot (hangs at "host <serverip> is alive" and does not continue), but I will have to test that further. Howevby chessplayer - Debian
@dhead666, could you upload a photo, maybe?by chessplayer - Debian
Thanks. wpa_supplicant was already installed, but neither wireless_tools nor iw were. However, after installing those, I now get: ┌──[~] └──> iwconfig lo no wireless extensions. eth0 no wireless extensions. So, no more joy here. Anyway, I guess I have to clarify one thing: I have to manually issue the command modprobe rt2800usb before I can see the modby chessplayer - Debian
shv Wrote: ------------------------------------------------------- > This looks good. With iwconfig you can see which > network interfaces are available. Hhhmmm, no joy: ┌──[~] └──> iwconfig -bash: iwconfig: command not found ┌──[~] └──> ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.xxx.xxx.xxx netby chessplayer - Debian
twinclouds Wrote: ------------------------------------------------------- > chessplayer Wrote: > -------------------------------------------------- > ----- > > It is: > > > > > > ┌──[~] > > └──> lsmod | grep rt2 > > rt2800usb 11906 0 > > rt2x00usb 7590 1 rt2800usb > > rt2800libby chessplayer - Debian
It is: ┌──[~] └──> lsmod | grep rt2 rt2800usb 11906 0 rt2x00usb 7590 1 rt2800usb rt2800lib 39393 1 rt2800usb rt2x00lib 30207 3 rt2800lib,rt2x00usb,rt2800usb mac80211 170543 3 rt2x00lib,rt2800lib,rt2x00usb cfg80211 143659 2 mac80211,rt2x00lib When I have more time (maybe next weekend)by chessplayer - Debian
Indeed, modprobe results in the following: ┌──[~] └──> dmesg | grep rt2 ┌─[✗]──[~] └──> modprobe rt2800usb ┌──[~] └──> dmesg | grep rt2 [ 72.145164] usbcore: registered new interface driver rt2800usb ┌──[~] └──> Does that mean the chip is recognized? Sorry for the dummy question, but, although I have been active inby chessplayer - Debian
ingmar_k Wrote: ------------------------------------------------------- > There are newer kernel sources and with Debian I > don't think there are the same problems as with > Arch. > I am running my Pogos with Kernel 3.1. and > Emdebian Stable. I can't say anything about > longterm stabilty of Kernel 3.1., though.. So far > I didn't run into any problemby chessplayer - uBoot
Hi everyone, this is exciting news, since I got my Pogo Mobile today. In fact, as always, I had not been very thorough with my research and was disappointed at it not having the USB 3.0 and SATA port I was expecting ... Now this is definitely good news and I will keep tabs on this topic. Won't be able to contribute much, however, I fear. Just this much, maybe: dmesg | grep rt2 usingby chessplayer - Debian
I know these two: Hack247 A Google+ contributionby chessplayer - uBoot
Hi guys, this, however, is also strange. If you look at the picture in the post by Obihörnchen, it sure looks like he also uses putty. On the other hand, the bash.bashrc for the Archlinux case does not include calling something like linuxlogo, so maybe that messes things up for putty? But then again, who wants to use M$-OSes on their main computer anyway? Cheers, chessplayerby chessplayer - Debian
Twinclouds, what do you mean by "random characters"? Does that happen with the serial connected? If so, what you probably have to do is kill the terminal where you are running screen, unplug the serial cable from the master computer, plug it back in and start screen again in a new terminal. I am saying this, because something similar happened to me, it looked like "random&quoby chessplayer - Debian
Just an idea: could it be the keyboard layout? Also, I noticed that the background of the logo in your case is solid black while in my case it is a dark gray. What happens after a reboot? Other than that: no idea, sorry.by chessplayer - Debian