Tiny Core Linux

Tiny Core Base => TCB News => Alpha Releases => Topic started by: roberts on May 08, 2010, 10:53:23 PM

Title: Tiny Core 3.0 Alpha 1 Testing
Post by: roberts on May 08, 2010, 10:53:23 PM
Team Tiny Core is pleased to announce Tiny Core 3.0 Alpha1 is available for public testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates/tinycore_3.0alpha1.iso

This is an alpha level cut. If you decide to help test, then please test carefully. We don't want anyone to lose data.

Since this is an alpha cut, although the team has 5 preview cuts, we ask that only experienced users test. This cut is not for general use. The features in any alpha are not fixed and may change before a public release candidate is available.

We appreciate testing and feedback.

Download the new iso, and test features and extensions via the desktop appbrowser.
If you use distribution files note that you need both a new bzImage and tinycore.gz.

Do not mix Tiny Core 2.x with Tiny Core 3.x. They have different modules and major library changes, as well as all extensions now only support freedesktop specs.

Changelog for 3.0 alpha1:
* kernel update to 2.6.33.3 ( a upx'ed version is also available in the distribution file area ).
* 64-bit kernel available in distribtion files area.
* compressed swap in ram -> able to run more and longer, less crashes due to out of ram
* tmpfs root always -> no longer possible to exhaust ram in an "embed" boot via files
* improved virtualization support
* ext4 support in base/base tools
* delta extension updates as the default using zsync.
* glibc updated to 2.11.1 and recompiled against 2.6.33 kernel headers
* gcc updated to 4.4.3, recompiled against 2.6.33 kernel headers and cloog, ppl, mpfr, gmp
* e2fsprogs base libs/apps updated to 1.41.11
* kernel-agnostic dep files
* Updated many core files to support new 3.x repository.
* Updated search.sh, provides.sh, tc-config, tce-fetch, tce-setup, tce-load,
* Updated desktop.sh, startx, flwm, and wbar dropped jwm/wbar spec support.

Note:
Using 2.x type extensions will not work for 3.0 as no menu and no icons will appear for non-freedesktop extensions.. A script was run against the 3.x repository to strip out all jwm/wbar (/usr/local/tce.menu and /usr/local/tce.icons). 3.0 uses only freedesktop specs. The script auto created freedesktop items based on prior jwm/wbar specs.

Special Note:
This is alpha software. This is the first public access. Expect bugs. Not recommended for general use.

Alpha testing is for experienced Community Members to help test a totally new build of Tiny Core and help in creating needed updated modules and extensions.

Much work has been done by each Tiny Core Team member to create 3.0. Now is it time for the community to begin testing.

Title: Re: Tiny Core 3.0 Alpha Testing
Post by: jur on May 09, 2010, 12:09:53 AM
Posting from tc 3.0 chromium - congratulations roberts and the tc team!

[edit]Where should we post bugs and such?
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: bmarkus on May 09, 2010, 01:45:55 AM
As far as I remember it was discussed that 256 limit for max_loops will go away and there can be more loops used. What is the case?
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: curaga on May 09, 2010, 01:56:42 AM
We have unlimited loops now, but the userspace is not yet up to it. Waiting for a new major busybox version.
Until then, the limit is 256, without anything specified on the command line (remove any max_loop limit for 3.x)
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: bmarkus on May 09, 2010, 05:18:36 AM
It is not TC 3.0 bug, but a wrong repo conversion. In the 3.x repository the original .desktop files are overwritten and replaced with a .desktop file created from old TC definitions.

For example original filezilla.desktop is:

Quote
[Desktop Entry]
Name=FileZilla
GenericName=FTP client
GenericName[de]=FTP-Client
GenericName[fr]=Client FTP
Comment=Download and upload files via FTP, FTPS and SFTP
Comment[de]=Dateien ĂĽber FTP, FTPS und SFTP ĂĽbertragen
Comment[fr]=Transférer des fichiers via FTP, FTPS et SFTP
Exec=filezilla
Terminal=false
Type=Application
Categories=Network;FileTransfer;
Version=1.0
Icon=filezilla
X-FullPathIcon=/usr/local/share/pixmaps/filezilla.png

Replaced with:

Quote
[Desktop Entry]
Type=Application
Name=FileZilla
Exec=/usr/local/bin/filezilla
Icon=filezilla
X-FullPathIcon=/usr/local/share/pixmaps/filezilla.png
Categories=Utility

You see there are fields deleted, category changed to the common, etc.

Please fix the 3.x repo and do not overwrite existing .desktop files.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Jason W on May 09, 2010, 06:00:19 AM
If upstream .desktop files were not overwritten, then the tc menu entries and exec commands that users created would have been lost, as well as no multiple menu entries.  I chose to uphold the custom tc specific menu entry names and exec commands at the expense of upstream .desktop entries.  As well as overwriting the Icon field with the universally compatible Icon=iconI rather than not overwriting upstream.

If I had left existing .desktop files alone, then there would be complaints that I did not respect the user's custom menu entries and exec commands.  Had to make a choice. 

Title: Re: Tiny Core 3.0 Alpha Testing
Post by: bmarkus on May 09, 2010, 06:12:06 AM
If upstream .desktop files were not overwritten, then the tc menu entries and exec commands that users created would have been lost, as well as no multiple menu entries.  I chose to uphold the custom tc specific menu entry names and exec commands at the expense of upstream .desktop entries.  As well as overwriting the Icon field with the universally compatible Icon=iconI rather than not overwriting upstream.

If I had left existing .desktop files alone, then there would be complaints that I did not respect the user's custom menu entries and exec commands.  Had to make a choice.  


Jason,

you can't destroy original .desktop files. Removing original category makes it useless for the desktop menu system. Removal of localized comments, names, etc. will cause problems using a localised TC.

If it was working fine in 2.11 why to demage it in 3.x? If it is needed not just to add a TC specific field but change the basic fields itself it means something wrong in 3.x !

If you intend to keep 3.x repo as it is now, you are killing LXDE and Xfce4.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: meo on May 09, 2010, 08:52:50 AM
Hi Team TinyCore!

Very good work! I was suspecting that something like this was going to happen and fortunately it did. I have TinyCore 3.0 Alfa 1 in a frugal install and haven't had a problem so far. I'm converted to flwm so the issues mentioned above haven't caused problems to me. Again, very good work!!!

Have fun improving TinyCore,
meo
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: florian on May 09, 2010, 10:18:06 AM
trying out TC3.0 alpha with bzImage64... will the also be an upxed bzImage64 ?
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: gerald_clark on May 09, 2010, 11:16:32 AM
Tested "Net Boot" on Laptop, VIA C3, and Vortex 86.
Looks good.  No problems encountered so far.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: curaga on May 09, 2010, 11:21:16 AM
upx doesn't support 64-bit kernels currently. Please wait a bit on the 64-bit builds; running the 64-bit kernel on the 32-bit build lacks the modules, among them loop support ;)
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: meo on May 09, 2010, 11:54:26 AM
Hi again!

Just a little thing. The link to TC 3.0 alpha 1 is missing the "3.0" and therefore it isn't found just by clicking on the link in Roberts initial announcement.

Have fun,
meo
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: roberts on May 09, 2010, 12:01:12 PM
Fixed! Thanks.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: meo on May 09, 2010, 12:13:40 PM
Hi!

Forgot a suggestion (Sweden is playing hockey right now so I might be a little distracted). I changed the colour of the title bar to medium grey instead of light blue and I think it looks better but it's just an aesthetical thing.

Have fun and keep up the good work,
meo

P.S. Nice new logo!!! D.S.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Jason W on May 09, 2010, 12:16:56 PM
bmarkus-
 
3.x does not utilize tce.menu and tce.icon, that is why a conversion was done.  I didn't have time to do it manually, and the tc2freedesk utility in 2.x base was used.  If I left existing .desktop files alone, then there would have been extensions that did not work with simple WMs and other issues like multiple menu entries.  

The 3.x repo, like the base, is in alpha and is a starting point, not a destination.  If there are any extensions that do not have satisfactory .desktop files they can be mentioned in the "freedesktop standard for icons and desktop files" thread and I will copy over the 2.x desktop files with manual conversion if needed.  All you will have to do is mention the name and I will do the work.  I can't possibly do more than that.  

But, as no one knows more what the extension maker wants more than him, the extension maker converting his desktop files would be the most likely to assure his satisfaction.  That would have had to happen anyway if I did not do a repo conversion.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: curaga on May 09, 2010, 12:29:26 PM
Announcing the 64-bit build of 3.0 alpha 1.

tinycore64.gz is now available in distribution_files. The only difference to the main gz is that it has the 64-bit modules instead of the 32-bit ones.

Notes:
- Xvesa does not like to run on 64. Use Xorg or text mode. For reasoning see http://en.wikipedia.org/wiki/Virtual_8086_mode
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Jason W on May 09, 2010, 01:09:31 PM
For the time being, I have had more than 255 loop mounts by using a command like below to create them:

 
# for I in `seq 255 700`; do mknod /dev/loop"$I" b 7 "$I"; done

Of course, they won't be there on reboot but that can help temporarily create loop devices.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: bigpcman on May 09, 2010, 01:10:06 PM
Good work on tc3.0 team tc.

Currently testing 3.0alpha1 on qemu with kqemu accelerator. Initial installation running fine nothing to report so far.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Sandras on May 09, 2010, 01:27:32 PM
I know it's a minor thing, but when you first boot up the wallpaper i gray, but in /usr/bin/wallpaper the default background color is still #112949, as in the older versions. I think it would be nice if /usr/bin/wallpaper had the default set to #666666 like the background color right after booting into the system.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Arslan S. on May 09, 2010, 03:30:13 PM
testing 3.0alpha, no luck getting alsa to work :(

and desktop entries causes trouble for gnome, for example nautilus (file manager of gnome) does not know how to open a text file :) this is determined by missing "MimeType" section in desktop entries
http://farm2.static.flickr.com/1303/4592937309_990490f2a2_o.png (http://farm2.static.flickr.com/1303/4592937309_990490f2a2_o.png)


Title: Re: Tiny Core 3.0 Alpha Testing
Post by: jur on May 09, 2010, 03:37:20 PM
1) I have not been able to get Xorg going. When installing graphics-2.6.33.3-tinycore.tcz, the screen goes blank and the external monitor switches off. Ctrl-alt-bksp still works, and the text screen seems to have been switched to a higher resolution.

Mounting Xorg despite this, makes the PC freeze requiring a hard reset.

2) My netbook only shows the power button and the sleep button after installing acpid and accompanying files. None of the other function keys are responding.

3) The sound card works but the amixer entries shown are different from before. Not sure if this is a problem.

The basics on the netbook are working including wireless.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Jason W on May 09, 2010, 04:00:25 PM
What I will do is for extensions that already had a desktop file in 2.x, I will simply remove the tce.menu and tce.icon directories and copy over the extension with the Icon=icon thing.  Then extension makers can add back multiple menus or other missing pieces in time.  Perhaps that would provide a more agreeable starting point.

Title: Re: Tiny Core 3.0 Alpha Testing
Post by: meo on May 09, 2010, 04:21:28 PM
Hi!

Just saw someone that didn't get alsa to work. It works just fine for me.

Have fun,
meo
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: bmarkus on May 09, 2010, 04:22:48 PM
1) I have not been able to get Xorg going. When installing graphics-2.6.33.3-tinycore.tcz, the screen goes blank and the external monitor switches off. Ctrl-alt-bksp still works, and the text screen seems to have been switched to a higher resolution.

Mounting Xorg despite this, makes the PC freeze requiring a hard reset.


It works fin on my desktop PC with an old nVIDIA card.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: gwalther on May 09, 2010, 04:43:57 PM
Working surprisingly well on my very old, hardware limited thinkpad 760c (p90..64mb memory)
I use linld097 to boot tc out of dos...no problems...great job....tc team

Note this is the same laptop that  had problems with kernel panics booting from tc2.0...thru .2.8
Title: wireless_ tools.tcz...v3....dep
Post by: gwalther on May 09, 2010, 06:37:56 PM
wireless_tools.tcz for tcV3..lists wireless-KERNEL.tcz as a dependency..
I don't think this is correct...no such extension
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: ^thehatsrule^ on May 09, 2010, 07:14:51 PM
wireless_tools.tcz for tcV3..lists wireless-KERNEL.tcz as a dependency..
I don't think this is correct...no such extension
That is fine (new feature).  Is there an actual problem with it?
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Juanito on May 09, 2010, 08:27:55 PM
When you use the appbrowser or cli to download the extension, it will download either wireless-2.6.33.3-tinycore.tcz or wireless-2.6.33.3-tinycore64.tcz and the local copy of the dep file will also be modified accordingly.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Juanito on May 09, 2010, 08:31:01 PM
Note this is the same laptop that  had problems with kernel panics booting from tc2.0...thru .2.8

Once the problem in tc2.x was tracked down and corrected, the tc3.x glibc was built in the same way.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Juanito on May 09, 2010, 08:38:38 PM
1) I have not been able to get Xorg going. When installing graphics-2.6.33.3-tinycore.tcz, the screen goes blank and the external monitor switches off. Ctrl-alt-bksp still works, and the text screen seems to have been switched to a higher resolution.

Mounting Xorg despite this, makes the PC freeze requiring a hard reset.

I saw the same thing using the i915 module due to it working in KMS mode rather than UMS mode (dixit Curaga), adding "options i915 modeset=0" to /etc/modprobe.conf fixes this.

I can get the i915 module to work without the above by removing "vga=xxx" from the boot codes, but since this mode of operation clashes with both Xvesa and Xorg-7.4, things will be messed up again once you drop out of x.

Quote
2) My netbook only shows the power button and the sleep button after installing acpid and accompanying files. None of the other function keys are responding.

It might be worth looking at "dmesg | grep ACPI" to see which keys are recognised on boot?
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Juanito on May 09, 2010, 08:40:48 PM
testing 3.0alpha, no luck getting alsa to work :(

..works for me using the alsasound init.d - significantly faster at finding the drivers than tc2.x

I'm working on pulseaudio for tc3.x, but it still needs alsa  :(
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: roberts on May 09, 2010, 10:36:29 PM
I know it's a minor thing, but when you first boot up the wallpaper i gray, but in /usr/bin/wallpaper the default background color is still #112949, as in the older versions. I think it would be nice if /usr/bin/wallpaper had the default set to #666666 like the background color right after booting into the system.

Got it. Thanks.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Arslan S. on May 09, 2010, 11:06:17 PM
testing 3.0alpha, no luck getting alsa to work :(

..works for me using the alsasound init.d - significantly faster at finding the drivers than tc2.x


now got it to work, speakers were off by default  ???
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: curaga on May 10, 2010, 02:38:41 AM
Short: Intel graphics users wanting Xorg, you'll need to change the default to UMS mode for Xorg 7.4. 7.5 will support KMS.

Long:

What you're seeing is Intel's new graphics stack.
They only support KMS now (in the Xorg driver, the kernel driver still has the UMS mode for backwards compatibility); if you wish to use UMS, add "options i915 modeset=0" to /etc/modprobe.conf before loading the extension/module.

As you've seen, the KMS stack conflicts with both the vesa framebuffer and the vesa driver (both tinyX and Xorg), because it sets the resolution itself. It gives less flicker, and the optimal resolution from the start (full-res console).

The module in KMS mode should be loaded in pure text mode; inside X or with a framebuffer it's likely to crash and burn.


So far Intel is the only one going this far; radeon and nouveau also support KMS, but theirs defaults off.

The intel driver in Xorg 7.4 doesn't support KMS IIRC, so to run with it turn modesetting off.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: curaga on May 10, 2010, 03:18:04 AM
Quote
3) The sound card works but the amixer entries shown are different from before. Not sure if this is a problem.

Blame the alsa devs, this happens just about every new kernel version.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: bmarkus on May 10, 2010, 03:39:19 AM
Is there any benefit to recompile an extension in 3.0 which otherwise works perfectly from 2.x?
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: curaga on May 10, 2010, 03:46:51 AM
Possible speed gains and size losses, nothing guaranteed though.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Juanito on May 10, 2010, 03:50:53 AM
..and I guess also the extension could make use of additional functionality in the updated glibc and/or kernel.

I did notice some significant size differences in some cases - perhaps as a result of cloog, etc
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: yoshi314 on May 10, 2010, 03:56:47 AM
Short: Intel graphics users wanting Xorg, you'll need to change the default to UMS mode for Xorg 7.4. 7.5 will support KMS.

Long:

What you're seeing is Intel's new graphics stack.
They only support KMS now (in the Xorg driver, the kernel driver still has the UMS mode for backwards compatibility); if you wish to use UMS, add "options i915 modeset=0" to /etc/modprobe.conf before loading the extension/module.

As you've seen, the KMS stack conflicts with both the vesa framebuffer and the vesa driver (both tinyX and Xorg), because it sets the resolution itself. It gives less flicker, and the optimal resolution from the start (full-res console).

The module in KMS mode should be loaded in pure text mode; inside X or with a framebuffer it's likely to crash and burn.


So far Intel is the only one going this far; radeon and nouveau also support KMS, but theirs defaults off.

The intel driver in Xorg 7.4 doesn't support KMS IIRC, so to run with it turn modesetting off.
i think ati already does KMS by default.

worth noting - if your display gives corrupt EDID (old [worn down] CRTs tend to do it), you'd better steer clear from ati KMS. it can lockup your system, display garbage and lockup your system, or give you a white screen of death and lockup your system ;) (all of this on radeon module init, and it's pretty random).

there is work going into fixing such lockups, but it's still not commited nor finished.

recently a safe bet was to use "nomodeset" parameter which would disable modesetting on any driver, but it seems it might not work on all KMS aware drivers anymore.

Title: Re: Tiny Core 3.0 Alpha Testing
Post by: curaga on May 10, 2010, 03:59:13 AM
..and I guess also the extension could make use of additional functionality in the updated glibc and/or kernel.
Indeed, for example an updated Qemu would now take advantage of KSM. Not high on my todo list though, the userbase running a TC host with hundreds of similar VMs in KVM is quite small ;)

@yoshi314: it wasn't enabled by default, I left it that way. Ati users will need to enable it explicitly, via doing the same but with 1 of course.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: yoshi314 on May 10, 2010, 04:01:19 AM
one thing that might be important - ati driver now requires a small piece of firmware for accelerated operation.
one for KMS (all cards) , second for Xorg (some cards).

in case of my x1300 card, i need /lib/firmware/radeon/R520_cp.bin or KMS might fail to start.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Juanito on May 10, 2010, 04:16:22 AM
I foresee all kinds of fun coming with Xorg-7.5 testing  :)
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: bmarkus on May 10, 2010, 04:33:00 AM
Possible speed gains and size losses, nothing guaranteed though.

OK, I will make some tries and see result :)
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: jur on May 10, 2010, 05:36:21 AM
Short: Intel graphics users wanting Xorg, you'll need to change the default to UMS mode for Xorg 7.4. 7.5 will support KMS.

Long:

What you're seeing is Intel's new graphics stack.
They only support KMS now (in the Xorg driver, the kernel driver still has the UMS mode for backwards compatibility); if you wish to use UMS, add "options i915 modeset=0" to /etc/modprobe.conf before loading the extension/module.

As you've seen, the KMS stack conflicts with both the vesa framebuffer and the vesa driver (both tinyX and Xorg), because it sets the resolution itself. It gives less flicker, and the optimal resolution from the start (full-res console).

The module in KMS mode should be loaded in pure text mode; inside X or with a framebuffer it's likely to crash and burn.


So far Intel is the only one going this far; radeon and nouveau also support KMS, but theirs defaults off.

The intel driver in Xorg 7.4 doesn't support KMS IIRC, so to run with it turn modesetting off.

Thanks, I was able to make it work. Here are the steps I followed to get it to boot up into Xorg:

0. Xorg-7.4 and grpahics-2.6.33.3 must NOT be in the onboot list.
1. I added "options i915 modeset=0" to /etc/modprobe.conf and added it to filetool.
2. I added tce-load instructions for graphics-2.6.33.3-tinycore and Xorg-7.4 to .profile before the final startx statement.

That was it. This procedure was necessary as the extensions must be loaded after the modprobe.conf file gets restored. I don't know how to do it otherwise - is there a better, more streamlined method?
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: bmarkus on May 10, 2010, 05:42:34 AM
Possible speed gains and size losses, nothing guaranteed though.

Using the same build script, mc.tcz is 586k on 3.0 while 606k on 2.10

Speed? No idea :)
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: curaga on May 10, 2010, 06:22:09 AM
one thing that might be important - ati driver now requires a small piece of firmware for accelerated operation.
one for KMS (all cards) , second for Xorg (some cards).

in case of my x1300 card, i need /lib/firmware/radeon/R520_cp.bin or KMS might fail to start.

True, see firmware.tcz

@jur: Since that file does not exist in the base, it's a great candidate for an additional initrd, even if you use grub.
Place only it to a gzipped cpio archive, place the archive into tce dir. Profit :)

Quote
mkdir -p /tmp/ex/etc
cd /tmp/ex
cp /etc/modprobe.conf etc
find | cpio -o -H newc | gzip > ../modconf.gz
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: jur on May 10, 2010, 06:49:06 AM
2) My netbook only shows the power button and the sleep button after installing acpid and accompanying files. None of the other function keys are responding.

It might be worth looking at "dmesg | grep ACPI" to see which keys are recognised on boot?
Here are some dmesg results:
tc2.11:
Code: [Select]
tc@box:~$ dmesg | grep input

input: Power Button (FF) as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input1
input: Sleep Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2
input: Power Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
input: Asus EeePC extra buttons as /devices/virtual/input/input5
input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input6
generic-usb 0003:045E:0040.0001: input: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-0000:00:1d.1-2/input0
input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input7

and
Code: [Select]

tc@box:~$ dmesg | grep eeepc

eeepc: Eee PC Hotkey Driver
eeepc: Hotkey init flags 0x41
eeepc: Get control methods supported: 0x101713

tc3.0a:
Code: [Select]
tc@box:~$ dmesg | grep input

input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
input: Macintosh mouse button emulation as /devices/virtual/input/input4
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input5
input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input6
input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input7
generic-usb 0003:045E:0040.0001: input: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-0000:00:1d.1-2/input0
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
The dmesg | grep eeepc returns empty in tc3.0a.

I am using Asus 1000HE eeepc.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: roberts on May 10, 2010, 09:21:15 AM
Hi!

Forgot a suggestion (Sweden is playing hockey right now so I might be a little distracted). I changed the colour of the title bar to medium grey instead of light blue and I think it looks better but it's just an aesthetical thing.

Have fun and keep up the good work,
meo

P.S. Nice new logo!!! D.S.
Changed title bar to medium grey.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: bmarkus on May 10, 2010, 09:49:09 AM
On a stock TC I installed following extensions with appbrowser:

mc.tcz
glib2-dev.tcz
libiconv-dev.tcz
compiletc.tcz

/tce is stored on Linux ext4 partition of USB stick.

All extensions including dependencies are loaded and it works as expected. However after reboot only

mc.tcz
glib2-dev.tcz
libiconv-dev.tcz

loaded with their deps, compiletc and its dependencies are not. Reinstalling TC, formatting drive, moving /tce from USB to HDD ext3 partition gives the same result.

Trying to load compiletc.tcz from local repo appbrowser just gets stucked but nothing happenes.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Arslan S. on May 10, 2010, 10:02:33 AM
when i update dep files  through appsaudit some entries inside some dep files related to kernel modules are named to *-2.6.29.1-tinycore.tcz

for example:
download alsa, then update dep database then see alsa.tcz.dep
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Jason W on May 10, 2010, 10:20:25 AM
I just grepped for 2.6.29.1 in all the dep files and did not find an instance.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: bmarkus on May 10, 2010, 10:23:50 AM
On a stock TC I installed following extensions with appbrowser:

mc.tcz
glib2-dev.tcz
libiconv-dev.tcz
compiletc.tcz

/tce is stored on Linux ext4 partition of USB stick.

All extensions including dependencies are loaded and it works as expected. However after reboot only

mc.tcz
glib2-dev.tcz
libiconv-dev.tcz

loaded with their deps, compiletc and its dependencies are not. Reinstalling TC, formatting drive, moving /tce from USB to HDD ext3 partition gives the same result.

Trying to load compiletc.tcz from local repo appbrowser just gets stucked but nothing happenes.

Further info. Replacing compiletc.tcz with extension list from compiletc.tcz.dep in onboot.lst all extensions are loaded except gcc.tcz
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Arslan S. on May 10, 2010, 10:24:39 AM
I just grepped for 2.6.29.1 in all the dep files and did not find an instance.

dep files in 3.x repo correct but appsaudit is updating dep files from 2.x repo probably
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: curaga on May 10, 2010, 10:26:44 AM
Looks like tce-update and tce-audit both still refer to the 2.x repo.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: roberts on May 10, 2010, 11:35:31 AM
On a stock TC I installed following extensions with appbrowser:

mc.tcz
glib2-dev.tcz
libiconv-dev.tcz
compiletc.tcz

/tce is stored on Linux ext4 partition of USB stick.

All extensions including dependencies are loaded and it works as expected. However after reboot only

mc.tcz
glib2-dev.tcz
libiconv-dev.tcz

loaded with their deps, compiletc and its dependencies are not. Reinstalling TC, formatting drive, moving /tce from USB to HDD ext3 partition gives the same result.

Trying to load compiletc.tcz from local repo appbrowser just gets stucked but nothing happenes.

That is because of infinite loop in ppl.tcz.dep. It contains self reference.
Easy fix to edit ppl.tcz.dep and remove ppl.tcz

I have updated it in the 3.x repo.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: roberts on May 10, 2010, 11:36:35 AM
Looks like tce-update and tce-audit both still refer to the 2.x repo.
Got it fixed for alpha2. Thanks!
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: maro on May 10, 2010, 02:11:20 PM
As I was curious about any other "2.x" occurrence in 3.0alpha1 I did a search across the entire initrd. In addition to the already reported scripts the 'appbrowser' executable showed up as well. So I had a quick look at the latest available source and found command = "busybox wget -cq ftp://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/tcz/mirrors.lst"; (in line 258 of 'appbrowser.fl').

I now wonder if it would make sense to store this information (i.e. the "major" release) in a file like '/opt/tce_major' instead of hard coding it in scripts and sources.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: roberts on May 10, 2010, 03:17:46 PM
Thanks but it has already been taken care in a generic way.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: tclfan on May 11, 2010, 06:05:57 AM
In result of my limited testing it appears all worked in terms of browsers and desktops with the exception that when using hackedbox wm the wbar and around was messed up after loading firefox or chromium.
This is nothing new or related to 3.0 though as the same behavior was detected in 2.11.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: bmarkus on May 11, 2010, 06:34:00 AM
It looks OK. I set up a development environment and started to compile/update my extensions on 3.0alpha1 No any issue found during compilation and use of the enw or old extensions.

Title: Re: Tiny Core 3.0 Alpha Testing
Post by: jur on May 11, 2010, 06:46:09 AM
Any word on the missing eeepc modules (is that the right word?)that I mentioned previously? My netbook hardware does not work as well as it does in 2.x.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: Juanito on May 11, 2010, 06:56:08 AM
Any word on the missing eeepc modules (is that the right word?)that I mentioned previously? My netbook hardware does not work as well as it does in 2.x.

I see there's a module named "dell*" that loads on my laptop - that I haven't investigated yet. Do have an equivalent for eeepc?

Is there anything in the .config that references eeepc that might have been missed?
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: curaga on May 11, 2010, 07:04:19 AM
Re eeepc module

Looks like it has taken an additional dependency, pci hotplug, and that's why it doesn't show up in the config list.
Added on my todo list; don't expect it in alpha2 though.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: MakodFilu on May 11, 2010, 07:53:09 AM
In result of my limited testing it appears all worked in terms of browsers and desktops with the exception that when using hackedbox wm the wbar and around was messed up after loading firefox or chromium.
This is nothing new or related to 3.0 though as the same behavior was detected in 2.11.

I wonder if that is related to a whole line that has disappeared from .setbackground between 2.10 and 2.11.
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: jano on May 11, 2010, 01:55:43 PM
Results of limited testing after installing in a pendrive: no problems.
It finds & mounts the hard drives of my Acer Aspire One netbook (as it has a poulso chipset, it was not supported before TC 2.xx) - and with Alsa, Pcmanfm and VLC all working, it seems I have all I needed  ;D ;D ;D
Thanks for the great job !!
Title: Re: Tiny Core 3.0 Alpha Testing
Post by: roberts on May 11, 2010, 02:57:07 PM
On then to alpha2...