WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: tinycore_v2.9rc3  (Read 11969 times)

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
tinycore_v2.9rc3
« on: February 12, 2010, 06:56:51 PM »
The Third Release Candidate of v2.9 (tinycore_2.9rc3.iso), is now posted and ready for testing
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates

tinycore_2.9rc3.iso
tinycore_2.9rc3.iso.md5.txt

Change log for Tiny Core v2.9

Release Candidate 1

* Updated appbrowser - added "Provides" to search for "What provides", also speed improvements.
* Updated appsaudit - added "Display All Not Depends On".
* Updated tce-load - added support for recursive dependencies.
* Updated tc-config - persistent home and/or opt, changed ext only support to not Microsoft file system support.
* Updated ab to use tmp work files.
* Improved language support by auto loading locale support extension(s) when both "lang=  " and the "-locale.tcz" extension(s) are available in tce/optional.
* Renamed *.core.gz to simply *.gz for ISO9660 compliance.
* Clean up of reported relics and empty directories.
* Updated f2 & f3 boot message screens.
* Fixed bug in tce-update easy mode.
* Dropped the embedded help file.

Notes:

Attention extension makers, please test the new recursive dependency process, but hold in abeyance until v2.9 is final.

Since the embedded help file has been dropped, your system menu, likely in your backup will need to be adjusted. Edit/remove such entry.


Release Candidate 2

* Upgraded busybox to stable 1.15.3
* Upgraded udev to 151.
* New "Set TCE Drive" in control panel to setup TCE directory, optional and mydata.tgz from cloud mode.
* Upgraded tce-load and appsaudit to support copy2fs flag and list in the base tce directory.
* Updated OnDemand to also support re-launching applicatons. Now one can always use the OnDemand menu section.
* Updated support for easy mode remastering /opt/tce now uses onboot.lst
* Updated tc-config to also make, if necessary, optional directory when tce= boot code is used.
* Added cache, .logo.xpm, and stats.txt to default /opt/.xfiletool.lst
* Updated  /opt/.xfiletool.lst to persist OnDemand menu item across reboots via normal backup.


Notes: Files likely in your backup that need updating:
The following have been added to the default /opt/.xfiletool.lst:

cache
home/tc/.wmx/Applications
home/tc/.logo.xpm
home/tc/stats.txt

Release Candidate 3
* Fixed new udev firmware issue.
* Fixed easy mode remaster to support copy2fs flag and list in static /opt/tce.
* Updated Control Panel, label change TCE Update to Update Apps.
* Purged system menu Tools section with item already present in Control Panel.

Items likely in your backup or persistent store that need to be updated
/home/tc/.wmx/Tools/

   
10+ Years Contributing to Linux Open Source Projects.

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: tinycore_v2.9rc3
« Reply #1 on: February 12, 2010, 10:30:40 PM »
As reported for rc2 and still in rc3:

Quote
rebuildfstab[2685]: segfault at 8 ip 0806f590 sp bffd8510 error 4 in busybox[8048000+7c000]

I see these only when I have wireless_tools in onboot.

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11520
Re: tinycore_v2.9rc3
« Reply #2 on: February 13, 2010, 12:44:49 AM »
I do not see any errors with
Code: [Select]
$ sudo rebuildfstab /etc/fstab

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11520
Re: tinycore_v2.9rc3
« Reply #3 on: February 13, 2010, 05:49:41 AM »
I first though this was something between tc-1.x and tc2.x, but in fact things work as expected in tc-1.x and tc-2.8.1 - the issue is with tc-2.9rc3 - something to do with udev?

I've recently tried updating my old kayak xu from tc-1.x to tc-2.x

For some reason no usb devices show up in tc-2.9rc3 - I've played around for a while without much progress.

On both tc-1.x and tc-2.9rc3, I get this:
Code: [Select]
$ lspci
...
00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
...
00:10.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:10.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:10.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:10.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01)

On tc-1.x, I get this:
Code: [Select]
$ lsmod
Module                  Size  Used by
usblp                  11264  0
ohci_hcd               19076  0

On tc-2.9rc3 (with usb ohci, ehci compiled in), I get this:
Code: [Select]
$ lsmod
...
usblp                   6556  0

On tc-1.x, I get this:
Code: [Select]
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:a700 Standard Microsystems Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 03f0:0211 Hewlett-Packard OfficeJet G85

..but on tc-2.9rc3, "lsusb" doesn't show anything, but I do get this:
Code: [Select]
$ lsusb -t
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/2p, 12M
    |__ Port 1: Dev 2, If 0, Class=print, Driver=usblp, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/2p, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/2p, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
    |__ Port 3: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M

..and on tc-2.9rc3:
Code: [Select]
$ dmesg | grep usb
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usb usb1: configuration #1 chosen from 1 choice
usb usb2: configuration #1 chosen from 1 choice
usb usb3: configuration #1 chosen from 1 choice
usb usb4: configuration #1 chosen from 1 choice
usb usb5: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
usb 1-3: new high speed USB device using ehci_hcd and address 2
usb 1-3: configuration #1 chosen from 1 choice
usb 4-1: new full speed USB device using ohci_hcd and address 2
usb 4-1: configuration #1 chosen from 1 choice
usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 3 vid 0x03F0 pid 0x0211
usbcore: registered new interface driver usblp
usbcore: registered new interface driver oss_usb


Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11520
Re: tinycore_v2.9rc3
« Reply #4 on: February 13, 2010, 05:53:53 AM »
Also on tc-2.8.1 compared to tc-2.9rc3...

This works in .xsession tc-2.8.1:
Code: [Select]
/usr/bin/Xvesa -br -screen 1280x1024x16 -shadow -mouse /dev/psaux,5 -nolisten tcp -I >/dev/null 2>&1 &
waitforX
...

..but in tc-2.9rc3, I get a message about the screen mode requested not being supported - however, if I run xsetup.sh and chose the same thing - i.e. "1280x1024x16", then things work??

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v2.9rc3
« Reply #5 on: February 13, 2010, 06:31:41 AM »
I would agree that the udev upgrade is the bane of 2.9.
It probably should have been delayed until Core v3.0.
 I may have to pull it.
10+ Years Contributing to Linux Open Source Projects.

Offline meo

  • Hero Member
  • *****
  • Posts: 563
Re: tinycore_v2.9rc3
« Reply #6 on: February 13, 2010, 06:49:56 AM »
Hi there!
Thank you Robert for your work to improve tinycore. Unfortunately I still get the following boot message:

Starting sound driver: snd-nm256
amixer: Mixer attach defaulterror: No such file or directory

finishing the boot sequence. Is there a way to pass around this problem and get the sound to work? I use alsa and have it started by the bootlocal.sh. I have never had any problem with my somewhat troublesome neomagic sound chip in tinycore before, neither in DSL by the way. Other huge distributions that come with everything but the kitchen sink (read SuSE linux, Mandriva and Ubuntu) have given me problems during the years associated with the sound chip.

Have fun constantly improving this wonderful distro,
meo
"All that is very well," answered Candide, "but let us cultivate our garden." - Francois-Marie Arouet Voltaire

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v2.9rc3
« Reply #7 on: February 13, 2010, 06:51:32 AM »
Meo, Does it work in v2.8.1 ?
10+ Years Contributing to Linux Open Source Projects.

Online curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10157
Re: tinycore_v2.9rc3
« Reply #8 on: February 13, 2010, 07:00:51 AM »
Juanito, is it possible the device has changed paths? find /dev -name "*lp*"

I have only usb sticks available, but those work fine in rc3.

Robert, I do agree it's a rough ride; but this is why I hoped for it to be over before the other major changes in 3.0. Changing a lot at once it becomes much harder to pinpoint where things broke.

Meo, sorry if I've asked this already, but is your alsa.tcz up to date?
The only barriers that can stop you are the ones you create yourself.

Offline sci_fi

  • Jr. Member
  • **
  • Posts: 86
Re: tinycore_v2.9rc3
« Reply #9 on: February 13, 2010, 07:08:16 AM »
Confirming.

I am having similar problems to Meo with alsa. The problems were present in rc2 and continue in rc3, although seemed not present in rc1 (I am currently using rc1 with skype for example). Alsa works fine for me in 2.8.1 as well.  My alsa module is up to date, per appsedit.

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.

The firmware fix in rc3 is working fine for me.

Best regards,

sci_fi

Online curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10157
Re: tinycore_v2.9rc3
« Reply #10 on: February 13, 2010, 07:14:05 AM »
Also on tc-2.8.1 compared to tc-2.9rc3...

This works in .xsession tc-2.8.1:
Code: [Select]
/usr/bin/Xvesa -br -screen 1280x1024x16 -shadow -mouse /dev/psaux,5 -nolisten tcp -I >/dev/null 2>&1 &
waitforX
...

..but in tc-2.9rc3, I get a message about the screen mode requested not being supported - however, if I run xsetup.sh and chose the same thing - i.e. "1280x1024x16", then things work??
Is the same line generated by xsetup? I wonder what does it change.
The only barriers that can stop you are the ones you create yourself.

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11520
Re: tinycore_v2.9rc3
« Reply #11 on: February 13, 2010, 07:17:43 AM »
Juanito, is it possible the device has changed paths? find /dev -name "*lp*"

I have only usb sticks available, but those work fine in rc3.

in tc-1.x:
Code: [Select]
$ find /dev -name "*lp*"
/dev/.udev/names/usb\x2flp0
/dev/.udev/names/usb\x2flp0/\x2fdevices\x2fpci0000:00\x2f0000:00:10.2\x2fusb5\x2f5-1\x2f5-1:1.0\x2fusb\x2flp0
/dev/.udev/names/par0/\x2fdevices\x2fpci0000:00\x2f0000:00:10.2\x2fusb5\x2f5-1\x2f5-1:1.0\x2fusb\x2flp0
/dev/.udev/db/\x2fdevices\x2fpci0000:00\x2f0000:00:10.2\x2fusb5\x2f5-1\x2f5-1:1.0\x2fusb\x2flp0
/dev/usb/lp0

In tc-2.9rc3 on a different machine, the above does not give anything and lsusb does not give anything (even though the usb stick I booted from is there)

Do you see your usb sticks with lsusb in 2.9rc3?

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11520
Re: tinycore_v2.9rc3
« Reply #12 on: February 13, 2010, 07:22:03 AM »
I didn't pay attention to all of .xsession, but the "1280x1024x16" bit did not change...

Online curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10157
Re: tinycore_v2.9rc3
« Reply #13 on: February 13, 2010, 07:23:10 AM »
Everybody with udev problems, or suspected ones, please enable syslog, and:

Quote
cd /var/log

sudo udevadm control --log-priority=err
sudo udevadm trigger

grep -i udev messages* > /tmp/udev-err-logs

sudo udevadm control --log-priority=info
sudo udevadm trigger

grep -i udev messages* > /tmp/udev-info-logs
Then, please upload those two log files from /tmp somewhere, and post links here. This should help debug the issue.

pastebin.ca is a good text upload service.

edit: Had old info there, should have been "log-priority" with a dash instead of an underscore.
« Last Edit: February 13, 2010, 07:48:14 AM by curaga »
The only barriers that can stop you are the ones you create yourself.

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11520
Re: tinycore_v2.9rc3
« Reply #14 on: February 13, 2010, 07:35:54 AM »
I get:
Code: [Select]
$ sudo udevadm control --log_priority=err
control: unrecognized option '--log_priority=err'
unrecognized command
..same thing with =debug, but =info works

info log attached