Archlinuxarm On C3x00

[ArchiMark]

Just tried to decompress the Arch tarball onto my microdrive from my SD card.....

Get the following:

# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....

I am in directory of the arch tarball on SD card (vfat)...

/dev/hda1 (on microdrive...) is mounted on /mnt/arch....

What am I doing wrong?.................

[greguu]

Just tried to decompress the Arch tarball onto my microdrive from my SD card.....

Get the following:

# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....

I am in directory of the arch tarball on SD card (vfat)...

/dev/hda1 (on microdrive...) is mounted on /mnt/arch....

What am I doing wrong?.................

Try this :

Code: [Select]

cd /mnt/arch
tar -xvf /path/to/ArchLinuxARM-armv5-latest.tar
You need to change /path/to to the SD card location where your tar is.

[ArchiMark]

Just tried to decompress the Arch tarball onto my microdrive from my SD card.....

Get the following:

# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....

I am in directory of the arch tarball on SD card (vfat)...

/dev/hda1 (on microdrive...) is mounted on /mnt/arch....

What am I doing wrong?.................

Try this :

Code: [Select]

cd /mnt/arch
tar -xvf /path/to/ArchLinuxARM-armv5-latest.tar
You need to change /path/to to the SD card location where your tar is.

Hmmmm...thought I could do it the reverse....I cd'd to the directory of the Arch tarball is located and provided path to where the uncompressed files go to......
Oh well, will try your suggestion.....

Thanks!

UPDATE:

Tried it, but now get other error message:

tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Error exit delayed from previous errors
#

 

[greguu]

Just tried to decompress the Arch tarball onto my microdrive from my SD card.....

Get the following:

# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....

I am in directory of the arch tarball on SD card (vfat)...

/dev/hda1 (on microdrive...) is mounted on /mnt/arch....

What am I doing wrong?.................

Try this :

Code: [Select]

cd /mnt/arch
tar -xvf /path/to/ArchLinuxARM-armv5-latest.tar
You need to change /path/to to the SD card location where your tar is.

Hmmmm...thought I could do it the reverse....I cd'd to the directory of the Arch tarball is located and provided path to where the uncompressed files go to......
Oh well, will try your suggestion.....

Thanks!

UPDATE:

Tried it, but now get other error message:

tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Error exit delayed from previous errors
#

 

This is odd, did you try with the bsd-tar from the kexecboot  package ?

[ArchiMark]

Just tried to decompress the Arch tarball onto my microdrive from my SD card.....

Get the following:

# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....

I am in directory of the arch tarball on SD card (vfat)...

/dev/hda1 (on microdrive...) is mounted on /mnt/arch....

What am I doing wrong?.................

Try this :

Code: [Select]

cd /mnt/arch
tar -xvf /path/to/ArchLinuxARM-armv5-latest.tar
You need to change /path/to to the SD card location where your tar is.

Hmmmm...thought I could do it the reverse....I cd'd to the directory of the Arch tarball is located and provided path to where the uncompressed files go to......
Oh well, will try your suggestion.....

Thanks!

UPDATE:

Tried it, but now get other error message:

tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Error exit delayed from previous errors
#

 

This is odd, did you try with the bsd-tar from the kexecboot  package ?

Ummmm.....no......used 'tar -xvf.....'

Just tried again....

# bsdtar -xvf.....
bsdtar: not found

How do I either 'install' bsdtar or invoke it from kexecboot package?

Sorry, if my questions are dumb.....but I know just enough linux to be dangerous....  

Thanks.

[greguu]

Just tried to decompress the Arch tarball onto my microdrive from my SD card.....

Get the following:

# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....

I am in directory of the arch tarball on SD card (vfat)...

/dev/hda1 (on microdrive...) is mounted on /mnt/arch....

What am I doing wrong?.................

Try this :

Code: [Select]

cd /mnt/arch
tar -xvf /path/to/ArchLinuxARM-armv5-latest.tar
You need to change /path/to to the SD card location where your tar is.

Hmmmm...thought I could do it the reverse....I cd'd to the directory of the Arch tarball is located and provided path to where the uncompressed files go to......
Oh well, will try your suggestion.....

Thanks!

UPDATE:

Tried it, but now get other error message:

tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Error exit delayed from previous errors
#

 

This is odd, did you try with the bsd-tar from the kexecboot  package ?

Ummmm.....no......used 'tar -xvf.....'

Just tried again....

# bsdtar -xvf.....
bsdtar: not found

How do I either 'install' bsdtar or invoke it from kexecboot package?

Sorry, if my questions are dumb.....but I know just enough linux to be dangerous....  

Thanks.

No worries, we will get it going.

Copy the bsd-tar from the oe-kexecboot package to the SD card alongside with the ALARM tar file.

Mount SD card and Microdrive.

Then try something like this :

Code: [Select]

cd /mnt/hda1
/path/to/bsd-tar -xvf /path/to/ALARM.tar
Did you gunzip the ALARM tar.gz before saving it on the SD ?

Maybe document all the steps you do and share.

[ArchiMark]

Just tried to decompress the Arch tarball onto my microdrive from my SD card.....

Get the following:

# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....

I am in directory of the arch tarball on SD card (vfat)...

/dev/hda1 (on microdrive...) is mounted on /mnt/arch....

What am I doing wrong?.................

Try this :

Code: [Select]

cd /mnt/arch
tar -xvf /path/to/ArchLinuxARM-armv5-latest.tar
You need to change /path/to to the SD card location where your tar is.

Hmmmm...thought I could do it the reverse....I cd'd to the directory of the Arch tarball is located and provided path to where the uncompressed files go to......
Oh well, will try your suggestion.....

Thanks!

UPDATE:

Tried it, but now get other error message:

tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Error exit delayed from previous errors
#

 

This is odd, did you try with the bsd-tar from the kexecboot  package ?

Ummmm.....no......used 'tar -xvf.....'

Just tried again....

# bsdtar -xvf.....
bsdtar: not found

How do I either 'install' bsdtar or invoke it from kexecboot package?

Sorry, if my questions are dumb.....but I know just enough linux to be dangerous....  

Thanks.

No worries, we will get it going.

Copy the bsd-tar from the oe-kexecboot package to the SD card alongside with the ALARM tar file.

Mount SD card and Microdrive.

Then try something like this :

Code: [Select]

cd /mnt/hda1
/path/to/bsd-tar -xvf /path/to/ALARM.tar
Did you gunzip the ALARM tar.gz before saving it on the SD ?

Maybe document all the steps you do and share.

Think I gunzip'd it.....I think.....

Just checked the oe-kexexboot package.....

Don't see bsdtar there, but I do see gnu-tar there....is this the one?

Thanks!

UPDATE:

OK, used gnu-tar file......

Code: [Select]

cd /mnt/hda1
/path/to/gnu-tar -xvf /path/to/ALARM.tar
and now it's scrolling through a long list.....very fast....

But I see error messages.....on each line....

 

Could not create symlink....: No such file or directory
Could not create file.......: No such file or directory....

Thanks!

[ArchiMark]

Think it would be really helpful if there was a way to post the Arch tarball in the right format to untar on the Z.....

I know it's easy for me to say.....

[greguu]

Think it would be really helpful if there was a way to post the Arch tarball in the right format to untar on the Z.....

I know it's easy for me to say.....

aw, my fault. Of course I meant gnu-tar.

Ok,

do a reboot, go into D+B emergency console.
there do :

Code: [Select]

fdisk /dev/hda
the press "p" then "enter" and post us the output. use "q" then "enter" to quit fdisk.

after do:

Code: [Select]

mkdir /mnt/arch
mount /dev/hda1 /mnt/arch
and then:

Code: [Select]

mount

df -h

ls -la /mnt/arch
and post the output.

also please :

Code: [Select]

mkdir /mnt/sdcard
mount /dev/mmcblk0p1 /mnt/sdcard
mount
df -h
ls -la /mnt/sdcard
you can take photos and post them if you can not ssh / telnet to the device yet.

It could be your /dev/hda is not partitioned, formated properly (/dev/hda1 /dev/hda2 etc)

Cheers.

[greguu]

Think it would be really helpful if there was a way to post the Arch tarball in the right format to untar on the Z.....

I know it's easy for me to say.....

Hi ArchiMark,

the idea would be to make a custom tar ball, containing kernel and initial fixes to get someone going.
I will see if I can provide one once I got a new kexecboot going.

What network / wifi / bt cards do you use ArchiMark?
Any needs for special USB drivers etc ?

Cheers!

[greguu]

New kexeboot release added : arch-kexecboot

If you are keen, please test.

- Based on Linux Kernel 3.5
- Based on Kexecboot 0.6 (latest release)
- Boots Linux kernels from ext2/3/4 (SD,CF,USB) and ubifs (NAND)
- Features ArchLinux logos and theming (wonder why I did that)
- Auto Boots first entry in your boot.cfg after 5 seconds (hard coded)

I will attempt to build a newer kernel 3.18 series first, maybe 4.2. series later in the coming days.

[greguu]

Hi ArchiMark,

here a step by step guide to get you a ALARM booting of a SD card. From there everything else should be a breeze.

Following steps have been confirmed and tested. Any issues , just ask.

00. Wipe your microdrive partitions (OPTIONAL)

   (following steps will erase all on your microdrive card)

   Boot into D+B emergency then do a:

Code: [Select]

    fdisk /dev/hda
   "d" enter until all partitions are deleted
   "w" to write and exit
   

01. Install arch-kexecboot from my github

   https://github.com/greguu/linux-3.11.3-borz...leases/tag/v0.4


02. On you linux machine LM17 download

   http://archlinuxarm.org/os/ArchLinuxARM-armv5-latest.tar.gz

   and save it on your home folder /home/yourusername

   open terminal as user

Code: [Select]

    cd ~
    wget  http://archlinuxarm.org/os/ArchLinuxARM-armv5-latest.tar.gz
03. Take a working SD card and place it in your LM17 laptop

   (do not mount it from you desktop environment)
   (following steps will erase all on your SD card)
      
   open a terminal and become root
   (this is an example, change sdc to the sdX that reflects the SD card)

Code: [Select]

    fdisk /dev/sdc  

   "d" enter until all partitions are deleted

   then
     
   "n" enter to create a new partition
   "p" to set primary
   "1" to set partition number one
   and double enter to accept default size (full SD card)
   "p" to verify you new partition layout
   "w" to write to disk

       Then format to ext4 and mount.

   

Code: [Select]

        
    mkfs.ext4 /dev/sdc1    

    mkdir /mnt/sdarch
    
    mount /dev/sdc1 /mnt/sdarch   
04. Unpack the ArchLinuxARM-armv5-latest.tar.gz

   

Code: [Select]

    cd /mnt/sdarch
    
    tar xf /home/yourusername/ArchLinuxARM-armv5-latest.tar.gz   (this will take a while)
   
05. Remove zImage from /mnt/sdarch/boot

06. Copy kernel "zImage-3.11.3-c3x00" and "boot.cfg" from my git hub to /mnt/sdarch/boot
   
07. Edit boot.cfg to look like this:

Code: [Select]

    LABEL=ArchLinuxARM
    KERNEL=/boot/zImage-3.11.3-c3x00
    APPEND=root=/dev/mmcblk0p1 rootfstype=ext4 fbcon=rotate:1 noinitrd loglevel=3
08. Copy 3.11.3-c3x00 folder to /mnt/sdarch/lib/modules

   (no need to copy firmware files, they are already installed)

   (you can remove the 4.x kernel and other modules folder under /mnt/sdarch/lib/modules)

   
09. Edit /mnt/sdarch/etc/fstab to look like this

Code: [Select]

    /dev/mmcblk0p1           /               ext4     noatime,nodiratime,commit=600,reservation,defaults,errors=remount-ro 0 1
10. Download keymap file from github , borzoi.map.gz

   as root :
       

Code: [Select]

       cd /mnt/sdarch/usr/share/kbd/keymaps
       mkdir zaurus
       cp /home/yourusername/borzoi.map.gz /mnt/sdarch/usr/share/kbd/keymaps/zaurus   
       create and edit /mnt/sdarch/etc/vconsole.conf to like this:

   

Code: [Select]

    KEYMAP=borzoi
11. Unmount SD card and place in Z, boot Z ! (user "root" / pass "root" )

12. Then repeat all these steps for the microdrive


( Once you got ALARM on your micro drive, keep this SD card, it might come in handy as a rescue system.)

[greguu]

daalnroti:

The only report I've found of someone having my wifi prob is this:

http://lists.infradead.org/pipermail/liber...May/003490.html

Thankfully he includes a patch so I'd appreciate it if you could try applying it for me if it never got mainlined?

Thanks!

Hi danboid,

this patch is already included in 3.11.3  

it is just for tx timeouts.

the issue you experience are tx lockups, different matter.

there is code about the lockups in main.c of the libertas driver :

Code: [Select]

/**
 * lbs_tx_lockup_handler - handles the timeout of the passing of TX frames
 * to the hardware. This is known to frequently happen with SD8686 when
 * waking up after a Wake-on-WLAN-triggered resume.
 *
 * @data: &struct lbs_private pointer
 */
static void lbs_tx_lockup_handler(unsigned long data)
{
        struct lbs_private *priv = (struct lbs_private *)data;
        unsigned long flags;

        lbs_deb_enter(LBS_DEB_TX);
        spin_lock_irqsave(&priv->driver_lock, flags);

        netdev_info(priv->dev, "TX lockup detected\n");
        if (priv->reset_card)
                priv->reset_card(priv);

        priv->dnld_sent = DNLD_RES_RECEIVED;
        wake_up_interruptible(&priv->waitq);

        spin_unlock_irqrestore(&priv->driver_lock, flags);
        lbs_deb_leave(LBS_DEB_TX);
}
I would suggest to get at least your other WiFi card going first and then see maybe if a newer kernel does make the libertas_cs work.

Did you buy the libertas card new ?

Or use a USB WiFi on a powered hub, or a CF/USB ethernet adapter to get further.

I am happy to apply patches but I am not sure removing the lockup handler fixes your issue. You want me to try ?

[greguu]

I dared to post on ALARM forums after being registered since 2012!

http://archlinuxarm.org/forum/viewtopic.php?f=27&t=9381

what a lame attempt to get more users

[danboid]

daalnroti:

The only report I've found of someone having my wifi prob is this:

http://lists.infradead.org/pipermail/liber...May/003490.html

Thankfully he includes a patch so I'd appreciate it if you could try applying it for me if it never got mainlined?

Thanks!

Hi danboid,

this patch is already included in 3.11.3  

it is just for tx timeouts.

the issue you experience are tx lockups, different matter.

there is code about the lockups in main.c of the libertas driver :

Code: [Select]

/**
 * lbs_tx_lockup_handler - handles the timeout of the passing of TX frames
 * to the hardware. This is known to frequently happen with SD8686 when
 * waking up after a Wake-on-WLAN-triggered resume.
 *
 * @data: &struct lbs_private pointer
 */
static void lbs_tx_lockup_handler(unsigned long data)
{
        struct lbs_private *priv = (struct lbs_private *)data;
        unsigned long flags;

        lbs_deb_enter(LBS_DEB_TX);
        spin_lock_irqsave(&priv->driver_lock, flags);

        netdev_info(priv->dev, "TX lockup detected\n");
        if (priv->reset_card)
                priv->reset_card(priv);

        priv->dnld_sent = DNLD_RES_RECEIVED;
        wake_up_interruptible(&priv->waitq);

        spin_unlock_irqrestore(&priv->driver_lock, flags);
        lbs_deb_leave(LBS_DEB_TX);
}
I would suggest to get at least your other WiFi card going first and then see maybe if a newer kernel does make the libertas_cs work.

Did you buy the libertas card new ?

Or use a USB WiFi on a powered hub, or a CF/USB ethernet adapter to get further.

I am happy to apply patches but I am not sure removing the lockup handler fixes your issue. You want me to try ?

Yes, the libertas card is new. I've only tried it with the one AP in work so far but I'll get to try it at home tonight,

I'm pretty much out of ideas for getting my old wifi card to work under ALARM - it just won't find any primary firmware and I've tried every one I could find.

I don't think I've got access to any other devices with a CF slot so I may end up having to reinstall OBSD or pdaX to see if it works with those unless you have some kernel options I can try that might help?

I've not finished my experiments with BT tethering. There is a script called 'test-network' included with bluez that can supposedly configure BT tethering although I'll only get ~2Mb/s tops over my BT2 adapter.

I'd like to get a CF ethernet adapter but I was struggling to find a new one. I used to have a USB ethernet adapter that worked well with Linux but I lent it to a friend and I think he's lost it so I'll prob buy another one of those as they're cheap and more likely to work than USB wifi adapters.