GNU/Linux@N80XX

Search This thread
By:
Advanced…
S

seb7o

Senior Member
Feb 18, 2012
65
8
is it possible to get android and gnu installed, like when booting device: being asked which system to boot?
 
X-Stranger

X-Stranger

Senior Member
Sep 2, 2008
164
204
This requires boot loader to be changed. Currently we use only stock boot loader.

One of good possibilities to implement "boot loader" alike functionality is to setup special type of boot partition containing kernel with kexec-support and some menu utiity in initrd image. I've tried this, but looks like kexec does not work. If somebody knows how to fix it - please send me working kernel patch.
 
  • Like
Reactions: r_e_v, seb7o and damz37
R

r_e_v

New member
Sep 6, 2010
4
0
Patches and Config

X-Stranger said:
Posting updated Kernel versions + modules:
  • for the systems on mmcblk0p13: ....
  • for the systems on mmcblk1p1: ....
Based on Samsung offiical opensource kernel Update7 + our patches. You need to unpack the archive, put modules to the right place, update initramfs image, update recovery with fresh kernel and updated initramfs files.
Click to expand...
Click to collapse

Hello guys, huge thanks for this great job!! :highfive:
I'm interested to run Debian on my upcoming n8010..could you post kernel's config and patches? I definitely want to give it a try!
 
C

cctoro

Senior Member
Feb 23, 2013
68
19
Conflicting Dependencies

Wow, impressive! Very nice job.

I keep getting dependency conflicts when trying to update though. I'm new to Arch Linux, its going to take some getting use to.

Here is the error:

error: unresolvable package conflict detected
error: failed to prepare transaction (conflicting dependencies)
:: bluez an obexd-client are in conflict

Not sure how to resolve this.
 
E

evilx_systems

Member
May 4, 2013
6
1
cctoro said:
Wow, impressive! Very nice job.

I keep getting dependency conflicts when trying to update though. I'm new to Arch Linux, its going to take some getting use to.

Here is the error:

error: unresolvable package conflict detected
error: failed to prepare transaction (conflicting dependencies)
:: bluez an obexd-client are in conflict

Not sure how to resolve this.
Click to expand...
Click to collapse

I'm having similar issues trying to upgrade this image. The current upgrade for archlinux involves an intervention as discussed here:
*URL can't be listed because I'm a noob with < 10 posts :/ Go to the archlinux website...it's there *

I'd really like to upgrade this image so that I can install libreoffice from the repositories, which I currently can't do. From my attempt at following the instructions I was stopped because rc.d remained in sbin and was owned by the filesystem and initscripts. I tried moving sbin to sbin_old and forcing the upgrade, but I broke my image. It's not clear if it was broken due to the forced upgrade or having it hang afterwards after reboot or the subsequent e2fsck that gave me more problems than I've ever seen. Perhaps X-stranger has updated his image successfully and can post a new one, or walk us through what the problem is?:confused:

Also I've noticed that this image has something strange with gnome-games that's giving me problems doing a full update as well.

-jason
 
E

evilx_systems

Member
May 4, 2013
6
1
I went back to my backup image and now I'm getting the same bluez conflict that you are, something must have changed in the repos in the last two days and I have no idea either how to fix it....
 
C

cctoro

Senior Member
Feb 23, 2013
68
19
evilx_systems said:
I went back to my backup image and now I'm getting the same bluez conflict that you are, something must have changed in the repos in the last two days and I have no idea either how to fix it....
Click to expand...
Click to collapse

I ran #pacman -Rdd *filename* to get rid of any problem files like bluez and/or obexd-client. I was going to reinstall/update them after I updated the system, but I got a new error "file conflicts" in filesystem. So I ran #pacman -Syyu --ignore filesystem, this updated most of the files but gave more errors (don't remember what they were) and broke the image. The "file conflict" error in the filesystem seems to be a common problem in Arch Linux (its all over the Arch forums), I haven't been able to find a solution to.

If you want to save changes you've made, copy the revised linux.img to sdcard and if your image gets broken just replace the broken image with the backup.

Anyone get any other distro's working? Does anyone have a copy of the Debian image?
 
Last edited:
C

cctoro

Senior Member
Feb 23, 2013
68
19
cctoro said:
I ran #pacman -Rdd *filename* to get rid of any problem files like bluez and/or obexd-client. I was going to reinstall/update them after I updated the system, but I got a new error "file conflicts" in filesystem. So I ran #pacman -Syyu --ignore filesystem, this updated most of the files but gave more errors (don't remember what they were) and broke the image. The "file conflict" error in the filesystem seems to be a common problem in Arch Linux (its all over the Arch forums), I haven't been able to find a solution to.

If you want to save changes you've made, copy the revised linux.img to sdcard and if your image gets broken just replace the broken image with the backup.

Anyone get any other distro's working? Does anyone have a copy of the Debian image?
Click to expand...
Click to collapse

Has this been abandoned? I have not heard anything in a while.
 
E

evilx_systems

Member
May 4, 2013
6
1
I've been talking with X-STRANGER over email...he's using a different image now and manually updated all of his packages. He says he's really busy right now and can't post a new image. He did say that we shouldn't uninstall initscripts since he's using them...not sure how to proceed...I'm thinking maybe we should try starting with a new image and patch everything again.
 
  • Like
Reactions: cctoro
heavylildude

heavylildude

Member
Feb 13, 2011
46
16
Isla De Muerta
typogeek.com
Framebuffer

Hi all, been tracking down this amazing thread for awhile.. KUDOS for this amazing work!

Btw I've managed to successfully use framebuffer with ubuntu raring 'dual-boot' (not really sure if its dual boot) using Linux Deploy.. s-pen works, networking works etc..

How is this project different from Linux Deploy Framebuffer?
 
darksabre_x

darksabre_x

Senior Member
Nov 8, 2008
115
41
heavylildude said:
Hi all, been tracking down this amazing thread for awhile.. KUDOS for this amazing work!

Btw I've managed to successfully use framebuffer with ubuntu raring 'dual-boot' (not really sure if its dual boot) using Linux Deploy.. s-pen works, networking works etc..

How is this project different from Linux Deploy Framebuffer?
Click to expand...
Click to collapse

This preceded the framebuffer mode. It allows you to dualboot, however framebuffer mode on Linux Deploy is pretty awesome. While it's functionally similar, this setup is without all the android bits running underneath.
 
heavylildude

heavylildude

Member
Feb 13, 2011
46
16
Isla De Muerta
typogeek.com
darksabre_x said:
This preceded the framebuffer mode. It allows you to dualboot, however framebuffer mode on Linux Deploy is pretty awesome. While it's functionally similar, this setup is without all the android bits running underneath.
Click to expand...
Click to collapse

I see that..

Personally I love the easiness of framebuffer mode for its “no-set-up“ environment, no need to reconfigure wifi, 3g, bluetooth whatsoever.. just load up your xorg.conf and its done..

Is there any significant 'speed-boost' between 'real dual-boot' and framebuffer mode? Cos as far as my experience, my framebuffer set up run even smoother than Raring on Pineview/Cedarview Atom Netbooks! :D

Anyhow HUGE respect to everyone involved here! Someday we'll have X and mobile-environment running side by side.. Imagine Win 8 like Metro & Desktop mode applications running on an affordable double-octa-core processor, what a dream phablet it will become :laugh:
 
E

evilx_systems

Member
May 4, 2013
6
1
heavylildude said:
I see that..

Personally I love the easiness of framebuffer mode for its “no-set-up“ environment, no need to reconfigure wifi, 3g, bluetooth whatsoever.. just load up your xorg.conf and its done..

Is there any significant 'speed-boost' between 'real dual-boot' and framebuffer mode? Cos as far as my experience, my framebuffer set up run even smoother than Raring on Pineview/Cedarview Atom Netbooks! :D

Anyhow HUGE respect to everyone involved here! Someday we'll have X and mobile-environment running side by side.. Imagine Win 8 like Metro & Desktop mode applications running on an affordable double-octa-core processor, what a dream phablet it will become :laugh:
Click to expand...
Click to collapse

I've been unable to get frame buffer mode to work on the galaxy note 10.1. Can you tell me how you've got it configured? I can get graphics when I suppress the android UI, but I can't get any touch input. Any tips?
 
C

chachmar

Member
Sep 3, 2007
9
0
help

Hi all I have tried the aforementioned method but havent had any luck booting. I must inform you that I am using the stock image rooted. Steps I have taken are as follows, downloaded source for 5110 from opensource.samsung and compiled with patches using the config specified by the readme (supplied config not for my device), modified initrd as described, remade recovery image with abootimg, after all of this when I boot into recovery it shows the samsung logo pauses at black screen for a second shows samsumg logo again and then reboots into android. Has anyone ran into this problem? My device in its current state can run cwm recovery so I know it supports custom boot.img. I donk know where I go wrong. Is there any way to debug at boot obviously logcat is not an option?
 
heavylildude

heavylildude

Member
Feb 13, 2011
46
16
Isla De Muerta
typogeek.com
evilx_systems said:
I've been unable to get frame buffer mode to work on the galaxy note 10.1. Can you tell me how you've got it configured? I can get graphics when I suppress the android UI, but I can't get any touch input. Any tips?
Click to expand...
Click to collapse

What rom are u on and what distro did u use? I'm on custom stock (self debloat) 4.1.2 using ubuntu raring 13.04 set your video to fb0 and drop the android UI, you'll be able to boot back to android after you logout from ubuntu.. make sure you set your xorg accordingly.. match your xorg.config with your android input.. you can take a look at your android's via android terminal typing cat proc/bus/input/devices

Simply include input event for spen, bluetooth keyboard, mouse, etc.. :good:
 
  • Like
Reactions: crashtheface
You must log in or register to reply here.

Similar threads

I
[N8000][ROM 4.4.2 Samsung offcial not final] So I herd u lieke kitekats?
Replies
667
Views
291K
L
lucato
X-Stranger
Ubuntu for N80xx
Replies
240
Views
70K
X-Stranger
X-Stranger
H
[HOW TO] Install Native ArchLinux on N80XX [HOW TO]
Replies
89
Views
76K
J
juasjuas
LiMITZERO
[ROM][OFFICIAL][STOCKROM] N8000XXUDNE4 KitKat (4.4.2) (18.05.2014)
Replies
186
Views
216K
L
lucato
G
N8000 PIT File - How to save your PIT file
Replies
57
Views
156K
M
maxcaxxoduro98

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 24
    E
    exception13
    I'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/opensgn
    View
    11
    X-Stranger
    X-Stranger
    How 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
    As soon as you done with settings, get back and press "Download" button, then wait until downloading, installing, configuring is done. Voila! Now you can press "Play" button and work with your favorite distribution right from Android, or connect to it remotely from desktop. Just use proper VNC/SSH client. I was using VNC Viewer for VNC and ConnectBot for SSH.


    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:
    I've unpacked all this to /opt folder:
    • /opt/linux - unpacked kernel sources
    • /opt/platform_prebuilt-master - prebuilt toolchain
    You'll also need my kernel config and patch based on the config/patch ((fix for touchscreen and power button) provided by exception13 - I've just tuned it and added a few fixes for successfull compilation. Please find both files attached to this message. The file config.txt must be renamed to .config and moved to /opt/linux, n8000.patch must be applied to kernel sources (something like "cd /opt/linux && patch -s -p1 ../n8000.patch"). My kernel config uses the next kernel parameters: "root=/dev/loop0 ro rootfstype=ext4 rootwait quiet". E.g. it suggests to boot from loopback device, but you can change it to /dev/mmcblkXX, if you have already re-partitioned EMMC and installed Linux on separate partition (I'm have done this later). Any change to kernel config can be done using "make menuconfig" inside kernel sources folder. After you done, run this:
    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
    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.

    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:
    Code: 
    dd if=/dev/block/mmcblk0p6 of=/boot/recovery.img
cp /boot/recovery.img /boot/recovery.img_orig
    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: 
    # 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
}
    Then I've run:
    Code: 
    cd /boot
mkinitcpio -k 3.0.31 -g initrd.img
    Okay, right now a few other tricks :) 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:
    Code: 
    cd /boot
abootimg -u recovery.img -k zImage -r initrd.img
dd if=/boot/recovery.img of=/dev/block/mmcblk0p6
    Well done! Now, we are almost ready to reboot.


    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...
    View
    10
    X-Stranger
    X-Stranger
    ArchLinux

    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 better
    View
    7
    E
    exception13
    i create http://code.google.com/p/opensgn. current in this repo my linux kernel for n8000 and some stuff
    View
    6
    X-Stranger
    X-Stranger
    I 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 :)
    View

New posts