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

Nate,

Looks like you have done this step incorrectly:

Since you are going to run the new rootfs, which is a FDT rootfs (see info in the 1st post), you need to flash the default envs image.

2. The env image pogopro_uboot_env.img should only be flashed if your rootfs has FDT kernel. If your kernel is an older non-FDT kernel then do not flash this env image.

Your netconsole was set up correctly, so try to connect netconsole. On Ubuntu, the default netcat is not working properly. I recall that you need to install a different version of netcat to make it work.

To check that your netconsole is running on the Pogo. On Ubuntu, start pinging the Pogo IP address

ping 192.168.1.13

and then power up the Pogo. See if you get any response. If you do get a few responses then netconsole is running.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Ah yeah, I skipped that bit, I thought that I am having a non FDT! silly me.

OK, I tried pinging the Pogo while it boots (3x), I got no ping back.

What should I do now?

@Nate,

You have flashed spl and u-boot successfully, so I think your netconsole should work. Look at your network setup and see if you can find any thing wrong. If you have another box I would temporarily connect it to the same ethernet cable for this Pogo V3, and ping it from the Ubuntu box. Just to verify that you dont have any problem getting to this end.

If netconsole does not work, you would have to either:

- Connect serial console. I would do this if you can get a serial console quickly, or willing to wait. This is an indispensible tool, if you plan to hack another pogoplug after this.

- boot with SATA. See what Robert is trying to boot with SATA in this thread:
http://forum.doozan.com/read.php?3,16017,19655#msg-19655

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@Bodhi

I've tried pinging the netconsole, no luck. So decided to go with the SATA boot way.

Still no luck!!

This is what I've done for SATA HDD:
1. Format HDD following this [http://forum.doozan.com/read.php?3,16017,19666#msg-19666]
my fdisk-l output:

root@ubuntu-VirtualBox:/mnt# fdisk -l

Disk /dev/sda: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x90300e5f

Device     Boot    Start      End  Sectors  Size Id Type
/dev/sda1  *        2048 14680063 14678016    7G 83 Linux
/dev/sda2       14682110 16775167  2093058 1022M  5 Extended
/dev/sda5       14682112 16775167  2093056 1022M 82 Linux swap / Solaris

Disk /dev/sdb: 55.9 GiB, 60022480896 bytes, 117231408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xa4b694fd

Device     Boot   Start       End   Sectors  Size Id Type
/dev/sdb1          2048   8390655   8388608    4G 83 Linux
/dev/sdb2       8390656 117231407 108840752 51.9G 83 Linux

my disk label:

root@ubuntu-VirtualBox:/mnt# ls -la /dev/disk/by-label
total 0
drwxr-xr-x 2 root root  60 Feb  9 15:23 .
drwxr-xr-x 6 root root 120 Feb  9 15:23 ..
lrwxrwxrwx 1 root root  10 Feb  9 15:23 rootfs -> ../../sdb1

2. extract the [ox820-sata-uboot.tar.gz] to my sdb1, then run the "disk_create" script (from [http://forum.doozan.com/read.php?3,16017,19666#msg-19666])

3. sync

4. sync

5. Plug HDD to the SATA connector on Pogoplug Mainboard.

Let me know where have I gone wrong, please.

Thanks.

@Nate,

Do you have the installation log? It is hard to say what went wrong without seeing exactly what you did.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Bodhi,

This is my install log:
1. fdisk

root@ubuntu-VirtualBox:/home/ubuntu# fdisk /dev/sdb

Welcome to fdisk (util-linux 2.25.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/sdb: 55.9 GiB, 60022480896 bytes, 117231408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xa4b694fd

Device     Boot   Start       End   Sectors  Size Id Type
/dev/sdb1          2048   8390655   8388608    4G 83 Linux
/dev/sdb2       8390656 117231407 108840752 51.9G 83 Linux


Command (m for help): o
Created a new DOS disklabel with disk identifier 0x7133f033.

Command (m for help): n
Partition type
   p   primary (0 primary, 0 extended, 4 free)
   e   extended (container for logical partitions)
Select (default p):

Using default response p.
Partition number (1-4, default 1):
First sector (2048-117231407, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-117231407, default 117231407): +4G

Created a new partition 1 of type 'Linux' and of size 4 GiB.

Command (m for help): n
Partition type
   p   primary (1 primary, 0 extended, 3 free)
   e   extended (container for logical partitions)
Select (default p):

Using default response p.
Partition number (2-4, default 2):
First sector (8390656-117231407, default 8390656):
Last sector, +sectors or +size{K,M,G,T,P} (8390656-117231407, default 117231407):

Created a new partition 2 of type 'Linux' and of size 51.9 GiB.

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

root@ubuntu-VirtualBox:/home/ubuntu# sync

2. Drive Formatting

root@ubuntu-VirtualBox:/home/ubuntu# mkfs.ext4 -L 'rootfs' /dev/sdb1
mke2fs 1.42.10 (18-May-2014)
/dev/sdb1 contains a ext3 file system labelled 'rootfs'
        last mounted on /media/ubuntu/rootfs on Mon Feb  9 18:08:16 2015
Proceed anyway? (y,n) y
Creating filesystem with 1048576 4k blocks and 262144 inodes
Filesystem UUID: b3aefd91-af8b-4d20-aa9c-ced7dc206e8e
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

root@ubuntu-VirtualBox:/home/ubuntu# mkfs.ext4 /dev/sdb2
mke2fs 1.42.10 (18-May-2014)
/dev/sdb2 contains a ext3 file system
        last mounted on Mon Feb  9 18:08:16 2015
Proceed anyway? (y,n) y
Creating filesystem with 13605094 4k blocks and 3407872 inodes
Filesystem UUID: d2bca4cd-af6d-402b-bfd7-d5b4b0f647da
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

root@ubuntu-VirtualBox:/home/ubuntu# sync

3. u-boot

root@ubuntu-VirtualBox:/home/ubuntu# mount /dev/sdb1 /mnt/sdb1
root@ubuntu-VirtualBox:/home/ubuntu# cp ox820-sata-uboot.tar.gz /mnt/sdb1
root@ubuntu-VirtualBox:/home/ubuntu# cd /mnt/sdb1/
root@ubuntu-VirtualBox:/mnt/sdb1# tar -zxvf ox820-sata-uboot.tar.gz
boot/
boot/uImage_2.6.31.14_OX820_1.2_shv.Pro
boot/u-boot.img
boot/u-boot.env
boot/uInitrd
boot/dts/
boot/dts/ox820-pogoplug-pro.dtb
boot/uImage
boot/u-boot-spl.bin
root@ubuntu-VirtualBox:/mnt/sdb1# ls
boot  lost+found  ox820-sata-uboot.tar.gz
root@ubuntu-VirtualBox:/mnt/sdb1#sync

4. disk_create script

root@ubuntu-VirtualBox:/mnt/sdb1# vi disk_create
root@ubuntu-VirtualBox:/mnt/sdb1# cat disk_create
#!/bin/sh

# uncomment line below and set to the correct disk
disk=/dev/sdb1

if [ -z "${disk}" ] ; then
   echo "You must uncomment/set the 'disk' variable"
   exit -1
fi

workarea="boot"

stage1File=$workarea/u-boot-spl.bin

perl <<EOF | dd of="$disk" bs=512
    print "\x00" x 0x1a4;
    print "\x00\x5f\x01\x00";
    print "\x00\xdf\x00\x00";
    print "\x00\x80\x00\x00";
    print "\x00" x (0x1b0 -0x1a4 -12 );
    print "\x22\x80\x00\x00";
    print "\x22\x00\x00\x00";
    print "\x00\x80\x00\x00";
EOF

if [ -f $stage1File ];then
        echo "Writing stage 1"
        dd if=$stage1File    of="$disk" bs=512 seek=34
fi
root@ubuntu-VirtualBox:/mnt/sdb1# sync
root@ubuntu-VirtualBox:/mnt/sdb1# ./disk_create
0+1 records in
0+1 records out
444 bytes (444 B) copied, 0.0052846 s, 84.0 kB/s
Writing stage 1
62+1 records in
62+1 records out
32120 bytes (32 kB) copied, 0.157186 s, 204 kB/s
root@ubuntu-VirtualBox:/mnt/sdb1# sync

5. rootfs

oot@ubuntu-VirtualBox:/mnt/sdb1# cd /home/ubuntu
root@ubuntu-VirtualBox:/home/ubuntu# cp Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 /mnt/sdb1
root@ubuntu-VirtualBox:/gome/ubuntu# cd /mnt/sdb1
root@ubuntu-VirtualBox:/mnt/sdb1# ls
boot                                            lost+found
Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2  ox820-sata-uboot.tar.gz
disk_create
root@ubuntu-VirtualBox:/mnt/sdb1# tar -xjf Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
root@ubuntu-VirtualBox:/mnt/sdb1# ls
bin                                             ox820-sata-uboot.tar.gz
boot                                            proc
Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2  root
dev                                             run
disk_create                                     sbin
etc                                             selinux
home                                            srv
lib                                             sys
lost+found                                      tmp
media                                           usr
mnt                                             var
opt
root@ubuntu-VirtualBox:/mnt/sdb1# sync
root@ubuntu-VirtualBox:/mnt/sdb1# cd ..
root@ubuntu-VirtualBox:/mnt# umount sdb1

@Nate,

I've noticed you did not state what u-boot envs were modified. What is the content of u-boot-env.txt?

You can compare notes with what morph027 did to make it work here:
http://forum.doozan.com/read.php?3,16017,19707#msg-19707

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Bodhi,

Do you know where can I get mkenvimage?

I've installed u-boot-tools on my ubuntu box, couldn't find mkenvimage though...

Nate,

I've attached the mkenvimage tar file here. It is part of u-boot build (it's not available in Debian repo).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 02/10/2015 09:22PM by bodhi.

Bodhi,

I got this error when running mkenvimage:

root@ubuntu-VirtualBox:/mnt/sdb1/boot# ./mkenvimage -s 16384 -o u-boot.env u-boot-env.txt
bash: ./mkenvimage: cannot execute binary file: Exec format error

Nate Wrote:
-------------------------------------------------------
> Bodhi,
>
> I got this error when running mkenvimage:
>

> root@ubuntu-VirtualBox:/mnt/sdb1/boot#
> ./mkenvimage -s 16384 -o u-boot.env
> u-boot-env.txt
> bash: ./mkenvimage: cannot execute binary file:
> Exec format error
>

Ah! This binary is ARM (compiled on Kirkwood). So you can't run it on Ubuntu (if it's x386).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hmm,

Don't think Virtualbox can do ARM emulation....

do you think if I use raspberry pi, I can get this to work?

Yes, you can run it on the rPi.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Bodhi,

Ran the mkenvimage on my rPi...no error whatsoever.
tried to plug the ssd-sata to pogo.....

same thing...green blink, orange blink, green blink, orange blink, orange stay.

Damn......

Do you have any idea what should I do? :(((

@Nate,

I think you best next step is to:

- See what robert did here:
http://forum.doozan.com/read.php?3,16017,19718#msg-19718

Try using robert's u-boot envs file.

- If it still fail, connect serial console.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 02/11/2015 07:26AM by bodhi.

Kernel linux-3.18.5-oxnas-tld-1 package was uploaded. Please see 1st post for download link.

The following features are new in this version:

- Added various kernel configuration that are newly available in 3.18, and also various kernel configuration per forum users requests: loop device, stock wifi supports, encrypted fs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> Kernel linux-3.18.5-oxnas-tld-1 package was
> uploaded. Please see 1st post for download link.
>
> The following features are new in this version:
>
> - Added various kernel configuration that are
> newly available in 3.18, and also various kernel
> configuration per forum users requests: loop
> device, stock wifi supports, encrypted fs.

With 3.18, does stock wifi (i.e. Realtek RT3390sta) work our of the box now? If so that would be awesome!



Edited 4 time(s). Last edit at 02/13/2015 07:23AM by LeggoMyEggo.

LeggoMyEggo,

This update includes the config CONFIG_CFG80211_WEXT, that was omitted. A few people have reported this particular config missing that cause problem with the supplicant . I suspect that the problem also has something to do with the updated Realtek drivers in kernel 3.17+.

Please try. I don't have the wifi card installed in my Pogo Pro currently so can't test it. If this did not help then perhaps I will have put that back in and troubleshoot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> Please try. I don't have the wifi card installed
> in my Pogo Pro currently so can't test it. If this
> did not help then perhaps I will have put that
> back in and troubleshoot.

OK, will put that on the todo list. I had actually purchased a used Atheros 9k N300 compatible card from an eBay seller from Asia but the boat it's on must be taking the scenic route:) Hoping the Realtek will work for now. Last time I tried I placed the RT3390sta.ko I copied from Shv's rootfs to /lib/modules/...., created /etc/Wireless/RT2860 directory and copied RT2860.DAT into it and when I tried to do a modprobe, I think I got a Execution error of some sort. So I kind of gave up after 5 total hours trying to get it to work. I also tried to compile it from source and that was a no go as I don't know how to cross compile and as you point out I might have needed the missing config file. Let's hope for the best this time.

Edit 3 hour later: Just loaded 3.18 over my 3.17 disk. Boots fine but stock Realtek wifi does not respond to modprobe rt3390sta.ko or rt3390sta. Also tried modprobe rt2800pci. rt3390sta does not show up in lsmod.



Edited 3 time(s). Last edit at 02/13/2015 07:00PM by LeggoMyEggo.

hi bodhi

Where can i download initramfs-3.18.5-oxnas-tld-1

many thx for your prebuild Uboot and the linux system

dump,

When you install kernel with dpkg, initramfs-3.18.5-oxnas-tld-1 will be generated automatically.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

LeggoMyEggo,

> Edit 3 hour later: Just loaded 3.18 over my 3.17
> disk. Boots fine but stock Realtek wifi does not
> respond to modprobe rt3390sta.ko or rt3390sta.
> Also tried modprobe rt2800pci. rt3390sta does not
> show up in lsmod.

What was the error when you did modprobe?

Look for the module see if you can find it:

find /lib/modules/ -name '*3390*'
find /lib/modules/ -name 'rt*'

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 02/14/2015 02:23PM by bodhi.

bodhi,

thank you so so much for your latest kernel (once again). I am really grateful for all your work!

I just upgraded to your 3.18.5 kernel. I have a question: is there support for bluetooth devices? My goal is to setup a bluetooth a2dp audio sink and output audio through a connected usb soundcard. Using the lsusb command i can see that my bluetooth receiver is properly recognized:

Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

but nothing happens more than that. I tried to modprobe bluetooth and bluez kernel module, but it seems they are not compiled. Do you have any idea how this could work? As soon as i find some time, i will try to compile the kernel modules in order to manually probe them.

@denexo,

Let me double check, bluetooth is fully supported on the Kirkwood boxes, but I'm not sure I had it compiled on the Pogo V3.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@denexo,

> I tried to
> modprobe bluetooth and bluez kernel module, but it
> seems they are not compiled. Do you have any idea
> how this could work? As soon as i find some time,
> i will try to compile the kernel modules in order
> to manually probe them.

Confirmed, bluetooth was not compiled in the OXNAS kernel. Pls try compile the modules to see if it will work. I'll add BT in the next release.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> Pls try compile the modules to see if it will work.

And if you succeed pls tell us how you did it :)



Edited 2 time(s). Last edit at 02/25/2015 05:29PM by LeggoMyEggo.

For anyone trying to get internal wifi to work with their Oxnas PP (Pro w/mPCIe), I just replaced the stock Realtek RT3090 card with an Atheros AR5B93 card and it loaded with the drivers built into 3.18.5. I also tried an Atheros AR5B225 and it worked without issue as well. Both use the Ath9k firmware / drivers and both are available for less than $5 off of eBay if you are willing to wait a couple weeks. It's nice having internal wifi working as it frees up a USB slot. I'm currently using my Pro as a wireless Squeezelite and Shairplay device with a cheapo Sabrent USB audio card (USB-AUDD). The audio card worked with the stock firmware as well although I did have to tell asound.conf to use USB audio as the default (snd_usb_audio index=0) in order to get alsamixer to work to set the volumes.



Edited 2 time(s). Last edit at 02/27/2015 06:23AM by LeggoMyEggo.

Hello all, having some trouble.

I simply want to get Wheezy running off USB on my Pogoplug Classic (P21). Here is what I did so far:

-I followed the instructions here: http://archlinuxarm.org/platforms/armv6/pogoplug-v3oxnas-eol (Under installation)

-I followed the instructions in this thread for a rootfs build. Formatted a flashkey ext3, named it rootfs, uzipped the file, dblchecked the fstab showed ext3, ran the mkimage commands, synced, unmounted, done.

The device doesn't want to boot up.

All I want is a debian system, and I don't have jtag/serial equipment, so I felt like staying with the default uboot. From my understanding this should work.

The only thing I can think of is:
-I am preparing the rootfs flashkey wrong somehow, or
-My bootloader is wrong on the mtdblock

Here is a blparam

[root@alarm bin]# ./blparam 
bootdelay=2
baudrate=115200
autoload=n
netmask=255.255.0.0
bootfile="uImage"
kernflmode=s
load_nand=nboot 60500000 0 200000
load_nand2=nboot 60500000 0 800000
boot=bootm 60500000
boot_nand=run load_nand boot || run load_nand2 boot
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:25:31:02:94:4D
cesvcid=2NBD9UVLL5X5RF63QW5QYKW3TE
ceboardver=PPV3
serverip=192.168.1.20
ipaddr=192.168.1.122
bootargs_stock=root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes
load_custom_nand=nboot 60500000 0 500000
load_custom_nand2=nboot 60500000 0 B00000
boot_custom=run load_custom_nand boot || run load_custom_nand2 boot
bootargs=root=/dev/sda1 ubi.mtd=2,512 rootfstype=ext3 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes rootwait
bootcmd=run boot_custom

From that I can see it is going to look for /dev/sda1 and expect it to be ext3, and boot from that (like it does from this default old ALARM one), but it doesnt.

What am I missing?

tufkal,

You are stiil trying to boot with the old kernel in NAND. There is no need to do that. The new rootfs has the latest Debian kernel.

So this needs to change

boot_custom=run load_custom_nand boot || run load_custom_nand2 boot
bootargs=root=/dev/sda1 ubi.mtd=2,512 rootfstype=ext3 console=ttyS0,115200 elev
ator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes rootwait
bootcmd=run boot_custom

The booting envs need to have settings that will load kernel from the usb rootfs, similar to this (this is not to be cut/pasted as is, it is for information only)

bootcmd_usb=usb start; run usb_bootcmd; usb stop; reset
usb_bootcmd=run usb_set_bootargs; run usb_boot
usb_boot=run load_uimage; run load_initrd; bootm 0x60500000 0x60a00000
load_initrd=ext2load usb 0:1 0x60a00000 /boot/uInitrd
load_uimage=ext2load usb 0:1 0x60500000 /boot/uImage
bootcmd=run bootcmd_usb

Warning: running stock u-boot without serial console, it is quite easy to lock yourself out of the box by changing u-boot envs to some wrong settings. What you should do is get an envs listing from others who are running the same configuration, and use it. I don't have one that I can post, because I am running with new u-boot. If needed, I have to look at my old log.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> tufkal,
>
> You are stiil trying to boot with the old kernel
> in NAND. There is no need to do that. The new
> rootfs has the latest Debian kernel.
>
> So this needs to change
>

> boot_custom=run load_custom_nand boot || run
> load_custom_nand2 boot
> bootargs=root=/dev/sda1 ubi.mtd=2,512
> rootfstype=ext3 console=ttyS0,115200 elev
> ator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01
> mem=128M poweroutage=yes rootwait
> bootcmd=run boot_custom
>

>
> The booting envs need to have settings that will
> load kernel from the usb rootfs, similar to this
> (this is not to be cut/pasted as is, it is for
> information only)
>

> bootcmd_usb=usb start; run usb_bootcmd; usb stop;
> reset
> usb_bootcmd=run usb_set_bootargs; run usb_boot
> usb_boot=run load_uimage; run load_initrd; bootm
> 0x60500000 0x60a00000
> load_initrd=ext2load usb 0:1 0x60a00000
> /boot/uInitrd
> load_uimage=ext2load usb 0:1 0x60500000
> /boot/uImage
> bootcmd=run bootcmd_usb
>

>
> Warning: running
> stock u-boot without serial console, it is quite
> easy to lock yourself out of the box by changing
> u-boot envs to some wrong settings. What you
> should do is get an envs listing from others who
> are running the same configuration, and use it. I
> don't have one that I can post, because I am
> running with new u-boot. If needed, I have to look
> at my old log.


Thanks for the quick response. I guess I was reading the output of blparam wrong, in (as you said) it is still loading the kernel from NAND. Your red bold text scares me, because as I said I have no serial/JTAG equipment.

Which way is less risky? Getting your newer uboot installed, or giving the old uboot these parameters manually?