udovdh: any updates?
boris: hi
boris: ive got sapphire HD2600 PRO and radeonhd doesnt seem to start, instead vesa starts
boris: here is my Xorg
boris: http://pastebin.com/m2699fa24
boris: can somebody check if everything is ok ?
boris: oh btw, i used instructions from phoronix, i got ubuntu ultimate 1.6
udovdh: hmmm, I am no expert, but the xorg.conf looks OK
boris: ok
reist: ditto, but the xorg.conf looks a bit off
udovdh: Device section is most important I guess
udovdh: Section "Device"
udovdh: Identifier "Videocard0"
udovdh: Driver "radeonhd"
udovdh: EndSection
udovdh: is mine
reist: boris: can you change the Device and Monitor in section "Screen" to the names the identifiers in your file?
boris: reist: what '
boris: oh
boris: ive set Identifier myself
udovdh: yes, the conf can loose the modelines and modes
boris: i dont believe that changes anything ?
reist: i mean
reist: #
reist: Device "Failsafe Device"
reist: #
reist: Monitor "Failsafe Monitor"
udovdh: it is just a label
reist: really? xorg ignores these two lines in "Screen"?
reist: in my experience, it always looks at least at the Device line
udovdh: see mine: http://pastebin.com/d6c363904
udovdh: and mine works
udovdh: maybe change or remove the Virtual line
udovdh: and moit the commented lines
udovdh: omit...
udovdh: I have been using the conf since 1.0.0 of the driver
reist: udovdh: yeah, because yours has the correct ids in "Screen" for your other sections
reist: I think Failsafe is the vesa driver on Ubuntu
udovdh: so boris, give it a try
udovdh: with xrandr you can, if it works, switch modes, add modes, etc
udovdh: gotta do something will be back in 15 minutes
boris: i got ubuntu ultimate
boris: i changed my xorg now
boris: pray for me
boris: still doesnt work
boris: somebody please change it so that it will work
boris: my native resolution is 1440x900@60
boris: ive got Sapphire ATI Radeon HD2600 PRO
boris: my monitor is Samsung SyncMaster 940NW
reist: boris: what did you try to do?
boris: reist: changed xorg a bit
boris: changed resolutions and video card to "Videocard0"
boris: also, i changed my screen to Screen0, i think
boris: http://pastebin.com/d50171bdc
reist: boris: did you change both the Identifier line in 'Section "Device"' and the Device line in 'Section "Screen"' to "Videocard0" ?
boris: don't know
boris: please, change my xorg to what it should be like
reist: boris: try this one: http://pastebin.com/m119cc48e
boris: reist: OK, rebooting
udovdh: no
udovdh: ah
udovdh: a reboot for X!?
boris: damn
boris: still doesnt work
boris: i get a bluish ubunu splash screen
boris: anyway
boris: (i got ubuntu ultimate edition 1.6)
boris: after the splash screen, a "wizard" appears, tellin me im running in low video mode and asking me what driver it should use
boris: but i dont see any "radeonhd"
udovdh: boris...
udovdh: you do not have to reboot to try a video driver
udovdh: just restart x
udovdh: e.g.
udovdh: do init 3
udovdh: init 5
udovdh: or restart x by ctrl-alt-backspace
boris: what about ctrl alt backspace =
boris: k
udovdh: then your problem:
udovdh: are you sure you have the radeonhd driver in the right place on the PC?
udovdh: on my F8 box it is in /usr/lib64/xorg/modules/drivers/radeonhd_drv.so
boris: ive got it in /home/boris/xf86-video-radeonhd
udovdh: because the failsafe thing makes me wonder about the fact that the driver you specify might not be there
udovdh: I don't think X will look there for it?
boris: wait, ill check
udovdh: if your system is 32-bit it might be
udovdh: /usr/lib/xorg/modules/drivers/radeonhd_drv.so
boris: radeonhd_drv.so
boris: its there
boris: also
boris: radeonhd_drv.la
udovdh: on the path I just pasted?
udovdh: la is not thr right one?
udovdh: we need .so
boris: both
boris: there are both
boris: .so and .la
udovdh: in /usr/lib/xorg/modules/drivers/
udovdh: ?
boris: ye
udovdh: ok
udovdh: is there a /var/log/Xorg.0.log?
udovdh: I am not a developer but maybe someone can see in there what goes wrong if you are using the right config
boris: yep
udovdh: and have the driver in the rigth spot
udovdh: but end up with vesa
udovdh: any error or warning lines in there?
boris: http://pastebin.com/mf525e2a
boris: udovdh: i can choose which driver i want
boris: there's plenty of em
reist: ...i think i missed one thing - you should delete the xorg.conf.failsafe files from /etc/X11
boris: oh, btw, my card is AGP
reist: or some file with a similar name
boris: sir, yes sir !
reist: otherwise ubuntu fill replace xorg.conf with that one
udovdh: AGP hdpro?
udovdh: is that possible?
boris: yes
boris: reist: done !
reist: boris: and now fix up the xorg.conf
boris: reist : but there's still xorg.conf.failsafe.bak
udovdh: you can remove that one as well
reist: delete that one too, to be on the safe side
udovdh: maybe also clean out /var/log/Xorg*log before restarting X?
reist: also, update your xorg.conf file
reist: because it currently will load vesa
udovdh: yust use mine or reist's
boris: yo
boris: look what i found
boris: # This file was generated by failsafeDexconf, using
boris: # values from the debconf database and some overrides to use vesa mode.
boris: #
boris: # You should use dexconf or another such tool for creating a "real" xorg.conf
boris: # For example:
boris: sudo dpkg-reconfigure -phigh xserver-xorg
boris: do i do that ?
udovdh: don't need that now
boris: ok
udovdh: a minimal xorg.conf will work
boris: so ctrl alt backspace ?
udovdh: if the xorg.conf mentions radeonhd and is as it should be?
udovdh: maybe do a pastebin to be sure?
boris: ok
udovdh: reist can then have a look
udovdh: if it is OK make a backup copy and restart x
boris: http://pastebin.com/m612d84da
boris: brb
udovdh: can be a lot smoller
udovdh: smaller
udovdh: you do not need the modes
udovdh: nor the modelines
udovdh: butbasically it is OK
boris: ok
reist: i agree
udovdh: reist, what do you think?
boris: so ctrl alt backspace ?
reist: yep
boris: gr8
boris: just gr8
boris: so here i am, back with vesa
udovdh: hmmm
reist: boris: can you pastebin Xorg.0.log.old?
boris: what about if i uninstall it ?
udovdh: don't do that yet boris
boris: why not Xorg.0.log.new ? :P
udovdh: just let us see
boris: reist : i also got Xorg.0.log
reist: well, there should be two logs from just now
boris: yeh
reist: .log will show you vesa and Failsafe taking over
reist: .log.old should show the error with radeonhd
boris: which 1 do i post '
reist: so post Xorg.0.log.old
boris: http://pastebin.com/m1ca4352b
boris: old 1
reist: ...i think this is what you should try:
reist: go to init 3
boris: how ?
boris: sudo init 3 =
boris: ?*
reist: yes, that should do it
reist: after that
boris: yes ?
reist: check that there is no gdm or X running with 'ps aux'
boris: wait wait wait
boris: im still in X
reist: after you run 'init 3' X should shut down and you will be in text mode
boris: reist: im not in text mode
boris: else konversation would quit
reist: oh...
boris: i can get into failsafe ?
boris: and join this channel from my other comp
udovdh: you can
udovdh: or get back to x with
udovdh: init 5
udovdh: (form a text console)
boris: not every time
boris: ok
boris: brb
udovdh: when hardware is in a sane state
udovdh: you can
blaz: im here
reist: failsafe mode is annoying - it's a program wrapping X, so it seems even ctrl-alt-backspace leaves you right in it :/
reist: which means killing it probably should be done from the console
blaz: ????
blaz: im already in console
blaz: or no
reist: blaz: in a window, or a text screen?
blaz: seems it hung
blaz: text screen
blaz: Assuming drive cache: write through
blaz: eh
blaz: i just had to press enter
blaz: *Awaiting further instructions*
reist: ok, now type 'ps ax'
blaz: you mean ps ax more
blaz: i cant scroll, remember
reist: don't shift+pageup and shift+pagedown work for you?
blaz: not in text mode
blaz: i didnt use shift anyway
reist: i see
reist: so use ps ax with more and see if there are any gdm or X processes still runing
reist: if there are, kill them with kill -9
reist: as well anything with "Failsafe" in it's name
blaz: seems no
udovdh: looks good
reist: yeah
udovdh: maybe try to start just X
blaz: what looks good
udovdh: with logverbose 7?
reist: no no no
blaz: with startx ?
udovdh: no
blaz: ok, no
reist: first check that there are no failsafe conf files in /etc/X11
udovdh: indeed
blaz: xorg.conf.failsafe
reist: and replace xorg.conf - it probably reverted to Failsafe again :/
blaz: delete ?
udovdh: yes
blaz: should section module be there ?
udovdh: try this one http://pastebin.com/d6c363904
blaz: wait wait wait
blaz: how am i supposed to put it in ?
blaz: im gonna have to work 30 mins !
udovdh: copy the text
blaz: im in text mode
blaz: i aint got firefox
udovdh: does lynx work?
blaz: lynx ????
reist: or links?
reist: text mode browsers
udovdh: or copy the text on one pc
udovdh: and put it in a file
udovdh: then copy it to the otehr one
udovdh: in /etc/X11/xorg.conf
udovdh: whatever you feel comfortable with
udovdh: if you have an email I might even email it to you
blaz: how am i supposed to reach it ?!
udovdh: no network?
udovdh: usb stick?
blaz: no
udovdh: ftp?
udovdh: scp?
blaz: network yes
blaz: no and no
udovdh: ssh?
blaz: if i add user
udovdh: ssh boxwithXproblem
blaz: but i dont kno how 2 use it
udovdh: cant ssh with root?
udovdh: useradd newuser
blaz: dono
udovdh: passwd newyuser
udovdh: bla
udovdh: bla
udovdh: and you are done
blaz: yes, and what else
blaz: ill try to put it on cd
udovdh: then ssh newuser@boxwithproblem
udovdh: su -
udovdh: #
udovdh: vi /etc/X11/xorg.conf
udovdh: and paste the conf in the ssh session
udovdh: you know vi?
blaz: ye
blaz: just wait
blaz: oh
blaz: here goes whole saturday.....
udovdh: no. can be close now
udovdh: does useradd work on the problembox?
udovdh: first just try ssh to the problembox
udovdh: without creating a user
dusan: gimme that link again
dusan: udovdh
dusan: xorg
udovdh: http://pastebin.com/d6c363904 ?
udovdh: or /etc/X11/xorg.conf
dusan: xorg
dusan: you know
dusan: the xorg for radeonhd
udovdh: http://pastebin.com/d6c363904 works for me
udovdh: you cna take out the commented lines
udovdh: and the Virtual line
udovdh: does it work?
dusan: no
dusan: it seems my comp cant read usb
dusan: disk
dusan: well, it does open it, but says its empty
dusan: now im gonna write xorg file to cd
udovdh: no network?
udovdh: did you unmount/eject the usb from the pc wher you wrote to it?
udovdh: spoiling a cdr for a file of a few bytes is not necessary
blaz: yes i di
blaz: d
blaz: links says it cant find host
pasky: Hi, is there any way how can I help with development of acceleration support for radeonhd? Has the specs already been released? Is there any timeframe in which it is expected to be released?
udovdh: lynx should work if dns is ok
udovdh: pasky, as far as I know amd/ati still have to release specs beyond the modesetting info
blaz: thinkin logicaly could work
blaz: i just had to start x and save the file
blaz: then restart, go into failsafe and replace
blaz: now, my graphics dont work
blaz: cuz i deleted failsafe
udovdh: the whole failsafe thingie is messing with a quite normal setup
udovdh: you can use my very basic config with either the radeonhd driver mention
udovdh: or replace that mention by vesa nd you hav 'failsafe'
udovdh: now you need to be ina situation where you know for sure you start x with radeonhd to debug the problem
udovdh: if you can't do that helping is a problem
udovdh: maybe ask the devlopers when they get online?
blaz: and what else
udovdh: what else?
blaz: my only choice now is to reinstall
blaz: everything
udovdh: just edit the config I gave you
udovdh: not necessary
blaz: i cant get into graphics !
udovdh: vi /etc/X11/xorg.conf
blaz: what ??
udovdh: and change radeonhd into vesa
blaz: oh
blaz: k
udovdh: save the file
udovdh: and restart x
udovdh: should give you grafix because you then use vesa
udovdh: hallo libvde
libvde: morning :)
udovdh: maybe you can help blaz to get radeonhd to work on an AGP 2600 card?
udovdh: for me it is getting towards the evening libv... 16:20 here almost
libvde: hrm... what are the symptoms?
libvde: udovdh: same here :p
udovdh: some failsafe mechanism steps in whenever he tries radeonhd
libvde: ubuntu again?
udovdh: it is on ubuntu if I recall
blaz: no
blaz: ubuntu ultimate
blaz: btw i just got graphics
udovdh: see blaz , vesa works
libvde: blaz: heh, which probably even makes it worse :p
libvde: blaz: is there no Xorg.0.log.old?
udovdh: we removed the failsafe configs
pasky: udovdh: ok... but I wonder, does anyone have any idea on when might they do so?
blaz: just wait
udovdh: and now he has more or less a simple basic xorg.conf
udovdh: now running with vesa
libvde: right, but what is up with the fallback?
udovdh: pasky, later. is being worked on is the word we hear/read
boris: gimme that X link again
boris: udovdh:
pasky: I did a stupid thing, choose radeon card when deciding on my new box, and didn't research state of radeonhd properly before ;-) now I'm stuck with horribly unstable fglrx :(
udovdh: http://pastebin.com/d6c363904
libvde: pasky: why?
pasky: why what?
boris: now pray for me
libvde: pasky: why are you stuck with fglrx?
pasky: libvde: because I want to watch movies and play ddr
libvde: ddr?
pasky: dancedancerevolution ;)
libvde: whatever that is :p
pasky: game, needing 3d acceleration :)
udovdh: movies work pasky
udovdh: just use a bit more cpu
pasky: they didn't work for me - the image was choppy
udovdh: weird. a amd X2 Be2350 does the job here
udovdh: even at 1 GHz
libvde: pasky: the overlay is pretty limited on r5xx and up
libvde: pasky: so we need 3d first
pasky: yes i know about that
pasky: I'd gladly help with the coding
libvde: pasky: maybe things will already get better when we have 2d emulation going on that hardware
reist: udovdh: try to play a movie on a 24", you can SEE the frames switching
blaz: udovdh: did it
blaz: now lets see what happens
pasky: udovdh: i have fairly good cpu, and that wasn't the trouble...
libvde: but this will take a bit, we're still working on rv620/rv635 support and r5xx accel
udovdh: 20" here. I watch diVX and stuff with little trouble
blaz: nooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
libvde: udovdh: is the monitor section really needed?
blaz: again low video thingz
udovdh: in the config?
udovdh: dunno
udovdh: this one works for me
blaz: thingy *
blaz: when i start
libvde: blaz: what is "low video things"?
pasky: libvde: I have RV610 and aside of acceleration, radeonhd worked like a charm for me
blaz: libvde: ubuntu ultimate pops up a window, telling me im running in low video settings, letting me choose monitors default resolution and driver
udovdh: rv630 here pasky , same compliments
blaz: but i dont see radeonhd
libvde: low video settings being vesa
udovdh: blaz, can you open an xterm and use xrandr?
libvde: ubuntu is really horrible. 1.5y ago they totally messed up packaging my unicrome driver
libvde: and now this mess
libvde: trying to be smarter than X driver developers.
libvde: in both cases
blaz: libvde: ubuntu {ULTIMATE}
udovdh: on Fedora I had little trouble
libvde: blaz: and?
blaz: udovdh: what distro u got ?
libvde: why is ultimate supposed to make it better?
libvde: blaz: when did marketing ever change the nature of the beast?
blaz: libvde: i dont think ubuntu has got this low video settings thingy
libvde: blaz: good. install normal ubuntu
blaz: libvde: well, then u tell me what distro to use
blaz: libv
blaz: libvde: gutsy doesnt even attempt to use VESA
libvde: blaz: great!
libvde: blaz: that means it listens to config files
udovdh: haha :-)
blaz: libvde: are you going to help me or discuss ubuntu's bad points ?
libvde: blaz: i do not see anything that could involve me here.
libvde: blaz: if i do not see a log of radeonhd failing, preferably at -logverbose 7, then there is nothing i can do
boris: im here
boris: libvde: what logs, located where =
boris: ?*
libvde: blaz: did you expect me to take another stance here? or would you rather see me work on useful things like, say, rv620/rv635 support or, since i still lack info, on r5xx drm support?
boris: libv
boris: libvde: i was expecting you could tell me whats wrong
libvde: boris: i do not have a crystal ball i can look into
boris: libvde: i tought you said you need logs of radeonhd ?
libvde: yes, and not one of vesa.
libvde: usually it lives at /var/log/Xorg.0.log
boris: i think that's vesa
boris: .old also seems to be vesa
udovdh: init 3
libvde: great, please ebay me a crystal ball
udovdh: rm -f /var/log/Xorg*log
udovdh: vi /etx/X11/xorg.conf
udovdh: edit to use radeonhd
udovdh: X -logverbose 7
udovdh: then kill X
udovdh: revert to vesa
udovdh: and email the log to libv
boris: -logverbose7 ?? i dont know whats that
boris: or where to enter it
boris: btw, X is already set to radeonhd
boris: ill try restarting again
udovdh: ah...
udovdh: read
udovdh: and ask...
blaz: what ?
udovdh: I give the command sto get the right logs
udovdh: when you init 3 you get to text mode
udovdh: you then start X manually and directly
blaz: it doesnt work again
udovdh: with the logverbose option set to 7
blaz: im tired of trying to get this working
udovdh: this way you get more detail in the log
blaz: thanks for help udovdh
udovdh: but we don't have the log with the logverbose 7
udovdh: kill X
udovdh: get to textmode
udovdh: and type:
blaz: how???
udovdh: X -logverbose 7
blaz: from failsafe ?
udovdh: to get to textmode
udovdh: do ctrl-alt-F1
blaz: or graphics session ?
udovdh: log in if necessary
udovdh: and do init 3
udovdh: kill remaining X stuff
udovdh: ctrl-alt-F1....
udovdh: does that work?
blaz: no
blaz: X dissapears
blaz: but i dont get to console
udovdh: and a black screen?
udovdh: strange... should work with vesa
blaz: theres a - blinking
udovdh: cursor
udovdh: then you have textmode
udovdh: but there is no text, no getty working
blaz: i cant type
udovdh: very useful setup?
udovdh: is this an ubuntu thing?
blaz: ?
blaz: dono
blaz: but i installed system today
udovdh: normally you can log in on a few vertual consoles on alt-f1 - f7 or so
blaz: i got ubuntu ultimate
udovdh: dunno if that matters
blaz: maybe thats reason it doesnt work
blaz: meh
blaz: forget it
blaz: im done trying to get it working
blaz: thanks for help
udovdh: make networking work to the problem box
blaz: also, thank you for help, reist
udovdh: and you can use ssh to make stuff easier
blaz: network works
blaz: ive got a strange greenish screen with vesa
blaz: how do i setup ssh ?
udovdh: doesn't ubuntu come with ssh?
udovdh: ssh somebox
udovdh: then you should get a login
blaz: i added a user
blaz: oh
blaz: ive got a router
blaz: btw
udovdh: on the problembox?
blaz: no
blaz: my problembox is in home network
blaz: but i think router is configured to forwars
udovdh: first open a terminal on the not-problematic box
blaz: ye
udovdh: in the termianl type
udovdh: ssh problembox
udovdh: what happens?
boris: ssh: problembox: Name or service not known
boris: just forget it
boris: i dont kno router ip
boris: besides
boris: this took too much time
boris: bye and thanks for help
boris: im not gonna spend the rest of the day on computer
udovdh: router?
boris: ive got a router
udovdh: not literally
boris: ?
udovdh: your problembox has a name or ip
boris: 192.168.100.16
boris: thats home network IP
udovdh: use that ip instead of the problembox label
udovdh: what happens then?
boris: it asks for passwork
boris: password
udovdh: log in...
boris: ye
boris: wait
boris: im loging in to my own comp
boris: why would i do that =
boris: im typing from that comp
boris: udovdh : forget it
boris: bye and thanks for help
udovdh: you are working on a box that is differentr from the problem machine, right?
boris: im repeating that tenth time
yojoe: does radeonhd already supports to set the device to certain power states (like fglrx allows)?
boris: udovdh: no, im working on my problem machine
boris: with vesa and 1024x768
udovdh: well, then you can do what I explained?
udovdh: not bad
boris: do what
boris: omg
udovdh: get a getty working on a text console
boris: i told u i cant get into text mode !!!!!!!!
udovdh: then you can use textmode
blaz: now what ???
udovdh: vi /etc/inittab
blaz: i cant use textmode !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
blaz: unless i get into failsafe !
udovdh: do vi in an xterm
blaz: what xterm
udovdh: you say you have vesa
udovdh: so you can use X
udovdh: so you have an xterm
blaz: whats xterm _
udovdh: a terminalwindow in a graphical environment
blaz: you could have told me that before !
udovdh: pardon?
blaz: i got into failsafe now
blaz: i was in X
udovdh: what is failsafe?
blaz: when you boot up
udovdh: failsafe is useless for us
blaz: you get into GRUB terminal
blaz: i mean menu
blaz: and u select ubuntu failsafe
udovdh: grub is way too lowlevel
udovdh: dont do that
blaz: ok ok
udovdh: just edit the line to say 'single' at the end
udovdh: then boot
udovdh: and you will get single use textmode
blaz: edit what line, for gods sake ?!
udovdh: in grub, slect a kernle entry and press e
blaz: ooommmmgg
udovdh: or is that option disabled?
blaz: I JUST GOT INTO GRAPHICS MODE
udovdh: (hiddenmenu in grub.conf?)
udovdh: do not get into shouting
blaz: im in xterm now
blaz: what do i do ?
udovdh: and what is the boris/blaz/etc thing when you are on the problem box?
udovdh: we can't really understand that
udovdh: if you have a working text session\
udovdh: you can edit inittab
blaz: udovdh:
blaz: my main comp is boris
blaz: my brothers comp is blaz
udovdh: and the problem is on?
blaz: my fathers comp is dusan
blaz: boris
boris: ye
udovdh: so get to blaz
udovdh: and ssh to boris
boris: why
udovdh: it saves you a lot of hassle
boris: im on boris
boris: nonono
boris: just tell me what to do
udovdh: you just need to get to textmode
udovdh: i.e.:
boris: udovdh: what textmode
udovdh: init 3
udovdh: from a terminal window
boris: xterm ?
udovdh: whatever
boris: and now what =
udovdh: you are in textmode now?
boris: init needs to be root
udovdh: you are not root?!
boris: if i was in text mode, konversation would quit
udovdh: become root
boris: with sudo ?
udovdh: su -
boris: k
boris: now what
udovdh: init 3
boris: im not in text mode
boris: root@boris-desktop:/home/boris# init 3
boris: root@boris-desktop:/home/boris#
udovdh: we want to go to textmode
boris: well we cant
udovdh: if inti 3 doesn't work by design
udovdh: we can consider ubuntu ultimate broken
boris: ok
boris: so
udovdh: sorry
boris: reccomend me a distro
boris: opensuse : no
udovdh: you could edit /etc/inittab
udovdh: fedora works for me
udovdh: free
boris: fedora 8 ?
udovdh: indeed
boris: k, ill install it tomorrow
udovdh: even has vesa
udovdh: and no failsafe stuff
libvde: boris: why not, they pay about half of the time spent on this driver of yours.
boris: libvde: you mean about opensuse ?
udovdh: indeed
udovdh: novell does that
boris: libvde: ive had a bad experience with yast
boris: i just didnt like suse
udovdh: MS -> novell -> suse -> libv <- amd/ati
udovdh: ?
libvde: udovdh: pffff :p
udovdh: haha
libvde: udovdh: none of the ms money flows to suse
udovdh: no, it trickels
libvde: udovdh: flows straight to novell stockholders i guess
boris: libvde: you got SuSe ?
libvde: boris: i am an old debian user, but at work i of course use suse
libvde: boris: this because i can directly complain at the person packaging X then :p
libvde: boris: but really, anything is ok if it doesn't try to be too smart
libvde: too smart == failing badly
libvde: suse has its issues too, but every distribution you choose has issues
libvde: so choose fedora, suse, debian, whatever
libvde: just as long as you can get a decent Xorg.0.log out of it
the-me: hmm cute
the-me: what could be the reason why some fonts seems to be bigger with radeonhd as with fglrx
the-me: for example in xchat there are only in the chanlist all fonts bigger and the characters which I type in the editbox
libvde: the-me: because the dpi calculation is done differently?
the-me: oh, and the nicklist
libvde: the-me: try option forcedpi
boris: libvde: how come you dont like ubuntu ?
libvde: boris: i have been doing X drivers longer than the last few weeks and i've seen them doing bad things.
boris: k
libvde: boris: besides what you are seeing now
libvde: because what you are seeing now is really bad.
boris: well
boris: i guess ill install fedora then
the-me: libv, hmm I cant find anywhere the forcedpi option in the xorg.conf manpage, could you give me an example?
udovdh: if only to debug the problem for you, boris
boris: udovdh: what graphics card you got ?
libvde: the-me: eh?
libvde: the-me: Option "Forcedpi" "integer"
libvde: the-me: in the device section
the-me: libvde, ah tanks :)
libvde: the-me: depending on how you installed the driver, man radeonhd
the-me: sorry but this one isnt documented
libvde: the-me: not even in the radeonhd manpage?
udovdh: i have a rv630 ina gigabyte 2600 pro card
the-me: libvde, I tried the xorg.conf manpage :x
libvde: the-me: there is only a command line argument for dpi with X itself
libvde: this is another of those weird X things, which is why we ourselves provide a conf file workaround
boris: udovdh: HD2600PRO ?
udovdh: yes
udovdh: but a pciE version
boris: i got agp
boris: i figured HD2600PRO can run crysis quite well
boris: on low settings, that is
libvde: ?
libvde: boris: drivers should come up just as fine on agp and pcie
the-me: hu? xdpyinfo reports, that the XVideo extension is loaded. I thought this isn't supported yet with radeonhd?
boris: im talking about games
boris: on windoze
libvde: the-me: does this mean that the extension cannot be loaded?
boris: libvde: ever heard of Crysis ?
udovdh: crypsis?
boris: Crysis
libvde: boris: i am a driver developer, not a gamer
boris: k k
libvde: boris: i do not have the time to game
boris: crysis is famous for overheating graphics cards
boris: i do
boris: i got 12 yrs
the-me: hmm, the thing after resolution: at xdpyinfo are the used dpi?
libvde: the-me: xdpy means x display
libvde: the-me: yes
libvde: the-me: this is indeed the resolution
udovdh: 12 years for what?
udovdh: did you kill somebody?
libvde: the-me: but forcedpi is a single integer only
the-me: hmm. I've forced it to 96 dpi but the resolution thing shows me 98
the-me: me@gnu:~$ grep -i forcedpi /etc/X11/xorg.conf; xdpyinfo|grep resolution
the-me: Option "Forcedpi" "96"
the-me: resolution: 98x98 dots per inch
libvde: the-me: rounding issue?
libvde: the-me: let me see whether i put enough verbosity in the driver for this
the-me: libvde, okay and I will try it again with fglrx and will find out which dpi settings I've got with it
the-me: back in a few minutes :)
boris: udovdh: i killed a few mosquitos
libvde: the-me: when you run our driver with logverbose 7, you should se this: "Forcing DPI through configuration option."
libvde: the-me: it will then just pass the configured value, when sane, to both horizontal and vertical dpi, and will never bother to do anything else
boris: udovdh: are you still here ?
libvde: the-me: this of course, unless RandR1.2 tries to be too smart and overwrites it
udovdh: ?
the-me: hmm
boris: udovdh: did you see my response ?
the-me: with fglrx it reports: resolution: 97x95 dots per inch
udovdh: yes
the-me: it's an notebook with an widescreen
boris: udovdh: and ?
udovdh: maybe start he torrent for the fedora dvd
boris: good point
the-me: libvde, what could I do to force exactly this settings?
libvde: the-me: hrm, this is a widescreen monitor on your laptop
libvde: the-me: does it have ddc?
boris: libvde: any opinions about sabayon linux ?
the-me: hmm not explizit loaded in my radeonhd config
libvde: the-me: check the log
the-me: libvde, okay but would you say, that this configuration is correct? Maybe it's just an error of my: http://nopaste.linux-dev.org/?367
libvde: the-me: hrm, i am not certain whether my code even tries to adhere to displaySize
libvde: the-me: it is mostly geared towards finding a reasonable value for all monitors attached
libvde: with some future configuration doing the rest
the-me: I could comment it out. fglrx has often problems with the fontsize without this option :)
libvde: hrm... let me dig through server code again
libvde: it's been 2+ months since i wrote this
the-me: heh okay I will restart with new settings, one moment
pasky: *sigh* fglrx locked up again
boris: nothing new
the-me: hmm, still the same with outcommented displaysize.
the-me: and here's my xorg log: http://nopaste.linux-dev.org/?368
libvde: the-me: this is not a verbose log
libvde: the-me: but the driver does accept your option
the-me: but not the correct one :(
boris: do randr doesnt try to be smart ?
boris: :P
the-me: hmm I noticed an little error
the-me: for a few weeks I reported an error on starting X with uninitialized vram (in the top I've saw some ati and hp logos with stripes etc)
the-me: this has been gone. but I tried to switch to another user, without problems. then I've logged out and it switched to this session again but at the switch time, this vram issue appears again :)
libvde: the-me: hrm...
libvde: according to your ddc, the dpi is 98.22x98.16
the-me: hm but fglrx gives me 97x95 which should be more correct I think :)
libvde: how would it come to that number?
libvde: if it is from what you provided, then it looks like it is also, quite harshly, rounding down
libvde: because your figures translate to 97.92x95.85
the-me: I don't know anything about developing graphic drivers. I just want to use a good driver on my notebook :) fglrx has to much problems. On my desktop I'll drive still with fglrx, there I need much 3d power :)
libvde: 98x98 really is a common dpi these days
the-me: maybe it differs on displays which has an native resolution of 1280x800?
the-me: because of with this 97x95 thing it looks quite nice
libvde: this seems to have a native resolution of exactly that
the-me: libvde, no way to force the x and y dpi settings?
libvde: the-me: not currently, and i am trying to find out whether there really is a proven difference
libvde: because i do not want to go and implement code for that when, when it is implemented, this happens to not deliver the result you expected
libvde: the-me: we are in a situation where we need a solid dynamic configuration infrastructure, but where randr1.2 is barely more than a stopgap. so we have to worry about where to draw the configurationability line for the time being
libvde: configurability even
the-me: libvde, hm and that means what for me?
libvde: well, for me it means, should i go and implement this or not.
libvde: because there really is no end to the option we could expose, if only there was a good way to expose them alreadw
libvde: the-me: rhd_driver.c, at the end of rhdModeDPISet
libvde: before #ifndef MMPERINCH
libvde: pScrn->xDpi = 97;
libvde: pScrn->yDpi = 95;
the-me: hmm, sounds good but I think this is just an workaround for me and not for other users :)
libvde: this is the first time i have heard this
boris: libvde: do you know any guide on how to install radeonhd on fedora 8 ?
libvde: plus... it contradicts what ddc says, and ddc is very reasonable here
libvde: and, what fglrx does is not rounding, it is rounding down.
the-me: hmm, maybe my fglrx conf could clare something
the-me: http://nopaste.linux-dev.org/?369 this is my config for fglrx
libvde: the-me: i have no intention to blindly copy what i think is idiocy in the fglrx driver
libvde: the-me: but please hardcode this for now, and check whether this gives you your desired result
libvde: because it could very well be that this is not the point where things differ
the-me: libvde, I'm on the way :)
the-me: libvde, hmm still the same and it reports 98x98
the-me: libvde, http://nopaste.linux-dev.org/?370 should I hardcode line 4 and 6 maybe, too?
andrei: Hi, I'm using the radeonhd driver, the latest one from cvs and I get a bad match when I try to rotate my screen (Radeon Mobility X2100)
andrei: Any ideas what's up?
libvde: andrei: i think this is because your xrandr utility is too old
andrei: libvde, 1.2.2; the latest one in gentoo
libvde: andrei: emmes fixed a few upstream issues when developing the randr compatibility in our driver, and iirc, there was one like this
andrei: libvde, There's no newer version on the xrandr website
libvde: website?
andrei: libvde, It has a wiki on freedesktop.org
libvde: get the git version :)
andrei: libvde, Okies, of the library or the app?
libvde: .... "xrandr" "utility"
libvde: tends to imply application
libvde: ah, heh, version numbers are kept in sync too
andrei: libvde, Okies, I just installed and tried head; same thing
libvde: ok
libvde: can you send in a mail to the mailinglist, with -logverbose 7, and the log of a run of xrandr?
libvde: i cannot go and test this atm
andrei: Sure