dCore-wily and dCore-jessie crashing on bootup...

[FuzzyQuills]

In both cases, the log looked like this:

Code: [Select]

Booting dCore-jessie:2016.02.27.21.36
Running Linux Kernel 3.16.6-tinycore
Checking boot options...Done.
Starting udev daemon for hotplug support...Done.
Scanning hard disk partitions to create /etc/fstab
Setting Language to C Done.
Possible swap partition(s) enabled.
Loading Extensions... Segmentation fault
Done.
Setting keymap to usSegnemtation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
I have not had this before with dCore-wheezy... could it be because it's detecting my current dCore install?
Maybe i used the dd command with the iso image wrong? (perhaps an incorrect block size?)

Any help would be appreciated as otherwise, using wheezy, I'm stuck on glibc 2.13...

[Jason W]

You mention glibc, are you loading any SCEs that contain files from another glibc version since that is where the segfault occurs?

[Jason W]

Is this a USB boot, were you able to import extensions on a previous session, what SCEs are being loaded, what are the boot codes being used?  With more information we can help find the issue.

[FuzzyQuills]

what I am trying to boot on the target machine is a USB drive with the ISO image directly dd'ed to it. No modifications have been made.

And I have a new development: trying the USB in another machine (my main computer) works fine and doesn't crash...
The only real difference between the two machines is that one of them is only 32-bit. Is there a chance dCore's only 64-bit capable?

That, and I used all default boot options (just hit enter at "boot:" prompt)

[Jason W]

dCore is definitely not only 64 bit compatible.

[Jason W]

So booting dCore on another machine by usb does not crash? 

[Jason W]

Is there a default named tce directory on that main machine that may have SCE extensions from a different dCore port?  if so, it would be detected and used if no other tce directory is specified.  I always name my tce directories for each dCore port I use and specify it in the boot code, like /mnt/sda2/dCore-wily so each dCore I boot is sure to use the right one.