Hugo Vanwoerkom [EMAIL PROTECTED] wrote:
| You can either rebuild the kernel and turn that off (Note: but in
| that case I had hard hangs in qemu!) *or* use the descriptions
| in that page to rebuild the kbuild .deb and install nvidia so it does
| not mind paravirt.
Just to close out the
Hello.
I did a recent install of Debian etch on a system with an nVidia
graphics controller. I used module-assistant to install the nvidia
kernel module, and under kernel 2.6.18 from the install, that all
worked fine.
A few days later, I upgraded to kernel package 2.6.18.2-686 (from
lenny) to
On Fri July 6 2007 11:19:55 pm Jim McCloskey wrote:
Hello.
I did a recent install of Debian etch on a system with an nVidia
graphics controller. I used module-assistant to install the nvidia
kernel module, and under kernel 2.6.18 from the install, that all
worked fine.
A few days later, I
Jim McCloskey wrote:
Hello.
I did a recent install of Debian etch on a system with an nVidia
graphics controller. I used module-assistant to install the nvidia
kernel module, and under kernel 2.6.18 from the install, that all
worked fine.
A few days later, I upgraded to kernel package
On Sat July 7 2007 05:00:06 am Hugo Vanwoerkom wrote:
Jim McCloskey wrote:
Hello.
I did a recent install of Debian etch on a system with an nVidia
graphics controller. I used module-assistant to install the nvidia
kernel module, and under kernel 2.6.18 from the install, that all
Hugo Vanwoerkom [EMAIL PROTECTED] wrote:
| Extensively discussed here:
| http://www.nvnews.net/vbulletin/showthread.php?t=90214
|
| The problem is that post 2.6.18 Debian kernels have PARAVIRT_CONFIG
| and nvidia does not like that.
|
| You can either rebuild the kernel and turn that off
Drew Parsons [EMAIL PROTECTED] writes:
Running on the theory that it might help speed up my Pentium II system
(debatable, but that's beside the point), I've tried
recompiling a selection of packages with pentium optimisation, downloading
the debian source and running `./debian/rules binary`.
On Wed, Feb 09, 2000 at 11:04:27AM -0800, Chris Waters wrote:
Drew Parsons [EMAIL PROTECTED] writes:
Running on the theory that it might help speed up my Pentium II system
(debatable, but that's beside the point), I've tried
recompiling a selection of packages with pentium optimisation,
After doing a apt-get upgrade apt downloaded and installed the debian
Speaking of it, how would one put a package on hold, apt-get manual doesn't
state how to do it. I always have this problem of getting the same version
package, as I just compiled and installed via 'apt-get upgrade'
Please format your emails to 76 characters or less.
On Wed, Feb 09, 2000 at 03:33:09PM -0500, [EMAIL PROTECTED] wrote:
After doing a apt-get upgrade apt downloaded and installed the debian
Speaking of it, how would one put a package on hold
echo 'package_name hold' | dpkg --set-selections
On Wed, Feb 09, 2000 at 11:04:27AM -0800, Chris Waters wrote:
Actually, it's not really about newer, it's about having a
version number that sorts later, so, one possibility is to use a
special version number that will always sort later. This is the trick
suggested for custom kernels. Thus,
Hiya,
Thanks for your note. I guess I was a bit misleading about patching. The
patch I used was a buslogic flashpoint patch for my scsi controller. Not
a kernel patch. I got the new 2.0.29 complete sources before I tried to
compile. Sorry 'bout that...
J. Goldman
--
TO UNSUBSCRIBE FROM THIS
Hi,
This was a bug in kernel-package which has now been corrected.
manoj
Daniel == Daniel J Mashao [EMAIL PROTECTED] writes:
Daniel It looks like you new kernel was made after all. I would copy
Daniel it to the right place /boot/vmlinuz and use it. I think your
Daniel problem
On Sun, 16 Feb 1997, Jesse Goldman wrote:
I've run into a snag making a kernel package for version 2.0.29. I got
new sources, patched them, did a make-kpkg clean and then a make-kpkg
Why patch the new sources? I thought you only needed to patch if you had
2.0.28 sources and wanted to upgrade
Hi,
Thank you for the report, this is a real bug in kernel-package
version 3.16: vi has, for some obscure reason, started to expand info
to information and so on spontaneously. I generally catch it at it,
but this time it snuck up and changed Feb to February in the
changelog, causing
On 17 Feb 1997 [EMAIL PROTECTED] wrote:
Hi,
Thank you for the report, this is a real bug in kernel-package
version 3.16: vi has, for some obscure reason, started to expand info
to information and so on spontaneously. I generally catch it at it,
Hi,
Could you please mail me the debian/changelog file? Also,
could you run dpkg-gencontrol manually and see if it sheds any more
light? Also, Could you give the version of kernel-package installed?
manoj
--
IT'S THE TWO GODDAMNED CULTURES AGAIN !*! Bit-brained nerdery on
17 matches
Mail list logo
