WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: [1] 2 3 ... 10
1
TCE Q&A Forum / Re: Oracle VBoxAdditions for TC 5.2
« Last post by beerstein on Today at 03:34:28 AM »
question: do I have to make my own  VBoxAdditions for TC 5.2extension?
2
General TC Talk / help ! someone know how to recover...
« Last post by for_answer on September 21, 2014, 11:41:08 PM »
Days ago I put TinyCore on my usbkey using 'dd' comand, and had a trial of this distro,
now I cannot use this usbkey anymore, and cannot find a way to format it.  gparted gave error messages and stopped.  The usbkey is recognized as sdc and sdc1,  there are two folders in sdc which I cannot remove
them. Please tell me a correct way to overcome this, good guys here !
English is my foreign, sorry for mistakes
3
dCore X86 / Re: Debian Jessie dCore
« Last post by netnomad on September 21, 2014, 09:29:30 PM »
hi jason,

thank you for sharing your plans and concepts.

keep on hacking :)
4
dCore X86 / Re: Debian Jessie dCore
« Last post by Jason W on September 21, 2014, 04:15:18 PM »
Thanks netnomad for testing.  I still see an issue with my own ext2 usb bootable drive and will find a fix.  The sytstemd thing in Jessie has provided a set of challenges that will likely not be seen the next Debian version upgrade.

But I am also of the mind that I would rather make one dCore that is excellent than have several that are in various stages of repair, which is the case of packages between the dCores available.  Debian stable does not upgrade libraries or apps except for bugfixes in its lifecycle, and Ubuntu seems to upgrade more often which can cause breakage.  So a Debian stable dCore as the official dCore is much more doable as there are so many packages and basically one dCore maintainer.  The next testing version of dCore will be available when things settle down in Debian testing, I plan it next time to be more closer to the next Debian release so I can do this kind of bugfixing before there is a public dCore testing release.  The Ubuntu dCores were a test of concept, and it would work with Linux Mint, Kali, etc.  But again, better to support one good implementation than spread development effort across a number of concepts. 

So for right now, "waitusb=5" or similar will do, and I will work on a fix that allows the LABEL to be specified in the waitusb command to maximize performance.
5
dCore X86 / Re: Debian Jessie dCore
« Last post by netnomad on September 21, 2014, 01:30:48 PM »
hi jason,

no, my usbstick and it`s filesystems seems to be flawless,
there are no error messages,
but nevertheless i check it regulary with
sudo e2fsck -pv /dev/sdc2

i just asume that perhaps dcore-jessie could have problems with the shutdown:
that the usbstick is not cleanly unmounted or has problems to be reinitialized and mounted at the next reboot?
... i just try to find reasons for the problem.

by the way the usbstick makes no problems with other cuts of tinycore or other livessystems!
6
dCore X86 / Re: Debian Jessie dCore
« Last post by Jason W on September 21, 2014, 12:44:18 PM »
Does your usb drive have an unclean file system?  Fixing the fs would remove one variable that could certainly cause issue.

What errors do you see?

EDIT:  I am still having LABEL boot issues with ext2 usb, I will look into it.
7
dCore X86 / Re: Debian Jessie dCore
« Last post by netnomad on September 21, 2014, 11:35:02 AM »
hi jason,

sorry, but there are still minor issues, so the last cut is still a bit unstable.

i guess a warm reboot of dcore-jessie could initiate errors,
rebooting from tinycore 4.7.7 to dcore-jessie works better.
a cold boot process seems to be more stable.
there could be a problem with the reboot of unclean-ext3-filesystems, too?
or is it just the problem that a warm reboot causes issues with the init of the usb-bus?

you improved the situation, but some reboots still fail :(
8
TCB Tips & Tricks / ASPM enabled logic changed
« Last post by nick65go on September 21, 2014, 04:17:00 AM »
To automaticaly enable ASPM (Active State Power Management) you need a good BIOS.
My BIOS is bad. Some users could tame it by using a kernel parameter in the boot-loader config line like
acpi_osi="Windows 2006" (the correct string is in assembled DSDT, a ACPI table);
to change the feature that the BIOS exposes to the kernel.

If BIOS is stuborn still, you need to force the ASMP manually using a kernel parameter in the boot-loader config line like pcie_aspm=force

But unfortunate the kernel guys changed the logic of activating ASPM.
1. You still need the pcie_aspm=force, but it just enables (not activate!) it.
2. you activate ASPM yourself, by issuing in a shell:
sudo sh -c "echo powersave > /sys/module/pcie_aspm/parameters/policy"

from my $ dmesg, without issuing the shell command:
Kernel command line: initrd=/boot/rootfs64a.gz,/boot/modules64a.gz tce=sda3 pcie_aspm=force BOOT_IMAGE=/boot/vmlinuz64
PCIe ASPM is forcibly enabled
pci0000:00: ACPI _OSC support notification failed, disabling PCIe ASPM

for me, the poke value in /sys activated ASMP and helped me at least to sleep longer my crazy GPU fan.
9
dCore X86 / Re: Debian Jessie dCore
« Last post by netnomad on September 20, 2014, 11:53:44 PM »
hi jason,

yeah, you solved it :)

thank you for your great work.
10
dCore X86 / Re: Debian Jessie dCore
« Last post by Jason W on September 20, 2014, 06:34:25 PM »
This was a udev issue in Debian Jessie that needed a simple udev fix.  Thank you netnomad, JLS, and any others that tested and reported this issue, for helping to make dCore/dCore-jessie better than it was yesterday.  The fix is also applicable or at least not damaging to dCore Wheezy, also updated in the release_candidates area.
Pages: [1] 2 3 ... 10