haggai: Hi everyone. Can anyone help me solve http://bugs.freedesktop.org/show_bug.cgi?id=14216 ? I can only use a monitor on my Analogue output, the monitor is not detected on the DVI output.
arekm: try ati driver from git maybe
arekm: ah, it is git
haggai: yup :) I saw there was some stuff to get more info from the Bios in git so I tried it
Zoopee: OK I updated to xf86-video-ati from git.
Zoopee: Still I get only one screen.
Zoopee: Except for two screen and two device sections, what do I need?
haggai: Zoopee: I'm trying to get help to solve another problem so I can't really tell you much :) But from what I've seen on the mailing lists, you need to provide logs from the X server and xrandr. Is there a bugzilla bug open for your problem already?
umtc: i was told that it was supposed to be backwards compatible with our old configuration files, so that should work. could i see xrandr output?
haggai: umtc: who's xrandr ouptut did you want to see? Zoopee or mine?
umtc: he's trying to migrate the same setup as me, two independent screens
agd5f: haggai: XPRESS chips use sdvo for DVI, whether it works or not is somewhat luck. I do plan to fix it, but it hard finding info on the chips
haggai: agd5f: what is involved in fixing it? Is it a case of experimenting with reading the chip registers, or something else? Is there any existing code to implement sdvo that can be used, or does the whole lot need writing?
agd5f: haggai: I need to find the internal documentation on how it works. there are some new registers involved
haggai: agd5f: ah. And you have access to that somehow?
haggai: agd5f: is there anything I can do in the meantime?
agd5f: haggai: I work for AMD :)
haggai: agd5f: ah sorry :) I just recognised your name from the savage ML
agd5f: haggai: used to hack on savage too :)
haggai: right, didn't occur to me you might be working for amd now
OipOS: Compiz hard locks my X server instantly when started :(
rx__: :)
umtc: i finally broke down and installed that "git" program and i've got the latest version now. a few notes
umtc: zaphod mode is not config-file backwards compatible with the way it is specified in 6.6.x, if so then only the primary screen appears in xrandr and you get a system freeze on x quit
umtc: how do you create another screen number with xrandr? i can't just specify another screen line in xorg.conf without all the entries to back it up
agd5f: umtc: xrandr != zaphod
agd5f: umtc: you can pass the display to xrandr. see xrandr --help
umtc: am i not supposed to use it to configure it?
umtc: also, modify my earlier statement of a freeze to be just "monitors stay in dpms off mode in console"
werdz: BphFDFgt
umtc: i see about the -d :0.1, i thought since xrandr said "screen 0" by default, it would list "screen 1" after that if it existed
umtc: looks like edid reading from that monitor fails, and xv displays green with junk picture
umtc: normal x items seem to work
umtc: looks like xv brings a signal 11 also
agd5f: xv is busted with zaphod
agd5f: as we don't properly tack the overlay in that case
agd5f: *track
umtc: ok, regular x applications are a start
umtc: would you want me to post the xorg.conf/xorglog somewhere for the edid failure?
Zerizzle0: anyone know how to get a "ATI Radeon® Xpress 1150 256MB HyperMemoryTM (integrated)" working? in Fedora?
umtc: actually, i don't think it's xv causing the signal 11. (unless the damage it does persists across x restarts)
umtc: seems to be that starting mozilla causes the signal 11, but it works for about five seconds before it happens
umtc: i'll go back to 6.6 until this becomes more stable and xv, but i'll keep the .so files to do any debugging on request
agd5f: umtc: see if you can get a bt
umtc: it's not mozilla's fault, it's just happening when you move the cursor to the rightmost pixel on the primary screen. i'll go look up how to get a trace of xorg
agd5f: umtc: https://wiki.ubuntu.com/DebuggingXorg
agd5f: there's also a page on wiki.x.org
umtc: it'll have to wait until the screens are fixed after quitting x
sytse: zaphod mode?
sytse: I'm guessing that's 'multi head' mode :]
Zerizzle0: anyone know how to get a "ATI Radeon® Xpress 1150 256MB HyperMemoryTM (integrated)" working? in Fedora?
sytse: I'm guessing you have about.. a gazillion options :)
sytse: but if you want acceleration, probably the best way would still be fglrx :(
agd5f: Zerizzle0: try it and see?
airlied: Zerizzle0: fedora 8 should just work..
Zerizzle0: fedora does work but gaming is the problem like running css with wine just crashes and it wont use the radeon driver
airlied: Zerizzle0: you might need to enable DRI, which may or may not work, we don't fully support all the Xpress chipsets unfortuantely..
airlied: Option "DRI" "On" in Device section of xorg.conf
airlied: but it may just lockup..
Zerizzle0: ok ill try that .. also when i set under device in xorg.conf to "radeon" instead of "fglrx" it wont load X at all =\ brb
Zerizzle0: uggh still crashes and my screen rez is like 600X400 or something lol/
Zerizzle0: maybe theres something wrong in my xorg.conf? ..http://rafb.net/p/DdpbcN57.html
slango: is tv-out working on the radeon mobility 9700 with the radeon driver yet?
agd5f: slango: should work
damentz__: hey agd5f
damentz: the new pll patches didn't help
agd5f: damentz: what new pll patches?
damentz: 4 days ago
damentz: Alex Deucher
damentz: RADEON: re-work i2c for DDC
damentz: commit | commitdiff
damentz: 5 days ago
damentz: Alex Deucher
damentz: RADEON: get dac2 adj values from the bios tables
damentz: commit | commitdiff
damentz: 5 days ago
damentz: Alex Deucher
damentz: RADEON: grab pll_in_min/pll_in_max from bios tables ...
damentz: commit | commitdiff
damentz: umm, those...
agd5f: right. yeah, I doubt they would help anyway
damentz: rx__: helped me figure out how to compile this stuff
damentz: well configure at least
damentz: ./autoconf --prefix=/usr... thats new to me
slango: agd5f, what version of the driver does it work in, and how do I check which version i have?
agd5f: slango: for ntsc it's worked for the whole 6.7.19x series, for pal you need git master
slango: agd5f, really? how do I get it working?
slango: I've never been able to get it to work
agd5f: damentz: give this patch a try: http://www.botchco.com/alex/xorg/damentz.diff
agd5f: slango: it doesn't auto-detect by default
agd5f: slango: xrandr --addmode S-video 800x600; xrandr --output S-video --mode 800x600
damentz: agd5f: errr, hunk failures
damentz: do i need to use an older version?
agd5f: damentz: ati git master
damentz: ok
damentz: how to i update git?
agd5f: git pull origin master
damentz: it says already up-to-date
damentz: agd5f: so i guess you were working on a different version?
agd5f: no I'm on master
agd5f: patch -p1 -i damentz.diff
damentz: still fails
damentz: OH
damentz: wrong patch
damentz: sorry man
damentz: just checked
damentz: ok it patched
damentz: agd5f: ugh, no go
damentz: it did longer than usual for X to start the screen though
damentz: but when i got in and changed the res, screen goes white again
slango: agd5f, do I have to run those xrandr commands each time I startup?
slango: do I add them to my .xinitrc for example, or do I just run them once and enjoy forever
agd5f: slango: there are xorg options to try load detection or force tv-out to always be on
agd5f: config options
agd5f: Option "ForceTVOut" "true" will force it on always
agd5f: Option "TVDACLoadDetect" "true" will turn on load detect which may or may not work for you
slango: agd5f, hmm... I just switched to radeon in my xorg.conf file, and restarted X and tv-out worked
slango: did I not restart X enough for the new driver to kick in?
agd5f: slango: ?
rx__: the forcetvout may not be necessary
rx__: i think the force implies it's a quirk :)
slango: hmm... nevermind. edited the wrong device section
rx__: oh.. eh
slango: alright, now TV-out is working. I just need to get my resolution back on track
slango: oh no!
slango: video is not playing on my TV!
slango: it plays fine on the laptop screen (better than with fglrx even), but I just get a black screen on the TV when I try to play video
slango: it works otherwise
slango: any ideas about what might be causing that?
agd5f: slango: overlay only works on one crtc at a time
agd5f: if you are using clone mode you ahve to pick which crtc to use
rx__: oh.. no wonder you have to pick primary/secondary in windows..
agd5f: xvattr -a XV_CRTC -v 1
slango: agd5f, two issues with that.... first, I'm using a laptop, so i have one lcd, one crt in my setup. Second, how can I not use clone mode? it would actually be far more convenient to split the desktops and make myth run on the TV
agd5f: slango: xrandr --output S-video --right-of LVDS
slango: agd5f, and is their an xorg.conf equivalent setting for that?
agd5f: slango: http://www.intellinuxgraphics.com/dualhead.html
agd5f: basically add a monitor section and assign it to S-video and add Option "RightOf" "LVDS"
agd5f: to the monitor section
slango: perfect
slango: agd5f, that article is helping, but I'm getting "Error, screen can not be larger than 1280x1200 (desired size is 2080x800)" when I run the xrandr command you suggested
agd5f: slango: you'll need to add a virtual line
agd5f: virtual 2080 800
agd5f: see the bottom of that page
slango: alright
slango: I'm starting my xorg.conf from scratch
slango: because it's WAY messed up now
slango: agd5f, is it possible for me to do 800x600 on the TV and 1280x800 on the LCD?
slango: or should I not even try for that?
umtc: i've done that
agd5f: slango: yes
agd5f: slango: all you needed is that virual line
slango: agd5f, great
slango: I think I should be good to go now
umtc: slango, how do you avoid the problem of the mouse wandering into the second display?
slango: agd5f, alright last one. Is there a xorg.conf alternative to this line that you gave me: xvattr -a XV_CRTC -v 1
agd5f: nope. but you don't need it for dualhead
agd5f: with dualhead the overlay will follow the window
slango: agd5f, hmm.. it's not doing so in this case...
agd5f: slango: are you runnign dualhead or clone?
slango: agd5f, there was a setting in Myth's configuration that I missed
agd5f: cool. working now?
slango: agd5f, I am so close to sending you flowers or candy or a hooker
slango: thanks for your help
slango: this is incredible
slango: everything that I didn't like about my setup is now fantastic
agd5f: heh :)
slango: hmm
slango: it seems I have another question...
slango: right now, there is a black bar on the left side of my screen. what might be causing that?
slango: it's not caused by Myth... it seems that the screen just isn't stretching far enough to the left on that monitor...
slango: or that it's offset to the right somehow
agd5f: slango: TV? you can adjust the tv image with the output attributes
agd5f: xrandr --verbose to see what's available
agd5f: then xrandr --output S-video --set tv_horizontal_position 2
agd5f: etc.