Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,732,206 Members 43,703 Now Online
XDA Developers Android and Mobile Development Forum

GNU/Linux@N80XX

Tip us?
 
exception13
Old
#111  
Member - OP
Thanks Meter 140
Posts: 76
Join Date: Mar 2008
Location: Kazan
Quote:
Originally Posted by darksabre_x View Post
Both times I did select the reboot to recovery option when shutting down Android instead of just power off. Would that make a difference?
"reboot to recovery" use scratchpad memory for pass some options to bootloader. android recovery may handle this and reset "reboot to recovery" flag in scratchpad memory but plain GNU/Linux can't. try with clean shutdown.
The Following User Says Thank You to exception13 For This Useful Post: [ Click to Expand ]
 
jan rinze
Old
#112  
Junior Member
Thanks Meter 2
Posts: 12
Join Date: Feb 2013
I have managed to boot into linux with the supplied files recovery.img and linux.img.

On my Linux PC i have succesfully compiled the kernel with the patches supplied on page 3.

Are there more recent patches for the kernel of add-on's available? does it have kexec enabled?

The Distro is nice, I will try and see if i can setup Debian on the emmc.

Thanks!!

---------- Post added at 10:58 PM ---------- Previous post was at 10:43 PM ----------

strange:

when i do 'shutdown -h now' the system shutsdown nicely and i can reboot into Android. BUT when i try to boot linux again i get the Android system recovery!!

is it possible that the system resets the recovery image?
 
darksabre_x
Old
#113  
darksabre_x's Avatar
Member
Thanks Meter 25
Posts: 90
Join Date: Nov 2008
Quote:
Originally Posted by jan rinze View Post
when i do 'shutdown -h now' the system shutsdown nicely and i can reboot into Android. BUT when i try to boot linux again i get the Android system recovery!!

is it possible that the system resets the recovery image?
That's one of the issues of staying completely stock. The stock rom does indeed flash a stock recovery back upon boot. It's due to the recovery-from-boot.p in /system (You'll need to be rooted to rename or delete this)



Quote:
Originally Posted by exception13 View Post
try with clean shutdown.
You were right. I totally forgot about the reboot to recovery flag. After using dd to flash and then powering down the proper way, I now have access to both ArchLinux and my Android rom.
 
exception13
Old
#114  
Member - OP
Thanks Meter 140
Posts: 76
Join Date: Mar 2008
Location: Kazan
i create http://code.google.com/p/opensgn. current in this repo my linux kernel for n8000 and some stuff
The Following 7 Users Say Thank You to exception13 For This Useful Post: [ Click to Expand ]
 
malak2
Old
#115  
Junior Member
Thanks Meter 0
Posts: 5
Join Date: Feb 2013
thanks exception13

please could you post some instructions to get the mali drivers and hardware 3d acceleration working ?
 
jan rinze
Old
#116  
Junior Member
Thanks Meter 2
Posts: 12
Join Date: Feb 2013
CC drivers/misc/tzic.o
/tmp/cccpbEfZ.s: Assembler messages:
/tmp/cccpbEfZ.s:56: Error: unknown pseudo-op: `.arch_extension'
/tmp/cccpbEfZ.s:182: Error: unknown pseudo-op: `.arch_extension'
/tmp/cccpbEfZ.s:192: Error: unknown pseudo-op: `.arch_extension'
make[2]: *** [drivers/misc/tzic.o] Error 1
make[1]: *** [drivers/misc] Error 2
make: *** [drivers] Error 2

do we really need the Linux Mobicore support configured in the kernel?
 
Kondra007
Old
#117  
Kondra007's Avatar
Senior Member
Thanks Meter 65
Posts: 236
Join Date: Aug 2012
Location: Moscow
Quote:
Originally Posted by exception13 View Post
i create http://code.google.com/p/opensgn. current in this repo my linux kernel for n8000 and some stuff
Are you going to make an standalone app for installing ?
I'm stuck a little bit and didn't manage to install, don't understand how to implement patches.
Could you post your instruction in Russian ?
Device #1: Samsung Galaxy SII i9100
Device #2: Samsung Galaxy SIV i9505 - SlimKat 6.2
 
exception13
Old
#118  
Member - OP
Thanks Meter 140
Posts: 76
Join Date: Mar 2008
Location: Kazan
Quote:
Originally Posted by jan rinze View Post
CC drivers/misc/tzic.o
/tmp/cccpbEfZ.s: Assembler messages:
/tmp/cccpbEfZ.s:56: Error: unknown pseudo-op: `.arch_extension'
/tmp/cccpbEfZ.s:182: Error: unknown pseudo-op: `.arch_extension'
/tmp/cccpbEfZ.s:192: Error: unknown pseudo-op: `.arch_extension'
make[2]: *** [drivers/misc/tzic.o] Error 1
make[1]: *** [drivers/misc] Error 2
make: *** [drivers] Error 2

do we really need the Linux Mobicore support configured in the kernel?
which version of gcc and binutils?
The Following User Says Thank You to exception13 For This Useful Post: [ Click to Expand ]
 
jan rinze
Old
#119  
Junior Member
Thanks Meter 2
Posts: 12
Join Date: Feb 2013
Quote:
Originally Posted by exception13 View Post
which version of gcc and binutils?
I have tried versions 4.4 , 4.5 , 4.6 and 4.7. all of them struggle with the code at various places.
I have tried to compile on the Panda board natively and on my Debian PC with a cross compiler.

Which version of gcc and binutils do you use?

---------- Post added at 10:56 AM ---------- Previous post was at 10:32 AM ----------

Quote:
Originally Posted by jan rinze View Post
I have tried versions 4.4 , 4.5 , 4.6 and 4.7. all of them struggle with the code at various places.
I have tried to compile on the Panda board natively and on my Debian PC with a cross compiler.

Which version of gcc and binutils do you use?
Also i get these kind of errors which seem like the code is either incomplete or poorly written.

CC drivers/media/video/exynos/fimc-lite/fimc-lite-reg.o
In file included from drivers/media/video/exynos/fimc-lite/fimc-lite-reg.c:16:0:
drivers/media/video/exynos/fimc-lite/fimc-lite-reg.c: In function ‘flite_hw_set_source_format’:
drivers/media/video/exynos/fimc-lite/fimc-lite-core.h:298:32: error: inlining failed in call to always_inline ‘find_flite_format’: function body not available
drivers/media/video/exynos/fimc-lite/fimc-lite-reg.c:103:26: error: called from here
make[5]: *** [drivers/media/video/exynos/fimc-lite/fimc-lite-reg.o] Error 1
make[4]: *** [drivers/media/video/exynos/fimc-lite] Error 2
make[3]: *** [drivers/media/video/exynos] Error 2
make[2]: *** [drivers/media/video] Error 2
make[1]: *** [drivers/media] Error 2
make: *** [drivers] Error 2
 
jan rinze
Old
(Last edited by jan rinze; 24th February 2013 at 12:39 PM.)
#120  
Junior Member
Thanks Meter 2
Posts: 12
Join Date: Feb 2013
On a side note, the provided linux.img and recovery.img seems to crash and after boot hangs with a fsck error.
when trying to fsck manually it crashes again and hangs.

Does the kernel have overclocking or other stuff enabled? it seems pretty unstable.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes