makepkg was surprisingly straightforward thereafter.go was not installing, surprisingly go-2:1.19-1 was updated on Aug 3 itself and I hadn't done pacman -SyyReiterated the importance of keeping my package lists updated in a rolling release distro.had to install base-devel for this: sudo pacman -S base-devel (install everything, most of them are useful).needed to set a proxy for this: git config -global http.proxy "".utilities: sudo pacman -S man-db man-pages nvim htop tree.run id to verify you're added to the right groups.visudo the sudoers file to give the wheel group access to sudo.ssh on as your new user, and su to root.After a lot of repeated tries, wpa_supplicant finally launched before NetworkManager on one boot, allowing me to ssh on and disable NetworkManager for good. I tried doing this, only to blow the network setup on my Pi, because once you set up the NetworkManager service, it would take over wlan0 on boot and because it didn't know the wifi configuration, it would never connect to the network, so I couldn't SSH/VNC onto it. One important thing to note: Don't try switching to NetworkManager without a working display and ethernet connection. This is still my primary means of using my Pi. Systemctl enable wpa_supplicant systemctl start wpa_supplicant this and rebooting, I was able to ssh onto my pi, by connecting it to my mobile hotspot. use timedatectl to see if the system clock is accurate:.From there, note down your pi's IP and ssh on to it. Plug in your Pi to ethernet, and use your WiFi router settings page to see all connected devices.The best way of setting up is to connect to your router via ethernet, then do an arp-scan -localnet (on mac, install with brew install arp-scan) to find the ip, ssh on, and get rolling (default user alarm, password alarm and root password is just root) Connecting and basics No drivers for Bluetooth, or Wifi set upįortunately, the ARM arch ships with a few more things: netctl, X11, and wifi drivers.Arch ships with nothing, and I mean nothingĪll these are forgiveable (and quite common on server distros), but then we have: Remember to download it from GitHub rather than from SourceForge: SourceForge mirrors are garbage, while the GitHub one downloads in under a minute.Īfter getting PINN, just point-and-click to install arch. Installation was fairly straightforward: NOOBS doesn't ship with an option to get arch, so PINN was used. So yeah, if you enjoy the hike a steep learning curve gives you, arch is perfect. And in the span of less than half a day, I've used atleast 6 utilities I've never seen or heard of before. So why arch? 2 Well, the biggest reason is learning: learning to setup arch and use it would teach me more about UNIX fundamentals than using a prebuilt OS. While definetly a suboptimal solution, for the upcoming courses (networks, parallel programming, OS), a core linux machine would be a neccessity.īefore you pick up your pitchforks, yes, RPi is ARM based: I know this is a completely different ballgame from CISC i386/x86-64 processors, which is also partly the reason I wanted linux on an ARM machine: we did ARM assembly in the previous course, so that'll make this easier? idk I'm bad at CS Baby Steps I got around this by running a VM on my 6 year old, 128GB mac sobs. The real need for a linux system became apparent last semester, when one of our courses needed a program that would run only on Windows/Ubuntu. Contextįor starters, I already use linux/unix systems quite a bit. I finally got around to installing Arch Linux on a Raspberry Pi 1: Here's how I did it. So, I needed a linux box that I could hack around, preferably at the kernel level. For the upcoming semesters, we have a ton of systems courses.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |