Tiny Core Linux
General TC => General TC Talk => Topic started by: Luix on December 05, 2016, 05:12:24 AM
-
Hello, everyone. Love the distro, love the concept. I'm still taking baby steps in it, but i have a question. I am using it in an old laptop, already configured to my taste (almost), but when i take the USB pen and use it in another PC, it boots like a live distro, ignoring all my modifications. Does it recognize the hardware and saves the user file accordingly?
Sent from my HIGHWAY STAR using Tapatalk
-
Does your USB stick has a "tce" directory ?
How does your boot code look like ?
What boot loader do you use ?
If you're on either x86 or x64 platform
Using the respected "tc-install" / "tc-install64" is recommended
You will find many useful tips in the core book
http://tinycorelinux.net/corebook.pdf (http://tinycorelinux.net/corebook.pdf)
-
Hi
User files are not stored based on hardware.
If the tce directory is not specified via boot code, Core will search for it on available partitions.
Maybe your USB pen wakes up too slowly for this process and/or you have multiple tce dirs Core might find during boot.
Try adding these boot codes to your boot managers config (substitute FOOBAR with your USB pen's partition label).
waitusb=10:LABEL="FOOBAR" tce=LABEL="FOOBAR"/tce
-
It's 32 bit, syslinux, no bootcode and i only have one tce directory. The desktop in which it boots to live is newer than the laptop where I costumized it, but i will try your bootcode to see if in fact the problem is in the slow USB.
Thanks, people
Sent from my HIGHWAY STAR using Tapatalk
-
I've finally tested, retested and it seems to be working fine with your bootcodes. In fact, without the 5 sec wait (10 sec was too long) it randomly booted to base or to tce. With the 5 sec wait and the path defined it boots straight to were i want.
I thought that slow machines didn't applied to USB sticks, but it also seems to be relevant.
-
Also, only by curiosity, has anyone ever build xbmc/Kodi to Tiny? It would kick openelec, fast and with DE...
---> sudo apt-get install \m/ (°-°) \m/
-
Hi Luix, glad you got it figured out.
However, providing sufficient delay has been given using the "waitusb" bootcode, then max number of seconds is irrelevant. The boot process will continue immediately after a USB (waitusb=10) or the specified USB (with UUID, or Label eg; waitusb=10:LABEL="MYUSB") has been found. 10 seconds is never too long, you'll understand if you watch the countdown.
:)
-
Didn't know that, but it makes sense. Thanks, i'll update the bootcode. Now for something completely different, trying to read the book step by step :)
---> sudo apt-get install \m/ (°-°) \m/
-
Here's the list of deps:
Build-Depends: autoconf, automake, autopoint, autotools-dev, cmake, curl,
default-jre, gawk, gperf, libao-dev, libasound2-dev,
libass-dev (>= 0.9.8), libavahi-client-dev, libavahi-common-dev, libbluetooth-dev,
libbluray-dev (>= 0.7.0), libbz2-dev, libcap-dev,
libcdio-dev, libcec-dev, libcurl4-openssl-dev | libcurl4-gnutls-dev | libcurl-dev,
libcwiid-dev, libdbus-1-dev, libegl1-mesa-dev, libfontconfig-dev, libfreetype6-dev,
libfribidi-dev, libgif-dev (>= 4.1.6), libgl1-mesa-dev | libgl-dev, libglu1-mesa-dev | libglu-dev,
libiso9660-dev, libjpeg-dev, libltdl-dev, liblzo2-dev, libmicrohttpd-dev,
libmodplug-dev, libmpcdec-dev, libmysqlclient-dev, libnfs-dev,
libpcre3-dev, libplist-dev, libpng12-dev | libpng-dev, libpulse-dev, librtmp-dev,libsdl2-dev,
libshairplay-dev, libsmbclient-dev, libsqlite3-dev, libssh-dev, libssl-dev, libswscale-dev,
libtag1-dev (>= 1.8), libtinyxml-dev (>= 2.6.2), libtool, libudev-dev,
libusb-dev, libva-dev, libvdpau-dev, libxinerama-dev, libxml2-dev,
libxmu-dev, libxrandr-dev, libxslt1-dev, libxt-dev, libyajl-dev (>=2.0), lsb-release,
nasm [!amd64], python-dev, python-imaging, python-support, swig, unzip, uuid-dev, yasm,
zip, zlib1g-dev
-
That's a lot of deps, lol! Good to know if someone later on tries to build it...
---> sudo apt-get install \m/ (°-°) \m/
-
kodi (xbmc) posted to corepure64 repo
-
I can't hardly wait for Server maintenance to be finished just to try this :)
thanks Juanito
-
Don't say thanks too soon, it's likely to be quite rough ;)
Note that you'll need to update the pcre and taglib extensions.
-
It's a tough extension to put together, I'm sure it'll be awesome. We used to have it I tc-4.x iirc
Sent from my iPhone using Tapatalk
-
No 64bit laptop... :( But nice work!
---> sudo apt-get install \m/ (°-°) \m/
-
The build instructions are here:
http://tinycorelinux.net/7.x/x86_64/tcz/src/kodi/
..if you'd like to try yourself on x86.
-
Thanks, I'll give it a try...
---> sudo apt-get install \m/ (°-°) \m/
-
When loading kodi, there are several references to "lsb_release not found" then proceedes to a blank screen which can not be killed. Not sure if kodi hangs on lsb_release not found or not?
-
Using Xorg-7.7-3d, the intel driver and with locale set, there is a several second pause, but then kodi runs without problems:
$ kodi
sh: lsb_release: not found
sh: lsb_release: not found
sh: lsb_release: not found
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Edit: The above was without any audio configured, if I load alsa/pulseaudio and start dbus, kodi starts almost instantaneously.
-
Hi.
How can I install KODI on Raspberry pi 3 running tiny core?
-
No idea, do not know what KODI is. If not in the repo, you can build it yourself.
-
see:
http://tinycorelinux.net/8.x/x86_64/tcz/src/kodi
..and replace "-mtune=generic' by "-march=armv6zk -mtune=arm1176jzf-s -mfpu=vfp"