Hi Bob, That's strange, the old kernel in the rootfs should work fine with the new DTB. But I'm glad you've solved the problem using the new kernel! The new kernel should boot fine with uImage only. However, you will miss a whole bunch of modules that were configured in the initramfs. So it is best to boot with uInitrd. If you have problem loading it using whatever address inby bodhi - Debian
ElMariachi, > I formatted the partition and freshly created the > rootfs from > Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2. That should work. The only thing I would look for is your router. Does it use MAC address to assign certain IP address range? Also, mount the Debian 4.4 rootfs on another Linux box and look at this issue: https://forum.doozan.com/read.php?2,2by bodhi - Debian
> Ethernet is working fine with this new dtb! Cool :) We are getting closer. Thanks Bob! [ 0.376537] Initramfs unpacking failed: junk in compressed archive This problem is due to the load address of the uInitrd. Did you use the same location in u-boot env as Koen's?by bodhi - Debian
Hopefully Ethernet will be available with this new version. Please try!by bodhi - Debian
Hi Bob, Thanks! I double checked and saw some problem in my last DTS so will recompile and upload a new version.by bodhi - Debian
ElMariachi, > I tried to get Kernel 4.4.0 working for some time > now, but with no success. net console showed it > booted fine, but after loading the kernel there > was no network connectivity. I could not even ping > the GoFlex, even with setting a static ip in > /etc/interfaces. Did you install kernel 4.4, or did you create a new 4.4 rootfs from the released tarrbby bodhi - Debian
Bob, Thanks for the info! was the hwinfo --all run inside stock OS (Ubuntu)?by bodhi - Debian
This forum mission is to replace stock OS with a GNU/Linux OS that is much more powerful, and tracking mainlined Debian Linux. Basically we are making low cost ARM boxes performing like expensive NAS boxes, and keeping them up-to-date with latest Linux software development.by bodhi - uBoot
balanga Wrote: ------------------------------------------------------- > The good thing about Stock is that it's all > embedded, or is it possible to just update uboot > and leave the OS in situ? > > Apologies if this is a dumb question... It is possible with some extra steps to set up. But it would be a waste of effort to install new uboot and then run it that wby bodhi - uBoot
balanga Wrote: ------------------------------------------------------- > Having just reinstalled Stock on my GoFlex Home > unit, I wondered if it might be possible to > install netconsole on it, .... or might it already > be installed somewhere? If not can I simply wget > it? Stock uboot is very old, and there is no netconsole support. Netconsole is integrated in uboot. Thby bodhi - uBoot
This is the official manual: http://www.denx.de/wiki/DULG/UBootEnvVariables It is, as usual for open source software, quite old.by bodhi - uBoot
Manos Wrote: ------------------------------------------------------- > Hello, > I'm trying to put Debian on my NSA325v2 but I'm > stooped in this message > "BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in > shell (ash) > Enter 'help' for a list of built-in commands. > > /bin/sh: can't access tty; job control turned off > (initramfsby bodhi - uBoot
If you can't SSH in, then try to start dropbear in stock OS. /usr/sbin/dropbearby bodhi - uBoot
> You should enter each line from bodhi's post 1 > line at a time. Right!by bodhi - Debian
Looks like that Ethernet PHY is wrong so it screwed up SATA PHY too :)by bodhi - Debian
echowarrior108 Wrote: ------------------------------------------------------- > Here is my situation, I am now setup at home to > run my network tethered to my cell phone as the > cable provider I was using was unreliable at best, > that being said I have found no way to connect my > network to my router which was my plan and if i > run my cell as a hotspot my phone proviby bodhi - uBoot
Here is the update with Ethernet activated. Update: this version does not work right. Back to previous one.by bodhi - Debian
Try setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) earlyprintk=serial' setenv load_image_usb 'ext2load usb 0:1 0x800000 /boot/uImage' setenv load_initrd_usb 'ext2load usb 0:1 0x2100000 /boot/uInitrd' setenv bootcmd_usb 'setenv mainlineLinux yes; usb start; mw 0x800000by bodhi - Debian
mari8b, > But the other question(s) - can I flash new U-boot > from serial console? Do I need it actually? Should > I care about envs bad CRC or bad blocks? See parts of my answer above. You don't need to flash new u-boot to run the latest rootfs. The CRC error indicated that your u-boot version does not not use the same location for the envs that the rootfs expecteby bodhi - uBoot
mari8b, > So long I'm able to boot new Debian (with new > kernel) with my current U-boot, I don't need it > now. > > But I got problem with network: > Maybe are my envs wrong? fw_printenv isn't able to > read real U-boot envs... > root@debian:~# fw_printenv ethaddr > Warning: Bad CRC, using default environment Probably, this is becausby bodhi - uBoot
Do this with USB rootfs attached. It should boot to Debian. Power up, interrupt seriall console and setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) earlyprintk=serial' setenv bootcmd_usb 'setenv mainlineLinux yes; usb start; mw 0x800000 0 1; ext2load usb 0:1 0x800000 /boot/uImage; ext2load uby bodhi - Debian
mari8b, QuoteNow I can boot Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (uImage and uinitrd read from USB, the rest read from HDD), but mtd0 partition is read only. How can I mount it writeable? At the moment, you can only change u-boot envs in serial console for the NSA310. This was an oversight on my part when I put in the changes to allow these Kirkwood devices RW access to mtd0 (Inby bodhi - uBoot
balanga, > although I can't login. I'm not really sure what > the mtdx files contain... is it the full system > including any passwd entries? Yes. > > I'm tempted to go through the whole thing again > now that I have a better idea about what is going, > but I think I'd better get a serial connection set > up for the target box. Good iby bodhi - uBoot
QuoteKoen 88e1310-nnb2: Marvell Ethernet chip QuoteRay Marvell Alaska 88E1310S Transceiver 88e1310 Ethernet chip should be easy to activate . Let me look and will upload anther DTB.by bodhi - Debian
I've also looked into the GPU issue. I will need to release a new kernel version for this to work (will be 4.18.x). Currently the MVEBU kernel I released does not have the mainline graphics driver for this SoC configured in (we have no Marvell Armada box with graphics until now!).by bodhi - Debian
Is Ray info correct, and Koen info was wrong? QuoteRay Chips in addition to the SOC are as follows: Marvell Alaska 88E1310S Transceiver LANKom Electronics LG-2405S-1A Magnetics Module ENE Technology KB3930QF Keyboard Controller (data sheet says its for OLPC) Realtek ALC5650 Codec Genesys Logic GL850G USB 2.0 Hub Controller Silicon Image Sil164CTG64 DVI 1.0 compliant PanelLink transmitby bodhi - Debian
trx30, QuoteJust wanted to say thankyou! I now have Debian 9.5 on my n1t1 QuoteCurrently i am booting via serial each time the device starts Please post the serial boot log that shows how you run u-boot envs to boot the new kernel on USB. I only need to see from the beggining of u-boot until the first part of kernel booting that inlcude the kernel command line. And you can post the loby bodhi - Debian