WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: tinycore_v2.9rc4  (Read 11500 times)

Offline jur

  • Hero Member
  • *****
  • Posts: 863
    • cycling photo essays
Re: tinycore_v2.9rc4
« Reply #15 on: February 18, 2010, 03:09:37 AM »
Robert:
 
Booting my netbook at home is an even bigger mess. Something fundamental seems to be going wrong - I get an avalanche of error messages, all of which go away if I use 'base'.

The thing is, my two setups are just totally different - one is booting of a vfat usb stick on my work laptop (couple years old Toshiba Satellite 512MB mem) with only /tce persistent and no onboot extensions, while the home netbook is an Asus 1000he with 1GB mem different everything, Xorg, persistent /home, /opt, on ext3 hard drive partition.

But these 2 very different setups give very similar results - total mess while booting. Both cases boot fine with tc-2.8.1

One thing I have in both setups, is a whole swag of tinycore.gz files, named eg tinycore-2.9rc4 if I am not booting off them. Both setups, these files are in /tce, not in/boot or whatever. Could there be some mixup?

Is there a way to record a boot log so I can send you the error messages?

Offline jur

  • Hero Member
  • *****
  • Posts: 863
    • cycling photo essays
Re: tinycore_v2.9rc4
« Reply #16 on: February 18, 2010, 03:51:27 AM »
I think I have found the problem.

In both the aforementioned cases, once I moved the booting files to a directory called /boot, booting proceeds fine. Permissions for /dev/shm are also correct.

So the difference between tc-2.8 and tc-2.9rc4 is, the booting files cannot be in /tce in 2.9rc4, while with 2.8.1 (and prior versions) this presents no problem.

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11901
Re: tinycore_v2.9rc4
« Reply #17 on: February 18, 2010, 05:30:18 AM »
once I moved the booting files to a directory called /boot, booting proceeds fine.

By "booting files", do you mean bzImage and tinycore.gz/microcore.gz and/or Xlibs.gz, XProgs.gz and Xvesa.gz?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10207
Re: tinycore_v2.9rc4
« Reply #18 on: February 18, 2010, 06:08:05 AM »
@bmarkus: the glibc extensions haven't yet been updated to 2.11.1.
The only barriers that can stop you are the ones you create yourself.

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7035
    • My Community Forum
Re: tinycore_v2.9rc4
« Reply #19 on: February 18, 2010, 06:37:29 AM »
@bmarkus: the glibc extensions haven't yet been updated to 2.11.1.

OK, I will postpone this test. Do you have a timeframe?
Béla
Ham Radio callsign: HA5DI

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

Offline jls

  • Hero Member
  • *****
  • Posts: 2134
Re: tinycore_v2.9rc4
« Reply #20 on: February 18, 2010, 08:31:48 AM »
I think I have found the problem.

In both the aforementioned cases, once I moved the booting files to a directory called /boot, booting proceeds fine. Permissions for /dev/shm are also correct.

So the difference between tc-2.8 and tc-2.9rc4 is, the booting files cannot be in /tce in 2.9rc4, while with 2.8.1 (and prior versions) this presents no problem.
I also moved bzimage and tinycore.gz from tce to boot and now chromium shows the pages
dCore user

Offline jls

  • Hero Member
  • *****
  • Posts: 2134
Re: tinycore_v2.9rc4
« Reply #21 on: February 18, 2010, 08:32:31 AM »
@bmarkus: the glibc extensions haven't yet been updated to 2.11.1.
so this menas that using this rc4, the apps only start in english?
dCore user

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7035
    • My Community Forum
Re: tinycore_v2.9rc4
« Reply #22 on: February 18, 2010, 08:52:51 AM »
@bmarkus: the glibc extensions haven't yet been updated to 2.11.1.
so this menas that using this rc4, the apps only start in english?

Yes
Béla
Ham Radio callsign: HA5DI

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

Offline jur

  • Hero Member
  • *****
  • Posts: 863
    • cycling photo essays
Re: tinycore_v2.9rc4
« Reply #23 on: February 18, 2010, 01:28:15 PM »
once I moved the booting files to a directory called /boot, booting proceeds fine.

By "booting files", do you mean bzImage and tinycore.gz/microcore.gz and/or Xlibs.gz, XProgs.gz and Xvesa.gz?
Yes.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10207
Re: tinycore_v2.9rc4
« Reply #24 on: February 18, 2010, 02:38:58 PM »
I see now, the core gz code had picked up your tinycore.gz/microcore.gz images.
The only barriers that can stop you are the ones you create yourself.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v2.9rc4
« Reply #25 on: February 18, 2010, 03:15:59 PM »
jur, Glad to hear the mystery is solved. The difference in 2.9 was making the core.gz file ISO9660 compliant, i.e., simply using .gz  which matches the base initramfs files of tinycore.gz and microcore.gz.
10+ Years Contributing to Linux Open Source Projects.

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7035
    • My Community Forum
Re: tinycore_v2.9rc4
« Reply #26 on: February 19, 2010, 01:46:06 AM »
Installing an already installed application with Appbrowser message is 'successfully installed'. Few versions back it was changed to 'already installed' but this change is gone. :(
Béla
Ham Radio callsign: HA5DI

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

Offline jur

  • Hero Member
  • *****
  • Posts: 863
    • cycling photo essays
Re: tinycore_v2.9rc4
« Reply #27 on: February 19, 2010, 04:49:05 AM »
I just noticed I have no sound in rc4. There was a sound issue in an earlier 2.9rc but that was resolved at the extension level, involving udev rules. I get this after alsasound start:
Code: [Select]
amixer: Mixer attach default error: No such file or directory
« Last Edit: February 19, 2010, 04:51:15 AM by jur »

Offline meo

  • Hero Member
  • *****
  • Posts: 563
Re: tinycore_v2.9rc4
« Reply #28 on: February 19, 2010, 05:21:16 AM »
Hi jur!

I've had the same problem until I discovered that curaga has updated alsa.tcz to work with the newer rc's. So it is just to reinstall alsa I would guess. It works for me now in tinycore 2.9rc4. To Robert I want to offer my sincere apologies for believing that the sound problem was caused by the core. Just as stated above it was just a matter of updating alsa.tcz to the newest one. In my defense I can say that I tried out tinycore 2.9rc4 at approximately 3 am local time after trying to resolve a problem of a complete different kind and as if that wouldn't be enough I have a chronic medical condition, furthermore I had a really bad cold that finally is getting better. So thanks for the new improved rc!

Have fun and keep on refining tinycore,
meo
"All that is very well," answered Candide, "but let us cultivate our garden." - Francois-Marie Arouet Voltaire

Offline jur

  • Hero Member
  • *****
  • Posts: 863
    • cycling photo essays
Re: tinycore_v2.9rc4
« Reply #29 on: February 19, 2010, 10:53:47 PM »
tce-update didn't report that alsa needs updating. So I deleted it plus all its dependencies, and re-downloaded it, and now sound works. Thanks meo!