Core v4.4rc3

[Rich]

Hi AbNoRMiS
I think your /opt directory may not have its permissions set correctly. I just checked under TC2.1, TC3.4, and TC4.1
which all show the permissions set to 775.

[AbNoRMiS]

yep really, it's my fault, sorry
my /opt has permissions 755 and member of root group, not staff
owing you i found the excessive sudo in my script for core repackaging
thanks

[Rich]

Hi AbNoRMiS
Your welcome. Yes, I should have also mentioned the correct ownership is root:staff

[roberts]

hi roberts,

with the actual release candidate my ethernet-card works flawless now.

b44 ssb0:0: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet
b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
b44 ssb0:0: eth0: Flow control is off for TX and off for RX

thank you.

Thanks for sharing. Good news and success strories are always welcomed!

[coreplayer2]

isolinux 4.02 as used in core 4.4rc3 still will not boot on older Pentium III / Pheonix BIOS machines, hangs on first line of isolinux 4.02 text at boot, same applies with isolinux 4.05 

isolinux 3.82 and 3.84 continue to boot fine.

[coreplayer2]

While booting PLOP Boot Manager from a cd to boot TinyCore-4.4rc3.iso using YUMI from a multiboot USB (this specific machine can neither boot USB or any version of tc using isolinux version 4.x )  I've failed in all but one time, to find and mount sdb1 using "fromISOfile"  with bootcode or after boot using YUMI as described, short method or full path yet still unable to find or mount /mnt/sdb1/multiboot/ISOS/TinyCore-4.4rc3.iso 

Using either
sudo fromISOfile /mnt/sdb1
or 
sudo fromISOfile /mnt/sdb1/multiboot/ISOS/TinyCore-4.4rc3.iso

the script complains that it can't find either in fstab  which incidentally only contains /dev/sda1 and /dev/sr0 + a few other non pertinent entries..

Any ideas what we're missing here?

Update:  the key was in using something like  " sudo fromISOfile /sr0 "  which then mounted the tc.iso to /mnt/cdrom

[coreplayer2]

The next gotcha, is trying to establish a wifi connection.   wireless-3.0.3-tinycore.tcz is installed to cde/optional   

You know this is coming..  the latest TinyCore-4.4rc3 needs wireless-3.0.21-tinycore.tcz  to function

please

[AbNoRMiS]

there is missing checksum cde/optional/wireless-3.0.21-tinycore.tcz.md5.txt in CorePlus-4.4rc3.iso

[curaga]

isolinux 4.02 as used in core 4.4rc3 still will not boot on older Pentium III / Pheonix BIOS machines, hangs on first line of isolinux 4.02 text at boot, same applies with isolinux 4.05 

isolinux 3.82 and 3.84 continue to boot fine.

Please report this bug to syslinux, if you haven't already.

[bernhard]

isolinux 4.02 as used in core 4.4rc3 still will not boot on older Pentium III / Pheonix BIOS machines, hangs on first line of isolinux 4.02 text at boot, same applies with isolinux 4.05 

no problems with a dual PIII 700MHz (BX chipset) with AMI BIOS and booting via PloP from an USB stick  the CorePlus-4.4rc3.iso image with iso=sdb1 ...

PS: take care that there is no other iso image on the stick, otherwise you have to specify the full name and path to the iso (see also: http://forum.tinycorelinux.net/index.php/topic,12724.msg69967.html#msg69967)

Bernhard

[coreplayer2]

The ISOLINUX problem is consistently reproducible with each and every isolinux version  since IIRC 4.0, 4.01, 4.02, 4.03, 4.05, I believe I just attempted 4.06 it's a shame but they all fail to boot on old equipment I have..    Pity really because Grub is considerably slower to boot than isolinux on PC's that it works on.

Isolinux 3.x (all versions) work great on my old notebook, yet for some reason I have trouble booting TC after version 4.1 with it.  I don't think there is any reason for this, right?  Am really looking for tc4.4 to run on older equipment but the isolinux issue makes this a non starter. 

Thanks bernhard for that link, I spent hours looking for that thread again yesterday without any luck..     But what is a "Dual PIII" anyhow??  A dual core or a dual proc.? either of which is a newer design than the notebook I'm using

[coreplayer2]

Additionally, I still get the "udevadm settle - timeout of 5 seconds reached, the  event queue contains: /sys/module/scsi_wait_scan (874) " issue  which hangs until depressing the enter key which then brings up a command prompt

[curaga]

Additionally, I still get the "udevadm settle - timeout of 5 seconds reached, the  event queue contains: /sys/module/scsi_wait_scan (874) " issue  which hangs until depressing the enter key which then brings up a command prompt

It's not a hang, it's merely printed on top of the terminal...

[coreplayer2]

..On top of the terminal, ok agreed but there is no command line prompt until after some user input,  because we are waiting for the prompt to appear, it doesn't until after some user initiated keyboard input, which kinda constitutes a hang right?

How about not having the status message at all? instead have the command exit to a prompt??

[bernhard]

Thanks bernhard for that link, I spent hours looking for that thread again yesterday without any luck..    

you're welcome ...

But what is a "Dual PIII" anyhow??  A dual core or a dual proc.?

a dual processor. It is an industrial dual slot 1 motherboard and about 10 years old. Bios is dated back to 2001.

either of which is a newer design than the notebook I'm using

oh, what is it dated?

Bernhard