Re: FC3 and ruby, not working [updated]

[Ricardo A. G. <rgo...@co...>]

first, a correction:
startx -- vt7 : Don't work (problem with keyboard)
why? my bug. I'm using tty1-8 and first free tty is '9' startx -- vt9 
run Ok. (gdm updated to use vt9 and not vt7 run ok too)

This problem is solved, now I have a bug (that come from FC2+nvidia 
6111, my first ruby experience): sometimes X0 (first server) hang 
(display/keyboard/mouse) and process X0 use 100% of cpu (second server 
run ok). I is 100% reproducible with xmatrix 
(/usr/X11R6/lib/xscreensaver/xmatrix), and never happens in X1. I feel 
it is not 'ruby related' bug. I will test it in  FC3's kernel (without 
patches) and send comments.

Ricardo.-

Ricardo Ariel Gorosito wrote:

> My new tests with FC3's kernel + ruby & NVIDIA driver 6111 (without 
> isolatebusid, with 'hackvideo'=1):
> startx -- vt7 : Ok (mouse & keyboard)
> startx -- vt17 : Ok (mouse & keyboard)
> gdm : First display hang (kerboard only, mouse ok) and second display 
> ok. If I try to kill X0 (first server), PC hang
> I have BusID options (not isolatedbusid) in xorg.conf
>
> Ricardo.-
>
> Aivils wrote:
>
>> On Thursday 18 November 2004 08:47, Ricardo Ariel Gorosito wrote:
>>  
>>
>>> I patched the Fedora 3 official kernel with 
>>> ruby-2.6.9-20041021.diff.bz2 and patched Xorg with 
>>> Xorg-6.7.0-isolate_device.patch but I can't get X work.
>>> I'm using 2 nvidia cards (AGP is Geforce4 MX 4000 and PCI Geforce2 
>>> MX/MX 400). This config run ok with Fedora 2 and nvidia's 6111.
>>> I've installed NVidia 6629 and 6111 with same results:
>>> * using isolatebusid option:
>>> first X start, second not. when I press any key en first console, 
>>> screen black and back
>>> * without isolatebusid option, with or without 'hackvideo=1':
>>> first X start, when second try to start, machine hang
>>>   
>>
>>
>> I never test Xorg. I am under Mandrake 10.0
>> If X will use right keyboard, after command
>> startx -- vt7
>> startx -- vt17
>> then all rest manipulations are magic.
>> Most helpful in my case is starting X -probeonly , where X use
>> conifguration without any "isolatebusid", be sure please, if You use
>> option in the Server Layout , then  "isolatebusid" is allways turned on.
>> X -probeonly can use all videoadaters and properly
>> initializes nvidia kernel module. You can check out probeonly log
>> file.
>>
>> Aivils 
>