Linux Kernel 4.4.124 Oxnas (OX820) Pogo V3 package and Debian rootfs

agiorgio Wrote:
-------------------------------------------------------
> The plug was running Debian Squeeze, and I
> replaced the root filesystem on the USB hard disk
> with shv's Wheezy one. That seemed to work
> perfectly. It's been a while since I hacked that
> plug to run Debian, and I don't remember exactly
> what I did. I'll probably end up just leaving it
> alone, since I'm just using it as a remote backup
> device.

You are running stock U-Boot, so the envs must be listed/edited with blparam. Except if you have serial console, then in serial console it's printenv/setenv.

Yes. It should work. I meant to release u-boot images for this, but have not get around to test it. Booting directly with SATA is really not necessary, since you can put just the rootfs on SATA and boot it with NAND u-boot, similar to USB. So in this case, this bootable SATA is only used as a backup booting mechanism.

The default u-boot settings is for booting USB drive. To boot SATA, you will need to clone them for SATA. For example:

dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset

would become

dt_bootcmd_sata=ide reset; run dt_sata_bootcmd; reset

And

dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage

would become

dt_load_uimage_sata=ext2load ide 0:1 $uimage_addr /boot/uImage

And so on for the rest of other envs that specify usb as the boot drive. If you're not sure, prepare them in a notepad, and paste them here for checking. And do these in serial console, without saving them until after you can boot into Debian.

BTW, I'll include SATA boot option envs in the next release of the envs image in the OXNAS U-Boot thread.

@bodhi,
I found the reason for the problem with network not available due to "Configuring network interfaces...SIOCSIFHWADDR: No such device". It could occur that a wrong or different MAC address is registered in /etc/udev/rules.d/70-persistent-net.rules. To solve the problem it is just necessary to remove the line(s) form the file.

My guess would be that you probably only told U-Boot to load the uImage file, but not the device tree (.dtb) file, together with it. That would explain why the kernel complains that it does not know the Hardware it is supposed to run on.

Could be something else, though, too. Not enough Information from your part, so far.

Hi,
i have built the .dtb-file with my new kernel by running "make ox820-pogoplug-classic.dtb". I then copied the resulting .dtb-file to /boot/dts, while my self-built uImage and uInitrd reside in /boot/.

Where do you normally get the zImage and initrd.img-file? I used the zImage-file from the kernel-source directory arch/arm/boot and the uInitrd.img-3.15.8-oxnas-tld-1, which was installed in /boot/ by the debian-package. Is there a smarter way where to find the initrd.img?

I attached my environment-variables from u-Boot. I assume them to be correct, because they can boot bodhi's kernel without any problems.

> Where do you normally get the zImage and
> initrd.img-file? I used the zImage-file from the
> kernel-source directory arch/arm/boot and the
> uInitrd.img-3.15.8-oxnas-tld-1, which was
> installed in /boot/ by the debian-package. Is
> there a smarter way where to find the initrd.img?

That the easiest way to get initrd.img. And zImage should be retrieved from arch/arm/boot.

Hi bodhi!
Sorry I was off for some days, but anyway thanks for the new kernel. I'll try it asap.
I have several Huawei modems (E160, E172 etc.), I think it's all the same driver/module. I don't know which it is exactly, it worked with my Raspberry Pi out of the box (maybe this helps?).

First of all, thanks to the community for keeping this device alive.
Just dusted of my V3 non-pro and trying to get it too run with the latest Debian rootfs.
The plug is running an ancient version of Arch (2012.05 rootfs).
Can I just use the 3.12.13 rootfs listed in the OP or do I need to update uBoot first?

> The plug is running an ancient version of Arch
> (2012.05 rootfs).
> Can I just use the 3.12.13 rootfs listed in the OP
> or do I need to update uBoot first?

The instruction on the first page (2 ways to install). To run with stock u-boot you must load it using tftp, because stock u-boot does not have USB.

However, if you are running ALARM installation (WarheadsSE u-boot version) then it might work (can't recall exactly) with the DTB embedded in uImage. U-boot envs will have to change to load uImage from USB.

Please, enter the code that you see below in the input field.
This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right.
If you enter the wrong code, a new image is created and you get
another chance to enter it right.