Tiny Core Linux
dCore Import Debian Packages to Mountable SCE extensions => dCore X86 => Topic started by: Jason W on August 23, 2013, 03:33:19 AM
-
The first release candidate of dCore 5.0 is released and ready for testing:
Changes for RC1:
- Separate custom arch specific packages, allow md5 tracking of them with -s secure option with changes to deb2sce, import, debGetDeps
- deb2sce: Bugfix for custom meta packages
- usr/bin/import: Fix bug that did not allow Debian meta packages to be imported.
- import: correct identification of pkgprebuilt from dependency
- loadsce: Check for wbar and update icons.
- debExtract: Fixed chown typo resulting in a root:root owned tce.installed directory.
- debExtract: using tar pipe as cpio was not preserving directory perms.
- deb2sce: Fixed bug of removing already used md5sum files in secure function
- debGetPkgList: Fixed bug of writing md5sum files in secure import mode
Files can be found at:
http://www.tinycorelinux.net/5.x/x86/release_candidates/
-
I redid some of my testing, now with persistent /opt and /tce but non-persistent /home. And no mega-packages.
My extlinux.conf:
LABEL dcore
KERNEL /tce/boot/dcore/vmlinuz
APPEND initrd=/tce/boot/dcore/dCore.gz quiet host=zepto tz=CET-1CEST,M3.5.0,M10.5.0/3 opt=sda6 tce=sda6 psmouse.proto=imps nodhcp
My sceboot.lst (no mega-packages):
wireless-tools
wireless-3.8.10-tinycore
firmware-iwlwifi
wpasupplicant
xorg-intel
wbar
flwm_topside
Xtc
Xprogs
Directly after boot I ran:
import -b libreoffice-gnome
loadsce libreoffice-gnome
Then I looked at my wbar, no libreoffice icon. But in the Application menu libreoffice had appeared. I started libreoffice from the application menu. I found that I still was unable to create new documents from the welcome screen. All buttons/links were greyed out except the ones labeled Open... and Templates... I then took a screenshot. I got the popup saying the screenshot was saved to my home. I checked my home directory, no screenshot found. Running screenshot.sh from prompt gave me the same result and an error: imlib2_grab: not found.
I then ran:
import -b firefox
loadsce firefox
I checked my wbar and no Firefox icon, it was present in the application menu though. By accident I then happened to right click my wbar. Wbar reloaded and the Firefox icon appeared (but still no libreoffice icon).
Now you should be able to reproduce some of my issues.
Regarding the inability to import flwm_topside, the same goes for Xtc and Xprogs.
Regards
Uggla
¤ Firefox wbar icon now appears without right click :)
¤ Libreoffice still has no wbar icon :(
¤ Still unable to create new documents using Libreoffice :(
Wireless is working fine when wireless-tools, wireless-3.8.10-tinycore, firmware-iwlwifi and wpasupplicant is loaded individually at boot but it does not when they are part of a mega-package.
Still not working.
-
As for libreoffice, what is the output of "ls -l /home"? I will check the wbar issue once I import it again.
Did you re-import the wireless stuff, by making a file with a name of your choice, here it will be /home/tc/wireless?
Its contents:
wireless-tools
wireless-3.8.10-tinycore
firmware-iwlwifi
wpasupplicant
And importing it with the command:
import -f /home/tc/wireless
-
I think I see what you are talking about with libreoffice, I will look more into it tonight.
The wbar icon is not there because there is not a TC specific icon path specified in the .desktop file, I believe. There will be some apps that do not have icons there as freedesktop is the standard.
-
Did you re-import the wireless stuff, by making a file with a name of your choice, here it will be /home/tc/wireless?
Its contents:
wireless-tools
wireless-3.8.10-tinycore
firmware-iwlwifi
wpasupplicant
And importing it with the command:
import -f /home/tc/wireless
Yes I did that. During boot I get an error that the iwlwifi firmware can't be found.
-
Does it work if the firmware-iwlwifi package is imported separately and loaded before the other packages in that file list?
-
Does it work if the firmware-iwlwifi package is imported separately and loaded before the other packages in that file list?
Yes, that did work.
Another observation:
I've imported Firefox and Gnash but Firefox doesn't find the Gnash plugin.
-
It's still not possible to import flwm_topside, Xprogs and Xtc.
-
I just imported Xtc, Xprogs, and flwm_topside with no issue.
Load the wireless mega extension you made and do this command if the name of the sce is "wireless":
find /tmp/tcloop/wireless > /home/tc/filelist
Then attach that filelist file with your next post.
Also, what is the output of the "version" command? Just to be sure.
-
FWIW there is no need to import Xtc for the same reason as there is no need to import fltk-1.1.10.
Only the following 4 imports should be needed to get X on x86 dCore.
import -b Xprogs
import -b flwm_topside
import -b tcWbar
import -b xorg-all
-
FWIW there is no need to import Xtc for the same reason as there is no need to import fltk-1.1.10.
Only the following 4 imports should be needed to get X on x86 dCore.
import -b Xprogs
import -b flwm_topside
import -b tcWbar
import -b xorg-all
But Xsetup.sh is importing wbar, not tcWbar. What's the difference between wbar and tcWbar?
-
I just imported Xtc, Xprogs, and flwm_topside with no issue.
I tried again and this time it worked for me too but flwm_topside is not found when doing import flwm, import flwm_topside works fine though.
-
Xsetup.sh should no longer be used as loadsce is being deprecated in favor is a single tool import.
Most of the work on the latest cut was to ensure that the base packages could be import'ed.
Perhaps your issues are related to not using import but instead Xsetup.sh and/or loadsce directly.
I have updated the README-X-Setup.txt
-
Re: import of flwm. I see the issue. For now stay with topside.
-
Xsetup.sh should no longer be used as loadsce is being deprecated in favor is a single tool import.
Most of the work on the latest cut was to ensure that the base packages could be import'ed.
Perhaps your issues are related to not using import but instead Xsetup.sh and/or loadsce directly.
I have updated the README-X-Setup.txt
I'm not using Xsetup.sh. I looked at it earlier (last alpha) and thought that since it was using wbar I should too. So, what is the difference between wbar and tcWbar?
-
On x86 dCore tcWbar incudes the wbar binary. So no need for the extra import.
-
Load the wireless mega extension you made and do this command if the name of the sce is "wireless":
find /tmp/tcloop/wireless > /home/tc/filelist
Then attach that filelist file with your next post.
Also, what is the output of the "version" command? Just to be sure.
Here's the filelist. Version shows 5.0-rc1
-
On x86 dCore tcWbar incudes the wbar binary. So no need for the extra import.
So what is included in tcWbar that isn't in wbar? I've been using dcore with xorg and wbar and not tcWbar, it seems to work fine.
-
(http://i42.tinypic.com/2r3lfua.png)
-
uggla, I see it is simple with the firmware-iwlwifi package, it is not in main but in non-free, so it does not exist as a package and is not imported.
-
beroje, sceupdatecheck will be deprecated as premade packages are going to be imported like the others.
But there is an importupdatecheck that can be imported the will check sce's that were imported with the "import -s" option. It simply tells a user which packages inside an sce have available updates whether they are Debian packages or custom Tinycore ones.
Import a package:
import -s firefox
Then at a later time, check it with:
importupdatecheck firefox
It will tell you of any packages contained in it that have newer versions. The sce does not have to be mounted, it will work either way.
-
(http://i40.tinypic.com/34io2dz.png)
thanks
Gracias
-
beroje, sceupdatecheck will be deprecated as premade packages are going to be imported like the others.
But there is an importupdatecheck that can be imported the will check sce's that were imported with the "import -s" option. It simply tells a user which packages inside an sce have available updates whether they are Debian packages or custom Tinycore ones.
Import a package:
import -s firefox
Then at a later time, check it with:
importupdatecheck firefox
It will tell you of any packages contained in it that have newer versions. The sce does not have to be mounted, it will work either way.
Why isn't the -s option used as default? What is the drawbacks using the -s option?
-
uggla, I see it is simple with the firmware-iwlwifi package, it is not in main but in non-free, so it does not exist as a package and is not imported.
But how am I supposed to download firmware-iwlwifi if it can't be imported?
-
The -s option is used as it causes a list of md5sums to be created that not everyone will use, so for the sake of efficiency it is an option to create it.
As for the firmware, we are in the process of making a prebuilt wireless sce that can be downloaded so folks with wireless only have to download vmlinuz, dCore.gz, and the wireless sce. I hope to get it up shortly.
-
As for the firmware, we are in the process of making a prebuilt wireless sce that can be downloaded so folks with wireless only have to download vmlinuz, dCore.gz, and the wireless sce. I hope to get it up shortly.
I was thinking of having a system with only one (mega-) sce. Together with vmlinuz and dCore.gz it would make the whole system. But now there is going to be wireless.sce too :(
-
I am in the process of making individual firmware packages that can be imported, which along with the wireless stuff can be either made modular/mega via import, or to be downloaded as a single sce for those who want to download one wireless.sce and be ready to go.
Be patient. :-)
The individual packages are there now, I will make the premade wireless sce soon that will have all one needs to connect with wireless when loaded.
-
wireless.sce uploaded. This is intended for those who desire a single file download to get connected on any wireless hardware without having to determine exactly what drivers or packages are needed. It includes wpasupplicant, b43-fwcutter, all available wireless firmware, wireless-tools, and relevant kernel modules. Once connected, one can use import to fetch just the needed packages for one's hardware requirements. Available at the below link:
http://tinycorelinux.net/5.x/x86/sce/wireless.sce
http://tinycorelinux.net/5.x/x86/sce/wireless.sce.md5.txt
The same package can be obtained by import with the below command:
import wireless
-
I've now tried to put everything I need in one mega-sce. Dcore boots up fine with both wireless and xorg working. Some application icons show up in wbar but Applications menu are totally empty. I've included alsa-modules-3.8.10-tinycore and alsa-base but I don't know how to get sound working.
-
alsa-base does not appear to have alsa-utils as a dependency according to it's web page. I use alsa-utils plus alsa-modules-3.8.10-tinycore for sound, with alsa-utils you should have working sound without much if any manual intervention.
What window manager or desktop are you using?
-
flwm_topside
-
I see the flwm_topside issue, the tar.gz package in the importable section is not current with what was in the premade sce area. I will fix and upload it now.
-
flwm_topside fixed and available for import.
-
The screen shot tool still isn't able to actually save.
-
I am heading out the door, but I see that imlib2_grab is missing and apparently is why the screenshot.sh utility does not work. import Xprogs again and the screenshot utility should work.
Thanks for reporting.
-
alsa-base does not appear to have alsa-utils as a dependency according to it's web page. I use alsa-utils plus alsa-modules-3.8.10-tinycore for sound, with alsa-utils you should have working sound without much if any manual intervention.
I have alsa-utils and alsa-modules-3.8.10-tinycore in my mega-sce. I've run alsamixer and my intel sound is identified and all bars are up but still no sound. :(
-
When I import and load gnash separately I get a Wbar icon but when gnash is loaded as part of a mega-sce there is no Wbar icon.
(and as I said before, gnash doesn't work with Firefox)
-
With alsa, are you sure the channels are not muted, which can be toggled with the "m" button?
I will look into the gnash wbar issue.
-
Gnash's /usr/share/applications/gnash.desktop file has the "NoDisplay=true" line, so it is not supposed to show. That line is grepped for in loadsce and apps that have it are not given an icon or menu entry to keep with the intended freedesktop behavior.
-
Gnash's /usr/share/applications/gnash.desktop file has the "NoDisplay=true" line, so it is not supposed to show. That line is grepped for in loadsce and apps that have it are not given an icon or menu entry to keep with the intended freedesktop behavior.
But the icon is added to Wbar when doing.
import gnash
loadsce gnash
It seems like a bug.
-
With alsa, are you sure the channels are not muted, which can be toggled with the "m" button?
I will look into the gnash wbar issue.
But then the alsamixer volume bars should be all the way down shouldn't they? (they are not)
-
In RC2 our premade packages will be given priority over Debian one's when their name is the same. That way we can host flwm, wbar, and others that are custom TC packages but we will not have to change the name to avoid conflict. Right now as I am testing the changes, I can import wbar and the gnash icon does not show. Also, "import flwm" installs our flwm and it's fltk dependency. So the gnash issue should be fixed there.
As for alsa, below is an example of the first three channels being muted while their volume bars are up. The M at the bottom of the bar means mute.
https://docs.google.com/file/d/0B_xwlkY06TgZd2hUNFhybjJpTjA/edit?usp=sharing (https://docs.google.com/file/d/0B_xwlkY06TgZd2hUNFhybjJpTjA/edit?usp=sharing)
-
As for alsa, below is an example of the first three channels being muted while their volume bars are up. The M at the bottom of the bar means mute.
You were right, thanks!
I've found out that the proper gnash browser plugin package is mozilla-plugin-gnash. The reason I didn't load it from the beginning is that it doesn't show up in the list when doing import gnash (I think it would be a good idea if it did). Still havn't got it working though.