"Bruce" == Bruce Park <[EMAIL PROTECTED]> writes:
Bruce> Hello debian users, I'm currently using the 2.4.18-bf2.4
Bruce> kernel and I would like to use a new kernel so that I can
Bruce> have access to my ms sidewinder joystick.
Bruce> Since I'm new to kernel compiling, I was w
Bruce Park, 2002-Dec-23 21:33 -0500:
> Hello debian users,
>
> I'm currently using the 2.4.18-bf2.4 kernel and I would like to use a new
> kernel so that I can have access to my ms sidewinder joystick.
> Since I'm new to kernel compiling, I was wondering if anyone can give me
> some pointers on
Hello debian users,
I'm currently using the 2.4.18-bf2.4 kernel and I would like to use a new
kernel so that I can have access to my ms sidewinder joystick.
Since I'm new to kernel compiling, I was wondering if anyone can give me
some pointers on this. For example, I don't even know what new ker
04/11/2002 13:12:57, "Emanuele Boieri" <[EMAIL PROTECTED]> wrote:
> then I copied the new image in the boot location of the old one /boot/
> bzImage.(I saved the old one). So I edit the lilo.conf
if you copied the new image to the same place as the old one, you shouldnt
need to edit lilo.conf
>
On Mon, 2002-11-04 at 07:12, Emanuele Boieri wrote:
> Hi everybody I hope that somenone can help me. I just followed
> precisely the instruction for compiling/installing a new kernel
>(2.4.19). The previeous version was 2.2.
> 1.. tar xvjf "the kernel source"
> 2.. make menuconfig
> 3.. make
On Monday 04 November 2002 14:12, Emanuele Boieri wrote:
> Hi everybody I hope that somenone can help me. I just followed precisely
> the instruction for compiling/installing a new kernel (2.4.19). The
> previeous version was 2.2. 1.. tar xvjf "the kernel source"
> 2.. make menuconfig
> 3.. ma
2002
13:13To: debianSubject: Compiling a new
kernel
Hi everybody I hope that somenone can help me. I
just followed precisely the instruction for compiling/installing a new
kernel (2.4.19). The previeous version was 2.2.
tar xvjf "the kernel source"
make menu
Hi everybody I hope that somenone can help me. I
just followed precisely the instruction for compiling/installing a new
kernel (2.4.19). The previeous version was 2.2.
tar xvjf "the kernel source"
make menuconfig
make dep
make bzImage
make modules
make modules_install
then I copi
> bash-2.03# insmod ./es1371.o
> ./es1371.o: kernel-module version mismatch
> ./es1371.o was compiled for kernel version 2.2.18pre21
> while this kernel is version 2.2.17.
Hi Kaloyan!
I think you shold look whether your new kernel is booting. The new vmlinuz
should be in /boot or if you made no c
> bash-2.03# insmod ./es1371.o
> ../es1371.o: kernel-module version mismatch
> ./es1371.o was compiled for kernel version 2.2.18pre21
> while this kernel is version 2.2.17.
Looks like you're not running the newly compiled kernel 2.2.18pre21, but
your old 2.2.17. You can check what kernel you're
Hello,
I recently tried to compile a new kernel (2.2.18pre21) on my machine. I used
the instructions in "Compiling a new kernel" from "Installing Debian
GNU/Linux 2.2 For Intel x86" document:
http://www.debian.org/releases/stable/i386/ch-post-install.en.html#s-kernel-b
Hi,
>>"Rajesh" == Rajesh Saxena <[EMAIL PROTECTED]> writes:
Rajesh> (Then I moved /lib/modules/2.2.17 to /lib/modules/2.2.17.old)
Please note that this location shall not be used by either
your old kernel, nor you new one. May I humbly suggest
kernel-package, and specifically point yo
dprobe: modprobe: Can't locate module net-pf-1
Before I attach the .config file let me say that this computer booted up
fine before compiling a new kernel and that I've tried to boot into
single user mode but that won't work either because of the module
problems. Can someone please point
On Thu, Jun 29, 2000 at 10:28:12AM +0200, Luca De Giorgi wrote:
> Hi,
> I'm a new entry in the worderful Debian world.
> Previously i'd used Red Hat 6.x ad Mandrake but i thought i' was time to
> make a jump in the real Linux world and started using a potato release
> Well, my problem arise when i
Hi,
I'm a new entry in the worderful Debian world.
Previously i'd used Red Hat 6.x ad Mandrake but i thought i' was time to
make a jump in the real Linux world and started using a potato release
Well, my problem arise when i want to build a custom kernel the Debian-way.
When i built it i found a
hello,
i did just upgrade my laptop to potato, noticed that an old 2.2.1 kernel was
running and launched compile...
but it aborted with the message:
erm7:/usr/src/linux# make-kpkg binary
...
(cd debian/tmp-source/usr/src/; tar zcf kernel-source-2.2.3.tar.gz
kernel-source-2.2.3;\
rm -r
>> "JRL" == James R Lunsford <[EMAIL PROTECTED]> writes:
JRL> /usr/src/linux is linked to the 2.0.34 directory. Am I correct
JRL> in assuming that I have to relink /usr/src/linux to the 2.0.35
JRL> directory?
Yes.
JRL> Anyway, can someone give me a down and dirty way to do this? Also, what
JR
I'd like to go from 2.0.34 to 2.0.35. I'm moving kind of slow because
I'm using the SuSE 3DLabs xserver for my Creative Labs video card, and
I've heard that it won't work with kernels above 2.0.34 and I recently
heard that it WILL work with 2.0.35.
Anyway, I've had to recompile my existing kerne
Thalia L. Hooker wrote:
> Hi,
>
...
> I tried the kernel package and compilation went fine except it didn't seem
> to compile any of the new modules even though I requested SCSI support,
> SCSI disk support, and the driver AHA152x. I say this because when I
> noticed it had not detected an
Hi,
>>"Thalia" == Thalia L Hooker <[EMAIL PROTECTED]> writes:
Thalia> Hi, I finally got over my signal 11 problems and can now
Thalia> recompile a kernel. The problems seem to have been due to bad
Thalia> RAM. I reinitialized my partitions because I was afraid I
Thalia> would run into filesystem p
Hi,
>>"Mike" == Mike Miller <[EMAIL PROTECTED]> writes:
Mike> I'm thinking of starting a Debian custom kernel faq that would
Mike> address issues such as Ignus' questions and my own experience
Mike> with pcmcia and the kernel. Any one interested in contributing?
Please include the Proble
Hi,
I finally got over my signal 11 problems and can now recompile a kernel.
The problems seem to have been due to bad RAM. I reinitialized my
partitions because I was afraid I would run into filesystem problems due to
the numerous times my computer froze when I was trying to recompile a
kernel.
Hi,
>>"Ignus" == Ignus Fast <[EMAIL PROTECTED]> writes:
Ignus> I am still having a lot of trouble! I have no trouble running:
Ignus> 'make xconfig', followed by
Ignus> 'make kpkg-clean',
This is the wrong order. Try
make-kpkg clean,
followed by
make xconfig
Ignus> 'make-kpkg
You might have better success it you make your modules using
make-kpkg rather than make-ing in the source directory. Try
executing `make-kpkg --targets' to get a list of targets (which
includes modules).
Caveat - I haven't made modules with make-kpkg myself, so I don't
know what pitfalls might aw
On Tue, 28 Oct 1997, Ignus Fast wrote:
> I am still having a lot of trouble! I have no trouble running:
>
> 'make xconfig', followed by
> 'make kpkg-clean',
> 'make-kpkg -r custom.1.0 kernel_image'
> 'dpkg -i /usr/src/kernel-image-2.0.30_custom.1.0_i386.deb'
Ready?!?
> 'make modules'
> 'make m
I am still having a lot of trouble! I have no trouble running:
'make xconfig', followed by
'make kpkg-clean',
'make-kpkg -r custom.1.0 kernel_image'
'dpkg -i /usr/src/kernel-image-2.0.30_custom.1.0_i386.deb'
'make modules'
'make modules_install'
to create a custom kernel boot disk. But
> In the instructions that came with the kernel source package, Linus
> recommends making symlinks in the include directory to directories in the
> usr/src/linux/arch directory.
>
> I also remember reading that libc5-dev contains a set of headers.
>
> Someone on the list recommended that the dire
In the instructions that came with the kernel source package, Linus
recommends making symlinks in the include directory to directories in the
usr/src/linux/arch directory.
I also remember reading that libc5-dev contains a set of headers.
Someone on the list recommended that the directories in the
28 matches
Mail list logo
