Linux Kernel 4.4.0

[ArchiMark]

Just tried booting without any cards in slots.....

Same situation....

Selected Arch and then nothing happens.....

Just realized I left all my other SD cards at office....so, won't be able to see if I have the card I used to install Arch until Monday....

Oh well.........

[greguu]

I the boot.cfg file from the tar.xz is configured for archlinux's kexecboot and looks for a kernel on a SD card only.

If you copied the boot.cfg file over the boot.cfg on your CF card it will not boot and may cause the issue you are experiencing.

Are you using kexecboot from archlinux or OE ? You can use the rootfs tar from github to create a boot SD card and fix you boot.cfg on our CF card.

[ArchiMark]

I the boot.cfg file from the tar.xz is configured for archlinux's kexecboot and looks for a kernel on a SD card only.

If you copied the boot.cfg file over the boot.cfg on your CF card it will not boot and may cause the issue you are experiencing.

OK, understand....

Are you using kexecboot from archlinux or OE ?

Whatever was included in your instructions.

You can use the rootfs tar from github to create a boot SD card and fix you boot.cfg on our CF card.

Thanks for the suggestion.

[greguu]

I the boot.cfg file from the tar.xz is configured for archlinux's kexecboot and looks for a kernel on a SD card only.

If you copied the boot.cfg file over the boot.cfg on your CF card it will not boot and may cause the issue you are experiencing.

OK, understand....

Are you using kexecboot from archlinux or OE ?

Whatever was included in your instructions.

You can use the rootfs tar from github to create a boot SD card and fix you boot.cfg on our CF card.

Thanks for the suggestion.

So to get you going again:

I assume your CF partition is ext4 for sda1 and your alarmz root and you did copy the new kernel to the right location on you CF card, including the kernel modules.

Follow Dan's guide to create an arch SD card : https://github.com/danboid/ZALARM-install

Insert the SD card and turn on the Zaurus.

Boot from the SD card. Kexecboot should list the kernel.

Once logged on as root mount your CF card and edit boot.cfg

Code: [Select]

mount /dev/sda1 /mnt
nano /mnt/boot/boot.cfg
Example boot.cfg for single kernel boot from sda1 on ext4:

Code: [Select]

LABEL=ArchLinux
KERNEL=/boot/zImage-4.4.0-cxx00
APPEND=root=/dev/sda1 rootfstype=ext4 fbcon=rotate:1 noinitrd loglevel=3
Then exit the editor and unmount and reboot.

Code: [Select]

unmount /mnt
reboot
Then remove the SD card and fingers crossed you can boot back into you arch on the CF card.

Hope this helps.

I recommend before doing an kernel upgrade to do a backup first and more importantly have recovery partition or SD card handy for situations like this.

[ArchiMark]

Tried booting up with SD card....

Kexecboot does not list it at the selection screen....

Selected System Tools and then Debug Info....

See the following regarding the SD card:

Code: [Select]

Found device '/dev/mmcblk0' (179, 0) of size 970Mb
+ creating device node
+ can't identify FS type
Hmmm........I formatted card as EXT4.....

I checked card to see that all the directories were there......

Maybe bad card?

UPDATE

Found the SD card that I used originally to install ALARMZ before....

It is recognized in kexecboot.....yeah!

It's booting up Z now.....

 

[p0c]

Tried booting up with SD card....

Kexecboot does not list it at the selection screen....

Selected System Tools and then Debug Info....

See the following regarding the SD card:

Code: [Select]

Found device '/dev/mmcblk0' (179, 0) of size 970Mb
+ creating device node
+ can't identify FS type
Hmmm........I formatted card as EXT4.....

I checked card to see that all the directories were there......

Maybe bad card?

Please scroll down a bit in the debug log, as it should contain information regarding the first partition I think (/dev/mmcblk0p1)..

[ArchiMark]

Tried booting up with SD card....

Kexecboot does not list it at the selection screen....

Selected System Tools and then Debug Info....

See the following regarding the SD card:

Code: [Select]

Found device '/dev/mmcblk0' (179, 0) of size 970Mb
+ creating device node
+ can't identify FS type
Hmmm........I formatted card as EXT4.....

I checked card to see that all the directories were there......

Maybe bad card?

Please scroll down a bit in the debug log, as it should contain information regarding the first partition I think (/dev/mmcblk0p1)..

Thank you for your help, p0c.....

And welcome to the club.....

Didn't see your post until after I edited my post above...

So, already booted up with my other SD card.....

Strange thing is that even though I used my SD card to boot up, it booted up into login screen and then into Fluxbox which is all installed on my internal CF card.

Edited boot.cfg and rebooted....

Now it boots up OK and only error message is about swap which makes sense as I now need to redo SD card to be swap again.

Whew!


@Greg

Should I try your new updated kernel?

 

[greguu]

Tried booting up with SD card....

Kexecboot does not list it at the selection screen....

Selected System Tools and then Debug Info....

See the following regarding the SD card:

Code: [Select]

Found device '/dev/mmcblk0' (179, 0) of size 970Mb
+ creating device node
+ can't identify FS type
Hmmm........I formatted card as EXT4.....

I checked card to see that all the directories were there......

Maybe bad card?

Please scroll down a bit in the debug log, as it should contain information regarding the first partition I think (/dev/mmcblk0p1)..

Thank you for your help, p0c.....

And welcome to the club.....

Didn't see your post until after I edited my post above...

So, already booted up with my other SD card.....

Strange thing is that even though I used my SD card to boot up, it booted up into login screen and then into Fluxbox which is all installed on my internal CF card.

Edited boot.cfg and rebooted....

Now it boots up OK and only error message is about swap which makes sense as I now need to redo SD card to be swap again.

Whew!


@Greg

Should I try your new updated kernel?

 

Up to you. There may some unknown issues. You can add it as a secondary boot option.