No edit summary |
|||
| Line 84: | Line 84: | ||
- systems with less than 512mb ram - using vnc you may get OOM during package install. you will need to either do a default install or select a smaller package set<BR> | - systems with less than 512mb ram - using vnc you may get OOM during package install. you will need to either do a default install or select a smaller package set<BR> | ||
- repo issues when installing - There repos are not laid out exactly as anaconda wants when doing a netinstall. you can pass repo="path to mirror" or fix up in the gui<BR> | - repo issues when installing - There repos are not laid out exactly as anaconda wants when doing a netinstall. you can pass repo="path to mirror" or fix up in the gui<BR> | ||
=== rawhide === | === rawhide === | ||
Revision as of 08:58, 17 May 2015
Fedora SPARC
Architecture Maintainer Team
- Tom "spot" Callaway (team lead) (Fedora Account: spot)
- Dennis Gilmore (Fedora Account: ausil)
- Patrick "Jima" Laughton (Fedora Account: jima)
- PeterJones (Fedora Account: pjones)
Interested in joining the SPARC team? Contact the team lead .
Contact Info
- IRC: #fedora-sparc on irc.freenode.net
- Mailing List: sparc@lists.fedoraproject.org
- Regular IRC Meeting: Fedora SPARC will have regular IRC meetings on TBD.
History
Fedora SPARC started out as the Aurora SPARC Linux Project , when Red Hat stopped support for SPARC with Red Hat Linux 6.2. Fedora SPARC is the continuation of the Aurora efforts, in an official capacity as part of the Fedora Project.
SPARC LiNUX docs
CPU and Architecture Target
The baseline SPARC CPU architecture that we have chosen to support is sparcv9 in 32bit. Although Aurora (the predecessor to Fedora SPARC) supported sparcv7 as its baseline, poor upstream kernel support for sparc(32-bit) combined with significant optimization gain make sparcv9 a much more viable target. Unfortunately, this means that sparc32 systems (anything sun4c, sun4d, sun4m and LEON) will not work with Fedora SPARC.
It is possible that we will release a sparcv7 baselined tree again at some point, either under the Aurora name or as a Fedora SPARC release.
Sandbox Systems
Currently, there are no Fedora SPARC sandbox systems available.
Buildservers
Koji Instance
The Sparc Koji instance can be found at http://sparc.koji.fedoraproject.org/koji
Build Servers
| daedalus | Sun Fire T1000, 32 1ghz thread Niagara 1 CPU, 2x73gb sas drives, 16gb ram. |
| korolev | Sun Fire T2000, 32 1ghz thread Niagara 1 CPU, 2x73gb sas drives, 8gb ram, 253gb T3 StorEdge shelf. |
Database Server
| vala | Netra X1, 500mhz Ultrasparc IIi, 2x80gb ide drives, 2gb ram. |
Tracker Bug
If excluding sparc architectures you need to make the bug block F-ExcludeArch-SPARC
to see whats currently blocking visit Bugzilla
Releases
Fedora SPARC 12
- Beta ISOs are available here: http://secondary.fedoraproject.org/pub/fedora-secondary/archive/releases/test/12-Beta/sparc/iso/
- Beta FILES are available here: http://secondary.fedoraproject.org/pub/fedora-secondary/archive/releases/test/12-Beta/sparc/os/
- Beta UPDATES are available here: http://secondary.fedoraproject.org/pub/fedora-secondary/archive/updates/12/
Known issues:
- SBUS devices do not autodetect
- serial console install - By default the serial console is not enabled. To install with only a serial console you just boot into single user mode with a serial console by adding "console=ttyS0,9600 single" to the SILO boot prompt, At the '# ' prompt edit /boot/silo.conf to remove the rhgb and add "console=ttyS0,9600". Then copy /etc/event.d/tty1 /etc/event.d/serconsole and edit serconsole to use ttyS0 in place of tty1. You then must edit /etc/securetty to include ttyS0 for pam to accept the root password on the serial console. After doing this 'exit' will boot multi-user and you should see a login prompt on the serial console. If you do not do these steps, the multi-user boot will appear to hang.
- serial console install - to do any customisation at all you need to use vnc
- sunblade and Fire systems with qlogic hba's for primary storage - Make sure that you do a graphical install (vnc or local X) or kickstart and include "hardware support" this is so that you have the firmware for your primary storage
- install blowing up at partitioning - parted doesnt seem to like old parted disk labels. in rescue mode "dd if=/dev/zero of=/dev/sdX bs=512 count=2" where X == the value of each disk (e.g. /dev/sda)
- partitioning is fragile - simple partitioning works fine more complicated setups might require you to manually use parted to setup the partitioning you want and then choosing custom partitiing and allocate as you need to
- systems with less than 512mb ram - using vnc you may get OOM during package install. you will need to either do a default install or select a smaller package set
- repo issues when installing - There repos are not laid out exactly as anaconda wants when doing a netinstall. you can pass repo="path to mirror" or fix up in the gui