dCore Import Debian Packages to Mountable SCE extensions > dCore X86

Boot-code tce=LABEL not working

<< < (2/3) > >>

sm8ps:
Many thanks for double-checking, Jason! I have always been using those boot-codes without any trouble, too.

Another thought: the laptop sports an Intel Pentium M processor. Could it be that the kernel does not support it? I recall quite some discussions about PAE. But then I would expect the machine going bonkers way more dramatically.

The Grub2 boot-stanza reads

--- Code: ---menuentry "ub-dC sm" {
search --no-floppy --label --set=root "dC"
linux /boot/vmlinuz-trusty blacklist=pcspkr tce=LABEL="dC" home=LABEL="dC" opt=
LABEL="dC" user=sm host=fjsa lang="de_CH.UTF-8" tz=CET-1CEST,M3.5.0,M10.5.0/3 m
ultivt syslog showapps desktop=openbox resume=/dev/sda7 laptop
initrd /boot/dCore-trusty.gz
}
--- End code ---

I copied it basically verbatim from the existing dCore-trusty installation:

--- Code: ---menuentry "ub-dCore" {
search --no-floppy --label --set=root "dCORE"
linux /boot/vmlinuz-xenial blacklist=pcspkr tce=LABEL="dCORE" home=LABEL="dCORE
" opt=LABEL="dCORE" host=fjs lang="de_CH.UTF-8" tz=CET-1CEST,M3.5.0,M
10.5.0/3 multivt syslog showapps desktop=openbox resume=LABEL="SWAP" laptop
initrd /boot/dCore-xenial.gz
}
--- End code ---
The only noticable change regards the use of "LABEL" in the boot-code "resume". Yet that should be irrelevant for the boot-up if there is no resume image available (double-checked).

''blkid'' gives

--- Code: ---/dev/sda1: LABEL="SYSTEM" UUID="DA76EE3976EE1653" TYPE="ntfs"
/dev/sda5: LABEL="ROOT" UUID="2b05e3fe-295b-47fb-9f65-c6f33261afe1" TYPE="ext4"
/dev/sda6: LABEL="HOME" UUID="10aa76a6-d5d0-4d99-ac00-5ded978f9493" TYPE="ext4"
/dev/sda7: LABEL="SWAP" UUID="fd6d2f55-b8c0-466f-ba89-7f38e8199b73" TYPE="swap"
/dev/sda8: LABEL="dC" UUID="9fa1b78d-ead6-45c8-90e0-8b406c0690cf" TYPE="ext4"
/dev/sda9: LABEL="dCORE" UUID="e51b6b98-7a47-4f44-8255-f1a9bb963bf6" TYPE="ext4"
--- End code ---

''mount'' shows '/dev/sda9' mounted on '/mnt/sda9', '/home' and '/opt' but not on '/etc/sysconfig/tce-dir'.

sm8ps:
I must be overlooking something terribly obvious! I tested with kernel and initrd from the Trusty installation copied to the same location as the new Xenial kernel (sda9=dCORE). Even then the tec-directory points to '/tmp/tce'. So things do not seem to behave normally here.

After issueing ''tce-setdrive'' and ''sce-load wireless'', I get segmentation faults in busybox. Is my harddisk failing? Though, Busybox should not be affected by such a problem, or should it? The MD5-sums of kernel and initRD were OK. SMART-values of the disk are OK.

I suspect that I have to search for the cause of the error somewhere outside. So in case anybody has some clue on what to check then I would be grateful.

sm8ps:
I have found a solution but one that should not be needed! Exchanging "=LABEL=dCORE" with "sda9" everywhere in the boot stanza makes dCore-xenial behave as expected. The persistent tce-directory is detected and ''sce-load'' works flawlessly.

Now I would be glad to understand why this is so. -- Anybody?

Rich:
Hi sm8ps
Do you have more than one partition labeled  dCORE ? Are you sure you didn't label it  dCore ? Are labels case sensitive?

sm8ps:
Thanks for your thoughts, Rich! The list of labels as seen by ''blkid'' is printed out above. I have double- and triple-checked it. The only thing I could imagine is that "dC" is mistaken for "dCORE" as it starts with the same letters. Though that seems quite absurd, doesn't it?

Navigation

[0] Message Index

[#] Next page

[*] Previous page