DOCSLIB.ORG

Using Linuxbios to Liberate Embedded X86 Processors

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Breaking the Chains—Using LinuxBIOS to Liberate Embedded x86 Processors Jordan H. Crouse Marc E. Jones Ronald G. Minnich Advanced Micro Devices, Inc. Advanced Micro Devices, Inc. Sandia National Labs [email protected] [email protected] Abstract systems have abandoned the BIOS hardware interfaces and access the hardware directly. The desktop computer While x86 processors are an attractive option for embed- focus of the traditional BIOS model frustrates embed- ded designs, many embedded developers avoid them be- ded systems designers and developers, who struggle to cause x86-based systems remain dependent on a legacy get a BIOS that embraces their unique platforms. Due to BIOS ROM to set up the system. LinuxBIOS is an the very specific requirements for system boot time and open source solution that replaces the proprietary BIOS resource usage, it is difficult to meet embedded stan- ROMs with a light-weight loader. LinuxBIOS frees the dards with a BIOS designed for two decades of desktop developer from complex CPU and chipset initialization computers. and allows a variety of payloads to be loaded, including The LinuxBIOS project exists to address legacy BIOS the Linux kernel itself. issues. It is licenced under the GNU Public License This presentation reviews the journey of the AMD (GPL) to promote a transparent and open loader. Lin- GeodeTM processors and chipset as they were integrated uxBIOS provides CPU and chipset initialization for x86, into LinuxBIOS to become the centerpoint of the One x86_64, and Alpha systems and allows the flexibility to Laptop Per Child (OLPC) project. We also discuss how load and run any number of different payloads. embedded developers can take advantage of the Lin- This paper discusses the development and use of Lin- uxBIOS environment for their own x86-based projects. uxBIOS for embedded x86 platforms based on AMD Geode processors. The first section examines the history 1 Introduction of LinuxBIOS and the AMD Geode processors. The next section moves into detail about the system initial- Ever since the x86 Personal Computer (PC) architec- ization process. The final section discusses integrating ture was introduced in 1981, it has been accompanied by payloads with the LinuxBIOS firmware. bootstrap code known as the Basic Input/Output System (BIOS) that executes a Power On Self Test (POST). Al- 2 History most every year since the PC’s introduction, hardware and operating system features have increased in com- “History is a guide to navigation in perilous plexity. Each new feature adds complexity to the BIOS, times. History is who we are and why we are which must maintain compatibility with older operating the way we are.” systems and yet also provide support for new ones. The —David C. McCullough end result is a convoluted and cryptic combination of old standards (such as software interrupts for accessing the 2.1 LinuxBIOS History display and storage devices) and new standards (such as Advanced Configuration and Power Interface (ACPI)). Ron Minnich started the LinuxBIOS project at Los Almost all BIOS implementations are proprietary and Alamos National Lab (LANL) in September 1999 to ad- many Open Source developers are in conflict with what dress problems caused by the PC BIOS in large clusters. is perceived to generally be a “black magic” box. Due to The team agreed that the ideal PC cluster node would the arcane nature of the BIOS, most modern operating have the following features: • 103 • 104 • Breaking the Chains—Using LinuxBIOS to Liberate Embedded x86 Processors • Boot directly into an OS from non-volatile RAM; GX processor based LinuxBIOS loader, originally uti- lizing a Linux-as-bootloader payload. This later tran- • Configure only the network interfaces; sitioned to OpenFirmware after it became available in the middle of 2006. In 2007, AMD Geode LX proces- • Connect to a control node using any working net- sor support was added to the loader, making it a freely work interface; available reference BIOS design for interested develop- ers of other AMD Geode solutions. • Take action only at the direction of the control node. 2.2 AMD Geode History R At that time, the LANL team felt that Linux did a bet- The AMD Geode processor is the offspring of the Me- ter job of running the hardware than the PC BIOS. Their diaGX processor released by Cyrix in 1997. The Medi- concept was to use a simple hardware bootstrap to load aGX saved total system cost by embedding a graphics a small Linux kernel from flash to memory. Leveraging engine that used one of the first Unified Memory Ar- work from the OpenBIOS project, the LinuxBIOS team chitecture (UMA) implementations. It also featured an booted an Intel L440GX+ motherboard after approxi- integrated northbridge memory controller and Sound- mately six months of development. Early on, the team Blaster emulation in the CPU. The MediaGX broke the decided that assembly code would not be the future of sub-$1000, sub-$500, and sub-$200 price barrier on the LinuxBIOS. OpenBIOS was disregarded because it was Compaq Presario 2100 in 1996 and 1997. In 1997, based on a great deal of assembly code and a difficult-to- Cyrix was purchased by National Semiconductor, who master build structure. The team found a simple loader renamed the MediaGX line to Geode. National Semi- from STMicroelectronics called STPC BIOS that was conductor released the Geode GX2 (today, just called written in C and available to be open sourced, so it be- the GX) and CS5535 companion chip in 2002. In 2003, 1 came the basis for the first version of LinuxBIOS. the Geode division was sold to AMD. AMD focused heavily on power, price, and performance, and in 2005 In 2000, Linux NetworX and Linux Labs joined the released the AMD Geode LX [email protected] processor and effort. The LinuxBIOS team added Symmetric Multi- CS5536 companion chip, with the LX [email protected] pro- ple Processor (SMP) support, an Alpha port, and cre- cessor following in 2007. ated the first 13-node LinuxBIOS-based Supercomput- ing Clusters. Since 2001, the team has added devel- The AMD Geode GX and LX processors support the opers and they continue to port to new platforms, in- i586 instruction set, along with MMX and 3DNow!TM TM TM cluding AMD Opteron processor- and AMD Athlon extensions. The LX features a 64K instruction and a processor-based platforms. Interestingly enough, Lin- 64K data L1 cache and 128K L2 cache. Both proces- uxBIOS was originally designed for clusters, yet Lin- sors have on-board 2D graphics and video accelerators. uxBIOS for non-cluster platforms far exceeds the clus- The LX adds an on-board AES engine and true random ter use. number generator. The CS5536 companion chip pro- vides southbridge capabilities: IDE, USB 2.0, SMBus, In 2005, some current and past members of the MIT Me- AC97, timers, GPIO pins, and legacy x86 peripherals. dia Lab joined together to create the One Laptop Per Child (OLPC) program, dedicated to making a low-cost laptop for educational projects around the globe. The 3 Geode LinuxBIOS ROM image OLPC team designed an x86 platform that incorporates an AMD Geode solution. As low price and open tech- While the entire image is known as LinuxBIOS, it is nology were part of the core requirements for the lap- constructed of individual pieces that work together. An top, the designers decided to use a royalty-free open AMD Geode LinuxBIOS ROM image is made up of 2 source BIOS solution, ultimately choosing LinuxBIOS. three main binary pieces: The first two board revisions included the AMD Geode TM • LinuxBIOS Loader: system initialization code; 1Version 2 started after the addition of Hypertransport technol- ogy support changed the device model enough to warrant a version 2OLPC also adds additional binary code for its embedded con- bump. troller. 2007 Linux Symposium, Volume One • 105 • VSA2: the AMD Geode proccessor’s System Man- linuxbios/src agement Interrupt (SMI) handler; |-- cpu |-- amd • Payload: the image or program to be loaded to boot |-- model_gx2 the OS. |-- model_lx 3.1 LinuxBIOS Architecture The mainboard/ directory contains platform-specific configuration and code. The platform Config.lb file contains the PCI device configuration and IRQ routing. LinuxBIOS version 2 is structured to support multiple This directory also contains the source file compiled by motherboards, CPUs, and chipsets. The overall plat- ROMCC. form configuration is described in Config.lb in the mainboard directory. The Config.lb file contains important information like what CPU architecture to linuxbios/src build for, what PCI devices and slots are present, and |-- mainboard where code should be addressed. The mainboard also |-- amd contains the pre-DRAM initialization file, auto.c. |-- norwich ROMCC compiles auto.c and generates a stackless |-- olpc assembly code file, auto.inc. The use of ROMCC |-- rev_a works well for small sections of simple C code, but for complicated memory controller initialization, there are (Note: ‘Norwich’ is the code name for an AMD Geode some issues with code size and C variable-to-register development platform). space conversion. The source code in northbridge/ includes memory To work around the ROMCC issues, Yinghai Lu of initialization and the PCI bridge 0 configuration and ini- AMD developed support for the AMD64 architecture’s tialization. In the AMD Geode processor’s architecture, Cache-as-RAM (CAR) feature [1]. Compiled C code the northbridge is integrated into the CPU, so the direc- makes heavy use of the stack. Only a few lines of assem- tory name is the same as the CPU. bly code are needed to set up the CPU cache controller to be used as temporary storage for the stack. All the pre-DRAM initialization (including memory initializa- linuxbios/src tion) is compiled as normal C code.
Recommended publications
  • Implementation of a Linux Kernel Module to Stress Test Memory Subsystems in X86 Architecture

    Implementation of a Linux Kernel Module to Stress Test Memory Subsystems in X86 Architecture

    Robert Taylor Implementation of a Linux Kernel Module to Stress Test Memory Subsystems in x86 Architecture Helsinki Metropolia University of Applied Sciences Bachelor of Engineering Information Technology 27th February 2011 Abstract Author(s) Robert Taylor Title Implementation of a Linux Kernel Module to Stress Test Memory Subsystems in x86 Architecture Number of Pages 36 pages Date 27 February 2011 Degree Bachelor of Engineering Degree Programme Information Technology Specialisation option Software Engineering Antti Piironen, Dr (Project Supervisor) Instructors Janne Kilpelainen (Hardware Supervisor, NSN) Antti Virtaniemi (Software Supervisor, NSN) The aim of the project was to implement software which would stress test the memory subsystem of x86 based hardware for Nokia Siemens Networks (NSN). The software was to be used in the validation process of memory components during hardware develop- ment. NSN used a number of software tools during this process. However, none met all their requirements and a custom piece of software was required. NSN produced a detailed requirements specification which formed the basis of the project. The requirements left the implementation method open to the developer. After analysing the requirements document, a feasibility study was undertaken to determine the most fitting method of implementation. The feasibility study involved detailed discussions with senior engineers and architects within both the hardware and software fields at NSN. The study concluded that a Linux kernel module met the criteria best. The software was successfully implemented as a kernel module and met the majority of the requirements set by NSN. The software is currently in use at NSN and is being actively updated and maintained.
  • DAY ONE: Vsrx on KVM Verma & Kat - and Saves Tme Saves and Juniper Techlibrary Juniper Writen Writen in Tandem with the Juniper

    DAY ONE: Vsrx on KVM Verma & Kat - and Saves Tme Saves and Juniper Techlibrary Juniper Writen Writen in Tandem with the Juniper

    DAY ONE: vSRX on KVM Day One: vSRX on KVM is for network administrators, network architects, or engineers in- terested in quickly startng to use the Juniper Networks vSRX Virtual Firewall. Any tme you ONE: DAY need to design and test diferent topology use cases, train yourself or others, or even practce DAY ONE: vSRX on KVM certfcaton exams, this book covers such usage with step-by-step instructons and practcal examples. vSRX ON KVM Day One: vSRX on KVM requires Basic networking knowledge and a general understanding of the TCP/IP protocol suite, Linux systems, and Ubuntu. Writen in tandem with the Juniper vSRX documentaton, it curates links and tutorials with the Juniper TechLiBrary and saves tme for vSRX users by coordinatng deployment steps with the TechLibrary’s archives. Learn how to deploy vSRX instances today! IT’S DAY ONE AND YOU HAVE A JOB TO DO, SO LEARN HOW TO: Confgure the vSRX in a KVM environment Install vSRX’s prerequisite packages and confgure and deploy an instance of vSRX on KVM. and build lab topologies on day one. Create a single instance topology and then a mult-device topology using two vSRX instances. Design topologies for diferent use cases. Complete the three challenge topologies. Troubleshoot vSRX operatons. Verma & Kat ISBN 978-1941441893 5 1 6 0 0 By Rahul Verma & Madhavi Kat Juniper Networks Books are focused on network reliaBility and efficiency. Peruse the complete liBrary at www.juniper.net/books. 9 781941 441893 DAY ONE: vSRX on KVM Day One: vSRX on KVM is for network administrators, network architects, or engineers in- terested in quickly startng to use the Juniper Networks vSRX Virtual Firewall.
  • Proceedings of the Linux Symposium

    Proceedings of the Linux Symposium

    Proceedings of the Linux Symposium Volume One June 27th–30th, 2007 Ottawa, Ontario Canada Contents The Price of Safety: Evaluating IOMMU Performance 9 Ben-Yehuda, Xenidis, Mostrows, Rister, Bruemmer, Van Doorn Linux on Cell Broadband Engine status update 21 Arnd Bergmann Linux Kernel Debugging on Google-sized clusters 29 M. Bligh, M. Desnoyers, & R. Schultz Ltrace Internals 41 Rodrigo Rubira Branco Evaluating effects of cache memory compression on embedded systems 53 Anderson Briglia, Allan Bezerra, Leonid Moiseichuk, & Nitin Gupta ACPI in Linux – Myths vs. Reality 65 Len Brown Cool Hand Linux – Handheld Thermal Extensions 75 Len Brown Asynchronous System Calls 81 Zach Brown Frysk 1, Kernel 0? 87 Andrew Cagney Keeping Kernel Performance from Regressions 93 T. Chen, L. Ananiev, and A. Tikhonov Breaking the Chains—Using LinuxBIOS to Liberate Embedded x86 Processors 103 J. Crouse, M. Jones, & R. Minnich GANESHA, a multi-usage with large cache NFSv4 server 113 P. Deniel, T. Leibovici, & J.-C. Lafoucrière Why Virtualization Fragmentation Sucks 125 Justin M. Forbes A New Network File System is Born: Comparison of SMB2, CIFS, and NFS 131 Steven French Supporting the Allocation of Large Contiguous Regions of Memory 141 Mel Gorman Kernel Scalability—Expanding the Horizon Beyond Fine Grain Locks 153 Corey Gough, Suresh Siddha, & Ken Chen Kdump: Smarter, Easier, Trustier 167 Vivek Goyal Using KVM to run Xen guests without Xen 179 R.A. Harper, A.N. Aliguori & M.D. Day Djprobe—Kernel probing with the smallest overhead 189 M. Hiramatsu and S. Oshima Desktop integration of Bluetooth 201 Marcel Holtmann How virtualization makes power management different 205 Yu Ke Ptrace, Utrace, Uprobes: Lightweight, Dynamic Tracing of User Apps 215 J.
  • QEMU Interface Introspection: from Hacks to Solutions

    QEMU Interface Introspection: from Hacks to Solutions

    QEMU interface introspection: From hacks to solutions Markus Armbruster <[email protected]> KVM Forum 2015 Part I What’s the problem? Interfacing with QEMU QEMU provides interfaces QMP Monitor Command line to management applications like libvirt QEMU evolves rapidly Many interface versions Our command line is big In v2.4: 139 total options -14 deprecated -2 internal use 123 supported options 0.57kg If I had a coin for each of them. It’s big: output of -help QEMU emulator version 2.3.93, Copyright (c) 2003-2008 Fabrice Bellard -alt-grab use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt) configure a network backend to connect to another network -incoming rdma:host:port[,ipv4][,ipv6] usage: upstream-qemu [options] [disk_image] -ctrl-grab use Right-Ctrl to grab mouse (instead of Ctrl-Alt) using an UDP tunnel -incoming unix:socketpath -no-quit disable SDL window close capability -netdev vhost-user,id=str,chardev=dev[,vhostforce=on|off] prepare for incoming migration, listen on ’disk_image’ is a raw hard disk image for IDE hard disk 0 -sdl enable SDL configure a vhost-user network, backed by a chardev ’dev’ specified protocol and socket address -spice [port=port][,tls-port=secured-port][,x509-dir=<dir>] -netdev hubport,id=str,hubid=n -incoming fd:fd Standard options: [,x509-key-file=<file>][,x509-key-password=<file>] configure a hub port on QEMU VLAN ’n’ -incoming exec:cmdline -h or -help display this help and exit [,x509-cert-file=<file>][,x509-cacert-file=<file>] -net nic[,vlan=n][,macaddr=mac][,model=type][,name=str][,addr=str][,vectors=v]
  • Geode™ Gxm Processor Integrated X86 Solution with MMX Support

    Geode™ Gxm Processor Integrated X86 Solution with MMX Support

    Geode™ GXm Processor Integrated x86 Solution with MMX Support April 2000 Geode™ GXm Processor Integrated x86 Solution with MMX Support General Description The National Semiconductor® Geode™ GXm processor graphics accelerator provides pixel processing and ren- is an advanced 32-bit x86 compatible processor offering dering functions. high performance, fully accelerated 2D graphics, a 64-bit A separate on-chip video buffer enables >30 fps MPEG1 synchronous DRAM controller and a PCI bus controller, video playback when used together with the CS5530 I/O all on a single chip that is compatible with Intel’s MMX companion chip. Graphics and system memory accesses technology. are supported by a tightly-coupled synchronous DRAM The GXm processor core is a proven design that offers (SDRAM) memory controller. This tightly coupled memory competitive CPU performance. It has integer and floating subsystem eliminates the need for an external L2 cache. point execution units that are based on sixth-generation The GXm processor includes Virtual System Architec- technology. The integer core contains a single, six-stage ture® (VSA™ technology) enabling XpressGRAPHICS execution pipeline and offers advanced features such as and XpressAUDIO subsystems as well as generic emula- operand forwarding, branch target buffers, and extensive tion capabilities. Software handler routines for the Xpress- write buffering. A 16 KB write-back L1 cache is accessed GRAPHICS and XpressAUDIO subsystems can be in a unique fashion that eliminates pipeline stalls to fetch included in the BIOS and provide compatible VGA and 16- operands that hit in the cache. bit industry standard audio emulation. XpressAUDIO tech- In addition to the advanced CPU features, the GXm pro- nology eliminates much of the hardware traditionally asso- cessor integrates a host of functions which are typically ciated with audio functions.
  • How Microprocessors Work E 1 of 64 ZM

    How Microprocessors Work E 1 of 64 ZM

    How Microprocessors Work e 1 of 64 ZM How Microprocessors Work ZAHIDMEHBOOB +923215020706 [email protected] 2003 BS(IT) PRESTION UNIVERSITY How Microprocessors Work The computer you are using to read this page uses a microprocessor to do its work. The microprocessor is the heart of any normal computer, whether it is a desktop machine, a server or a laptop. The microprocessor you are using might be a Pentium, a K6, a PowerPC, a Sparc or any of the many other brands and types of microprocessors, but they all do approximately the same thing in approximately the same way. If you have ever wondered what the microprocessor in your computer is doing, or if you have ever wondered about the differences between types of microprocessors, then read on. Microprocessor History A microprocessor -- also known as a CPU or central processing unit -- is a complete computation engine that is fabricated on a single chip. The first microprocessor was the Intel [email protected] +923215020706 (2003) How Microprocessors Work e 2 of 64 ZM 4004, introduced in 1971. The 4004 was not very powerful -- all it could do was add and subtract, and it could only do that 4 bits at a time. But it was amazing that everything was on one chip. Prior to the 4004, engineers built computers either from collections of chips or from discrete components (transistors wired one at a time). The 4004 powered one of the first portable electronic calculators. The first microprocessor to make it into a home computer was the Intel 8080, a complete 8- bit computer on one chip, introduced in 1974.
  • MICROPROCESSOR REPORT the INSIDERS’ GUIDE to MICROPROCESSOR HARDWARE Slot Vs

    MICROPROCESSOR REPORT the INSIDERS’ GUIDE to MICROPROCESSOR HARDWARE Slot Vs

    VOLUME 12, NUMBER 1 JANUARY 26, 1998 MICROPROCESSOR REPORT THE INSIDERS’ GUIDE TO MICROPROCESSOR HARDWARE Slot vs. Socket Battle Heats Up Intel Prepares for Transition as Competitors Boost Socket 7 A A look Look by Michael Slater ship as many parts as they hoped, especially at the highest backBack clock speeds where profits are much greater. The past year has brought a great deal The shift to 0.25-micron technology will be central to of change to the x86 microprocessor 1998’s CPU developments. Intel began shipping 0.25-micron A market, with Intel, AMD, and Cyrix processors in 3Q97; AMD followed late in 1997, IDT plans to LookA look replacing virtually their entire product join in by mid-98, and Cyrix expects to catch up in 3Q98. Ahead ahead lines with new devices. But despite high The more advanced process technology will cut power con- hopes, AMD and Cyrix struggled in vain for profits. The sumption, allowing sixth-generation CPUs to be used in financial contrast is stark: in 1997, Intel earned a record notebook systems. The smaller die sizes will enable higher $6.9 billion in net profit, while AMD lost $21 million for the production volumes and make it possible to integrate an L2 year and Cyrix lost $6 million in the six months before it was cache on the CPU chip. acquired by National. New entrant IDT added another com- The processors from Intel’s challengers have lagged in petitor to the mix but hasn’t shipped enough products to floating-point and MMX performance, which the vendors become a significant force.
  • 2018 Annual Report on Form 10-K

    2018 Annual Report on Form 10-K

    2018 ANNUAL REPORT ON FORM 10-K MARCH 2019 DEAR SHAREHOLDERS: From the industry’s first 1GHz CPU to the world’s first GPU delivering a teraflop of computing power, AMD has always stood for pushing the boundaries of what is possible. A few years ago, we made several big bets to accelerate our pace of innovation, strengthen our execution, and enable AMD to deliver a leadership portfolio of computing and graphics processors capable of increasing our share of the $75 billion high-performance computing market. In 2018, we saw those bets begin to pay off as we delivered our second straight year of greater than 20% annual revenue growth and significantly improved our gross margin and profitability from the previous year. REVENUE GROSS MARGIN % R&D INVESTMENT EXPENSE/REVENUE % $ Billions $ Billions $6.5B 38% $1.43B 34% $5.3B 34% 33% $4.3B $1.20B 23% $1.01B 31% 2016 2017 2018 2016 2017 2018 2016 2017 2018 2016 2017 2018 Added $2.2B in revenue Significantly improved gross Increased R&D by more than Significant improvement over the last 2 years margin over last 2 years based 40% over the last 2 years in OPEX leverage on new product portfolio Our newest Ryzen™, EPYC™ and datacenter GPU products contributed more than $1.2 billion of revenue in 2018 and helped us gain share across our priority markets. In 2018, we added 3.9% points of desktop processor unit share, 5.3% points of notebook processor unit share and met our goal of exiting the year with mid-single digit server processor market share.
  • Installing a Real-Time Linux Kernel for Dummies

    Installing a Real-Time Linux Kernel for Dummies

    Real-Time Linux for Dummies Jeroen de Best, Roel Merry DCT 2008.103 Eindhoven University of Technology Department of Mechanical Engineering Control Systems Technology group P.O. Box 513, WH -1.126 5600 MB Eindhoven, the Netherlands Phone: +31 40 247 42 27 Fax: +31 40 246 14 18 Email: [email protected], [email protected] Website: http://www.dct.tue.nl Eindhoven, January 5, 2009 Contents 1 Introduction 1 2 Installing a Linux distribution 3 2.1 Ubuntu 7.10 . .3 2.2 Mandriva 2008 ONE . .6 2.3 Knoppix 3.9 . 10 3 Installing a real-time kernel 17 3.1 Automatic (Ubuntu only) . 17 3.1.1 CPU Scaling Settings . 17 3.2 Manually . 18 3.2.1 Startup/shutdown problems . 25 4 EtherCAT for Unix 31 4.1 Build Sources . 38 4.1.1 Alternative timer in the EtherCAT Target . 40 5 TUeDACs 43 5.1 Download software . 43 5.2 Configure and build software . 44 5.3 Test program . 45 6 Miscellaneous 47 6.1 Installing ps2 and ps4 printers . 47 6.1.1 In Ubuntu 7.10 . 47 6.1.2 In Mandriva 2008 ONE . 47 6.2 Configure the internet connection . 48 6.3 Installing Matlab2007b for Unix . 49 6.4 Installing JAVA . 50 6.5 Installing SmartSVN . 50 6.6 Ubuntu 7.10, Gutsy Gibbon freezes every 10 minutes for approximately 10 sec 51 6.7 Installing Syntek Semicon DC1125 Driver . 52 Bibliography 55 A Menu.lst HP desktop computer DCT lab WH -1.13 57 i ii CONTENTS Chapter 1 Introduction This document describes the steps needed in order to obtain a real-time operating system based on a Linux distribution.
  • J7F3 Mini-ITX Motherboard Series

    J7F3 Mini-ITX Motherboard Series

    Mainboard Diagram J7F3 Mini-ITX Motherboard Series -SiS 741CX Northbridge + SiS 964 Southbridge Chipsets -Support Socket-462 AMD Geode NX processor -Support Front Side Bus 133MHz -Single Channel DDR2 400 Memory DIMM -Support 2 Serial ATA Devices with RAID 0, 1 -Support 2xAD Connector With Expansion Daughter-boards -Ethernet LAN Supported -AC’97 6 Channel Audio CODEC -VIA VT6307S IEEE1394a Controller for J7F3E -17 x 17CM Mini-ITX Form Factor Features and Benefits Support Socket 462 AMD Geode™ NX Processor The AMD Geode™ NX processor family gives product designers a wide range of options in low-power, high-performance processors. Based on Mobile AMD Athlon™ processor technology, AMD NX processors deliver superior computing performance for applications including thin-client, point-of-sale terminals, kiosks, high-end printers, and home media systems. AMD Geode Solutions have received new model numbers to better reflect total performance beyond just megahertz. This presentation of attributes gives designers greater understanding of the capabilities of AMD Geode Solutions. SiS 741CX Northbridge Chipset and SiS964 Southbridge Chipset The SiS741CX chipset can be combined with three different AMD Geode NX processors, including the AMD Geode™ NX 1250@6W processor*, AMD Geode™ NX 1500@6W processor** and AMD Geode™ NX 1750@14W processor***, enabling development of a wider variety of products for different market segments. The SiS741CX chipset supports the AMD Geode NX processor family, DDR266 front side bus, as well as high-speed DDR333 DRAM. Furthermore, the SiS741CX chipset incorporates SiS's revolutionary HyperStreaming™ Technology, which provides multiple divided pipelines for data, allows data to be sent concurrently, and separates data for easier memory retrieval, resulting in a remarkable reduction in latency versus traditional chipsets.
  • Multiboot Guide Booting Fedora and Other Operating Systems

    Multiboot Guide Booting Fedora and Other Operating Systems

    Fedora 23 Multiboot Guide Booting Fedora and other operating systems. Fedora Documentation Project Copyright © 2013 Fedora Project Contributors. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries. All other trademarks are the property of their respective owners.
  • Linux System Administration

    Linux System Administration

    Linux System Administration Jonathan Quick, Hartebeesthoek Radio Astronomy Observatory Ari Mujunen, Metsähovi Radio Observatory Linux Startup and Shutdown Managing Hard Disks, Partitions, Backups Rescuing a Failing PC / System Modifying Configuration Adding/Removing Packages 1 Goals Help you to understand how Linux starts up, keeps running, and shuts down Give confidence in dealing with hardware and software failures Give an overview of what you can configure and how Show you where to find more information when you need it 2 Basic Linux Concepts Linux Kernel Base monolithic kernel + loadable modules Gives standardized access to underlying hardware Linux System / "Distribution" Kernel + lots of software Adds both system and application level software to the system Background processes ("daemons") 3 Logging in as 'root' In order to do any system-wide changes you usually have to be logged in as 'root' You can change to a virtual console (Ctrl-Alt- F1) and login normally or use 'su -' 'root' can override all permissions, start and stop anything, erase hard drives,... So please be careful with disk names and similar! You can browse and check many (if not most of the) things as a normal user (like 'oper'). 4 Getting System Information ps axf, top; kill, kill -9 free df, mount netstat -an, ifconfig, route -n w, who cat /proc/cpuinfo (and others) 5 Linux PC-Level Startup PC ROM BIOS initializes hardware and boots a Master Boot Record (MBR) From a floppy, hard disk, CD-ROM, ... That MBR contains LILO, the Linux Loader