Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 279472 - SPARC install cd fails to boot
Summary: SPARC install cd fails to boot
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: InstallCD (show other bugs)
Hardware: Sparc Linux
: High normal (vote)
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-28 13:54 UTC by Chris Reffett (RETIRED)
Modified: 2009-08-24 20:37 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Reffett (RETIRED) gentoo-dev Security 2009-07-28 13:54:39 UTC
When booting from the most recent (20090727) SPARC64 minimal install cd, the boot fails at "Mounting squashfs filesystem" with the error "mount:mounting /dev/loop0 on /newroot/mnt/livecd fauled: Invalid argument   !!Failed to $1, falling back to the shell..." Running dmesg | tail reveals the line "SQUASHFS: Mounting a different endian SQUASHFS filesystem on loop0" I tried the previous autobuild, and that one didn't work either.
Reproducible: Always
Comment 1 Martin Müller - Sun Germany SE 2009-07-29 12:05:21 UTC
Same happened for me while booting a Logical Domain of the the install-sparc64-minimal-20090727.iso image, dmesg had no hint on what's going wrong.
Comment 2 Chris Reffett (RETIRED) gentoo-dev Security 2009-07-30 12:15:19 UTC
I tried the install cd on another SPARC box (a quad-CPU UltraSPARC-II), with the same results. Note that the first computer I used it with was an UltraSPARC-IIIi.
Comment 3 Jan Dirnberger 2009-08-17 12:49:18 UTC
Same here, but with newer install-image (20090803). Hardware is SunFire V100 (UltraSPARC IIi, 1GB RAM, "normal" IDE HDD and CDROM).
Comment 4 Jan Dirnberger 2009-08-17 13:25:58 UTC
Reproducable, also occuring with install-sparc64-minimal-20090706.iso
Comment 5 James Yoder 2009-08-24 20:32:48 UTC
This bug was caused by an incompatibility between the kernel version and squashfs 4 filesystem. It has been fixed as of the 8/17/2009 autobuild.