Tiny Core Linux
Tiny Core Extensions => TCE Bugs => Topic started by: core-user on January 08, 2015, 01:43:53 AM
-
Installed CorePlus 6.0 & have found that there are a few problems with some tcz extensions.
Trying to use mplayer (on demand), I have no sound, (sound is working OK with xmms), also won't enlarge the movie to fill the screen.
Trying to run vlc (on demand), nothing happens when I try running it from the menu or wbar, missing libiconv.so.2 reported when trying to run it from a terminal.
Trying to run viewnior (on demand), nothing happens when I try running it from the menu or wbar, missing libffi.so.5 reported when trying to run it from a terminal.
-
today I tried to install pcmanfm and VLC player . Install worked OK. But could not start both from GUI (wbar) nor from CL.
Other than that 6.0 looks great. Firefox installed quicker then I was used to on previous versions. Youtube video worked right out of the box in Firefox. To get sound I installed almost everything from the repo which started with alsa. (alsa.tcz, alsamixergui.tcz, alsa.conf and alsa modules. The info txt from alsa tells you how to start alsa.
Excellent work. Thank you so much.
Now I have to put the alsa start command into bootlocal.sh - hope that will make the alsa start permanent over reboots.
-
OK -- the gparted extension has been fixed and he new gparted.tcz works. EXCEPT it does not show the content of a partition. To fix that: please install e2fsprogs.tcz. Somebody needs to put that into the dependency list too.
pcmanfm needs the libffi5 extensions. I installed them and pcmanfm works ok now. Dependencies need to be fixed too here.
VLC is not working yet. Here is the error message.:
tc@box:~$ vlc
vlc: error while loading shared libraries: libiconv.so.2: cannot open shared object file: No such file or directory
tc@box:~$
There is no libiconv.so.2 or similar extension in repo. What can we do?
-
Hi> Now I have another problem. Alsamixergui was working before. Now all of the sudden the alsamixer can not be started any more. I am getting the following error message:
alsamixer: function snc_ctl_open failed for default: No such file in directory
Any idea and help?
-
here are the error messages. When i first started alsasound - I had sound.
may be something went wrong after reboot.
Alsamixer works after reboot, but after I try to start alsasound the mixer can not be started any more.
tc@box:~$ sudo /usr/local/etc/init.d/alsasound start
rmmod: can't unload 'snd_hda_codec_realtek': Resource temporarily unavailable
rmmod: can't unload 'snd_hda_codec_generic': Resource temporarily unavailable
rmmod: can't unload 'snd_hda_codec': Resource temporarily unavailable
rmmod: can't unload 'snd_hwdep': Resource temporarily unavailable
rmmod: can't unload 'snd_pcm': Resource temporarily unavailable
rmmod: can't unload 'snd_timer': Resource temporarily unavailable
rmmod: can't unload 'snd': Resource temporarily unavailable
amixer: Mixer attach default error: No such file or directory
Something went wrong, sound was not set up.
tc@box:~
-
There is no libiconv.so.2 or similar extension in repo. What can we do?
Rebuild VLC
-
OK -- the gparted extension has been fixed and he new gparted.tcz works. EXCEPT it does not show the content of a partition. To fix that: please install e2fsprogs.tcz. Somebody needs to put that into the dependency list too.
As per the gparted info file: depending on the file operations desired, can be used with the dosfstools, e2fsprogs, jfsutils, mtools, ntfsprogs, reiserfsprogs and util-linux extensions
-
$ sudo /usr/local/etc/init.d/alsasound start
rmmod: can't unload 'snd_hda_codec_realtek': Resource temporarily unavailable
rmmod: can't unload 'snd_hda_codec_generic': Resource temporarily unavailable
I see these kind of errors when alsa is already set up and "alsasound start" is run again - it could be that you only need to load the alsa extension (without running "alsasound start") and un-mute the mixer for things to work.
Note also that, once you have alsa working, you can save the state with "sudo alsactl store" to avoid having to run "alsasound start" on reboot.
-
[...] To get sound I installed almost everything from the repo which started with alsa. (alsa.tcz, alsamixergui.tcz, alsa.conf and alsa modules. The info txt from alsa tells you how to start alsa. [...]
To get sound working in 6.0, I load only these extensions on-boot:
alsa.tcz
alsa-config.tcz
Then "sudo alsactl store" after un-muting as Juanito sais, plus "filetool.sh -b".
-
the situation on my laptop (dell e7240) is more difficult...
Until recently I was only able to get it to work through the laptop speakers about one boot in ten and to make things worse, hdmi sound is the default: $ lspci
...
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC3226 Analog [ALC3226 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
Eventually I noticed that the sound worked almost every time with corepure64/gnome-session and used the "sudo alsactl store" command to save asound.state.
After restoring asound.state with my usual wm (flwm) and loading the alsa extension, I was able to use alsamixer and F6 to chose device 1, adjust the settings to my liking and save asound.state again.
Now things appear to be working every boot after first restoring asound.state, then loading only the alsa extension (and deps) and without issuing any commands.
With my hardware, to test sound (requires the alsa-config extension): $ speaker-test -Ddefault:1 -c2 -t wav -l1
or, with xmms use the following settings (<ctrl-p>): output plugin: ALSA 1.2.11 out plugin [libALSA.so]
configure:
Audio device: hw:1,0
Mixer card: HDA Intel PCH
Mixer device: PCM
-
thank you so much guys. Sound works. I do not have to start alsasound again after reboot. Just start alsamixer and move the scroll bars.
But VLC still generates the same error messages. I deleted the previous installed VLC and installed the new extension fixed by a member yesterday.
-
There is no libiconv.so.2 or similar extension in repo. What can we do?
Rebuild VLC
Hi: Did you rebuild VLC?
It is still not starting. May it be that it is a general tce-load problem of version 6.0?
-
We've been trying to get rid of libiconv for sometime now - the iconv functions have been provided by glibc since at least tc-5.x if not before.
You can load libiconv.tcz from 5.x until VLC gets recompiled without libiconv dependency.
-
This is likely more of an "Apps" issue than a TCE issue but attempting to download vlc.tcz in tc-6.0 I find that Apps hangs and eventually quits with this error
md5sum: vlc.tcz.md5.txt: No such file or directory
I can however download vlc.tcz, vlc.tcz.dep and vlc.tcz.md5.txt manually
am using Apps to update deps and download missing deps :)
-
libiconv.tcz from http://tinycorelinux.net/5.x/x86/tcz/libiconv.tcz (http://tinycorelinux.net/5.x/x86/tcz/libiconv.tcz) is required to be loaded for vlc to run at present (as of this morning anyhow), even though libiconv.tcz is not listed as a dep. Then vlc runs great
-
thank you coreplayer2 and the other members who helped me. I downloaded the libiconv.tcz from the 5.x repo and copied it in to /tce/optional. I also added it to onboot.lst.
Now VLC works.
My CorePlus 6.0 runs on an 2GB SD card via a SATA to SD card adaptor. It is lightning fast and: VLC, Alsamixer, Firefox 21.0, Leafpad, pcmanfm, openssh, mc, gparted and evince work great now. (Youtube also works great)
Who is going to fix the dependency problems in repo? I do not know how o do it.
-
Tiny Core v6 installs/runs well.
Problems:
-wicd install error:
--Apps reports failed
--terminal output:
---wget: server returned error: HTTP/1.1 404 Not Found
---md5sum: wpa_supplicant-dbus.tcz.mdf.txt: No such file or directory
---Error on wpa_supplicant-dbus.tcz
--according to Apps, wpa_supplicant-dbus is not in the repository
-lxterminal installs but does not run (error loading shared library libffi.so.5 message)
-
Apps also failed when attempting to install OSS (didn't have time to troubleshoot via terminal).
TIA to the Tiny Core community and any specific assistance with these issues.
-
---wget: server returned error: HTTP/1.1 404 Not Found
---md5sum: wpa_supplicant-dbus.tcz.mdf.txt: No such file or directory
Could you try the version of wpa_supplicant-dbus from the 5.x repo and report if it works please?
-lxterminal installs but does not run (error loading shared library libffi.so.5 message)
The libffi5 extension can be used until the mainainer updates the extension
Apps also failed when attempting to install OSS (didn't have time to troubleshoot via terminal).
the oss-modules-KERNEL extensions are waiting on a volunteer to compile them and submit an extension. Did you try with alsa instead?
-
Thanks for your help Juanito.
Regarding the wicd install error, i downloaded and installed wpa_supplicant-dbus from this Tiny Core v5 ftp repository but the wicd install still failed: http://ftp.nluug.nl/os/Linux/distr/tinycorelinux/5.x/x86/tcz
Thanks for your help with lxterminal. The seperate installation of the libffi5 extension allowed lxterminal to open properly, hopefully the maintainer will be able to address this issue for other users. Should i be attempting to contact the maintainer myself or what is the process?
Sorry i wouldn't know how to compile and maintain OSS myself - otherwise i would be happy to help. I wanted to keep my installation as minimal as possible and was hoping to try OSS. If i want to try Alsa, what are the minimum packages that need to be installed?
-
...but the wicd install still failed
What error messages do you get when you issue the command "wicd" from a terminal window?
Should i be attempting to contact the maintainer myself or what is the process?
Please send the maintainer a pm
If i want to try Alsa, what are the minimum packages that need to be installed?
With modern hardware only the alsa extension (and deps) is usually required.
-
Thanks again for your help.
PM was sent to the lxterminal maintainer.
Manually downloading and installing wpa_supplicant-dbus.tcz plus the md5.txt from Tiny Core v5 appears to have worked. I will reboot, test and confirm.
Thanks for the Alsa information, i will attempt to install and also report back the results.
-
Got sound working by installing alsa.tcz and alsa-config.tc - too bad OSS is presently broken.
Am unable to get wicd running on tc-6. For sure issues related to dependency libraries, including:
- wpa_supplicant-dbus (not present in tc-6 repository)
- openssl (believe wrong version in repository for wicd)
Maybe other issues regarding wicd on tc-6, one of them being i'm new to Tiny Core. I probably should have installed tc-5 first, as it's probably much more tested, for my initial learning curve. As i'm presently testing an older netbook, also probably should have installed CorePlus. May start from scratch again to retest wireless.
-
Note that you can use the (much lighter) wifi extension instead of wicd.
-
FWIW, I was able to get a couple of 6.0 extensions I was having problems with to work by manually changing their dep files to match what was in the 6.0 repository (bit of a guess based on names), and then getting those missing dependencies. Wouldn't work of course if what is needed is a recompile...
-
being i'm new to Tiny Core. I probably should have installed tc-5 first, as it's probably much more tested, for my initial learning curve. As i'm presently testing an older netbook, also probably should have installed CorePlus.
I second that, it is quite a different distro to the majority of Linux.
I started out with 5.4 CorePlus before attempting to 'upgrade' to 6.0, which didn't go well for me as a newbie to TC.
So I 'installed' 6.0 CorePlus which works really well, the only problem is that some of the extensions (still) need to be updated.
-
PM was sent to the lxterminal maintainer.
lxterminal updated
-
Thanks all for the help and feedback. Toughed it out with my hacked install, cleaned up packages and onboot.list, learned how to use Apps and had to blacklist some wifi modules. Downloaded the CorePlus package so i could strip it for parts (wifi related extensions)!
Re-installed lxterminal from scratch and everything now works as expected - thanks bmarkus.
Gave up up wicd - too many dependency issues, but did gmail the wicd wpa_supplicant-dbus.tcz maintainer. If no response in a week i will ask the forum if anyone is willing to maintain this package for tc-6.
Ended up installing wifi. Thanks for the tips, very lightweight. Glad to have internet working as the Apps info pages don't work without a connection. Still used to Debian manpages - feel kinda lost working on the system but learning.
Praises and observations (not criticisms) from a new TC user with moderate Linux experience:
- TC is the real deal, not a toy distribution
- TC is quite revolutionary and very refreshing
- TC is how computing should be...lean and mean
- The Into TC pdf manual does not have one mention of wireless
- Section IV of the manual presents several use cases but none are related to setting up a wireless laptop, wouldn't this be a common use case?
- Many wiki pages are outdated, confusing new users trying to figure things out
- New users should use the previous old version first (eg. tc-5 vs 6), as the core system and extensions would have been better tested and maintained
- Searching previous forum posts is very helpful
- The community is very helpful and responsive - i really appreciate that - thanks again
- TC forces you to re-activate your Linux brain (in a good way)
- TC is both simplistic and complex, often at the same time!
- Once you understand how it works, TC really makes you feel in tune with your computer
- Debian minimal install has nothing on Tiny Core
- Puppy Linux has a lot of unnecessary cruft
Thanks again for all the help.
-
As of yesterday - vlc & xine still have a dependancy on libiconv & won't run.