Chuck, > Would it be ok to update uboot so I don't have to > boot with kwboot to get Debian loaded. Yes. It would be OK now to update u-boot. After updating u-boot, you need to correct the uImage before rebooting. This is because the new u-boot default is to boot with separated DTB. cd /boot cp -a uImage.orig uImage If you still have trouble copying the uImage file tby bodhi - uBoot
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > Oh well I'm getting the "no such file or > directory" message, meaning my pins have loosened > again. No, they are not loosen. You would get nothing if that is the case. > We had our chance earlier. Ray is going to > have to take up the slack because I'm about to > sby bodhi - Debian
Mr Dini Wrote: ------------------------------------------------------- > Yes, I found that command: > > > mw.l f1010100 1361c000 > > > Will try it tomorrow! > > Regarding the two partitions... Okay, but in case, > when I just have a rootfs, where the u-boot look > for the uImage (kernel). I haven't got a non stop > tftp server to download iby bodhi - Debian
red9r Wrote: ------------------------------------------------------- > Thank you Bodhi! > > I have my serial console in hand and looking > forward to learning the process. Please create a new thread in U-Boot subforum when you're ready with serial console.by bodhi - Debian
Mr Dini, Ah! I remember something about USB power on this stock u-boot. I have to look for it. And create one single Ext3 partition, as I mentioned above. Do not use 2 partitions. You don't need it. Stock u-boot will boot ext3 with the uImage that has DTB embedded inside it (step 4 in the kernel thread)by bodhi - Debian
Bjoern, As I mentioned above, in this thread. http://forum.doozan.com/read.php?2,13702,13704#msg-13704 Quote5. Use iotop command to watch frequent disk IOs (to figure out which log files needed to be moved or overmounted). iotop -o -b -qqq So what you should do is running it in the background and redirect output to a file in RAM. For example, run at 3-second interval and for 1200 tby bodhi - Debian
Joey, Set to a real IP, for example: 192.168.178.50 (xxx.xxx.x.xx means use your own number, whatever it is). setenv ipaddr 192.168.178.50 And the MAC address has this format: setenv eth1addr 64:00:F1:20:FF:B7by bodhi - Debian
mordchen Wrote: ------------------------------------------------------- > hello, > > I have successfully installed debian on my nsa325 > running on usb flash device. > But every flash device gets defect after using it > for 14 days. ( I have now 5 defect usb drives ) > I am using Intenso Micro Line 16 GB because > this one was able to boot, when I tried to insby bodhi - Debian
rayknight Wrote: ------------------------------------------------------- > I found specs for the following Marvell based LG > NAS units: > > N2B1DD2 has Marvell 88F6192 800MHz with 128 MB > DDR2 SDRAM, 2 SATA ports w/2 1TB drives, Blue-Ray > Rewriter, 3 USB 2.0, 4-in-1 memory card reader, > and 1 10/100/1000 Mbps LAN. > > The N1T1 is also supposed to have Mby bodhi - Debian
Please try this 2.5 version. I've added Ethernet code. - kwboot the box with this new version, as before, interrupt serial console and Test 1: try 2 tests, with ethernet cable connected to MON port, and then LAN port version setenv ipaddr xxx.xxx.x.xx setenv ethaddr <the MAC address of the 1st port> ping <your router IP> Test 2: try 2 tests, with ethernet cable connby bodhi - Debian
Thanks Joey! both USB and MMC are working. The errors you've seen were with the format of the drives.by bodhi - Debian
Chuck, Congrats :) Debian has booted. One more thing: because the DTB (the kernel file device tree file that describes the hardware) was the GoFlex Net DTB (you have appended it when you created the rootfs), it was booted as the GoFlex Net. QuoteRootfs instruction 4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed tby bodhi - uBoot
> ON100_K9> usb start > starting USB... > USB0: USB EHCI 1.00 > scanning bus 0 for devices... 2 USB Device(s) > found > scanning usb for storage devices... 1 > Storage Device(s) found > ON100_K9> ext2ls usb 0:1 / > ** Invalid partition 1 ** This is because the USB is FAT32. ext2ls works for ext2 or ext3 file system, but not FAT32. > ON100by bodhi - Debian
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > Hey Bodhi I tried a new USB stick newly formatted > to FAT32, and the old god-knows-what's-on-it 2GB > SDCard. > Results: > > ON100_K9> usb start > ON100_K9> mmc rescan > ** First descriptor is NOT a primary desc on 0:1 > ** > > MMC rescan: current device # 0by bodhi - Debian
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > > > You could buy cheap Android box, and install > Kodi > > on your own, too. > > > > At best it's weeks away, but if you've got the > advice I'll do it. I could fliby bodhi - Allwinner A10
> starting USB... > USB0: USB EHCI 1.00 > scanning bus 0 for devices... 2 USB Device(s) > found > scanning usb for storage devices... 1 > Storage Device(s) found > ON100_K9> mmc rescan > ** First descriptor is NOT a primary desc on 0:1 > ** > > MMC rescan: current device # 0 initialized OK > ON100_K9> > Cool! I think :-) Both Uby bodhi - Debian
Here is version 2.4. Please try usb start mmc rescan Ethernet will be more completed later, in next test version.by bodhi - Debian
Joey, > But Linux is another story. On a serious box like > that Kodi box I would rather wipe out an install > with known blacklisted apps than risk what else is > screwy. You could buy cheap Android box, and install Kodi on your own, too. > To each his own. Yes.by bodhi - Allwinner A10
> will need to know it is fully loaded with a lot of > Kodi blacklisted add-ons. These add-ons are not > bad at all, except if you wanna get helps from > folks in Kodi forum, they won't help if they know > your Android device is loaded with any of Kodi > blacklisted add-ons Can't blame the Kodi developers. Kodi is open source and free, but the least those vendby bodhi - Allwinner A10
Joey, A friendly suggestion and a nitpick: you have a "bad" habit ;) in that you update the post, instead of posting a new one. A lot of time people (eg. yours truly) don't know there is update because it does not get flagged as something new by the forum with a red indicator.by bodhi - Debian
Chuck99 Wrote: ------------------------------------------------------- > I think I am done with Debian on USB do I have to > do the Linux compile next or do I need that? After you created the rootfs on USB, you can start on booting it. Are you keeping stock u-boot, or going to install new u-boot? If you're going to install new u-boot then you should do it now. If you're kby bodhi - uBoot
Mr Dini Wrote: ------------------------------------------------------- > Okay! > > Summa-summarum: I have an uImage generated with > Your description, from the 4.6 tld archive (bz2). > And an uInitrd from madadmin's article. > No need for any of this. > I will place theese two files to a pendrive's > FAT16 part with boot label? And I will extractby bodhi - Debian
Mr Dini Wrote: ------------------------------------------------------- > Many-many thanks! I am very thankful! :) > > Certainly, I have serial cable and I Can use it. > > I will try it tomorrow. Ah. If you have serial console then you don't need ethernet to upgarde kernel to 4.6, either. In case you have problem with it, just login with serial console and upgrade keby bodhi - Debian
> this for making ubifs manually > https://forum.openwrt.org/viewtopic.php?id=63714 That was a quite good tutorial. But please do take your time to read and understand because it is not for beginners.by bodhi - uBoot
Mr Dini, > And the 4.4.0 rootfs will work with 4.6.0 kernel? > Because, as You read, the 320S ethernet fix is > just come with the future releases... Of course. Rootfs 4.4.0 has the kernel 4.4.0 in it, and NSA320S Ethernet works since several versions back (in 4.5 it was broken). If you want to be sure: - Create rootf 4.4 on USB - Copy the attached kirkwood-nsa320s.dtb (tby bodhi - Debian
Mr Dini Wrote: ------------------------------------------------------- > Okay, but I Can't install deb packages at my nas's > stock fw, because I haven't got dpkg package > manager... Note that I posted "Debian 4.4 ...." above. It is a full Debian system rootfs that you tar to a USB drive and use it. No need to install .deb package. Scroll down and findby bodhi - Debian
Chuck, Just do as Note 1 said. It is to secure your box, in case you have it facing the net. Ignore Note 2, unecessary for you. But these are done *after* you have booted into Debian. So wait until later. The best way to learn is to set out and do it. Create the rootfs on USB. Capture everything you did in a log, and post it here. I will look and point out any misstep you might have made,by bodhi - uBoot
Pogoplug.com is no longer usable. Stock OS should only be a vehicle to install new Debian/Arch rootfs and new u-boot. In the mean time, to make it easier to log in to the box. In stock OS, to kill pogoplug service and start SSH. edit the file /etc/init.d/rcS ###/etc/init.d/hbmgr.sh start /usr/sbin/dropbearby bodhi - uBoot
Mr Dini, > I have to make an uImage > manualy for the nas. That's okay, but how Can I do > that? Where Can I download a kernel source tree, > which compatible with my nas? It is in the kernel/rootfs thread as I mentioned above. QuoteUpdated 20 Feb 2016: This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2........ /quote]by bodhi - Debian