Hello . every one :laugh:. May i ask support for running linux natively on tab 3 7.0.?
Currently i could run Kali ,Ubuntu and Debian in my tablet,,, but only in chroot method , another is i am also able to install the image file (kali.img) in the 2nd partition of my ext sdcard to give it more space,,,, .
The only method that i couldnt make is to run it natively on this tab,,,, I hope there is solution to this ,,,,
How did you get the chroot method to work? I can't get it to
Sent from my 831C using XDA Free mobile app
reinaldistic said:
How did you get the chroot method to work? I can't get it to
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
just download the complete linux installer ,allow superuser permission
then go to /data/data/com.zpwebsites.linuxonandroid/files
you will see a bootscript.sh file .Edit it using a text editor you prefered and find this line
"mount -t ext2 /dev/block/loop255 /data/local/mnt"
and edit it as
"mount -t ext4 /dev/block/loop255 /data/local/mnt"
save the file. and boot linux now via complete linux installer.
You must have terminal emulator and vnc (if you want to see the GUI).
:good:
stuff to DO
anvil_10 said:
Hello . every one :laugh:. May i ask support for running linux natively on tab 3 7.0.?
Currently i could run Kali ,Ubuntu and Debian in my tablet,,, but only in chroot method , another is i am also able to install the image file (kali.img) in the 2nd partition of my ext sdcard to give it more space,,,, .
The only method that i couldnt make is to run it natively on this tab,,,, I hope there is solution to this ,,,,
Click to expand...
Click to collapse
anvil,
working on p5210 towards this end.
you need
1 an arm-linux distro set to /boot /root and/or /system and /home on seperate partitions and then an .img of those partitions
to correspond to the limitations of your devices mmcblk setup.
2 rebuild your kernel to work with the above - mountpoints dev etc.
3 put up with android for a while because figuring out the above is going to take a WHILE.
if i figure out anything i will post.
m
an afterthought- most of it's already here in a lesser form i think it's mostly
unhooking from one userspace setup into another.
moonbutt74 said:
anvil,
working on p5210 towards this end.
you need
1 an arm-linux distro set to /boot /root and/or /system and /home on seperate partitions and then an .img of those partitions
to correspond to the limitations of your devices mmcblk setup.
2 rebuild your kernel to work with the above - mountpoints dev etc.
3 put up with android for a while because figuring out the above is going to take a WHILE.
if i figure out anything i will post.
m
an afterthought- most of it's already here in a lesser form i think it's mostly
unhooking from one userspace setup into another.
Click to expand...
Click to collapse
yeah i saw many post on other forum your procedure, but unfortunately i dont have any idea how to do it, like making the custom kernel to boot the linux distro instead of android,
init process and initramfs
anvil,
i was reading on another site that the linux kernel since 2.6 [i think] has a default behaviour of searching
for an init process in alternate locations when it can't find the first one, there's also an option
during configuration that allows you to specify an specific location of/for the ramdisk.
meaning if i understand it correctly, the kernel itself is bound to your boot/kernel mmcblk
by the bootloader BUT you could locate your init/ramdisk "off-world" by setting a different / location in kernel cmdline
you can also specify support for different compression methods for initramfs/initrd but i'm not sure if that actually builds in
or if you need a module [*.ko].
m
kali linux
How to get kali linux on tab 3 7.0?? Plz tell me . Tell what all things needed and how to??
Related
Hi !
I'm actually porting/playing with ubuntu on my Galaxy S. The goal would be to boot ubuntu "natively" from the ubuntu initramfs, but since i was unable to get a working framebuffer output on kernel boot (if someone have a solution for this, it would really help me), i'm using a chrooted environment for now. Some guys already had ubuntu to run on the Galaxy S in a chrooted environment, but the android UI was still running (using a lot of memory) and we had to use VNC to experience the ubuntu desktop. With this version, X is using the s3cfb framebuffer and fbdev driver to draw to the screen. I have also modified a Xorg input driver (plpevtch) to have a preliminary touch screen support. Since we still run it after the android services initializations, ubuntu will use the current connection (wifi, 3G).
If someone want's to play/help/try this stuff, here is the procedure i'v done for now :
Requirements :
- A Linux computer ( tested on ubuntu 10.10 )
- Galaxy S i9000 running an android kernel with ext2 support ( tested with Universal lagfix kernel )
- root (provided with the previous kernel i think)
- busybox (market)
- sdcard 2GB at least, primary partition formated to ext2 (play with the scripts to change to fat or ext4 etc)
- I think that's all
Download :
Download the attached package and extract it, this one contains the required scripts to download/patch ubuntu, prepare the sdcard, and stat/stop ubuntu.
Usage :
create.sh :
usage : create.sh /path/to/my/ext2/sdcard
This script will download the ubuntu netbook 10.10 compressed image for arm, decompress it, mount it then copy the filesystem to a specified path (should be an ext2 formated partition on the sdcard, and be the first partition on the sdcard ( /dev/mmcblkXp1 ).
Should be run first, one time ...
start.sh :
usage : start.sh
This script run "droid_ubuntu_init.sh" on the phone, which stop the android interface, mount the sdcard, prepare the chrooted environment and start a chrooted session (chroot_init.sh, which simulate a "daemon" to allow services to run in the background and start the ubuntu desktop.
Should be run everytime you wants to start ubuntu.
update.sh :
usage : update.sh
At the first "boot", ubuntu desktop (X) will not work, we have to update the distribution. To do so, run "start.sh" (if not already done) to start ubuntu, then run this script. It will update ubuntu (you should really use a wifi connection to do so), and X should then work. It will also install an ssh server. This will take a long time
Should be run one time.
====== Notes =====
If you want to run some "services", you should edit the file "scripts/chroot_init.sh" and add your service here (after the ssh service for example).
The package contains the "patch" applied to the ubuntu rootfs, and the sources of the modified touchscreen xorg input driver.
I did not work on a "stop" script yet, you'll have to reboot the phone if you want the android UI back.
It's really a work in progress, nothing really usable for now.
This is realy cool thumbs up
Il defently start looking at this at first possible time slice.
Download the attached package
Click to expand...
Click to collapse
Hi, where is the script ?
I would love to see Ubuntu running in native mode like it did on my former HD2 (witch, btw, i still think it's the best smartphone ever, Galaxy S - no were near).
mdalacu said:
Hi, where is the script ?
I would love to see Ubuntu running in native mode like it did on my former HD2 (witch, btw, i still think it's the best smartphone ever, Galaxy S - no were near).
Click to expand...
Click to collapse
Won't that be primarily because of the HUGE amount of development for it?
What about trying with a lightweight disto like puppy linux? last one uses lucid lynx package and it can run in ram (so very light).
Also maybe you can make some kind of "boot menu" using recovery mode:
in recovery mode, android is not started so if we add an entry to to recovery to run the start script on the sd from there it should be what you are looking for.
The only big problem i see for me to port ubuntu or anything else natively is a way to debug the boot process. Unfortunately, i was unable to get the kernel framebuffer to work, i would really need some help on this. For now it work great enough in a chrooted env to port some drivers etc. Anyone ? Else yes i'm using a custom rootfs to debug the kernel/drivers/rootfs.
Let's hope i find the time to try this tonight, while booting from a Ubuntu livecd
Oups, i did forget to attach the files. .. Will do so tomorow.
Has anyone worked on "really" porting another distro, done some work on kernel drivers? Actually it seems the s3cfb framebuffer isnt hardware accelerated using fbdev, preventing screen rotation and such. Any hint?
Hi,
I'm a french poweruser of Ubuntu (Server/Desktop).
May I have your script please?
Thanks,
RolluS
Hi,
I'm a french poweruser of linux
Mais ou sont donc les scripts ?
How is the script ?
Julien_050
Cpasjuste said:
Oups, i did forget to attach the files. .. Will do so tomorow
Click to expand...
Click to collapse
Posting the script might generate more interest.
When the files are up, i will try it thx.
koe1974 said:
Posting the script might generate more interest.
Click to expand...
Click to collapse
+1
hi, i was almost at goal, but when starting X-session, it unmounts my sd card... any ideas?
Right when it starts?
Maybe some x app is taking over the sdcard.. just an idea
I've been working on a set of scripts that will install Debian on a running XDAndroid. There are a lot of sites that offer similar pre-packaged collection, but they always seem to include too much (aka 700M downloads) or have files from various places.
I have so far gotten the initial setup up and running pretty consistently. This is not meant to replace Rhodbuntu, but act as a co-existing subsystem along with Android using what is known as chroot. As Android uses the kernel derived from Linux, Debian's GNU subsystem can interface pretty well with our kernel.
One of the major stumbling blocks for the msm72k chips is that it is based on the older ARM1136 (ARM6) cpu, and the current armel distribution targets Cortex (ARM7) platform, which is incompatible and will segfault when run on our msm's. To my knowledge, Debian 5.0 (lenny) or Ubuntu 9.04 is the last supported binary-compatible distribution widely available. Debian is semi-supported with patches for the near future, but the same cannot be said for Ubuntu. While it is possible to cross-compile a newer version to run on ARM6, that is beyond the scope and man-effort for this project.
Currently, the files required to get a bare-bones Debian system is what I wrote in the past 24hr, plus either a debian root tarball (which runs about 90M on mine) or a Debian cdebootstrap-static that can be downloaded from your nearest Debian mirror. Using cdebootstrap means a consistent root image can be made from official Debian sources, as well probable support for Ubuntu or other Debian-based distribution having an armel static cdebootstrap (cdeb). In fact, since I have no desire to upload 90M over my phone, using cdeb is your only way to get your system using my script for now. Please read top part of debian.sh inside the zip file to understand how to use the cdeb support.
Using it is pretty straightforward. Unzip the contents to /sdcard, open terminal, su and cd, and sh debian.sh (along with what's necessary for cdeb). Once you have run debian.sh and have a working GNU subsystem, typing "linux shell" is enough to start a chroot'ed bash shell. I suggest starting off with "apt-get update" and start installing some other packages.
The script should be generic enough to work on any Android system that does not have a brain-dead busybox residing in /sbin (aka Epic). The only "odd" requirement is that lenny cdeb requires quite a few files in "/usr". I solved that by symlinking it to the toolset mount directory. You will also need at least 600M free on your SD card to create a looped fs image. Don't ask about VNC support yet, I need to go through installing it before that is supported.
As for other FS support that is up to the xdandroid kernel developers. They would need to add support for fs other than ext2 before I can even add support for that. Feel free to suggest ideas to improve this.
http://db.tt/pFkD9ou
Update for 0.20:
Rewrote the linux scripts.
No longer allow linux to start without su, due to restrictions by superuser.apk.
Added check command, will e2fsck the image if e2fsck is available.
Uses mount -t auto instead of -t ext2.
Update for 0.15:
Fixed typo for cp tool/data that caused copying of directory instead of content.
After running cdebootstrap continue with the rest of script instead of exiting.
Use mountpoint instead of relying on -e hack.
Add restart to list of commands.
Make sure stuff is unmounted after running script and make "stop" a bit more intelligent.
Change cdebootstrap default to squeeze.
Create /usr/conf/fs* if it doesn't exist, should get rid of error messages.
-- Starfox
Not sure where you got your info about 6.0 segfaulting - Squeeze is going pretty strong on my rhod 400.
Two-step debootstrap ftw.
Well, I've had supposed ARM6 binaries segfault or illegal instruction on me. If squeeze works, great. Perhaps you'd be willing to upload a root tarball for those who don't want to go through with doing debootstrap.
I was told by more than one person that lenny was the latest that properly supported ARM6 armel. My script is easy enough to modify to support different Debian distros.
-- Starfox
I just wanted to give you a heads-up in case you hadn't tried squeeze - it works just fine. I haven't put it through its paces yet, but I did get a vncserver up and going last night just to satisfy my curiosity. Other than some resolution issues, this too was fairly painless.
I think it'll take me more effort to upload a tarball on my connection than for a non-noob user to debootstrap 6.0 on their phone. As far as the beginner, I am not sure that a tarball would be doing them any favors, there's something to be said about head-butting against the installation process.
Good job with the script by the way.
Nice script. Worked on second try, some corrupt packages, not the scripts fault. Its a bit slow with connectbot but using a local dropbear helps alot.
Thanks
Updated to 0.15. Script shouldn't encounter mount-point issues and should create /usr/conf automagically. Updated the default to squeeze, I still used lenny-backport cdeboot-static to test it out.
-- Starfox
Updated to 0.20. Mostly internal changes, but now supports other filesystem types. Also added linux check to allow e2fsck to make sure nothing is corrupted.
-- Starfox
can someone help me, i get an error that cant execute /bin/bash no such file or directory, i installed busybox, what can i do?
Hi,
i 'm an archos user since not so long Thanks to the community I managed to install sde and root my device.
I have been lately searching for a tutorial or guide on how to cook a custom firmware, but I couldn't find such info.
Can someone write one for us newbies of Android and archos?
What I'm looking for is how to create the archos. ext4. update file from. aos and how to install busybox root etc..
thanks
adonix said:
Hi,
i 'm an archos user since not so long Thanks to the community I managed to install sde and root my device.
I have been lately searching for a tutorial or guide on how to cook a custom firmware, but I couldn't find such info.
Can someone write one for us newbies of Android and archos?
What I'm looking for is how to create the archos. ext4. update file from. aos and how to install busybox root etc..
thanks
Click to expand...
Click to collapse
Hi There,
Like most things on XDA, we've already covered it and the search is very much you're friend , However heres some links which sould help you on your way [HOWTO] Unpack and repack stock firmware, works also for gen8 and [HOW TO] Root, Install Busybox and SuperCharge your G9 These guides are on pages 4-5 of this section you might to work on that "searching" technique
Hi trevd and thanks for your reply.
I did find these links before i posted my request.
The first one provides tools for Gen8 and supposedly compatible with Gen9. But as i read through the thread, it seems to be dealing with a squashfs partition and not ext4 like the one we're using. So it confused me.
The second one shows how to install busybox. But how is it possible to do the same thing directly on the mounted ext4 partition?
Thanks
You can also use my update/modify script as base:
http://forum.xda-developers.com/showthread.php?t=1735790&highlight=script
Quallenauge said:
You can also use my update/modify script as base:
http://forum.xda-developers.com/showthread.php?t=1735790&highlight=script
Click to expand...
Click to collapse
Thank you Quallenauge for your help.
i've tried the script, but it's not working properly at step 4. It seems that it's unable to mount the file to the loop. I'm using ubuntu x64. any idea?
Code:
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Thanks
Quallenauge said:
You can also use my update/modify script as base:
http://forum.xda-developers.com/showthread.php?t=1735790&highlight=script
Click to expand...
Click to collapse
Which version of linux did you use? letama's unpackAOS doesn't work on Lubuntu 12.10 even when I install correct version of libcrypto. So I tried Xubuntu 12.04 and your script works fine. Thank you for the script.
stevemp said:
Which version of linux did you use? letama's unpackAOS doesn't work on Lubuntu 12.10 even when I install correct version of libcrypto. So I tried Xubuntu 12.04 and your script works fine. Thank you for the script.
Click to expand...
Click to collapse
I use ubuntu 12.04 x64. Any idea?
root
adonix said:
I use ubuntu 12.04 x64. Any idea?
Click to expand...
Click to collapse
Unpack ExtractAOS.tar.bz2
cd ExtractAOS
copy firmware_archos_it4.aos to dl directory
I use terminal as root.
Type sudo -i in terminal then your password.
Then ./unpackAOS Do step 1 to 5 options, check archos_update_folder to see if firmware unpacked. Make your mods now, do the rest of steps.
1) clean
2) downloadPackages
3) setupBuildDir
4) createExt4Image
5) unpackAOS
6) copyAOSData
7) addSuperuser addBusyBox
8) finish
Thanks for the reply stevemp.
i'm doing the exact same steps but it fails at 4 while trying to mount the ext4 image.
I tried the same steps in OpenSuse and it seems to be working. I'm not sure if everything is getting extracted, but i'll check that.
Since the created update file is 512MB, is there a way to trim the unused space prior to flashing?
Thanks.
change image size
adonix said:
Thanks for the reply stevemp.
i'm doing the exact same steps but it fails at 4 while trying to mount the ext4 image.
I tried the same steps in OpenSuse and it seems to be working. I'm not sure if everything is getting extracted, but i'll check that.
Since the created update file is 512MB, is there a way to trim the unused space prior to flashing?
Thanks.
Click to expand...
Click to collapse
Just change the size in unpackAOS script.
# Image size in MByte
EXT4_IMAGE_SIZE=512
Well I ran into a little struggle when trying to use the complete Linux installer by default so I thought I would post how I got it to work correctly.
When trying to run by default I got errors stating it could not mount the loop device, it is a very simple
Download the bootscript4-3.sh file from
sourceforge.net/projects/linuxonandroid/files/bootscript4-3.sh/downloadSorry not allowed to hyperlink)
and rename it as bootscript.sh
After you have that file ready move it to the directory /data/data/com.zpwebsites.linuxonandroid/files/ and replace the file that is already in there.
You now have a working CompleteLinuxInstaller app enjoy!
Expressionless said:
Well I ran into a little struggle when trying to use the complete Linux installer by default so I thought I would post how I got it to work correctly.
When trying to run by default I got errors stating it could not mount the loop device, it is a very simple
Download the bootscript4-3.sh file from
sourceforge.net/projects/linuxonandroid/files/bootscript4-3.sh/downloadSorry not allowed to hyperlink)
and rename it as bootscript.sh
After you have that file ready move it to the directory /data/data/com.zpwebsites.linuxonandroid/files/ and replace the file that is already in there.
You now have a working CompleteLinuxInstaller app enjoy!
Click to expand...
Click to collapse
What branch are you running? I mean I want to install Ubuntu, but all the installers say it's really buggy, and to use a different branch.
bobbyphoenix said:
What branch are you running? I mean I want to install Ubuntu, but all the installers say it's really buggy, and to use a different branch.
Click to expand...
Click to collapse
I haven't really toyed around with the different packs of Ubuntu, the only one I have used is the Ubuntu 10.10 version by Linux-on-android, it seemed to run okay, but I have not looked into it.
Expressionless said:
Well I ran into a little struggle when trying to use the complete Linux installer by default so I thought I would post how I got it to work correctly.
When trying to run by default I got errors stating it could not mount the loop device, it is a very simple
Download the bootscript4-3.sh file from
sourceforge.net/projects/linuxonandroid/files/bootscript4-3.sh/downloadSorry not allowed to hyperlink)
and rename it as bootscript.sh
After you have that file ready move it to the directory /data/data/com.zpwebsites.linuxonandroid/files/ and replace the file that is already in there.
You now have a working CompleteLinuxInstaller app enjoy!
Click to expand...
Click to collapse
Hi. Thanks for your efforts. Just a couple questions. Do you need to use a kernel that has SELinux set to permissive. Also, can I just take the ubuntu image file I was using on my GN II and bring it over to my GN 3 to use.
mscion said:
Hi. Thanks for your efforts. Just a couple questions. Do you need to use a kernel that has SELinux set to permissive. Also, can I just take the ubuntu image file I was using on my GN II and bring it over to my GN 3 to use.
Click to expand...
Click to collapse
I am using a kernel with SElinux set to permissive, also any arm based Linux distro should theoretically work, I do no believe they are phone specific. I would recommend the sabrekernel.
Expressionless said:
I am using a kernel with SElinux set to permissive, also any arm based Linux distro should theoretically work, I do no believe they are phone specific. I would recommend the sabrekernel.
Click to expand...
Click to collapse
Ok. Great! So basically once I have appropriate kernel, I then run Linux on Android. It will set up its file structure and I then I replace bootscript.sh and I'm good to go.
EDIT. This bootscript file is from Linux on android project. I wonder if it is going under further testing. Doesn't hurt to try, and, of course, report to them as it is an open project!
I present to you instructions on how to get Arch Linux working natively on your shield TV dual booted with your Android rom. This is all thanks to the amazing people in this thread for getting Ubuntu on the shield and would not be possible without them.
http://forum.xda-developers.com/shield-tv/general/ubuntu-utopic-nvidia-shield-tv-t3150352
This install will put arch Linux on a micro SD card, and does not modify your shield at all if you so choose. First download these 2 files.
Archlinux Stage 3 install
http://archlinuxarm.org/os/ArchLinuxARM-aarch64-generic-latest.tar.gz
Kernel (Credits to jagger11 from his thread) You only need nvidia_boot.img
https://drive.google.com/folderview...ZSS1VxUVBJZmFqSXNFYUhpN2lHcklhVzZtX0Z5OENxdU0
To intstall
1. Unlock your shield TV
2. Format your SD card to EXT4
3. Mount the SD card
4. As the root user on your linux distro (not sudo) run this command (From the same directory that you downloaded that file to, and replacing mountpoint to where you mounted the SD to)
bsdtar -xpf ArchLinuxARM-aarch64-generic-latest.tar.gz -C mountpoint
5. Unmount the drive, then run the command "sync". When that finishes, pull the SD card from the computer.
6. Put the SD in the shield
7. Reboot to bootloader (adb reboot fastboot) with your preferred method
8. Boot Linux
To boot it once run this
a) fastboot boot nvidia_boot.img
To save to recovery run this (Reboot android to recovery to boot arch after)
b) fastboot flash recovery nvidia_boot.img
Default users and passwords are
root:root
alarm:alarm
For more information, check this page.
http://archlinuxarm.org/platforms/armv8/generic
Tested Working
*Ethernet
*USB
*TTY Terminals
*Framebuffer (Install X11 as usual and xf86-video-fbdev)
Untested
*WIFI (Should work)
*Bluetooth (Probably doesn't work)
Broken
*3D acceleration (Will work on this in the future)
*You tell me
*Sometimes does not boot after a few working boots (I think it's a problem with my SD, or my android install messing with it. Working that out now, but please report if you have this issue only after it boots fine at least once)
My request to you. I am not a kernel dev any more. I once was, but things have unfortunately changed, and I don't have the time or resources to learn it all again. If anyone wants to develop a kernel for this, please do and I'll add it in the OP. Unless something changes, and Ubuntu kernel from the Utopic thread will work fine here)
I'll format this a bit better later, but hopefully this is a good start. I have some good tips and tricks to add if people are interested in this, and was able to watch quite a lot of my videos in vlc even on framebuffer. Please give me some feedback on what you want to see, and ask any questions. I'll be glad to help!
kdb424 said:
I present to you instructions on how to get Arch Linux working natively on your shield TV dual booted with your Android rom. This is all thanks to the amazing people in this thread for getting Ubuntu on the shield and would not be possible without them.
http://forum.xda-developers.com/shield-tv/general/ubuntu-utopic-nvidia-shield-tv-t3150352
This install will put arch Linux on a micro SD card, and does not modify your shield at all if you so choose. First download these 2 files.
Archlinux Stage 3 install
http://archlinuxarm.org/os/ArchLinuxARM-aarch64-generic-latest.tar.gz
Kernel (Credits to jagger11 from his thread) You only need nvidia_boot.img
https://drive.google.com/folderview...ZSS1VxUVBJZmFqSXNFYUhpN2lHcklhVzZtX0Z5OENxdU0
To intstall
1. Unlock your shield TV
2. Format your SD card to EXT4
3. Mount the SD card
4. As the root user on your linux distro (not sudo) run this command (From the same directory that you downloaded that file to, and replacing mountpoint to where you mounted the SD to)
bsdtar -xpf ArchLinuxARM-aarch64-generic-latest.tar.gz -C mountpoint
5. Unmount the drive, then run the command "sync". When that finishes, pull the SD card from the computer.
6. Put the SD in the shield
7. Reboot to bootloader (adb reboot fastboot) with your preferred method
8. Boot Linux
To boot it once run this
a) fastboot boot nvidia_boot.img
To save to recovery run this (Reboot android to recovery to boot arch after)
b) fastboot flash recovery nvidia_boot.img
Default users and passwords are
root:root
alarm:alarm
For more information, check this page.
http://archlinuxarm.org/platforms/armv8/generic
Tested Working
*Ethernet
*USB
*TTY Terminals
*Framebuffer (Install X11 as usual and xf86-video-fbdev)
Untested
*WIFI (Should work)
*Bluetooth (Probably doesn't work)
Broken
*3D acceleration (Will work on this in the future)
*You tell me
*Sometimes does not boot after a few working boots (I think it's a problem with my SD, or my android install messing with it. Working that out now, but please report if you have this issue only after it boots fine at least once)
My request to you. I am not a kernel dev any more. I once was, but things have unfortunately changed, and I don't have the time or resources to learn it all again. If anyone wants to develop a kernel for this, please do and I'll add it in the OP. Unless something changes, and Ubuntu kernel from the Utopic thread will work fine here)
I'll format this a bit better later, but hopefully this is a good start. I have some good tips and tricks to add if people are interested in this, and was able to watch quite a lot of my videos in vlc even on framebuffer. Please give me some feedback on what you want to see, and ask any questions. I'll be glad to help!
Click to expand...
Click to collapse
Thanks for the new thread. You are correct that the "nvidia_boot.img" from jagger11 can boot to archLinux but the kernel I built can't.
I have always been using Ubuntu with desktop enabled by default. How did you install X11 under archLinux?
yahoo2016 said:
Thanks for the new thread. You are correct that the "nvidia_boot.img" from jagger11 can boot to archLinux but the kernel I built can't.
I have always been using Ubuntu with desktop enabled by default. How did you install X11 under archLinux?
Click to expand...
Click to collapse
Following the standard guide on their wiki.
I installed
xorg-server
xorg-server-utils
xorg-init
xf86-video-fb
And then just the standard startx after setting my xinitrc to the usual. In my case I used awesome WM, though you can use any, and exec that in your .xinitrc file
kdb424 said:
Following the standard guide on their wiki.
I installed
xorg-server
xorg-server-utils
xorg-init
xf86-video-fb
And then just the standard startx after setting my xinitrc to the usual. In my case I used awesome WM, though you can use any, and exec that in your .xinitrc file
Click to expand...
Click to collapse
I have to admit I was spoiled by Ubuntu which installs everything by default. I have to read archLinux wiki and try them tomorrow morning.
yahoo2016 said:
I have to admit I was spoiled by Ubuntu which installs everything by default. I have to read archLinux wiki and try them tomorrow morning.
Click to expand...
Click to collapse
Those packages will do you other than desktop manager, but I have to say, I'm pretty minimalist, and arch is by default, so don' feel too bad. I've just been using arch for the last few years, and was using Gentoo before that, which is all even more manual and source built.
https://wiki.archlinux.org/index.php/Xorg
That page will go through it all. Once you know what desktop manager you want (I recommend XFCE if you don't know what, or LXDE which is even lighter), check the pages out on there for them. It covers haw to do absolutely everything. I honestly use arch linux for the wiki. It's by far the best source of linux information on the net I'd be willing to bet.
kdb424 said:
Those packages will do you other than desktop manager, but I have to say, I'm pretty minimalist, and arch is by default, so don' feel too bad. I've just been using arch for the last few years, and was using Gentoo before that, which is all even more manual and source built.
https://wiki.archlinux.org/index.php/Xorg
That page will go through it all. Once you know what desktop manager you want (I recommend XFCE if you don't know what, or LXDE which is even lighter), check the pages out on there for them. It covers haw to do absolutely everything. I honestly use arch linux for the wiki. It's by far the best source of linux information on the net I'd be willing to bet.
Click to expand...
Click to collapse
What display driver should I install?
The wiki starts with
lspci | grep -e VGA -e 3D
But lspci does not work for shield TV.
yahoo2016 said:
What display driver should I install?
The wiki starts with
lspci | grep -e VGA -e 3D
But lspci does not work for shield TV.
Click to expand...
Click to collapse
xf86-video-fbdev works for me. Since we don't have access to the GPU directly, we are using the framebuffer at the moment.
kdb424 said:
xf86-video-fbdev works for me. Since we don't have access to the GPU directly, we are using the framebuffer at the moment.
Click to expand...
Click to collapse
That confused me since I thought xf86 meant x86 but Shield has Arm CPUs.
yahoo2016 said:
That confused me since I thought xf86 meant x86 but Shield has Arm CPUs.
Click to expand...
Click to collapse
Yeah, it's actually got nothing to do with architecture. Not quite sure why they are named as such. Also, xf86-video-fbdev isn't listed there as it's a last resort kinda thing, but it works well on the shield for the moment. Once I figure out why my system stops booting linux from time to time, I'll work on GPU drivers. Hard to know what broke it if I don't fix that first.
kdb424 said:
Yeah, it's actually got nothing to do with architecture. Not quite sure why they are named as such. Also, xf86-video-fbdev isn't listed there as it's a last resort kinda thing, but it works well on the shield for the moment. Once I figure out why my system stops booting linux from time to time, I'll work on GPU drivers. Hard to know what broke it if I don't fix that first.
Click to expand...
Click to collapse
You may want to have a look at this: https://github.com/NVIDIA/tegra-nouveau-rootfs
Arch Linux is the target rootfs and the Jetson TX1 is supported. Now the questions is how to get a mainline kernel running on shield tv. I guess one issue is the device tree which will not be provided by uboot like on normal arm systems. In the kernel configuration you can define that the device tree is appended to the kernel image (e.g. by "cat Image foster.dtb > newImage"). Maybe this is a solution.
Thanks_Meter said:
You may want to have a look at this: https://github.com/NVIDIA/tegra-nouveau-rootfs
Arch Linux is the target rootfs and the Jetson TX1 is supported. Now the questions is how to get a mainline kernel running on shield tv. I guess one issue is the device tree which will not be provided by uboot like on normal arm systems. In the kernel configuration you can define that the device tree is appended to the kernel image (e.g. by "cat Image foster.dtb > newImage"). Maybe this is a solution.
Click to expand...
Click to collapse
Thanks for the info. I'm going to have the next 2 days off work, so I'll definately get to work. I'm going to need assistance in getting a working kernel as I don't have an x86 machine around currently. Crazy, I know, but I don't. I'll see if I can get the drivers installed if someone works on a kernel. If not, I'll contact some of my linux friends and see what they come up with.
kdb424 said:
Thanks for the info. I'm going to have the next 2 days off work, so I'll definately get to work. I'm going to need assistance in getting a working kernel as I don't have an x86 machine around currently. Crazy, I know, but I don't. I'll see if I can get the drivers installed if someone works on a kernel. If not, I'll contact some of my linux friends and see what they come up with.
Click to expand...
Click to collapse
That link mentioned:
"The first prerequisite is that you must use an up-to-date U-Boot as bootloader"
Jetson TK1 and TX1 uses U-boot, Shield TV however uses fastboot not U-boot and the kernel is not Linux but Android.
I'd really like someone can have u-boot ported to Shield TV as 2nd or 3rd stage boot loader.
Damn! I just found out that this CONFIG_ARM_APPENDED_DTB trick only works with zImage but not with Image as needed for abootimg. Currently I don't have an idea how to get a mainline kernel running on the shield tv. I guess uboot makes no sense since we don't have an uart.
Thanks_Meter said:
Damn! I just found out that this CONFIG_ARM_APPENDED_DTB trick only works with zImage but not with Image as needed for abootimg. Currently I don't have an idea how to get a mainline kernel running on the shield tv. I guess uboot makes no sense since we don't have an uart.
Click to expand...
Click to collapse
u-boot could use netconsole:
http://forum.doozan.com/read.php?3,14,14
---------- Post added at 10:33 PM ---------- Previous post was at 10:28 PM ----------
My kernel can boot to command line archLinux now, I updated the procedure:
http://forum.xda-developers.com/showpost.php?p=64330336&postcount=147
I'll try that kernel when get home with the gui running on framebuffer. Should work.
kdb424 said:
I'll try that kernel when get home with the gui running on framebuffer. Should work.
Click to expand...
Click to collapse
I uploaded my latest kernel tested with command line archLinux:
https://drive.google.com/file/d/0Bz5kaPQJx_AgUklNekxGeWFuNW8/view
yahoo2016 said:
I uploaded my latest kernel tested with command line archLinux:
https://drive.google.com/file/d/0Bz5kaPQJx_AgUklNekxGeWFuNW8/view
Click to expand...
Click to collapse
Any chance you can maybe try to patch in the Nouveau kernel driver from here?
With a kernel running that I can get 3D acceleration work started. Till I get that sorted out I can only guess if my changes are working or not.
I'll also be trying to get the closed source binaries running on this. I have decided to pay a decent sum of money for a VPS to get a compile machine. Hopefully we can get this project rolling.
kdb424 said:
Any chance you can maybe try to patch in the Nouveau kernel driver from here?
With a kernel running that I can get 3D acceleration work started. Till I get that sorted out I can only guess if my changes are working or not.
I'll also be trying to get the closed source binaries running on this. I have decided to pay a decent sum of money for a VPS to get a compile machine. Hopefully we can get this project rolling.
Click to expand...
Click to collapse
I did not expect it'd take me so long just to have gui running for archLinux. As I mentioned before this thread started, I'd like to try Cuda 7.0 on ArchLinux. I main goal is to have Cuda working so I can use Gpgpu of Tegra for image processing and other applications.
A script or procedure for post installation to quickly install gui is what I was interested. To install archlinux rootfs without gui was very simple and I did it the first day when I received my Shield TV to troubleshoot Utopic rootfs. I could read the wiki to have gui working for archLinux, but I have to spend my time on other things, e.g., without hope to have u-boot or multirom working for Shield TV, I have to learn Android kernel (I'm in the process of clone Android kernel source tree).
I'll write a script for you once I get home. Thanks for the input. Any requests for a desktop environment or window manager? If not I'll just pick a light one like lxde.
kdb424 said:
I'll write a script for you once I get home. Thanks for the input. Any requests for a desktop environment or window manager? If not I'll just pick a light one like lxde.
Click to expand...
Click to collapse
Any desktop is fine. I'd like to push Cuda 7.0 from my build PC to archLinux like I did for L4T. Network connection and any desktop are what I need. If it works, we can see performance differences between 32 bits and 64 bits
Thanks.