Tiny Core Linux
Tiny Core Base => CorePlus => Topic started by: eltone on March 17, 2013, 12:48:39 AM
-
Hi,
TCP 4.7.3 boots fine, but Desktop only displays the center 'CORE' icon.
Nothing at all can be launched, except shutdown, via right mouse click!
Is there any way to recover these essential icons that have always appeared/functioned at the bottom of the screen?
Kind Regards,
eltone
-
It sounds like one or more extensions is missing. What's in /tmp/tcloop ?
No icons at all could indicate missing wbar.tcz (no icon display/dock ) or missing Xprogs.tcz (no icons to display).
Most likely it is that Xprogs is not loading - possibly related to the naming issue with fltk-1.1.10.tcz vs. fltk-1.10.tcz
-
It sounds like one or more extensions is missing. What's in /tmp/tcloop ?
No icons at all could indicate missing wbar.tcz (no icon display/dock ) or missing Xprogs.tcz (no icons to display).
Most likely it is that Xprogs is not loading - possibly related to the naming issue with fltk-1.1.10.tcz vs. fltk-1.10.tcz
Dear Lee,
This is tricky to pursue, since the Desktop is zapped! The only clue why this happened was that I had just installed/ran 'bitstormlite.tcz'. I will use another torrent alternative, after this experience. Any suggestions on a 'bitstormlite' replacement candidate?
How can I discern the contents of /tmp/tcloop, since the Desktop is frozen?
Faithfully,
eltone
-
It sounds like one or more extensions is missing. What's in /tmp/tcloop ?
No icons at all could indicate missing wbar.tcz (no icon display/dock ) or missing Xprogs.tcz (no icons to display).
Most likely it is that Xprogs is not loading - possibly related to the naming issue with fltk-1.1.10.tcz vs. fltk-1.10.tcz
Hey Lee!
I notice now that TCP trapped this error:
CP: WRITE ERROR: NO SPACE LEFT ON DEVICE
UDEVD[75]: FAILED TO CREATE QUEUE FILE:
CAN'T OPEN DISPLAY
*************
I then booted my stable TCP and found that:
/mnt/sdb1/tce/optional
has a LOT of TCZ bloat!
Q: Can I remove this TCZ bloat, inorder to provide the needed space for queue file?
thanks,
eltone
-
Use Apps to mark extensions for deletion.
-
Use Apps to mark extensions for deletion.
Hi gerald_clark,
Q: Since TCP trapped 'CAN'T OPEN DISPLAY' error, how can 'Apps' be of any use?
I can't even launch 'editor' from CLI!
eltone
-
Hi Paulo
Then boot into your stable TCP and remove a large application from /mnt/sdb1/tce/optional, such as a web browser.
Do not remove something that other applications may depend on. Then edit /mnt/sdb1/tce/onboot.lst and remove
that applications name from it. Then try rebooting and see if the error is gone.
-
It sounds like one or more extensions is missing. What's in /tmp/tcloop ?
Lee,
Using my stable TCP, this is the complete contents of /tmp/tcloop:
/tmp/tcloop/xz
/tmp/tcloop/Xvesa
/tmp/tcloop/Xprogs
/tmp/tcloop/Xorg-7.6-lib
/tmp/tcloop/Xlibs
/tmp/tcloop/x264
/tmp/tcloop/wpa_supplicant-dbus
/tmp/tcloop/wireless_tools
/tmp/tcloop/wireless-3.0.21-tinycore
/tmp/tcloop/wicd
/tmp/tcloop/wbar
/tmp/tcloop/vcdimager
/tmp/tcloop/urwid-2.7
/tmp/tcloop/udev-lib
/tmp/tcloop/ttf-bitstream-vera
/tmp/tcloop/totem-pl-parser
/tmp/tcloop/tc-install
/tmp/tcloop/taglib
/tmp/tcloop/syslinux
/tmp/tcloop/squashfs-tools-4.x
/tmp/tcloop/sqlite3
/tmp/tcloop/shared-mime-info
/tmp/tcloop/SDL
/tmp/tcloop/rfkill
/tmp/tcloop/readline
/tmp/tcloop/python
/tmp/tcloop/pygtk-2.7
/tmp/tcloop/pygobject-2.7
/tmp/tcloop/pycairo-2.7
/tmp/tcloop/popt
/tmp/tcloop/pixman
/tmp/tcloop/perl5
/tmp/tcloop/pcre
/tmp/tcloop/pcmanfm
/tmp/tcloop/parted
/tmp/tcloop/pangomm
/tmp/tcloop/pango
/tmp/tcloop/p11-kit
/tmp/tcloop/ossxmix
/tmp/tcloop/OSS-modules-3.0.21-tinycore
/tmp/tcloop/OSS
/tmp/tcloop/ORBit2
/tmp/tcloop/openssl-1.0.0
/tmp/tcloop/nss
/tmp/tcloop/nspr
/tmp/tcloop/nettle
/tmp/tcloop/net-tools
/tmp/tcloop/ncurses-utils
/tmp/tcloop/ncurses-common
/tmp/tcloop/ncurses
/tmp/tcloop/mpfr
/tmp/tcloop/mirrors
/tmp/tcloop/man
/tmp/tcloop/make
/tmp/tcloop/lxde-icon-theme
/tmp/tcloop/linux-headers-3.0.3-tinycore
/tmp/tcloop/linux-headers-3.0.21-tinycore
/tmp/tcloop/libxml2
/tmp/tcloop/libxcb-util
/tmp/tcloop/libxcb
/tmp/tcloop/libwmf
/tmp/tcloop/libvorbis
/tmp/tcloop/libunique
/tmp/tcloop/libtheora
/tmp/tcloop/libtasn1
/tmp/tcloop/libstartup-notification
/tmp/tcloop/libssl-0.9.8
/tmp/tcloop/libssh2
/tmp/tcloop/libsoup-gnome
/tmp/tcloop/libsoup
/tmp/tcloop/libsigc++
/tmp/tcloop/librsvg
/tmp/tcloop/libproxy
/tmp/tcloop/liborc
/tmp/tcloop/liboil
/tmp/tcloop/libogg
/tmp/tcloop/libnotify
/tmp/tcloop/libnl1
/tmp/tcloop/libmpeg2
/tmp/tcloop/libmpc
/tmp/tcloop/libmad
/tmp/tcloop/liblzma
/tmp/tcloop/libltdl
/tmp/tcloop/libiw
/tmp/tcloop/libisofs
/tmp/tcloop/libIDL
/tmp/tcloop/libid3tag
/tmp/tcloop/libiconv
/tmp/tcloop/libgsf
/tmp/tcloop/libgpg-error
/tmp/tcloop/libgnome-keyring
/tmp/tcloop/libglade
/tmp/tcloop/libgcrypt
/tmp/tcloop/libffi
/tmp/tcloop/libexif
/tmp/tcloop/libetpan
/tmp/tcloop/libdvdread
/tmp/tcloop/libdvdnav
/tmp/tcloop/libdca
/tmp/tcloop/libcroco
/tmp/tcloop/libcdio
/tmp/tcloop/libcdaudio
/tmp/tcloop/libcap
/tmp/tcloop/libcanberra
/tmp/tcloop/libburn
/tmp/tcloop/libattr
/tmp/tcloop/libasound
/tmp/tcloop/libarchive
/tmp/tcloop/libao
/tmp/tcloop/liba52
/tmp/tcloop/less
/tmp/tcloop/lame
/tmp/tcloop/iso-codes
/tmp/tcloop/ImageMagick
/tmp/tcloop/hunspell
/tmp/tcloop/hicolor-icon-theme
/tmp/tcloop/gtkmm
/tmp/tcloop/gtk2
/tmp/tcloop/gtk1
/tmp/tcloop/gstreamer
/tmp/tcloop/gst-plugins-ugly
/tmp/tcloop/gst-plugins-good
/tmp/tcloop/gst-plugins-base
/tmp/tcloop/gst-plugins-bad
/tmp/tcloop/gst-ffmpeg
/tmp/tcloop/gsettings-desktop-schemas
/tmp/tcloop/groff
/tmp/tcloop/graphics-libs-1
/tmp/tcloop/gparted
/tmp/tcloop/gobject-introspection
/tmp/tcloop/gnutls
/tmp/tcloop/gmp
/tmp/tcloop/gmime
/tmp/tcloop/glibmm
/tmp/tcloop/glib2
/tmp/tcloop/glib1
/tmp/tcloop/glib-networking
/tmp/tcloop/gimp2
/tmp/tcloop/gftp
/tmp/tcloop/getFlash11
/tmp/tcloop/gegl
/tmp/tcloop/gdk-pixbuf2
/tmp/tcloop/GConf
/tmp/tcloop/gcc_libs
/tmp/tcloop/gcc_base-dev
/tmp/tcloop/gcc-3.3.6
/tmp/tcloop/gcc
/tmp/tcloop/gamin
/tmp/tcloop/fribidi
/tmp/tcloop/fontconfig
/tmp/tcloop/flwm_topside
/tmp/tcloop/fltk-1.1.10
/tmp/tcloop/flash11
/tmp/tcloop/flac
/tmp/tcloop/firmware-openfwwf
/tmp/tcloop/firmware-broadcom
/tmp/tcloop/firefox
/tmp/tcloop/file
/tmp/tcloop/faad
/tmp/tcloop/expat2
/tmp/tcloop/enchant
/tmp/tcloop/eglibc_gconv
/tmp/tcloop/eggdbus
/tmp/tcloop/dvdauthor
/tmp/tcloop/dvd+rwtools
/tmp/tcloop/dosfstools
/tmp/tcloop/djvulibre
/tmp/tcloop/dhcpcd
/tmp/tcloop/dbus-python-2.7
/tmp/tcloop/dbus-glib
/tmp/tcloop/dbus
/tmp/tcloop/curl
/tmp/tcloop/claws-mail
/tmp/tcloop/cdrtools
/tmp/tcloop/cdrkit
/tmp/tcloop/cdrdao
/tmp/tcloop/cairomm
/tmp/tcloop/cairo
/tmp/tcloop/bzip2-lib
/tmp/tcloop/bsddb
/tmp/tcloop/brasero
/tmp/tcloop/binutils
/tmp/tcloop/bash
/tmp/tcloop/babl
/tmp/tcloop/b43-tools
/tmp/tcloop/atkmm
/tmp/tcloop/atk
/tmp/tcloop/acl
*********
I will start by removing firefox, under the guidelines of Rich.
eltone
* I will cross my fingers & toes, in the process*
-
Then boot into your stable TCP and remove a large application from /mnt/sdb1/tce/optional, such as a web browser.
Do not remove something that other applications may depend on. Then edit /mnt/sdb1/tce/onboot.lst and remove
that applications name from it. Then try rebooting and see if the error is gone.
Hey Rich!
Firefox is so stable, I don't want to remove it. GCC compiler is the problem app, so, can these apps be safely removed from /mnt/sdb1/tce/optional/:
1) gcc_libs
2) gcc_base-dev
3) gcc-3.3.6
4) gcc
eltone
-
Well - I see at least Xlibs, Xprogs, Xvesa, fltk-1.1.10, wbar and flwm_topside so I think the base applets should show up. I'd concentrate on the "WRITE ERROR: NO SPACE LEFT ON DEVICE" issue.
* I will cross my fingers & toes, in the process*
I usually end up with my eyes crossed, too. :)
-
Hi eltone
Removing gcc-3.3.6 should be enough to determine if the problem is insufficient free space on the device.
-
I am not clear on what device is out of space. Is it the root file system?
If so, remove some applications from onboot.lst.
-
Hi,
The last app I installed prior to the write error was 'bitstormlite.tcz'. I see it in 'onboot.1st', but there is no listing of it in /tmp/tloop. Is this normal? Also, 'gcc.tcz' is the only gcc app for 'onboot.1st'.
eltone
* onboot.1st:
Xvesa.tcz
Xlibs.tcz
Xprogs.tcz
wbar.tcz
flwm_topside.tcz
wl-modules-3.0.21-tinycore.tcz
iw.tcz
pci-utils.tcz
ndiswrapper.tcz
firmware.tcz
firmware-ipw2100.tcz
firmware-ipw2200.tcz
firmware-libertas.tcz
firmware-openfwwf.tcz
firmware-wimax.tcz
firmware-zd1211.tcz
b43-fwcutter.tcz
tc-install.tcz
ezremaster.tcz
mirrors.tcz
rfkill.tcz
b43-tools.tcz
b43-tools-doc.tcz
firmware-broadcom.tcz
firefox.tcz
wicd.tcz
gparted.tcz
pcmanfm.tcz
man.tcz
mc.tcz
ossxmix.tcz
brasero.tcz
cdrdao.tcz
dvdauthor.tcz
vcdimager.tcz
gst-ffmpeg.tcz
libburn.tcz
libisofs.tcz
getFlash11.tcz
flash11.tcz
testdisk-6.11.3.tcz
librsvg-dev.tcz
gcc.tcz
compiletc.tcz
linux-headers-3.0.21-tinycore.tcz
bitstormlite.tcz
***
-
Hi eltone
Removing gcc-3.3.6 should be enough to determine if the problem is insufficient free space on the device.
Hi Rich,
To be on the safe side, I'll remove gcc, also, since gcc.tcz is listed in 'onboot.1st'
eltone
-
eltone
forgive me if you had other distractions, but you may like to modify your posts and enclose those lists with either a
[quote]
your list
[/quote]
or replace quote with code
-
Hi eltone
The file is called
onboot.lstnot
onboot.1stThat should be a lower case L, not a one.
-
Yes, you ran out of RAM and thus udev and some extensions failed to load. To get the usual GUI you can use the "base" bootcode.
How much RAM does the system have?
-
Also, do you have any swap activated at boot time?
If not, then such might potentially ease the situation.
-
Yes, you ran out of RAM and thus udev and some extensions failed to load. To get the usual GUI you can use the "base" bootcode.
How much RAM does the system have?
Hi curaga,
Can "base" bootcode be a constant, or only after the fact? It would be nice to have an error trap in TCP, so this would never happen! This PC has 1 GB RAM, that was just upgraded.
eltone
-
It means "don't load any extensions", so using it constantly would be pointless ;)
-
Also, do you have any swap activated at boot time?
If not, then such might potentially ease the situation.
Greetings tinypoodle!
I can't say for sure if there is any 'swap' activated at boot time. All I have done for the Linux swap file, is have Gparted create a 256 MB space on the thumb drive.
Q: What is a bare minimum amount of 'swap' and what is the syntax to activate it at boot time?
If this is the root cause, it has got to be nipped in the bud!
thanks,
eltone
-
Unless you have the 'nozswap' boot option, RAM will be used for compressed swap.
All mkswap formatted partitions found will automatically be activated.
Thumb drives make poor swap devices.
-
Unless you have the 'nozswap' boot option, RAM will be used for compressed swap.
All mkswap formatted partitions found will automatically be activated.
Thumb drives make poor swap devices.
Hi gerald_clark,
Up to now, default boot options have been used.
Q: Selecting the fast, compressed swap, in RAM, is accomplished using which boot option?
thanks,
eltone
-
It is enabled by default. You must use the noted option to turn it off.
-
I can't say for sure if there is any 'swap' activated at boot time. All I have done for the Linux swap file, is have Gparted create a 256 MB space on the thumb drive.
This sounds confusing...
gparted could be used to create swap partitions but hardly would get involved to create swap files.
If you search the web, there is a gazillion of tutorials how to create and manage swap space under Linux ;)
Particular to core is that swap partitions get auto scanned for at boot, while a swap file should be named "tc.swp" in combination with boot code:
swapfile{=hda1} Scan or Specify swapfile
Q: What is a bare minimum amount of 'swap' and what is the syntax to activate it at boot time?
The bare minimum depends entirely on needs created by particular usage, you should rather ask yourself what is the bare minimum of extensions to be loaded onboot.
Should you ever want to hibernate, then there will be a minimum of swap space, but even the size for that is usage dependent.
-
I am not clear on what device is out of space. Is it the root file system?
If so, remove some applications from onboot.lst.
Not sure about this, but given the fact that in mount mode extensions would populate rootfs mainly with symlinks, perhaps there could be a possibility such a message would be the result of running out of inodes?