rivanvx: hey guys
rivanvx: is anyone experiencing this http://img354.imageshack.us/my.php?image=dscf0434ju7.jpg
rivanvx: that's on a 780G
nha: this is when you shutdown, right?
nha: looks like some textmode state isn't restored properly
nha: do you see the same kind of weirdness when you switch virtual terminals?
rivanvx: nha: on debian yes
rivanvx: on arch no
rivanvx: I don't know why
rivanvx: it actually gets better; if I shut down right at KDM (without ever logging in) I _don't_ experience that issue, don't know why
nha: I don't know about 2D country, so I can't really help you much, just trying to collect info that might help more knowledgable people in tracking it down
nha: but I see you've already experimented a lot
rivanvx: yeah, I also tried different drivers
rivanvx: but radeonhd works best
Honk: though I get to see mor FAILED messages ;P
libvde: rivanx/Honk: that's a badly restored VGA font
libvde: i bet there were messages from the MC/VGA subsystems about being unable to properly access the VGA memory from the main memory map
libvde: why he saw it on debian and not on arch is probably because debian used the vga text console versus arch using vesafb
rivanvx: libvde: I saw you mentioned that the issue I'm experiencing is badly restored VGA console
rivanvx: is there a way I can fix it?
rivanvx: does it matter that I'm using DVI or VGA connector?
libvde: rivanvx: nothing to do with the connectors
libvde: rivanvx: vga as in the ibm vga graphics "standard"
rivanvx: aha, I get it
rivanvx: because, on radeon console is restored properly but only on DVI
rivanvx: weird stuff
libvde: rivanvx: it's an issue with accessing the VGA memory
rivanvx: driver bug, then?
libvde: no, badly setup hardware
libvde: the driver could work around it though
rivanvx: so, is there any BIOS option that I can mess with?
libvde: we could use the vga registers directly, poke with the read-out masks, and read the whole 256kB out from the 64kB aperture
libvde: and then restore it the same way
libvde: quite a lot of work
rivanvx: btw, my card is supported using AtomBIOS
rivanvx: not directly
rivanvx: I don't know if this makes any difference
libvde: then there's the option of interpreting the memory setup and then setting up the memory controller so that this part of memory can be accessed
rivanvx: IOW, RADEONHD(0): Unknown card detected: 0x9610:0x1565:0x0017.
libvde: but this is rather dangerous
libvde: rivanvx: what hardware is this in real terms? rv620/635?
rivanvx: hmm, dunno
libvde: ah, rs780
libvde: heh, atombios versus non-atombios has nothing to do with this
rivanvx: well, phoronix news once mentioned that radeonhd supports 780G using non-AtomBIOS code
libvde: rivanvx: atombios doesn't exactly have functionality to restore VT
rivanvx: aha, ok then it doesn't make any change
libvde: rivanvx: partly, there are some things in some atombios motherboards where there is no option but to use hardcoded crap in the bios
libvde: rivanvx: as we have no other way of finding out what is really happening on that board
rivanvx: are you telling me that different boards behave differently?
libvde: of course.
libvde: board manufacturers do quite a lot of things
rivanvx: Honk: what board do you have?
rivanvx: I have BIOSTAR TA780G M2+
rivanvx: libvde: do PCI IDs then help identifying different classes of boards?
libvde: rs780 is really funky that way
rivanvx: and, btw, I have a 3450 (RV610?) around here that works just great, so, yeah RS780 is funky
libvde: board makers patch in parts of the atombios function tables depending on what option is chosen in the bios
libvde: funny thing is, they are able to do this because the rs780 bios is loaded in the old (ibm ps2 standard) pci expansion rom area (vga sits at the C segment), straight from the motherboards main bios image
libvde: stick in another card, boot that one as the primary, and you have no option whatsoever to get to the atombios of this IGP :)
rivanvx: I can't boot with two cards
libvde: so whenever they sell you IGP based multi-gpu support...
rivanvx: kernel stops boting at some point
libvde: you better enable the igp as the main device
rivanvx: is this what you are referring to
rivanvx: when you say that I should set IGP as main devicE?
rivanvx: but it shouldn't affect booting regardless, if I understand corretly
libvde: rivanvx: sure, but as a user, would you rather have your display connected to the discrete card, or to the internal graphics?
rivanvx: discrete card
rivanvx: hehe, that's funny
libvde: i hope this live patching of the loaded vga rom is smart
rivanvx: there is an option in bios that sets the order of cards
libvde: smart enough to check the pcir structure, smart enough to do a checksum
rivanvx: so, there is nothing we can do when discrete card is set as primary
rivanvx: but let's assume it's not
rivanvx: is there a way to workaround this corruption thing?
Diablo-D3: rivanvx: yuck, biostar
Diablo-D3: say goodbye to system stability
Diablo-D3: and you'll be replacing that mobo in a year
rivanvx: it has two year warranty, so who cares
libvde: rivanvx: as i said, one option is to code up the old VGA style memory save/restore
Diablo-D3: try getting them to follow the warrenty
rivanvx: libvde: but you said this is also dangerous, is there anything "normal" that we can do
rivanvx: Diablo-D3: you had a bad experience?
Diablo-D3: rivanvx: theres a very small list of mobo companies I consider buying from
Diablo-D3: very very small
Diablo-D3: biostar is not on that list
rivanvx: is Asrock on that list?
Diablo-D3: nor is foxconn
Diablo-D3: sapphire mobos no, sapphire radeons yes (sapphire manufs. ati branded radeons)
rivanvx: I had been offered Asrock, Sapphire and Biostar
libvde: rivanvx: the other way is dangerous, this way should be relatively safe
rivanvx: libvde: oh, I apparently misunderstood :)
rivanvx: Honk: you have a discrete card?
rivanvx: which one?
libvde: there are two ways, use the old VGA way, or poke the memory controller to be able to access this memory (dangerous, as it might have been pointing to the middle of nowhere in the first place)
rivanvx: is it also detected as an "unknown card" with a note to send mail in case it has problems?
Honk: cant remember ;P
Honk: I dont think so
rivanvx: libvde: hmm, but will fixing it for some cards break it for others?
Honk: and right now I'm in windows ;)
rivanvx: libvde: otherwise, we would need to isolate specific PCI IDs that have problems and apply that fix only for them, right?
libvde: rivanvx: no, as most cards, most setups, will still use the normal way, where we read out from the mapped framebuffer directly (when the vga memory location is pointing to a sane place)
rivanvx: aha, ok
libvde: no, we check for sanity already
libvde: rivanvx: you should have a (WW) in your log about the VGA memory not being accessible
rivanvx: lemme check
rivanvx: no, I don't have anything like that
rivanvx: only suspicios line is: RADEONHD(0): RHDVGASave: VGA FB Offset (0xC0000000) is out of range of the Cards Internal FB Address (0xD0000000)
libvde: ah, yes, that's the one
Diablo-D3: how much memory do you have?
rivanvx: 4 GB system memory
rivanvx: 512MB set for the card
rivanvx: I believe, it is set to "Auto" in bios
Diablo-D3: and you're on x86-64?
Diablo-D3: what northbridge?
Diablo-D3: ... I said what northbrige not what gpu
libvde: rivanvx: please file a bug, and state there that direct VGA access could be implemented to work around this
rivanvx: libvde: ok
rivanvx: Diablo-D3: 780G?
libvde: rivanvx: choose the component radeonhd, and then it'll automatically get assigned to me anyway
Diablo-D3: rivanvx: oh, amd chipshit?
Diablo-D3: er, chipset
Diablo-D3: wow, best typo ever
Diablo-D3: writes that down for later
Diablo-D3: but yeah, Im not aware of any problems on amd chipsets
rivanvx: it says this: 113-B27721-025 RS780 DDR2 200e/500m
Diablo-D3: so its a driver bug
rivanvx: ok, filling it now
libvde: Diablo-D3: well... the memory setup is hosed and a workaround can be provided
rivanvx: libvde: lemme guess, this would also cause massive problems with 3D if it worked?
Diablo-D3: libvde: works for me, however
Diablo-D3: libvde: Im on a intel p45 board... one that fucks up memorymapping and flgrx isnt smart enough to cope
Diablo-D3: as where the windows driver and radeonhd copes fine
libvde: we fix up the mapping after we have tried to store the vga state
libvde: but we can then only guess as to where the VGA memory really lived
Diablo-D3: hey guys
Diablo-D3: you know the thermal tape on heatsinks?
Diablo-D3: where can I buy that stuff
yangman: people usually perfer the paste
Honk: though it's easy to mess up when using it ;P
yangman: I've never had issues myself
Honk: me neither
Honk: well.. depends on what you see as "issue"
Honk: I did have several degrees temperature difference from simply reapplying the paste
Diablo-D3: I cant use paste because its for ram heatsinks
Diablo-D3: and I dont wanna use artic silver's perm epoxy
Honk: just make sure you dont use too much
Diablo-D3: no, its perm
Honk: and it wont reach any electronices ;P
Diablo-D3: as in, never comes off
Honk: I mean.. when using normal stuff
Diablo-D3: I'd like to have my heatsinks back when this card gets replaced
Diablo-D3: I use artic silver 5 as it is, Honk
Diablo-D3: I have for years
Diablo-D3: best paste on the planet
Diablo-D3: thats apparently what I want
Diablo-D3: its the best thermal tape out there
Honk: well.. but why? ;P
Diablo-D3: why what?
Honk: why do you want tape? =)
yangman: Honk: for video card RAM heatsinks
Diablo-D3: I just said, for ram heatsinks
yangman: they don't typically have retention systems
Honk: yangman: d'oh!
Diablo-D3: I have a ram heatsink that doesnt want to stick
Honk: video card ;P
Diablo-D3: so I need to replace it
Diablo-D3: uses as5 on his gpus as well :D
Honk: you could've said that earlier ;P
Diablo-D3: I DID!
Honk: well.. ram.. as in system ram ;P
Honk: anyway.. that stuff is expensive :·]
Diablo-D3: well, most heatsinks just use normal double sided tape
Diablo-D3: the rest use 3M's thermal tape which I know from experience wont fucking stick right
erudified: is regsdef.h actually used?