WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Tiny Core v4.0 Alpha 2 Testing  (Read 5393 times)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 6347
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #15 on: September 03, 2011, 04:13:59 AM »
..but doing that in tc-3 stopped the broadcom "wl" driver (and possibly others) from working, as ssb needed to be blacklisted.

Offline netnomad

  • Hero Member
  • *****
  • Posts: 738
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #16 on: September 03, 2011, 04:19:28 AM »
modprobe ssb
modprobe -r b44 ssb
don't work...

is it a mistake in the core and should it work with the base without user interaction or as an onboot.lst-item?
there is also a hint to a modprobe.dep, what does that mean?
what do you recommend?
« Last Edit: September 03, 2011, 04:21:33 AM by netnomad »

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 7818
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #17 on: September 03, 2011, 07:02:21 AM »
Right, it's a compromise either way. As I have no broadcom hw of any kind, I'm probably not the right person to make that choice.

I would lean towards supporting the wired one by default, and requiring blacklisting to use the broadcom wl module, but would like to hear what you guys think.
The only barriers that can stop you are the ones you create yourself.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 6347
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #18 on: September 03, 2011, 07:09:51 AM »
I believe it makes most sense to support wired connections by default

Online bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 4850
    • My Community Forum
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #19 on: September 03, 2011, 09:03:26 AM »
I believe it makes most sense to support wired connections by default

+1
Béla
Ham Radio callsign: HA5DI

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

Offline netnomad

  • Hero Member
  • *****
  • Posts: 738
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #20 on: September 03, 2011, 11:04:33 AM »
I believe it makes most sense to support wired connections by default

hopefully that's the direction or decision!

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7344
  • Founder Emeritus
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #21 on: September 03, 2011, 11:20:45 AM »
Supporting as much wired as was possible with the kernel was the original goal and should therefore remain.
10+ Years Contributing to Linux Open Source Projects.

Offline yoshi314

  • Full Member
  • ***
  • Posts: 117
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #22 on: September 04, 2011, 10:52:59 AM »
when using Xorg, installing firmware-radeon and graphics-3.0.3 the boot progress gets stuck on loading extensions.

i have a few dmesg messages about radeon drm and then i get the rotating spinner, and nothing else happens. it just keeps spinning, and apparently waits for something.

i'd like someone with radeon gfx card to re-check this.
« Last Edit: September 04, 2011, 10:54:55 AM by yoshi314 »

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7344
  • Founder Emeritus
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #23 on: September 04, 2011, 11:11:04 AM »
If you can, boot with boot option,  'showapps'. Each extension will then be displayed. This might be useful to see which extension is hanging.
10+ Years Contributing to Linux Open Source Projects.

Offline u54749

  • Jr. Member
  • **
  • Posts: 66
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #24 on: September 04, 2011, 11:49:55 AM »
The busybox binary isn't setuid root anymore.  Is this intentional?

I have serious instabilities with this alpha version (Xorg, ALSA, ...).  After four hours of searching I have come to the conclusion that the new "ldconfig" binary is malfunctioning.

Here is an example with the libva extension

~ $ tce-load -i libva.tcz
libva.tcz: OK
~ $ ldconfig -p | grep libva

result with the alpha2 ldconfig
        libva.so.1 (libc6) => /usr/local/lib/libva.so.1
        libva.so (libc6) => /usr/local/lib/libva.so
        libva-x11.so.1 (libc6) => /usr/local/lib/libva-x11.so.1
        libva-x11.so (libc6) => /usr/local/lib/libva-x11.so
        libva-tpi.so.1 (libc6) => /usr/local/lib/libva-tpi.so.1
        libva-tpi.so (libc6) => /usr/local/lib/libva-tpi.so
        libva-glx.so.1 (libc6) => /usr/local/lib/libva-glx.so.1
        libva-glx.so (libc6) => /usr/local/lib/libva-glx.so

result with the alpha1 ldconfig
        libva.so.1.0.4 (libc6) => /usr/local/lib/libva.so.1.0.4
        libva.so.1 (libc6) => /usr/local/lib/libva.so.1
        libva.so (libc6) => /usr/local/lib/libva.so
        libva-x11.so.1.0.4 (libc6) => /usr/local/lib/libva-x11.so.1.0.4
        libva-x11.so.1 (libc6) => /usr/local/lib/libva-x11.so.1
        libva-x11.so (libc6) => /usr/local/lib/libva-x11.so
        libva-tpi.so.1.0.4 (libc6) => /usr/local/lib/libva-tpi.so.1.0.4
        libva-tpi.so.1 (libc6) => /usr/local/lib/libva-tpi.so.1
        libva-tpi.so (libc6) => /usr/local/lib/libva-tpi.so
        libva-glx.so.1.0.4 (libc6) => /usr/local/lib/libva-glx.so.1.0.4
        libva-glx.so.1 (libc6) => /usr/local/lib/libva-glx.so.1
        libva-glx.so (libc6) => /usr/local/lib/libva-glx.so

The new ldconfig misses part of the entries.
When I copy over the old "ldconfig" in alpha2 everything works normally.


Offline yoshi314

  • Full Member
  • ***
  • Posts: 117
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #25 on: September 04, 2011, 11:56:12 AM »
If you can, boot with boot option,  'showapps'. Each extension will then be displayed. This might be useful to see which extension is hanging.
i'm having a hunch it's actually alsa startup script atm.

will test with the parameter.

edit: well, this is beyond embarrassing, but it seems i left the getfllash10 script in onboot.lst

and it asks for confirmation to reinstall, but it only shows with showapps boot parameter.
« Last Edit: September 04, 2011, 12:05:17 PM by yoshi314 »

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7090
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #26 on: September 04, 2011, 12:18:10 PM »
I noticed and fixed that getFlash10 issue as i saw the same thing almost a week ago. It happened when flash10.tcz is lower down the list in onbootl.st, which it naturally would be.

Have you updated your extensions recently, or is it doing this on a new install?

I will take another look at the startup script.

EDIT:  I see that my correction got lost in the shuffle, corrected extension is uploaded now.
« Last Edit: September 04, 2011, 12:27:07 PM by Jason W »

Offline yoshi314

  • Full Member
  • ***
  • Posts: 117
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #27 on: September 04, 2011, 12:44:44 PM »
I noticed and fixed that getFlash10 issue as i saw the same thing almost a week ago. It happened when flash10.tcz is lower down the list in onbootl.st, which it naturally would be.

Have you updated your extensions recently, or is it doing this on a new install?

I will take another look at the startup script.

EDIT:  I see that my correction got lost in the shuffle, corrected extension is uploaded now.

new install.

also, there is no cryptsetup in 4.x repositories. version from 3.x works just fine.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7344
  • Founder Emeritus
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #28 on: September 04, 2011, 01:42:54 PM »
The busybox binary isn't setuid root anymore.  Is this intentional?

I have serious instabilities with this alpha version (Xorg, ALSA, ...).  After four hours of searching I have come to the conclusion that the new "ldconfig" binary is malfunctioning.

Here is an example with the libva extension

~ $ tce-load -i libva.tcz
libva.tcz: OK
~ $ ldconfig -p | grep libva

result with the alpha2 ldconfig
        libva.so.1 (libc6) => /usr/local/lib/libva.so.1
        libva.so (libc6) => /usr/local/lib/libva.so
        libva-x11.so.1 (libc6) => /usr/local/lib/libva-x11.so.1
        libva-x11.so (libc6) => /usr/local/lib/libva-x11.so
        libva-tpi.so.1 (libc6) => /usr/local/lib/libva-tpi.so.1
        libva-tpi.so (libc6) => /usr/local/lib/libva-tpi.so
        libva-glx.so.1 (libc6) => /usr/local/lib/libva-glx.so.1
        libva-glx.so (libc6) => /usr/local/lib/libva-glx.so

result with the alpha1 ldconfig
        libva.so.1.0.4 (libc6) => /usr/local/lib/libva.so.1.0.4
        libva.so.1 (libc6) => /usr/local/lib/libva.so.1
        libva.so (libc6) => /usr/local/lib/libva.so
        libva-x11.so.1.0.4 (libc6) => /usr/local/lib/libva-x11.so.1.0.4
        libva-x11.so.1 (libc6) => /usr/local/lib/libva-x11.so.1
        libva-x11.so (libc6) => /usr/local/lib/libva-x11.so
        libva-tpi.so.1.0.4 (libc6) => /usr/local/lib/libva-tpi.so.1.0.4
        libva-tpi.so.1 (libc6) => /usr/local/lib/libva-tpi.so.1
        libva-tpi.so (libc6) => /usr/local/lib/libva-tpi.so
        libva-glx.so.1.0.4 (libc6) => /usr/local/lib/libva-glx.so.1.0.4
        libva-glx.so.1 (libc6) => /usr/local/lib/libva-glx.so.1
        libva-glx.so (libc6) => /usr/local/lib/libva-glx.so

The new ldconfig misses part of the entries.
When I copy over the old "ldconfig" in alpha2 everything works normally.
Both will be corrected in next cut. Thanks for reporting.
10+ Years Contributing to Linux Open Source Projects.

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7090
Re: Tiny Core v4.0 Alpha 2 Testing
« Reply #29 on: September 04, 2011, 01:48:35 PM »
yoshi314-

Try getFlash10 from a new download again, my correction had a typo that is fixed now.

Also, cryptsetup or anything that depends on kernel modules was not copied over to the 4.x repo.   When new modules are made and the 3.x extension tested, they can be submitted to 4.x.  Every extension was manually reviewed and copied or not copied over to 4.x on a case by case basis, so as to not start out with a broken repo.