=== TheMuso` is now known as TheMuso
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
[17:18] <mach20x> I am experiencing a problem with my framebuffer, it appears with the desktop GUI for a portion of a second and then disappears leaving only a blinking CPU monitor behind that persists on the display even when I leave the Linux deploy app and traverse the android realm.
[17:19] <ogra_> not sure what the "linux deploy app" is ... ever heard of it
[17:19] <ogra_> *never
=== doko_ is now known as doko
[17:19] <ogra_> but you should probably talk to the people providing that thing
[17:21] <k1l> its a chroot thing
[17:21] <ogra_> k1l, sure, but definitely not an ubuntu thing
[17:23] <mach20x> … hmm, I don't know how good and prompt support is for it. I could really use a bit of knowledge on how framebuffer/x server integrates with my machine via chroot.
[17:24] <k1l> there were some chroot apps which connected with vnc locally to the chroot running linuxes to simulate a desktop linux on the android devices. i tested it once then and it was "rubbish".
[17:24] <mach20x> I have seen forums, and none express this particular problem
[17:25] <ogra_> well, on a native ubuntu install you would just use the xorg fbdev driver which would use /dev/fb0 or some such to get graphics on the screen
[17:25] <ogra_> (unaccelerated)
[17:25] <mach20x> The vnc server its rubbish/laggy from what I hear from everyone. That is why I elected to the framebuffer for my deployment
[17:28] <mach20x> dev/fb0 is the driver I'm using and I am seeing feedback, but something its happening which is distorting it this way.
[17:28] <ogra_> no, /dev/fb0 is the device, not the driver
[17:28] <mach20x> Is not it's * x2
[17:28] <ogra_> the driver would attach to the device
[17:30] <mach20x> Right
[17:32] <mach20x> I'm sorry the path on the Android device is /dev/graphics/fb0
[17:33] <mach20x> The path that you are describing is what you would see in Ubuntu
[17:37] <mach20x> I tried ln -s /dev/graphics/fb0 /dev/fb0 without success
[17:42] <mach20x> Tried this as well cp -af /dev/graphics/fb0 $chroot_dir/dev/fb0 , perhaps its the reason I'm seeing anything at all, I don't know
[17:44] <ogra_> well, whatever you do inside the chroot, it will depend on the permissions set by the host system ...
[17:44] <ogra_> (and copying devices wont work)
[17:46] <mach20x> Ok, I have root permissions available, what would I have to change on the hosting device?
[17:47] <ogra_> dunno
[17:48] <ogra_> but if android restricts access to a group you are not in for example ... you need to have the same group with the same GID insode your chroot
[17:48] <ogra_> (which gets awfully messy between android and ubuntu if you want all permissions right)
[17:50] <mach20x> right, I can imagine that.
[17:53] <mach20x> Though why would it be that I get any signal at all when I try to open Ubuntu, if I'm out their k outside THE GID
[17:54] <mach20x> If I'm outside the GID *
[17:55] <ogra_> dunno, check your logs etc, fix whatever it complains about ... and in the end, talk to the people that created this tool
[17:55] <mach20x> Ok
[17:55] <ogra_> there is really not much that can be done on the ubuntu side if you have a broken tool that created your setup
[18:09] <mach20x> I sent an email, so we'll see what comes of it
[18:11] <mach20x> I know that you are right, but I'm pretty sure I can ssh into the Ubuntu side to interface
[18:12] <mach20x> I still wouldn't know what would need to be done to effectively iron out this issue when I got there
[18:13] <mach20x> How to set up the dependencies and all that
[18:16] <ogra_> well, but is not something we usually do in ubuntu ... we dont bastardize an install on top of some android system ...
[18:39] <mach20x> The only error I'm seeing is “ Stdin: is not a tty ”
[19:02] <mach20x> Do you think this will work if I put it into the custom script option?
[19:03] <mach20x> Ogra ^^
[19:14] <mach20x> http://forum.xda-developers.com/showthread.php?t=1328742
[19:15] <mach20x> Forgot to drop the URL sorry ogra