Tiny Core Base > Corepure64

Corepure64 v5.1rc1

<< < (2/3) > >>

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:

--- Quote from: coreplayer2 on November 25, 2013, 01:44:17 AM ---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: ---boot/
    extlinux/
    modules-3813.gz
    modules64-3813.gz
    rootfs-51rc1.gz
    rootfs64-51rc1.gz
    vmlinuz-3813
    vmlinuz64-3813

--- End code ---

 8)

--- End quote ---

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: ---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

--- End code ---


Contents of /boot :

--- Code: ---core.gz
modules64.gz
rootfs64.gz
vmlinuz
vmlinuz64
core.gz
--- End code ---

--- Code: ---
--- End code ---

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.


--- Quote ---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
--- End quote ---

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: ---KERNEL /boot/vmlinuz64
APPEND initrd= /boot/rootfs64.gz,/boot/modules64.gz [...]
--- End code ---



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

--- Quote ---Contents of /boot :
Code:

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

Code:
--- End quote ---

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

Navigation

[0] Message Index

[#] Next page

[*] Previous page