WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Tiny Core 3.0 Alpha 3 Testing  (Read 14618 times)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 7812
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #15 on: May 15, 2010, 01:16:08 PM »
I didn't try this before in the previous alpha versions:
Code: [Select]
$ 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.
The only barriers that can stop you are the ones you create yourself.

Offline jur

  • Hero Member
  • *****
  • Posts: 863
    • cycling photo essays
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #16 on: May 15, 2010, 03:07:44 PM »
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.

Offline jano

  • Newbie
  • *
  • Posts: 37
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #17 on: May 16, 2010, 05:46:32 AM »
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  :(

Offline lucky13

  • Jr. Member
  • **
  • Posts: 76
    • my mostly linux-related blog
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #18 on: May 16, 2010, 06:08:07 AM »
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.

Offline popolon

  • Newbie
  • *
  • Posts: 5
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #19 on: May 16, 2010, 06:49:05 AM »
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?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 7812
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #20 on: May 16, 2010, 07:46:46 AM »
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.
The only barriers that can stop you are the ones you create yourself.

Online bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 4841
    • My Community Forum
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #21 on: May 16, 2010, 11:26:56 AM »
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:

Quote
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:

Quote
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.
« Last Edit: May 16, 2010, 11:29:22 AM by bmarkus »
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 7812
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #22 on: May 16, 2010, 01:00:39 PM »
@bmarkus, I see you're running in KMS mode. See the earlier alpha threads, can't remember which one.
The only barriers that can stop you are the ones you create yourself.

Online bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 4841
    • My Community Forum
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #23 on: May 16, 2010, 09:04:17 PM »
@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.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline jur

  • Hero Member
  • *****
  • Posts: 863
    • cycling photo essays
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #24 on: May 16, 2010, 09:33:44 PM »
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:
Quote from: 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
Code: [Select]
mkdir -p /tmp/ex/etc
cd /tmp/ex
cp /etc/modprobe.conf etc
find | cpio -o -H newc | gzip > ../modconf.gz

Offline jano

  • Newbie
  • *
  • Posts: 37
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #25 on: May 16, 2010, 09:44:32 PM »
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 ...
« Last Edit: May 16, 2010, 09:46:04 PM by jano »

Offline lucky13

  • Jr. Member
  • **
  • Posts: 76
    • my mostly linux-related blog
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #26 on: May 17, 2010, 01:02:23 AM »
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?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 7812
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #27 on: May 17, 2010, 01:33:27 AM »
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.
The only barriers that can stop you are the ones you create yourself.

Online bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 4841
    • My Community Forum
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #28 on: May 17, 2010, 03:19:31 AM »
BTW, what is about Xorg update for 3.0?
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 7812
Re: Tiny Core 3.0 Alpha 3 Testing
« Reply #29 on: May 17, 2010, 05:25:44 AM »
When it's ready.
The only barriers that can stop you are the ones you create yourself.