From: ludovic p. <pl...@nn...> - 2004-09-24 06:17:58
|
Hello... Le vendredi 24 Septembre 2004 00:46, Johannes Gajdosik a =E9crit : > The result in both cases is the same: according to > lspci -v the secondary display adapter has no memory. > Anyway it did not crash my computer. That is strange... Maybe the normal way of configuring pci devices doesn'= t=20 work on amd64 kernel.=20 That was my problem (due to the hackvideo thing), and in this case, X rep= orts=20 no errors but silently fails to set the pci configuration... Can you try the same setpci command with the swithch -H1 ? It asks setpci= to=20 bypass the kernel when accessing the pci bus. > Up to now only one configuration has some promising results: > MGA is primary, NVidia secondary, i386 kernel: > In this case I can start the first XServer on the NVidia (vt7), > and then a second Xserver on the MGA (vt17). Both Xservers > have the prefbusid patch. That looks like a virtual console problem...=20 If the MGA is primay, I suppose it is used for the vga console display. I= n=20 this case you should start the MGA x server on vt7, and NVidia on vt17. Appart from the keyboard problem, is the first server really dead ?=20 (ie does it respond to mouse click ... ) If not, you can try killing the = X=20 server with the SIGUSR1 signal. And are you sure that the prefbusid is correctly set ? I think it is deci= mal,=20 while lspci reports hexadecimal bus id... Ludovic Pollet --=20 If it happens once, it's a bug. If it happens twice, it's a feature. If it happens more than twice, it's a design philosophy. |