Archlinuxarm On C3x00

[TheWalt]

Are we closer to five eyes? We need ZALARM users from Canada and Australia to complete the five. Where do you live Walt?

On a clear day I can see Canada from across Lake Erie in Ohio, does that count?  

[danboid]

3.2 to match our internal CF drive capacity or 3.3 eyes at a push to go with the real 5 eyes undoubted Masonic leanings  

[danboid]

Has anyone tried a >=64GB CF card with their Z yet?

[ArchiMark]

3.2 to match our internal CF drive capacity or 3.3 eyes at a push to go with the real 5 eyes undoubted Masonic leanings  

Hmmm.....something to look forward to!.....

Should I dust off my decoder ring?

Has anyone tried a >=64GB CF card with their Z yet?

Not yet.....

I'm still enjoying all the space with 32GB card versus the dinky 6GB MB I just yanked out....

 

[danboid]

Should I dust off my decoder ring?

We should have a decoder ring as the ALARMZ 'mascot' / logo.

[tux]

Has anyone tried a >=64GB CF card with their Z yet?

Saw the posts about putting a CF card into the Z. iamasmith documented the process in 2006 on here. I hope the link I include will take you there. Seems clearer and more detailed than the link in this thread?


 iamasmith's posts about CF card

[ArchiMark]

Should I dust off my decoder ring?

We should have a decoder ring as the ALARMZ 'mascot' / logo.

Great idea!.....So, we'll have 3.2 eyes on it?

Has anyone tried a >=64GB CF card with their Z yet?

Saw the posts about putting a CF card into the Z. iamasmith documented the process in 2006 on here. I hope the link I include will take you there. Seems clearer and more detailed than the link in this thread?


 iamasmith's posts about CF card

Where were you yesterday, tux, when I was trying to take apart my Z???    

Great post and pics.....

Thanks, for sharing this. Should help Walt and others that come along.......

or when I put in a 256GB CF card and need to open it up again...

 

[ArchiMark]

A question please...

Time & Date - Timezone

Want to get time correct....date is one day behind and time of day is off.

When I check it, I get:

Code: [Select]

# timedatectl
   Local time:     Thu 2015-10-29 14:06:33 UTC
Universal time:  Thu 2015-10-29 14:06:33 UTC
    RTC time:      Sat 2000-01-01 00:16:50
  Time zone:      UTC (UTC, +0000)
Network time on:  yes
NTP synchronized: no
  RTC in local TZ: no
When I try to set local timezone, I get:

Code: [Select]

# timedatectl set-timezone America/Los_Angeles
Failed to set time zone: Access denied
Seems odd since I logged in as root.....but I did read on Arch wiki, to try reinstalling tzdata and then set timezone....

Any suggestion to change timezone and set proper time?  

Use ntp or ?

Thanks!

[ArchiMark]

Have more serious issue now....

Hope there's a relatively simple fix....

I thought I had put the systemd related pkg names in /etc/pacman.conf on the IgnorePkg line as instructed here.

I did, later came to realize I had forgot to uncomment that line.....  

So, when I did 'pacman -Syu' I noticed midway that it was starting to update systemd......panicked and did ctrl-C to stop process thinking it would not update it if process was halted. However, it must have done some updating as I noticed strange behavior afterwards. For example, when I did 'poweroff' it failed.

So, thought I would downgrade systemd again with the files provided here as I did before. But would not work this time.

Do 'pacman -U systemd-226-3-arm.pkg.tar.xz', then it starts process, but I get error messages:

Code: [Select]

# pacman -U systemd-226-3-arm.pkg.tar.xz
loading packages...
warning: downgrading package systemd (226-3.2 => 226-3)
resolving dependencies...
looking for conflicting packages....
error: could not open file /var/lib/pacman/local/systemd-226-3.2/desc: No such file or directory

Packages (1) systemd-226-3

Total Installed Size:  68.27 MiB

:: Proceed with installation? [Y/n]
If I say Yes, then it starts, but get error messages at each line saying that the item referred to 'exists in filesystem'
Then says at end 'Errors occurred, no packages were upgraded.'

I shutdown system by removing battery and restarted. Of course, won't boot up now with system on internal CF card.

So, put in my SD card with Arch on it and have now booted up Z and chrooted into the CF Card. But still get same error messages when doing 'pacman - U systemd-226-3-arm.pkg.tar.xz'......

Any suggestions as to how to get pacman to do the downgrade?

Or have I borked system to where I need to start with fresh install again?

Thanks.

[ArchiMark]

So tried with --force to see if I could downgrade, but I get other messages now:

 

Code: [Select]

        # pacman -U --force systemd-226-3-arm.pkg.tar.xz
        loading packages...
        warning: downgrading package systemd (226-3.2 => 226-3)
        resolving dependencies...
        looking for conflicting packages....
        error: could not open file /var/lib/pacman/local/systemd-226-3.2/desc: No such file or directory

        Packages (1) systemd-226-3

        Total Installed Size:  68.27 MiB

        :: Proceed with installation? [Y/n]
    (1/1) checking keys in keyring      [*********] 100%
    (1/1) checking package integrity  [*********] 100%
    (1/1) loading package files           [*********] 100%
    (1/1) checking for file conflicts    [*********] 100%
    error: could not open file:  /etc/mtab:  No such file or directory
    error: could not determine filesystem mount points
    error: not enough free disk space
    error: failed to commit transaction (unexpected error)
    Errors occurred, no packages were upgraded.

Any suggestions now ?

Thanks!

[danboid]

I've not got much useful to suggest really other than to point out 226-3.2 coud actually have worked OK if you had let it fully install as it was 227 that had issues. Maybe 226-3 is fine?

I would imagine that cancelling midway through a systemd upgrade / downgrade wouldn't go down well as I think systemd is prob the biggest single package on most Arch systems.

[ArchiMark]

I've not got much useful to suggest really other than to point out 226-3.2 coud actually have worked OK if you had let it fully install as it was 227 that had issues. Maybe 226-3 is fine?

I see your point about 226-3.2 now...but when I saw that systemd was on verge of updating, I panicked a bit thinking it was updating to 227...and figured I'd better stop it immediately....
seemed like a good idea at the moment.....    

I would imagine that cancelling midway through a systemd upgrade / downgrade wouldn't go down well as I think systemd is prob the biggest single package on most Arch systems.

Yep, agree......but too late now.....  

 


Seems like it's reinstall Arch time.....

[ArchiMark]

Want to reinstall Arch onto my internal 32GB card. But don't want to remove it from my Zaurus....

Thought I'd download the rootfs file onto my SD card that has the Arch install on it that I use now to boot my Z with....

Did the following:

Code: [Select]

# wget -i https://github.com/greguu/alarm-zaurus-c3x00/releases/download/October2015/alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz
Get lots of text....then
Resolving github-cloud.s3.amazonaus.com.....54.231.112.136
Connecting to github-cloud.....connected.
HTTP request sent, awaiting response.....200 OK
Length:  135779144 (129M) [application/octet-stream]
Saving to: 'alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz.1'

alarm-zaurus-c3x00-    0%[               ]    0 --, -KB/s   in 0/004s

Cannot write to 'alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz.1' (Success).
No URLs found in https://github.com/greguu/alarm-zaurus-c3x00/releases/download/October2015/alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz.
What am I missing here?

Thanks.

[danboid]

If you'd followed my install guide step-by-step then you would've already copied the rootfs tarball (in its unextracted form) onto your SD card but I presume thats not the case here.

The bit of terminal output you pasted showed you trying to download the tarball but where to, direct to the SD card? It says it cannot write to the current device so either:

* You didn't run the command as root
* There isn't enough space on your SD card or
* Your SD card is write protected

One of those was most likely tripping you up.

I wonder if daal will return now the rugby is over (and they won, again, of course)?

EDIT

If you do end up doing a re-install / upgrade Mark it would be useful for us if you tried out systemd 226-3. You may be better off with that than running 226-2 and you may not need the IgnorePkg?

[teh.sean]

Hey gang. I gave this a go today.

I ran into some issues with the KEXECBOOT updater not working on my Zaurus. I wound up having to do a complete NAND restore to factory settings to be able to install KEXECBOOT. The SD / CF updater would always fail.

After doing that, I was able to at least install KEXECBOOT and boot into ALARM on my CF card.

I then attempted to replace the internal 4GB microdrive with a 64GB microSD card housed in a Type 2 CF to MicroSD card adapter. I had planned on setting up the internal drive from the CF install of ALARM but to my surprise ALARM would not boot properly after putting in the new internal drive. I suspect that KEXECBOOT (or the NAND app) writes some data to the partitions on the Microdrive normally.

So I took out the internal CF / MicroSD card and partitioned it so that the two Sharp original partitions and files (.SYS directory) were on the new card.

I had planned on reinstalling from scratch (reinstall KEXECBOOT, etc) but even after the new partitioning of the SD / CF adapter, the KEXECBOOT install script tells me the microdrive is not found. Suxxor.

I'll continue with it some time next week. I don't know much about Arch Linux (avid OpenBSD user) so I'll have to learn the ecosystem. It's different enough for me to not know how to do a majority of the stuff I'd like to.