Corepure64 v5.1

[killerhippy]

I'm about to do the same with the 32 bit version...

works.

Now I can say, using the recipe from ibiblio which gives a basic TC X deskotop:

- works here with 32 bit version
- does not work here with 64 bit version

Therefore, I assume a wrong compilation, because I have installed the same packages.

If I do "ls tcv5.1/tce/optional > list1" and "ls tcv5.1-64/tce/optional > list2" and then diff "list1 list2" I get:

Code: [Select]

4a5
> Xorg-7.7-bin.tcz.dep
29a31,32
> gcc_libs.tcz
> gcc_libs.tcz.md5.txt
56a60
> libXcomposite.tcz.dep
105a110
> libXtst.tcz.dep
140a146,148
> openssh.tcz
> openssh.tcz.dep
> openssh.tcz.md5.txt

tcv5.1-64 has openssh so could get the Xorg.0.log. It has also the additional files you see above, the rest is the same.

Keyboard and mouse are connected via PS/2, maybe the 64 Bit version lacks PS/2 Support?

[Juanito]

All that is needed for a basic desktop in corepure64 is to download and load the Xorg-7.7, Xprogs, flwm and wbar extensions using tce-load.

You are not getting as far as the part where the mouse/keyboard drivers are loaded because you are missing other deps.

For some reason Xorg-7.7 and all of its deps are not loaded on your system.

From your latest Xorg log it looks like the glu extension is not loaded.

Could you try "tce-load -w Xorg-7.7" and check that the extension and all of its deps download.

[killerhippy]

I thought I did so by doing the same insallation procedure for the 32 and the 64 bit version.

I can do as you wish and check that /tmp/tcloop looks the same at both versions later...

[killerhippy]

All that is needed for a basic desktop in corepure64 is to download and load the Xorg-7.7, Xprogs, flwm and wbar extensions using tce-load.

I did so following the recipe, though i did not use core but rootfs + modules
I'll try core at both later..

For some reason Xorg-7.7 and all of its deps are not loaded on your system.

My inspection says the opposite.

From your latest Xorg log it looks like the glu extension is not loaded.

Despite glue is loaded and mounted!

Could you try "tce-load -w Xorg-7.7" and check that the extension and all of its deps download.

Says the same at 32 and 64 bit:
Xorg-7.7 is already downloaded.

I inspected loaded extensions from the live system by " mount > mounts.<bitversion>" - in the end I have got mounts.32 and mounts.64
I sed'ed out the leading "/dev/loop?? on " characters into a new file.
Then I sort'ed from the new file in a new file.

Diff at the sorted files gives:

Code: [Select]

diff mounts-32.sorted mounts-64.sorted
10a11
> /tmp/tcloop/gcc_libs type squashfs (ro,relatime)
51a53
> /tmp/tcloop/openssh type squashfs (ro,relatime)
65c67
< rootfs on / type rootfs (rw,relatime,size=3262392k,nr_inodes=216579)
---
> rootfs on / type rootfs (rw,relatime,size=3230892k,nr_inodes=447469)

This shows that both systems, 32 and 64 bit have the same loop mounted extensions.
The 64 bit has gcc_libs mounted but not the 32 bit for unknown reason.
I installed openssh at 64 bit, this show up at 64 bit but not at 32 bit. All ok.

Is this sufficient to you, or do you want me to do something else?

[killerhippy]

I think I have found the source of all evil 

I, well, don't understand the difference between /release_candidates/distribution_files/ and /release/distribution_files/ at http://tinycorelinux.net/5.x/x86_64/
Maybe you can explain?
And btw, I wonder why you don't give a md5sum for the kernel file?

Nevertheless, it has come out, that rootfs64 from http://tinycorelinux.net/5.x/x86_64/release/distribution_files/rootfs64.gz works and from http://tinycorelinux.net/5.x/x86_64/release_candidates/distribution_files/rootfs64.gz  does not.

Case solved.

[coreplayer2]

After release, I believe the intention is to use only files from  http://tinycorelinux.net/5.x/x86/release/

I think release candidates are normally pulled once release goes public, at least until candidates for a new potential release are available for testing.  In any case we should definitely not mix modules from release http://tinycorelinux.net/5.x/x86/release/  with any files from  http://tinycorelinux.net/5.x/x86/release_candidates/

I think you'll find instructions/notes from the announcement page helpful http://forum.tinycorelinux.net/index.php/topic,16293.0.html

Distribution files are for those who wish to build custom configurations.  There is no "core.gz" for x86_64 or corepure64, so you would need files from http://tinycorelinux.net/5.x/x86/release/distribution_files/  only.


From http://tinycorelinux.net/5.x/x86/release/distribution_files/  use
For x86_64 (with 32bit userspace)
rootfs.gz
modules64.gz
vmlinuz64

For x86_64 (corepure64)
rootfs64.gz
modules64.gz
vmlinuz64


Hope that's clearer

[Juanito]

In fact the files at http://repo.tinycorelinux.net/5.x/x86_64/release_candidates/ were outdated.

I've updated the files to 5.2rc1 and will try to remember to delete the files when there are no release candidates for testing in order to avoid confusion.

'Happy to hear that you got things working 

[Juanito]

In case it helps users try out corepure64, iso created at:

http://repo.tinycorelinux.net/5.x/x86_64/release/CorePure64-5.1.iso

[killerhippy]

Happy me indeed!

At this point want to say thank you for your good work. Don't mind about errors, they happen, all is human 

From my point of view, a "release" is a publication.
A "release candidate" then is a "to be released", right?
I didn't think about it until now.

Before I thought, a "relase candidate" is the newest version and so the "release" version was older - which isn't correct.