Tiny Core Linux
dCore Import Debian Packages to Mountable SCE extensions => dCore X86 => Topic started by: Jason W on November 09, 2013, 09:23:06 PM
-
Team Tinycore is pleased to announce the release of dCore-5.13.11.06. Changes since dCore-5.13.10.22:
- tc-functions: getbootparam to properly match a parameter that is a substring, via Gerald Clark.
- tc-config: Added missing write to /sys/block/zram0/disksize.
- profile: Adjust to auto start X when specific xorg servers are specified.
- loadsce: Clean up spurious messages when used from CLI.
- 90-permission.rules: Added missing rules.
- group: Added Debian groups with dCore specifics.
- .profile: Cosmetic cleanup of root/.profile upon boot.
- etc/skel/.profile: Using check for /usr/bin/Xorg for automatic X starting
- loadsce: Adding /opt to paths linked to system during extension loading.
- loadsce: Adding sudo to the find commands to find files not readable by non-privileged user.
Files can be found at:
http://www.tinycorelinux.net/5.x/x86/release/
-
Getbootparam() is still not working.
result="${CMDLINE##*$1=}"
should be
result="${CMDLINE##* $1=}"
There is a missing space.
-
My bad, I overlooked that file. Reposted corrected dCore.gz and dCore-5.13.11.06.iso.
-
When is the kernel going to be fixed?
http://forum.tinycorelinux.net/index.php/topic,16073.0.html
-
As we use Core's kernel, when Core releases a kernel update we will follow.
-
OK, getbootparam() working now. Thanks.
-
hi jason w,
during the boot i get still the swap-error message and no swap-device is installed:
Unable to find swap-space signature
swap-on: /dev/zram0: Invalid argument
my desktop is not loaded automatically, although i included the boot-parameter desktop=fluxbox in my syslinux.cfg. perhaps my .xsession is not confirm anymore, cause it has many individual configurations from former tinycore-environments...
thank you for your help.
-
The zram fix is another file I overlooked. Reposted with fix. Thanks for reporting!
With the differences in the X environment in dCore as opposed to Core, so starting with a fresh .xinitrc and similar files would be a good starting point.
-
hi jason w,
swap is created fine :-) !
now i used the .xinitrc from /etc/skel and copied it in my home-dir,
but nevertheless fluxbox doesn't start automatically.
usually i'm used to configure a .xsession-file!?
actually i had no luck with both alternatives...
thank you for every hint and help.
-
Are you using a backup of your ~/.profile file?
-
I downloaded the new dCore .gz file and re-imported the desktop sce's. Now when I do a shutdown I get an error message about xserver still running. FWIW I copied over the /etc/skel/.profile to /home/tc/.profile, with no apparent effect.
-
Are you using a backup of your ~/.profile file?
hi jason w,
yeah, you've got it :)
fluxbox starts fine with the .profile, i found in /etc/skel/.
thank you for your help.
-
using the kernel inside the iso the system hangs during loading extensions, booting with base norestore and tryng to loadsce an extension, hags. Also eth0 doesn't exists.
I've attached dmesg.
Using the older kernel I've no problem.
-
What older kernel?
That could be the sync problem. Just let it sit for about 15 minutes and see if it finishes.
-
The kernelthat was inside the previous dCore iso
-
I see what has happened, a testing vmlinuz was packed into the iso unintentionally. Will correct soon.
-
iso should be fixed now and available for download from repo.tinycorelinux.net.
-
Mounted latest ISO (burned to CD) and copied dCore.gz and vmlinuz over to USB. Still getting "waiting for xserver to shutdown" error message when either doing regular shutdown or exiting to prompt.
-
Ok, I see the error when exiting gnome but not fluxbox. I will look around and see what may be causing it.
-
Please post the exact error message, what I see does not exactly amount to an error so much as it is X shutdown messages.
And is this causing any change in system behavior?
-
As far as I can tell there's no change to system behavior. The messages:
Waiting for xserver to shut down error setting MTRR (base = 0xd0000000, size = 0x04000000, type = 1) Invalid argument (22)
Server terminated successfully (0). Closing log file
-
Thane,
Do you have an intel video card on your system, or an nvidia?
My box with nvidia primary and a built in intel video card gives this error, while my box with only an ati card does not. Googling has led me to believe it may be video card related.
Did this happen with earlier dCore releases?
-
Looks like nvidia. AFAIK the messages started with the first final release of dCore; I don't recall seeing it in the rc's.
-
Some letters are missing, look at the screenshot
-
Missing in seamonkey? The l's ?