Menu
▾
▴
linuxconsole-dev
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
(235) |
Apr
(30) |
May
(32) |
Jun
(86) |
Jul
(81) |
Aug
(108) |
Sep
(27) |
Oct
(22) |
Nov
(34) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(78) |
Feb
(10) |
Mar
(81) |
Apr
(27) |
May
(13) |
Jun
(105) |
Jul
(78) |
Aug
(52) |
Sep
(59) |
Oct
(90) |
Nov
(127) |
Dec
(49) |
| 2002 |
Jan
(102) |
Feb
(72) |
Mar
(54) |
Apr
(98) |
May
(25) |
Jun
(23) |
Jul
(123) |
Aug
(14) |
Sep
(52) |
Oct
(65) |
Nov
(48) |
Dec
(48) |
| 2003 |
Jan
(22) |
Feb
(25) |
Mar
(29) |
Apr
(12) |
May
(16) |
Jun
(11) |
Jul
(20) |
Aug
(20) |
Sep
(43) |
Oct
(84) |
Nov
(98) |
Dec
(56) |
| 2004 |
Jan
(28) |
Feb
(39) |
Mar
(41) |
Apr
(28) |
May
(88) |
Jun
(17) |
Jul
(43) |
Aug
(57) |
Sep
(54) |
Oct
(42) |
Nov
(32) |
Dec
(58) |
| 2005 |
Jan
(80) |
Feb
(31) |
Mar
(65) |
Apr
(41) |
May
(20) |
Jun
(34) |
Jul
(62) |
Aug
(73) |
Sep
(81) |
Oct
(48) |
Nov
(57) |
Dec
(57) |
| 2006 |
Jan
(63) |
Feb
(24) |
Mar
(18) |
Apr
(9) |
May
(22) |
Jun
(29) |
Jul
(47) |
Aug
(11) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: Erik W. <om...@vc...> - 2005-08-24 21:10:18
|
Erik Walthinsen wrote: >>Third workaround: Configure framebuffers in your kernel, >>get a framebuffer for each and every screen. > > This is something I tried for a while, but didn't have much luck with. > I'll give it another shot though. No go. When loading the radeonfb module, I get /dev/fb0 for the first card, but no other cards load up. They all come back with "0k" VRAM and refuse to create an FB device. There are hacks in the driver for a couple of video cards to deal with this situation, but not for the same reason. |
|
From: Erik W. <om...@vc...> - 2005-08-24 17:09:50
|
Helge Hafting wrote: > This is probably the classic problem where an xserver mistakenly > thinks it has the "only" vga-compatible card in the box, and > tries reprogramming video timings using legacy vga hardware > addresses that might affect the wrong card. Isn't this what the "VGAAccess" "false" option is for? > Third workaround: Configure framebuffers in your kernel, > get a framebuffer for each and every screen. This is something I tried for a while, but didn't have much luck with. I'll give it another shot though. Accelleration isn't a huge deal, and 3D is out with multiple cards anyway, so speed should be acceptible. What I'd really like to be able to do is get both heads of the dual-headed cards running separate framebuffers, and get separate X servers running on those. That would let me get away with only 3 video cards for 6 heads, freeing other PCI slots for either other cards, or smaller motherboards. Problem is, I couldn't figure out if it is even possible to have separate /dev/fb devices with the kernel fb driver... Everything I tried was either 5+ years old and didn't exist anymore, or didn't work in the slightest otherwise. |
|
From: Mark H. <mar...@xs...> - 2005-08-24 10:57:36
|
Hi, Just wondering, are you running an SMP kernel? I seem to have similar problems as described in this thread, when I use an SMP enabled kernel on Ubuntu, with a similar setup. I'm using two dualhead Matrox cards, a primary G550, which I currently use as text console only (was hoping to see a kernel panic there, but nothing appears), and a pci G450, which I use for the two X servers. I noticed that the stock 2.6.10-5-386 kernel works perfectly for me, however, whenever I try an SMP kernel, it just dies. Sometimes it happens almost instantly, sometimes it takes a while (~30-60 minutes), but it always dies silently. No info on the text console. I'm still in the process of figuring out wether it's the X server, the kernel, or my hardware (I doubt it is the hardware, since on gentoo/ruby it seems to work properly, as well as under windows XP). I've tried almost all available ubuntu-smp kernel images (for k7/386/686), but all show the problem. So far any attempt to build a custom kernel for my Ubuntu system has resulted in crashes, even if they are based on the working ubuntu kernel & .config (simply switch on smp), or on my working (on gentoo) vanilla kernel & .config :-(, so I'm seriously starting to doubt the X server. Still want to try: - attach serial console - no-X/single-seat-X on smp image - vanilla kernel without smp - build xserver from scratch (find latest xorg version, aply patches manually) Apart from the problem described, I really like this Ubuntu setup. However, I specifically moved from gentoo/ruby to Ubuntu to be able to easily upgrade my kernel, and exactly that does not seem to work... :-( Regards, Mark. |
|
From: Helge H. <hel...@ai...> - 2005-08-24 09:23:45
|
Erik Walthinsen wrote: >Hugo Vanwoerkom wrote: > > >>The reason for the textconsole is if the crash is a >>kernel panic then that is where the last message will >>show up. >> >> >Of course. But if it's corrupted by the other heads, I'm not sure >whether or not a panic message would even have showed up anyway. OTOH >kgdb should give me even better results, if/when it happens again. > > > >>I am still not clear on what exactly dies. Is anything >>still running? >>When the crash occurs, everything is dead? >> >> >It varies. The most extreme crash is where everything just locks >exactly where it is, with some heads sleeping and others with a mouse on >its way to some menu somewhere on the screen, whatever is going on. In >these cases the machine ceases to respond to pings, and I have to >hard-reset the box. > >Other cases involve a single head going black, and even shutting down >the CRTC completely. Yesterday I was actively using one of the heads >and it blanked out from underneath me, then the LCD switched to >displaying "No Cable Attached"... Thing is, the rest of the machine was >working properly, to the point of the other heads going to sleep and >waking up as expected, before I rebooted the machine later. > > This is probably the classic problem where an xserver mistakenly thinks it has the "only" vga-compatible card in the box, and tries reprogramming video timings using legacy vga hardware addresses that might affect the wrong card. A workaround: make sure you set up all your xservers with at least two different resolutions. The user who got a blank display can then tap ctrl+alt and "+" or "-" on the numeric keypad, and that xserver will reset its own resolution. (If the other resolution isn't wanted, just press the key combination again to get back.) The resolution is reset, and the display restored. Another workaround: Use only graphichs cards that aren't backwards compatible with VGA - at all. If you can find such cards, that is. Third workaround: Configure framebuffers in your kernel, get a framebuffer for each and every screen. Set sutiable resolutions using kernel boot parameters for the framebuffer drivers. Use the framebuffer xserver. This one don't try to set the resolution, it uses whatever resolution the framebuffer is set to. So problems don't ever happen. Of course this driver is unaccelerated, so your cpu(s) are going to do all the rendering work. Performance may still be fine for simple 2D work like word processing and web browsing and simple 2D games. (I didn't notice any X performance difference between accelerated and unaccelerated 2D X with a 400MHz celeron cpu and two screens.) The correct fix: complain to x.org developers. Perhaps a fix will materialize someday. It certainly won't happen if nobody complains. Helge Hafting |
|
From: Helge H. <hel...@ai...> - 2005-08-24 09:06:00
|
Aivils Stoss wrote: >Hi , All! > >Don't like patched kernel. Ok try out vanilla! > > Main goal of this fake TTY driver is multi seat Linux box creation >without any patch under Debian stable or Mandriva 2005 LE , which distros >contains -isolateDevice patch of X. > > Recent Linux kernel does not force us use evdev or tty layer. Even sytem >operator can load new input handler. Actualy i write faketty kernel module, >which create device file for each keyboard. That device file emulate TTY >layer. > > Interesting. Do this have an advantage compared to using evdev, which is supported in ubuntu's x.org? (this x.org also works on debian testing, making multiseat X possible with a standard kernel. But of course only one user gets a vga console. >Keypress events are translated to standard TTY layer keycodes. These keycodes >can use X for input. > > Is it possible to run a getty taking input from such a faketty, and also redirecting the output of that getty to some process who renders it on a framebuffer device? That'd allow a terminal to appear when X dies for some reason. Even on the second screen. . . Helge Hafting |
|
From: Aivils S. <ai...@un...> - 2005-08-24 06:30:37
|
On Pirmdiena, 22. Augusts 2005 13:59, Hugo Vanwoerkom wrote: > > Hi , All! > > > > Don't like patched kernel. Ok try out vanilla! > > <snip> > > > LIMITATIONS: > > > > =A0=A0=A0=A0=A0=A0All pluged in keybords must be opened via new > > faketty driver, because > > each keyboard at normal TTY steer LED's of all > > keyboards of system. If You > > will > > start multiple X, every one X must use faketty for > > correct work of LED's. This > > mean text mode console is unavaible. > > Boooo!!! =A0:-( http://www.ltn.lv/~aivils/files/hijackled-2.6.11-12mdk.tar.bz2 hijacled kernel module is prepared for 2.6.11-12mdk kernel runtime modification. It replaces keyboard LED steering function with another proper one. After loading of hijackled into kernel use is new LED function. After module unload old function comes back. At normal kernel any keyboard steer LED's of all keyboards without any state cheking. New function does not touch already grabed input devices. With new function ungrabed keyboard steer all ungrabed keyboard LED's, grabed keyboard steer only his own LED's. This feature is neccessary for faketty kernel module. INSTALL: # make # make install # modprobe hijacled If You will use this module under another kernel, please replace hj_kbd_handler hj_keyboard_tasklet hj_ledstate hj_kbd_table addresses, which can be found in /boot/System.map Unfortunately i do not know which kernel is true under Mandriva 2005 LE Both modules, faketty and hijackled, i can load and set up my system without reboot. Non x86 platform status is unknown. Aivils Stoss |
|
From: <han...@sa...> - 2005-08-23 22:13:38
|
Hi, You need to apply the attached patches to your x.org 6.8.2 source tree, and recompile. The options should work after that. -Hans > Hi, > > I am having the same problem with the two NVidia cards > GeForce4 MX4000 AGP 8x and GeForce FX5200 PCI on > Debian unstable with Ruby patched kernel 2.6.12. I am > using the NVidia driver version 7676. > > I read somewhere that I should use the -sharevts > option when starting the second X server. I tried, but > this option is not recognized. How should I do this? > > Thanks a bunch! > > Andrej > > --- han...@sa... wrote: > > > > > Hi! > > > > I have 1 NVIDIA Gefore FX 5200 PCI, and one NVIDIA > > Gefore 6600 PCI-E > > card. I have both X servers set up correctly so that > > they run without > > any problem seperatly (with different keyboards and > > mice). Both X > > servers use the nvidia close source 6629 driver. > > > > My problem is that whenever I try to start the > > second X server, while > > the first one is already running, the monitor > > connected to the first X > > server goes black (monitor is turned off/signal > > lost). The xserver > > itself however continues running, and all > > applications (like music from > > xmms) also continue running. There are no errors in > > any log files. There > > is no difference when trying to start the X servers > > in the opposite > > order. Starting the second X server always kills the > > display of the one > > already running. > > > > I have tried to turn the monitor back on with "xset > > dpms dorce on > > -display :0.0", but this doesn't help. > > > > I'm running x.org 6.8.2 with the IsloateDevice > > patch. I'm actually not > > running ruby anymore, but I'm using the evdev driver > > for the separate > > keyboards/mice > > (https://bugs.freedesktop.org/show_bug.cgi?id=968), > > so in > > a sence I'm posting to the "wrong" list, but I guess > > people here are the > > most experienced with these kind of setups. > > > > The PCI card is also set as the primary graphics > > card in bios, otherwise > > it didn't work at all. > > > > Thanks for any help on this! > > > > -Hans > > > > > > > > > ------------------------------------------------------- > > SF.Net email is Sponsored by the Better Software > > Conference & EXPO > > September 19-22, 2005 * San Francisco, CA * > > Development Lifecycle Practices > > Agile & Plan-Driven Development * Managing Projects > > & Teams * Testing & QA > > Security * Process Improvement & Measurement * > > http://www.sqe.com/bsce5sf > > _______________________________________________ > > Linuxconsole-dev mailing list > > Lin...@li... > > > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > > > > > > > ___________________________________________________________ > To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev |
|
From: Erik W. <om...@vc...> - 2005-08-23 19:37:10
|
Hugo Vanwoerkom wrote: > You probably have already said this, but what patch > version of Ruby are you running? None. It's not necessary for this setup AFAICT, esp since it works properly except for this crash. Ruby seems to be far too much complexity for an X-only multi-seat system. Also, the 'multiseat' package that's in Ubuntu that will theoretically set up this kind of system (but is not even alpha-level yet, I'll be working on dramatic enhancements to it once I have the second round of hardware), doesn't use Ruby at all. |
|
From: Hugo V. <hvw...@ya...> - 2005-08-23 19:31:09
|
--- Erik Walthinsen <om...@vc...> wrote: > Hugo Vanwoerkom wrote: > > The reason for the textconsole is if the crash is > a > > kernel panic then that is where the last message > will > > show up. > Of course. But if it's corrupted by the other > heads, I'm not sure > whether or not a panic message would even have > showed up anyway. OTOH > kgdb should give me even better results, if/when it > happens again. > > > I am still not clear on what exactly dies. Is > anything > > still running? > > When the crash occurs, everything is dead? > It varies. <snip> You probably have already said this, but what patch version of Ruby are you running? H __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Erik W. <om...@vc...> - 2005-08-23 18:48:58
|
Hugo Vanwoerkom wrote: > The reason for the textconsole is if the crash is a > kernel panic then that is where the last message will > show up. Of course. But if it's corrupted by the other heads, I'm not sure whether or not a panic message would even have showed up anyway. OTOH kgdb should give me even better results, if/when it happens again. > I am still not clear on what exactly dies. Is anything > still running? > When the crash occurs, everything is dead? It varies. The most extreme crash is where everything just locks exactly where it is, with some heads sleeping and others with a mouse on its way to some menu somewhere on the screen, whatever is going on. In these cases the machine ceases to respond to pings, and I have to hard-reset the box. Other cases involve a single head going black, and even shutting down the CRTC completely. Yesterday I was actively using one of the heads and it blanked out from underneath me, then the LCD switched to displaying "No Cable Attached"... Thing is, the rest of the machine was working properly, to the point of the other heads going to sleep and waking up as expected, before I rebooted the machine later. Sometimes I get one or more of the heads blanking a la DPMS, the never waking up, while the machine is otherwise working just fine. Periodically in this situation attempting to wake a display by moving the mouse or hitting a key will trigger a *complete* crash a la the first paragraph above. And of course once I put a kgdb kernel on the machine, and switched to xserver-xorg-dbg-6.8.2-1ubuntu, it ran for many hours operating just fine. Classic Heisenbug. I'll be hammering on it continuously for the remainder of the next two weeks, and if running a debug X server "solves" the problem, so be it. I'll have more time to *really* solve the problem once I get back. |
|
From: Hugo V. <hvw...@ya...> - 2005-08-23 11:43:39
|
--- Erik Walthinsen <om...@vc...> wrote: > Hugo Vanwoerkom wrote: > > When you say that it crashes with no signs of > > anything, I presume you mean that everything > freezes > > and you cannot move anything? > > That is a kernel panic that most likely shows up > on > > the AGP vc console, the one you boot with. > > > > Has that been active, i.e. visible during a crash? > Not until now, I just ran a test with the 2nd and > 3rd heads running X > and the first head (all PCI) sitting at a text VT. > Problem is, the text > VT got throroughly hozed once the X servers started > up, incapable of > scrolling when e.g. trying to log in, and getting > interleaved in weird > patterns when trying to switch VTs. I may try > putting a Matrox G400 AGP > card in to see if I can avoid this kind of > corruption by having a > totally different engine on the 1st head. > > However, there is nothing on the console now that > the machine has > crashed. AFAIK there were no events such as DPMS > wakeup etc to trigger > the crash. > > Now I'm going to see if a) I have or have to go buy > a null modem cable, > and b) whether kgdb can give me anything useful. > The reason for the textconsole is if the crash is a kernel panic then that is where the last message will show up. I am still not clear on what exactly dies. Is anything still running? When the crash occurs, everything is dead? H ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs |
|
From: Erik W. <om...@vc...> - 2005-08-22 19:27:03
|
Hugo Vanwoerkom wrote: > When you say that it crashes with no signs of > anything, I presume you mean that everything freezes > and you cannot move anything? > That is a kernel panic that most likely shows up on > the AGP vc console, the one you boot with. > > Has that been active, i.e. visible during a crash? Not until now, I just ran a test with the 2nd and 3rd heads running X and the first head (all PCI) sitting at a text VT. Problem is, the text VT got throroughly hozed once the X servers started up, incapable of scrolling when e.g. trying to log in, and getting interleaved in weird patterns when trying to switch VTs. I may try putting a Matrox G400 AGP card in to see if I can avoid this kind of corruption by having a totally different engine on the 1st head. However, there is nothing on the console now that the machine has crashed. AFAIK there were no events such as DPMS wakeup etc to trigger the crash. Now I'm going to see if a) I have or have to go buy a null modem cable, and b) whether kgdb can give me anything useful. |
|
From: Aivils S. <ai...@un...> - 2005-08-22 12:01:41
|
On Pirmdiena, 22. Augusts 2005 13:59, Hugo Vanwoerkom wrote: > > LIMITATIONS: > > > > =A0=A0=A0=A0=A0=A0All pluged in keybords must be opened via new > > faketty driver, because > > each keyboard at normal TTY steer LED's of all > > keyboards of system. If You > > will > > start multiple X, every one X must use faketty for > > correct work of LED's. This > > mean text mode console is unavaible. > > Boooo!!! =A0:-( Google: KERNEL FUNCTION HIJACKING and replace kbd_bh kernelspace func :-) Aivils |
|
From: Hugo V. <hvw...@ya...> - 2005-08-22 10:59:28
|
--- Aivils Stoss <ai...@un...> wrote: > Hi , All! > > Don't like patched kernel. Ok try out vanilla! <snip> > > > LIMITATIONS: > > All pluged in keybords must be opened via new > faketty driver, because > each keyboard at normal TTY steer LED's of all > keyboards of system. If You > will > start multiple X, every one X must use faketty for > correct work of LED's. This > mean text mode console is unavaible. > Boooo!!! :-( H __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Mabelle M. <Mck...@je...> - 2005-08-22 10:59:10
|
Hello,
Burn, burn, former life!time at the word Attendant. The cylinder =
=
rang quietly in response,some reason, and, blacker than a storm =
cloud, went backstage to receive theextensively in south-west Asia, =
adopted by the Jews after the Babylonian Margarita was put in =
place, and under her left arm she found a lowvisitor. On whom you =
have come calling? In half an hour, Styopa replied and, hanging up =
the receiver, pressed You dont say! Can you describe his character =
for me? A fanatic?Margarita, without ceasing to dip into the ointment =
and apply it to Wolandsstaff was overjoyed - he had run away! Those =
who entered the living room contemplated this cat for quite a =
`Theres no need for any points of view, the strange =
professorstrengthlessly from the tablecloth, everything around the =
master in theand grunted. The questions he asked seemed crazy to me. =
Saving nothing aboutOnly then did the dog also fall asleep.having been =
covered with writing about Ivan, it was turned over, and the
|
|
From: Aivils S. <ai...@un...> - 2005-08-22 07:17:44
|
Hi , All! Don't like patched kernel. Ok try out vanilla! Main goal of this fake TTY driver is multi seat Linux box creation without any patch under Debian stable or Mandriva 2005 LE , which distros contains -isolateDevice patch of X. Recent Linux kernel does not force us use evdev or tty layer. Even sytem operator can load new input handler. Actualy i write faketty kernel module, which create device file for each keyboard. That device file emulate TTY layer. Keypress events are translated to standard TTY layer keycodes. These keycodes can use X for input. linux-ruby assign /dev/ttyXX for each keyboard. faketty assign /dev/fttyXX for each keyboard. Current i use simple starting method # modprobe faketty # rm -f /dev/tty5[0-9] # ln -s /dev/ftty0 /dev/tty50 Now /dev/tty50 is not standard TTY layer device but new. Start X via new layer: # startx -- vt50 LIMITATIONS: All pluged in keybords must be opened via new faketty driver, because each keyboard at normal TTY steer LED's of all keyboards of system. If You will start multiple X, every one X must use faketty for correct work of LED's. This mean text mode console is unavaible. BUGS: faketty creates /dev/fttyXX files for each input device, but must create for keyboards only. file attached to mail. Aivils Stoss |
|
From: Andrej v. d. Z. <ma...@ya...> - 2005-08-21 21:17:02
|
Hi, I am having the same problem with the two NVidia cards GeForce4 MX4000 AGP 8x and GeForce FX5200 PCI on Debian unstable with Ruby patched kernel 2.6.12. I am using the NVidia driver version 7676. I read somewhere that I should use the -sharevts option when starting the second X server. I tried, but this option is not recognized. How should I do this? Thanks a bunch! Andrej --- han...@sa... wrote: > > Hi! > > I have 1 NVIDIA Gefore FX 5200 PCI, and one NVIDIA > Gefore 6600 PCI-E > card. I have both X servers set up correctly so that > they run without > any problem seperatly (with different keyboards and > mice). Both X > servers use the nvidia close source 6629 driver. > > My problem is that whenever I try to start the > second X server, while > the first one is already running, the monitor > connected to the first X > server goes black (monitor is turned off/signal > lost). The xserver > itself however continues running, and all > applications (like music from > xmms) also continue running. There are no errors in > any log files. There > is no difference when trying to start the X servers > in the opposite > order. Starting the second X server always kills the > display of the one > already running. > > I have tried to turn the monitor back on with "xset > dpms dorce on > -display :0.0", but this doesn't help. > > I'm running x.org 6.8.2 with the IsloateDevice > patch. I'm actually not > running ruby anymore, but I'm using the evdev driver > for the separate > keyboards/mice > (https://bugs.freedesktop.org/show_bug.cgi?id=968), > so in > a sence I'm posting to the "wrong" list, but I guess > people here are the > most experienced with these kind of setups. > > The PCI card is also set as the primary graphics > card in bios, otherwise > it didn't work at all. > > Thanks for any help on this! > > -Hans > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software > Conference & EXPO > September 19-22, 2005 * San Francisco, CA * > Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects > & Teams * Testing & QA > Security * Process Improvement & Measurement * > http://www.sqe.com/bsce5sf > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com |
|
From: Mario S. <zwe...@gm...> - 2005-08-21 12:05:34
|
Am Sonntag, 21. August 2005 07:19 schrieb Dr. Sichendra Bista: > Dear Mario: > Great to learn about your success story. > > 1)From where did you download the patches and xserver-xorg? Did you do > apt-get? Could you give me the links of the patch? The xserver-xorg is in the Debian repo. unstable. I don't need patch for them. Ruby patch is from http://members.westnet.com.au/vanzeeland/ The cvs-ruby doesn't compile. > Besides the ruby patch do you have to apply patch to the xserver-xorg > also? If yes, which one? No. > And do you have to use any hotplug hacks? Or hotplug works natively? no, works natively Thank for you interest. mfg Mario -- mar...@we... ( Auch verschluesselt ) http://www.marioscheel.de ( Mit Public-Key ) ICQ# 223567831 -- mar...@we... ( Auch verschluesselt ) http://www.marioscheel.de ( Mit Public-Key ) ICQ# 223567831 |
|
From: Hugo V. <hvw...@ya...> - 2005-08-21 11:57:54
|
--- "Dr. Sichendra Bista" <dr...@ep...> wrote: > Dear Mario: > > On Sunday 21 August 2005 09:24, > lin...@li... > wrote: > <snip> > > Great to learn about your success story. > > 1)From where did you download the patches and > xserver-xorg? Did you do > apt-get? Could you give me the links of the patch? > http://members.westnet.com.au/vanzeeland/Linux/kernel/ruby-2.6.12.patch > Besides the ruby patch do you have to apply patch to > the xserver-xorg > also? If yes, which one? > Debian has the IsolateDevice patch in its distributions of both stable (Xfree86) and unstable (Xorg) > And do you have to use any hotplug hacks? Or hotplug > works natively? > Usual hotplug files: per Multi-User HOWTO. But see my post to this list that I find: http://members.westnet.com.au/vanzeeland/Linux/kernel/patch-2.6.11-vz93.diff.gz better in behavior. Hugo __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Dr. S. B. <dr...@ep...> - 2005-08-21 04:19:32
|
Dear Mario: On Sunday 21 August 2005 09:24, lin...@li... wrote: > > Message: 2 > From: Mario Scheel <zwe...@gm...> > To: lin...@li... > Subject: Successstory > Date: Sat, 20 Aug 2005 21:08:16 +0200 > > Hello > > On my computer can I use two different users, with the Ruby patch. > Kernel: > 2.6.12-ruby > Xorg: > xserver-xorg 6.8.2.dfsg.1-4 > Distri: > Debian SID Great to learn about your success story. 1)From where did you download the patches and xserver-xorg? Did you do apt-get? Could you give me the links of the patch? Besides the ruby patch do you have to apply patch to the xserver-xorg also? If yes, which one? And do you have to use any hotplug hacks? Or hotplug works natively? May you, your family and your team be successful in your missions, prosperous, healthy, happy, free from sufferings and in peace, always! Thanking you in anticipation for your invaluable time and continued cooperation, Webocratically yours, Dr. Sichendra Bista, Chief Architect and Secretary General eParliament.org: The Pioneering OPERATIONAL Mode of Webocracy Consultant on Int'l Relations and Online Advocacy, Feminist League Founder and President, Global Initiatives International Secretariat ------------------------------------------------------------------------------------------------ PEACE | JUSTICE | HUMAN RIGHTS | DEMOCRACY | DEVELOPMENT ------------------------------------------------------------------------------------------------ Address in Exile: C/o Ms. Galina Morozova, President Feminist League of Kokshetau Abaya Street, 112 off. 24, Kokshetau, Kazakhstan Cell: 7-300-330-0664 Fax: (7-3162) 257354 http://www.eParliament.org http://giis.netfirms.com/anupa.htm http://feministleague.f2o.org > > graphic cards: > 0000:01:00.1 Display controller: ATI Technologies Inc Radeon RV250 > [Radeon 9000] (Secondary) (rev 01) > 0000:02:00.0 VGA compatible controller: ATI Technologies Inc 215CT > [Mach64 CT] (rev 0a) > > 1 keyboard are connected with PS/2 > 1 keyboard are connected with USB > 2 mouses are connected with USB > > First xorg.conf > Section "InputDevice" > Driver "mouse" > Option "Device" "/dev/input/mouse0" > > Section "InputDevice" > Identifier "Generic Keyboard" > Driver "kbd" > > Second xorg.conf > Identifier "Generic Keyboard" > Driver "kbd" > Option "Protocol" "evdev" > Option "Dev Name" "Buddy Buddy (TM) PS/2 > Keyboard-PS/2 Mouse " Option "Dev Phys" > "usb-0000:02:07.1-1/input0" > > Section "InputDevice" > Driver "mouse" > Option "Device" "/dev/input/mouse1" > > > mfg > Mario > -- > mar...@we... ( Auch verschluesselt ) > http://www.marioscheel.de ( Mit Public-Key ) > ICQ# 223567831 -- --- Easiest Way to Money Transfer: https://www.paypal.com/us/mrb/pal=RJN9PP2YM9WTN |
|
From: Mario S. <zwe...@gm...> - 2005-08-20 19:08:24
|
Hello On my computer can I use two different users, with the Ruby patch. Kernel: 2.6.12-ruby Xorg: xserver-xorg 6.8.2.dfsg.1-4 Distri: Debian SID graphic cards: 0000:01:00.1 Display controller: ATI Technologies Inc Radeon RV250 [Radeon 9000] (Secondary) (rev 01) 0000:02:00.0 VGA compatible controller: ATI Technologies Inc 215CT [Mach64 CT] (rev 0a) 1 keyboard are connected with PS/2 1 keyboard are connected with USB 2 mouses are connected with USB First xorg.conf Section "InputDevice" Driver "mouse" Option "Device" "/dev/input/mouse0" Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Second xorg.conf Identifier "Generic Keyboard" Driver "kbd" Option "Protocol" "evdev" Option "Dev Name" "Buddy Buddy (TM) PS/2 Keyboard-PS/2 Mouse " Option "Dev Phys" "usb-0000:02:07.1-1/input0" Section "InputDevice" Driver "mouse" Option "Device" "/dev/input/mouse1" mfg Mario -- mar...@we... ( Auch verschluesselt ) http://www.marioscheel.de ( Mit Public-Key ) ICQ# 223567831 -- mar...@we... ( Auch verschluesselt ) http://www.marioscheel.de ( Mit Public-Key ) ICQ# 223567831 |
|
From: Hugo V. <hvw...@ya...> - 2005-08-20 10:04:23
|
--- Erik Walthinsen <om...@vc...> wrote: > Hugo Vanwoerkom wrote: > > Did you run this setup on a vanilla system (no > > patches) first and does it crash then? > > Yup, when I run with just one head it's been rock > solid for the duration > of testing. I'll run it singleheaded all this > weekend while I'm gone, > and get someone to prod it periodically to make > sure. > When you say that it crashes with no signs of anything, I presume you mean that everything freezes and you cannot move anything? That is a kernel panic that most likely shows up on the AGP vc console, the one you boot with. Has that been active, i.e. visible during a crash? H ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs |
|
From: Erik W. <om...@vc...> - 2005-08-19 16:28:36
|
Hugo Vanwoerkom wrote: > Did you run this setup on a vanilla system (no > patches) first and does it crash then? Yup, when I run with just one head it's been rock solid for the duration of testing. I'll run it singleheaded all this weekend while I'm gone, and get someone to prod it periodically to make sure. |
|
From: Andrej v. d. Z. <ma...@ya...> - 2005-08-19 12:38:52
|
Here is the log of the second X server that causes the hanging: XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-14 20050601051219 fab...@fa...) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.29-pre2 i686 [ELF] Build Date: 01 June 2005 This version of XFree86 has been extensively modified by the Debian Project, and is not supported by the XFree86 Project, Inc., in any way. Bugs should be reported to the Debian Bug Tracking System; see <URL: http://www.debian.org/Bugs/Reporting >. We strongly encourage the use of the "reportbug" package and command to ensure that bug reports contain as much useful information as possible. Before filing a bug report, you may want to consult the Debian X FAQ: XHTML version: file:///usr/share/doc/xfree86-common/FAQ.xhtml plain text version: file:///usr/share/doc/xfree86-common/FAQ.gz Module Loader present OS Kernel: Linux version 2.6.11-ruby (root@andrej) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #3 Sun Jul 31 22:38:40 CEST 2005 TF Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.1.log", Time: Fri Aug 19 14:30:05 2005 (==) Using config file: "/etc/X11/XF86Config-4" (==) ServerLayout "X0" (**) |-->Screen "Screen CRT" (0) (**) | |-->Monitor "Trust CRT" (**) | |-->Device "GeForce FX5200 CRT" (**) |-->Input Device "Keyboard2" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "Mouse1" (WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist. Entry deleted from font path. (WW) The directory "/usr/lib/X11/fonts/CID" does not exist. Entry deleted from font path. (**) FontPath set to "/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi" (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (**) Option "PciOsConfig" "1" (++) using VT number 8 (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2570 card 1043,8110 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2571 card 0000,0000 rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,24d2 card 1043,80a6 rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24d4 card 1043,80a6 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24d7 card 1043,80a6 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:3: chip 8086,24de card 1043,80a6 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24dd card 1043,80a6 rev 02 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev c2 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24d0 card 0000,0000 rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24db card 1043,80a6 rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,24d3 card 1043,80a6 rev 02 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,24d5 card 1043,810d rev 02 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0185 card 0000,0000 rev c1 class 03,00,00 hdr 00 (II) PCI: 02:05:0: chip 10ec,8139 card 1043,8109 rev 10 class 02,00,00 hdr 00 (II) PCI: 02:0a:0: chip 10de,0322 card 1682,203e rev a1 class 03,00,00 hdr 00 (II) PCI: 02:0d:0: chip 4444,0016 card 0070,8003 rev 01 class 04,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0000 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0 0x0000d000 - 0x0000dfff (0x1000) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xf8f00000 - 0xf9ffffff (0x1100000) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xe0000000 - 0xebffffff (0xc000000) MX[B] (II) PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:30:0), (0,2,2), BCTRL: 0x000a (VGA_EN is set) (II) Bus 2 I/O range: [0] -1 0 0x0000e000 - 0x0000efff (0x1000) IX[B] (II) Bus 2 non-prefetchable memory range: [0] -1 0 0xfa000000 - 0xfbffffff (0x2000000) MX[B] (II) Bus 2 prefetchable memory range: [0] -1 0 0xec000000 - 0xf7ffffff (0xc000000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI: (1:0:0) nVidia Corporation unknown chipset (0x0185) rev 193, Mem @ 0xf9000000/24, 0xe0000000/27, BIOS @ 0xf8fe0000/17 (--) PCI:*(2:10:0) nVidia Corporation NV34 [GeForce FX 5200] rev 161, Mem @ 0xfa000000/24, 0xf0000000/27, BIOS @ 0xfbfc0000/17 (--) PCI: (2:13:0) unknown vendor (0x4444) unknown chipset (0x0016) rev 1, Mem @ 0xec000000/26 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xd8000000 from 0xdfffffff to 0xd7ffffff (II) Active PCI resource ranges: [0] -1 0 0xfbfffc00 - 0xfbfffcff (0x100) MX[B] [1] -1 0 0xf8eff400 - 0xf8eff4ff (0x100) MX[B] [2] -1 0 0xf8eff800 - 0xf8eff9ff (0x200) MX[B] [3] -1 0 0x20000000 - 0x200003ff (0x400) MX[B] [4] -1 0 0xf8effc00 - 0xf8efffff (0x400) MX[B] [5] -1 0 0xd8000000 - 0xd7ffffff (0x0) MX[B]O [6] -1 0 0xec000000 - 0xefffffff (0x4000000) MX[B](B) [7] -1 0 0xfbfc0000 - 0xfbfdffff (0x20000) MX[B](B) [8] -1 0 0xf0000000 - 0xf7ffffff (0x8000000) MX[B](B) [9] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B) [10] -1 0 0xf8fe0000 - 0xf8ffffff (0x20000) MX[B](B) [11] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B) [12] -1 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B](B) [13] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B] [14] -1 0 0x0000c400 - 0x0000c43f (0x40) IX[B] [15] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B] [16] -1 0 0x00000400 - 0x0000041f (0x20) IX[B] [17] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B] [18] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B] [19] -1 0 0x0000c880 - 0x0000c89f (0x20) IX[B] [20] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [21] -1 0 0x0000c480 - 0x0000c49f (0x20) IX[B] (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xfbfffc00 - 0xfbfffcff (0x100) MX[B] [1] -1 0 0xf8eff400 - 0xf8eff4ff (0x100) MX[B] [2] -1 0 0xf8eff800 - 0xf8eff9ff (0x200) MX[B] [3] -1 0 0x20000000 - 0x200003ff (0x400) MX[B] [4] -1 0 0xf8effc00 - 0xf8efffff (0x400) MX[B] [5] -1 0 0xd8000000 - 0xd7ffffff (0x0) MX[B]O [6] -1 0 0xec000000 - 0xefffffff (0x4000000) MX[B](B) [7] -1 0 0xfbfc0000 - 0xfbfdffff (0x20000) MX[B](B) [8] -1 0 0xf0000000 - 0xf7ffffff (0x8000000) MX[B](B) [9] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B) [10] -1 0 0xf8fe0000 - 0xf8ffffff (0x20000) MX[B](B) [11] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B) [12] -1 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B](B) [13] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B] [14] -1 0 0x0000c400 - 0x0000c43f (0x40) IX[B] [15] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B] [16] -1 0 0x00000400 - 0x0000041f (0x20) IX[B] [17] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B] [18] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B] [19] -1 0 0x0000c880 - 0x0000c89f (0x20) IX[B] [20] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [21] -1 0 0x0000c480 - 0x0000c49f (0x20) IX[B] (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x1fffffff (0x1ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x1fffffff (0x1ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xfbfffc00 - 0xfbfffcff (0x100) MX[B] [6] -1 0 0xf8eff400 - 0xf8eff4ff (0x100) MX[B] [7] -1 0 0xf8eff800 - 0xf8eff9ff (0x200) MX[B] [8] -1 0 0x20000000 - 0x200003ff (0x400) MX[B] [9] -1 0 0xf8effc00 - 0xf8efffff (0x400) MX[B] [10] -1 0 0xd8000000 - 0xd7ffffff (0x0) MX[B]O [11] -1 0 0xec000000 - 0xefffffff (0x4000000) MX[B](B) [12] -1 0 0xfbfc0000 - 0xfbfdffff (0x20000) MX[B](B) [13] -1 0 0xf0000000 - 0xf7ffffff (0x8000000) MX[B](B) [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B) [15] -1 0 0xf8fe0000 - 0xf8ffffff (0x20000) MX[B](B) [16] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B) [17] -1 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B](B) [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [20] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B] [21] -1 0 0x0000c400 - 0x0000c43f (0x40) IX[B] [22] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B] [23] -1 0 0x00000400 - 0x0000041f (0x20) IX[B] [24] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B] [25] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B] [26] -1 0 0x0000c880 - 0x0000c89f (0x20) IX[B] [27] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [28] -1 0 0x0000c480 - 0x0000c49f (0x20) IX[B] (II) LoadModule: "bitmap" (II) Reloading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Loading font Bitmap (II) LoadModule: "dbe" (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.2 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "ddc" (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) LoadModule: "dri" (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.2 (II) Loading sub module "drm" (II) LoadModule: "drm" (II) Loading /usr/X11R6/lib/modules/linux/libdrm.a (II) Module drm: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.0 ABI class: XFree86 Server Extension, version 0.2 (II) Loading extension XFree86-DRI (II) LoadModule: "extmod" (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a (II) Module extmod: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.2 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension FontCache (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "freetype" (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.a (II) Module freetype: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 2.0.2 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font FreeType (II) LoadModule: "glx" (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so (II) Module glx: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.7174 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.1 (II) Loading extension GLX (II) LoadModule: "int10" (II) Loading /usr/X11R6/lib/modules/linux/libint10.a (II) Module int10: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) LoadModule: "record" (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.13.0 Module class: XFree86 Server Extension ABI class: XFree86 Server Extension, version 0.2 (II) Loading extension RECORD (II) LoadModule: "speedo" (II) Loading /usr/X11R6/lib/modules/fonts/libspeedo.a Skipping "/usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o": No symbols found (II) Module speedo: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.1 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Speedo (II) LoadModule: "type1" (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a (II) Module type1: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.2 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Type1 (II) Loading font CID (II) LoadModule: "vbe" (II) Loading /usr/X11R6/lib/modules/libvbe.a (II) Module vbe: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.1.0 ABI class: XFree86 Video Driver, version 0.6 (II) LoadModule: "nvidia" (II) Loading /usr/X11R6/lib/modules/drivers/nvidia_drv.o (II) Module nvidia: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.7174 Module class: XFree86 Video Driver (II) LoadModule: "mouse" (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.4 (II) NVIDIA X Driver 1.0-7174 Tue Mar 22 06:48:37 PST 2005 (II) NVIDIA Unified Driver for all NVIDIA GPUs (II) Primary Device is: PCI 02:0a:0 (WW) NVIDIA: No matching Device section for instance (BusID PCI:1:0:0) found (--) Chipset NVIDIA GPU found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x1fffffff (0x1ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xfbfffc00 - 0xfbfffcff (0x100) MX[B] [6] -1 0 0xf8eff400 - 0xf8eff4ff (0x100) MX[B] [7] -1 0 0xf8eff800 - 0xf8eff9ff (0x200) MX[B] [8] -1 0 0x20000000 - 0x200003ff (0x400) MX[B] [9] -1 0 0xf8effc00 - 0xf8efffff (0x400) MX[B] [10] -1 0 0xd8000000 - 0xd7ffffff (0x0) MX[B]O [11] -1 0 0xec000000 - 0xefffffff (0x4000000) MX[B](B) [12] -1 0 0xfbfc0000 - 0xfbfdffff (0x20000) MX[B](B) [13] -1 0 0xf0000000 - 0xf7ffffff (0x8000000) MX[B](B) [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B) [15] -1 0 0xf8fe0000 - 0xf8ffffff (0x20000) MX[B](B) [16] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B) [17] -1 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B](B) [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [20] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B] [21] -1 0 0x0000c400 - 0x0000c43f (0x40) IX[B] [22] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B] [23] -1 0 0x00000400 - 0x0000041f (0x20) IX[B] [24] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B] [25] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B] [26] -1 0 0x0000c880 - 0x0000c89f (0x20) IX[B] [27] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [28] -1 0 0x0000c480 - 0x0000c49f (0x20) IX[B] (II) resource ranges after probing: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x1fffffff (0x1ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xfbfffc00 - 0xfbfffcff (0x100) MX[B] [6] -1 0 0xf8eff400 - 0xf8eff4ff (0x100) MX[B] [7] -1 0 0xf8eff800 - 0xf8eff9ff (0x200) MX[B] [8] -1 0 0x20000000 - 0x200003ff (0x400) MX[B] [9] -1 0 0xf8effc00 - 0xf8efffff (0x400) MX[B] [10] -1 0 0xd8000000 - 0xd7ffffff (0x0) MX[B]O [11] -1 0 0xec000000 - 0xefffffff (0x4000000) MX[B](B) [12] -1 0 0xfbfc0000 - 0xfbfdffff (0x20000) MX[B](B) [13] -1 0 0xf0000000 - 0xf7ffffff (0x8000000) MX[B](B) [14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B) [15] -1 0 0xf8fe0000 - 0xf8ffffff (0x20000) MX[B](B) [16] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B) [17] -1 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B](B) [18] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [19] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [20] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [21] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [22] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [23] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B] [24] -1 0 0x0000c400 - 0x0000c43f (0x40) IX[B] [25] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B] [26] -1 0 0x00000400 - 0x0000041f (0x20) IX[B] [27] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B] [28] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B] [29] -1 0 0x0000c880 - 0x0000c89f (0x20) IX[B] [30] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [31] -1 0 0x0000c480 - 0x0000c49f (0x20) IX[B] [32] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [33] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32 (==) NVIDIA(0): RGB weight 888 (==) NVIDIA(0): Default visual is TrueColor (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) (**) NVIDIA(0): Option "NoLogo" "True" (**) NVIDIA(0): Option "NvAGP" "1" (**) NVIDIA(0): Option "ConnectedMonitor" "crt" (**) NVIDIA(0): Option "RenderAccel" "true" (**) NVIDIA(0): Option "TVOverScan" "1.0" (**) NVIDIA(0): Enabling experimental RENDER acceleration (**) NVIDIA(0): Use of NVIDIA internal AGP requested (**) NVIDIA(0): ConnectedMonitor string: "crt" (--) NVIDIA(0): Linear framebuffer at 0xF0000000 (--) NVIDIA(0): MMIO registers at 0xFA000000 (II) NVIDIA(0): NVIDIA GPU detected as: GeForce FX 5200 (--) NVIDIA(0): VideoBIOS: 04.34.20.27.02 (--) NVIDIA(0): Interlaced video modes are supported on this GPU (--) NVIDIA(0): VideoRAM: 131072 kBytes (II) NVIDIA(0): Using ConnectedMonitor string "CRT-0" (--) NVIDIA(0): Display device CRT-0: maximum pixel clock at 8 bpp: 400 MHz (--) NVIDIA(0): Display device CRT-0: maximum pixel clock at 16 bpp: 400 MHz (--) NVIDIA(0): Display device CRT-0: maximum pixel clock at 32 bpp: 400 MHz (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/X11R6/lib/modules/libddc.a (II) NVIDIA(0): Trust CRT: Using hsync range of 30.00-70.00 kHz (II) NVIDIA(0): Trust CRT: Using vrefresh range of 50.00-120.00 Hz (II) NVIDIA(0): Clock range: 12.00 to 400.00 MHz (II) NVIDIA(0): Not using default mode "1280x960" (hsync out of range) (II) NVIDIA(0): Not using default mode "640x480" (hsync out of range) (II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range) (II) NVIDIA(0): Not using default mode "640x512" (hsync out of range) (II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range) (II) NVIDIA(0): Not using default mode "640x512" (hsync out of range) (II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range) (II) NVIDIA(0): Not using default mode "800x600" (hsync out of range) (II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range) (II) NVIDIA(0): Not using default mode "800x600" (hsync out of range) (II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range) (II) NVIDIA(0): Not using default mode "800x600" (hsync out of range) (II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range) (II) NVIDIA(0): Not using default mode "800x600" (hsync out of range) (II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range) (II) NVIDIA(0): Not using default mode "800x600" (hsync out of range) (II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range) (II) NVIDIA(0): Not using default mode "896x672" (hsync out of range) (II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range) (II) NVIDIA(0): Not using default mode "896x672" (hsync out of range) (II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range) (II) NVIDIA(0): Not using default mode "928x696" (hsync out of range) (II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range) (II) NVIDIA(0): Not using default mode "928x696" (hsync out of range) (II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range) (II) NVIDIA(0): Not using default mode "960x720" (hsync out of range) (II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range) (II) NVIDIA(0): Not using default mode "960x720" (hsync out of range) (II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range) (II) NVIDIA(0): Not using default mode "700x525" (hsync out of range) (II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range) (II) NVIDIA(0): Not using default mode "960x720" (hsync out of range) (II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range) (II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range) (II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range) (II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range) (II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range) (II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range) (II) NVIDIA(0): Not using default mode "1400x1050" (width too large for virtual size) (WW) NVIDIA(0): Not using mode "700x525" (height 1050 is larger than (WW) NVIDIA(0): EDID-specified maximum 1024) (WW) NVIDIA(0): Not using mode "1152x768": (WW) NVIDIA(0): horizontal sync start (1178) not a multiple of 8 (WW) NVIDIA(0): Not using mode "576x384": (WW) NVIDIA(0): horizontal sync start (589) not a multiple of 8 (WW) NVIDIA(0): Not using mode "360x200": (WW) NVIDIA(0): horizontal sync start (378) not a multiple of 8 (**) NVIDIA(0): Validated modes for display device CRT-0: (**) NVIDIA(0): Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz (**) NVIDIA(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz (**) NVIDIA(0): Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz (**) NVIDIA(0): Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz (**) NVIDIA(0): Default mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0 Hz (**) NVIDIA(0): Default mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz (**) NVIDIA(0): Default mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz (**) NVIDIA(0): Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz (**) NVIDIA(0): Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz (**) NVIDIA(0): Default mode "1024x768": 44.9 MHz, 35.5 kHz, 87.0 Hz (I) (**) NVIDIA(0): Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz (**) NVIDIA(0): Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz (**) NVIDIA(0): Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz (**) NVIDIA(0): Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz (**) NVIDIA(0): Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz (**) NVIDIA(0): Default mode "640x512": 54.0 MHz, 64.0 kHz, 60.0 Hz (D) (**) NVIDIA(0): Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz (**) NVIDIA(0): Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz (**) NVIDIA(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (**) NVIDIA(0): Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D) (**) NVIDIA(0): Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz (**) NVIDIA(0): Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz (**) NVIDIA(0): Default mode "576x432": 54.0 MHz, 67.5 kHz, 75.0 Hz (D) (**) NVIDIA(0): Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz (**) NVIDIA(0): Default mode "512x384": 47.2 MHz, 68.7 kHz, 85.0 Hz (D) (**) NVIDIA(0): Default mode "512x384": 39.4 MHz, 60.1 kHz, 75.1 Hz (D) (**) NVIDIA(0): Default mode "512x384": 37.5 MHz, 56.5 kHz, 70.1 Hz (D) (**) NVIDIA(0): Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D) (**) NVIDIA(0): Default mode "512x384": 22.4 MHz, 35.5 kHz, 86.9 Hz (D) (**) NVIDIA(0): Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D) (**) NVIDIA(0): Default mode "400x300": 28.1 MHz, 53.7 kHz, 85.3 Hz (D) (**) NVIDIA(0): Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D) (**) NVIDIA(0): Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D) (**) NVIDIA(0): Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D) (**) NVIDIA(0): Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D) (**) NVIDIA(0): Default mode "320x240": 18.0 MHz, 43.3 kHz, 85.2 Hz (D) (**) NVIDIA(0): Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D) (**) NVIDIA(0): Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D) (**) NVIDIA(0): Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D) (**) NVIDIA(0): Default mode "320x200": 15.8 MHz, 37.9 kHz, 85.3 Hz (D) (**) NVIDIA(0): Default mode "320x175": 15.8 MHz, 37.9 kHz, 85.3 Hz (D) (II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024 (--) NVIDIA(0): Display dimensions: (300, 230) mm (--) NVIDIA(0): DPI set to (108, 113) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/X11R6/lib/modules/libfb.a (II) Module fb: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 1.0.0 ABI class: XFree86 ANSI C Emulation, version 0.2 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/X11R6/lib/modules/libramdac.a (II) Module ramdac: vendor="The XFree86 Project" compiled for 4.3.0.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.6 (--) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xf0000000 - 0xf7ffffff (0x8000000) MX[B] [1] 0 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B] [2] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [3] -1 0 0x00100000 - 0x1fffffff (0x1ff00000) MX[B]E(B) [4] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [5] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [6] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [7] -1 0 0xfbfffc00 - 0xfbfffcff (0x100) MX[B] [8] -1 0 0xf8eff400 - 0xf8eff4ff (0x100) MX[B] [9] -1 0 0xf8eff800 - 0xf8eff9ff (0x200) MX[B] [10] -1 0 0x20000000 - 0x200003ff (0x400) MX[B] [11] -1 0 0xf8effc00 - 0xf8efffff (0x400) MX[B] [12] -1 0 0xd8000000 - 0xd7ffffff (0x0) MX[B]O [13] -1 0 0xec000000 - 0xefffffff (0x4000000) MX[B](B) [14] -1 0 0xfbfc0000 - 0xfbfdffff (0x20000) MX[B](B) [15] -1 0 0xf0000000 - 0xf7ffffff (0x8000000) MX[B](B) [16] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[B](B) [17] -1 0 0xf8fe0000 - 0xf8ffffff (0x20000) MX[B](B) [18] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B) [19] -1 0 0xf9000000 - 0xf9ffffff (0x1000000) MX[B](B) [20] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD) [21] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) [22] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) [23] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [24] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [25] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B] [26] -1 0 0x0000c400 - 0x0000c43f (0x40) IX[B] [27] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[B] [28] -1 0 0x00000400 - 0x0000041f (0x20) IX[B] [29] -1 0 0x0000fc00 - 0x0000fc0f (0x10) IX[B] [30] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B] [31] -1 0 0x0000c880 - 0x0000c89f (0x20) IX[B] [32] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [33] -1 0 0x0000c480 - 0x0000c49f (0x20) IX[B] [34] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [35] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (II) NVIDIA(0): Setting mode "1280x1024" (II) Loading extension NV-GLX (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture (==) NVIDIA(0): Backing store disabled (==) NVIDIA(0): Silken mouse enabled (**) Option "dpms" (**) NVIDIA(0): DPMS enabled (II) Loading extension NV-CONTROL (==) RandR enabled Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing extension GLX (II) Keyboard "Keyboard2" handled by legacy driver (**) Option "Protocol" "ImPS/2" (**) Mouse1: Protocol: "ImPS/2" (**) Option "CorePointer" (**) Mouse1: Core Pointer (**) Option "Device" "/dev/input/mouse0" (**) Option "Emulate3Buttons" "true" (**) Mouse1: Emulate3Buttons, Emulate3Timeout: 50 (**) Option "ZAxisMapping" "4 5" (**) Mouse1: ZAxisMapping: buttons 4 and 5 (**) Mouse1: Buttons: 5 (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE) (II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other) (II) Mouse1: ps2EnableDataReporting: succeeded Warning: font renderer for ".pcf" already registered at priority 0 Warning: font renderer for ".pcf.Z" already registered at priority 0 Warning: font renderer for ".pcf.gz" already registered at priority 0 Warning: font renderer for ".snf" already registered at priority 0 Warning: font renderer for ".snf.Z" already registered at priority 0 Warning: font renderer for ".snf.gz" already registered at priority 0 Warning: font renderer for ".bdf" already registered at priority 0 Warning: font renderer for ".bdf.Z" already registered at priority 0 Warning: font renderer for ".bdf.gz" already registered at priority 0 Warning: font renderer for ".pmf" already registered at priority 0 AUDIT: Fri Aug 19 14:30:33 2005: 7414 X: client 5 rejected from local host --- Andrej van der Zee <ma...@ya...> wrote: > Hi, > > I have a problem: > > Twice I installed Debian testing with a vanilla > kernel > (once with 2.6.7 and once with 2.6.11) and patched > it > with Backstreet Ruby. Everything seemed fine for > about > one month but then suddenly my system hangs (in the > gdm login screen) after starting the second X > server. > If I remove the lines from gdm.conf that start the > second X-server my system works fine (but what is > the > use of Ruby if I can start only one X-server?). > > I dont wanna start all over from scratch again. > Besides, I have no faith that this will not happen a > third time. Did anybody experience the same problem? > How can I solve this? I realy have no clue where to > look for... Maybe try another Linux distro and wait > for another month to see if it succeeds? There must > be > better way... > > Please help! > > Andrej > > > > > > > ___________________________________________________________ > > Yahoo! Messenger - NEW crystal clear PC to PC > calling worldwide with voicemail > http://uk.messenger.yahoo.com > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software > Conference & EXPO > September 19-22, 2005 * San Francisco, CA * > Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects > & Teams * Testing & QA > Security * Process Improvement & Measurement * > http://www.sqe.com/bsce5sf > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com |
|
From: Andrej v. d. Z. <ma...@ya...> - 2005-08-19 12:01:19
|
Hi, I have a problem: Twice I installed Debian testing with a vanilla kernel (once with 2.6.7 and once with 2.6.11) and patched it with Backstreet Ruby. Everything seemed fine for about one month but then suddenly my system hangs (in the gdm login screen) after starting the second X server. If I remove the lines from gdm.conf that start the second X-server my system works fine (but what is the use of Ruby if I can start only one X-server?). I dont wanna start all over from scratch again. Besides, I have no faith that this will not happen a third time. Did anybody experience the same problem? How can I solve this? I realy have no clue where to look for... Maybe try another Linux distro and wait for another month to see if it succeeds? There must be better way... Please help! Andrej ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com |
1998 messages has been excluded from this view by a project administrator.
