Corepure64 v5.1rc1

[Juanito]

The first "five series" of corepure64 is ready for testing.

The release takes the form of roots64.gz + modules64.gz + vmlinux64, modules64.gz and vmlinuz64 being common with the 32-bit version of core.

The release is designed to be in sync with core, hence starting at 5.1rc1.

The distribution files are available at:

http://tinycorelinux.net/5.x/x86_64/release_candidates/distribution_files/

Change log:
rc1
* Updated kernel to 3.8.13 with (u)efi boot enabled
* Updated eglibc to glibc-2.17
* Updated e2fsprogs base libs to 1.42.7
* Updated gcc base libs to 4.7.2
* Updated util-linux base libs to 2.23.1
* uses vmlinuz64 + rootfs64.gz + modules64.gz
* aterm, freetype, imlib2, jpeg and libpng factored out of Xlibs/Xprogs and will need to be downloaded as  extensions
* localhost.local domain added to /etc/hosts, /usr/bin/sethostname for avahi compatibility/libcups printing
* 50-udev-default.rules adjusted to allow rw access to /dev/rfkill

Notes:
* due to significant changes in Xlibs and Xprogs it is recommended to make these for deletion, reboot and re-download.
* due to significant changes from Xorg-7.6* to Xorg-7.7*  it is recommended to make these for deletion, reboot and re-download.
* due to the updates to libpng in particular, some corepure64-4.x gui extensions will not work in corepure64-5.x.
* Xorg-7.7 is now compiled against libxcb enabling gtk3
* Once 4.x extensions are confirmed working under 5.x they can be copied to the 5.x repo

Testing and feedback is welcomed

[Juanito]

Just in case anybody has problems setting up a boot loader for corepure64, here's a  grub2 example - note that modules64.gz and vmlinux64 are shared with the standard x86 release.

Code: [Select]

set default=0
set timeout=30

insmod ext2
search --no-floppy --fs-uuid --set=root 3916536c-ab5b-45f4-92de-a6b8af8ec630

menuentry "corepure64" {
  linux /boot/vmlinuz64 quiet noswap waitusb=10:UUID="3916536c-ab5b-45f4-92de-a6b8af8ec630" tce=UUID="3916536c-ab5b-45f4-92de-a6b8af8ec630" tz=GMT-4 blacklist=bcma blacklist=ssb blacklist=b43 text
  initrd /boot/rootfs64.gz /boot/modules64.gz
}

[Juanito]

..and a grub2-efi example:

Code: [Select]

loadfont unicode
insmod efi_gop
set gfxterm=auto
terminal_output gfxterm

search --no-floppy --fs-uuid --set=root f8422ac1-fef4-48ce-b79e-abce5a598e8a

menuentry "rootfspure64" {
  linux /boot/vmlinuz64 quiet noswap tce=UUID=f8422ac1-fef4-48ce-b79e-abce5a598e8a waitusb=10:UUID=f8422ac1-fef4-48ce-b79e-abce5a598e8a tz=GMT-4 blacklist=bcma blacklist=ssb blacklist=b43 text
  initrd /boot/rootfs64.gz /boot/modules64.gz
}

menuentry "rootfspure64_base" {
  linux /boot/vmlinuz64 quiet noswap tce=UUID=f8422ac1-fef4-48ce-b79e-abce5a598e8a waitusb=10:UUID=f8422ac1-fef4-48ce-b79e-abce5a598e8a tz=GMT-4 blacklist=bcma blacklist=ssb blacklist=b43 text base norestore
  initrd /boot/rootfs64.gz /boot/modules64.gz
}


[coreplayer2]

If it helps anyone using syslinux,  this is an extract of my extlinux.conf  showing pertinent info.

I've also attached the complete extlinux.conf file here in case anyone is looking to multi-boot core, core64 and corepure64 from the same partition, obviously each with their own onboot.lst file

Code: [Select]


LABEL Corepure64
MENU LABEL Corepure64
TEXT HELP

Boot Pure64 system
onbootpure64.lst
ENDTEXT
KERNEL /tce/boot/vmlinuz64-3813
APPEND initrd=/tce/boot/rootfs64-51rc1p.gz,/tce/boot/modules64-3813.gz loglevel=3 noswap lst=onbootpure64.lst tce=sda2/corepure64/tce opt=sda2 home=sda2


I took the liberty to rename some files as core, core64 and corepure64 (and previous versions of each) all reside in the same directory, forcing a rename to maintain my sanity.

[coreplayer2]

I like the idea of using common kernels and modules.  Now I can boot 3 systems, core (32), core64 and corepure64 with only 6 files (using combinations of common kernels & modules) instead of the 9 files it took previously

Showing the contents of my boot directory

Code: [Select]

boot/
    extlinux/
    modules-3813.gz
    modules64-3813.gz
    rootfs-51rc1.gz
    rootfs64-51rc1.gz
    vmlinuz-3813
    vmlinuz64-3813

 

[Juanito]

Perhaps worth mentioning that a separate tce/optional folder is required for corepure64 as the extensions are 64-bit though 

[coreplayer2]

Yes good point,   separate tce directories can be seen in the above extlinux config file   

[CaptBill]

I like the idea of using common kernels and modules.  Now I can boot 3 systems, core (32), core64 and corepure64 with only 6 files (using combinations of common kernels & modules) instead of the 9 files it took previously

Showing the contents of my boot directory

Code: [Select]

boot/
    extlinux/
    modules-3813.gz
    modules64-3813.gz
    rootfs-51rc1.gz
    rootfs64-51rc1.gz
    vmlinuz-3813
    vmlinuz64-3813

 

Hi,
I have set my iso just like you describe and am recieving "Corrupt kernal image" message. Do I need the UUID somewhere or something? Microcore loads fine. Using syslinux.

Code: [Select]

display boot.msg
default microcore

LABEL Corepure64
MENU LABEL Corepure64
TEXT HELP

Boot Pure64 system
onbootpure64.lst
ENDTEXT
KERNEL /boot/vmlinuz64
APPEND initrd= /boot/rootfs64.gz,/tce/boot/modules64.gz loglevel=3 noswap lst=onbootpure64.lst tce=sda4/Core64/tce opt=sda4 home=sda4

label microcore
kernel /boot/vmlinuz
initrd /boot/core.gz
append loglevel=3

label mc
kernel /boot/vmlinuz
append initrd=/boot/core.gz loglevel=3
implicit 0
prompt 1
timeout 300
F1 boot.msg
F2 f2
F3 f3
F4 f4


Contents of /boot :

Code: [Select]

core.gz
modules64.gz
rootfs64.gz
vmlinuz
vmlinuz64
core.gz

Code: [Select]

[coreplayer2]

Multi-boot can be fun right?

It's important to be extra careful with path's and naming of files in the extlinux.conf file.

KERNEL /boot/vmlinuz64
APPEND initrd= /boot/rootfs64.gz,/tce/boot/modules64.gz loglevel=3 noswap lst=onbootpure64.lst tce=sda4/Core64/tce opt=sda4 home=sda4

the paths most likely do not match the actual locations of vmlinuz64, rootfs64.gz & modules64.gz.   I suspect these files are co-located with your 32bit version core.gz and vmlinuz in /boot as indicated above? then Perhaps

Code: [Select]

KERNEL /boot/vmlinuz64
APPEND initrd= /boot/rootfs64.gz,/boot/modules64.gz [...]


Also there are two core.gz files in your above list??   

Contents of /boot :
Code: [Select]

core.gz
modules64.gz
rootfs64.gz
vmlinuz
vmlinuz64
core.gz

Code: [Select]

Also 5.1rc1 is no longer current,  5.1 has been released.

[CaptBill]

Yes, I botched the label entry ("/tce/boot" should have been "/boot") ,as you noted. Fixed that. That was a typo with the two core.gz's .

Still same issue. "microcore" and "mc" boot fine. I am burning this to cd, I should mention. Any ideas?

Thanks

[CaptBill]

Yes, I botched the label entry ("/tce/boot" should have been "/boot") ,as you noted. Fixed that. That was a typo with the two core.gz's .

Still same issue. "microcore" and "mc" boot fine. I am burning this to cd, I should mention. Any ideas?

Thanks

Do i need to supply the onboot.lst in the /Core64 directory perhaps?

[coreplayer2]

onboot.lst should be in their respective /corepure64/tce  /corex86/tce directories I believe (is how I run it)


How does that work out for you?

[Juanito]

Since the 5.1 release candidate phase is finished, topic locked