tinycore_v2.9rc3

[curaga]

Just tested a fresh boot, and to be sure manually removed existing /dev/sd*. The device node for my stick appeared as it should.

Lsusb didn't show a thing, but it seems not to be a bug:
http://lkml.indiana.edu/hypermail/linux/kernel/0705.3/1225.html

I'll add that udev rule for testing.

edit: Confirmed, lsusb works with one added rule.

[meo]

Hi Robert!

Yes, the sound works just fine in tinycore 2.8.1. It also works just fine in tinycore 2.9rc1 which I'm running right now.

Have fun continuing your excellent work,
meo

[sci_fi]

Hi curaga,

here are some urls of the log files I tried to collect. Too big so I broke into two parts. info only. The error log only had a few bytes of complaints about wanting to change the command syntax in a later release. So not included.

http://pastebin.ca/1795391

http://pastebin.ca/1795392

Not sure I did everything properly here.
What commands should I run before doing the grep to extract the files. I did alsamixer only.

Best regards

sci_fi

[curaga]

Thanks sci_fi. Your logs were very useful.

Seems the alsa startup script somehow did not reload udev rules. Can you post the following:
- cat /usr/local/tce.installed/alsa
- ls -l /etc/udev/rules.d

[gerald_clark]

Also continuing to see segfaults ala busybody and rebuildfstab during boot. These problems did not occur in rc1 but are present in both rc2 and rc3.

I am also getting these errors, but only if I include wireless_tools in the boot?
Have you tried identifying which extension is triggering these errors on your system?

[sci_fi]

Hi curaga,

Here are the logs you requested.

http://pastebin.ca/1795521
http://pastebin.ca/1795522

Hope it helps.

sci_fi

[sci_fi]

Hi gerald_clark,

I have not tried to isolate the problems to a specific extension. I will try booting wo wireless tools to see if I can duplicate your results.

sci_fi

[sci_fi]

Follow up.

I removed wireless_tools.tcz and wireless-2.6.29.1-tinycore.tcz from my boot up. The segfaults and alsa problems still occurred.

sci_fi

[curaga]

Looks like your alsa.tcz is the one from Oct 2009 - before the -config split and the two updates for supporting the new udev. Are you perhaps using a mirror?

Here's the md5sum of the latest alsa.tcz:
75af7f641bac0be51dd53b6ac2aa7c14  alsa.tcz

If the app updater is reporting an older one as the latest, there's something amiss here.

Edit: s/appsaudit/app updater/

[sci_fi]

Thanks for the tip. I will check again and respond.

Also, fwiw I have gotten a warning all the way back to rc1 during extension loading as follows:

touch: usr/local/tce.installed/libusb: permission denied.
libusb is present belonging to tc staff rw  r r
Never seemed to cause a problem so I did not mention before.

Perhaps not important.

I will now double check alsa.

sci_fi

[sci_fi]

Hi Curaga,

When I do Appsaudit->Update->Check for updates the return is only that I need to upgrade firefox. Nothing else is mentioned.

The checksum does not match the checksum I have on alsa-config.tcz.md5 which is the only alsa related checksum in my optional older.

I will now uninstall alsa and reboot and reinstall.

sci_fi

[sci_fi]

Hi curaga,

Re-installing alsa on rc3 works. Skype and audio works.
Do check out appsaudit because it certainly gave me no indication that I was not current. Wonder what else may be old.

This did not help all the segfaults, however. Still, one more down.

Thanks,

sci_fi

[curaga]

Hi curaga,

Re-installing alsa on rc3 works. Skype and audio works.

Good to hear

[jur]

Code: [Select]

I have problems with chromium. Chromium won't load web pages, it reports
[code]
[2458:2463:677390998:ERROR:base/shared_memory_posix.cc(192)] Creating shared memory in /dev/shm/org.chromium.o3QTBj failed: No such file or directory
There are about 4 such lines, all same but with the number stuff different.

tc2.8.1 has no problem.

Also when booting, when the extensions are loaded I get a whole string of repeated messages, something about

Code: [Select]

/init.d/rcS (sp?) line 415: usleep: Text file busy
I haven't reproduced it exactly, but from memory.[/code]

[curaga]

On rc3, /dev/shm is mounted tmpfs as it should, and is world writable. If "touch /dev/shm/test" works as user tc, this is a chromium bug, as you can clearly use the area with user privileges then.