On Mon, Oct 13 2008, Lachlan wrote:
> i am also running amd64
>
> i got 2.6.27 running this morning but that's about it.
> booted into gnome and didn't really know what to do after that. i used:
>
> kernel source# make menuconfig
> (made sure iwl stuff was added etc. saved as .config)
> kernel so
t;> The kernel compiles correctly using the usual toolchain provided with
>> the sources but fails on the packaging part using make-kpkg.
>>
>> The compile process gets all the way to the end and fails with
>> debian/stamp/Install: Is a directory
>> The exact comma
On Sun, Oct 12 2008, Adrian Levi wrote:
> I have since tried compiling the kernel in a clean lenny debootstrap
> chroot sucessfully.
> Strangely is was called,
> linux-xenu-2.6.27_2.6.27-10.00.Custom_amd64.deb
>
> But it boots and works, must be a version incompatibility somewhere, I
> still have
the sources but fails on the packaging part using make-kpkg.
>
> The compile process gets all the way to the end and fails with
> debian/stamp/Install: Is a directory
> The exact command line I'm using at the top level linux-2.6.27 direcory is:
> fakeroot make-kpkg --initrd -
2008/10/12 thveillon.debian <[EMAIL PROTECTED]>:
> Adrian Levi a écrit :
>
>> I have since tried compiling the kernel in a clean lenny debootstrap
>> chroot sucessfully.
>> Strangely is was called,
>> linux-xenu-2.6.27_2.6.27-10.00.Custom_amd64.deb
>>
> Maybe you enabled xen support in the config :
Adrian Levi a écrit :
I have since tried compiling the kernel in a clean lenny debootstrap
chroot sucessfully.
Strangely is was called,
linux-xenu-2.6.27_2.6.27-10.00.Custom_amd64.deb
Maybe you enabled xen support in the config : CONFIG_XEN
But it boots and works, must be a version incompati
2008/10/12 thveillon.debian <[EMAIL PROTECTED]>:
> I've used Lenny default for the kernel I'm currently running
> (11.001-something I think), and then tried 11.007 from Sid with good
> results.
> The .config is from my previously home-rolled 2.6.26-6, gcc is Lenny 4.3.2,
> config is nothing fancy,
Adrian Levi a écrit :
But you ended up with a .deb package at the end, Mine is failing
before creating the package.
My installed kernel-package version is 11.007 what was yours?
What did you use for a .config file? Mine is from linux-image-2.6.26
in lenny, answered the few new questions and wen
2008/10/12 thveillon.debian <[EMAIL PROTECTED]>:
> Hi,
>
> I'm using a 2.6.27 compiled from kernel.org sources since the day it was
> released, running fine. I compiled it with Lenny default kernel-package, the
> Debian way, and had no trouble.
> I then compiled it with Sid newly revised kernel-pac
Adrian Levi a écrit :
I'm having troubles compiling a vanilla 2.6.27 kernel using
kernel-package. Looks like there is a new iwl4965 driver and I'd like
to try it out.
The kernel compiles correctly using the usual toolchain provided with
the sources but fails on the packaging part
gt; the sources but fails on the packaging part using make-kpkg.
Have you tried kernel-package 11.007 from sid?
> The compile process gets all the way to the end and fails with
> debian/stamp/Install: Is a directory
> The exact command line I'm using at the top level linux-2.6.27
on the packaging part using make-kpkg.
>
> The compile process gets all the way to the end and fails with
> debian/stamp/Install: Is a directory
> The exact command line I'm using at the top level linux-2.6.27 direcory is:
> fakeroot make-kpkg --initrd --arch amd64 kernel_image
&
I'm having troubles compiling a vanilla 2.6.27 kernel using
kernel-package. Looks like there is a new iwl4965 driver and I'd like
to try it out.
The kernel compiles correctly using the usual toolchain provided with
the sources but fails on the packaging part using make-kpkg.
The compi
On Thu, Jan 11, 2007 at 10:51:13AM -0700, jdaues wrote:
> Just curious:
> >
> >If you're using a stock debian kernel, why not use the pre-packaged
> >nvidia drivers?
> >
> >Get X working with the nv driver and save that xorg.conf as
> >xorg.conf.nv.
> >
> >Then install the nvidia drivers and run
I'm now sure I know enough to answer your question.
I'm *NOT* sure I know enough
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I'm now sure I know enough to answer your question. I first attempted to
use NVIDIA-Linux-x86-1.0-9746-pkg1.run from here:
http://www.nvidia.com/object/linux_display_ia32_1.0-9746.html
but my graphics card is too old.
Anyways, it is now working at 1024x768. I thinks its capable of more,
though.
On Thu, Jan 11, 2007 at 10:11:09AM -0700, jdaues wrote:
> I am following instructions for Debian NVIDIA proprietary display driver
> installation through APT here:
> http://wiki.serios.net/wiki/Debian_NVIDIA_proprietary_display_driver_installation_through_APT
>
> I get to the point of this comman
Thanks, when searching for help on this message, all the hits were in
french. Ah zut!
I now have the .deb file
Wackojacko wrote:
jdaues wrote:
I am following instructions for Debian NVIDIA proprietary display
driver installation through APT here:
http://wiki.serios.net/wiki/Debian_NVIDIA_pr
jdaues wrote:
I am following instructions for Debian NVIDIA proprietary display driver
installation through APT here:
http://wiki.serios.net/wiki/Debian_NVIDIA_proprietary_display_driver_installation_through_APT
I get to the point of this command:
make-kpkg modules_image
and i get this messag
I am following instructions for Debian NVIDIA proprietary display driver
installation through APT here:
http://wiki.serios.net/wiki/Debian_NVIDIA_proprietary_display_driver_installation_through_APT
I get to the point of this command:
make-kpkg modules_image
and i get this message:
The modules_*
On 3/2/06, Doofus <[EMAIL PROTECTED]
> wrote:
Harish G. Naik wrote:> $make-kpkg kernel_image> $dpkg --install kernel-2.6.15*.deb>> Now when I try reebooting into the new kernel, I get:
> If you don't include the switch "--initrd" on your "make-kpkg" command
> line then you *must* compile the drive
Harish G. Naik wrote:
Hi,
I am currently running Debian Sarge testing.
GCC version is 3.3.4
I needed to compile and install 2.6.15
used
$make-kpkg kernel_image
$dpkg --install kernel-2.6.15*.deb
Now when I try reebooting into the new kernel, I get:
VFS: Cannot open root device "hdas" or unkn
Hi,I am currently running Debian Sarge testing.GCC version is 3.3.4I needed to compile and install 2.6.15used $make-kpkg kernel_image$dpkg --install kernel-2.6.15*.deb
Now when I try reebooting into the new kernel, I get:
VFS: Cannot open root device "hdas" or unknown-block(0,0)Please append a corr
On Thu, Mar 02, 2006 at 04:54:42PM +0530, Harish G. Naik wrote:
> Hi,
>
> I am currently running Debian Sarge testing.
> GCC version is 3.3.4
>
> I needed to compile and install 2.6.15
> used
> $make-kpkg kernel_image
> $dpkg --install kernel-2.6.15*.deb
>
> Now when I try reebooting into the ne
Hi,I am currently running Debian Sarge testing.GCC version is 3.3.4I needed to compile and install 2.6.15used $make-kpkg kernel_image$dpkg --install kernel-2.6.15*.debNow when I try reebooting into the new kernel, I get:
VFS: Cannot open root device "hdas" or unknown-block(0,0)Please append a corre
On Tue, Aug 24, 2004 at 05:21:30PM +0100, robin wrote:
> Using make menuconfig, initrd set to built-in under device drivers /
> block devices
You don't need an initrd for kernels you compile yourself. Remove it, and
ensure you compile in (statically) support for block IDE, and your
filesystem(s)
Using make menuconfig, initrd set to built-in under device drivers /
block devices
After configuring run make-kpkg buildpackage following debs produced:
kernel-doc-2.6.7_10.00.Custom_all.deb
kernel-image-2.6.7_10.00.Custom_i386.deb
kernel-headers-2.6.7_10.00.Custom_i386.deb
kernel-source-2
On Fri, 6 Jun 2003 17:07:02 -0400
Kevin McKinley <[EMAIL PROTECTED]> wrote:
>On Fri, 6 Jun 2003 08:24:09 -0400
>Chris Metzler <[EMAIL PROTECTED]> wrote:
>
>> No. The kernel is built *and* then a .deb file containing the kernel
>> is built, which you can then install using "deb -i".
>
> Methinks
On Fri, 6 Jun 2003 08:24:09 -0400
Chris Metzler <[EMAIL PROTECTED]> wrote:
> No. The kernel is built *and* then a .deb file containing the kernel
> is built, which you can then install using "deb -i".
Methinks that's "dpkg -i kernel-image..."
> Please read http://newbiedoc.sourceforge.net/syst
On Fri, 6 Jun 2003, Colin Watson wrote:
>On Fri, Jun 06, 2003 at 01:56:42PM +0200, David List wrote:
>> Just to make sure that I have understood the man page for make-kpkg
>> right:
>> If I issue 'make-kpkg kernel_image', the kernel is built *and* installed
>> *and* any symlink are set correctly.
I am afraid my friend, that you haven't understood well.
The command make-kpkg only makes the *.deb files.
Then you have to do:
dpkg -i *.deb in the dir these deb files are created...
On Fri, Jun 06, 2003 at 01:56:42PM +0200, David List wrote:
> Just to make sure that I have understood the man pag
On Fri, Jun 06, 2003 at 01:56:42PM +0200, David List wrote:
> Just to make sure that I have understood the man page for make-kpkg
> right:
> If I issue 'make-kpkg kernel_image', the kernel is built *and* installed
> *and* any symlink are set correctly.
Not quite; the kernel is built but not instal
On Fri, 6 Jun 2003 13:56:42 +0200 (CEST)
David List <[EMAIL PROTECTED]> wrote:
>
> Just to make sure that I have understood the man page for make-kpkg
> right:
> If I issue 'make-kpkg kernel_image', the kernel is built *and* installed
> *and* any symlink are set correctly.
>
> Is this correct?
No
Just to make sure that I have understood the man page for make-kpkg
right:
If I issue 'make-kpkg kernel_image', the kernel is built *and* installed
*and* any symlink are set correctly.
Is this correct?
Best regards,
David List
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
On Mon, Jul 02, 2001 at 12:51:17PM -0500, John Foster wrote:
> If I put the CONCURRENCY_LEVEL := 2 in my root environment variable will
> it be useful in allowing all of my compiled applications to run with
> maximum efficiency on my dual processor system?
No, it will only affect the (one-time) co
Steve Kowalik wrote:
>
> On Sun, Jul 01, 2001 at 02:42:20PM -0500, S.Salman Ahmed uttered:
> >
> > Is there any way to pass the "-j " option to make when building
> > kernels using make-kpkg ?
> >
> Read the README for kernel-package.
> Make a .kern
S.Salman Ahmed <[EMAIL PROTECTED]> writes:
> Is there any way to pass the "-j " option to make when building
> kernels using make-kpkg ?
Yes. See kernel-pkg.conf(5) for details.
--
Leonard Stiles <[EMAIL PROTECTED]>
On Sun, Jul 01, 2001 at 02:42:20PM -0500, S . Salman Ahmed wrote:
>
> Is there any way to pass the "-j " option to make when building
> kernels using make-kpkg ?
RTFM. 'man kernel-pkg.conf' and search for CONCURRENCY_LEVEL or just
'-j'.
> I am hopi
On Sun, Jul 01, 2001 at 02:42:20PM -0500, S.Salman Ahmed uttered:
>
> Is there any way to pass the "-j " option to make when building
> kernels using make-kpkg ?
>
Read the README for kernel-package.
Make a .kernel-pkg.conf in ~ as the user you compile it as.
[EMAIL
package, such as pcmcia-cs, using make-kpkg?
>
> I go into /usr/src and untar pcmcia-cs.tar.gz . Then
> I go into /usr/src/linux and run make-kpkg modules_image.
> make-kpkg answers all the questions that ordinarily I
> would answer if I ran "Configure". Unfortunately it
>
What is the best way to select "configure" options when
compiling a package, such as pcmcia-cs, using make-kpkg?
I go into /usr/src and untar pcmcia-cs.tar.gz . Then
I go into /usr/src/linux and run make-kpkg modules_image.
make-kpkg answers all the questions that ordinarily I
would a
I've just tried compiling pcmcia-source 3.1.22 using make-kpkg but it
fails, telling me:
make[4]: Entering directory `/usr/src/modules/pcmcia-cs/modules'
MD -O2 -Wall -Wstrict-prototypes -pipe -I../include
-I/usr/src/linux/include -D__KERNEL__ -DMODULE -c cs.c
make[4]: MD: Command
Richard A Nelson wrote:
> Version: N/A
> Severity: grave
Never, EVER, EVER*** file a grave bug report without a version
number.
--
see shy jo
On Sat, Jan 15, 2000 at 09:17:51AM -0800, Eric G . Miller wrote:
> On Sat, Jan 15, 2000 at 11:45:16AM -0500, Rajesh Radhakrishnan wrote:
> >
> > dpkg-deb - error: (upstream) version (`linux') doesn't contain any digits
> > dpkg-deb: 1 errors in control file
> > make: *** [kernel-image-deb] Error 2
On Sat, Jan 15, 2000 at 11:45:16AM -0500, Rajesh Radhakrishnan wrote:
> Hi,
>
> I am creating the a custom 2.2.14 kernel using kernel-package. I gave
> the following command,
>
> make-kpkg -rev Custom.1 kernel_image
>
> It went thru the kernel compilation process (after configure), and at
> fina
Hi,
I am creating the a custom 2.2.14 kernel using kernel-package. I gave
the following command,
make-kpkg -rev Custom.1 kernel_image
It went thru the kernel compilation process (after configure), and at
finally it gave me the foll error
test -f System.map && cp System.map \
rich wrote:
...
>Finally, I have found that to do the steps required to compile the
>kernel, I need to be root the whole time. I was under the impression
>that I shouldn't have to be for every step, and that 'fakeroot' should
>be used for the steps that require root permissions. This didn't
Shaleh wrote:
>
> On 03-May-99 rich wrote:
> >> You need to do some tweaking to get sound support to work properly as
> >> a module. If you don't do anything special, a read request on
> >> /dev/audio tells the kernel to try to get sound support, so it loads
> >> the 'sound' module. Since there'
On 03-May-99 rich wrote:
>> You need to do some tweaking to get sound support to work properly as
>> a module. If you don't do anything special, a read request on
>> /dev/audio tells the kernel to try to get sound support, so it loads
>> the 'sound' module. Since there's no module installed that
> You need to do some tweaking to get sound support to work properly as
> a module. If you don't do anything special, a read request on
> /dev/audio tells the kernel to try to get sound support, so it loads
> the 'sound' module. Since there's no module installed that can
> provide actual audio da
rich <[EMAIL PROTECTED]> writes:
rich> Today I tried to set up module support for my kernel and
rich> "modulize" a bunch of stuff, and I'm having some
rich> problems. First, from reading the
rich> /usr/doc/kernel-source-2.2.1/debian.README file, I thought that
rich> 'make-kpkg --revision=custom.1.
Hello all,
I have compiled my kernel using 'make-kpkg' before and found it
relatively painless - as long as I didn't use modules.. Today I tried to
set up module support for my kernel and "modulize" a bunch of stuff, and
I'm having some problems. First, from read
Lawrence Chim <[EMAIL PROTECTED]> writes:
> I have problem to compile the Linux kernel 2.0.28 using make-kpkg,
> here is a part of the screen dump, it didn't happen when I compiled
> 2.0.26
>
> MIDI interface support (CONFIG_MIDI) [Y/n/?]
> FM synthesizer (YM3812/
> I have problem to compile the Linux kernel 2.0.28 using make-kpkg,
> here is a part of the screen dump, it didn't happen when I compiled
> 2.0.26
This is because the behaviour of GNU expr regexps in shellutils 1.14 has
changed to be more POSIX-like, AND 2.0.28 has started usi
I have problem to compile the Linux kernel 2.0.28 using make-kpkg,
here is a part of the screen dump, it didn't happen when I compiled
2.0.26
MIDI interface support (CONFIG_MIDI) [Y/n/?]
FM synthesizer (YM3812/OPL-3) support (CONFIG_YM3812) [Y/n/?]
I/O base for SB Check from manual of the
55 matches
Mail list logo
