Menu
▾
▴
linuxconsole-dev
|
From: Boszormenyi Z. <zb...@fr...> - 2004-03-08 11:40:42
|
Hi, my system is Fedora Core 1, running linux-2.6.3-ruby (+ DRM-cvs-update.patch from the 2.6.4-rc1-mm2 patchset) and I have rebuilt XFree86-4.3.0-55 with the xf86-430-prefbusid3.diff patch. I have a Sapphire Radeon 9200SE 128M/TV-Out/AGP8x and a Sapphire Radeon 7000 PCI/32M/TV-Out and an MSI K8T Neo FIS2R with an Athlon64 3200+. I have successfully set it up as a dualhead machine with 2 PS/2 keyboards and 2 USB mice. This configuration is so good, even DRI works on both videocards! Two kids can play tuxracer at once. :-) I use the Option "PciOsConfig" "1" tweak but I don't use the echo "1" >/proc/bus/pci/hackvideo because it stalled one of the cards, gdm could not start it until I logged in and out on the other at first but then this card was stalled... Strange. So I stayed with the -prefbusid XFree86 option. There are few things that bugs me still. Some devices (like /dev/mixer) can only be used by the first login, no matter which display. Changes to /etc/security/console.perms is needed, users should be put into groups to be able to access devices but I can handle these kinds of problems. My main problem is that localhost:1.0 is destroyed by logging out on localhost:0.0. What cause this? The XFree86 patch is not enough? I can login/logout any time I want on :1.0 without disturbing :0.0. I have set up the two heads this way: - PS/2 keyb. on keyboard port + Radeon9200SE (:1.0) - PS/2 keyb. on mouse port + Radeon7000 (:0.0) (I don't think the the order of the USB mice makes any difference) If I change the order of displays, the effect is the same. I will try the rawhide XFree86-4.3.0-62 (that has fixes for not accessing the keyboard kontroller's IO ports directly) I will see if it fixes anything but I don't think it is the problem because swapping heads does not change things. I mean it's still :1.0 that is destroyed when logging out on :0.0. Maybe gdm is restarting one too many servers? I try to look into it... -- Best regards, Zoltán Böszörményi --------------------- What did Hussein say about his knife? One in Bush worth two in the hand. |
|
From: lumarga <lu...@it...> - 2004-05-28 19:17:49
|
Hi everyone, Excuse-me, I don't know where ask this, then I'm asking here. The problem: 'Successful ruby setup and a problem -- localhost:1.0 is destroyed by logging out on localhost:0.0 ' posted by Boszormenyi Zoltan and Wayne Whitney on March was solved in newer patch's? My video cards are: Trident Microsystems CyberBlade/i1 (onboard 1:0:0) and Trident Microsystems TGUI 9440 (rev e3) (0:8:0). My kernel: Linux slac90 2.4.25-backstreet-ruby My XFree86: Version 4.3.0 - X Protocol Version 11, Revision 0, Release 6.6 - patch xf86-430-prefbusid3.diff (from http://disjunkt.com/dualhead/) My Display Manager: gdm. I'm a bad English writer. Thanks, Celso.Silva |
|
From: <ce...@ri...> - 2004-05-30 10:04:32
|
lumarga wrote: > Hi everyone, > Excuse-me, I don't know where ask this, then I'm asking here. > The problem: 'Successful ruby setup and a problem -- localhost:1.0 > is destroyed by logging out on localhost:0.0 ' posted by Boszormenyi > Zoltan and Wayne Whitney on March was solved in newer patch's? No, there is no patch for this issue which was discussed specifically to=20 ATI radeon cards. Maybe, Wayne could post his Xfree hack used to restore=20 the display but this should not be relevant to you since you have=20 different hardware. Would you suggest that you experience the same behavior because you have=20 also cards based on an identical graphic chipset ? > My video cards are: Trident Microsystems CyberBlade/i1 (onboard 1:0:0) > and Trident Microsystems TGUI 9440 (rev e3) (0:8:0). > My kernel: Linux slac90 2.4.25-backstreet-ruby > My XFree86: Version 4.3.0 - X Protocol Version 11, Revision 0, > Release 6.6 - patch xf86-430-prefbusid3.diff (from > http://disjunkt.com/dualhead/) > My Display Manager: gdm. Don't know anything particular about Trident cards. You should post=20 configuration and log files to give a good understanding of your setup. >=20 > I'm a bad English writer. You can write me privately in portuguese if it can help. Cheers, C=E9dric |
|
From: Helge H. <hel...@ai...> - 2004-03-09 08:11:34
|
Boszormenyi Zoltan wrote: > Hi, > > my system is Fedora Core 1, running linux-2.6.3-ruby > (+ DRM-cvs-update.patch from the 2.6.4-rc1-mm2 patchset) > and I have rebuilt XFree86-4.3.0-55 with the > xf86-430-prefbusid3.diff patch. > > I have a Sapphire Radeon 9200SE 128M/TV-Out/AGP8x and > a Sapphire Radeon 7000 PCI/32M/TV-Out and an MSI > K8T Neo FIS2R with an Athlon64 3200+. > > I have successfully set it up as a dualhead > machine with 2 PS/2 keyboards and 2 USB mice. > > This configuration is so good, even DRI works on both videocards! > Two kids can play tuxracer at once. :-) I'm very interested in how you got the dual DRI part working. I use ruby 2.6.2, with DRI on one screen only. The other uses software rendering so I have 3D there too, but _way_ too slow for tuxracer. Is this setup open-source only, or do you use some closed 3D driver? Did you do anything special to get this, other than compiling your own patched xserver? Also, it looks like you have a single cpu. Are both games nice and smooth with such a setup, or does the first game get noticeably worse when the second one starts? I've noticed that tuxracer doesn't like a compile going on at the same time, but that's on a 333MHz processor. A dual cpu setup fixed that for me. > My main problem is that localhost:1.0 is destroyed by logging > out on localhost:0.0. Destroyed how - logging out kills the other xserver too? Helge Hafting |
|
From: Boszormenyi Z. <zb...@fr...> - 2004-03-09 08:43:36
|
Helge Hafting =EDrta: > Boszormenyi Zoltan wrote: > = >> Hi, >> >> my system is Fedora Core 1, running linux-2.6.3-ruby >> (+ DRM-cvs-update.patch from the 2.6.4-rc1-mm2 patchset) >> and I have rebuilt XFree86-4.3.0-55 with the >> xf86-430-prefbusid3.diff patch. >> >> I have a Sapphire Radeon 9200SE 128M/TV-Out/AGP8x and >> a Sapphire Radeon 7000 PCI/32M/TV-Out and an MSI >> K8T Neo FIS2R with an Athlon64 3200+. >> >> I have successfully set it up as a dualhead >> machine with 2 PS/2 keyboards and 2 USB mice. >> >> This configuration is so good, even DRI works on both videocards! >> Two kids can play tuxracer at once. :-) > = > = > I'm very interested in how you got the dual DRI part working. I use > ruby 2.6.2, with DRI on one screen only. The other uses software > rendering so I have 3D there too, but _way_ too slow for tuxracer. > = > Is this setup open-source only, or do you use some closed 3D driver? I used the opensource driver. > Did you do anything special to get this, other than compiling your own > patched xserver? Yes, patched the kernel with the updated DRM driver, too. I put these to /etc/rc.d/rc.local: modprobe amd64-agp modprobe radeon dmesg reports now two DRI devices, the old DRM driver did not report anything. Minor 0 is the PCI Radeon, minor 1 is AGP Radeon. My first attempts setting up DRI on both cards failed. I used the AGP Radeon for :0.0 and the PCI one for :1.0, this did not work. Somehow the detection code cannot work out this config, it tries to set the "private label" of the DRI device to the PCI bus id of the device and it fails somehow. Changing the display order makes DRI work on both! > Also, it looks like you have a single cpu. Are both games nice > and smooth with such a setup, or does the first game get > noticeably worse when the second one starts? They both show occasional hiccups (some frames lost) but they are very fast. Yes, a single CPU but such a beast! :-) Running at 2GHz with an 1MB L2 cache. Did I say Athlon64 3200+? I think that the scheduler tweaks that made their way into 2.6.4-rc2-mm1 would help here. > I've noticed that tuxracer doesn't like a compile going on at > the same time, but that's on a 333MHz processor. A dual cpu > setup fixed that for me. Playing a movie in Xine while rpmbuild --rebuild XFree86 causes sound dropouts (very rare) and frame drops (even less) That's with the onboard AC97 sound card. >> My main problem is that localhost:1.0 is destroyed by logging >> out on localhost:0.0. > = > = > Destroyed how - logging out kills the other xserver too? The monitor goes black, looks powersave mode but it's not. Pressing Ctrl-Alt-BkSpace brings back the gdm login. -- = Best regards, Zolt=E1n B=F6sz=F6rm=E9nyi --------------------- What did Hussein say about his knife? One in Bush worth two in the hand. |
|
From: Svetoslav S. <sv...@gm...> - 2004-03-09 09:20:27
|
Hi, > >> my system is Fedora Core 1, running linux-2.6.3-ruby > >> (+ DRM-cvs-update.patch from the 2.6.4-rc1-mm2 patchset) > >> and I have rebuilt XFree86-4.3.0-55 with the > >> xf86-430-prefbusid3.diff patch. > >> > >> I have a Sapphire Radeon 9200SE 128M/TV-Out/AGP8x and > >> a Sapphire Radeon 7000 PCI/32M/TV-Out and an MSI > >> K8T Neo FIS2R with an Athlon64 3200+. > >> > >> I have successfully set it up as a dualhead > >> machine with 2 PS/2 keyboards and 2 USB mice. > >> > >> This configuration is so good, even DRI works on both videocards! > >> Two kids can play tuxracer at once. :-) > > > > > > > > I'm very interested in how you got the dual DRI part working. I use > > ruby 2.6.2, with DRI on one screen only. The other uses software > > rendering so I have 3D there too, but _way_ too slow for tuxracer. > > me too, very, very interested :-) the other good news is that the dri developers are planing to integrate it in XF-5.0 http://www.alsa-project.org/links.php3 [points 6 & 7] but i wasn't ware it's already present > > Is this setup open-source only, or do you use some closed 3D driver? > > I used the opensource driver. > > > Did you do anything special to get this, other than compiling your own > > patched xserver? > > Yes, patched the kernel with the updated DRM driver, too. > I put these to /etc/rc.d/rc.local: > > modprobe amd64-agp > modprobe radeon > > dmesg reports now two DRI devices, the old DRM driver did not report > anything. Minor 0 is the PCI Radeon, minor 1 is AGP Radeon. > My first attempts setting up DRI on both cards failed. > I used the AGP Radeon for :0.0 and the PCI one for :1.0, > this did not work. Somehow the detection code cannot work out > this config, it tries to set the "private label" of the DRI device > to the PCI bus id of the device and it fails somehow. > Changing the display order makes DRI work on both! > could you post somewere on a http/ftp server XF config files, logs, glxinfo output ? > > Also, it looks like you have a single cpu. Are both games nice > > and smooth with such a setup, or does the first game get > > noticeably worse when the second one starts? > > They both show occasional hiccups (some frames lost) but they > are very fast. Yes, a single CPU but such a beast! :-) > Running at 2GHz with an 1MB L2 cache. Did I say Athlon64 3200+? > I think that the scheduler tweaks that made their way into > 2.6.4-rc2-mm1 would help here. and more importantly the cpu is not 32bit, but 64 :-) !!! you are the first non i386 ruby user !!!! isn't it great that ruby also works on other archs :-) which remainds me, have you applied the x86_64 ruby changes ? > > I've noticed that tuxracer doesn't like a compile going on at > > the same time, but that's on a 333MHz processor. A dual cpu > > setup fixed that for me. > > Playing a movie in Xine while rpmbuild --rebuild XFree86 > causes sound dropouts (very rare) and frame drops (even less) > That's with the onboard AC97 sound card. are all the apps compiled for 64bit? i would expect no problems with such a beast CPU, have you tried updating alsa ? another soundcard? i don't see such problems with amd XP2700 1024 MB DDR333 RAM sb audigy radeon AIW 7500 AGP geforce4 440 PCI > >> My main problem is that localhost:1.0 is destroyed by logging > >> out on localhost:0.0. > > > > Destroyed how - logging out kills the other xserver too? > > The monitor goes black, looks powersave mode but it's not. > Pressing Ctrl-Alt-BkSpace brings back the gdm login. > have you tried disabling all DPMS stuff in XFree and kernel ? some time ago my monitor used to go in power saving even as i type and i think Andreas Schuldei had the same problem i think disabling : power managment --> APM ... --> enable console blanking ... fixed it best, svetljo -- +++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++ 100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz |
|
From: Boszormenyi Z. <zb...@fr...> - 2004-03-09 09:48:36
|
Svetoslav Slavtchev =EDrta: > could you post somewere on a http/ftp server XF config files, logs, > glxinfo output ? I gather them for tomorrow, it's my home machine. > and more importantly the cpu is not 32bit, but 64 :-) > !!! you are the first non i386 ruby user !!!! This is not true, yet. :-) The system is i386 version of Fedora Core 1. I am downloading the ISOs of FC1/x86_64 now... > isn't it great that ruby also works on other archs :-) > = > which remainds me, > have you applied the x86_64 ruby changes ? Where are they? The CVS contains arch/i386 but no other archs. >>>I've noticed that tuxracer doesn't like a compile going on at >>>the same time, but that's on a 333MHz processor. A dual cpu >>>setup fixed that for me. >> >>Playing a movie in Xine while rpmbuild --rebuild XFree86 >>causes sound dropouts (very rare) and frame drops (even less) >>That's with the onboard AC97 sound card. > = > = > are all the apps compiled for 64bit? > i would expect no problems with such a beast CPU, > have you tried updating alsa ? > another soundcard? > i don't see such problems with = > amd XP2700 = > 1024 MB DDR333 RAM I only have 512M, but DDR400. > sb audigy I also have an SB Live! 1024. > radeon AIW 7500 AGP = > geforce4 440 PCI = > = > = >>>>My main problem is that localhost:1.0 is destroyed by logging >>>>out on localhost:0.0. >>> >>>Destroyed how - logging out kills the other xserver too? >> >>The monitor goes black, looks powersave mode but it's not. >>Pressing Ctrl-Alt-BkSpace brings back the gdm login. > = > have you tried disabling all DPMS stuff in XFree and kernel ? That should not be a problem, as I said I can login/logout on display :1.0 any time I want, it does not bother display :0.0. It's logging out on :0.0 that confuses :1.0, its monitor goes blank. On :0.0 the gdm login screen comes back as it should on logout. > some time ago my monitor used to go in power saving even as i type > and i think Andreas Schuldei had the same problem > i think disabling : > power managment --> APM ... --> enable console blanking ... = > fixed it I use ACPI on this machine. -- = Best regards, Zolt=E1n B=F6sz=F6rm=E9nyi --------------------- What did Hussein say about his knife? One in Bush worth two in the hand. |
|
From: Boszormenyi Z. <zb...@fr...> - 2004-03-09 10:41:25
|
Boszormenyi Zoltan =EDrta: > Svetoslav Slavtchev =EDrta: >> which remainds me, >> have you applied the x86_64 ruby changes ? > = > Where are they? The CVS contains arch/i386 but no other archs. Never mind, the arch/i386/setup.c has five lines deleted compared to the mainstream kernel, I can delete those lines from arch/x86_64/setup.c by hand, there is no other arch dependent difference. -- = Best regards, Zolt=E1n B=F6sz=F6rm=E9nyi --------------------- What did Hussein say about his knife? One in Bush worth two in the hand. |
|
From: Boszormenyi Z. <zb...@fr...> - 2004-03-10 07:05:56
|
Svetoslav Slavtchev =EDrta: > could you post somewere on a http/ftp server XF config files, logs, > glxinfo output ? http://www.users.broadband.hu/forsz98kft/dd.tar.gz (dd for dual-display) $ tar tzvf dd.tar.gz -rw-rw-r-- zozo/zozo 12747 2004-03-09 17:00:22 dmesg.log -rw-r--r-- zozo/zozo 18324 2004-03-09 17:01:39 gdm.conf -rw-rw-r-- zozo/zozo 3143 2004-03-09 17:49:23 glxinfo.0.0.log -rw-rw-r-- zozo/zozo 2980 2004-03-09 17:49:28 glxinfo.1.0.log -rwxr-xr-x zozo/zozo 292 2004-03-09 17:01:10 rc.local -rw-r--r-- zozo/zozo 4264 2004-03-09 17:42:13 XF86Config -rw-r--r-- zozo/zozo 53918 2004-03-09 17:39:20 XFree86.0.log -rw-r--r-- zozo/zozo 47124 2004-03-09 17:39:21 XFree86.1.log -rw-rw-r-- zozo/zozo 3070 2004-03-09 17:50:59 xvinfo.0.0.log -rw-rw-r-- zozo/zozo 3065 2004-03-09 17:50:54 xvinfo.1.0.log >>The monitor goes black, looks powersave mode but it's not. >>Pressing Ctrl-Alt-BkSpace brings back the gdm login. > = > have you tried disabling all DPMS stuff in XFree and kernel ? Tried it, did not really help. I have disabled dpms in the monitor section of the XF86Config, and after restarting both displays by pressing Ctrl-Alt-BkSpace, it worked. I was able to login/logout on both displays without disturbing the other one. Reboot: problem appeared again. -- = Best regards, Zolt=E1n B=F6sz=F6rm=E9nyi --------------------- What did Hussein say about his knife? One in Bush worth two in the hand. |
|
From: Svetoslav S. <sv...@gm...> - 2004-03-11 11:13:58
|
> >>The monitor goes black, looks powersave mode but it's not. > >>Pressing Ctrl-Alt-BkSpace brings back the gdm login. > > > > have you tried disabling all DPMS stuff in XFree and kernel ? > > Tried it, did not really help. I have disabled dpms in the monitor > section of the XF86Config, and after restarting both displays by > pressing Ctrl-Alt-BkSpace, it worked. I was able to login/logout > on both displays without disturbing the other one. > Reboot: problem appeared again. hm, strange :( have you tried also disabling DPMS in the device section ? best, svetljo PS: you might also try turning on & of dpms using xset, /* not just off, but on & off */ -- +++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++ 100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz |
|
From: Helge H. <hel...@ai...> - 2004-03-09 09:35:22
|
Boszormenyi Zoltan wrote: > Helge Hafting írta: [...] > > dmesg reports now two DRI devices, the old DRM driver did not report > anything. Minor 0 is the PCI Radeon, minor 1 is AGP Radeon. > My first attempts setting up DRI on both cards failed. > I used the AGP Radeon for :0.0 and the PCI one for :1.0, > this did not work. Somehow the detection code cannot work out > this config, it tries to set the "private label" of the DRI device > to the PCI bus id of the device and it fails somehow. > Changing the display order makes DRI work on both! > I have a matrox G550 AGP card, and I'm trying to figure out what PCI card to get, that will support DRI. Looks like the Sapphire radeon 7000 is a good choice. :-) >> Also, it looks like you have a single cpu. Are both games nice >> and smooth with such a setup, or does the first game get > > > noticeably worse when the second one starts? > > They both show occasional hiccups (some frames lost) but they > are very fast. Yes, a single CPU but such a beast! :-) > Running at 2GHz with an 1MB L2 cache. Did I say Athlon64 3200+? > I think that the scheduler tweaks that made their way into > 2.6.4-rc2-mm1 would help here. > Good to know. I'm planning to upgrade from the current dual 333MHz celeron, and dual opteron is kind of expensive right now. I want something 64-bit capable though. >> I've noticed that tuxracer doesn't like a compile going on at >> the same time, but that's on a 333MHz processor. A dual cpu >> setup fixed that for me. > >>> My main problem is that localhost:1.0 is destroyed by logging >>> out on localhost:0.0. >> >> Destroyed how - logging out kills the other xserver too? > > The monitor goes black, looks powersave mode but it's not. > Pressing Ctrl-Alt-BkSpace brings back the gdm login. I see something similiar, my current setup uses the matrox driver for the first screen and the framebuffer driver on the second framebuffer on the same card. Switching consoles on the first screen (or starting/stopping X) always switch mode on the other screen too. I always thought the problem was because it is a single card and features for the two displays aren't well separated in the driver because "everybody" uses it for dual-head single-keyboard setups where it doesn't matter. But now I'm not so sure. I fixed the login/logout problem by running a matrox-specific program that resets the mapping between framebuffers and vga connectors each time X runs. That fixes most of the problems for me. I have also noticed that something goes wrong with console blanking or some such. Leaving the computer alone overnight occationally gives me a black screen on the framebuffer screen, even though X is running there. X is unaware of it and doesn't repaint automatically, but moving a window around fixes that. Helge Hafting |
|
From: Boszormenyi Z. <zb...@fr...> - 2004-03-09 10:21:16
|
Helge Hafting =EDrta: > I have a matrox G550 AGP card, and I'm trying to figure out what PCI > card to get, that will support DRI. Looks like the Sapphire radeon 700= 0 > is a good choice. :-) My choice of buying two Radeons were not completely a jump in the dark. The XFree86 radeon driver uses the MMAPed registers, not the old VGA IO ports. The PCI BIOS and the kernel should separate PCI memory ranges correctly. So any PCI Radeons would do. I set them up at the very first for single user/ two screens mode. The XFree86 logfile contained a line saying that the cards share no resources. I was then encouraged to experiment further. I had planned such a setup years ago, the GGI people promised something like this, too. -- = Best regards, Zolt=E1n B=F6sz=F6rm=E9nyi --------------------- What did Hussein say about his knife? One in Bush worth two in the hand. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X