depau/arch-flo-junk
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

clean the README up, add further information

Browse source
This commit is contained in:
Davide Depau 2014-11-02 21:07:05 +01:00
parent c358fe321c
commit 888b6d979c
1 changed files with 159 additions and 150 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

299
README.md
View file

@ -1,215 +1,224 @@
# Arch Linux on Nexus 7 Flo Native # Arch Linux on Nexus 7 2013 Flo (Native)
Here are my instructions on getting Arch Linux ARM natively booting on the Here are my instructions on getting Arch Linux ARM natively booting on the
Nexus 7 Flo. Ideally this would be booting from a usb stick or a dedicated Nexus 7 2013 Flo. Ideally this would be booting from a usb stick or a dedicated
partition on the mmc but this is working for me now. partition on the mmc but this is working for me now.
## BUGS!!!
There is no frambuffer console :(
If you cannot get it booting you will need to If you cannot get it booting you will need to
reboot into recovery and check /proc/last_kmsg for the errors. Or try and build reboot into recovery and check /proc/last_kmsg for the errors. Or try and build
the UART cable (which I failed at) the UART cable (which I failed at)
The Software Refresher in the kernel does not work. You will need to run my ### What's working
- Wi-Fi
- Bluetooth
- ADB
- USB Reverse Tethering/RNDIS (guest)
- USB OTG (host)
- fb0
- Audio - you need to setup PulseAudio as systemwide. Not sure why it does not work as a normal user. You will also need the alsaucm files from libasound2-data_1.0.27.2-1ubuntu6_all.deb
### Bugs/What's not working
- There is no frambuffer console
- The Software Refresher in the kernel does not work. You will need to run my
refresher app or fix the kernel :) refresher app or fix the kernel :)
- The new xa code from x86-video-freedreno-git does not work. gpuaddr in
The new xa code from x86-video-freedreno-git does not work. gpuaddr in
kgsl_bo_gpuaddr comes back a 0 kgsl_bo_gpuaddr comes back a 0
- Hardware acceleration. Needs LibHybris, we're working on it.
## Quick Guide ### Not tested
1: I roughly followed the instructions form
https://github.com/borh/nexus-7-2013-arch-scripts to get a working chroot
first.
1a: remove trimslice packages from chroot - NFC (if you know how to test it please let @Davideddu know, I have a bunch of NFC tags to test it with. You can tag me in an issue).
2: Edit the init script to point to your arch.img or partition ## Quick guide (boot with fastboot)
3: Edit and Run makebootimage.sh 1. Follow the instuctions at https://github.com/borh/nexus-7-2013-arch-scripts to get a working chroot.
1. Remove trimslice packages from chroot.
1. Edit the init script (systemd-initramfs/init) to point to your arch.img.
1. Build the kernel (instructions below).
1. Build the initramfs (instructions below).
1. Edit makebootimage.sh to point to the new kernel and to the initramfs you just built and run it to create an Android boot image.
1. Use *fastboot boot <image\>* to boot the image you just created.
1. Enjoy ;)
4: fastboot boot newboot ## Booting with MultiROM (using an image)
5: ??? You will need to follow the guide at http://forum.xda-developers.com/showthread.php?t=2457063 to install MultiROM on your device.
6: Profit The init script needs to be modified to support this. You currently can't boot the same boot image via both fastboot and MultiROM.
## Booting with MultiROM 1. Create a ROM folder for ArchLinuxARM.
adb shell mkdir /data/media/0/multirom/roms/*<rom name\>*
1. Restart adbd as root using *adb root*; if your ROM doesn't support it, reboot to recovery.
1. Push the provided rom_info.txt file. You might want to edit it, it's a plaintext config file documented at https://github.com/Tasssadar/multirom/wiki/Add-support-for-new-ROM-type
adb push rom_info.txt /data/media/0/multirom/roms/*<rom name\>*/
1. Move your root image to /data/media/0/multirom/roms/ArchLinux*<rom name\>*/root.img
1. Edit the init script (systemd-initramfs/init) to point to your new root.img location, then rebuild the initramfs (you don't need to build the boot image for MultiROM).
1. Make sure you have the kernel zImage in
/data/media/0/multirom/roms/*<rom name\>*/boot/vmlinuz
and the initramfs in
/data/media/0/multirom/roms/*<rom name\>*/boot/initrd.img
1. Mount the image, and copy these files (with the same names) to /boot/ into it.
You will need to follow the guide at http://forum.xda-developers.com/showthread.php?t=2457063 first. ## Booting with MultiROM (directly from /data, no image)
1: The initcpio hooks have been modified to support this, so if you were using the old ones, you have to replace them with the new. You currently can't boot the same installation via both fastboot and MultiROM. *(coming soon)*
2: Boot the Nexus into Android recovery mode. Make sure /data is mounted. /data/media/0/multirom cannot be seen from normal Android. ## Booting from USB with MultiROM (not tested)
You basically have to follow the MultiROM image steps, but instead of placing the files into /data/media/0/multirom you will want to put them into a *multirom* directory inside of your fat32-formatted USB drive. You will however have to edit the init script, find the USB drive's device (it should be /dev/block/sda1 but don't count on that), mount it and pass the torch to systemd's init.
3: Create a ROM folder for ArchLinuxARM. This hasn't been tested yet. Detailed instructions will come as soon as I test it.
adb shell mkdir /data/media/0/multirom/roms/ArchLinuxARM ## Getting Wi-Fi working
4: Push the included rom_info.txt file. (it's a plaintext config file documented at https://github.com/Tasssadar/multirom/wiki/Add-support-for-new-ROM-type) A normal Nexus 7 Flo boot will call */system/bin/conn_init*, which does a whole lot of verifying your MAC address and then writes out a config with the MAC address in it. Very annoying (especially if you want to spoof it). To get around this you need a copy of the Wi-Fi configs and manually enable the wifi driver since it's not loaded on boot.
adb push rom_info.txt /data/media/0/multirom/roms/ArchLinuxARM/ The firmware.service is only needed since the firmware is not loaded in the initramfs.
5: Move your root image to /data/media/0/multirom/roms/ArchLinuxARM/root.img 1. Copy /system/vendor/firmware [android] to /usr/lib/firmware [arch] (you might want to mount system in the chroot or copy the files to /sdcard, then access them from /media/sdcard in the chroot).
1. *rm /usr/lib/firmware/wlan/prima/{WCNSS_qcom_cfg.ini,WCNSS_qcom_wlan_nv.bin}* <-- these are simlinks
1. *cp /data/misc/wifi/{WCNSS_qcom_cfg.ini,WCNSS_qcom_wlan_nv.bin} /usr/lib/firmware/wlan/prima/* <-- these are the files which conn_init writes your mac address to - again, use /sdcard or mount /data into the chroot.
1. Copy the provided firmware.service to /etc/systemd/system/
1. *ln -s /etc/systemd/system/firmware.service /etc/systemd/system/multi-user.target.wants/firmware.service*
1. *ln -s /usr/lib/systemd/system/wpa_supplicant-nl80211@wlan0.service /etc/systemd/system/multi-user.target.wants/wpa_supplicant-nl80211@wlan0.service*
1. *ln -s /lib/systemd/system/dhcpcd.service /etc/systemd/system/multi-user.target.wants/dhcpcd.service*
1. *ln -s /lib/systemd/system/sshd.service /etc/systemd/system/multi-user.target.wants/sshd.service*
1. Disable the wpa_supplicant hook in /etc/dhcpcd.conf by adding *nohook wpa_supplicant* at the end.
6: Make sure you have the kernel and ramdisk in /data/media/0/multirom/roms/ArchLinuxARM/boot/vmlinuz and /data/media/0/multirom/roms/ArchLinuxARM/boot/initrd.img. ### Setting up shared Wi-Fi configuration between Arch and Android
6a: Mount the image, and copy them (with the same name) to /boot/ in it. 1. Make sure /data is mounted at boot:
## To get WiFi Working
A normal Nexus 7 Flo boot will call /system/bin/conn_init which does a whole
lot of verifying your mac address and then writes out a config with the mac
address in it. Very annoying. To get around this you need a copy of the wifi
configs and manually enable the wifi driver since it does not start on boot.
The firmware.service is only needed since I do not load the firmware in the
initramfs (which I am haven't done yet)
1: Copy /system/vendor/firmware [android] to /usr/lib/firmware [arch]
2: rm /usr/lib/firmware/wlan/prima/{WCNSS_qcom_cfg.ini,WCNSS_qcom_wlan_nv.bin} <-- these are simlinks
3: cp /data/misc/wifi/{WCNSS_qcom_cfg.ini,WCNSS_qcom_wlan_nv.bin} /usr/lib/firmware/wlan/prima/ <-- these are the files which conn_init writes your mac address to
4: Copy firmware.service to /etc/systemd/system/
5: ln -s /etc/systemd/system/firmware.service /etc/systemd/system/multi-user.target.wants/firmware.service
6: ln -s /lib/systemd/system/wpa_supplicant-nl80211@wlan0.service /etc/systemd/system/multi-user.target.wants/wpa_supplicant-nl80211@wlan0.service
7: ln -s /lib/systemd/system/dhcpcd.service /etc/systemd/system/multi-user.target.wants/dhcpcd.service
8: ln -s /lib/systemd/system/sshd.service /etc/systemd/system/multi-user.target.wants/sshd.service
Note: Disable the wpa_supplicant hook in /etc/dhcpcd.conf
# Setting up shared Wi-Fi configuration between Arch and Android
1: Make sure /data is mounted at boot:
mkdir /data mkdir /data
echo '/dev/disk/by-partlabel/userdata /data ext4 errors=remount-ro 0 0' >> /etc/fstab echo '/dev/disk/by-partlabel/userdata /data ext4 errors=remount-ro 0 0' >> /etc/fstab
mount /data mount /data
1. Forcibly symlink the Android wpa_supplicant.conf to the Linux location.
2: Forcibly symlink the Android wpa_supplicant.conf to the Linux location.
ln -fs /data/misc/wifi/wpa_supplicant.conf /etc/wpa_supplicant/wpa_supplicant-nl80211-wlan0.conf ln -fs /data/misc/wifi/wpa_supplicant.conf /etc/wpa_supplicant/wpa_supplicant-nl80211-wlan0.conf
1. Create a name for the Android wifi group
3: Create a name for the Android wifi group
groupadd -g $(stat -c '%g' /data/misc/wifi) -r android_wifi groupadd -g $(stat -c '%g' /data/misc/wifi) -r android_wifi
1. Add your main user to said group, so you can access the control sockets. You will need to manually their path if you want to edit the Wi-Fi network configuration.
usermod -aG android_wifi *<your username\>*
4: Add your main user to said group, so you can access the control sockets. You will need to manually their path if you want to edit the WiFi network configureation. ## Getting fbterm console
## To get fbterm console 1. Copy provided fbterm/getty@.service to /etc/systemd/system/
Copy fbterm/getty@.service to /etc/systemd/system/ and fbterm/fbterm-login to 1. Copy fbterm/fbterm-login to /opt/fbterm-login and make it executable
/opt/fbterm-login and then systemctl enable getty@tty1.service 1. *systemctl enable getty@tty1.service*
ln -s getty@.service autovt@.service to get it on all vt's *ln -s getty@.service autovt@.service* to get it on all vt's
## To get X working ## Getting Xorg
Install xf86-video-freedreno-git (aur) Use the xorg.conf included
Install xf86-video-freedreno-git (AUR). Use the xorg.conf included
Instead of filling the AUR with crap you can use the mesa and libdrm PKGBUILDs Instead of filling the AUR with crap you can use the mesa and libdrm PKGBUILDs
included. Always use the git versions as they have the latest freedreno fixes included. Always use the git versions as they have the latest freedreno fixes.
Your .xinitrc should contain something like
~/refresher &
exec awesome
## Refreshing (refresher.c) ## Refreshing (refresher.c)
Since the MSMFB_SW_REFRESHER does not seem to be working i wrote this instead.
Just compile and put in you ~/ or whereever so xinit can run it.
You can also use the included systemd unit file for the refresher. Since the MSMFB_SW_REFRESHER does not seem to be working, I wrote this instead.
Just compile it inside of the chroot (do not crosscompile it on your computer), copy it to /bin/refresher and make it executable.
1: inside the initial chroot compile refresher.c and move to /bin/refresher You can use the included systemd unit file for the refresher:
2: copy systemd/refresher.service to /etc/systemd/system/refresher.service Copy the provided systemd/refresher.service to /etc/systemd/system/refresher.service
## Serial console
USB serial works. I had some problems connecting with the Android Composite Gadget, however just using the USB_G_SERIAL kernel config seems to work (it's enabled by default in the patched kernel).
To enable it, run
systemctl enable serial-getty@ttyGS0.service
and then you will be able to connect to the device via minicom or similar on /dev/ttyACM0.
Getting kernel console boot messages is still a no go as the device is registered too late to work.
## Enabling ADB and RNDIS (reverse USB tethering) ## Enabling ADB and RNDIS (reverse USB tethering)
1: Create this link for ADB to be able to find the shell, etc.
ln -s / /system
2: Add the included systemd-tmpfiles config files. They go in /etc/tmpfiles.d, and require a reboot to apply them. 1. Create this link for ADB to be able to find the shell, etc.
ln -s / /system
1. Add the included systemd-tmpfiles config files. They go in /etc/tmpfiles.d, and require a reboot to apply them.
ADB shell works, but you will need to set the size ($COLUMNS and $LINES) and terminal type ($TERM) manually. ADB shell works, but you will need to set the size ($COLUMNS and $LINES) and terminal type ($TERM) manually.
To use RNDIS, plug the Nexus into a computer and bridge the virtual ethernet adapter with your local network. Then, bring up the link and get an address as usual. The interface name should be 'usb0'. To use RNDIS, plug the Nexus into a computer and bridge the virtual ethernet adapter with your local network. Then, bring up the link and get an address as usual. The interface name should be 'usb0'.
# Kernel stuff # Kernel
You can use the kernel from here https://github.com/crondog/kernel_msm You can use the kernel from here https://github.com/crondog/kernel_msm. Use the **mr1** branch.
## To get Touchscreen working ## Building the kernel
Apply 0001-make-ektf3k-driver-report-non-MT-events-too.patch
## Debugging A guide to build kernels for Nexus devices can be obtained from Google: http://source.android.com/source/building-kernels.html
USB serial works. I had some problems connecting with the Android Composite
Gadget however just using USB_G_SERIAL seems to work. To enable run systemctl
enable serial-getty@ttyGS0.service and then you will be able to connect to the
device via minicom or similar on /dev/ttyACM0. Getting kernel console boot
messages is still a no go as the device is registered too late to work
## Kernel configs Just make sure you use the patched fork provided above instead of the default repository, or that you apply the patches below, otherwise you will likely have issues.
## Getting touchscreen working
Apply provided *0001-make-ektf3k-driver-report-non-MT-events-too.patch*.
## Kernel configuration
I used the following additional configs to get this working. Some might not be I used the following additional configs to get this working. Some might not be
necessary but it helps with debugging necessary but it helps with debugging
Required for display/graphics: *Required for display/graphics:*
CONFIG_FB_MSM_DEFAULT_DEPTH_BGRA8888 (with RGBA patch from robclark) - CONFIG_FB_MSM_DEFAULT_DEPTH_BGRA8888 (with RGBA patch from robclark)
CONFIG_DRM=y - CONFIG_DRM=y
CONFIG_MSM_KGSL_DRM=y - CONFIG_MSM_KGSL_DRM=y
Required for Wi-Fi/network: *Required for Wi-Fi/network:*
CONFIG_ANDROID_PARANOID_NETWORK=n - CONFIG_ANDROID_PARANOID_NETWORK=n
CONFIG_MODULES=y - CONFIG_MODULES=y
CONFIG_PRIMA_WLAN=y - CONFIG_PRIMA_WLAN=y
CONFIG_WCNSS_CORE=y - CONFIG_WCNSS_CORE=y
Required to boot: *Required for USB serial:*
CONFIG_FHANDLE=y - CONFIG_USB_G_SERIAL=y
CONFIG_DEVTMPFS=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
Debugging: *Required to boot:*
CONFIG_DETECT_HUNG_TASK=y - CONFIG_FHANDLE=y
CONFIG_DEBUG_SPINLOCK=y - CONFIG_DEVTMPFS=y
CONFIG_DEBUG_MUTEXES=y - CONFIG_UTS_NS=y
CONFIG_DEBUG_ATOMIC_SLEEP=y - CONFIG_IPC_NS=y
CONFIG_STACKTRACE=y - CONFIG_USER_NS=y
CONFIG_DEBUG_BUGVERBOSE=y - CONFIG_PID_NS=y
CONFIG_LOG_BUF_SHIFT=21 - CONFIG_NET_NS=y
CONFIG_PANIC_TIMEOUT=0 - CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
- CONFIG_FANOTIFY=y
- CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
- CONFIG_SECURITY_SELINUX_BOOTPARAM=y
If you use the kernel at https://github.com/crondog/kernel_msm, there is a default configuration named flo_defconfig which contains most of the needed options. *Debugging:*
## Build initramfs (Manually) - CONFIG_DETECT_HUNG_TASK=y
1: Edit makebootimage.sh with paths - CONFIG_DEBUG_SPINLOCK=y
2: cd systemd-initramfs; find . | cpio -o -H newc | gzip > ../minimal.initramfs - CONFIG_DEBUG_MUTEXES=y
3: ./makebootimage.sh - CONFIG_DEBUG_ATOMIC_SLEEP=y
- CONFIG_STACKTRACE=y
- CONFIG_DEBUG_BUGVERBOSE=y
- CONFIG_LOG_BUF_SHIFT=21
- CONFIG_PANIC_TIMEOUT=0
If you use the kernel at https://github.com/crondog/kernel_msm (mr1 branch), there is a default configuration named flo_defconfig which contains most of the needed options.
# Building the initramfs
## Manually
Make sure *abootimg* is installed.
1. Edit makebootimage.sh and correct paths
1. *cd systemd-initramfs; find . | cpio -o -H newc | gzip > ../minimal.initramfs*
1. *./makebootimage.sh*
## Build initramfs (mkinitcpio) ## Using mkinitcpio
1: Copy zImage to /boot/ 1. Copy zImage to /boot/
2: Copy modules to /lib/modules/`uname -r` 1. Copy modules to /lib/modules/`uname -r`
3: Apply mkinitcpio.patch 1. Apply mkinitcpio.patch
4: Copy hooks/imgmount and install/imgmount to /lib/initcpio 1. Copy hooks/imgmount and install/imgmount to /lib/initcpio
5: sudo mkinitcpio -p linux 1. sudo mkinitcpio -p linux
6: abootimg --create boot.img -f bootimg.cfg -k /boot/zImage -r /boot/initramfs-linux.img 1. abootimg --create boot.img -f bootimg.cfg -k /boot/zImage -r /boot/initramfs-linux.img
# Whats Working
Wifi
ADB
USB Reverse Tethering/RNDIS (guest)
USB OTG (host)
fb0
Audio -- Need to setup Pulse Audio as systemwide. Not sure why it does not work as a normal user
You will also need the alsaucm files from libasound2-data_1.0.27.2-1ubuntu6_all.deb
Bluetooth - We now have bluez5 support :) Only tested with a Wedge keyboard
# Not tested
NFC