Tiny Core Linux
Tiny Core Extensions => TCE Talk => Extension requests => Topic started by: Dualityonme on February 14, 2016, 12:05:37 PM
-
;) ;) ;) ;) ;) ;)
-
1: I'm really lazy to start with,I will attempt to overgo laziness later..
This is not likely to encourage others to build sunxi-tools for you :P
$ tce-load -i compiletc git libusb-dev
$ git clone https://github.com/linux-sunxi/sunxi-tools
$ cd sunxi-tools
$ make
$ sudo make install
-
When compiling awusb.c with make it gives an error "No rule to make target 'default' stop ....".
Do i need dkms to build awusb module?
-
I'd guess that you need to prepare the kernel source
Edit: $ tce-load -i compiletc git perl5 bash ncurses-dev bc advcomp
$ tar xf linux-4.2.9-patched.tar.xz
$ cd linux-4.2.9
$ make mrproper
$ cp config-4.2.9-tinycore .config
$ make oldconfig
$ make prepare
$ make modules_prepare
$ gunzip Module.symvers-4.2.9-tinycore.gz
$ cp Module.symvers-4.2.9-tinycore Module.symvers
$ make SUBDIRS=scripts/mod
$ cd /lib/modules/4.2.9-tinycore
$ sudo ln -s /usr/src/linux-4.2.9 build
$ git clone https://github.com/linux-sunxi/sunxi-livesuite.git
$ cd sunxi-livesuite/awusb
$ make
$ gzip awusb.ko
$ advdef -z4 awusb.ko.gz
-
And what about Livesuit.it only gives errors like wrong architecture, and I can't get it's source to compile anywhere! ??? ??? :P
-
What errors did you get when trying to compile it?
-
I used this link as instructions ' http://linux-sunxi.org/LiveSuit (http://linux-sunxi.org/LiveSuit) ' but tiny core doesn't have dims in any of repos,maybe using dCore will help get Livesuite(the ease of flashing to NAND really fast when modifying stock img) working on low hardware,at last I read it has Debian and Ubuntu packages compatibility.
wrong architecture
'Core doesn't supported' or 'unknown architecture i586'
-
What I see is:
$ ./LiveSuit.sh
Starting x86/LiveSuit.
x86/LiveSuit: error while loading shared libraries: libaudio.so.2: cannot open shared object file: No such file or directory
..which is because tinycore does not have a nas extension.
If I make my machine look like an i486, then I get: $ ./LiveSuit.sh
Error: unknown architecture i486
..so this would indicate the minimum hardware for LiveSuit (not tinycore) is i686, exactly what machine are you trying to use?
Edit: As a hack, if you copy libaudio* from the debian package libaudio2 into the filesystem and load the qt-4.x-base extension, LiveSuit will run on tinycore as long as you have at least an i686.
-
What I see is: $ ./LiveSuit.sh
Starting x86/LiveSuit.
x86/LiveSuit: error while loading shared libraries: libaudio.so.2: cannot open shared object file: No such file or directory
..which is because tinycore does not have a nas extension.
If I make my machine look like an i486, then I get: $ ./LiveSuit.sh
Error: unknown architecture i486
..so this would indicate the minimum hardware for LiveSuit (not tinycore) is i686, exactly what machine are you trying to use?
Edit: As a hack, if you copy libaudio* from the debian package libaudio2 into the filesystem and load the qt-4.x-base extension, LiveSuit will run on tinycore as long as you have at least an i686.
`uname -a` gives i586 as output but maybe it's still possible to compile Livesuit on that too ( i use really,not-old-but-very-low-n-cheap,AMD geode-based netbook as main PC.Don't tell me to buy new one!!)
-
The only thing you can compile is the kernel module - the rest is a collection of pre-built binaries.
If you're lucky, only the ./LiveSuit.sh check looks for an i686 - what happens when you try the LiveSuit binary in the x86 folder?
-
The only thing you can compile is the kernel module - the rest is a collection of pre-built binaries.
If you're lucky, only the ./LiveSuit.sh check looks for an i686 - what happens when you try the LiveSuit binary in the x86 folder?
the same,doesn't work!
-
"doesn't work" doesn't make it easy to help you - how doesn't it work? What error messages did you get? Did you load the qt-4.x-base extension?
-
is it possible to remake Livesuit for i486 or even i386 Linux?? >:(
-
i got Livesuit gui working but i need awusb drivers which always fail on compilation. :'( :'(
-
Again, can you give details of what "always fail on compilation" actually means (i.e. the exact error message)?
Did you follow the instructions I gave you several posts ago?
-
Hi Dualityonme
Copy the error from your terminal and paste it into your next post. If you don't know how to copy/paste, see:
http://tinycorelinux.net/faq.html#c_p
Please use code tags when pasting from the terminal. It's the # button above the reply box.
-
i didn't get copy/paste from terminal to browser(doesn't work, any help?
-
Is this on tinycorelinux?
What terminal extension are you using?
What browser extension are you using?
What did you try and did you get any error messages?
Is this related to the title of the thread?
-
Yes, on tc.I'm using aterm, minefiel21 and chromium,no error messages, just copy/paste isolation form aterm to browser.And the last one -
sorry, wrong thread. :P Please, move it to general talk or somewhere else
i replied to Rich.
-
Hi Dualityonme
What I do is hold down the left button while dragging the mouse. Once the text I want to copy is highlighted, release
the left button. Move the mouse pointer to where I want to paste the text. Left click once to place the cursor and center
click to paste.
-
my mouse only have two buttons, no solution?
-
Pressing both buttons at the same time emulates a center button press.
-
Pressing both buttons at the same time emulates a center button press.
I though of using 3.16.6 kernel because 'uname -a' gives it as output.
i got error while compiling awusb according to instructions by Juanito with 'make'
make -C /lib/modules/3.16.6-tinycore/build SUBDIRS=/lib/modules/3.16.6-tinycore/sunxi-livesuite/awusb modules
make[1]: Entering directory '/usr/src/linux-3.16.6'
make[1]: *** No rule to make target 'modules'. Stop.
make[1]: Leaving directory '/usr/src/linux-3.16.6'
Makefile:6: recipe for target 'default' failed
make: *** [default] Error 2
What must be in /usr/src/linux-3.16.6/ ?
-
I explained what to do at the beginning of the thread, just use linux-3.16.6-patched.txz instead of linux-4.2.9-patched.txz