Menu
▾
▴
linuxconsole-dev
|
From: Kjetil K. <kj...@kj...> - 2004-05-11 20:19:31
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! Long time, no see! Seems to have been quiet around here lately...? Well, I bring some good news (and I need a little advice): Some of you=20 might allready know, thanks to some great work by Andreas Schuldei and=20 others, the patches to X most of us need to run multi-head setups have=20 been applied to the Debian packages, they have been in the unstable=20 release for 11 days now, and today, they are going into Sarge. Unless=20 it breaks the system of somebody who aren't using it, it will be in=20 Sarge when it some day is released as Stable! Which means, it will be=20 accessible to many more users. Cool, eh? The first version it can be=20 found in is 4.3.0.dfsg.1-1. There has been some changes to the patch however. It has been reviewed=20 by Branden Robinson in particular and the rest of the Debian X Strike=20 =46orce team. Branden felt that "PrefBusID" wasn't very descriptive of=20 what it really does, so it is in Debian known as "IsolateDevice". They=20 have also written some documentation to it and made some other minor=20 changes if I understand it correctly. In addition to "IsolateDevice",=20 it also has a "SingleCard" layout option.=20 If I have understood the branches in the repository, the diff is=20 available at http://necrotic.deadbeast.net/xsf/XFree86/branches-4.3.0-sid/debian/patches= /080_pci_isolate_device_feature.diff and I thought you guys might want to review it.=20 I haven't tried the new packages out myself yet, I plan to do it Real=20 Soon Now[tm]. But before I venture off into the somewhat unknown, I=20 just wanted to ask those who understand the patch: To reconfigure my X=20 servers to use the new Debian packages, all I have to do is=20 s/PrefBusID/IsolateDevice/g right? Then, I wondered about the HOWTO: Probably, we should now add some=20 Debian-specific notes, now that people most likely can just use Sarge=20 or Sid and get the X servers they need, but must use slightly different=20 options than the rest of the world. Unless you guys find Branden's=20 changes reasonable, and adopt and recommend the above patch to others=20 that want to get this stuff running, in which case the HOWTO could be=20 changed to reflect the new names. So, what do you think about that?=20 Cheers, Kjetil =2D --=20 Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAoTVLlE/Gp2pqC7wRAtQhAKCnfp+eQdfgd1YhdahxW4HcZDCpmACfYgul NWvQzlRwzWKt9FkYCMooQu4=3D =3DSmOY =2D----END PGP SIGNATURE----- |
|
From: Aivils <ai...@un...> - 2004-05-17 06:53:30
|
On Tuesday 11 May 2004 23:18, Kjetil Kjernsmo wrote: > Hi all! > > Long time, no see! Seems to have been quiet around here lately...? > > Well, I bring some good news (and I need a little advice): Some of you > might allready know, thanks to some great work by Andreas Schuldei and > others, the patches to X most of us need to run multi-head setups have > been applied to the Debian packages, they have been in the unstable > release for 11 days now, and today, they are going into Sarge. Unless > it breaks the system of somebody who aren't using it, it will be in > Sarge when it some day is released as Stable! Which means, it will be > accessible to many more users. Cool, eh? The first version it can be > found in is 4.3.0.dfsg.1-1. > > There has been some changes to the patch however. It has been reviewed > by Branden Robinson in particular and the rest of the Debian X Strike > Force team. Branden felt that "PrefBusID" wasn't very descriptive of > what it really does, so it is in Debian known as "IsolateDevice". They > have also written some documentation to it and made some other minor > changes if I understand it correctly. In addition to "IsolateDevice", > it also has a "SingleCard" layout option. > > If I have understood the branches in the repository, the diff is > available at > http://necrotic.deadbeast.net/xsf/XFree86/branches-4.3.0-sid/debian/patches/080_pci_isolate_device_feature.diff > and I thought you guys might want to review it. > > I haven't tried the new packages out myself yet, I plan to do it Real > Soon Now[tm]. But before I venture off into the somewhat unknown, I > just wanted to ask those who understand the patch: To reconfigure my X > servers to use the new Debian packages, all I have to do is > s/PrefBusID/IsolateDevice/g > right? Yep. > Then, I wondered about the HOWTO: Probably, we should now add some > Debian-specific notes, now that people most likely can just use Sarge > or Sid and get the X servers they need, but must use slightly different > options than the rest of the world. If end-user will start muptiple local xf86, then "IsolateDevice" is not enough. Each xf86 open /dev/ttyXX , which one current is allowed under Linus-tree kernel. Secondary xf86 become active when user press Alt-F8 and primary xf86 goes spleep until user activate /dev/tty7. Multiple current /dev/ttyXX exist only in linux-ruby. > Unless you guys find Branden's > changes reasonable, and adopt and recommend the above patch to others > that want to get this stuff running, in which case the HOWTO could be > changed to reflect the new names. So, what do you think about that? While single current TTY only allowed Branden have not a raw material about what write how-to. Aivils |
|
From: Kjetil K. <kj...@kj...> - 2004-05-17 09:59:33
|
On mandag 17. mai 2004, 09:45, Aivils wrote: > > s/PrefBusID/IsolateDevice/g > > right? > > Yep. Cool! And thanks! > > Then, I wondered about the HOWTO: Probably, we should now add some > > Debian-specific notes, now that people most likely can just use > > Sarge or Sid and get the X servers they need, but must use slightly > > different options than the rest of the world. > > If end-user will start muptiple local xf86, then "IsolateDevice" is > not enough. Each xf86 open /dev/ttyXX , which one current is allowed > under Linus-tree kernel. Secondary xf86 become active when user press > Alt-F8 and primary xf86 goes spleep until user activate /dev/tty7. > > Multiple current /dev/ttyXX exist only in linux-ruby. Yes, of course. Debian's approach to that is that you can create kernel-patch-packages, which the user can trivially apply if s/he chooses to build a kernel themself. For example, that's how Reiser4 is supported in Debian: http://packages.debian.org/unstable/devel/kernel-patch-2.6-reiser4 I know Andreas has been thinking about making such a kernel-patch package for ruby (and suggested I could do it, he'd sponsor it, but I do not feel quite up to the task... :-) ). It would be really cool to have the xf86 patches and the kernel-patch package. Meanwhile, there are a lot more good tools available to compile a kernel, and people do that more routinely, than to compile xf86, so it is a real advancement. So, I just use Linus tree with (backstreet) ruby patches now. > > Unless you guys find Branden's > > changes reasonable, and adopt and recommend the above patch to > > others that want to get this stuff running, in which case the HOWTO > > could be changed to reflect the new names. So, what do you think > > about that? > > While single current TTY only allowed Branden have not a raw material > about what write how-to. Uhm, I must admit I didn't fully parse that... :-) BTW, the linuxconsole-dev archives on Sourceforge seems dead... Nothing has been archived since March, that's why I thought the list was quiet... Cheers, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Svetoslav S. <sv...@gm...> - 2004-05-18 22:52:20
|
> On mandag 17. mai 2004, 09:45, Aivils wrote: > > > s/PrefBusID/IsolateDevice/g > > > right? > > > > Yep. > > Cool! And thanks! i'd say that the "SingleCard" would be a better choice, no need for sed or perl :-) > > > Then, I wondered about the HOWTO: Probably, we should now add some > > > Debian-specific notes, now that people most likely can just use > > > Sarge or Sid and get the X servers they need, but must use slightly > > > different options than the rest of the world. if you are talking about my howto, i'd prefer the notes to be generic, and i'll add them but first i've to find some time and i've to finaly integrate your patch in my Xorg binaries > > > > If end-user will start muptiple local xf86, then "IsolateDevice" is > > not enough. Each xf86 open /dev/ttyXX , which one current is allowed > > under Linus-tree kernel. Secondary xf86 become active when user press > > Alt-F8 and primary xf86 goes spleep until user activate /dev/tty7. > > > > Multiple current /dev/ttyXX exist only in linux-ruby. > > Yes, of course. Debian's approach to that is that you can create > kernel-patch-packages, which the user can trivially apply if s/he > chooses to build a kernel themself. For example, that's how Reiser4 is > supported in Debian: > http://packages.debian.org/unstable/devel/kernel-patch-2.6-reiser4 > > I know Andreas has been thinking about making such a kernel-patch > package for ruby (and suggested I could do it, he'd sponsor it, but I > do not feel quite up to the task... :-) ). It would be really cool to > have the xf86 patches and the kernel-patch package. Meanwhile, there > are a lot more good tools available to compile a kernel, and people do > that more routinely, than to compile xf86, so it is a real advancement. > So, I just use Linus tree with (backstreet) ruby patches now. > > > > > Unless you guys find Branden's > > > changes reasonable, and adopt and recommend the above patch to > > > others that want to get this stuff running, in which case the HOWTO > > > could be changed to reflect the new names. So, what do you think > > > about that? > > > > While single current TTY only allowed Branden have not a raw material > > about what write how-to. > > Uhm, I must admit I didn't fully parse that... :-) mee too, Aivils, what did you had in your mind :-) > BTW, the linuxconsole-dev archives on Sourceforge seems dead... Nothing > has been archived since March, that's why I thought the list was > quiet... it's not just linux-console, it's a lot of(if not all) sf.net project's ml's it would be cool to have it archived on some other place too best, svetljo -- "Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen! Jetzt aktivieren unter http://www.gmx.net/info |
|
From: Helge H. <hel...@ai...> - 2004-05-19 08:24:03
|
Svetoslav Slavtchev wrote: >>On mandag 17. mai 2004, 09:45, Aivils wrote: >> >> >>>>s/PrefBusID/IsolateDevice/g >>>>right? >>>> >>>> >>>Yep. >>> >>> >>Cool! And thanks! >> >> > >i'd say that the "SingleCard" would be a better choice, >no need for sed or perl :-) > > I believe "device" is a better word than "card" in this context, it is possible for hw designers to put several devices on a card (or spread the device over several cards). Today there is usually one device per card, but who knows what the future will bring. > > > >>>>Then, I wondered about the HOWTO: Probably, we should now add some >>>>Debian-specific notes, now that people most likely can just use >>>>Sarge or Sid and get the X servers they need, but must use slightly >>>>different options than the rest of the world. >>>> >>>> > >if you are talking about my howto, >i'd prefer the notes to be generic, >and i'll add them but first i've to find some time >and i've to finaly integrate your patch in my Xorg binaries > > > >>>If end-user will start muptiple local xf86, then "IsolateDevice" is >>>not enough. Each xf86 open /dev/ttyXX , which one current is allowed >>>under Linus-tree kernel. Secondary xf86 become active when user press >>>Alt-F8 and primary xf86 goes spleep until user activate /dev/tty7. >>> >>>Multiple current /dev/ttyXX exist only in linux-ruby. >>> >>> >>Yes, of course. Debian's approach to that is that you can create >>kernel-patch-packages, which the user can trivially apply if s/he >>chooses to build a kernel themself. For example, that's how Reiser4 is >>supported in Debian: >>http://packages.debian.org/unstable/devel/kernel-patch-2.6-reiser4 >> >>I know Andreas has been thinking about making such a kernel-patch >>package for ruby (and suggested I could do it, he'd sponsor it, but I >>do not feel quite up to the task... :-) ). It would be really cool to >>have the xf86 patches and the kernel-patch package. Meanwhile, there >>are a lot more good tools available to compile a kernel, and people do >>that more routinely, than to compile xf86, so it is a real advancement. >>So, I just use Linus tree with (backstreet) ruby patches now. >> >> >> >> >>>>Unless you guys find Branden's >>>>changes reasonable, and adopt and recommend the above patch to >>>>others that want to get this stuff running, in which case the HOWTO >>>>could be changed to reflect the new names. So, what do you think >>>>about that? >>>> >>>> >>>While single current TTY only allowed Branden have not a raw material >>>about what write how-to. >>> >>> >>Uhm, I must admit I didn't fully parse that... :-) >> >> My guess: Branden can't write a proper howto on this, as he works with a standard (non-ruby) kernel that have the single-tty limitation. > >mee too, >Aivils, what did you had in your mind :-) > > We live in a world with many different languages, with english being second or third or something for many of us. I'm happy I don't need to write in German. :-/ Helge Hafting |
|
From: Svetoslav S. <sv...@gm...> - 2004-05-19 08:57:52
|
> Svetoslav Slavtchev wrote: > > >>On mandag 17. mai 2004, 09:45, Aivils wrote: > >> > >> > >>>>s/PrefBusID/IsolateDevice/g > >>>>right? > >>>> > >>>> > >>>Yep. > >>> > >>> > >>Cool! And thanks! > >> > >> > > > >i'd say that the "SingleCard" would be a better choice, > >no need for sed or perl :-) > > > > > I believe "device" is a better word than "card" in this context, > it is possible for hw designers to put several devices on a > card (or spread the device over several cards). Today there > is usually one device per card, but who knows > what the future will bring. you're right "device" seems more reasonable, and you seem to forget about the overpriced Matrox MMS series with 2/4 chips/devices on a single card :-) > > > > > > > >>>>Then, I wondered about the HOWTO: Probably, we should now add some > >>>>Debian-specific notes, now that people most likely can just use > >>>>Sarge or Sid and get the X servers they need, but must use slightly > >>>>different options than the rest of the world. > >>>> > >>>> > > > >if you are talking about my howto, > >i'd prefer the notes to be generic, > >and i'll add them but first i've to find some time > >and i've to finaly integrate your patch in my Xorg binaries > > > > > > > >>>If end-user will start muptiple local xf86, then "IsolateDevice" is > >>>not enough. Each xf86 open /dev/ttyXX , which one current is allowed > >>>under Linus-tree kernel. Secondary xf86 become active when user press > >>>Alt-F8 and primary xf86 goes spleep until user activate /dev/tty7. > >>> > >>>Multiple current /dev/ttyXX exist only in linux-ruby. > >>> > >>> > >>Yes, of course. Debian's approach to that is that you can create > >>kernel-patch-packages, which the user can trivially apply if s/he > >>chooses to build a kernel themself. For example, that's how Reiser4 is > >>supported in Debian: > >>http://packages.debian.org/unstable/devel/kernel-patch-2.6-reiser4 > >> > >>I know Andreas has been thinking about making such a kernel-patch > >>package for ruby (and suggested I could do it, he'd sponsor it, but I > >>do not feel quite up to the task... :-) ). It would be really cool to > >>have the xf86 patches and the kernel-patch package. Meanwhile, there > >>are a lot more good tools available to compile a kernel, and people do > >>that more routinely, than to compile xf86, so it is a real advancement. > >>So, I just use Linus tree with (backstreet) ruby patches now. > >> > >> > >> > >> > >>>>Unless you guys find Branden's > >>>>changes reasonable, and adopt and recommend the above patch to > >>>>others that want to get this stuff running, in which case the HOWTO > >>>>could be changed to reflect the new names. So, what do you think > >>>>about that? > >>>> > >>>> > >>>While single current TTY only allowed Branden have not a raw material > >>>about what write how-to. > >>> > >>> > >>Uhm, I must admit I didn't fully parse that... :-) > >> > >> > My guess: Branden can't write a proper howto on this, as he works > with a standard (non-ruby) kernel that have the single-tty limitation. > > > > >mee too, > >Aivils, what did you had in your mind :-) > > > > > We live in a world with many different languages, with english being > second or third or something for many of us. I'm happy I don't > need to write in German. :-/ /* just kidding */ do you know Bulgarian may be :-) best, svetljo -- "Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen! Jetzt aktivieren unter http://www.gmx.net/info |
|
From: Kjetil K. <kj...@kj...> - 2004-05-19 07:56:14
|
On onsdag 19. mai 2004, 00:52, Svetoslav Slavtchev wrote: > > On mandag 17. mai 2004, 09:45, Aivils wrote: > > > > s/PrefBusID/IsolateDevice/g > > > > right? > > > > > > Yep. > > > > Cool! And thanks! > > i'd say that the "SingleCard" would be a better choice, > no need for sed or perl :-) Hehe, but you're saying that "SingleCard" is the option that replaces the old "PrefBusID" in this patch? Well, the dual-head config didn't work when I installed the new binaries, I guess there could be a reason for it... :-) But then, Xinerama is nice too... :-) > > > > Then, I wondered about the HOWTO: Probably, we should now add > > > > some Debian-specific notes, now that people most likely can > > > > just use Sarge or Sid and get the X servers they need, but must > > > > use slightly different options than the rest of the world. > > if you are talking about my howto, Yup! > i'd prefer the notes to be generic, > and i'll add them but first i've to find some time > and i've to finaly integrate your patch in my Xorg binaries OK, nice! > > BTW, the linuxconsole-dev archives on Sourceforge seems dead... > > Nothing has been archived since March, that's why I thought the > > list was quiet... > > it's not just linux-console, > it's a lot of(if not all) sf.net project's ml's > it would be cool to have it archived on some other place too OK, I know that there are at least one much used archive at http://marc.theaimsgroup.com/?q=about#Add Cheers, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Svetoslav S. <sv...@gm...> - 2004-05-19 08:13:08
|
> On onsdag 19. mai 2004, 00:52, Svetoslav Slavtchev wrote: > > > On mandag 17. mai 2004, 09:45, Aivils wrote: > > > > > s/PrefBusID/IsolateDevice/g > > > > > right? > > > > > > > > Yep. > > > > > > Cool! And thanks! > > > > i'd say that the "SingleCard" would be a better choice, > > no need for sed or perl :-) > > Hehe, but you're saying that "SingleCard" is the option that replaces > the old "PrefBusID" in this patch? it doesn't replace it, its an addition, and IMO it's easier to use /* why specify BusID on 2 places, when it could be just one */ and it's the one that kept it's name in both patches :-) > Well, the dual-head config didn't work when I installed the new > binaries, I guess there could be a reason for it... :-) can you explain a bit more? what do you think is the reason? if it's the new patch, i'll stay with prefbusid (and will have to add debian notes :( ) anyone using IsolateDevice Xserver successfully ? > But then, Xinerama is nice too... :-) > > > > > > Then, I wondered about the HOWTO: Probably, we should now add > > > > > some Debian-specific notes, now that people most likely can > > > > > just use Sarge or Sid and get the X servers they need, but must > > > > > use slightly different options than the rest of the world. > > > > if you are talking about my howto, > > Yup! ok, any other debian notes ? other general notes ? > > i'd prefer the notes to be generic, > > and i'll add them but first i've to find some time > > and i've to finaly integrate your patch in my Xorg binaries > > OK, nice! > > > > BTW, the linuxconsole-dev archives on Sourceforge seems dead... > > > Nothing has been archived since March, that's why I thought the > > > list was quiet... > > > > it's not just linux-console, > > it's a lot of(if not all) sf.net project's ml's > > it would be cool to have it archived on some other place too > > OK, I know that there are at least one much used archive at > http://marc.theaimsgroup.com/?q=about#Add that's my favourite :-) would you add them ? best, svetljo -- NEU : GMX Internet.FreeDSL Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/dsl |
|
From: Kjetil K. <kj...@kj...> - 2004-05-19 19:49:20
|
On onsdag 19. mai 2004, 10:12, Svetoslav Slavtchev wrote: > > Hehe, but you're saying that "SingleCard" is the option that > > replaces the old "PrefBusID" in this patch? > > it doesn't replace it, its an addition, > and IMO it's easier to use > /* why specify BusID on 2 places, > =A0when it could be just one */ > and it's the one that kept it's name in both patches :-) Oh, OK, so I just need to skip "BusID" and use SingleCard instead of=20 both BusID and PrefBusID? > > Well, the dual-head config didn't work when I installed the new > > binaries, I guess there could be a reason for it... :-) > > can you explain a bit more? > what do you think is the reason? Dunno, but it feels awfully familiar... One consol gets garbage, I kill=20 the server, it restarts, takes the whole CPU, but I can log onto the=20 other.=20 Anyway, the problem is, I'm really under a lot of pressure at work right=20 now, head well below water, and my girlfriend, who was using the other=20 console, doesn't really need it now. So, I guess I just have to stay=20 away from big tweaking right now... Xinerama is cool too, you=20 know... :-) > if it's the new patch, i'll stay with prefbusid > (and will have to add debian notes :( ) Well, I would have to downgrade the packages, which can be a pain.=20 > anyone using IsolateDevice Xserver successfully ? Andreas does. > > Yup! > > ok, > any other debian notes ? > other general notes ? Mmmmm, I guess Andreas would be better to address this, I think. But=20 he's possibly very busy too. They've got a big release soon, I think...=20 > > OK, I know that there are at least one much used archive at > > http://marc.theaimsgroup.com/?q=3Dabout#Add > > that's my favourite :-) > would you add them ? Well, they want the list admins permission anyway, so perhaps the list=20 admin better make the contact...?=20 Best, Kjetil =2D-=20 Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Kjetil K. <kj...@kj...> - 2004-05-21 20:22:43
|
On onsdag 19. mai 2004, 10:12, Svetoslav Slavtchev wrote: > > Well, the dual-head config didn't work when I installed the new > > binaries, I guess there could be a reason for it... :-) > > can you explain a bit more? > what do you think is the reason? Uhm, found it.... I needed to prefix the BusIDs with "PCI:"... The really bad thing is that I understood that from reading the patch a couple of weeks ago, but seeing it blow up in my face erased it from my mind, and so I went around screaming in terror instead of trying to use my brain... :-) That's life I guess... But since I didn't have that before, and it worked, it is perhaps a Debian-specific note for the HOWTO? Also, I'm running on two different cards, which means, I shouldn't use SingleCard, right? Cheers, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Arne G. G. <ar...@li...> - 2004-05-19 09:51:23
|
* Kjetil Kjernsmo > OK, I know that there are at least one much used archive at > http://marc.theaimsgroup.com/?q=about#Add There's one at http://news.gmane.org/gmane.linux.kernel.console which is already operative. It's only got a month's worth of articles yet, though. Arne. |
|
From: Daniel L. <dan...@ya...> - 2004-05-22 22:45:44
|
Hi, I thought someone might like to know that with Svetljo's great patience and assistance (thank you yet again) I have managed to get my first Ruby working. The configuration is: - PCI ATI Radeon 7000 32MB (Sapphire) - PCI Matrox Millenium I 4MB I start X0 on the Radeon, and then open a konsole window to start X1 on the Matrox. I can reliably stop and restart X1 without problems. I haven't tried stopping and starting X0 from X1 yet. These 2 worked with the SingleCard option in my XF86Config-4 file. I couldn't get them working with PrefBusID option, and didn't try the hackvideo thing. I've noticed a few problems that I haven't solved yet... 1) Keyboard autorepeat doesn't work once I start X1. 2) I have a three PCI Radeon 7000 cards. I can't seem to find a combination where any 2 or 3 of these cards will be happy together. Generally whenever I try and start a second of them, the system locks up, screens go blank (but not into power saving mode), and caps/scroll/num lock fail to have any effect. One day I'll have 3 cards working all with DRI... in my dreams... Regards, Dan --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.688 / Virus Database: 449 - Release Date: 18/05/2004 |
|
From: Daniel L. <dan...@ya...> - 2004-05-18 19:23:33
|
Hello list,
I've been experimenting with the Backstreet Ruby patch and I feel that I
almost have it working, but I'm having difficulty getting X running on my
second or third graphics card. I'm hoping someone on the list can kindly
give me some help. (please?!)
Setup:
- Duron 1.6
- VIA KT4AV Motherboard
- 512MB
- 3 * PCI Sapphire ATI Radeon 7000 32MB (0:5:0, 0:6:0, 0:7:0)
- Mandrake 8.2
- 1 standard PS2 keyboard
- 1 USB keyboard
- 2 USB mice
The kernel works just fine (I think). I downloaded a clean 2.4.25, patched
it, mkinitrd'd, grub'd, no problems. USB is compiled as modules, because the
Mandrake init scripts seem to like it like that.
X server is installed from XFree86-concurrent-server-4.2.0-10mdk.i586.rpm
and I'm not using /proc/bus/pci/hackvideo
I can start 'X0' as :0 on the first PCI card with either keyboard (vt7 or
vt17), and either mouse (/dev/input/mouse0 or mouse1), so it seems the
inputs are all in /dev/input (devfs) correctly.
So here's the problem... After stopping X0 (no X server running at all now),
I cannot get X1 to start on the second PCI card, using:
startx -- /usr/X11R6.bin/X1 :1 -xf86config /etc/X11/XF86Config-4-X1 -layout
X1 vt17 > tmp.log 2>&1
The console display I'm on goes blank (but monitor isn't entering power
saving mode), no LEDs function on the keyboard, and as far as I can tell
Linux hangs. There's no /var/log/XFree.1.log after rebooting to single user
mode / rc3, and the last messages I can see in my tmp.log read :
(WW) RADEON: No matching Device section for instance (BusID PCI 0:5:0)
found
(WW) RADEON: No matching Device section for instance (BusID PCI 0:7:0)
found
The file XF86Config-4-X1 contains:
Section "Device"
Identifier "ATI Radeon 2"
VendorName ""
BoardName ""
Driver "radeon"
Option "DPMS" "off"
BusID "PCI:0:6:0"
EndSection
Section "Screen"
Identifier "screen2"
Device "ATI Radeon 2"
Montior "monitor2"
...
EndSection
Section "ServerLayout"
Identifier "X1"
Screen "screen2"
InputDevice "USB Mouse 2" "CorePointer"
InputDevice "Keyboard2" "CoreKeyboard"
Option "SingleCard" "true"
#Option "PrefBusID" "0:6:0" # does this work?
EndSection
I tried using -prefbusid, but the XFree-concurrent I've got doesn't seem to
recognise it?
So, please, can someone suggest where I might be going wrong?!
Many thanks for any help offered,
Dan
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.686 / Virus Database: 447 - Release Date: 14/05/2004
|
|
From: Svetoslav S. <sv...@gm...> - 2004-05-18 20:23:08
|
> Hello list, Hi Daniel, > > I've been experimenting with the Backstreet Ruby patch and I feel that I > almost have it working, but I'm having difficulty getting X running on my > second or third graphics card. I'm hoping someone on the list can kindly > give me some help. (please?!) > > Setup: > - Duron 1.6 > - VIA KT4AV Motherboard > - 512MB > - 3 * PCI Sapphire ATI Radeon 7000 32MB (0:5:0, 0:6:0, 0:7:0) > - Mandrake 8.2 don't you know that MDK-8.2 suport is discontinued :-) kidding, but update might help a bit > - 1 standard PS2 keyboard > - 1 USB keyboard > - 2 USB mice > > The kernel works just fine (I think). I downloaded a clean 2.4.25, patched > it, mkinitrd'd, grub'd, no problems. USB is compiled as modules, because > the > Mandrake init scripts seem to like it like that. > > X server is installed from XFree86-concurrent-server-4.2.0-10mdk.i586.rpm > and I'm not using /proc/bus/pci/hackvideo using the concurrent X server is equal to using the hack, not sure if this is the problem thought > I can start 'X0' as :0 on the first PCI card with either keyboard (vt7 or > vt17), and either mouse (/dev/input/mouse0 or mouse1), so it seems the > inputs are all in /dev/input (devfs) correctly. > > > So here's the problem... After stopping X0 (no X server running at all > now), > I cannot get X1 to start on the second PCI card, using: > > startx -- /usr/X11R6.bin/X1 :1 -xf86config /etc/X11/XF86Config-4-X1 > -layout > X1 vt17 > tmp.log 2>&1 > > The console display I'm on goes blank (but monitor isn't entering power > saving mode), no LEDs function on the keyboard, and as far as I can tell > Linux hangs. There's no /var/log/XFree.1.log after rebooting to single > user > mode / rc3, and the last messages I can see in my tmp.log read : > > (WW) RADEON: No matching Device section for instance (BusID PCI 0:5:0) > found > (WW) RADEON: No matching Device section for instance (BusID PCI 0:7:0) > found > you should first get all cards working in single mode, or/and Xinerama Xinerama would be probably easier with XFdrake but ... your XFree version is tooooooo old :( (it shouldn't metter if you are configuring under bruby or normal kernel) when you get them working in Xinerama drop a line :-) > The file XF86Config-4-X1 contains: > > Section "Device" > Identifier "ATI Radeon 2" > VendorName "" > BoardName "" > Driver "radeon" > Option "DPMS" "off" > BusID "PCI:0:6:0" > EndSection > > Section "Screen" > Identifier "screen2" > Device "ATI Radeon 2" > Montior "monitor2" > ... > EndSection > > Section "ServerLayout" > Identifier "X1" > Screen "screen2" > InputDevice "USB Mouse 2" "CorePointer" > InputDevice "Keyboard2" "CoreKeyboard" > Option "SingleCard" "true" > #Option "PrefBusID" "0:6:0" # does this work? > EndSection > > > I tried using -prefbusid, but the XFree-concurrent I've got doesn't seem > to > recognise it? nope, it's unsupported, both commandline parameter & config file options PrefBusID & SingleCard are unsuported by it that's why for a bit newer mdk versions there are both -prefbusid & concurrent Xservers, and for latest only prefbusid(as the hack is equal to concurrent) well there are no "official" packages for MDK-10, but in case of interest i have some Xorg packages (if i didn't messed up smth, there should be -prefbusid Xserver for any MDK that ships with XFree-4.3) > So, please, can someone suggest where I might be going wrong?! > sorry to say it, but i can not help a lot without working Xinerama or all cards in single mode :( i really think a XFree update could help, which probably means distro update too best, svetljo -- NEU : GMX Internet.FreeDSL Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/dsl |
×
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