Re: [2.4.2-ac5] X (4.0.1) crashes
Pavel Machek wrote : > Hi! > > > > I use XFree86 4.0.1 with nvidia-drivers 0.96. > > > > Take it up with nvidia. Obfuscated effectively binary only code isnt anyone > > elses problem It is not only "effectively binary" but "actually binary". There are no sources, only a few line of C "glue" code. Maybe you are confusing it with the XFree86 nv drivers from xfree86.org ? These are the nVidia drivers from nvidia.com > Is it legal, BTW? Obfuscated drivers should _not_ be linked into > kernel, because they are not "form preferable for editing". > > > The source code for a work means the preferred form of the work for > making modifications to it. For an executable work, complete source > > > So nvidia drivers *are* binary only, as far as GPL is concerned. They > should never be linked into kernel. > > [Or, someone should get kernel with nvidia drivers compiled in from > nvidia, and then ask them for sources :-)] >Pavel -- David Balazic -- "Be excellent to each other." - Bill & Ted - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [2.4.2-ac5] X (4.0.1) crashes
Hi! > > I use XFree86 4.0.1 with nvidia-drivers 0.96. > > Take it up with nvidia. Obfuscated effectively binary only code isnt anyone > elses problem Is it legal, BTW? Obfuscated drivers should _not_ be linked into kernel, because they are not "form preferable for editing". The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source So nvidia drivers *are* binary only, as far as GPL is concerned. They should never be linked into kernel. [Or, someone should get kernel with nvidia drivers compiled in from nvidia, and then ask them for sources :-)] Pavel -- I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents at [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [2.4.2-ac5] X (4.0.1) crashes
I'm having no problems with 2.4.2-ac6, using XFree86 4.0.2 and the included nv (nvidia) driver. Works great with my geForce2 GTS, without any binary only drivers. 4.0.2 seemed to have improved support for nvidia chips. If it's any help, I'm also using the rivafb for console (although not for X). Erik On Tue, Feb 27, 2001 at 03:08:30PM +0100, Manfred H. Winter wrote: > Hi! > > Yesterday I've upgraded my 2.4.2 kernel to ac5, because loop-device > seems not to work in plain 2.4.2. But now my X-server crashes. > > When I start with startx, X comes up, gnome starts, sawfish starts. Then > the system freezes. Even SysRQ-keys don't work. > > I use XFree86 4.0.1 with nvidia-drivers 0.96. > > I can't find anything about the crash in the logs, even the output from > X doesn't get written to disk. > > Is this a known problem? > > I'm going back to vanilla 2.4.2 for now. Is there another way to get > loop to work? > > Bye, > > Manfred > -- > /"\| PGP-Key available at Public Key Servers > \ / ASCII ribbon campaign | or at "http://www.mahowi.de/" > X against HTML mail | RSA: 0xC05BC0F5 * DSS: 0x4613B5CA > / \ and postings | GPG: 0x88BC3576 * ICQ: 61597169 > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [2.4.2-ac5] X (4.0.1) crashes
> I use XFree86 4.0.1 with nvidia-drivers 0.96. Take it up with nvidia. Obfuscated effectively binary only code isnt anyone elses problem - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [2.4.2-ac5] X (4.0.1) crashes
"Manfred H. Winter" wrote: > I'm going back to vanilla 2.4.2 for now. Is there another way to get > loop to work? Working fine here: 2.4.2 + Axboe's loop patch + Morton's low latency patch jjs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.4.2-ac5] X (4.0.1) crashes
Hi! Yesterday I've upgraded my 2.4.2 kernel to ac5, because loop-device seems not to work in plain 2.4.2. But now my X-server crashes. When I start with startx, X comes up, gnome starts, sawfish starts. Then the system freezes. Even SysRQ-keys don't work. I use XFree86 4.0.1 with nvidia-drivers 0.96. I can't find anything about the crash in the logs, even the output from X doesn't get written to disk. Is this a known problem? I'm going back to vanilla 2.4.2 for now. Is there another way to get loop to work? Bye, Manfred -- /"\| PGP-Key available at Public Key Servers \ / ASCII ribbon campaign | or at "http://www.mahowi.de/" X against HTML mail | RSA: 0xC05BC0F5 * DSS: 0x4613B5CA / \ and postings | GPG: 0x88BC3576 * ICQ: 61597169 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
