Install Arch from Windows

[pepedog]

I would like to thank you, fotl

[fruitoftheloom]

I would like to thank you, fotl

Why do you need to thank me ?
Just trying to tie the various threads together

[pepedog]

I wouldn't have seen that other thread though

[Axolotl9250]

Can the dd command be used to make a .img that's 16GB for a 16GB microSD? I tried by making count=16384 but after a while it said dd: writing `arch-rpi.img`: No space left on device.

Thanks,
Ben.

[Axolotl9250]

Also, when it comes to doing mkfs.vfat - /dev/loop0p1 does not exist, only /dev/loop0.

Best,
Ben.

[fruitoftheloom]

Also, when it comes to doing mkfs.vfat - /dev/loop0p1 does not exist, only /dev/loop0.

Best,
Ben.

You should have 2 partitions. ""/dev/mmcblk0p1 and /dev/mmcblk0p2"" the fisrst is boot and the second is Arch, usually one just expands the second partition with parted if needs be after Arch has booted up first time..


fyi Arch Linux Arm do not recommend to use the July 2014 image but create a SD Card as per instructions for a Linux OS

http://archlinuxarm.org/platforms/armv6/raspberry-pi

http://archlinuxarm.org/platforms/armv7 ... berry-pi-2

[pepedog]

Also, when it comes to doing mkfs.vfat - /dev/loop0p1 does not exist, only /dev/loop0.

Best,
Ben.

You may need something like loop.max_part=15 in cmdline.txt, sync && reboot

[Axolotl9250]

Doing the sync and adding the line to codlin.txt and sync+reboot still does not make p1 and p2 appear in dev for loop0, however I do see mmcblk0 , mmcblk0p1, and mmcblkp2 and if I fdisk on mmcblk0 the table has a FAT partition and an Linux partition with the same Id variables as for /dev/loop0.

[Enki]

My whole reason for starting this thread was to try to use Arch to reduce boot times on my B+. Since the release of the 2 B, I'm not so sure I need to anymore (as it looks like innate boot times are just about halved, and can probably still be improved).

Thanks to everyone that saw fit to help a fledgeling Pi consumer out.

[pepedog]

Doing the sync and adding the line to codlin.txt and sync+reboot still does not make p1 and p2 appear in dev for loop0, however I do see mmcblk0 , mmcblk0p1, and mmcblkp2 and if I fdisk on mmcblk0 the table has a FAT partition and an Linux partition with the same Id variables as for /dev/loop0.

You wouldn't see it until you did losetup -f arch-rpi.img

[spuffin]

It seems like some of us are odd use-cases for the Pi. I am not so much using them to learn Linux but just as an extremely low power workhorse that serves NAS/voip/VPN/remote access. The Pi is the only non-embedded Linux box I have so the previously provided ArchARM images were ideal for flashing to an SD-card and moving on to better tasks. After hassling with the process to create a suitable image on Windows and OS X, I gave up and just installed VirtualBox, installed a Linux VM, mounted my USB reader via the VM and installed Arch that way.

That sequence is ridiculous IMHO. Even if the sequence was to install NOOBS, Raspbian, or any other distro to create an image file to then transfer to my Windows/OS X box and then write to a memory card is just as inefficient.

That said, I've already gone through the trouble so I can create a .torrent of the image file so that no one else has to go through the same process. Is there any interest in this? Is it okay to post a link to it?

I will note, however, that these images should ideally come straight from the source (Arch Linux ARM) or created yourself via the processes or alternatives defined in this thread.

[sdjf]

I think that the reason an image would be frowned upon is that one week later, it is outdated. I personally think it would be a great way to help people out, but the bottom line is that if they want support with problems with the image, then official support from the primary Arch Linux Arm folks over at archlinuxarm.org would be lacking. People here in the subforum at the foundation site are a bit more lenient, but unless you update your image constantly, people may get confused when they run into trouble, not understanding that NOT updating with pacman -Syu immediately would put them behind updates that happened since you created the image.

I do think that if you post a link here, it would be okay, but I am not a forum moderator and cannot speak for them. But you do need to emphasize intensely that the image is not necessarily up to date and absolutely must be updated with pacman before trying to install any packages.

EDIT: One more caveat. If you do post a link to an image you create, note the exact size in BYTES of the card it is from. This is because it will not be possible to copy it to any microSD card that is smaller than your image needs, even by 1 byte! Not all 16 GB microSD cards will have the same capacity, and that is true for any media cards. Manufacturers vary in the way they interpret the term GB, and cards of theoretically the same size in GB will not necessarily actually be the same size in K or bytes.

[rtaudio]

...
fyi Arch Linux Arm do not recommend to use the July 2014 image but create a SD Card as per instructions for a Linux OS

http://archlinuxarm.org/platforms/armv6/raspberry-pi

http://archlinuxarm.org/platforms/armv7 ... berry-pi-2

I've tried this, but my system has no "mkfs.ext4".
So I downloaded a VM image of ArchLinux just to create this SD card, but the ArchLinux won't recognize my USB card reader! it says "usb 1-2: Invalid ep0 maxpacket: 9", whatever that means.

I would really, really appreciate a pre-made image to simply dd onto my SD card just like the other distros do. They are there for a reason.
Why make it so hard for non-die-hard Linux users?

[fruitoftheloom]

...
fyi Arch Linux Arm do not recommend to use the July 2014 image but create a SD Card as per instructions for a Linux OS

http://archlinuxarm.org/platforms/armv6/raspberry-pi

http://archlinuxarm.org/platforms/armv7 ... berry-pi-2

I've tried this, but my system has no "mkfs.ext4".
So I downloaded a VM image of ArchLinux just to create this SD card, but the ArchLinux won't recognize my USB card reader! it says "usb 1-2: Invalid ep0 maxpacket: 9", whatever that means.

I would really, really appreciate a pre-made image to simply dd onto my SD card just like the other distros do. They are there for a reason.
Why make it so hard for non-die-hard Linux users?

Over 2 years and Arch Linux Arm have not changed their stance one iota, so it would seem the only way to install without using their instructions is P.I.N.N. (a re-spin of the NoobS installer / chooser)

https://github.com/procount/pinn/blob/master/README.md

[mikerr]

I would really, really appreciate a pre-made image to simply dd onto my SD card just like the other distros do. They are there for a reason.
Why make it so hard for non-die-hard Linux users?

I've been hosting pre-made Arch .img's on sourceforge for a year or so, updated today:

https://sourceforge.net/projects/archlinuxrpi/ .img for Pi B/B+ & Zero
and
https://sourceforge.net/projects/archlinux-rpi2/ .img for Pi 2 & 3

[cjan]

I've been hosting pre-made Arch .img's on sourceforge for a year or so, updated today:
https://sourceforge.net/projects/archlinux-rpi2/ .img for Pi 2 & 3

last .img seems update to kernel-4.4.39 and raspbian was 4.4.38.
maybe arch forgot do some patches from raspbian(e.g. 8192cu module), what to do now?

[pepedog]

dkms
pacman -S dkms-8192cu

[cjan]

dkms
pacman -S dkms-8192cu

no wired, so install by manual, got 'Segmentation fault (core dumped)' error.
does it kernel version matter? and its arch=any.

its old isuue(bug?) why DEVs ignored it?

[pepedog]

You are going to need a whole lot more than that package, this is going to compile the module (against the right headers), and dkms is going to be installed (service will need enable too).
Search the wiki for dkms

[cjan]

You are going to need a whole lot more than that package, this is going to compile the module (against the right headers), and dkms is going to be installed (service will need enable too).
Search the wiki for dkms

no wired.