dCore-wheezy for x86 now posted.

[Jason W]

Ok, you have assigned a label to the device, that does help narrow it down.  I can test that when I get in tonight.

How many devices do you have attached (hd, usb) and has that changed since dCore was last working as expected?

What is the output of the below command?

blkid -s LABEL /dev/sdb1

[jls]

Hi
what's the difference between http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie.gz
and
http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie-5.14.09.03.iso
?
 

[Jason W]

Should only be that one is an ISO.   I will be posting ISOs of releases/release candidates for all the dCore once things settle down.

[Jason W]

JLS, are you having the same issue still?  If so, please give me all the details you can so I can narrow it down. 

[jls]

I get the the extensions loaded at boot time changing :

Code: [Select]

waitusb=5:UUID=f184710d-4609-47c3-897e-4b8a0a6c02a2to

Code: [Select]

waitusb=5

[jls]

Code: [Select]

jls@eeepc:~$ showbootcodes
BOOT_IMAGE=/boot/dCore/vmlinuz loglevel=3 noutc tz=CET-1CEST-2,M3.5.0,M10.5.0 lang=fr_FR.UTF-8 waitusb=5 tce=UUID=f184710d-4609-47c3-897e-4b8a0a6c02a2/dce user=jls host=eeepc vga=788 laptop multivt

[jls]

Code: [Select]

jls@eeepc:~$ version
5.14.06.13
should be updated

[netnomad]

Ok, you have assigned a label to the device, that does help narrow it down.  I can test that when I get in tonight.
How many devices do you have attached (hd, usb) and has that changed since dCore was last working as expected?
What is the output of the below command?
blkid -s LABEL /dev/sdb1

tc@box:~$ blkid -s LABEL /dev/sdb1
/dev/sdb1: LABEL="MYSTICK"
tc@box:~$ blkid -s LABEL /dev/sdb2
/dev/sdb2: LABEL="tc"

my setup offers an internal harddisk sda and i use an usbstick with sdb1 fat32 and sdb2 ext4.
sdb1 boots with syslinux the different core-files and several other live-systems.
sdb2 labeled with tc contains my extensions and my chronological backups.

[Jason W]

Netnomad, that is my exact same hardware setup so I can test label booting and hopefully find what is going on.

[Jason W]

I will automate the updating of the version file, it is easy to overlook.

[Jason W]

Netnomad, your boot options look like they are for core.gz and not dCore.

[Jason W]

Ok, I think I have found a fix.  I am booting with the LABEL= options, and it is working here, it did not before.

Please test.

[netnomad]

Ok, I think I have found a fix.  I am booting with the LABEL= options, and it is working here, it did not before.

hi jason,
you've got it!!! now it boots fine!
great work

Netnomad, your boot options look like they are for core.gz and not dCore.

sorry, i gave you the wrong bootcodes
i corrected them above and offer them here, too:

kernel /live/dcore-current/boot/vmlinuz waitusb=5:LABEL=tc protect restore=LABEL=tc tce=LABEL=tc/tce lst=sceboot.lst vga=795 psmouse.proto=imps settime tz=CET-1CEST,M3.5.0,M10.5.0/3 laptop kmap=de multivt lang=de_DE.UTF-8 mydata=dcore blacklist=snd_usb_audio intel_rng.no_fwh_detect=-1 printk.time=1 cron desktop=fluxbox log=3 acpi_sleep=s3_bios,s3_mode showapps
append initrd=/live/dcore-current/boot/dCore.gz


these options worked fine for so long.
i thought that the same kernel is loaded with similar tinycore-specific options.
are there options that make no sense?

thank you for your help and commitment

[Jason W]

I copied the dCore.gz in release_candidates to release, updated the /usr/share/doc/tc/release.txt, actually automated it so it should always reflect the day it was packed. 

Please report any issues.

[netnomad]

...works flawless, smooth and fine for me