Re: The AMD/ATI Bar & Grill

KMS stands for "Kernel Mode Setting". Catalsyt is not - yet - compatible with KMS, so you need to disable it. Either add "nomodeset" to your "kernel" line in /boot/grub/menu.lst or add "!radeon" to your MODULES array in /etc/rc.conf

For a detailed explanation see the catalyst article in the wiki.

Last edited by dcc24 (2010-07-09 16:01:08)

It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)

Re: The AMD/ATI Bar & Grill

dcc24 wrote:

KMS stands for "Kernel Mode Setting". Catalsyt is not - yet - compatible with KMS, so you need to disable it. Either add "nomodeset" to your "kernel" line in /boot/grub/menu.lst or add "!radeon" to your MODULES array in /etc/rc.conf

For a detailed explanation see the catalyst article in the wiki.

oohh thank you, I didnt read what was that for, but yes I did add nomodest in my kernel loader

What most concerncs me, I think, it is the fglrx in the loader, which says it is not recognized in the rc.d .. I dont remember that being normal.

My rc config is

#
# /etc/rc.conf - Main Configuration for Arch Linux
#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="America/Argentina/Buenos_Aires"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs fglrx crond alsa hal)

Re: The AMD/ATI Bar & Grill

Catalyst package lots of changes!

Lately i noticed existance of great catalyst package called catalyst-nostock created and maintained by Shen "dickeny" Miren. Shen's idea was to made catalyst package more flexible, more self-sufficient, and more independent from the kernel we are using atm. And he did it very well - he's catalyst can autorecompile whenever you are installing/updating kernel. He reached it with mkinitcpio's hook.Unfortunately catalyst-nostock wasn't updated for some time. cyberpatrol decided to write email to Shen and ask him whats happening, and Shen replay to him that he orphaned package. So cyberpatrol decided to adopt the package and wrote me a preposition so maybe it could be pulled in into catalyst. After doing some tests and writing some code(that should remove unused fglrx modules) i decided to do it.

Sooo... heres new catalyst package! From now on it will be available on aur only, and after your successful tests (hope you will be so kind to let me know if its [not]working) i will put this into repo.

Actually new catalyst can not only autorecompile fglrx module whenever kernel is updated, but it's very good solution for people who are using more than one kernel. Cuz with it you can simply build fglrx module (and easily have more than just one fglrx module in system) for any kernel, even if you arent using this kernel right now, just with one simple command:

Ofcourse last command isn't so necessary cuz fglrx module for kernel you are using at the moment will be builded when you will install catalyst, although it can be useful.

Plus i modified original remove function:

# catalyst_build_module remove

so now it should remove fglrx module from /lib/modules/kernel_name whenever kernel_name looks unused. I did it by checking if directory /lib/modules/kernel_name/kernel still exist. If you know better way how to check that some kernel isnt actually existing - write about it please. (plus catalyst_build_module remove is called automatically by the hook whenever kernel is updated/installed)

Re: The AMD/ATI Bar & Grill

To all those using catalyst repository:because of today's downgrade of libva package (in extra repo) i downgraded packages mplayer-vaapi (switching back to mplayer-vaapi-20100602-4) and xvba-video (switching back to xvba-video-0.6.11-1) at catalyst repo.So please install it with:# pacman -Sy# pacman -Suu

Re: The AMD/ATI Bar & Grill

[catalyst] repo update: catalyst 10.6 package was updated, now it has automatic re-compilation of fglrx module whenever kernel is installed/updated functionality and multi-kernel support.More info about that features can be found at wiki

Re: The AMD/ATI Bar & Grill

Feedback time! Here are the steps:I was with kernel .33, removed catalyst 10.6-1, installed catalyst 10.6-4, installed kernel .34, rebooted and during bootcheck it said fglrx module not found. When I entered into openbox I did a modprobe fglrx but again it said module not found. I ran fglrx_build_module with no errors, then again modprobe fglrx, restarted X and it worked

Re: The AMD/ATI Bar & Grill

maevius wrote:

Feedback time! Here are the steps:I was with kernel .33, removed catalyst 10.6-1, installed catalyst 10.6-4, installed kernel .34, rebooted and during bootcheck it said fglrx module not found. When I entered into openbox I did a modprobe fglrx but again it said module not found. I ran fglrx_build_module with no errors, then again modprobe fglrx, restarted X and it worked

So basically fglrx module was created for 2.6.33-ARCH kernel when installing catalyst 10.6-4.Then when you were upgrading to kernel 2.6.34-ARCH fglrx hook didn't work because (i believe) package kernel26-headers was installed after kernel26 installation - so there was no /lib/modules/2.6.34-ARCH/build directory and fglrx module couln't been build by fglrx hook.Important Note:I guess that this situation could happen more often - so its good to run

# catalyst_build_module new_kernel_version

just after some main (i mean ie. 2.6.33->2.6.34, not 2.6.34.1->2.6.34.2) kernel26 update.