OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio

IPB

Welcome Guest ( Log In | Register )

3 Pages V  < 1 2 3  
Reply to this topicStart new topic
> Linux Kernel 4.4.0, Experimental Kernel Build for Sharp Zaurus C3x00
ArchiMark
post Oct 29 2016, 10:24 AM
Post #31





Group: Admin
Posts: 1,649
Joined: 25-June 03
From: Silicon Valley
Member No.: 208



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.........
Go to the top of the page
 
+Quote Post
greguu
post Oct 29 2016, 12:00 PM
Post #32





Group: Moderators
Posts: 374
Joined: 14-November 05
From: New Zealand
Member No.: 8,535



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.
Go to the top of the page
 
+Quote Post
ArchiMark
post Oct 29 2016, 04:27 PM
Post #33





Group: Admin
Posts: 1,649
Joined: 25-June 03
From: Silicon Valley
Member No.: 208



QUOTE(greguu @ Oct 29 2016, 01:00 PM) *
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....

QUOTE
Are you using kexecboot from archlinux or OE ?


Whatever was included in your instructions.


QUOTE
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.
Go to the top of the page
 
+Quote Post
greguu
post Oct 29 2016, 08:06 PM
Post #34





Group: Moderators
Posts: 374
Joined: 14-November 05
From: New Zealand
Member No.: 8,535



QUOTE(ArchiMark @ Oct 30 2016, 01:27 AM) *
QUOTE(greguu @ Oct 29 2016, 01:00 PM) *
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....

QUOTE
Are you using kexecboot from archlinux or OE ?


Whatever was included in your instructions.


QUOTE
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
mount /dev/sda1 /mnt
nano /mnt/boot/boot.cfg


Example boot.cfg for single kernel boot from sda1 on ext4:

CODE
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
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.
Go to the top of the page
 
+Quote Post
ArchiMark
post Oct 31 2016, 08:01 AM
Post #35





Group: Admin
Posts: 1,649
Joined: 25-June 03
From: Silicon Valley
Member No.: 208



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
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.....

biggrin.gif

This post has been edited by ArchiMark: Oct 31 2016, 08:08 AM
Reason for edit: Added UPDATE
Go to the top of the page
 
+Quote Post
p0c
post Oct 31 2016, 08:07 AM
Post #36





Group: Members
Posts: 3
Joined: 31-October 16
Member No.: 795,594



QUOTE(ArchiMark @ Oct 31 2016, 07:01 PM) *
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
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)..
Go to the top of the page
 
+Quote Post
ArchiMark
post Oct 31 2016, 08:24 AM
Post #37





Group: Admin
Posts: 1,649
Joined: 25-June 03
From: Silicon Valley
Member No.: 208



QUOTE(p0c @ Oct 31 2016, 09:07 AM) *
QUOTE(ArchiMark @ Oct 31 2016, 07:01 PM) *
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
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?

smile.gif
Go to the top of the page
 
+Quote Post
greguu
post Oct 31 2016, 01:20 PM
Post #38





Group: Moderators
Posts: 374
Joined: 14-November 05
From: New Zealand
Member No.: 8,535



QUOTE(ArchiMark @ Oct 31 2016, 05:24 PM) *
QUOTE(p0c @ Oct 31 2016, 09:07 AM) *
QUOTE(ArchiMark @ Oct 31 2016, 07:01 PM) *
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
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?

smile.gif


Up to you. There may some unknown issues. You can add it as a secondary boot option.
Go to the top of the page
 
+Quote Post

3 Pages V  < 1 2 3
Reply to this topicStart new topic
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st November 2019 - 07:12 AM