I made a custom kernel:
make kpkg --revision=.custom.10 --append-to-version=.cybo.1 --initrd
kernel_image
this issued in: linux-image-2.6.25.cybo.1_custom.1.0_amd64.deb
I installed this and wanted to make nvidia modules for it:
make-kpkg modules_image
This issued an error: (para phrased
make-kpkg modules_image Error
Hello,
Got a Wacom tablet (For Christmas) and the latest driver from the Wacom Project.
This then required pulling in packages from unstable to satisfy dependencies.
Now, make-kpkg is broke.
Even make-kpkg clean gives the error shown below.
Still need to compile
> version=3.0.1
>
> On Mon, 2004-12-20 at 19:22 -0500, John wrote:
> > On (20/12/04 15:30), Matt Zagrabelny wrote:
> > > hello,
> > > trying to get the hostap modules working:
> > > # aptitude install hostap-source
> > > $ make-kpkg --append-to
On (20/12/04 15:30), Matt Zagrabelny wrote:
> To: debian-user@lists.debian.org
> hello,
> trying to get the hostap modules working:
> # aptitude install hostap-source
> $ make-kpkg --append-to-version=.20041220.0 kernel_image modules_image
> # dpkg -i /usr/src/kernel-image2.6.
hello,
trying to get the hostap modules working:
# aptitude install hostap-source
$ make-kpkg --append-to-version=.20041220.0 kernel_image modules_image
# dpkg -i /usr/src/kernel-image2.6.9.20041220.0_10.00.Custom_i386.deb
# dpkg -i /usr/src/hostap-modules-2.6.9.20041220.0_0.2.5-1
+10.00
Okay I believe I have figured things out, I mean things are working but
I have found no documentaion stating this is how we do this.
I believe in the 2.6.x series the modules_image is essentially
obsolete. Initrd is what is used.
make-kpkg --initrd kernel_image
seems to work
Can anyone
On Sat, 03 Jul 2004 01:01:05 -0400, Paul Tsai <[EMAIL PROTECTED]> wrote:
> hello,
> I'm trying to recompile a kernel with make-kpkg kernel_image
> modules_image . However, the process terminates without any errors and
> there is not modules.deb package. I just instal
hello,
I'm trying to recompile a kernel with make-kpkg kernel_image
modules_image . However, the process terminates without any errors and
there is not modules.deb package. I just installed sid though a nework
install.
Paul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
Incoming from Michael Vert:
> Has anyone succeeded in creating a
>
> make-kpkg ... modules_image
>
> with loop-aes in the "modules" tree?
I thought the "make modules_image" step went the way of the dodo with
2.6.x. A month or so ago there was a thread on
Has anyone succeeded in creating a
make-kpkg ... modules_image
with loop-aes in the "modules" tree?
Kernel sources 2.6.6, and the current loop-aes have been installed from
the unstable distribution and are stored in /usr/src/linux and
/usr/src/modules/loop-aes, resp..
(As required
also sprach Manoj Srivastava <[EMAIL PROTECTED]> [2003.07.11.0457 +0200]:
> See? Each lndir directory only has files that were patched, or
> object files; and the ../linux-2.4.20 is pristine, ready to be
> patched up to 2.4.21.
I see this, yes. I used to do it exactly the same way, with
ha
-f . configdirs/$machine ]; then
. configdirs/$machine
# $patches is now either empty, or it has --added-patches=a,b
fi
cd $machine
make-kpkg --rootcmd fakeroot --append-to-version $machine \
$patches $modules kernel_image
if [ "X$modules" != "X" ]
i hope you don't mind me asking a question...
also sprach Manoj Srivastava <[EMAIL PROTECTED]> [2003.07.06.0223 +0200]:
> % sudo echo 'debian := 5:501c' >> /etc/kernel-pkg.conf
what does this line do?
the reason why i don't like your approach, although i really
appreciate you showing it to me, i
/src/cryptoapi-core.tar.gz
% tar zvvfx /usr/src/cryptoloop.tar.gz
% tar jvvfx linux-2.4.21.tar.bz2
% mkdir 2.4.21
% cd 2.4.21
% lndir ../linux-2.4.21
% cp /boot/config-2.4.20 .config
% make-kpkg --rootcmd fakeroot --append-to-version -cryptoloop kernel_image
% fakeroot make-kpkg --append-to-version
also sprach martin f krafft <[EMAIL PROTECTED]> [2003.07.01.0006 +0200]:
> I still don't understand why that would solve the problem.
I am giving up. I thought it would be nice if make-kpkg could do
some magic to be able to compile modules from /usr/src/modules even
if /usr is read-only. Like some
On Tue, 01 Jul 2003 11:43:01 -0500
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> > So I am wondering: what am I doing wrong? I *should* be able to
> > compile modules for an existing kernel tree without write privs to
> > /usr/src/modules/..., right?
>
>
> Right.
>
> What is MODULE_
On Monday 30 June 2003 05:06 pm, martin f krafft wrote:
> also sprach Kevin McKinley <[EMAIL PROTECTED]> [2003.06.30.1548
+0200]:
> > When you do "fakeroot make-kpkg ..." make-kpkg itself runs under
> > fakeroot, so a root environment is provided whenever necessary,
> > instead of "as expected" by
On Mon, 30 Jun 2003 22:17:58 +0200, martin f krafft <[EMAIL PROTECTED]> said:
> also sprach David Z Maze <[EMAIL PROTECTED]> [2003.06.30.2141 +0200]:
>> > cp: cannot create regular file
>> > `/usr/src/modules/nvidia/debian/control': Permission denied
>>
>> Right: with the default setup, the u
ders
> these worked quite nicely.
Cool.
> Then I tried to compile a module for that kernel:
> make-kpkg --append-to-version
> -diamond-grsec-1.9.10+freeswan-ext-1.99+preempt-20030617-2
> --rootcmd fakeroot --added-modules nvidia modules_image
> This fails:
> if [ -f /
On Mon, 30 Jun 2003 22:17:58 +0200
martin f krafft <[EMAIL PROTECTED]> wrote:
> > Right: with the default setup, the user who runs make-kpkg needs write
> > access to /usr/src/modules, or you need to run under sudo.
>
> what??? this must be a joke? /usr can be mounted read-only!
That's not a jok
On 01 Jul 2003 09:57:19 +0200
JG <[EMAIL PROTECTED]> wrote:
> Setup:
> 1.- Add yourself to the "src" group (/usr/src/ belongs to root.src)
> 2.- Check that /usr/src/modules belongs to root.src, and has the sticky
> bit on:
>
> $ls -lsd /usr/src/modules/
>4 drwxrwsr-x2 root src
Package: kernel-package
Version: 8.040
Severity: normal
I am filing this as a bug.
also sprach martin f krafft <[EMAIL PROTECTED]> [2003.06.30.2217 +0200]:
> > fakeroot make-kpkg --options
>
> How will that help. It is actually trying to create a file under
> /usr/src while being called as a non
also sprach Kevin McKinley <[EMAIL PROTECTED]> [2003.06.30.1548 +0200]:
> When you do "fakeroot make-kpkg ..." make-kpkg itself runs under
> fakeroot, so a root environment is provided whenever necessary,
> instead of "as expected" by make-kpkg's author.
I still don't understand why that would so
On Mon, 30 Jun 2003 22:17:58 +0200
martin f krafft <[EMAIL PROTECTED]> wrote:
> How are other people doing it?
Umm, I'm doing it the way I suggested to you. :)
fakeroot make-kpkg ...
Works fine for me.
Kevin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tro
also sprach Kevin McKinley <[EMAIL PROTECTED]> [2003.06.29.2015 +0200]:
> Try a different syntax for make-kpkg:
>
> fakeroot make-kpkg --options
How will that help. It is actually trying to create a file under
/usr/src while being called as a non-root user. fakeroot won't
magically allow that...
On Sun, 29 Jun 2003 17:13:41 -0500
David <[EMAIL PROTECTED]> wrote:
> I noticed one oddity myself.. I've just been working with make-kpkg, and
> noticed in the output, that when it tried to delete (I think) and
> re-install the debian directory, that if I used --rootcmd fakeroot, it
> reported
martin f krafft <[EMAIL PROTECTED]> writes:
> Then I tried to compile a module for that kernel:
>
> make-kpkg --append-to-version
> -diamond-grsec-1.9.10+freeswan-ext-1.99+preempt-20030617-2
> --rootcmd fakeroot --added-modules nvidia modules_image
Kernel modules&#x
On Fri, Jun 27, 2003 at 11:50:31AM -0400, Emma Jane Hogbin wrote:
> I know that I've had ALSA working on this laptop, unfortunately I can't
> find my notes on how I installed it the last time. This time I'm getting
> errors that give me no information on how to track down the problem.
Totally dele
e nicely.
>
> Then I tried to compile a module for that kernel:
>
> make-kpkg --append-to-version
> -diamond-grsec-1.9.10+freeswan-ext-1.99+preempt-20030617-2
> --rootcmd fakeroot --added-modules nvidia modules_image
>
> This fails:
>
> if [ -f /usr/src/modules/
On Fri, 27 Jun 2003 18:50:13 +0200
martin f krafft <[EMAIL PROTECTED]> wrote:
> cp: cannot create regular file
> `/usr/src/modules/nvidia/debian/control': Permission denied
>
> which makes perfect sense, because
>
> diamond:...new/src/linux-2.4.21> id
> uid=1000(madduck) gid=100(users) .
+freeswan-ext-1.99+preempt-20030617-2
--rootcmd fakeroot --added-modules nvidia modules_image
This fails:
if [ -f /usr/src/modules/nvidia/debian/control.template ]; then \
cp -a /usr/src/modules/nvidia/debian/control.template
/usr/src/modules/nvidia/debian/control; \
fi
cp: cannot
ake-kpkg --append-to-version=.currentkernelname modules_image
(no errors at the end of the processing)
[EMAIL PROTECTED]:/usr/src$ sudo dpkg -i
alsa-modules-2.4.20.030603d_0.9.4-1+10.00.Custom_i386.deb
Password:
(Reading database ... 53070 files and directories currently installed.)
Preparing to
While I was working on re-installing my system I tried everything The
Debian Way first. I noticed that this does NOT work for my PCMCIA wireless
card. My problem was that not all of the modules loaded when I installed
the package (orinoco loaded, but orinoco_cs did not -- both should have
loaded an
Kurt Lieber <[EMAIL PROTECTED]> writes:
> On Sunday 20 January 2002 02:03 am, Brian Nelson wrote:
>
> > No. Do 'make-kpkg kernel_image' instead. modules_image is for modules
> > external to the kernel source, like ALSA.
>
> OK, so I went ahead a
On Sunday 20 January 2002 02:03 am, Brian Nelson wrote:
> No. Do 'make-kpkg kernel_image' instead. modules_image is for modules
> external to the kernel source, like ALSA.
OK, so I went ahead and recompiled the kernel using make-kpkg kernel_image
> > Assuming so, what d
Kurt Lieber <[EMAIL PROTECTED]> writes:
> I just compiled a new kernel and realized that I forgot to include ppp
> support in the kernel.
>
> Rather than recompiling a new custom kernel, can I just make-kpkg clean, make
> menuconfig and make-kpkg modules_image to compile
On Sat, Jan 19, 2002 at 10:00:31PM -0800, Kurt Lieber wrote:
> I just compiled a new kernel and realized that I forgot to include ppp
> support in the kernel.
>
> Rather than recompiling a new custom kernel, can I just make-kpkg clean, make
> menuconfig and make-kpkg modules_i
I just compiled a new kernel and realized that I forgot to include ppp
support in the kernel.
Rather than recompiling a new custom kernel, can I just make-kpkg clean, make
menuconfig and make-kpkg modules_image to compile ppp kernel support as a
module?
Assuming so, what do I then need to do
Hi,
>>"Richard" == Richard E Hawkins Esq <[EMAIL PROTECTED]> writes:
Richard> It seems that "make-kpkg modules_image" runs the pcmcia
Richard> config script, with a string of \n's to take the
Richard> defaults--forcing the package defaults, rathe
It took me a whiel to figure out what was going on here. I was trying
compile a kernel & pcmcia stuff for another computer (using a P2 for a
486).
It seems that "make-kpkg modules_image" runs the pcmcia config script,
with a string of \n's to take the defaults--
40 matches
Mail list logo
