Debian Jessie dCore

[Jason W]

Glad to hear that Wheezy is working now, I had adjusted Jessie at the same time as I was fairly confident it would be a go.  Have you tried it yet?

[netnomad]

hi jason,

with jessie i have no luck with your last cut.
by the way, i use the backup-file and the sce-packages from my wheezy setup.

[Jason W]

Don't try to mix wheezy and jessie sce's, it will not work.

By no luck, you mean the LABEL= boot option does not find the right device, or that there are issues with the packages?

[netnomad]

hi jason,

in my opinion my central problem is still the label-issue...
the error messages are the same as i experienced with wheezy.
sce-package-error-messages caused by a conflict between wheezy and jessie look different.

[netnomad]

hi jason,

importsce works fine,
but my tce-directory and my backup is not found during the boot process,
although i can manually mount my second partition on my usbstick that provides them.

if i avoid the label-option, the bootcodes restore=sdb2 and tce=sdb2/tce don't work, too

[Jason W]

Ok, I will look into it soon.

[Jason W]

Netnomad - pardon the delay, I have been busy lately.  Via ssh login to my box at home I think I see the simple culprit and I will fix and test it when I get home tonight.

[netnomad]

hi jason,

sounds great!

thank you for your work and commitment.

[Jason W]

I think I have fixed it, uploaded:

http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie.gz
http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie.gz.md5.txt

[netnomad]

hi jason,

with this cut i succeed without label:
kernel /live/dcore-testing/boot/vmlinuz waitusb=5 protect restore=sdb2 tce=sdb2/tce lst=sceboottest.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=dcoret 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-testing/boot/dCore.gz

but there are still problems with labels, perhaps its just the waitusb-command?
kernel /live/dcore-testing/boot/vmlinuz waitusb=5:LABEL=tc protect restore=LABEL=tc tce=LABEL=tc/tce lst=sceboottest.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=dcoret 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-testing/boot/dCore.gz

[netnomad]

hi jason,

i guess that waitusb has problems with labels!

waitusb=10:LABEL=tc
makes problems
but
waitusb=5
works fine

[netnomad]

hi jason,

in my configuration the swap based on zram does not work and in wbar the xterm icon does not appear ,
but the rest looks pretty promising

keep on hacking!

[Jason W]

Zramswap is still a work in progress.  I will look further into the rest.

[Jason W]

I can boot here with waitusb with both the UUID and LABEL.

waitusb=30:LABEL=SCE
waitusb=30:UUID=EF2B-4EE5

It echoes that it is waiting, then after a second or two it continues booting once the drive has been awakened.

[Jason W]

I have confirmed that Wheezy dCore is working as expected with the label and uuid specific waitusb commands as well as the uuid and label specified tce directory.

I will make these changes in the Ubuntu dCores as well.