| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13
Comments:
<0> Jemand: Don't insult me
<1> reality, you must be romanian.
<2> ermm guys can you fight later ?!?!
<0> Jemand: I'm in the US
<1> no matter where you live, you stay romanian.
<0> Ignorance at its best.
<2> ahhhhhhhhhh ....
<0> anavarro: Post your xorg.conf over to pastebin.com
<1> post ... over. like that is proper english.
<0> Jemand: Are you finished yet?
<2> reality i cant ...i am using irssi
<0> anavarro: So am I? What's your point?
<3> .o
<0> anavarro: check your /var/log/Xorg.0.log as well for (EE) errors
<2> how do i copy and paste in command line ?
<0> anavarro: Start up gpm
<0> That'll give you mouse support
<0> anavarro: If you can just write down the (EE) line which causes the fatal error for X, we can probably help
<2> i think it gave no error... the error i am seeing occurd quite long time ago .
<2> it says no screen found
<2> but that error happened when i was using "nv" driver instead of "nvidia"
<0> anavarro: That would mean you probably changed Identifier line under Devices in your xorg.conf and it doesn't match Device listed in the Screens section
<3> longword, Ferrari take the front row huh
<2> reality: No all the identifiers match
<0> anavarro: Distro?
<2> gentoo
<4> I am trying to do cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/gnuworld login and I get login failed no route to host... why?
<0> anavarro: Oi. The one distro I don't use
<2> it was all working till i changed graphics card
<0> dutz0r: If you don't know, you have no business of running an ircd
<0> anavarro: Can you pop into X with nv?
<5> dutz0r, hmm perhaps that site is down
<4> reality ; believe me I know but when I do it, I get login aborted ... connection to cvs.sourceforge.net failed no route to host
<2> no icant i get that error
<4> could be down?
<2> when iuse nvidia i get no erres but a blank scren
<6> heh
<6> typical nvidia
<7> Try forcing the display type (CRT/LCD/TV)
<6> bloody idiots. they just want to keep people from blaming them
<0> anavarro: Run an Xorg -configure
<6> yuck
<0> libv: ati is no better
<5> hmm Alonso only fifth
<2> Reality did that ... then when i test it, i get again a blank screen
<6> reality: check users-libv-... on gitweb.freedesktop.org
<0> anavarro: does ps aux | grep X show X as running?
<6> nvidia is trying to be proactive, ati just steers largely clear
<2> x shouldn't be running
<6> which is worse, the one breaking the Xv ABI right before the 7.1 freeze, trying to force in some functionality only they use, or the ones that don't do a thing?
<7> Wow. Ma***a
<5> wow crash
<0> anavarro: If you have a blank screen, your horizontal and vertical refresh rates might be out of range
<5> he m***a first
<7> More of an altercation than a crash
<0> anavarro: In which case X would be running but you wouldn't see anything but a blank screen
<5> hmm did MS take first place again?
<6> nvidias proprietary driver should make proactive use of DDC information
<6> err, edid
<0> libv: Your Mach64 offer hardware acceleration?
<2> they should be in range i just edited my old configuration card that used to work with a savage s3
<5> nooo Kimi
<5> :(
<2> aslo ctrl alt bksp doesnt kill X
<7> What about Monty?
<6> reality: it's atimisc cleaned up (WIP)
<5> who cares about monty
<6> reality: but yes, george fufutos has been adding exa support
<7> them: All the Colombian fans in the crowd
<0> anavarro: But is X running?
<5> longword_F1, well they already paid
<7> them: Lots more than Finlanders
<0> anavarro: Just check it with ps aux
<7> them: I bet Linus isn't even there
<0> libv: Well, let me know when it gets full hardware acceleration
<5> wow heidfeld
<0> I'll check it out then
<6> there are countless things that can happen for you to get a blackened screen, could even be an issue filling up a freshly cleared FB
<6> reality: hah
<7> wow ad break :-(
<2> reality i do that when i get a blank screen ?
<6> reality: you have no choice but to use that driver soon
<5> longword_F1, that was more then altercation
<5> longword_F1, did a few flips in the air
<0> anavarro: Yeah
<6> reality: that driver and thus me acquiring that ultra10 blocks pci-id based driver loading
<0> libv: What about the ATI proprietary driver?
<2> reality : i cant cause ctrl alt f<whatever> wont work
<6> reality: f 'em
<0> libv: Well, that would preclude you from saying having no choice
<5> need a what?
<6> reality: oh, well, given a timelapse
<5> Button needs what?
<6> anavarro: could be several things still
<0> anavarro: So I'm guessing things are failing at the monitor level...not the driver level
<6> anavarro: basic conclusion is, it's a closed driver, you can't do anything about it
<5> new frontwing
<6> reality: you couldn't be more wrong
<6> it's _always_ the driver level
<0> libv: I doubt I'm wrong in this case
<5> nope, looks ok
<7> ITV haven't show it yet :-(
<6> reality: yeah, do that, argue with the long time X driver developer
<7> Button dinged then wing
<2> means i'm pretyy F*cked up ?
<5> longword_F1, you dont get Ladeux?
<7> I don't know what Ladeux is.
<5> french tv channel
<5> doh commercial break now
<7> Oh there it is!
<0> anavarro: Reboot the system, append a video=vga16:off to your lilo
<5> ok back here as well
<7> Speed out too?
<8> yep
<6> heh
<7> 6 cars out?
<8> 7 if i counted right
<2> i use grub
<8> webber, montoya, kimi, heidfeld, klien, speed, montagny
<6> anavarro: that's just one of those typical workarounds for a driver badling handling modesetting
<0> anavarro: Then append that to your grub kernel line
<6> badly even
<0> libv: If it works, it works
<6> reality: dream on.
<5> SC lights out I think
<0> libv: Then write a new nvidia driver
<6> reality: people are on it.
<0> libv: Are you on it?
<6> haha
<5> oleee
<6> reality: what is it you do?
<5> next 2 cars out
<0> libv: I'm a clinical immunologist
<8> button out as well
<6> reality: i'm doing VIAs unichrome, and the atimisc cleanup (which is the single nastiest driver ever in X, and which no other X developer ever dared touch)
<5> monteiro badly damaged
<6> oh, i reworked tseng, soon to be touching chips and trident to remove static dotclocks
<6> after which i can finally start proper rework of xf86ValidateModes and all that surrounds it
<0> libv: I'm sure I could sit here and spout my credentials for about four hours as well in my given field...however, none of this relates to the end user's problem here
<6> still want me to handle your selfish request?
<6> your conclusions are wrong
<6> it's _never_ the monitor
<0> libv: I don't see you offering any sort of help whatsoever to said user
<0> If you're so high and mighty, either come up with a solution, or simply STFU
<6> he should be posting a log, and he should be using the nv driver
<6> if he's using the binary driver, then he's beyond helping
<0> I wouldn't say that at all. There are plenty of times when somebody just misses something in their X conf which causes a blank screen
<0> The most common one occuring on this channel being horiz and vert refresh rates being b0rked
<6> Option "PleasePleasePleaseDontGiveMeABlankScreen" "True" ?
Return to
#linuxhelp
or
Go to some related
logs:
#mirc
#teens
wget pokerroom
#linux
coolmenus_frame.js
#AllNiteCafe
lemeshias
#linux
#linux
someone should kill bush
|
|