The Anatomy of the Modern Window Manager a Case Study in Developing a Novel Top-Level Reparenting List-Based Tiling Window Manager for X in an Agile Manner

Total Page:16

File Type:pdf, Size:1020Kb

The Anatomy of the Modern Window Manager a Case Study in Developing a Novel Top-Level Reparenting List-Based Tiling Window Manager for X in an Agile Manner Bachelor thesis Computing Science Radboud University The anatomy of the modern window manager A case study in developing a novel top-level reparenting list-based tiling window manager for X in an Agile manner Author: First supervisor/assessor: Max van Deurzen dr. Cynthia Kop s4581903 [email protected] Second supervisor: dr. Peter Achten [email protected] 2019 Abstract At the heart of the modern personal computer experience lies the desktop environment, an implemen- tation of the desktop metaphor comprising a variety of programs that together provide common graphical user interface components. Arguably the most complex and, in some systems, the most important com- ponent of the desktop environment, is the window manager. A window manager is system software that controls the placement and appearance of windows within a graphical user interface. In this thesis we describe the functioning of top-level window managers. We showcase what common features window managers may consist of, and what their interaction with other system software looks like. In doing so, we will discuss the X Window System[1], along with the Inter-Client Communication Conventions Manual[2] (ICCCM) and Extended Window Manager Hints[3] (EWMH), two standard protocols that define policy on top of the X Window System. Together, they form an environment that facilitates the interoperability between window managers and other, regular programs. As a proof of concept, we provide and discuss kranewm, a complete C++ implementation of an ICCCM and EWMH compliant top-level reparenting, tiling window manager, built on top of the X Window System, using Xlib as client-side programming library. With it, we illustrate the low-level functioning of modern top-level window management. Leading up to an extensive demonstration of the product, we review several Agile software development concepts that were applied throughout, before describing the process undergone to realize the implementation. Acknowledgements I would like to thank both of my supervisors, dr. Cynthia Kop and dr. Peter Achten, for guiding me through the research process, for the many incremental proofreads, and for the suggestions made during the development phase of kranewm. Contents 1 Introduction 4 2 Window Management 5 2.1 Windowing systems ...................................... 5 2.1.1 Graphical user interface ................................ 5 2.1.2 Display server ..................................... 5 2.1.3 Widget toolkits .................................... 6 2.2 The window manager ..................................... 6 2.2.1 Responsibilities .................................... 7 2.2.2 Stacking ........................................ 7 2.2.3 Tiling ......................................... 7 2.2.4 Compositing ...................................... 11 2.2.5 Reparenting ...................................... 12 3 The X Window System 14 3.1 History ............................................. 14 3.2 Client-server architecture ................................... 14 3.3 System model ......................................... 15 3.4 Core protocol ......................................... 15 3.5 Client-side libraries ....................................... 15 3.6 Graphical environment ..................................... 16 3.7 Resources and identifiers ................................... 17 3.8 Messages ............................................ 18 3.8.1 Events ......................................... 18 3.9 Color .............................................. 19 3.10 Graphics operations ...................................... 20 3.10.1 Images ......................................... 20 3.10.2 Text .......................................... 20 3.10.3 Exposures ....................................... 21 3.11 Fonts .............................................. 21 3.12 Input .............................................. 21 3.13 Properties and atoms ..................................... 23 3.14 The X window manager .................................... 24 3.15 Wayland ............................................ 25 3.15.1 Architecture ...................................... 25 4 Policy in X 27 4.1 ICCCM ............................................. 27 4.1.1 Client properties .................................... 28 4.1.2 Window manager properties ............................. 30 4.2 EWMH ............................................. 35 4.2.1 Non-ICCCM features ................................. 35 4.2.2 Root window protocol definitions ........................... 37 4.2.3 Client window protocol definitions .......................... 40 5 Agile Software Development 44 5.1 Agile Manifesto ........................................ 44 5.2 Extreme Programming .................................... 44 5.3 Personal Software Process ................................... 45 5.4 Personal XP .......................................... 46 6 Implementation Process 48 6.1 The planning game ...................................... 48 Max van Deurzen Page 1 of 79 Case Study in Top-Level Window Management Contents 6.2 Small releases ......................................... 49 6.3 Metaphor ........................................... 49 6.4 Simple design ......................................... 50 6.5 Testing ............................................. 50 6.6 Refactoring ........................................... 51 6.7 Pair programming ....................................... 51 6.8 Collective ownership ...................................... 51 6.9 Continuous integration .................................... 51 6.10 40-hour week ......................................... 52 6.11 On-site customer ....................................... 52 6.12 Coding standard ........................................ 52 7 Implementation Product 53 7.1 Design ............................................. 53 7.2 Reparenting .......................................... 53 7.3 Workspaces .......................................... 54 7.4 Sidebar and struts ....................................... 55 7.5 Key bindings .......................................... 56 7.6 Mouse bindings ........................................ 57 7.7 General usage ......................................... 57 7.7.1 Terminal ........................................ 57 7.7.2 Program launching .................................. 57 7.7.3 Closing clients ..................................... 57 7.8 Window states ......................................... 57 7.8.1 Floating state ..................................... 57 7.8.2 Fullscreen state .................................... 58 7.9 Window manipulation ..................................... 58 7.9.1 Inner-workspace focus movement ........................... 58 7.9.2 Inner-workspace window movement .......................... 59 7.9.3 Cross-workspace window movement ......................... 60 7.10 Layouts ............................................. 60 7.10.1 Floating mode ..................................... 60 7.10.2 Tile mode ....................................... 60 7.10.3 Stick mode ...................................... 60 7.10.4 Deck modes ...................................... 61 7.10.5 Grid mode ....................................... 61 7.10.6 Pillar mode ...................................... 62 7.10.7 Column mode ..................................... 62 7.10.8 Monocle mode ..................................... 62 7.10.9 Center mode ...................................... 63 7.11 Rules .............................................. 63 7.11.1 Centering ....................................... 64 7.11.2 Autoclosing ...................................... 64 7.11.3 Workspace hint blocking ............................... 64 7.12 Process jumping ........................................ 64 7.13 Marking ............................................ 65 7.14 Summary ............................................ 65 8 Related Work 66 9 Conclusions 67 A List-based Tiling Window Managers 71 A.1 wmii .............................................. 71 A.2 dwm .............................................. 72 A.3 awesome ............................................ 73 Max van Deurzen Page 2 of 79 Case Study in Top-Level Window Management Contents A.4 xmonad ............................................ 73 B Tree-based Tiling Window Managers 75 B.1 i3 ................................................ 75 B.2 bspwm ............................................. 76 B.3 herbstluftwm .......................................... 77 C X.Org Foundation Distribution 79 Max van Deurzen Page 3 of 79 Chapter 1 Introduction Windowing systems and window managers alike have date a particular kind of window manager to be assumed crucial roles in guiding the look and feel of running and thereby allows its users to swap out graphical user interfaces. In fact, without them, the the window manager if they see fit, facilitating cus- concept of a graphical user interface would not even tomizability. To make such customizability possible, exist. The windowing system allows for the draw- the X Window System does not define policy, only ing of graphical primitives to the screen, and creates mechanism. To ensure that applications are able to the notion of windows. Windows are presented on work well together and can communicate with the screen, and convey important information from ap- window manager, several standard protocols were plications to the user, but how are they to be ma- designed to define a layer of policy atop of the X nipulated? The windowing system merely provides
Recommended publications
  • R&S®BBA100 Broadband Amplifier Open
    R&S®BBA100 Broadband Amplifier Open Source Acknowledgment 5353.8300.00 – 01 /RL/1/EN 01.00 / Broadcasting 3575.4620.02 M: - T - PAD Open Source Acknowledgment R&S BBA100 Introduction Contents 1 Introduction ......................................................................................... 3 1.1 Disclaimer ..................................................................................................................... 3 1.2 How to obtain the source code .................................................................................. 3 2 Software packages ............................................................................. 4 3 Verbatim license texts ........................................................................ 7 3.1 Apache License 2.0 ..................................................................................................... 7 3.2 GNU Library General Public License, Version 2.0 (LGPL 2.0) ..............................10 3.3 Boost Software License ............................................................................................18 3.4 GNU General Public License, Version 2.0 (GPL 2.0) ..............................................18 3.5 GNU Lesser General Public License, Version 2.1 (LGPL 2.1) ...............................24 3.6 Mozilla Public License, Version 1.1 (MPL 1.1) ........................................................32 3.7 MIT ...............................................................................................................................40 3.8 JDOM License
    [Show full text]
  • Release Notes for X11R6.8.2 the X.Orgfoundation the Xfree86 Project, Inc
    Release Notes for X11R6.8.2 The X.OrgFoundation The XFree86 Project, Inc. 9February 2005 Abstract These release notes contains information about features and their status in the X.Org Foundation X11R6.8.2 release. It is based on the XFree86 4.4RC2 RELNOTES docu- ment published by The XFree86™ Project, Inc. Thereare significant updates and dif- ferences in the X.Orgrelease as noted below. 1. Introduction to the X11R6.8.2 Release The release numbering is based on the original MIT X numbering system. X11refers to the ver- sion of the network protocol that the X Window system is based on: Version 11was first released in 1988 and has been stable for 15 years, with only upwardcompatible additions to the coreX protocol, a recordofstability envied in computing. Formal releases of X started with X version 9 from MIT;the first commercial X products werebased on X version 10. The MIT X Consortium and its successors, the X Consortium, the Open Group X Project Team, and the X.OrgGroup released versions X11R3 through X11R6.6, beforethe founding of the X.OrgFoundation. Therewill be futuremaintenance releases in the X11R6.8.x series. However,efforts arewell underway to split the X distribution into its modular components to allow for easier maintenance and independent updates. We expect a transitional period while both X11R6.8 releases arebeing fielded and the modular release completed and deployed while both will be available as different consumers of X technology have different constraints on deployment. Wehave not yet decided how the modular X releases will be numbered. We encourage you to submit bug fixes and enhancements to bugzilla.freedesktop.orgusing the xorgproduct, and discussions on this server take place on <[email protected]>.
    [Show full text]
  • Web Vmstat Any Distros, Especially Here’S Where Web Vmstat Comes Those Targeted at In
    FOSSPICKS Sparkling gems and new releases from the world of FOSSpicks Free and Open Source Software Mike Saunders has spent a decade mining the internet for free software treasures. Here’s the result of his latest haul… Shiny statistics in a browser Web VMStat any distros, especially Here’s where Web VMStat comes those targeted at in. It’s a system monitor that runs Madvanced users, ship an HTTP server, so you can connect with shiny system monitoring tools to it via a web browser and see on the desktop. Conky is one such fancy CSS-driven charts. Before you tool, while GKrellM was all the rage install it, you’ll need to get the in the last decade, and they are websocketd utility, which you can genuinely useful for keeping tabs find at https://github.com/ on your boxes, especially when joewalnes/websocketd. Helpfully, you’re an admin in charge of the developer has made pre- various servers. compiled executables available, so Now, pretty much all major you can just grab the 32-bit or distros include a useful command 64-bit tarball, extract it and there line tool for monitoring system you have it: websocketd. (Of course, Here’s the standard output for vmstat – not very interesting, right? resource usage: vmstat. Enter if you’re especially security vmstat 1 in a terminal window and conscious, you can compile it from copy the aforementioned you’ll see a regularly updating (once its source code.) websocketd into the same place. per second) bunch of statistics, Next, clone the Web VMStat Git Then just enter: showing CPU usage, free RAM, repository (or grab the Zip file and ./run swap usage and so forth.
    [Show full text]
  • The Gnome Bazaar How Gnome Gets Built and How We Can Improve
    the gnome bazaar how gnome gets built and how we can improve daniel g. siegel 1. some serious stuff about my thesis 2. awesome gnome stuff how do foss projects work, which structures do they have and which workflows have they established. to accomplish this, several foss will be analyzed in order to identify concertedly models. in addition they will be compared to traditional software engineering models in order to see whether they are similar or oppose differences. good selection of projects with which the analysis is able to produce reliable and reasonable results • popularity • community • age ◦ communication • category ◦ number of developers • activity ◦ conferences ◦ releases ◦ foundations ◦ downloads ◦ ongoing projects ◦ commits project origin category Debian 1993 operating system Drupal 2001 content management system Fedora 2002 operating system GNOME 1997 desktop environment KDE 1996 desktop environment MySQL/MariaDB 1997 database management system PHP 1994 interpreted programming language Plone 1999 content management system PostgreSQL 1986 database management system Python 1989 interpreted programming language results 1 • history & origin 2 • community structure 3 • release process 4 • development model "[...] rather, the community seemed to resemble a great babbling bazaar of differing agendas and approaches" eric s. raymond what? comparison 1 • history & origin 2 • community structure 3 • release process 4 • development model history & origin • diverse origin • small group of founders • big burst of growth after first release • more big bursts before big releases community structure • very hierarchical • lead by leader or team • differences in hierachical structure • though easy to step up the ladder community structure: remarks • missing visionary • role of rt • unfruitful discussions release process • mostly fixed release cycles • lead by release manager/team • similar phases in all projects release process: remarks • cycle often too long for small projects • api/abi compatibility • jhbuild etc.
    [Show full text]
  • Ubuntu Kung Fu
    Prepared exclusively for Alison Tyler Download at Boykma.Com What readers are saying about Ubuntu Kung Fu Ubuntu Kung Fu is excellent. The tips are fun and the hope of discov- ering hidden gems makes it a worthwhile task. John Southern Former editor of Linux Magazine I enjoyed Ubuntu Kung Fu and learned some new things. I would rec- ommend this book—nice tips and a lot of fun to be had. Carthik Sharma Creator of the Ubuntu Blog (http://ubuntu.wordpress.com) Wow! There are some great tips here! I have used Ubuntu since April 2005, starting with version 5.04. I found much in this book to inspire me and to teach me, and it answered lingering questions I didn’t know I had. The book is a good resource that I will gladly recommend to both newcomers and veteran users. Matthew Helmke Administrator, Ubuntu Forums Ubuntu Kung Fu is a fantastic compendium of useful, uncommon Ubuntu knowledge. Eric Hewitt Consultant, LiveLogic, LLC Prepared exclusively for Alison Tyler Download at Boykma.Com Ubuntu Kung Fu Tips, Tricks, Hints, and Hacks Keir Thomas The Pragmatic Bookshelf Raleigh, North Carolina Dallas, Texas Prepared exclusively for Alison Tyler Download at Boykma.Com Many of the designations used by manufacturers and sellers to distinguish their prod- ucts are claimed as trademarks. Where those designations appear in this book, and The Pragmatic Programmers, LLC was aware of a trademark claim, the designations have been printed in initial capital letters or in all capitals. The Pragmatic Starter Kit, The Pragmatic Programmer, Pragmatic Programming, Pragmatic Bookshelf and the linking g device are trademarks of The Pragmatic Programmers, LLC.
    [Show full text]
  • Windows 7 Operating Guide
    Welcome to Windows 7 1 1 You told us what you wanted. We listened. This Windows® 7 Product Guide highlights the new and improved features that will help deliver the one thing you said you wanted the most: Your PC, simplified. 3 3 Contents INTRODUCTION TO WINDOWS 7 6 DESIGNING WINDOWS 7 8 Market Trends that Inspired Windows 7 9 WINDOWS 7 EDITIONS 10 Windows 7 Starter 11 Windows 7 Home Basic 11 Windows 7 Home Premium 12 Windows 7 Professional 12 Windows 7 Enterprise / Windows 7 Ultimate 13 Windows Anytime Upgrade 14 Microsoft Desktop Optimization Pack 14 Windows 7 Editions Comparison 15 GETTING STARTED WITH WINDOWS 7 16 Upgrading a PC to Windows 7 16 WHAT’S NEW IN WINDOWS 7 20 Top Features for You 20 Top Features for IT Professionals 22 Application and Device Compatibility 23 WINDOWS 7 FOR YOU 24 WINDOWS 7 FOR YOU: SIMPLIFIES EVERYDAY TASKS 28 Simple to Navigate 28 Easier to Find Things 35 Easy to Browse the Web 38 Easy to Connect PCs and Manage Devices 41 Easy to Communicate and Share 47 WINDOWS 7 FOR YOU: WORKS THE WAY YOU WANT 50 Speed, Reliability, and Responsiveness 50 More Secure 55 Compatible with You 62 Better Troubleshooting and Problem Solving 66 WINDOWS 7 FOR YOU: MAKES NEW THINGS POSSIBLE 70 Media the Way You Want It 70 Work Anywhere 81 New Ways to Engage 84 INTRODUCTION TO WINDOWS 7 6 WINDOWS 7 FOR IT PROFESSIONALS 88 DESIGNING WINDOWS 7 8 WINDOWS 7 FOR IT PROFESSIONALS: Market Trends that Inspired Windows 7 9 MAKE PEOPLE PRODUCTIVE ANYWHERE 92 WINDOWS 7 EDITIONS 10 Remove Barriers to Information 92 Windows 7 Starter 11 Access
    [Show full text]
  • UKUI: a Lightweight Desktop Environment Based on Pluggable
    2016 International Conference on Artificial Intelligence and Computer Science (AICS 2016) ISBN: 978-1-60595-411-0 UKUI: A Lightweight Desktop Environment Based on Pluggable Framework for Linux Distribution Jie YU1, Lu SI1,*, Jun MA1, Lei LUO1, Xiao-dong LIU1, Ya-ting KUANG2, Huan PENG2, Rui LI1, Jin-zhu KONG2 and Qing-bo WU1 1College of Computer, National University of Defense Technology, Changsha, China 2Tianjin KYLIN Information Technology Co., Ltd, Tianjin, China *[email protected] *Corresponding author Keywords: Desktop environment, Ubuntu, User interface. Abstract. Ubuntu is an operating system with Linux kernel based on Debian and distributed as free and open-source software. It uses Unity as its default desktop environment, which results in more difficulties of usage for Microsoft Windows users. In this paper, we present a lightweight desktop environment named UKUI based on UbuntuKylin, the official Chinese version of Ubuntu, for Linux distribution. It is designed as a pluggable framework and provides better user experience during human-computer interaction. In order to evaluate the performance of UKUI, a set of testing bench suits were performed on a personal computer. Overall, the results showed that UKUI has better performance compared with Unity. Introduction Linux is a freely available operating system (OS) originated by Linux Torvalds and further developed by thousands of others. Typically, Linux is packaged in a form known as a Linux distribution for both desktop and server use. Some of the most popular mainstream Linux distributions are Red Hat [1], Ubuntu [2], Arch [3], openSUSY [4], Gentoo [5], etc. There are several desktop environments available for nowadays modern Linux distributions, such as XFCE [6], GNOME [7], KDE [8] and LXDE [9].
    [Show full text]
  • Porting a Window Manager from Xlib to XCB
    Porting a Window Manager from Xlib to XCB Arnaud Fontaine (08090091) 16 May 2008 Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version pub- lished by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". Contents List of figures i List of listings ii Introduction 1 1 Backgrounds and Motivations 2 2 X Window System (X11) 6 2.1 Introduction . .6 2.2 History . .6 2.3 X Window Protocol . .7 2.3.1 Introduction . .7 2.3.2 Protocol overview . .8 2.3.3 Identifiers of resources . 10 2.3.4 Atoms . 10 2.3.5 Windows . 12 2.3.6 Pixmaps . 14 2.3.7 Events . 14 2.3.8 Keyboard and pointer . 15 2.3.9 Extensions . 17 2.4 X protocol client libraries . 18 2.4.1 Xlib . 18 2.4.1.1 Introduction . 18 2.4.1.2 Data types and functions . 18 2.4.1.3 Pros . 19 2.4.1.4 Cons . 19 2.4.1.5 Example . 20 2.4.2 XCB . 20 2.4.2.1 Introduction . 20 2.4.2.2 Data types and functions . 21 2.4.2.3 xcb-util library . 22 2.4.2.4 Pros . 22 2.4.2.5 Cons . 23 2.4.2.6 Example . 23 2.4.3 Xlib/XCB round-trip performance comparison .
    [Show full text]
  • Introduction to the Enlightenment Foundation Libraries
    Introduction to the Enlightenment foundation libraries. An overview of EFL Kostis Kapelonis Introduction to the Enlightenment foundation libraries.: An overview of EFL Kostis Kapelonis Abstract The target audience of this document are UNIX programmers who are interested in the Enlightenment Foundation Libraries (EFL). You must already know C programming. You will not however learn how to program using the EFL. Instead, you will learn why you should program with the EFL. If you ever wanted to evaluate the EFL but did not see any advantages over previous graphic libraries then this document is for you! Table of Contents 1. Introduction ............................................................................................................................1 A little History ...................................................................................................................1 Related documentation ......................................................................................................... 2 Obtaining the EFL libraries ................................................................................................... 2 2. The EFL structure .................................................................................................................... 4 Organization of the Libraries ................................................................................................. 4 Brief description of each EFL library ...................................................................................... 5 3.
    [Show full text]
  • The Desktop (Overview)
    The desktop (overview) The desktop is the main screen area that you see after you turn on your computer and log on to Windows. Like the top of an actual desk, it serves as a surface for your work. When you open programs or folders, they appear on the desktop. You can also put things on the desktop, such as files and folders, and arrange them however you want. The desktop is sometimes defined more broadly to include the taskbar and Windows Sidebar. The taskbar sits at the bottom of your screen. It shows you which programs are running and allows you to switch between them. It also contains the Start button , which you can use to access programs, folders, and computer settings. On the side of the screen, Sidebar contains small programs called gadgets. The desktop, taskbar, and Sidebar Where did my desktop go? Because programs run on top of the desktop, the desktop itself is often partially or completely hidden. But it's still there, underneath everything. To see the whole desktop without closing any of your open programs or windows, click the Show Desktop button on the taskbar. The desktop is revealed. Click the icon again to restore all of your windows to the way they were. Desktop Training Session Handout Page 1 http://ict.maxwell.syr.edu/vista/ Working with desktop icons Icons are small pictures that represent files, folders, programs, and other items. When you first start Windows, you'll see at least one icon on your desktop: the Recycle Bin (more on that later).
    [Show full text]
  • System Requirements
    1. System Requirements . 2 1.1 Software Requirements . 3 1.1.1 Application Server Requirements . 4 1.1.2 Database Requirements . 5 1.1.3 Management Tool Requirements . 6 1.2 Hardware Requirements . 7 1.2.1 Small Deployments (Up to 200 Simultaneous Sessions) . 8 1.2.2 Medium Deployments (Up to 1,000 Simultaneous Sessions) . 9 1.2.3 Large Deployments (Up to 10,000 Simultaneous Sessions) . 10 1.3 Client Requirements . 11 1.3.1 The Client as a Terminal Server Requirements . 12 1.3.2 Windows Client Requirements . 13 1.3.3 Linux Client as a Terminal Server Requirements . 14 1.3.4 Linux Client Requirements (Monitoring of the GUI for X Window System) . 15 1.3.5 macOS Client Requirements . 16 1.3.6 Client Performance Numbers . 17 1 System Requirements Table of Contents Software Requirements Application Server Requirements Database Requirements Management Tool Requirements Hardware Requirements Small Deployments (Up to 200 Simultaneous Sessions) Medium Deployments (Up to 1,000 Simultaneous Sessions) Large Deployments (Up to 10,000 Simultaneous Sessions) Client Requirements The Client as a Terminal Server Requirements Windows Client Requirements Linux Client as a Terminal Server Requirements Linux Client Requirements (Monitoring of the GUI for X Window System) macOS Client Requirements Client Performance Numbers 2 Software Requirements Table of Contents Application Server Requirements Database Requirements Management Tool Requirements 3 Application Server Requirements • Windows Server 2019, Windows Server 2016 or Windows Server 2012 (x64 platform).
    [Show full text]
  • Ati Driver Freebsd
    Ati driver freebsd Hey, I`m new to teh the bsd *BSD world and just installed Freebsd FreeBSD. Only thing missing is my video driver. ATI Radeon X How to Solved - Switch between ATI and VESA drivers? If you want to automatically load a video driver at boot time, we recommend to do it from /etc/:Radeon​: ​ It allows the use of newer xfvideo-ati drivers and AMD GPUs. This project started in January Initial radeon code comes from Linux. EndSection DESCRIPTION radeon is an Xorg driver for ATI/AMD RADEON-based video cards with the following features: o Full support for 8-, , and. This package contains the xfvideo-ati driver. xdrivers/drm-kmod: Port for the DRM kernel drivers for FreeBSD This port. If I boot X11 with no or with ati driver, the system stops responding, although cursor continues to follow mouse movements. (I suppose. To all those concerned, I have read that FreeBSD would be supported by the latest graphic card drivers, which was also confirmed by. I bought an expensive ATI card when they announced they'll go Note that AMD doesn't provide a driver for FreeBSD, so you'll be using the. We now know for sure that FreeBSD will ship with a kernel mode-setting driver for supporting open-source AMD Radeon graphics with its. AMD tech support has allegedly confirmed that Catalyst is being ported to FreeBSD. A Phoronix reader pointed out this thread. I am not sure that FreeBSD will fully support this card. The Xorg version for FreeBSD is and the ATI driver used is version The reason is, AMD/ATI doesn't support FreeBSD, and you have to resort to the sucky open source drivers.
    [Show full text]