Nightwulf|work: hi all
ahox: Hi, does the radeonhd driver support the displayport?
ahox: xrandr does not seem to find it
Hazelesque: tries to work out exactly what she needs to do to install a recent radeonhd
Hazelesque: http://wiki.x.org/wiki/radeonhd%3AINSTALL < there's this guide, but this seems to be to do with r6xx/r7xx devices
Hazelesque: I have the "ATI Technologies Inc Radeon Mobility X1400", which appears to be r300, I think!?
Hazelesque: http://wiki.x.org/wiki/radeonhd%3ADRI < and there's this
Hazelesque: they both tell me to install stuff in /usr, but I'm not sure if I feel comfortable doing things that the package manager is going to trample later
adamk: That guide is pretty old, too.
Hazelesque: hmm, /me notices the bit about PREFIXes and reads that
Hazelesque: adamk: also, one of them said I wanted to "cd linux-core" and build that
adamk: It's geared towards getting Xv support going on r6xx/r7xx cards, but most up-to-date distributions already have that.
Hazelesque: but I get
Hazelesque: /home/hazel/src/Xorg/radeonhd-stuff-2009-11-10/drm/linux-core/drm_memory.c:286: error: ‘struct agp_memory’ has no member named ‘memory’
adamk: Most up-to-date distributions should already be providing you with 3D acceleration on your GPU without having to update radeonhd, in fact.
chithead: you are trying to build drm.git kernel modules. there is no need for that
chithead: in fact the drm.git kernel modules are obsolete and unmaintainted
Hazelesque: and googling it gets an "INVALID" bug on Nouveau, which says not to use linux-core, and some other waffle
Hazelesque: chithead: ah, OK, well, the page listed was just saying to do that
Hazelesque: heh
Hazelesque: chithead: do I still want to build the drm library in that tree?
chithead: wiki pages are often outdated and confusing
chithead: if your distro ships libdrm-2.4.13 or later, you should be find
chithead: fine*
Hazelesque: debian squeeze has libdrm2 2.4.14-1
Hazelesque: last time I tried xserver-xorg-radeonhd in squeeze, it was very slow
Hazelesque: so I switched to xserver-xorg-radeon
Hazelesque: -video-radeon
Hazelesque: or whatever
chithead: for radeonhd, you may have to explicitly enable dri and exa in xorg.conf
Hazelesque: but now (with radeon, not hd) I get "xrandr: Configure crtc 1 invalid time" when trying to configure a new external monitor
Hazelesque: hmm, the radeonhd in debian squeeze is built from "non-git sources"
Hazelesque: and so doesn't list a git revision
Hazelesque: but claims to be package version "1.2.5-1"
Hazelesque: chithead: http://qwerty.pastebin.com/d68722389 was the last xorg.conf I used with radeonhd, and it was being rubbish, although I can't remember specifically what was rubbish about it
chithead: Hazelesque: yes, dri was not enabled
Hazelesque: Option "DRI" "1"
Hazelesque: Option "AccelMethod" "EXA"
Hazelesque: ?
chithead: line 98 in your pastebin
Hazelesque: chithead: oh, no "1" on the end?
Hazelesque: just Option "DRI"?
Hazelesque: hmm
Hazelesque: one mailing list post had it as a "1", but googling for "Option DRI" finds most people using "true"
tommy99: hi guys, I have a problem setting up radeonhd on a Thinkpad T60 with an ati X1400 graphic card, on a gentoo linux! The screen just stays black! Xorg log: http://nopaste.info/4ef8347892.html Xorg.config: http://nopaste.info/91dccb097f.html
Hazelesque: right, well, wish me luck
adamk: tommy99, That's not the full log file.
adamk: Also, just running 'Xorg -config xorg.conf.new' is only going to produce a black screen these days.
adamk: Xorg no longer draws the old background unless you use the -retro option.
tommy99: adamk: hmm, didn't know this
tommy99: adamk: oh my god ... x server worked the whole time and I didn't recogniced this .... starting gdm seems to work fine
tommy99: adamk: thank you very much!
adamk: No problem.
Hazelesque: right
Hazelesque: I remembered why it was rubbish now
Hazelesque: it was not listing all of the right modes
Hazelesque: madarame:log# wc -l Xorg.0.log
Hazelesque: 4920 Xorg.0.log
Hazelesque: madarame:log# grep "Not using default mode" Xorg.0.log | wc -l
Hazelesque: 3711
Hazelesque: the native resolution of the TFT on DVI-D_1 is 1680x1050
Hazelesque: the best it is offering me is either 1360x768, or 1152x864
adamk: Try forcing it to 1680x1060 by creating creating a Modeline and using the PreferredMode option in the monitor section.
Hazelesque: adamk: is that a "see if it works at all" suggestion, or a "this is my best workaround" suggestion?
Hazelesque: as I regularly change which monitors I have attached
Hazelesque: as I take my laptop home when I go home, and stuff
Hazelesque: and I don't want to hard-code in my display config
adamk: That's all I can offer.
Hazelesque: hmm
adamk: Clearly it's not reading the correct EDID from that montior.
adamk: monitor, even.
Hazelesque: (II) RADEONHD(0): Not using default mode "1680x1050" (hsync out of range)
adamk: Do both radeonhd and radeon have that problem?
Hazelesque: adamk: no, radeon fails for a completely different reason to talk to that monitor
Hazelesque: complaining about crtc stuff
Hazelesque: but both of them will talk to my old monitor
Hazelesque: but radeonhd does not offer 1280x1024 on said old monitor, and radeon does
adamk: It sounds like they both might have problems related to EDID information.
adamk: All I can suggest is making sure you try with the latest drivers, and open up a bug report if it doesn't work.
Hazelesque: adamk: would you like me to pastebin the entire Xorg.0.log file?
Hazelesque: adamk: OK, so try to compile xf86-video-radeonhd git?
Hazelesque: s/so try/so I should try/
adamk: And xf86-video-ati from git. See if it works for either.
Hazelesque: OK
Hazelesque: adamk: should i do so with the latest stable branch, or master?
Hazelesque: re: both ati and radeonhd
adamk: master.
adamk: IMO.
Hazelesque: k
Hazelesque: adamk: presumably mesa version will have no bearing on whether it supports modeline foo?
Hazelesque: and so I don't need to bother updating mesa to anything newer than the distro ships?
adamk: That is correct.
Hazelesque: back soon
Hazelesque: curious
Hazelesque: I have
Hazelesque: a Section "Files"
Hazelesque: ignore me, pebkac
Hazelesque: I was setting it again later in the config file
Hazelesque: the ModulePath
Hazelesque: it appears to work fine with git master version of radeonhd
Hazelesque: thanks! :)
adamk: Woohoo.
Hazelesque: only thing now is to go and edit the config to re-enable Zap
udovdh: Option "DontZap" "False" ?
nego: Does anyone know if there is a particular issue with 3850hd cards that prevent them from working with the radeonhd driver?
nego: I keep getting these errors:
nego: (EE) RADEONHD(0): RHDDRIVersionCheck: drmOpen("radeon", "pci:0000:01:00.0") failed.
nego: (EE) RADEONHD(0): RandR: No valid modes. Disabling RandR support.
nego: (EE) RADEONHD(0): Failed to detect a connected monitor
nego: (EE) Screen(s) found, but none have a usable configuration.
adamk: I'm not aware of anything.
adamk: It's clearly not detecting the attached monitor. You could try a newer version, or even try the radeon driver.
nego: For some reason it says my 3850 is an unknown card, but it can tell the chipset on it.
nego: I'm using the radeon driver right now actually, but I was curious to see if the radeonhd driver offered better support.
nego: For 3d acceleration and such.
adamk: In terms of 2D, they are comparable. radeonhd supports HDMI audio.
adamk: 3D is provided by Mesa and the kernel module, not by either the radeon or radeonhd Xorg modules
nego: Ah.
adamk: Having said that, nearly all the 3D developers use 'radeon' so that combination is tested more.
joyful_dep: hi there
joyful_dep: hi there
MostAwesomeDude: Hey.
markinfo: could you to help me with radeon driver? it freezes always my system - it runs only with Option "DRI" "off in xorg.conf but is very, very slow.
yangman: markinfo: GPU and radeonhd version?
markinfo: yangman, Mobility Radeon X1800 (M58), radeon from GIT, kernel 2.6.31
yangman: radeon or radeonhd?
markinfo: radeonhd
markinfo: I should use radeonhd? or not?
yangman: ok. it's just that you keep saying radeon
yangman: running any 3D apps?
yangman: there was a known lockup issue with composite and GLX. it's fixed in master now
markinfo: it freezes just on start. If I turn dri off a have recorder xorg.log http://85.126.193.68/marek/data/xorg.log_2.6.31-radeonhd_git-dri_off
markinfo: I have compiled it yesterday
markinfo: 2D/3D: Fix Lockups on R5XX when running DRI clients with EXA/Textured Video.
markinfo: should be fixed already
markinfo: yangman, can you see something interesting from xorg.log? Should I show dmesg?
yangman: try the latest git
markinfo: I have pulled yesterday GIT an compiled.
yangman: ok, you do have that commit
yangman: does plain X also lock up?
markinfo: yes.
markinfo: only vesa is going
yangman: anything interesting in dmesg?
yangman: and log of a broken session would be more useful
markinfo: yangman, http://85.126.193.68/marek/data/dmesg
markinfo: I cannot log broken connection - as it freezes always.
markinfo: I tried some time ago over remote ssh
yangman: no useful Xorg.0.log.old either?
markinfo: yangman, hm, I am not linux profi - what is exactly Xorg.0.log.old ?
yangman: X always keeps a copy of the log from the previous session
markinfo: but it freezes an I do cold restart - then run fsck and i think there is no log available.
yangman: ok
yangman: seems like kernel locking, which is unusual
yangman: give radeon a try
markinfo: from remote ssh:
markinfo: It loads everything nice but at the end:
markinfo: ...
markinfo: (II) RADEONHD(0): EDID for output TV_SVIDEO
markinfo: (II) RADEONHD(0): LVDSSetBacklight: trying to set BL_MOD_LEVEL to: 0
markinfo: (WW) RADEONHD(0): DRMCPIdle: DRM CP IDLE returned BUSY!
markinfo: (WW) RADEONHD(0): DRMCPIdle: DRM CP IDLE returned BUSY!
markinfo: and it is repeating for ever
markinfo: yangman, well I try radeon. ....but i think I have tested it already.
markinfo: but I test it again. Do y need radeon from GIT?
yangman: latest release should be fine, afaik
markinfo: yangman, against what kernel version are this releases im GIT checked?
markinfo: and xserver version is also important - or?
yangman: no and no
yangman: 2.6.31 is new enough for all non-KMS things for r5xx
markinfo: yangman, Do I need http://packages.debian.org/squeeze/firmware-linux to be Installed? One part inside is * Radeon R500-family CP microcode, version unknown
markinfo: there is no dependency on this package from radeonhd drver.
adamk: Yes, you need that.
markinfo: but the instalation of that has not helped.
markinfo: and before - as radeonhd driver has worked firmware was not installed.
yangman: you need the firmwares for DRM to work
yangman: depends on how far back you go, but DRM wasn't on by default for radeonhd at some points
MostAwesomeDude: There's no dep on it because it's Debian policy to not depend on non-free packages.
MostAwesomeDude: Whoo Debian.
MostAwesomeDude: People are going to have *real* fun when nouveau starts shipping in-kernel. :C
jvd: looking forward to it
markinfo: there is only /lib/firmware/radeon/R520_cp.bin - how can i check if there is loaded this firmware? And wenn it loads? with xserver start?
yangman: markinfo: on drm module load
adamk: markinfo, I think it shows up in dmesg... I get: "platform radeon_cp.0: firmware: requesting radeon/R420_cp.bin" h343.
adamk: here, even.
markinfo: adamk, http://85.126.193.68/marek/data/dmesg nothing like this
adamk: Did you reload the kernel module after installing the firmware?
markinfo: what means reloa kernel? I have restarted many time since I have installed this firmware.
adamk: OK, then that's not the problem.
markinfo: but it is interesting - as I have written some of my first ugreport about it http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547360 there was a sign of loading firmware in dmesg.
markinfo: [ 1023.830909] [drm] Initialized radeon 1.30.0 20080528 for
markinfo: 0000:01:00.0 on minor 0 [ 1023.974202] [drm] Setting GART location
markinfo: based on new memory map [ 1023.975039] [drm] Loading R500 Microcode
markinfo: [ 1023.975045] platform radeon_cp.0: firmware: requesting
markinfo: radeon/R520_cp.bin [ 1024.056892] [drm] Num pipes: 3
markinfo: [ 1024.056906] [drm] writeback test succeeded in 2 usecs
markinfo: now anything like this.
MostAwesomeDude: Woot.
MostAwesomeDude: Looks like you're set.
markinfo: "I am set" ? what it means?
MostAwesomeDude: It should work now.
adamk: I think he's saying that he doesn't get that in dmesg now, but had it when he opened that bug report.
MostAwesomeDude: Oooh.
markinfo: it is so hard to test it - wenn it freezes i must reset system than wait for a fsck, system load - it takes much of time
markinfo: I would change graphic card - if it would be possible.
markinfo: It is about 2 years -there was announcement that AMD has made some specification of ATI graphic card free.
adamk: Yes, they are available.
markinfo: radeon driver is in pacage xserver-xorg-video-ati ?
yangman: YES
yangman: ops, caps
DeX77: hi
markinfo: so i have compiled ATI driver from GIT - i will try it. What should be in xorg.conf "ati" istead of "radeonhd" ?
markinfo: what with Option "DRI" "off"option "" Should be commented out completely?
markinfo: or make it sense to try with "on" "off" ?
adamk: markinfo, Either 'ati' or 'radeon' would work as the diver.
adamk: markinfo, The DRI option is ignored for the radeon driver.
markinfo: well.
agd5f: adamk: DRI option works for radeon as well
adamk: Oh...
adamk: Odd, why did I think it was ignored? Does it default to On?
agd5f: yeah
adamk: Gotcha... So you can disable it that way but don't have to enable it that way. With radeonhd, at least at one point, it had/has to be explicitly enabled.
adamk: What's the difference between setting that of off and disabling the dri module via the Modules section?
agd5f: adamk: DRI option is at the driver level, dri module is the server level
markinfo: ati driver - instead of radeonhd doesn not helped. With the option "DRI off" it starts, it looks like it is OK. but if I move any windows the borders of windows are not redraw - and very soon ist the screen unsuable. Wenn I comment out the Option "DRI off" in xorg.conf, it freezes on start - 100%CPU an only hard reset is possible.
markinfo: there is still no evidence that some microcode for radeon card is loading in dmesg.
MostAwesomeDude: If the microcode's not loading, DRI will *not* work.
markinfo: How to force loading of microcode?
MostAwesomeDude: Did you make sure that your microcode's still in /lib/firmware?
MostAwesomeDude: You shouldn't have to force it; it will try very hard to load it.
markinfo: marek@debian-xfce:~$ ls -al /lib/firmware/radeon/
markinfo: -rw-r--r-- 1 root root 2048 2009-09-02 11:04 R520_cp.bin
markinfo: and other files
MostAwesomeDude: Could you pastebin your dmesg?
markinfo: MostAwesomeDude, http://85.126.193.68/marek/data/dmesg
MostAwesomeDude: markinfo: Um. DRM'
MostAwesomeDude: DRM's not loading at all. Either that's not your entire dmesg, or you don't have the kernel modules around. Is this a custom kernel?
markinfo: MostAwesomeDude, hm...this kernel is from http://liquorix.net/ because debian still have only 2.6.30 Should i test it with that?
markinfo: but i think i have tested it also - but I can test again.
markinfo: i will be back.
markinfo: MostAwesomeDude, If i start xserver without to be mentioned "DRI - off" in xorg.log it freezes. Exactly - if I change quickly during the start of xserver to VT1 I can see the logs and it shows that the DRI was loaded - everywhere is "loaded OK"....But if i Return afterwards to VT7 it freezes and only hard reset is possible. The same is if i wait completely to load xserver. Only hard reset is possible then.
MostAwesomeDude: Hm.
MostAwesomeDude: I have no idea why this is.
markinfo: MostAwesomeDude, Ihave my system already very long - debian etch, lenny, squeeze. It has stopped to work after update to the new version of xserver (new radeonhd driver was updatet with that too). Could it help to reinstall it completely new? I see also after command "startx" on the first line something like "command not found " .... but it disappears quickly and desktop starts. Can it be loged somehow?
MostAwesomeDude: markinfo: I'm honestly not sure.
MostAwesomeDude: Have you started up in single-user mode and manually loaded DRM?
MostAwesomeDude: To see what the full kernel message is?
markinfo: MostAwesomeDude, hm "to start in single mode" ...I assume this is the second option im Grub. And how to load manually DRM?
MostAwesomeDude: markinfo: # modprobe radeon
markinfo: well - why is single mode important?
MostAwesomeDude: If you're feeling adventurous, try enabling KMS: # modprobe radeon modeset=1
MostAwesomeDude: Single mode's important because X won't start and nothing else will load. It'll be very bare-bones.
MostAwesomeDude: You can make sure nothing else is interfering.
MostAwesomeDude: Also in Debian, single-user mode terminals get kernel messages, so you can see immediately what's going on.
markinfo: and no modules are oaded? so that i must load radeon manually?
MostAwesomeDude: Right, radeon probably won't get loaded by default.
markinfo: nice - i will try.
markinfo: MostAwesomeDude, but to use KMS I need some special kernel?
MostAwesomeDude: markinfo: Oh, I figured that that's the reason you were on such a new kernel.
MostAwesomeDude: At any rate, don't worry about it; we're testing the firmware loading, which happens both in KMS and non-KMS.
markinfo: well.
markinfo: MostAwesomeDude, after I load radeon modul it display:
markinfo: [drm] Initialized drm 1.1.0 20060810
markinfo: pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
markinfo: pci 0000:01:00.0: setting latency timer to 64
markinfo: [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on minor 0
MostAwesomeDude: markinfo: Good. And what's in dmesg?
MostAwesomeDude: Does it say anything about loading firmware?
markinfo: rmmod: [drm] Module unloaded and modprobe radeon: [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on minor 0
markinfo: nothing else.
MostAwesomeDude: Hm.
MostAwesomeDude: Could you rmmod radeon and rmmod drm, then...
MostAwesomeDude: # modprobe drm debug=1
MostAwesomeDude: # modprobe radeon
MostAwesomeDude: It should spew a wall of text into dmesg.
MostAwesomeDude: Wait.
MostAwesomeDude: Are you checking /var/log/dmesg, or the output of the dmesg command?
markinfo: ??? I was checking /var/log/syslog ...... /var/log/dmesg seems to be not changing at all - or at least very seldom.
MostAwesomeDude: Check the output of the dmesg command. :3
MostAwesomeDude: That's the *actual* kernel log.
markinfo: tail -f /var/log/syslog is nearly identical with dmesg. Yes there is only [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on minor 0 even i set up modprobe drm debug=1
MostAwesomeDude: So if you do # dmesg | grep drm
MostAwesomeDude: What do you get?
markinfo: [drm] Module unloaded
markinfo: [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on minor 0
markinfo: [drm] Module unloaded
markinfo: [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on minor 0
markinfo: as i inserted them a few times
MostAwesomeDude: That's really really weird.
markinfo: could it be caused that my radeon mobility is a bit specific? For example my notebook has DVI output.
markinfo: it has somehow worked before - with older kernel with fglrfx ...but there was also some problems.
markinfo: I never managed to activate this external DVI aoutpu - only with fglrfx - but it was also somehow distorted.
markinfo: MostAwesomeDude, should i try to install Ubuntu Karmic - or make new instalation of debian testing? I have enouch place - i need to make only new logical volume and install there.
markinfo: debian-xfce:/home/marek# modprobe radeon modeset=1
markinfo: FATAL: Error inserting radeon (/lib/modules/2.6.31-5.dmz.4-liquorix-amd64/kernel/drivers/gpu/drm/radeon/radeon.ko): Unknown symbol in module, or unknown parameter (see dmesg)
edman007: so if i want to run compiz, what do i need to do?
davo: hi all. i'm trying to get X to display in the maximum resolution that my monitor/graphics card support.
yangman: davo: not working?