installation on ix2-200, unable to boot kernel

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

installation on ix2-200, unable to boot kernel

Postby Abzstrak » Sun Sep 13, 2020 7:14 pm

I've been trying to install Arch on my old IX2-200 following instructions here: https://kiljan.org/2016/11/15/installin ... a-ix2-200/

I cannot get it to boot, I'm completely out of my depths with Arm and could use assistance. After booting and completing all steps through Step 3, the first boot from the device itself with the 5.8 kirkwood kernel results in a boot loop. Here is some a copy and paste of the boot from console:


__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: RD-88F6281A LE

U-Boot 1.1.4 (Sep 8 2009 - 09:31:54) Marvell version: 3.4.14

Mapower version: 2.0 (32MB) (2009/09/08)

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CEE60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1000Mhz L2 running @ 333Mhz
SysClock = 333Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM Total size 256MB 16bit width
Flash: 0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:32 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0, egiga1 [PRIME]
Fan lookup table initialized.

Current remote temperature: 58
Current fan speed: 0

Hit any key to stop autoboot: 0
(Re)start USB...
USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 02000000 ...
Image Name: Arch Linux ARM kernel
Created: 2020-09-13 17:00:03 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 6196752 Bytes = 5.9 MB
Load Address: 02000000
Entry Point: 02000000
Verifying Checksum ... OK
XIP Kernel Image ... OK
## Loading Ramdisk Image at 08004000 ...
Image Name: Arch Linux ARM initrd
Created: 2020-09-13 18:19:02 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 8634042 Bytes = 8.2 MB
Load Address: 08004000
Entry Point: 08004000
Verifying Checksum ... OK

Starting kernel ...

software interrupt
pc : [<00da8aec>] lr : [<0060020c>]
sp : 00600000 ip : 005fd844 fp : 005fd898
r10: 00000000 r9 : 005fe530 r8 : 005fffcc
r7 : 0883fefa r6 : 08004040 r5 : 006460e4 r4 : 00000000
r3 : 02000000 r2 : 00000100 r1 : 00000692 r0 : 00000000
Flags: Nzcv IRQs off FIQs off Mode SVC_32
Resetting CPU ...


__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: RD-88F6281A LE

U-Boot 1.1.4 (Sep 8 2009 - 09:31:54) Marvell version: 3.4.14
Abzstrak
 
Posts: 6
Joined: Sun Sep 13, 2020 7:07 pm

Re: installation on ix2-200, unable to boot kernel

Postby summers » Mon Sep 14, 2020 10:37 am

That looks odd. From what I can see of the link you gave - should have gone further than that.

What it looks like is that the kernel/initramfs is wrong, its bombing out before it prints anything.

In uboot, escaping it and typing $this->bbcode_second_pass_code('', 'printenv') may give us some more idea how your uboot is configured. But anyway I'm confused so far ...

If it helps, what has probably gone wrong is $this->bbcode_second_pass_code('', 'mkimage -A arm -O linux -T ramdisk -C gzip -a 0x08004000 -n "Arch Linux ARM initrd" -d /mnt/boot/initramfs-linux.img /mnt/boot/uInitrd') although whats wrong with it can't say!
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm

Re: installation on ix2-200, unable to boot kernel

Postby summers » Tue Sep 15, 2020 12:37 pm

Ok one thing I havn't been able to work out, but I think I know the answer, is when you pass a initramfs as well as a kernel to bootm, what does bootm start executing. No what I think I'd expect is its the kernel image, and that has a link to the initramfs. Now with that the case, question is is why hasn't the kernel image posted anything to the screen?

Are you sure you are using the kirkwood kernel image? What did you install from?
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm

Re: installation on ix2-200, unable to boot kernel

Postby kriztioan » Tue Sep 15, 2020 4:42 pm

I have been successful in using Kiljan's original guide to get ALARM running on my ix2-200, but subtle things will have changed since I did that a few years back, e.g., the memory layout issue. One thing I had to do then was patch my fw_setenv-command as it guarded against changing ethaddr. Although you might not have come across that if you dropped to the uboot-prompt to change the environment variables.

There are three things that look 'suspicious' to me:

$this->bbcode_list('1')
  • The ** Bad partiion 1 ** messages.
  • No indication when or where from the images are loaded; see e.g., the boot log from viewtopic.php?f=53&t=13477&p=61065#p60776, albeit that I load my system from USB.
  • The XIP Kernel Image ... OK message.
  • As @summers asks, are you sure you're using the kirkwood-image?

    My first suggestion would be, while cumbersome, to start over. If that still fails, my second suggestion would be to try and get a USB to boot as that avoids the hassle from continuously changing out the disks. Finally, I'd suggest dropping to the uboot-prompt, inspecting the uboot environment and manually try booting the system.

    Know that, at least for me, running ALARM on the ix2-200 has been great. Especially when running it off a USB, which keeps the disks from spinning up unnecessarily, it almost doesn't draw any wattage. For sure, it is not a power-house, but for a simple media library and some simple always-on services it more than suffices. In short, its worth the effort.

    Good luck!
    kriztioan
     
    Posts: 51
    Joined: Sat Apr 29, 2017 1:32 am

    Re: installation on ix2-200, unable to boot kernel

    Postby Abzstrak » Wed Sep 16, 2020 11:46 pm

    yeah, I've started over 4 times now, and I'm using a USB... The initial boot works fine, once I switch to the kirkwood dt kernel, everything goes to crap.


    I'm using linux-kirkwood-dt, which, according to his instructions is modified on the USB before being rsync'd over to the drives... The USB boots fine on kirkwood, but no longer works on kirkwood-dt.... does exactly as I pasted above.

    I'm wondering how bad I really need kirkwood-dt , lol
    Last edited by Abzstrak on Wed Sep 16, 2020 11:54 pm, edited 1 time in total.
    Abzstrak
     
    Posts: 6
    Joined: Sun Sep 13, 2020 7:07 pm

    Re: installation on ix2-200, unable to boot kernel

    Postby Abzstrak » Wed Sep 16, 2020 11:52 pm

    here is the printenv -


    Marvell>> printenv
    baudrate=115200
    loads_echo=0
    ipaddr=10.4.50.165
    serverip=10.4.50.5
    rootpath=/mnt/ARM_FS/
    netmask=255.255.255.0
    console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1f00000@0x100000(root)
    CASset=min
    MALLOC_len=1
    ethprime=egiga1
    bootargs_end=:::DB88FXX81:eth0:none
    image_name=uImage
    standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
    ethmtu=1500
    eth1addr=00:50:43:3e:1e:38
    eth1mtu=1500
    mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
    mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
    usb0Mode=host
    yuk_ethaddr=00:00:00:EE:51:81
    nandEcc=1bit
    netretry=no
    rcvrip=169.254.100.100
    loadaddr=0x02000000
    autoload=no
    FanHysteresis=2
    FanTempStart=58
    uboot_start=0x0
    uboot_size=0xc0000
    env_start=0xa0000
    env_size=0x20000
    kernel_start=0x100000
    kernel_size=0x300000
    initrd_start=0x540000
    initrd_size=0x300000
    flash_load=run make_boot_args load1 load2 boot
    load1=nand read.e 0x2000000 $(kernel_start) $(kernel_size)
    load2=nand read.e 0x4500000 $(initrd_start) $(initrd_size)
    boot=bootm 0x2000000 0x4500000
    make_boot_args=setenv bootargs console=ttyS0,115200 mtdparts=nand_mtd:;setenv bootargs $(bootargs)$(uboot_size)@$(uboot_start)(uboot),;setenv bootargs $(bootargs)$(env_size)@$(env_sta;
    iomega=123
    ethaddr=AA:00:00:00:00:01
    arcNumber=1682
    bootargs_console=console=ttyS0,115200
    bootargs_mtdparts=mtdparts=orion_nand:640k(u-boot)ro,16k(u-boot-env),-(iomega-firmware)ro
    bootargs_root=root=LABEL=ROOT rw
    bootargs_combine=setenv bootargs ${bootargs_console} ${bootargs_mtdparts} ${bootargs_root}
    bootlinux=bootm ${memoffset_kernel} ${memoffset_initrd}
    usb_load_firstdevice=ext2load usb 0:1 ${memoffset_kernel} /uImage; ext2load usb 0:1 ${memoffset_initrd} /uInitrd
    usb_load=run bootargs_combine; usb reset; run usb_load_firstdevice; run bootlinux
    sata_load_disk1=ext2load ide 0:1 ${memoffset_kernel} /uImage; ext2load ide 0:1 ${memoffset_initrd} /uInitrd
    sata_load_disk2=ext2load ide 1:1 ${memoffset_kernel} /uImage; ext2load ide 1:1 ${memoffset_initrd} /uInitrd
    sata_load=run bootargs_combine; ide reset; run sata_load_disk1; run sata_load_disk2; run bootlinux
    bootcmd=run usb_load; run sata_load
    memoffset_kernel=0x02000000
    memoffset_initrd=0x08004000
    stdin=serial
    stdout=serial
    stderr=serial
    mainlineLinux=yes
    enaMonExt=no
    enaCpuStream=no
    enaWrAllo=no
    pexMode=RC
    disL2Cache=no
    setL2CacheWT=yes
    disL2Prefetch=yes
    enaICPref=yes
    enaDCPref=yes
    sata_dma_mode=yes
    netbsd_en=no
    vxworks_en=no
    bootdelay=3
    disaMvPnp=no
    hddPowerCtrl=no
    enaAutoRecovery=yes
    ethact=egiga1

    Environment size: 2776/16380 bytes
    Marvell>>
    Abzstrak
     
    Posts: 6
    Joined: Sun Sep 13, 2020 7:07 pm

    Re: installation on ix2-200, unable to boot kernel

    Postby Abzstrak » Wed Sep 16, 2020 11:57 pm

    I appreciate the ideas. Booting from USB is not a terrible idea.... I am just going to run this little box to spin up at not and rsync over some backups to. Its too slow for anything useful, now it's just frustrating. I ran Arch on it a long time ago, I do remember having trouble with it spinning up all the time, and running hotter due to that. I have a couple 2TB 7200rpm drives in here, so... not ideal.

    I probably wont get any more time to play with it until this next weekend, but I'll update in case any else runs into similar issues.
    Abzstrak
     
    Posts: 6
    Joined: Sun Sep 13, 2020 7:07 pm

    Re: installation on ix2-200, unable to boot kernel

    Postby kriztioan » Thu Sep 17, 2020 2:16 am

    Good to know that you at least make it through booting the none-dt kernel, which shows your uboot-environment is OK.

    Using the none-dt kernel for simple things is probably fine; the cryptodev module access you'd gain stopped working with ssh for me a while ago and it depends on how bad you want your buttons and front LEDs to work.

    As it looks like things go wrong when upgrading to the dt-kernel, I'd make triple-sure those steps are correct, e.g., are you using the >>-operator when appending the device tree, is there enough space on the boot-partition, does the mkimage-command have the correct arguments, etc.

    As a straight-forward test, I'll pm you a link to a copy of the 5.8.9-1 kernel-dt-image from my ix2-200 ;of course, use at your own risk.
    kriztioan
     
    Posts: 51
    Joined: Sat Apr 29, 2017 1:32 am

    Re: installation on ix2-200, unable to boot kernel

    Postby Abzstrak » Thu Sep 17, 2020 3:24 am

    everytime I try to quote on here, it says the topic is too old, really annoying....

    anyway, I got the pm, thank you.
    Abzstrak
     
    Posts: 6
    Joined: Sun Sep 13, 2020 7:07 pm

    Re: installation on ix2-200, unable to boot kernel

    Postby Abzstrak » Thu Sep 17, 2020 3:32 am

    so I was copying and pasting into console off his site, to prevent any typos....

    but I see he made a typo with the load offset for the dt kernel mkimage. so.... I'll have to try it with the correct offset... I suspect that's all it is. I suspect he forgot to update that line after the 5.0 kernel changes for memory offsets. If it works, I'll email him so he can update the site.
    Abzstrak
     
    Posts: 6
    Joined: Sun Sep 13, 2020 7:07 pm

    Next

    Return to Marvell Kirkwood

    Who is online

    Users browsing this forum: No registered users and 9 guests