Re: kernel-source*14-5_all.deb and make-kpkg

2000-04-26 Thread ktb
I'm not entirely sure what your trying to say here.  Are you saying that
you have compiled the kernel-source with kpkg and now are at the point
where you have something like --
kernel-image-2.0.36_custom.2.0.36.1_i386.deb ?

If so then just --
dpkg -i kernel-image-whatever your version.deb  

If that isn't the case let us know.
hth,
kent


Antonio Rodriguez wrote:
 
 The directions to install a kernel using make-kpkg are more or less
 clear to me if doing it with a kernel*tar.gz one, because it unpacks the
 make instructions. Now, what to do when it is a .deb one? I tried make
 menuconfig as indicated before in an earlier thread, but there aren't
 any make rules. Is there any way of unpacking them from the *_all.deb?
 Please be explicit with the directions, I am starting to believe I'm
 getting slow.
 Thanx
 Antonio.


Re: kernel-source*14-5_all.deb and make-kpkg

2000-04-26 Thread Antonio Rodriguez
No, what I meant was that I had apt-got (past tense on purpose) installed
kernel-source*, but make-kpkg was complaining that it didn't have make rules. 
So,
after reading a little more, I just got the original kernerl 2.2.14, unpacked 
it and
all then worked, except for my scssi emulation module, which is probably the 
only
reason I am persisting in this. Let me be more explicit: I got all unpacked, 
did make
menuconfig assuring myself of having all scssi related with Y, i.e., with 
*, saved
the config file. After this I made make-kpkg clean , make-kpkg --revision 
kernel_image
etc, dpkg -i kernel_image, created my boot floppy ( I can't boot from hdb, in 
hda I
have win 98). Now, when I booted again, the scsi modules were not there, that 
is ,
they had been probably killed by mak-kpkg clean.
So, I tried again, this time I didn't do the clean stuff, I added make-kpkg 
modules,
then make-kpkg --revision kernel_image, the dpkg -i the image. This time the 
modules
didn't load either, but at least they were there when I run insmod sg, which 
did not
happen with the cleaned image. All this makes me believe that clean takes 
care of
the unresolved symbols modules, i.e., deletes them. Now, what I have is a 
CDWriter HP
atapi ide and an ACER cdrom, i don't have scsi, but I need it for my burning
activities!
The positions are IRQ 14, IRQ 15 (0x3f6 and 0x376). Please throw some light 
onto this.

ktb wrote:

 I'm not entirely sure what your trying to say here.  Are you saying that
 you have compiled the kernel-source with kpkg and now are at the point
 where you have something like --
 kernel-image-2.0.36_custom.2.0.36.1_i386.deb ?

 If so then just --
 dpkg -i kernel-image-whatever your version.deb

 If that isn't the case let us know.
 hth,
 kent

 Antonio Rodriguez wrote:
 
  The directions to install a kernel using make-kpkg are more or less
  clear to me if doing it with a kernel*tar.gz one, because it unpacks the
  make instructions. Now, what to do when it is a .deb one? I tried make
  menuconfig as indicated before in an earlier thread, but there aren't
  any make rules. Is there any way of unpacking them from the *_all.deb?
  Please be explicit with the directions, I am starting to believe I'm
  getting slow.
  Thanx
  Antonio.

 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null


Re: kernel-source*14-5_all.deb and make-kpkg

2000-04-26 Thread Joachim Trinkwitz
Antonio Rodriguez [EMAIL PROTECTED] writes:

 The directions to install a kernel using make-kpkg are more or less
 clear to me if doing it with a kernel*tar.gz one, because it unpacks the
 make instructions. Now, what to do when it is a .deb one? I tried make
 menuconfig as indicated before in an earlier thread, but there aren't
 any make rules. Is there any way of unpacking them from the *_all.deb?

When you've got a kernel-source-xxx.deb package, you really *have* got
a kernelxxx.tar.{g|b}z one. It's sitting in /usr/src/ and is waiting
for you to untar it. Then you do a `ln -s kernel-source-xxx linux' and
go on with make-kpkg as before.

Greetings,
joachim