udovdh: brb
udovdh: the sync problem is not fixed :-(
udovdh: when I switch to text mode
udovdh: the desktop remains but is frozen
udovdh: even if I go back to the gfx console (f7)
udovdh: ctrl-alt-backspace does not work
udovdh: brb
udovdh: hello....
udovdh: just tested the latest git version after a fresh reboot
udovdh: and for me the textmode is now correctly restored
udovdh: (previous test was without the reboot, so that is a minor issue perhaps)
udovdh: I..e: start x
udovdh: then go to textmode with ctrl-alt-fX
udovdh: and then go back to X (probably at F7 or somewhere)
udovdh: video was OK in textmode and again in grafix mode
udovdh: hmmm....
udovdh: I now can't get more than 800x600...
udovdh: which was 1024x768, even with ddc not working
udovdh: xrandr -q shows only 800x600 and 640x480!
tech: what is git!
udovdh: a source repositry; see the wiki
udovdh: xrandr lets me define a new mode
udovdh: but I cannot (yet?) switch to it?
tech: oh
tech: git like that git
tech: i just needed to be remembered of it
tech: my memory is bad
tech: sorry
udovdh: no problem
udovdh: any experience with xrandr?
tech: nope, i just use it to change resolutions and show its default output :/
udovdh: how do I find the XID of a mode?
udovdh: brb
udovdh: just had that xrandr optin in xorg.conf set to no...
udovdh: now I have somethign strange (?)
udovdh: crt is at 1024x768
udovdh: but this vnc session shows the wider desktop that it is according to xrandr (1360x768)...
udovdh: xrandr helped me change that to 1024x768
udovdh: even online, no vnc connection disruption
udovdh: it just works (tm)
udovdh: that's my definition of 'enterpise' (ready), because working in IT you discover a lot of stuff isn't ready for enterprise
udovdh: but in that no-DDC modes table that xrandr gives me, I see no 'big' modes that I'll need for the LCD that is coming next week or so.
udovdh: nothing above 1360x768
tech: damn your expensive equipmen
tech: t
udovdh: what is the matter tech?
tech: hehehe, that i can't afford it, just joking, well, i'm getting some expensive equipment in january though, an a/v reciever, but the heavy v part of that will have to wait
udovdh: ?
tech: v part = a projector, currently i will have to use my 28" widescreen crt-tv
Honk: a/v reciever <-- like a tv-card? doesnt sound that expensive :P
tech: it's more of an amplifier
Honk: errh.. huh? :)
udovdh: receiver = tuner + amplifier
tech: http://en.wikipedia.org/wiki/AV_receiver
udovdh: just buy 300 euro ($4xx?) boxes for amp, cd, etc and you'll be OK
udovdh: and yes, that was another test
udovdh: I got the driver to ddc probe my crt!
udovdh: in RHDI2CFunc in rhd_i2c.c
udovdh: I inserted another rhdI2CProbeAddress call
udovdh: without the return, before the original call
udovdh: (II) RADEONHD(0): Printing probed modes for output DVI-I_2/analog
udovdh: it didn't do that before...
udovdh: so for now all appears to be `fixed` for me.
udovdh: the text issue is in git
udovdh: and this ddc issue needs some attention but can be worked around
udovdh: need a patch?
udovdh: (WW) RADEONHD(0): rhdAtomAllocateFbScratch: FW FB scratch area 536850432 (size: 20480) extends beyond available framebuffer size 268435456
udovdh: ?
udovdh: 20480 > 2684354656?
tech: so udovdh, do you visit many coffee shops while you hack?
udovdh: no?
udovdh: I don't really hack, don't know enough, just try stuff
tech: i heard coffee shops improve creativity
udovdh: but also affect your brain
udovdh: more mental patients from users
udovdh: only issue is that the refresh rate is still 60
udovdh: and doesn't go beyond that
tech: i used to love writing stoned code
tech: but i do not code as often anymore..
udovdh: don't really code. just patch here and there. minimal stuff
udovdh: like the VIA C7 dual RNG patch
udovdh: which is turned into a better patch with help from a guy at redhat
tech: i used to do some c programming, but not into system coding and stuff like that
udovdh: this DDC patch is just a quick workaround
tech: then i switched to perl, and am still doing the occasional perl script
udovdh: I am more into shell scripting etc for work
tech: but rare
udovdh: but don't do that enough
udovdh: most of the work is win32
tech: yeah i used shell scripting for a good while, until i switched to perl
udovdh: I can understand
udovdh: this morning I was looking at mrtg.cfg for the new box and tried to keep the number of tool invocations as minimal as possible
udovdh: does the radeon card have a temp sensor?
tech: i once installed the newest kernel because it had support for the sensor chip on my new motherboard
tech: and lm_sensors reported that my system temperature wwwas 110c
tech: hello, i live in the coldest north of europe
udovdh: wrong sensor type
tech: i asked myself, is my house on fire
udovdh: sensor bla 2
udovdh: sensor bla 3
udovdh: stuff like that
udovdh: my cpu is freezing according to the k8temp output
tech: udovdh: think there was a bug in the new driver, no way anything could be 110c in that time of year in norway
tech: yeah my cpu temp also go pretty low but then again that is probaly because my case is open and i never heat my house (i tend to not be bothered too much heat)
udovdh: sensor type also means a lot to the numbers, tech
tech: well there must be a bug somewhere
udovdh: check the sensors.conf first
tech: i just ran the sensor config tool
udovdh: taht is for the driver
udovdh: then comes the finetuning of the config
tech: hehe i'm not running the kernel anymore, as it wasn't useful for me, i tried it for two things, the sensor that requires the newest kernel, and the newer driver for my wlan card that requires it, but both turned out not to be too useful
udovdh: hmm. too bad. I like compiling custom kernels. (with some small patches)
tech: i tend to like the standard debian ones
tech: they're flexible and stable
udovdh: any updates?
tech: yeah, it looks like i'm soon getting hired again
udovdh: tech: good news! 1/1?
udovdh: 1/2?
Dottout: hi
Dottout: yesterday I updated to latest git and now my external dvi screen dont get anymore 1680x1050
udovdh: oh...
udovdh: and when you update again?
udovdh: no changes to the git?
udovdh: if so: that would be one of my worries, my new screen is about that size
udovdh: DDC still works?
udovdh: Dottout, ?
Dottout: I update every day
Dottout: so..2days ago was working good
Dottout: now I have an orrible 1152x864
Temujin_: Dottout: have you tried the VGA connector?
Dottout: gimme a second ;)
udovdh: there is at least one DDC issue
udovdh: (not working on my RC630 hd2600pro)
udovdh: which I hacked around with a small patch
udovdh: but...
udovdh: I only get 60 Hz modes
udovdh: not the 70+ Hz ones that my CRT monitor should be able to do
udovdh: (a CTX 1769SE)
Dottout: no way, still wrong res
udovdh: wb Dottout
Dottout: tnx
udovdh: I just explained that I only get 60Hz modes from DDC for my CRT monitor
udovdh: after my small patch (RV630 problem)
udovdh: maybe you have similar issues
udovdh: what modes are probed?
Dottout: for dvi monitor I have this:
Dottout: Option "PreferredMode" "1680x1050"
Dottout: Modeline "1680x1050" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +vsync
Dottout: xrandr -q shows 1680x1050 59.9 +
tech: udovdh: well the details aren't known yet, and it depends on investors blabla want me, it will be a telecommute kinda job (programming)
tech: so i will probably be able to pick whenever i want to job
udovdh: telecommute? not via the net? but interesting pay?
udovdh: Dottout, what is wrong with the xrandr output?
Dottout: I dont know?
udovdh: but you say the monitor is in 1152x864?
Dottout: xrandr gives no error but dvi doesnt take 1680x1050
udovdh: and there is no option about xrandr in xorg.conf?
Dottout: sorry I forgot to past first line
Dottout: DVI-I_1/digital connected 1152x864+1280+0 0mm x 0mm
Dottout: 1680x1050 59.9 +
Dottout: as you can now see it's at 1152x864
udovdh: aha
tech: udovdh: i think telecommute was the word, well yes, working remotely over the net, and yeah, the pay is good enough, i will get a standard monthly salary which will be awesome
udovdh: (FYI: I am no developer, just an interested party)
udovdh: good tech, oif the commute isn't too bad: go for it?
udovdh: Dottout, what if you use xrandr by hand to set 1680x1050?
Dottout: no output
udovdh: -v option?
Dottout: yep, no output
udovdh: Weird.
tech: udovdh: i def will, but i still have to wait and see if i get the job, but it seems like i have good chances
udovdh: what does Xorg.0.log show at such a try?
udovdh: ok, good luck, tech!
tech: thanks
tech: :)
udovdh: if i recall correctly overe here at each xrandr invocation I get the list of probed modes
Dottout: yes, with xrandr or xrandr -q
Dottout: xorg.0.log says just (II) RADEONHD(0): Output DVI-I_1/digital using initial mode 1152x864
udovdh: maybe try Xorg -logverbose 7 to see?
udovdh: (from runlevel 3 of course)
tech: so anyone gotten s-video out to work with radeonhd yet?
udovdh: report the issue to the developers at least
udovdh: not me tech. but I do have this breakout cable with my 2600pro
udovdh: email for the devs is in xorg.0.log if the card is unknown
tech: udovdh: breakout cable??
Dottout: again only (II) RADEONHD(0): Output DVI-I_1/digital using initial mode 1152x864
Dottout: do you know the meaning of different symbols in log syntax?
Dottout: I have (**) next to preferred mode
Dottout: (**) RADEONHD(0): Option "PreferredMode" "1680x1050"
tech: II probably means information
udovdh: indeed
udovdh: Dottout needs 1680x1050
udovdh: which he doesn't get anymore
udovdh: can you roll back, Dottout?
udovdh: even if you can: please do report this to the developers
Dottout: ehm..Im quite new to git, how to clone an old repo?
dli: Dottout, cd to the folder, try: "git-pull", and "git-fetch -u -v -f"
dli: Dottout, or, you can simply delete the old folder, and run git-clone from scratch
Dottout: yes I re-cloned from scratch but I need an old rev
Dottout: 2 days ago rev
udovdh: maybe the rpm will do?
dli: Dottout, cd to the folder, run: git-checkout
Dottout: Im on gentoo, rpm is evil
Dottout: tnx dli
dli: Dottout, or, run git-gui, go to menu File -> view history, right click on the one you want, "cherry pick this one"
Dottout: I have no gui but nice to know it ;)
dli: Dottout, run git-show to verify what you have
dli: Dottout, enable "tk" for git to get git-gui
Dottout: I see, thank you
Dottout: I was using from shell git+tab button eheh
Dottout: ok its time to restart X with old rev
Dottout: bbs
udovdh: and?
Dottout: mm I think Im missing something, I did git-checkout b991fe3d
Dottout: but apparenlty I had no downgrade
Dottout: git-pull now says that im not currently on a branch
dli: Dottout, try git-checkout -f
Dottout: HEAD is now at b991fe3... DACs: Properly set up and save/restore SYNC_SELECT.
Dottout: again this, but do I need to run something to downgrade effectively my source?
udovdh: ask a git expert...
dli: Dottout, I don't know what you mean "downgrade" your source
Dottout: I need the old code.. last updates broke my dvi res
Dottout: so I want to downgrade to 2 days ago git rev
udovdh: Dottout want to undo some patches
dli: Dottout, git-checkout
udovdh: there are two for fixing the sync on textmode
dli: Dottout, read the manual
udovdh: these probably don't conflict with DDC
udovdh: or what your problem's cause is
Dottout: git-checkout didnt help, read the manual is a good choice for everyone ;)
Dottout: well dont mind, for now Im going to try stable version first
dli: Dottout, git is difficult because n00b users don't know which git- tool to use. now, you know it's git-checkout
Dottout: yep, this is my first run with git
udovdh: a little help will be just that dli
radeonman: !list