Hi
Just recently came across qemu and I thought I would check it out.
I installed it on a i686 machine (debian) and it seems like there are kernel
modules pre built for it (kqemu). But on amd64 there doesn't seem to be,
instead there are kqemu-common kqemu-source.
Is there a particular reason
Użytkownik Alex Samad [EMAIL PROTECTED] napisał:
Hi
Just recently came across qemu and I thought I would check it out.
I installed it on a i686 machine (debian) and it seems like there are kernel
modules pre built for it (kqemu). But on amd64 there doesn't seem to be,
instead there are
When using module assistant to install a package (e.g. nvidia driver, some
wireless driver, whatever), it only compiles a module for that
currently-running kernel, correct?
So, then, after a dist-upgrade, in which I have installed a new kernel, when
the machine is rebooted into this
new
On Wed, 07 Feb 2007 16:20:31 +0100, Zachary Rizer wrote:
So, then, after a dist-upgrade, in which I have installed a new kernel,
when the machine is rebooted into this new kernel, I must re-run m-a to
install the modules for the new kernel?
Yes.
Is there any way around this?
Well you could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* On 07-02-2007 16:14 [EMAIL PROTECTED] wrote:
: When using module assistant to install a package (e.g. nvidia driver, some
wireless driver, whatever), it only compiles a module for that
currently-running kernel, correct?
# man m-a
: So,
On Wed, Feb 07, 2007 at 07:14:35AM -0800, Zachary Rizer wrote:
When using module assistant to install a package (e.g. nvidia driver, some
wireless driver, whatever), it only compiles a module for that
currently-running kernel, correct?
It only does so by default. You can give it a list of
Hi Zachary,
as far as I know, there is an easy way out, The -l flag of m-a.
The way I do it is:
1) dist-upgrade (or apt-get install new linux-image-x.y.z-xx-yyy)
2) check if linux-headers-x.y.z-xx-yyy are also installed, otherwise
3) apt-get install linux-headers-x.y.z-xx-yyy
4) m-a -l
On Wed, Feb 07, 2007 at 07:14:35AM -0800, Zachary Rizer wrote:
When using module assistant to install a package (e.g. nvidia driver,
some wireless driver, whatever), it only compiles a module for that
currently-running kernel, correct?
Yes.
So, then, after a dist-upgrade, in which I have
- Original Message
From: Lennart Sorensen [EMAIL PROTECTED]
To: Zachary Rizer [EMAIL PROTECTED]
Cc: debian-amd64@lists.debian.org
Sent: Wednesday, February 7, 2007 10:48:58 AM
Subject: Re: m-a question
On Wed, Feb 07, 2007 at 07:14:35AM -0800, Zachary Rizer wrote:
When using module
On Wednesday 07 February 2007 16:17, Zachary Rizer wrote:
- Original Message
From: Lennart Sorensen [EMAIL PROTECTED]
To: Zachary Rizer [EMAIL PROTECTED]
Cc: debian-amd64@lists.debian.org
Sent: Wednesday, February 7, 2007 10:48:58 AM
Subject: Re: m-a question
On Wed, Feb 07, 2007
On Tuesday 06 February 2007 23:12, Wolfgang Mader wrote:
I found out, that on heavy system load, my power supply only delivers
+11,4V. This seemes to be the lower limit to the specs. Could this course
the problems descripet below?
Hi all,
in earlier times an apt-get upgrade or apt-get dist-upgrade would
automatically install newer kernel versions. This behaviour is no more, but
some wrote, that a meta(?) package has to be installed, to get this behaviour
back.
Is this correct ? How do I rectivate this ? The problem is
Hi,
I just have installed the package
linux-image-2.6-amd64
This package depends on the latest binary image for Linux kernel
This packages just installes an new image, if one is availabel. You have to
uninstall the old one by hand.
Cheers
Am Mittwoch 07 Februar 2007 20:14 schrieb Hans-J.
On Wed, Feb 07, 2007 at 07:09:54PM +, Anton Piatek wrote:
It is a shame that it is not build into part of the mkinitrd scripts to build
your standard modules when installing a new kernel...
Sometimes you update your modules without updating the initrd. And vice
versa. Not really the
14 matches
Mail list logo
