November 2009 - Radeon HD - openSUSE Mailing Lists

0x9596:0x1787:0x0028: ATI Radeon HD 3650 AGP
by Pierce Lopez 18 Nov '09

18 Nov '09

Hi, The radeonhd driver (1.3.0) complains that it can't identify my card and asks me to send this email. It says that it's using "generic mode setting" which would explain why it isn't capable of my screen's native resolution of 1440x900 (over a VGA cable, not DVI), and instead falls back to 1024x768. The older xorg ati/radeon driver (6.12.4) properly identifies my video card, and provides the expected resolution. ========================================================= Key section of Xorg.0.log when using radeonhd: (II) RADEONHD: version 1.3.0, built from dist of git branch master, commit 8cbff7bf (II) Primary Device is: PCI 01@00:00:0 (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support (**) RADEONHD(0): Depth 24, (--) framebuffer bpp 32 (**) RADEONHD(0): Selected EXA 2D acceleration. (II) RADEONHD(0): Card not in database: 0x9596:0x1787:0x0028; using generic modesetting. If - and only if - your card does not work or does not work optimally please contact radeonhd(a)opensuse.org to help rectify this. Use the subject: 0x9596:0x1787:0x0028: <name of board> and *please* describe the problems you are seeing in your message. (--) RADEONHD(0): Detected an RV635 on an unidentified card (II) RADEONHD(0): Mapped IO @ 0xe0020000 to 0xb72c9000 (size 0x00010000) (II) RADEONHD(0): AGP Card Detected (II) RADEONHD(0): Getting BIOS copy from legacy VBIOS location (II) RADEONHD(0): ATOM BIOS Rom: SubsystemVendorID: 0x1787 SubsystemID: 0x0028 IOBaseAddress: 0xb000 Filename: SE525SAM.008 BIOS Bootup Message: RV635 GDDR2_32MX16 128BIT 512MB 725E/400M ^M ========================================================= Key section of Xorg.0.log when using ati/radeon: (II) Primary Device is: PCI 01@00:00:0 (II) [KMS] drm report modesetting isn't supported. (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support (II) RADEON(0): TOTO SAYS 00000000e0020000 (II) RADEON(0): MMIO registers at 0x00000000e0020000: size 64KB (II) RADEON(0): PCI bus 1 card 0 func 0 (**) RADEON(0): Depth 24, (--) framebuffer bpp 32 (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) (==) RADEON(0): Default visual is TrueColor (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/lib/xorg/modules/libvgahw.so (II) Module vgahw: vendor="X.Org Foundation" compiled for 1.7.1.901, module version = 0.1.0 ABI class: X.Org Video Driver, version 6.0 (II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (==) RADEON(0): RGB weight 888 (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) (--) RADEON(0): Chipset: "ATI Radeon HD 3650 AGP" (ChipID = 0x9596) (--) RADEON(0): Linear framebuffer at 0x00000000d0000000 (II) RADEON(0): AGP card detected (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/lib/xorg/modules/libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 1.7.1.901, module version = 1.0.0 ABI class: X.Org Video Driver, version 6.0 (II) RADEON(0): initializing int10 (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (II) RADEON(0): ATOM BIOS detected (II) RADEON(0): ATOM BIOS Rom: SubsystemVendorID: 0x1787 SubsystemID: 0x0028 IOBaseAddress: 0xb000 Filename: SE525SAM.008 BIOS Bootup Message: RV635 GDDR2_32MX16 128BIT 512MB 725E/400M ^M -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

2 1

[Bug 23716] New: crash on startup: unhandeled chipset
by bugzilla-daemon＠freedesktop.org 18 Nov '09

18 Nov '09

http://bugs.freedesktop.org/show_bug.cgi?id=23716 Summary: crash on startup: unhandeled chipset Product: xorg Version: 7.4 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: estellnb(a)gmail.com QAContact: xorg-team(a)lists.x.org Created an attachment (id=29228) --> (http://bugs.freedesktop.org/attachment.cgi?id=29228) Xorg.0.log + backtrace Sometimes but not always Xorg crashes on startup saying 'unhandeled chipset'; backtrace: see attachement. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 6

[Bug 20409] xdpyinfo returns wrong screen size
by bugzilla-daemon＠freedesktop.org 18 Nov '09

18 Nov '09

http://bugs.freedesktop.org/show_bug.cgi?id=20409 Elmar Stellnberger <estellnb(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #7 from Elmar Stellnberger <estellnb(a)gmail.com> 2009-11-18 09:03:29 PST --- resolved again for xorg-x11-driver-video-radeonhd-1.3.0_20091106_619706-2.1.x86_64 after an intermittent fallback to the old error. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

[Bug 24773] New: both screens stay dark
by bugzilla-daemon＠freedesktop.org 18 Nov '09

18 Nov '09

http://bugs.freedesktop.org/show_bug.cgi?id=24773 Summary: both screens stay dark Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: estellnb(a)gmail.com QAContact: xorg-team(a)lists.x.org Both screens stay dark with xorg-x11-driver-video-radeonhd-1.3.0_20091009_8cbff7b-5.1(integrated & external). If I thereupon reinit X with the /usr/lib64/xorg/modules of the old radeonhd (xorg-x11-driver-video-radeonhd-1.2.5_20090506_4be5f71-2.13.x86_64) only my integrated screen stays dark. Initiating X with the Vesa driver shows the same result. After rebooting and initing X with the old radeonhd first everything is OK again. related with Bug 24440. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 4

How about release (1.3.1)?
by Rafał Miłecki 18 Nov '09

18 Nov '09

There are some little fixes in git already and I don't think we wait for some great improvements anytime soon. So I thought about releasing new version. What do you think about it? Bug I still would like to see resolved before releasing is just: http://bugs.freedesktop.org/show_bug.cgi?id=24617 (patch exists) -- Rafał -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

2 1

Re: ChangeLog and INSTALL file
by Matthias Hopf 17 Nov '09

17 Nov '09

On Nov 17, 09 10:52:01 -0500, Gaetan Nadon wrote: > I wasn't aware of that. It makes sense now. I'd rather not make any > changes as I cannot test it in the older environment. There are > currently no important functional changes. May I suggest adding a > comment in configure.ac with the particular requirements? It would warn > others in the future. Patches are always welcome 8-) Thanks Matthias -- Matthias Hopf <mhopf(a)suse.de> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat(a)mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

Re: ChnageLog and INSTALL file
by Matthias Hopf 17 Nov '09

17 Nov '09

On Nov 16, 09 21:18:00 -0500, Gaetan Nadon wrote: > I am closing in on the driver directory to release patches for the few > remainder modules not having ChangeLog. I was wondering if there was > still an issue for radeonhd. A while ago the timing wasn't right. There I don't think so. We do not rely on current xorg-macros, because we want the driver to be able to build against older Xserver as well. Besides, the changelog generation is a oneliner :-] > In the mean time, things have changed a bit. Hardly any module had a > decent INSTALL file, if any. Rather than writing 251 files, the default > automake INSTALL file is copied in each module. Existing copies are > removed from git. The INSTALL from radeonhd *is* hand-crafted for the module. If it is general policy to use a standard INSTALL file for all xorg modules, I wouldn't have issues with that, but first our INSTALL file would have to be merged back into README, or distributed as a different file, as you suggested. This is something to be discussed on the radeonhd mailing list, CC'ing it. > There are other possibilities as well. Let me know how you would like to > handle the situation. I have included a copy of the INSTALL file for > your reference. This enhancement has been reviewed on xorg-devel. > > http://lists.x.org/archives/xorg-devel/2009-November/003387.html > Installation Instructions > ************************* > > Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, > 2006, 2007, 2008 Free Software Foundation, Inc. > > This file is free documentation; the Free Software Foundation gives > unlimited permission to copy, distribute and modify it. > > Basic Installation > ================== > > Briefly, the shell commands `./configure; make; make install' should > configure, build, and install this package. The following > more-detailed instructions are generic; see the `README' file for > instructions specific to this package. > > The `configure' shell script attempts to guess correct values for > various system-dependent variables used during compilation. It uses > those values to create a `Makefile' in each directory of the package. > It may also create one or more `.h' files containing system-dependent > definitions. Finally, it creates a shell script `config.status' that > you can run in the future to recreate the current configuration, and a > file `config.log' containing compiler output (useful mainly for > debugging `configure'). > > It can also use an optional file (typically called `config.cache' > and enabled with `--cache-file=config.cache' or simply `-C') that saves > the results of its tests to speed up reconfiguring. Caching is > disabled by default to prevent problems with accidental use of stale > cache files. > > If you need to do unusual things to compile the package, please try > to figure out how `configure' could check whether to do them, and mail > diffs or instructions to the address given in the `README' so they can > be considered for the next release. If you are using the cache, and at > some point `config.cache' contains results you don't want to keep, you > may remove or edit it. > > The file `configure.ac' (or `configure.in') is used to create > `configure' by a program called `autoconf'. You need `configure.ac' if > you want to change it or regenerate `configure' using a newer version > of `autoconf'. > > The simplest way to compile this package is: > > 1. `cd' to the directory containing the package's source code and type > `./configure' to configure the package for your system. > > Running `configure' might take a while. While running, it prints > some messages telling which features it is checking for. > > 2. Type `make' to compile the package. > > 3. Optionally, type `make check' to run any self-tests that come with > the package. > > 4. Type `make install' to install the programs and any data files and > documentation. > > 5. You can remove the program binaries and object files from the > source code directory by typing `make clean'. To also remove the > files that `configure' created (so you can compile the package for > a different kind of computer), type `make distclean'. There is > also a `make maintainer-clean' target, but that is intended mainly > for the package's developers. If you use it, you may have to get > all sorts of other programs in order to regenerate files that came > with the distribution. > > 6. Often, you can also type `make uninstall' to remove the installed > files again. > > Compilers and Options > ===================== > > Some systems require unusual options for compilation or linking that > the `configure' script does not know about. Run `./configure --help' > for details on some of the pertinent environment variables. > > You can give `configure' initial values for configuration parameters > by setting variables in the command line or in the environment. Here > is an example: > > ./configure CC=c99 CFLAGS=-g LIBS=-lposix > > *Note Defining Variables::, for more details. > > Compiling For Multiple Architectures > ==================================== > > You can compile the package for more than one kind of computer at the > same time, by placing the object files for each architecture in their > own directory. To do this, you can use GNU `make'. `cd' to the > directory where you want the object files and executables to go and run > the `configure' script. `configure' automatically checks for the > source code in the directory that `configure' is in and in `..'. > > With a non-GNU `make', it is safer to compile the package for one > architecture at a time in the source code directory. After you have > installed the package for one architecture, use `make distclean' before > reconfiguring for another architecture. > > On MacOS X 10.5 and later systems, you can create libraries and > executables that work on multiple system types--known as "fat" or > "universal" binaries--by specifying multiple `-arch' options to the > compiler but only a single `-arch' option to the preprocessor. Like > this: > > ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ > CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ > CPP="gcc -E" CXXCPP="g++ -E" > > This is not guaranteed to produce working output in all cases, you > may have to build one architecture at a time and combine the results > using the `lipo' tool if you have problems. > > Installation Names > ================== > > By default, `make install' installs the package's commands under > `/usr/local/bin', include files under `/usr/local/include', etc. You > can specify an installation prefix other than `/usr/local' by giving > `configure' the option `--prefix=PREFIX'. > > You can specify separate installation prefixes for > architecture-specific files and architecture-independent files. If you > pass the option `--exec-prefix=PREFIX' to `configure', the package uses > PREFIX as the prefix for installing programs and libraries. > Documentation and other data files still use the regular prefix. > > In addition, if you use an unusual directory layout you can give > options like `--bindir=DIR' to specify different values for particular > kinds of files. Run `configure --help' for a list of the directories > you can set and what kinds of files go in them. > > If the package supports it, you can cause programs to be installed > with an extra prefix or suffix on their names by giving `configure' the > option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. > > Optional Features > ================= > > Some packages pay attention to `--enable-FEATURE' options to > `configure', where FEATURE indicates an optional part of the package. > They may also pay attention to `--with-PACKAGE' options, where PACKAGE > is something like `gnu-as' or `x' (for the X Window System). The > `README' should mention any `--enable-' and `--with-' options that the > package recognizes. > > For packages that use the X Window System, `configure' can usually > find the X include and library files automatically, but if it doesn't, > you can use the `configure' options `--x-includes=DIR' and > `--x-libraries=DIR' to specify their locations. > > Particular systems > ================== > > On HP-UX, the default C compiler is not ANSI C compatible. If GNU > CC is not installed, it is recommended to use the following options in > order to use an ANSI C compiler: > > ./configure CC="cc -Ae" > > and if that doesn't work, install pre-built binaries of GCC for HP-UX. > > On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot > parse its `<wchar.h>' header file. The option `-nodtk' can be used as > a workaround. If GNU CC is not installed, it is therefore recommended > to try > > ./configure CC="cc" > > and if that doesn't work, try > > ./configure CC="cc -nodtk" > > Specifying the System Type > ========================== > > There may be some features `configure' cannot figure out > automatically, but needs to determine by the type of machine the package > will run on. Usually, assuming the package is built to be run on the > _same_ architectures, `configure' can figure that out, but if it prints > a message saying it cannot guess the machine type, give it the > `--build=TYPE' option. TYPE can either be a short name for the system > type, such as `sun4', or a canonical name which has the form: > > CPU-COMPANY-SYSTEM > > where SYSTEM can have one of these forms: > > OS KERNEL-OS > > See the file `config.sub' for the possible values of each field. If > `config.sub' isn't included in this package, then this package doesn't > need to know the machine type. > > If you are _building_ compiler tools for cross-compiling, you should > use the option `--target=TYPE' to select the type of system they will > produce code for. > > If you want to _use_ a cross compiler, that generates code for a > platform different from the build platform, you should specify the > "host" platform (i.e., that on which the generated programs will > eventually be run) with `--host=TYPE'. > > Sharing Defaults > ================ > > If you want to set default values for `configure' scripts to share, > you can create a site shell script called `config.site' that gives > default values for variables like `CC', `cache_file', and `prefix'. > `configure' looks for `PREFIX/share/config.site' if it exists, then > `PREFIX/etc/config.site' if it exists. Or, you can set the > `CONFIG_SITE' environment variable to the location of the site script. > A warning: not all `configure' scripts look for a site script. > > Defining Variables > ================== > > Variables not defined in a site shell script can be set in the > environment passed to `configure'. However, some packages may run > configure again during the build, and the customized values of these > variables may be lost. In order to avoid this problem, you should set > them in the `configure' command line, using `VAR=value'. For example: > > ./configure CC=/usr/local2/bin/gcc > > causes the specified `gcc' to be used as the C compiler (unless it is > overridden in the site shell script). > > Unfortunately, this technique does not work for `CONFIG_SHELL' due to > an Autoconf bug. Until the bug is fixed you can use this workaround: > > CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash > > `configure' Invocation > ====================== > > `configure' recognizes the following options to control how it > operates. > > `--help' > `-h' > Print a summary of all of the options to `configure', and exit. > > `--help=short' > `--help=recursive' > Print a summary of the options unique to this package's > `configure', and exit. The `short' variant lists options used > only in the top level, while the `recursive' variant lists options > also present in any nested packages. > > `--version' > `-V' > Print the version of Autoconf used to generate the `configure' > script, and exit. > > `--cache-file=FILE' > Enable the cache: use and save the results of the tests in FILE, > traditionally `config.cache'. FILE defaults to `/dev/null' to > disable caching. > > `--config-cache' > `-C' > Alias for `--cache-file=config.cache'. > > `--quiet' > `--silent' > `-q' > Do not print messages saying which checks are being made. To > suppress all normal output, redirect it to `/dev/null' (any error > messages will still be shown). > > `--srcdir=DIR' > Look for the package's source code in directory DIR. Usually > `configure' can determine that directory automatically. > > `--prefix=DIR' > Use DIR as the installation prefix. *Note Installation Names:: > for more details, including other options available for fine-tuning > the installation locations. > > `--no-create' > `-n' > Run the configure checks, but stop before creating any output > files. > > `configure' also accepts some other, not widely useful, options. Run > `configure --help' for more details. > Matthias -- Matthias Hopf <mhopf(a)suse.de> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat(a)mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

[Bug 24573] New: Sementation fault with radeonhd-1.3.0
by bugzilla-daemon＠freedesktop.org 13 Nov '09

13 Nov '09

http://bugs.freedesktop.org/show_bug.cgi?id=24573 Summary: Sementation fault with radeonhd-1.3.0 Product: xorg Version: 7.4 Platform: x86 (IA32) OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: mpagano(a)gentoo.org QAContact: xorg-team(a)lists.x.org Created an attachment (id=30480) --> (http://bugs.freedesktop.org/attachment.cgi?id=30480) Xorg log With xorg 7.4 and radeonhd-1.3.0 I get a a blank screen with a segmentation fault. With radeonhd-1.2.5, I do not have this issue. Backtrace: 0: X(xorg_backtrace+0x3c) [0x8126dfc] 1: X(xf86SigHandler+0x4e) [0x80c0050] 2: [0xb782a400] 3: /usr/lib/xorg/modules/drivers//radeonhd_drv.so [0xb7267771] 4: /usr/lib/xorg/modules/drivers//radeonhd_drv.so [0xb7291570] 5: X(xf86CrtcSetModeTransform+0x44c) [0x80e486e] 6: X(xf86SetDesiredModes+0x10e) [0x80e4baf] 7: /usr/lib/xorg/modules/drivers//radeonhd_drv.so(RHDRandrModeInit+0x7a) [0xb72911a7] 8: /usr/lib/xorg/modules/drivers//radeonhd_drv.so [0xb72759b6] 9: X(AddScreen+0x196) [0x806f38a] 10: X(InitOutput+0x1fc) [0x80a9386] 11: X(main+0x1e9) [0x806fa71] 12: /lib/libc.so.6(__libc_start_main+0xe5) [0xb7409725] 13: X [0x806f121] -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 20

[Bug 19802] [4850HD] Output DVI-I_2/analog enabled but has no modes
by bugzilla-daemon＠freedesktop.org 13 Nov '09

13 Nov '09

http://bugs.freedesktop.org/show_bug.cgi?id=19802 --- Comment #5 from Matthias Hopf <mhopf(a)suse.de> 2009-11-13 05:08:23 PST --- Version 1.2.4 is too old, please retry with newer 1.3.0. Also, the config seem to have a configured monitor. Retry with out the Monitor "Monitor[0]" or equivalent line in the Screen section. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0

radeon vs radeonhd
by Pierpaolo Follia 13 Nov '09

13 Nov '09

Hi, my card (Mobility x1400) is supported by both radeon drivers. It is really good with radeon driver (about 2000 fps with glxgears) but performances using radeonhd driver drop to about 1000fps. Is this an expected behaviour or my config is wrong? I attach my xorg log. Thank in advice. -- Pierpaolo Follia http://madchicken.altervista.org/tech

5 9