Archlinuxarm On C3x00

[danboid]

Thanks daalnroti! I'll try those kexc options shortly.

With any luck I'll get my new wifi card tomorrow and then I can start using/testing my Z for real! It looks likely I will be buying a CF ethernet adapter soon but I may not be able to find a new one by the looks of things.

After Mark is up and running, we'll just need a Z ALARMer from both Australia and Canda to form the Five Eyes zALARMers!

https://en.wikipedia.org/wiki/Five_Eyes

[ArchiMark]

Five Eyes sounds cool.....

Meanwhile, got kexecboot working....

Have created new partitions:

/dev/hda1  FAT32  (100MB)
/dev/hda2  linux swap (256MB)
/dev/hda3  linux (rest of 6GB drive...)

Did the following to mount the filesystems:

# mkfs.vfat /dev/hda1
# mkdir boot
# mount /dev/hda1 boot

# mkswap /dev/hda2

Having problem creating fs for ext3 or ext4 for /hda3......

Everything I try, I get not found message....

Tried:

# mksf.ext3 /dev/hda3
# mksf -t ext3 /dev/hda3
# mkext3fs /dev/hda3

What's the right way?

Thanks!

[greguu]

Five Eyes sounds cool.....

Meanwhile, got kexecboot working....

Have created new partitions:

/dev/hda1  FAT32  (100MB)
/dev/hda2  linux swap (256MB)
/dev/hda3  linux (rest of 6GB drive...)

Did the following to mount the filesystems:

# mkfs.vfat /dev/hda1
# mkdir boot
# mount /dev/hda1 boot

# mkswap /dev/hda2

Having problem creating fs for ext3 or ext4 for /hda3......

Everything I try, I get not found message....

Tried:

# mksf.ext3 /dev/hda3
# mksf -t ext3 /dev/hda3
# mkext3fs /dev/hda3

What's the right way?

Thanks!

Hi ArchiMark,

First, I believe there is no need for a FAT32 boot partition if you want to run Arch.

If you are using the sharp emergency console, (busybox), it will have no ext3/4 support I think.

You will need to boot of a newer ROM from a SD card to create the file system with ext3/4.

Alternatively, create a ext2 /dev/hda4 with 2GB, mkfs ext2 then install Arch, once installed and booted of ext2, mkfs ext3 on hda3 and move Arch.
Boot to ext3 and the remove hda4 and extend your hda3.  

Actually a good point raised, we need to cover this issue in the install guide somehow.

Cheers,

[ArchiMark]

Five Eyes sounds cool.....

Meanwhile, got kexecboot working....

Have created new partitions:

/dev/hda1  FAT32  (100MB)
/dev/hda2  linux swap (256MB)
/dev/hda3  linux (rest of 6GB drive...)

Did the following to mount the filesystems:

# mkfs.vfat /dev/hda1
# mkdir boot
# mount /dev/hda1 boot

# mkswap /dev/hda2

Having problem creating fs for ext3 or ext4 for /hda3......

Everything I try, I get not found message....

Tried:

# mksf.ext3 /dev/hda3
# mksf -t ext3 /dev/hda3
# mkext3fs /dev/hda3

What's the right way?

Thanks!

Hi ArchiMark,

First, I believe there is no need for a FAT32 boot partition if you want to run Arch.

If you are using the sharp emergence console, (busybox), it will have no ext3/4 support I think.

You will need to boot of a newer ROM from a SD card to create the file system with ext3/4.

Alternatively, create a ext2 /dev/hda4 with 2GB, mkfs ext2 then install Arch, once installed and booted of ext2, mkfs ext3 on hda3 and move Arch.
Boot to ext3 and the remove hda4 and extend your hda3.  

Actually a good point raised, we need to cover this issue in the install guide somehow.

Cheers,

Thanks for your help and input!

What partition layout would you recommend since I have a 6GB micro drive ?

Mark

[greguu]

Thanks for your help and input!

What partition layout would you recommend since I have a 6GB micro drive ?

If you want to use all of the 6GB for Arch / Home use a simple

/dev/hda1 5.5 GB ext4
/dev/hda2 0.5 GB Swap (128 MB may be enough)

If you can spare a few GB for a second Arch for fall back you can use

/dev/hda1 2 GB ext4 (fall-back Arch minimal)
/dev/hda2 0.5 GB Swap (128 MB may be enough)
/dev/hda3 3.5 GB ext4 Arch

Cheers,

[ArchiMark]

Thanks for your help and input!

What partition layout would you recommend since I have a 6GB micro drive ?

If you want to use all of the 6GB for Arch / Home use a simple

/dev/hda1 5.5 GB ext4
/dev/hda2 0.5 GB Swap (128 MB may be enough)

If you can spare a few GB for a second Arch for fall back you can use

/dev/hda1 2 GB ext4 (fall-back Arch minimal)
/dev/hda2 0.5 GB Swap (128 MB may be enough)
/dev/hda3 3.5 GB ext4 Arch

Cheers,

Thanks!

[greguu]

Thanks for your help and input!

What partition layout would you recommend since I have a 6GB micro drive ?

If you want to use all of the 6GB for Arch / Home use a simple

/dev/hda1 5.5 GB ext4
/dev/hda2 0.5 GB Swap (128 MB may be enough)

If you can spare a few GB for a second Arch for fall back you can use

/dev/hda1 2 GB ext4 (fall-back Arch minimal)
/dev/hda2 0.5 GB Swap (128 MB may be enough)
/dev/hda3 3.5 GB ext4 Arch

Cheers,

Thanks!

Keep in mind that after booting into Arch the harddrive / cf card will be named /dev/sda.

So boot.cfg and fstab for Arch need to be /dev/sdaX instead of  /dev/hda.

[ArchiMark]

Thanks for your help and input!

What partition layout would you recommend since I have a 6GB micro drive ?

If you want to use all of the 6GB for Arch / Home use a simple

/dev/hda1 5.5 GB ext4
/dev/hda2 0.5 GB Swap (128 MB may be enough)

If you can spare a few GB for a second Arch for fall back you can use

/dev/hda1 2 GB ext4 (fall-back Arch minimal)
/dev/hda2 0.5 GB Swap (128 MB may be enough)
/dev/hda3 3.5 GB ext4 Arch

Cheers,

Thanks!

Keep in mind that after booting into Arch the harddrive / cf card will be named /dev/sda.

So boot.cfg and fstab for Arch need to be /dev/sdaX instead of  /dev/hda.

OK, will keep this in mind.....

Thanks!

[danboid]

You can format ext3 using busybox by using

Code: [Select]

mkext2fs -j /dev/hdax
The -j switch enables journaling which means its really ext3 but I would recommend you mount it as ext4 as my tests earler in this thread show you get a little extra read speed when using ext4.

[greguu]

You can format ext3 using busybox by using

Code: [Select]

mkext2fs -j /dev/hdax
The -j switch enables journaling which means its really ext3 but I would recommend you mount it as ext4 as my tests earler in this thread show you get a little extra read speed when using ext4.

This does work, but I would not recommend this.
It would be better to create a  proper ext4 partition from a running system that has ext4 support or follow the conversion guide shown here.
https://wiki.archlinux.org/index.php/Ext4
Unless you need to be able to mount it again as ext2/3 in the future, there is no need to run mkfs.ext2 -j

[greguu]

BT : I have added all BT modules to a new kernel release . Please test.

KEXECBOOT : The settings for TIMEOUT and DEFAULT did not work for me. May be the kexecboot version needs to be updated, it is quite old.

[danboid]

Thanks daalnroti!

I didn't get to try the kexecboot options but I'd be willing to upgrade to get the default and timeout options. I installed the version you uploaded to github (0.5.9).

Unfortunately my USB BT adapter died over the weekend. It seemed to be working on Saturday but when I tried it again on Sunday - no go. I tried it on my laptop too to make sure it was dead so I'll try the BT tethering out when I get a replacement adapter.

EDIT

My new wifi adapter has failed to show again so I'm going to try and get a new BT adapter if I can find one cheap locally. The tracking says I should have the wifi tomorrow.

[danboid]

Mark:

I don't think daal or I have mentioned it so far but you also have to copy the firmware dir within the kernel; tarball to /usr/lib .

That's the correct location isn't it daalnroti?

[ArchiMark]

Mark:

I don't think daal or I have mentioned it so far but you also have to copy the firmware dir within the kernel; tarball to /usr/lib .

That's the correct location isn't it daalnroti?

Thanks for the heads up.....

Will be trying to get Arch setup in about 5 hours or so....

Tried using my MacBook last night to uncompress the Arch tarball, but didn't work well....

As I'd left my laptop with LM17 on it at the office, I had to wait until now to proceed further with Arch install.

Almost done downloading the Arch tarball and other files now. After I get back from a meeting, I will try to do the rest of the install....

When I get back I'll check if there's any further clarifications or tips regarding install.....

Thanks!

[danboid]

I bought a new USB BT adapter but it looks like I'm unlikely to get it working under kernel 3.11. My £1 BT adapter is manufactured by SIGNALEX and lsusb describes it as:

0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth

It works on my x64 Arch box running kernel 4.1.6 but I'm not the only person struggling to get it to work under 3.11.x according to this thread:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221995

The good news is that the btusb kernel module loads OK but obviously I can't confirm it actually works.

EDIT

I've got a bit further with this device now on the Z. I thought it wasn't going to work as the `hciconfig` command showed a hci0 device but `hcitool dev` showed nothing UNTIL I ran:

Code: [Select]

hciconfig device up
Which is something I've not had to do before in my limited BT experience. After running that, `hcitool dev` shows a hci0 device but scanning is failing currently so I cannot pair with my phone. I've only tried it plugged directly into the OTG port so I'll be trying again with a powered hub later to see if that helps.