snipex77: udovdh: are you here ?
udovdh: yes
snipex77: wow
snipex77: thats fast
snipex77: anyway
snipex77: how do i install radeonhd under fedora 8 ?
udovdh: you get the rpm
udovdh: yum install radeonhd
udovdh: then you edit /etc/X11/xorg.conf
snipex77: No package radeonhd available.
snipex77: Nothing to do
udovdh: or maybe use the normal desktop tools to switch driver and mode
udovdh: then you must add a repo I guess.
snipex77: yo
snipex77: i found somthing
snipex77: xorg-x11-drv-radeonhd
udovdh: http://koji.fedoraproject.org/koji/buildinfo?buildID=29303
udovdh: name looks OK
udovdh: you can also just build from git
udovdh: if you comfortable doing that
snipex77: do i download it from website or install from package manager ???
snipex77: oh btw
snipex77: in package manager
snipex77: next to the name
udovdh: you can download the rpm from the url I gave you
udovdh: choose the right build for your PC
udovdh: later you can correct the package manager repo thing
udovdh: once you download the rpm
udovdh: you do
snipex77: nope
udovdh: rpm -ivh nameofthe.rpm
udovdh: nope?
snipex77: radeonhd from the package manager is newer
snipex77: its something like 1.1.0-0.3...
udovdh: then you choose that one
udovdh: they'll both work I guess
snipex77: it's installed
udovdh: then edit xorg.conf
snipex77: yuhuuuu
udovdh: it's in /etc/X11
snipex77: i was able to choose radeonhd under display settings
snipex77: :)
udovdh: if that works...
snipex77: restarting
udovdh: then you can restart X to see if it works for you
blaz: fck everything
blaz: failed to start ur graphical interface
blaz: bla bla bla
blaz: would i like to view the x server output to diagnose the problem ?
blaz: udovdh: some help ?
blaz: wow wow wow
udovdh: yes
blaz: what a short report
blaz: wheres libvd ?
blaz: i need him
udovdh: you can edit xorg.conf to return to the driver you were using before
blaz: nonono
blaz: 2x : Module build in
blaz: RADEONHD : RandR: No valid modes. Disabled
blaz: RADEONHD: Failed to detecta connected monitor.
blaz: Screens found, but none have usable configuration
blaz: Fatal server error : No screens found
udovdh: oh
udovdh: your ddc doesn't work
udovdh: I had a similar issue with a crt monitor I have
blaz: i got LCD monitor
blaz: whats ddc ?
udovdh: LCD dos not matter
udovdh: ddc is the plug and play protocol
blaz: i can tell u last lines of detailed X server crash
udovdh: that the video card uses to ask the monitor what modes it can do
blaz: k
udovdh: so that you get a stable picture
blaz: now
udovdh: and not blow up the crt monitor like in the old days
blaz: radeonhd is trying to be smart
udovdh: so just revert to the old driver for now
udovdh: and wait for libv or another developer
blaz: i told my comp i want 1440x900 !!!
blaz: libv: is here
udovdh: they can help find out why your monitor is not detected
blaz: sir yes sir
udovdh: ping libv
udovdh: maybe you must turn your monitor off
udovdh: and power it on again just to be sure
udovdh: and restart X
udovdh: it might help (small chance)
udovdh: if you can ssh into that machine
udovdh: you can assist libv with the rhd_conntest tool
blaz: udovdh: after it asks me to view X, it gets me into text mode
the-me: hmm
udovdh: no problem blaz
udovdh: go to /etc/X11
udovdh: and edit xorg.conf
udovdh: replace radeonhd mention by vesa
the-me: if I completly hardcode the x and y dpi settings (http://nopaste.linux-dev.org/?371) to 97x95 xdpyinfo reports still 98x98
udovdh: save xorg.conf
blaz: im afraid radeonhd severely changed X
udovdh: the-me, can you generate a log? send it to the developers
udovdh: blaz: radeonhd is only 1 file on the HD
udovdh: did you get the fedora DVD already?
blaz: yes of course
udovdh: did you install it, blaz?
blaz: no, i didnt
blaz: im still doing it off ubuntu ultimate
blaz: !!!!!
blaz: of course i installed it !
udovdh: it might help to diagnose the problem you appear to have
udovdh: trying a different monitor might help as well
blaz: udovdh: just tell me how to restart comp from text mode
udovdh: why restart the comp?
blaz: just 2 be sure
udovdh: not necessary
udovdh: type:
udovdh: who -r
blaz: as you say, my lord
blaz: :P
udovdh: what runlevel do you have?
blaz: 5
udovdh: type:
udovdh: init 3
blaz: with root ?
udovdh: yes
udovdh: what else?
udovdh: your a sysadmin now
blaz: init : command not found
udovdh: /sbin/init 3
udovdh: you typed su instead of su -
blaz: init : command found
blaz: :P
udovdh: ok
blaz: yes
blaz: su
udovdh: now go to /etc/X11
udovdh: so type
blaz: whats the difference ?
udovdh: cd /etc/X11
blaz: im not a newb
udovdh: has to do with setting up a full environment
udovdh: now edit xorg.conf
udovdh: and replace radeonhd by vesa
udovdh: or any driver that works for you
blaz: yh
udovdh: ?
the-me: udovdh, your email?
udovdh: the-me, why? I am not a developer
blaz: i already did that
blaz: from runlevel 5
the-me: udovdh, oh :)
udovdh: the-me, see the wiki for getting info to the developers
blaz: why are runlevels so important ?
udovdh: the-me, xorg log might also have an email
udovdh: blaz, runlevel can help you restart x without booting the PC
udovdh: blaz, is the driver set to vesa in xorg.conf?
udovdh: blaz, if the edit was made type:
udovdh: /sbin/init 5
udovdh: so that xorg will start again
udovdh: blaz, ping?
blaz: udovdh: sorry, i was afk
blaz: what ping
blaz: o yes, i changed that
blaz: now im in graphics mode again
udovdh: see
udovdh: without rebooting
udovdh: if devellopers are around you can switch back and forth very easily
udovdh: just keep two copies of xorg.conf around
udovdh: one with radeonhd
udovdh: one with vesa
udovdh: and copy one of them to xorg.conf
udovdh: now make ssh work to the machine with the radeonhd problem
udovdh: so you can use irc with the developers and also work on the problem machine without graphics
blaz: udovdh: do you know what router is ?
udovdh: a router?
udovdh: sure
blaz: do you know that you have to configure router for ssh ?
udovdh: your ssh is locally
udovdh: so no routing needed
udovdh: so no config needed
udovdh: and even if it were outbound no reconfig was needed
blaz: do you know that im not such a pro to use ssh ?
blaz: yes, it was needed
udovdh: only for inboud stuff you might need to open a port perhaps
blaz: and forward the port to my comp
udovdh: what is different between a session via ssh and a local session?
Dioxin: hopefully someone can help me... I'm a bit new to Unix, I've downloaded RadeonHD and its on my system, I've unzipped it and managed to remove it from the tar.... what do I do next
Dioxin: the instructions say to use ./autogen.sh but this appears to be missing from my system
egore: logs of this channel are now available at: http://people.freedesktop.org/~cbrill/dri-log/
soc: hi
snipex77: hi
soc: something new in git to test?
arekm: is having problem with radeon mobility x1400: 0x7145:0x1043:0x1333: Query for AtomBIOS Get Panel EDID: failed
arekm: this ends with: (II) RADEONHD(0): Setting screen physical size to 370 x 277 while real size is 310 x 230
arekm: radeonhd 1.1.0
arekm: version from git gives me the same result
arekm: used workaround with displaysize for now
snipex77: libvde: are you here ?
Miklu: Hello! Does anyone know where I can get triakis.pkg? Please PM
snipex77: libvde: are you here ?
aneas: radeonhd driver, ATI x1700, RandR 1.2, Notebook + external Monitor. 'xrandr' displays 2 connected monitors, "PANEL" and "DVI-D_1". i want to change the mode on "DVI-D_1", but 'xrandr --output DVI-D_1 -s 0' doesnt change anything
Miklu: anyone have that triakis.pkg file?
snipex77: libvde
snipex77: are you here?
snipex77: libvde: come back !
Miklu: Where I can download triakis.pkg?
yangman: Miklu: I doubt you'll ever get an answer to that here
Miklu: why?
yangman: and it's not a relevant question for this channel, as far as I can figure out what that is
Miklu: many people have got a link from here
yangman: I doubt it. if that's the case, then it would show up on the public channel log
yangman: just to satisfy my own curiosity, I looked this up some more
yangman: I think you want #radeonhd on irc.osx86.hu
yangman: not freenode
Miklu: Ok thx man! Have to go there
Agiofws: hello
Agiofws: i have reported this bug on bugzilla http://ati.cchtml.com/show_bug.cgi?id=999 but from the time that i changed from fglrx to radeonhd the bug has not repeated its self ... when will radeonHD support 3d acc glx aiglx .... ? and how often does radeonhd up date do i just pull a new verion with git ? what version do i have now and what version is now on the servers that distribute it ?
Agiofws: i have reported this bug on bugzilla http://ati.cchtml.com/show_bug.cgi?id=999 but from the time that i changed from fglrx to radeonhd the bug has not repeated its self ... when will radeonHD support 3d acc glx aiglx .... ? and how often does radeonhd up date do i just pull a new verion with git ? what version do i have now and what version is now on the servers that distribute it ?
Agiofws: someone tell me why when i connect a second screen to my laptop my driver things that the MAIN screen is the external screen and not the laptops panel ?
Agiofws: someone tell me why when i connect a second screen to my laptop my driver thinks that the MAIN screen is the external screen and not the laptops panel ?
bobbens: you should be able to define which one is primary in xorg.conf
bobbens: man radeonhd
bobbens: should have a manpage (i use radeon, not radeonhd :) )
Agiofws: bobbens, whats the difference ?
bobbens: radeon is for r200 and r300 chipsets, radeonhd is for r500 and r600 chipsets
bobbens: r400 are radeon too :P
bobbens: but they should be similar
bobbens: and radeonhd will take a while to support 3d and friends, but it'll do it much better then fglrx :)
Agiofws: i have a radeon 2600hd
bobbens: just sit back and relax
bobbens: there's alot of talk and things are progressing
Agiofws: well i think it already better
Agiofws: fglrx gives me this bug
Agiofws: http://ati.cchtml.com/show_bug.cgi?id=999
bobbens: fglrx gave me endless headaches
bobbens: open source gives me waaaaay fewer :)
Agiofws: and i hade 600FPS
Agiofws: on a dualcore +2gb ram
airlied: bobbens: radeon runs all chipsets..
greg_: What is the best way to get involved with the radeonhd project? Specifically if I want to get involved in development where is help needed?
libvde: hi greg_
greg_: hello
libvde: we currently are working our way through rv620/rv635 support and r5xx acceleration
libvde: the best way to become involved at the moment is to try our driver and find bugs, and help out fixing bugs, as there are plenty around
greg_: I just bought a 2600hd card just for that purpose.
libvde: great :)
libvde: is it working ok for you?
greg_: I just ordered it.
greg_: I am very excited about AMD's attitude toward open development.
libvde: ah, ok, we hope we can get you some acceleration for you this quarter still
greg_: About 15 years ago I order a register programming manual from S3 for one of their chipesets so I could contribute to the XF86 code base. They sent it to me. I have been following development of graphics on open platforms since, and have been very disappointed with the attitude of the chipset manufacturers. I am very excited about AMD's new attitude!
libvde: yeah, those were the days
libvde: i keep a tseng et4000 datasheet on my desk :)
libvde: lifesaver whenever i need to deal with anything VGA
libvde: back when we proposed the freeing of documentation, we only gave ourselves a small chance, but we still went for it
libvde: but AMD went for it too :)
greg_: What it the critical path to releasing the GPU documentation?
libvde: creating it :)
greg_: That is kind of what I thought.
greg_: That is a serious investment for AMD to make.
libvde: but then, just dropping documentation on the floor and then stating "here you have it, now shut up and do everything yourself" is not really nice. We're actually writing hw support alongside as well
libvde: s/hw/driver/
greg_: Are you with AMD?
libvde: i am with SUSE
greg_: So what exactly is the relationship between AMD and SUSE?
libvde: AMD is this really open hardware vendor that likes to see its hardware supported decently and early. SUSE has been helping AMD with that ever since the AMD64 days
libvde: and now this is extended to graphics drivers as well :)
libvde: supported... meaning, supported under linux :)
greg_: Yeah, back to the days of the S3 manual.... I bought an ATI graphics card, and couldn't get it to work. So I bought something else that was better supported in X. I found out that ATI was not releasing information about their hardware so I was SOL unless I was running windows. I have been anti-ATI ever since. Now that AMD is in the picture, I have changed my mind an hence, the new purchase.
libvde: right, good choice
libvde: for r630 we currently should have basic driver and modesetting working rather well
greg_: It would be fun to compare the architecture to my old Mach64 card to my to r630
libvde: there is no hardware acceleration yet
libvde: but with shadowFB and hardware cursor, things work decent for most people
libvde: i hear a lot of people state that our driver feels faster than fglrx, but that is mostly due to their cpu and due to the bandwidth of pciexpress than anything else :)
greg_: I know. I reviewed the docs AMD published, so I know what is available.
libvde: :)
greg_: ?
greg_: why would that be?
libvde: what?
libvde: shadowfb faster than hw acceleration?
greg_: That the drivers would feel faster?
greg_: exactly
libvde: well, shadowfb keeps a copy of the scanoutbuffer in main ram and only writes out to fb from time to time
greg_: time to time meaning after a screen change
libvde: i think it just tries to combine some things together
libvde: and then, it only copies over the newly touched bits to the framebuffer
libvde: it is of course much better to have hardware acceleration
libvde: but it is good enough for basic usage
greg_: I understand
greg_: I can't wait to get it running.
greg_: And then to dive into the code.
libvde: :)
greg_: and then to play with tv-out, hd-out, etc
libvde: right, tv out is currently up in the air
greg_: ?
libvde: we aren't certain yet how it should be used
greg_: ?
libvde: we barely know what it looks like
libvde: yeah, same thing here :)
libvde: for working tv you depend on quite a few subsystems