Tiny Core Linux
Tiny Core Base => TCB News => Alpha Releases => Topic started by: roberts on May 14, 2010, 12:24:30 AM
-
Please continue testing the alpha versions of Tiny Core v3.0. Alpha3 is now posted:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates/tinycore_3.0alpha3.iso
Change log for alpha3.
* New kernel for support of pci-hotplug modules
* New modules for eeepc-laptop and ssb
* Updated tce-audit/appsaudit for agnostic kernel support.
* Updated ondemand, dropped jwm/wbar improved handling of multiple .desktop elements.
* Removed now unneeded tc2freedesk and add2file.
* Updated exittc to handle rare case of missing BACKUP env variable.
Note: You will need to update bzImage as well as tinycore.gz
-
Hi!
I'm impressed of the fast development of tinycore 3.0. Thanks to all that have been involved in the development of this excellent release even though it's still in alpha stage. It has worked extremely well with my laptop that is more than 8 years old. So thanks a lot!
Have fun developing tinycore 3.0 further,
meo
-
Eee pc users, the module now depends on both hwmon and pci-hotplug.
-
Good morning:
I use icewm. I notice that in the move to TC3.0 (all alpha's), the dropdown menu (right click on background) no longer contains a "Applications" ("tce extensions") entry. I am guessing that icewm may need an update, as this was not the case in 2.11.
This does not happen with flwm. The dropdown menu works as expected.
Also, the "TC Tools" entry in this dropdown is incomplete, that is, not all tools are listed. Perhaps not compatible with icewm?
Otherwise, I am having no problems so far with alpha3.
Best Regards,
sci_fi
-
Good morning:
I use icewm. I notice that in the move to TC3.0 (all alpha's), the dropdown menu (right click on background) no longer contains a "Applications" ("tce extensions") entry. I am guessing that icewm may need an update, as this was not the case in 2.11.
This does not happen with flwm. The dropdown menu works as expected.
Also, the "TC Tools" entry in this dropdown is incomplete, that is, not all tools are listed. Perhaps not compatible with icewm?
Otherwise, I am having no problems so far with alpha3.
Best Regards,
sci_fi
Alpha testing has been focused on the base.
The next phase will be to revisit the various window managers.
They should be ready during the release candidate phase.
-
I want to verify that b44 network driver is working now. Thanks.
-
I am going through the various extra things in this alpha.
* Looks like the eeepc hotkeys are back up - thanks!
* I am still having trouble mounting deps with KERNEL. I have to manually change all these to 2.6.33..... to get extensions to load. Examples are alsa, graphics, wireless-tools. If you look with appbrowser, alsa has as dep alsa-modules-2.6....., which itself has as dep input-joystick-KERNEL. That's where the wheels fall off.
-
@jur, the var is handled on dep download. Try updating deps via appsaudit, if you didn't already.
-
@jur, the var is handled on dep download. Try updating deps via appsaudit, if you didn't already.
Is it the idea that on one's machine, there should be no KERNEL deps, but that all are changed at download into the required 2.6....?
I'll start from scratch to make sure there is no "contamination." (Unfortunately my phone line is broken right now, will have to wait till later this week.)
-
OK, evidently the leftover KERNEL deps on my machine was indeed the problem. I deleted alsa+deps and tried, and it worked just fine. Also updated deps. (My pnone line is very intermittent so could just squeeze it through.)
-
I wonder of I might suggest some re wallpaper: Currently I am using the very nifty core logo but with blue background, the grey I find too industrial. It's just a bit difficult tweaking the color, as each time I start wallpaper, it starts with a default grey and I have to try and match the settings. Perhaps it could start with the current background color instead? That way small incremental tweaks are easy.
-
One more thing about wallpaper. It seems it is not possible to set a wallpaper image with a background color, you always have to leave it black, or, in case you wanna change it, it leaves you with the Tine Core logo in the center.
And I think jur has a good point there about the color picking mechanics.
-
I didn't try this before in the previous alpha versions:
$ ps aux | grep udev
80 root /sbin/udevd --daemon
1584 root /sbin/udevd --daemon
1587 root /sbin/udevd --daemon
It is normal that three instances of the daemon are running?
-
I wonder of I might suggest some re wallpaper: Currently I am using the very nifty core logo but with blue background, the grey I find too industrial. It's just a bit difficult tweaking the color, as each time I start wallpaper, it starts with a default grey and I have to try and match the settings. Perhaps it could start with the current background color instead? That way small incremental tweaks are easy.
The background color is recorded in /home/tc/.setbackground. By default all of /home/tc is included in the backup. Therefore user selected custom background color persists.
-
I didn't try this before in the previous alpha versions: $ ps aux | grep udev
80 root /sbin/udevd --daemon
1584 root /sbin/udevd --daemon
1587 root /sbin/udevd --daemon
It is normal that three instances of the daemon are running?
I saw this in tc2.11.
http://forum.tinycorelinux.net/index.php?topic=5871.msg31214#msg31214
-
I didn't try this before in the previous alpha versions: $ ps aux | grep udev
80 root /sbin/udevd --daemon
1584 root /sbin/udevd --daemon
1587 root /sbin/udevd --daemon
It is normal that three instances of the daemon are running?
Udev's threaded now, the amount of threads depends on activity I believe.
-
I wonder of I might suggest some re wallpaper: Currently I am using the very nifty core logo but with blue background, the grey I find too industrial. It's just a bit difficult tweaking the color, as each time I start wallpaper, it starts with a default grey and I have to try and match the settings. Perhaps it could start with the current background color instead? That way small incremental tweaks are easy.
The background color is recorded in /home/tc/.setbackground. By default all of /home/tc is included in the backup. Therefore user selected custom background color persists.
You misunderstood... I know that and my background is persistent... but if I want to make s amll adjustment I can't because when I open wallpaper, it starts with the default grey instead of the current user setting.
-
As with Alpha 2, I get boot errors with Alpha 3 (while mounting TC extensions). Then it boots, but (probably due to these boot errors) some things don't work (like mount from cpanel), so it's again back to Alpha 1 for me :(
-
As with Alpha 2, I get boot errors with Alpha 3 (while mounting TC extensions). Then it boots, but (probably due to these boot errors) some things don't work (like mount from cpanel), so it's again back to Alpha 1 for me :(
Testing has moved beyond alpha-1. If you're not going to test and report back on the latest alpha snapshot, please go back down to the latest 2.x release. The purpose of alpha testing is to find bugs and issues.
-
Hi
I can't find a driver anymore for the Ralink rt2860 wireless chipset in 3.0 alpha 3.
The rt2860 extension that works in 2.11 is not available. Which if i understand correctly is expected since that out-of-tree 2.6.29 driver has since become an in-tree staging driver. But the wireless-2.6.33-tinycore extension does not include the rt2860sta module, neither does it include the rt2800pci module (which is the target "official" driver for this chipset but might still not be fully working in 2.6.33).
Will the rt2860sta be included somewhere in the final Tiny Core 3.0?
-
No, the staging drivers offer an inferior experience, so at least not in the wireless extension. If someone from the community wishes to submit the out-of-tree driver against .33 that would be accepted, of course.
-
Installing graphics-2-6.33.3-tinycore.tcz on Acer Aspire 5720Z notebook with Intel graphics chipset WM/DE and default X server is terminated immediately when extension loaded; a terminal is available in frame buffer mode.
Syslog entries:
May 16 20:58:16 (none) local2.notice sudo: tc : TTY=unknown ; PWD=/mnt/sdb1/tce/optional ; USER=root ; COMMAND=/bin/mkdir -p /tmp/tcloop/i2c-2.6.33.3-tinycore
May 16 20:58:16 (none) local2.notice sudo: tc : TTY=unknown ; PWD=/mnt/sdb1/tce/optional ; USER=root ; COMMAND=/bin/mount i2c-2.6.33.3-tinycore.tcz /tmp/tcloop/i2c-2.6.33.3-tinycore -t squashfs -o loop,ro,bs=4096
May 16 20:58:16 (none) local2.notice sudo: tc : TTY=unknown ; PWD=/mnt/sdb1/tce/optional ; USER=root ; COMMAND=/bin/cp -as /tmp/tcloop/i2c-2.6.33.3-tinycore/usr /
May 16 20:58:16 (none) local2.notice sudo: tc : TTY=unknown ; PWD=/mnt/sdb1/tce/optional ; USER=root ; COMMAND=/sbin/depmod -a
May 16 20:58:16 (none) local2.notice sudo: tc : TTY=unknown ; PWD=/mnt/sdb1/tce/optional ; USER=root ; COMMAND=/sbin/udevadm trigger
May 16 20:58:17 (none) local2.notice sudo: tc : TTY=unknown ; PWD=/mnt/sdb1/tce/optional ; USER=root ; COMMAND=/sbin/ldconfig
May 16 20:58:17 (none) user.info kernel: i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19
May 16 20:58:17 (none) local2.notice sudo: tc : TTY=unknown ; PWD=/mnt/sdb1/tce/optional ; USER=root ; COMMAND=/bin/mkdir -p /tmp/tcloop/graphics-2.6.33.3-tinycore
May 16 20:58:17 (none) local2.notice sudo: tc : TTY=unknown ; PWD=/mnt/sdb1/tce/optional ; USER=root ; COMMAND=/bin/mount graphics-2.6.33.3-tinycore.tcz /tmp/tcloop/graphics-2.6.33.3-tinycore -t squashfs -o loop,ro,bs=4096
May 16 20:58:17 (none) local2.notice sudo: tc : TTY=unknown ; PWD=/mnt/sdb1/tce/optional ; USER=root ; COMMAND=/bin/cp -as /tmp/tcloop/graphics-2.6.33.3-tinycore/usr /
May 16 20:58:17 (none) local2.notice sudo: tc : TTY=unknown ; PWD=/mnt/sdb1/tce/optional ; USER=root ; COMMAND=/sbin/depmod -a
May 16 20:58:18 (none) local2.notice sudo: tc : TTY=unknown ; PWD=/mnt/sdb1/tce/optional ; USER=root ; COMMAND=/sbin/udevadm trigger
May 16 20:58:18 (none) local2.notice sudo: tc : TTY=unknown ; PWD=/mnt/sdb1/tce/optional ; USER=root ; COMMAND=/sbin/ldconfig
May 16 20:58:18 (none) user.info kernel: Linux agpgart interface v0.103
May 16 20:58:18 (none) user.info kernel: agpgart-intel 0000:00:00.0: Intel 965GM Chipset
May 16 20:58:18 (none) user.info kernel: agpgart-intel 0000:00:00.0: detected 7676K stolen memory
May 16 20:58:18 (none) user.info kernel: agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0x80000000
May 16 20:58:18 (none) user.info kernel: [drm] Initialized drm 1.1.0 20060810
May 16 20:58:18 (none) user.info kernel: i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
May 16 20:58:18 (none) user.debug kernel: i915 0000:00:02.0: setting latency timer to 64
May 16 20:58:18 (none) user.debug kernel: i915 0000:00:02.0: irq 30 for MSI/MSI-X
May 16 20:58:18 (none) user.info kernel: [drm] set up 7M of stolen space
May 16 20:58:18 (none) user.info kernel: [drm] initialized overlay support
May 16 20:58:19 (none) user.warn kernel: Console: switching to colour frame buffer device 160x50
May 16 20:58:19 (none) user.info kernel: fb0: inteldrmfb frame buffer device
May 16 20:58:19 (none) user.info kernel: registered panic notifier
May 16 20:58:19 (none) user.info kernel: acpi device:3a: registered as cooling_device2
May 16 20:58:19 (none) user.info kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input7
May 16 20:58:19 (none) user.info kernel: ACPI: Video Device [OVGA] (multi-head: yes rom: no post: no)
May 16 20:58:19 (none) user.info kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
May 16 20:58:33 (none) user.debug kernel: mtrr: no MTRR for 80000000,800000 found
Installing Xorg-7.4.tcz after that Xorg.0.log:
X.Org X Server 1.6.1
Release Date: 2009-4-14
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29.1-tinycore i686
Current Operating System: Linux box 2.6.33.3-tinycore #2012 SMP Wed May 12 17:05:42 EEST 2010 i686
Build Date: 25 April 2009 08:42:34PM
Before reporting problems, check www.tinycorelinux.com
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun May 16 21:04:24 2010
(II) Loader magic: 0x7abc
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 2
(--) PCI:*(0@0:2:0) unknown vendor (0x8086) unknown chipset (0x2a02) rev 3, Mem @ 0x94000000/1048576, 0x80000000/268435456, I/O @ 0x00005110/8
(--) PCI: (0@0:2:1) unknown vendor (0x8086) unknown chipset (0x2a03) rev 3, Mem @ 0x98500000/1048576
(==) Using default built-in configuration (39 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier "Builtin Default intel Device 0"
Driver "intel"
EndSection
Section "Screen"
Identifier "Builtin Default intel Screen 0"
Device "Builtin Default intel Device 0"
EndSection
Section "Device"
Identifier "Builtin Default i810 Device 0"
Driver "i810"
EndSection
Section "Screen"
Identifier "Builtin Default i810 Screen 0"
Device "Builtin Default i810 Device 0"
EndSection
Section "Device"
Identifier "Builtin Default vesa Device 0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Builtin Default vesa Screen 0"
Device "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier "Builtin Default fbdev Device 0"
Driver "fbdev"
EndSection
Section "Screen"
Identifier "Builtin Default fbdev Screen 0"
Device "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Builtin Default intel Screen 0"
Screen "Builtin Default i810 Screen 0"
Screen "Builtin Default vesa Screen 0"
Screen "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default intel Screen 0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default intel Device 0"
(==) No monitor specified for screen "Builtin Default intel Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default i810 Screen 0" (1)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default i810 Device 0"
(==) No monitor specified for screen "Builtin Default i810 Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (2)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (3)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
Using a default monitor configuration.
(==) Not automatically adding devices
(==) Not automatically enabling devices
(WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/local/lib/X11/fonts/100dpi/" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/local/lib/X11/fonts/misc/,
/usr/local/lib/X11/fonts/TTF/,
/usr/local/lib/X11/fonts/Type1/,
/usr/local/lib/X11/fonts/75dpi/,
built-ins
(==) ModulePath set to "/usr/local/lib/X11/modules"
(==) |-->Input Device "<default pointer>"
(==) |-->Input Device "<default keyboard>"
(==) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
(==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
- -1 0 0xffffffff - 0xffffffff (0x1) MX
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX
(II) LoadModule: "extmod"
(II) Loading /usr/local/lib/X11/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/local/lib/X11/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/local/lib/X11/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/local/lib/X11/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "intel"
(II) Loading /usr/local/lib/X11/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 2.7.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "i810"
(WW) Warning, couldn't open module i810
(II) UnloadModule: "i810"
(EE) Failed to load module "i810" (module does not exist, 0)
(II) LoadModule: "vesa"
(II) Loading /usr/local/lib/X11/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 2.2.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "fbdev"
(II) Loading /usr/local/lib/X11/modules/drivers//fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 0.4.0
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "mouse"
(II) Loading /usr/local/lib/X11/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.4.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(II) LoadModule: "kbd"
(II) Loading /usr/local/lib/X11/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 1.3.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, IGD_GM, IGD_G, 965G, G35,
965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
Mobile Intel® GM45 Express Chipset,
Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41
(II) VESA: driver for VESA chipsets: vesa
(II) FBDEV: driver for framebuffer: fbdev
(II) Primary Device is: PCI 00@00:02:0
(II) resource ranges after xf86ClaimFixedResources() call:
- -1 0 0xffffffff - 0xffffffff (0x1) MX
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX
(WW) Falling back to old probe method for vesa
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/local/lib/X11/modules/linux//libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
compiled for 1.6.1, module version = 0.0.2
ABI class: X.Org Video Driver, version 5.0
(II) FBDEV(1): using default device
Fatal server error:
Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
Please consult the TinyCore Linux support
at www.tinycorelinux.com
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
TC 2.11 with Graphics-2.6.29.1-tinycore.tcz / Xorg-7.4.tcz on the same hardware works fine.
-
@bmarkus, I see you're running in KMS mode. See the earlier alpha threads, can't remember which one.
-
@bmarkus, I see you're running in KMS mode. See the earlier alpha threads, can't remember which one.
You are right, it was in Alpha1. Using 'nomodeset' boot option it starts. Changing /etc/modprobe.conf reguires remastering and I had no time for it.
-
You are right, it was in Alpha1. Using 'nomodeset' boot option it starts. Changing /etc/modprobe.conf reguires remastering and I had no time for it.
I used a very simple procedure successfully for adding an initrd to tce, given by curaga:
@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
mkdir -p /tmp/ex/etc
cd /tmp/ex
cp /etc/modprobe.conf etc
find | cpio -o -H newc | gzip > ../modconf.gz
-
As with Alpha 2, I get boot errors with Alpha 3 (while mounting TC extensions). Then it boots, but (probably due to these boot errors) some things don't work (like mount from cpanel), so it's again back to Alpha 1 for me :(
Testing has moved beyond alpha-1. If you're not going to test and report back on the latest alpha snapshot, please go back down to the latest 2.x release. The purpose of alpha testing is to find bugs and issues.
Maybe I didn't make myself clear.
I've tested and reported issues on booting with alpha-2 and now with alpha-3 that I didn't have with alpha-1, hoping it would be useful. Perhaps I should have attached an excerpt of syslog with the booting errors, as I did while testing alpha-2. But as I didn't get any comment there, I thought that a simple statement here about the errors on booting and mount from cpanel not working would be enough...
[And as alpha-1 supports my chipset, while latest 2.x does not, I am currently using it in my system].
Sorry to have disturbed you lucky13 ...
-
Maybe I didn't make myself clear.
I've tested and reported issues on booting with alpha-2 and now with alpha-3 that I didn't have with alpha-1, hoping it would be useful. Perhaps I should have attached an excerpt of syslog with the booting errors, as I did while testing alpha-2. But as I didn't get any comment there, I thought that a simple statement here about the errors on booting and mount from cpanel not working would be enough...
[And as alpha-1 supports my chipset, while latest 2.x does not, I am currently using it in my system].
Sorry to have disturbed you lucky13 ...
First, you don't disturb me. I went back to the a-2 thread and you never elaborated on which extension(s) you loaded, what kind of hardware, etc., to explain what might be needed to reproduce the same problem. Was this related to 64-bit kernel? Did you get the same or similar errors booting "base norestore" etc.? What chipset was supported in a-1 but not previously?
-
You are right, it was in Alpha1. Using 'nomodeset' boot option it starts. Changing /etc/modprobe.conf reguires remastering and I had no time for it.
Well, you're right. Param "nomodeset" is a much simpler way to make Intel cooperate with UMS. I didn't recommend it earlier, because I wasn't sure if it was an official parameter (missing from kernel-parameters.txt), but I see now from the code it is.
-
BTW, what is about Xorg update for 3.0?
-
When it's ready.
-
First, you don't disturb me. I went back to the a-2 thread and you never elaborated on which extension(s) you loaded, what kind of hardware, etc., to explain what might be needed to reproduce the same problem. Was this related to 64-bit kernel? Did you get the same or similar errors booting "base norestore" etc.? What chipset was supported in a-1 but not previously?
You are absolutely right. But I didn't elaborate about all these things because I didn't know I had to, my knowledge of linux is very, very limited and nobody asked me to clarify.... so I'll try to make things better now. Excuse me if I post irrelevant information.
* My computer is a Acer Aspire One, AO751H with an Intel Atom processor Z520 with an ide 160 Gb harddisk. TC 2.10 was able to boot from a CD or a pendrive, but it didn't recognize (find?) the harddisk. In a thread I started on that issue curaga pointed that "it's a poulsbo chip. Unsupported currently in TC 2.x. Unless someone makes an extension, wait for 3.x." So I have been using TC 2.10 and 2.11 booting from a ext2 formatted SD card.
* The tests I have done with alpha-1, alpha-2 and alpha-3 all have been done booting from the same SD card (formatted as ext2, with persistent home and opt). All three alpha's do find the harddisk now.
* With alpha-1 I haven't found any problem so far and thus I use it now as if it were stable. With alpha-2 I found different boot errors (different in different boots as I mentioned in the alpha-2 thread) while loading the TC Extensions. With alpha-3, also boot errors at the same stage.
* As I think that the system is 32 bits, I have only used 32-bit kernel.
* The extensions I load on boot are: alsa, pcmanfm and vlc. Only these three.
* The bootcodes I use are: quiet vga=788 noswap home=sdb1 opt=sdb1 laptop restore=sdb1/tce max_loop=255 waitusb=5
* I changed waitusb to 10 but it didn't make any difference
* Both in alpha-2 or in alpha-3, after the boot errors, the system finally boots and all three extensions do work, but other things, like mounting a pendrive through cpanel's mount do not work (I guess is that it is related to the errors on booting)
I attach the message after booting with syslog enabled.
-
I suggest you start clean with a new V3 CD and no USB pen drive.
-
I suggest you start clean with a new V3 CD and no USB pen drive.
Will try that for testing and post the results, but as the netbook has no CD drive, I'll have to revert to pendrive for everyday use.
-
jano, what happens when you boot with the following boot options?
base norestore text
Perhaps you have the same issue as reported above with Acer Aspire and intel graphics chipset.
Worked in alpha1 but not alpha2 or alpha3 until they used nomodeset boot option. Might give that a try as well.
-
Here are the results:
* Booting from a new alpha-3 CD worked OK (no boot errors)
* Booting from the SD card with base norestore text worked OK (no boot errors either). startx then gave me back the WM
I've done some additional testing, always booting from the SD card :
* With base norestore worked OK (no boot errors either) and direct to the WM
* With base and home=sdb1 opt=sdb1 restore=sdb1/tce worked OK (no boot errors either), direct to the WM, have to manually install the extensions but all install and work OK
;D
* Finally, removing the base from the boot options [that is, my first boot configuration], brings back the boot errors. So it seems to me that the problem arises when installing the extensions at boot time.
* Adding nomodeset to the boot options doesn't prevent the boot errors
-
Here are the results:
* Booting from a new alpha-3 CD worked OK (no boot errors)
* Booting from the SD card with base norestore text worked OK (no boot errors either). startx then gave me back the WM
I've done some additional testing, always booting from the SD card :
* With base norestore worked OK (no boot errors either) and direct to the WM
* With base and home=sdb1 opt=sdb1 restore=sdb1/tce worked OK (no boot errors either), direct to the WM, have to manually install the extensions but all install and work OK
;D
* Finally, removing the base from the boot options [that is, my first boot configuration], brings back the boot errors. So it seems to me that the problem arises when installing the extensions at boot time.
* Adding nomodeset to the boot options doesn't prevent the boot errors
Is your Aspire One like mine with two card readers (left and right side)? In my past experience using Linux on my AA1, the right one has seldom worked (in fact, it caused more freezes during boot than it ever had successful boots) and the left one has been a little better. I've never trusted it enough to ever consider booting from it or even to let it mount it at boot (I have automount disabled in both Windows and Scientific Linux on the AA1) and it's pissed me off that it's so dodgy that I have to boot with a card inserted to be able to use it at all. My work around for both card readers in Linux has been to use a small USB card reader instead or directly connect my camera or whatever device; that way I can read SD/Micro/etc. cards whether I have one inserted at boot or not.
If it has two card readers, have you tried the SD card in both slots? Just the right one or just the left one? If you have a USB card reader/adapter, have you tried using it with the usual bootcodes?
Just to make sure we're on the same page, did you get the application extensions from the 3.0 repository or are those ones you have from the 2.0 repositories?
AFAIK, you should've been able to boot earlier TinyCore versions with that Atom CPU. Have you always tried to use the SD card slot for that or have you tried external readers, USB sticks, etc., and left the card slots on the AA1 out of the mix altogether?
-
My AA1 has only one card reader (in the right side) that has always worked without problems in Windows and Linux. It is the way I boot normally TC. I have tried with a usb card adapters with the same results. Booting from a usb pendrive has worked in the same way as with the SD card (and I prefer the SD card as it doesn't protrude out of the netbook). And both with fat and ext2 filesystems.
With the SD card (or pendrive, CD, etc) I hace been able to boot TC 2.10 and TC 2.11, but they didn't "find" the harddrive, so I couldn't install it to the harddisk.
I'm quite sure the extensions come from the 3.0 repository, as I did a fresh "USB install" (not an upgrade) (which formats the card) to the card from an alpha-1 CD and then downloaded the extensions.
My tests for tonight (as I have to go to work now) are (unless someone comes with different sugestions):
* Make and test a new fresh clean install from alpha-3 CD, reformatting the card and downloading the extensions.
* If that fails again, test booting with only one extension at a time, to see if the boot errors appear while installing a specific extension
* Then try with two extensions ...
Thank you for your comments
-
Do check both the fs and the card for bad blocks. (install e2fsprogs_apps.tcz, run "e2fsck -c -f /dev/sdx1", replace sdx1 with your device)
Also, it's highly peculiar your errors started from alpha2 when no changes were made to anything related. Signs would point to corruption somewhere.
Please also check the md5sums of all your extensions.
-
Something nice:
My wlan sensitivity is up by 20dB! I can now sit comfortably in the lounge by the fire. The EE in me can't explain how a radio can work better to the tune of a whopping 20dB with a new driver but I'll take it thanks!
Something broken:
My touchpad which had 100% workability before in 2.11 does not respond properly to tapping; it sorta works but only "halfway" eg tapping on wbar does not cause the icon to depress but does start the app. I also cannot click-drag with double-tapping action like before. Finally, 2-finger dragging across the pad which is supposed to scroll, no longer works.
dmesg in 2.11 reported a Logitech wheel-mouse, whereas now it reports a Elantech touchpad. Well it is a touchpad but it doesn't work vey well. Is there a driver I should load? Or can I somehow invoke the Logitech setup as before?
-
Are you using Xorg-7.4? If so, you could try the synaptics touchpad driver.
-
Are you using Xorg-7.4? If so, you could try the synaptics touchpad driver.
Well unfortunately that didn't work so well. Mounted the extension, modded xorg.conf. 2-finger scrolling now works but tapping is totally disabled. No amount of fiddling with parameters that looked likely, had any effect.
How about trying to use that which was in the previous kernel? I notice from dmesg that previously the input devices were shown a bit differently. I suppose that is due to the new kernel?
-
My AA1 has only one card reader (in the right side) that has always worked without problems in Windows and Linux. It is the way I boot normally TC. I have tried with a usb card adapters with the same results. Booting from a usb pendrive has worked in the same way as with the SD card (and I prefer the SD card as it doesn't protrude out of the netbook). And both with fat and ext2 filesystems.
I brought up the card slot(s) because I'm trying to figure out if it's basically like mine has been (this was my first and will be my last Acer). With the udevd error messages you were getting per your comment in the alpha-2 thread I was wondering if the card has been getting caught in some kind of loop or even delay after boot while devices are being populated so that it's not properly reading your tce directory (which reflects some of my own experiences frustrations with my AA1 and why I just use an external reader in Linux rather than deal with the way both readers on my AA1 have proven rather dysfunctional under Linux). But now you write that you get the same errors whether the card is in the internal slot or an external USB reader. I'm trying to figure out how -- barring any corrupt disk or extension(s); please test as curaga suggests -- you'd have no issue under alpha-1 even after trying -2 and -3 unless there's a rule change/conflict causing you some kind of delay since -2 (which is possible but doesn't seem likely from the changelog).
Just to make sure... Did you try alpha-1, -2, and -3 all with both external and internal readers? And did you get similar results either way -- working under -1 internal/external, not working in -2 or -3 internal/external (with comparable waitusb time periods)? And you were able to safely revert to -1 (internally or externally) without any recurrence of the same issue?
-
Well unfortunately that didn't work so well. Mounted the extension, modded xorg.conf. 2-finger scrolling now works but tapping is totally disabled. No amount of fiddling with parameters that looked likely, had any effect.
How about trying to use that which was in the previous kernel? I notice from dmesg that previously the input devices were shown a bit differently. I suppose that is due to the new kernel?
psmouse.proto should be your option; see kernel-parameters.txt for what protocols it takes.
-
No good news so far:
No errors in the SD card - md5sums of all the extensions are OK.
Reinstalled a fresh alpha-3 in the SD card and checked again for errors and the md5sums -> everything OK.
Booting from the card (directly through the card reader or with a USB reader or USB adapter) with base boot option works OK and I can manually install the extensions without problem, but trying to install only one extension on booting (alsa, pcmanfm or vlc) gives me again booting errors, with waitusb=10.
With alpha-1 (simply overwriting bzImage and tinycore.gz) makes everything work: the three extensions install on boot, without errors, with waitusb=5.
-
Initial setup on my Acer Aspire One netbook model ZG5 is going well. I'm using 32-bit everything, and happy to be submitting this forum post using 3.0a3 with a wireless link. Suggestions:
1. Make at least the wireless extensions easy to find and download without special tools like appbrowser, so users like me can grab them using some other distribution where the wireless works and stuff them into an appropriate tce directory or usb device before booting the alpha release, because its wireless is not working *yet*.
2. Consider putting the "o" back into the "Dwnload" label on the Appbrowser button. (Minimalism is great, but that's one "o" too far. ;))
3. Update the info file for package wireless_tools.tcz so it keeps up with the current kernel version. Right now the info file mentions 2.6.29.1, but the dep file cites wireless-KERNEL.tcz.
Warm regards to all contributors!
-
3. Update the info file for package wireless_tools.tcz so it keeps up with the current kernel version. Right now the info file mentions 2.6.29.1, but the dep file cites wireless-KERNEL.tcz.
Done
-
bug:
in the 64bit kernel the Xserver starts it does vm86 panic unknown execution codes.. when i install xorgs 7.4 it works but with 7.4 i can't change the display resolution.
at the begining the xsetup not works because of the same reason
bug:
also in 32bit and 64bit the gcc include path doesn't work properly.
i have downlodeded nginx and the configure script cant compalie a simple code
it says cant find sys/types.h
complaint:
on 32 and 64 the default resolution is 800x600 and it is too small
the resolution as in tinycore2 is good.
bad ideas:
i dont like the gray. i like the windows 7 color scheme.
or the bumptop default color scheme.
i was play around with a cmyk color, suppose the y is heat of color I set it to 50%, m is warning-ness of color I set it to 0, C is life or comness I set it to 100%, k is brightness I set it to somthing pleasent not too bright not too dark, maybe Golden ratio 38/62 may do the work.
how about thouse bg colors: #005b72(C100 M0 Y13 K60) or #00766d(C100 M0 Y50 K38 ) or #006991 or #03493a or #00aab0 ... (limited liability warning: this color theory i developed today on the spot so it might be totaly wrong and there is no replacment for trained eyes of a professional designer).
-
tinycore64.gz has been withdrawn due to the fact that Xvesa does not work. Xorg is required.
Please test microre64.gz together with Xlibs.gz, Xprogs.gz, ...
-
also in 32bit and 64bit the gcc include path doesn't work properly.
i have downlodeded nginx and the configure script cant compalie a simple code
it says cant find sys/types.h
Likely you installed only gcc, without the rest; try compiletc.tcz.
-
btw i also tested on 64bit the package 'Xvesa from XOrg 7.1' and it also did not worked.
@roberts
there is no xprogs package
-
@curaga
i have created a new microcore and the compilation worked ok.
maybe i have messed somthing.
probably one of the packages was not downloaded fully
-
in 64 bit version and probably in 32 bit
compiling gcc -m64
fails - sorry unimplemented
i guess the gcc is not compiled with x86_64 enabled
-
@roberts
there is no xprogs package
tinycore64.gz was built from microcore64.gz plus the other gzipped cpio'ed initramfs files as found here:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates/microcore/
It is where you will find Xlibs.gz, Xprogs.gz, ...
-
It's not multilib. 64-bit applies to kernel related stuff only afaik.
-
Well unfortunately that didn't work so well. Mounted the extension, modded xorg.conf. 2-finger scrolling now works but tapping is totally disabled. No amount of fiddling with parameters that looked likely, had any effect.
How about trying to use that which was in the previous kernel? I notice from dmesg that previously the input devices were shown a bit differently. I suppose that is due to the new kernel?
psmouse.proto should be your option; see kernel-parameters.txt for what protocols it takes.
Right. I finally got to proper experimentation with this, and found the boot option psmouse.proto=imps seems to get all functions working as before. Thanks!
-
It's not multilib. 64-bit applies to kernel related stuff only afaik.
True.
The 64-bit cross-toolchain can be found in the toolchain64.tcz extension.