I'm on the stock rom 4.1.2, ive tried several distros the one im using right now is arch with lxde. Can you link me to something explaining how to set up the xorg.conf? That cat command you listed didnt return anything in android.
GNU/Linux@N80XX
- Thread starter exception13
- Start date
@heavylildude Please, can you write a complete guide how to install Raring using Linux Deploy and framebuffer? And also posting all the necessary files. Thanks.
alrite mate, will try to write about this but gimme some time.. office works gone bizzare these few days.. :silly:
thats strange, below's me cat results.. will try to write about mine in few days mate.. hands quite full rite now, sorry..
it works now...not sure what I screwed up before...ill search around and see if I can get it xorg configured now...thanks!
Thaks again, but please can you post just xorg.conf.
I have managed to get Ubuntu Raring on my N7100 using framebuffer and also the SPen, by setting the input into Linux Deploy (/dev/input/event12). I can't seem to get working any onscreen keyboard (gnome/kde). How are you doing it?
Also, were you able to get system-center in any DE working?
Thanks.
Last edited:
aaah good for ya mate! So I wont need to write anymore LOL... okay here's my xorg.conf
Code:
Section "ServerLayout"
Identifier "Layout0"
Screen "Screen0"
InputDevice "Mouse0" "CorePointer"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "evdev"
Option "Device" "/dev/input/event6"
Option "ButtonMapping" "1 3 0"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "evdev"
Option "Device" "/dev/input/event8"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "evdev"
Option "Device" "/dev/input/event9"
EndSection
Section "Device"
Identifier "Card0"
Driver "fbdev"
Option "fbdev" "/dev/graphics/fb0" #linuxdeploy
#Option "Rotate" "CW"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection@heavylildude, Thank you again for replying but can you post a screenshot with the end of the file /proc/bus/input because on my N8000 i don't have anything over event7. So i need this to see the name of the devices for the event mapping. Event6 i think it is your SPen mapped as mouse0, but i don't make the rest of them.
What about an onscreen keyboad. What are you using?
Thanks.
What about an onscreen keyboad. What are you using?
Thanks.
Last edited:
Yep, event6 is spen mapped as mouse with pen button click as right-click, event 8 and 9 are bluetooth mouse and keyboard, event 7 is compass sensor which i didnt use..
I'm using xkvbd as my onscreen keyboard..
Hi @heavylildude I thought that you have mapped the touch buttons or the touchscreen some how. I don't have any bluetooth devices, so that's why the missing events.
Also, xvkbd was the only onscreen keyboard that worked.
Have a nice day and thank you for all your help!
Last edited:
Not really mate, Florence Keyboard is working as well.. Its just rather ugly for me taste (It has bubbly skin whatsoever LOL) Glad its working on ya mate, cheers! :highfive:
Yay after weeks of efforts I can boot the selfcompiled kernel ...
Fedora 18 - KDM/ KDE
Try to write a Howto soon ...
Video is on youtube
Nice Job. Looking forward to a guide. Can you share your image files with us? Can we just flash them like the Arch files?
Here is the link to the videohttp://www.youtube.com/watch?v=EzE-D3u3ulA
Fairly excited about the prospect of KDE and Krita running on the note.....any chance we could get that how-to ? Thanks
Request for updated links
Hello
I havent been able to work with this project for a few months as I was busy with school
Can someone please link the updated rootfs image and recovery image
And please mention whats working and any bugs
Thanks
Hello
I havent been able to work with this project for a few months as I was busy with school
Can someone please link the updated rootfs image and recovery image
And please mention whats working and any bugs
Thanks
The most recent combo of linux.img/recovery.img doesn't work too well. It will boot, but many things can't be installed/updated. A complete update fails miserably. One main thing seems to be the need to update the mali driver with the most recent xorg server version. No one has posted how that was done originally, so I'm a bit at a loss on how to get that accomplished. Here are the steps I've done to get close, but still stuck on the video driver:
Edit /etc/pacman.d/mirrorlist to get the closest mirror, edit /etc/pacman.conf to point cache to either mounted ext sdcard or /tmp (not enough space in the default to deal with all packages; ignore if you have expanded the size of the image)
pacman -Rdd bluez gnome-games
(removes some conflicts and annoying replacement messages)
pacman -Su --ignore filesystem,bash
(downloads a bunch of stuff, installs)
pacman -S bash
rm -Rf /usr/sbin (needed to get filesystem installed)
pacman -Su
(installs filesystem)
System reboots but fails to load mali driver (either no loading of X or get the sad computer screen face).
I think an updated version of mali driver is likely all that is needed in this case. Looking into how to compile that now.
relevant part from Xorg.log.0:
Edit /etc/pacman.d/mirrorlist to get the closest mirror, edit /etc/pacman.conf to point cache to either mounted ext sdcard or /tmp (not enough space in the default to deal with all packages; ignore if you have expanded the size of the image)
pacman -Rdd bluez gnome-games
(removes some conflicts and annoying replacement messages)
pacman -Su --ignore filesystem,bash
(downloads a bunch of stuff, installs)
pacman -S bash
rm -Rf /usr/sbin (needed to get filesystem installed)
pacman -Su
(installs filesystem)
System reboots but fails to load mali driver (either no loading of X or get the sad computer screen face).
I think an updated version of mali driver is likely all that is needed in this case. Looking into how to compile that now.
relevant part from Xorg.log.0:
Last edited:
debian is working, but in external sdcard
First of all, thank you very much to you and exception13. You rocks!
I follow your instructions and build a Debian/Gnu Linux perfectly. But without mali support.
Can you please share the pacthes ? Because, i'm not using rootfs in internal, but in a external sdcard.
Thankyou again.
First of all, thank you very much to you and exception13. You rocks!
I follow your instructions and build a Debian/Gnu Linux perfectly. But without mali support.
Can you please share the pacthes ? Because, i'm not using rootfs in internal, but in a external sdcard.
Thankyou again.
Is there any chance of seeing a more popular OS, like Fedora, Linux Mint, Debian or Ubuntu being released? I've looked all over XDA and with Google but to no avail. Everything is either ArchLinux (absolutely foreign to me and the releases become crippled after any sort of update) and Kali (really? sacrificing 7GB of space?). Someone please help us out, this tablet is great with Android, it can be greater with Linux.
Ubuntu
I've been working on Ubuntu and got it partially worked but not fully. I decided to abandon the project as I got no help from anyone. If anyone wants to help me out, I'm happy to sacrifice my time again for this.
Thanks
I've been working on Ubuntu and got it partially worked but not fully. I decided to abandon the project as I got no help from anyone. If anyone wants to help me out, I'm happy to sacrifice my time again for this.
Thanks
Please by all means release what you have working. Arch is even worse than kali for me, as everything I attempt to do crashes it. Chromium cant even load pages fully.
Sent from my GT-N8013 using xda app-developers app
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
24I'm successfull running Debian GNU/Linux on my SGN 10.1 with "dualboot" (my kernel and debian initrd in recovery partitions). It's very easy and nice to use.
look at demo video
currently don't work: GPU (hardkernel can release exynos Xorg drivers for Odroid project, DRI work in progress), MFC (hardware encoder/decoder), cameras (work in progress), gps (work in progress), modem (work in progress).
and it's nice work with my laser printer via cups
---
Linux Kernel source code and other stuff http://code.google.com/p/opensgn11How To install Linux to N80XX
Okay, below is my successfull story, which is still going on.
So, as the prerequisite you need to have Samsung Galaxy Note 10.1 rooted. You can do this anyhow described on the forum, I've used "Exynos Abuse" utility for that purpose.
The first step that I've done - got chrooted Linux distribution. The easyest wat is to install "Linux Deploy" program from Google Play, then select options you like. I've choosen the next:
- distribution: ArchLinux (there are also Ubuntu, Debian, and a few more in the latest version)
- version: latest
- architecture: armv7h
- mirror address: http://de.mirror.archlinuxarm.org
- installation type: image file (this is important, because I wanted to later boot Linux using loopback device)
- destination path: /sdcard/arch.img (internal emmc "sdcard")
- image size: 4096 (in Mb, e.g. 4Gb - better this size, because later you might want to move it to your real sdcard)
- filesystem: ext4
- username: stranger
- DNS-server: automatic detection
- locale: en_US.UTF-8
- desktop environment: LXDE (works fast when you don't have 3D acceleration or work via VNC)
- install GUI: yes
- SSH: yes
- VNC: yes (no, if you don't want to work with your chrooted environment via VNC client)
- other options: you might select as you like. Later I've added run of shell script, which was configuring a few things very useful for my chrooted Linux
All right, all this looks good, but how to get dualboot and run Linux natively? As you know, our device already has dual boot: regular Android and recovery. We'll just replace recovery with our Linux kernel (zImage) and initramfs (initrd.img), so they'll boot our Linux. For sure we can use the native Android kernel, but if you want to get for example CIFS filesystem support and working touchscreen - you need to compile your own kernel. For that purpose we need:
- Linux distribution where we'll compile kernel. I prefer to do this in clean environment, so I've used Ubuntu in VirtualBox. You don't need to set up it from scratch, just download pre-ready Ubuntu image for VirtualBox from here: http://sourceforge.net/projects/virtualboximage/files/UbuntuServer/12.10/ubuntu-12.10-server-i386.7z (there are also other images ready for you, if you don't like Ubuntu: http://virtualboxes.org/images/)
- GCC 4.4.3 cross-compiler for ARM. You can also download prebuilt Android toolchain from here: https://android.googlesource.com/platform/prebuilt (just clone this with Git client)
- Samsung kernel sources: http://opensource.samsung.com/recep...earchValue=GT-N8000_JB_Opensource_Update1.zip (this archive contains 2 tar.gz files, we need the one with kernel)
- /opt/linux - unpacked kernel sources
- /opt/platform_prebuilt-master - prebuilt toolchain
After compilation is done, you can find brend new shining kernel image as /opt/linux/arch/arm/boot/zImage file, and modules in /lib/modules/3.0.31 folder. I've copied those files to my chrooted Linux using SCP (zImage to /boot and modules folder to /lib/modules), and all other things was doing here: started LinuxDeploy, pressed Play, logged in to Linux using SSH.Code:export ARCH=arm export SUBARCH=armv7h export CROSS_COMPILE=/opt/platform_prebuilt-master/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- cd /opt/linux make -j2 make modules_install
So, we have kernel, modules, but still need to built initrd.img and replace original recovery with ours. First we need to get original recovery image, because we'll just update it and write back. By the second, we want to keep copy in safe place, just in case:
Preparing initrd.img depends on distribution you are working with. My ArchLinux has mkinitcpio utility, but as soon as I want it to boot from loopback device I did a few tricks based on the next HowTo: http://felixc.at/ArchLinux-loopback (I just needed /lib/initcpio/hooks/looproot file and /lib/initcpio/install/looproot, fixed /etc/mkinitcpio.conf by adding looproot to HOOKS, and properly changed /etc/fstab). Please note that internal sdcard is not ntfs or vfat, it is ext4, so the file looproot should be a bit different, and there is no need to include ntfs-3g or fuse into initrd. Also the path to arch.img file is /media/arch.img on /dev/mmcblk0p12 partition, so the looproot hook will look like this:Code:dd if=/dev/block/mmcblk0p6 of=/boot/recovery.img cp /boot/recovery.img /boot/recovery.img_orig
Then I've run:Code:# vim:set ft=sh: run_hook () { # Now mount the host filesystem mkdir /host mount -t ext4 /dev/mmcblk0p12 /host -o defaults,noatime,acl,barrier=1,data=ordered # And the loop filesystem losetup /dev/loop0 /host/media/arch.img mount -t ext4 /host/media/arch.img /new_root -o defaults,noatime,acl,barrier=1,data=ordered mount --bind /host /new_root/mnt/sdcard }
Okay, right now a few other tricksCode:cd /boot mkinitcpio -k 3.0.31 -g initrd.img Install abootimg utilities package (ArchLinux users can find them in AUR if I remember correcly). Then run "abootimg-unpack-initrd" in "/boot" folder, this will create "/boot/ramdisk" directory, go into it and edit "init" file commenting out ""$mount_handler" /new_root" line. Then run "abootimg-pack-initrd" in the same path and get initrd.img finally ready. To update recovery.img with our files and write it back to the system run:
Well done! Now, we are almost ready to reboot.Code:cd /boot abootimg -u recovery.img -k zImage -r initrd.img dd if=/boot/recovery.img of=/dev/block/mmcblk0p6
The last things: install Xorg + fbvev video driver + evdev input driver + some login manager ("lightdm" for example) + some onscreen keyboard (I would recommend "florence"). Configure login manager to autologin. Make /etc/X11/xorg.conf looking like this:
Code:Section "ServerLayout" Identifier "Layout0" Screen "Screen0" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Touchscreen0" "SendCoreEvents" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "evdev" Option "Device" "/dev/input/event0" EndSection Section "InputDevice" Identifier "Mouse0" Driver "evdev" Option "Device" "/dev/input/event6" Option "ButtonMapping" "1 3 0" EndSection Section "InputDevice" Identifier "Touchscreen0" Driver "evdev" Option "Device" "/dev/input/event1" Option "Calibration" "0 4096 0 4096" EndSection Section "Device" Identifier "Card0" Driver "fbdev" Option "fbdev" "/dev/fb0" VendorName "Unknown" BoardName "Unknown" EndSection Section "Screen" Identifier "Screen0" Device "Card0" DefaultDepth 24 EndSection Section "DRI" Mode 0666 EndSection
if all is okay, we can logout our chrooted system, press "pause" button in LinuxDeploy program and try to poweroff tablet. Press buttons "Volume-Up" and "Power", wait until Linux booting messages appear, and release buttons. If you've done all correctly, graphics should be started and LXDE too. Touchscreen must be working as touchscreen, S-Pen as mouse, when tablet is idle for a long time and screen becomes dark - just press "Power" button.
If something is wrong - you can reboot your tablet to Android, login to chroot via LinuxDeploy and fix anything you need.
The next things we will do are: configure WiFi, Bluetooth, sound. And also will repartition emmc and move Linux to the internal native partition (optional). See my next messages...10ArchLinux
For the interested people, below are the links to the updated recovery and rootfs images with ArchLinux:
- recovery: http://dfiles.ru/files/r6y96x5oo
- rootfs: http://dfiles.ru/files/dcolx02nj
Changelog:
- rootfs image size increased up to 3Gb
- Samsung Kernel Update 5 + our patches + working Mali/UMP support merged
- LXDM/XFCE stuff removed
- ArchLinux updates installed
- GDM/Gnome3 + extra packages installed
- wpa_supplicant disabled, NetworkManager activated instead
- Mali video driver and all dependencies installed and configured, so Gnome UI acceleration should work
How to install on to device with stock firmware:
- root your device and make sure you have "dd" utility
- backup your stock recovery partition just in case (dd if=/dev/block/mmcblk0p6 of=recovery.img_orig)
- burn recovery image to recovery partition (dd if=recovery.img of=/dev/block/mmcblk0p6)
- put rootfs file to the "internal" sdcard
- reboot to recovery and see Linux booting
- see GDM, select "android" user, enable onscreen keyboard if needed (in the accessibility menu, top right corner), type "changeme" password and press enter
P.S. ADB interface still works in case something is wrong and you need to login to Linux "from the backdoor"
P.P.S. The images are posted "As Is", feel free to change anything you think works incorrectly or you can do better7i create http://code.google.com/p/opensgn. current in this repo my linux kernel for n8000 and some stuff6I have got a few advices and help from exception13, and has successfully compiled kernel, replaced recovery and now have ArchLinux working natively on my N8000. However it is in loop-filesystem placed on emmc, instead of repartitioning. But this might be more useful for most of users. So, I'm going to post a small HowTo and probably something pre-ready for you very soon.
P.S. Attached is the picture of "Home PC" based on N8000 + Apple Wireless Keyboard + bluetooth mouse
