Difference between pages "Usability Testing" and "Amd64-jaguar"

From Funtoo
(Difference between pages)
Jump to navigation Jump to search
 
 
Line 1: Line 1:
This page provides a place to document your install experiences, highlighting pain points so that they can be addressed in future versions of Funtoo Linux.
{{Subarch
|CPU Family=64-Bit AMD Processors
|subarch=amd64-jaguar
|CHOST=x86_64-pc-linux-gnu
|CFLAGS=-march=btver2 -O2 -pipe
|USE=mmx sse sse2 sse3 sse4 3dnow 3dnowext
|CPU Features=low-power
|Description=
}}
The '''amd64-jaguar''' (also called AMD Family 16h) subarch supports the  [[Wikipedia:Jaguar (microarchitecture)|AMD jaguar microarchitecture]], which is targeted at low-power devices, including notebooks, tablets and small form-factor desktops and servers. It is perhaps most well-known for being the microarchitecture used for the [[Wikipedia:Playstation 4|Playstation 4]] and [[Wikipedia:Xbox One|Xbox One]], which each use custom 8-core Jaguar APUs.
Socketed Jaguar APUs use the [[Wikipedia:AM1 Socket|AM1 socket]], and  [[Wikipedia:Socket_FT3|FT3 socket]] for mobile devices. G-series [[Wikipedia:System_on_a_chip|"system on a chip" (SoC)]] APUs are available for non-socketed devices such as tablets and embedded system boards.


== Daniel Robbins, ninja2, 12/24/2010 ==
Desktop Jaguar APUs include the [[Wikipedia:List_of_AMD_accelerated_processing_unit_microprocessors#.22Kabini.22.2C_.22Temash.22_.282013.2C_28_nm.29|Kabini A-series APUs and Temash E-series APUs]], such as the Athlon 5150 and 5350 APUs, and Sempron 2650 and 3850.


Installation of ninja2 (Dell R710) using rhel5-openvz-binaries kernel/modules/initrd .tbz2 (compiled on another machine using gcc-4.1.2) and GPT/GUID partitions. Use of binary kernel was successful although directing Portage to use the binary package was difficult - it wanted to find it inside a package repository rather than accept it directly from the command-line. Forgot to downgrade udev-160 to udev-146-r4 which resulted in a missing /etc/udev/rules.d/70-persistent-net.rules. Also didn't have brctl (bridge-utils) or ifenslave on the stage3 to allow me to set up the network correctly. Also ran into an issue with boot-update where I got the configuration wrong, because I used "kernel-[-v]" instead of "kernel[-v]". This could be a usability issue with the boot.conf syntax.
Amd64-jaguar subarches use the MOVBE instruction which is not available on amd64-bulldozer, amd64-piledriver or amd64-steamroller. They are thus not instruction-compatible with any of these subarches.
 
After getting the system booted, I ran into an issue with macaddr renaming - you can't rename a device to eth1 if eth1 already exists! So I realized the limitations of macaddr renaming using nameif (built in to the Funtoo Linux network configuration scripts.) After fixing 70-persistent-net.rules and thinking of ways we could have some kind of default assignment rather than the currently random approach, I rebooted, configured my network, firewall, OpenVZ using the masked vzctl-3.0.25-r2 -- without issue -- and had the system up and running. I found that "bc" is no longer installed by default (I thought it was) -- so I added it to the default Metro stage3. Only ~90K.
 
Possible usability improvements:
 
* document use of rhel5-openvz-binaries
* improve Portage's ability to install binary packages by having the .tbz2 specified on the command-line
* improve management of udev to either force downgrade or allow multiple versions to exist on the same system (this is becoming more appealing....)
* add bridge-utils to default stage3 (DONE)
* add ifenslave to default stage3
* add bc to default stage3 (DONE)
* integrate some scheme for logically ordering ethX devices when you have many on a machine
* look into improving boot-update configuration syntax to avoid "-[-v]" issues that can cause thorny config problems.
 
Successes:
 
* the test of rhel5-openvz-binaries tbz2 was successful overall. It worked, and saved a ton of effort.
* GPT/GUID partitioning worked fine.
* testing of vzctl-3.0.25-r2 (currently in testing) worked perfectly.
* install was relatively pain-free for a pro but still needs work.
 
[[Category:QA]]

Revision as of 07:03, December 20, 2014

This section lists the CPU-optimized Funtoo Linux builds currently available for download for amd64-jaguar.

No downloadable stage builds are currently available for this sub-architecture.

.

Architecture and Optimization

The following settings are applied to all stages for this subarch via Funtoo subarch profiles:

CHOSTx86_64-pc-linux-gnu
CFLAGS-march=btver2 -O2 -pipe


The amd64-jaguar (also called AMD Family 16h) subarch supports the AMD jaguar microarchitecture, which is targeted at low-power devices, including notebooks, tablets and small form-factor desktops and servers. It is perhaps most well-known for being the microarchitecture used for the Playstation 4 and Xbox One, which each use custom 8-core Jaguar APUs. Socketed Jaguar APUs use the AM1 socket, and FT3 socket for mobile devices. G-series "system on a chip" (SoC) APUs are available for non-socketed devices such as tablets and embedded system boards.

Desktop Jaguar APUs include the Kabini A-series APUs and Temash E-series APUs, such as the Athlon 5150 and 5350 APUs, and Sempron 2650 and 3850.

Amd64-jaguar subarches use the MOVBE instruction which is not available on amd64-bulldozer, amd64-piledriver or amd64-steamroller. They are thus not instruction-compatible with any of these subarches.

Retrieved from "https://www.funtoo.org/index.php?title=Usability_Testing&oldid=7592"