Essentially you have 3 choices here 1 use both bluetooth and wireless but have half bandwidth and buffer overrun issues, 2 use wireless but don't use bluetooth, or 3 use bluetooth but don't use wireless. There are fixes and patches but I haven't delved too deeply into them. Pi wireless may misbehave as it isn't perfect and is shoehorned in on the same bus as the bluetooth. It turns out there are Setting up locale and timezone, as well as setting up swap, the fstab, and localhost and network. Once the ARM install wikki has been followed I browse through the main-line ArchLinux install wikki to see if there are any additional steps that are applicable. Then finnish the instructions in the ARM install wikki from above. Refer to the wikki tab on the arm installation page for details. We will also want to set up our config.txt for our screen hardware as well as any other Pi-specific instructions like alsa sound and poll only once to preserve the sd card. Now when we add any changes to our packages and we want to reflect this in our recovery file we can issue the command īefore you do any pacman related things here llike initializing the keyring you will want to jump across to the main-line ArchLinux install wikki and follow the section on setting up the pacman mirrorlist. I went one step further here and added an additional file called update.sh Add the option -color=auto to the pacman command for a colourful pacman display. NOTE: Watch for the missing closing bracket in the Authors code and refer to his screenshots of nano. Even if we didn't mess anything up we can still do this step so that we have a viable recovery option. So we can use this article here to create a recovery script to re-install everything. If you went this far and didn't use the correct program to unzip and install, and don't want to go back and repeat what you've already done, there is a solution, reinstalling a package will fix the extended file headers. If we use the incorrect program to extract these files we will lose these extended file headers and then we will begin to get into trouble. The Installation files are zipped in a special format called bsdtar which allows the storage of extended file meta-data which Arch uses to dynamically control file and service access permissions. berry-pi-2įor the longevity of this tutorial I won't repeat the instructions here as arch is a rolling distro this could change at any time, and probably will. Getting this right is important as it will affect everything else down the track (like user permissions which are truncated by tar causing file access escalation issues like needing to run ping as a super user, and disk RW acces issues when setting up/changing users home directories). Thanks for any and all of your time TroubledTuna Posts: 11 Joined: Thu 5:19 pmįirst Installation steps I took were to follow the ArchLinuxARM Install wikki to the letter. My question, in a nutshell is, in the pursuit of useful learning, starting with easier more interesting stuff for my own sake, what should I do, where and how do I go about learning what I can install on my Raspberry Pi 2 and what do you guys suggest? So far I've installed "mc" and "elinks" and that's super fun, having a somewhat CLI?-based (is this the correct term?) UI for my computer - are there any UI's that primarily work like "elinks" and "mc"? Anything else you can suggest? I installed them but I'm not sure what next to do? Or is this even the wisest thing to learn first? $this->bbcode_second_pass_quote('', 'T')he X.org driver for Raspberry Pi can be installed with the xf86-video-fbdev or xf86-video-fbturbo-git package. I checked the Wiki for Arch Linux Arm (here ) but all it says is So, I'd like to install a working display, something that isn't just the command line (I figured that would be a good thing to learn first) My intention is to learn as much about Arch as I can and have a computer I can tinker with and break (which I will do, as I'm beyond slow/daft) without damaging my actual computer. I have just installed Arch Arm to a Raspberry Pi 2Īs some may be aware I had a few bumps getting there but a day or so ago I managed to install Arch to my SDcard (while probably quite trivial for most, this was a real personal achievement for me).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |