Thanks for the response.
I first tried to do an apt-get install 2.6.0... and I tried that out.
When I tried to boot nothing appeares on screen, but the hard drive
continues to work.
Next I tried compiling my own kernel, and after a couple hours of
fighting in order to get it to compile, the end result was the same.
Next I found a fellow with the same hard ware that had posted a .config
(found at the bottom of
http://www.krwtech.com/ken/linux/2650c.html) for
2.5.69 which I used as a basis on my next try. Same result.
Perhaps something got broke between 2.5.69 and 2.6.0testwhatever?
I used instructions provided at
http://www.linuxathome.net/updating_kernel.php , although the make dep
step is evidently no longer needed.
At this point should I try compiling 2.5.69 with the other fellows
.config file or should I just resist the urge to try to get my battery
monitoring working?
der.hans wrote:
> Am 24. Jul, 2003 schwätzte Rob Wultsch so:
>
>
>>1. How do I force an upgrade/install of package even if it breaks other
>>things? I know I asked this a few months back, but I forgot the answer
>>and could not find it in the archeive. Sorry
>
>
> Answer: don't.
>
> If you choose to ignore that answer look at the man page for dpkg.
>
> Find out why the dependencies aren't working and get that fixed.
>
>
>>2. I see a package like "kernel-image-2.6.0-test0". I assumed that this
>>would install a precompiled 2.6 kernel. Is this correct? What is the
>>command to determine what kernel I am running?
>
>
> uname -a
>
> That will show you what kernel you're running.
>
> The kernel-image packages are precompiled kernels. You need to make sure
> you're bootloader is correctly configured, but otherwise they generally work
> well. I wouldn't expect that for the 2.6 test kernels, though :).
>
> $ feta show kernel-image-2.6.0-test1-1-386
> .
> .
> .
> Description: Linux kernel image for version 2.6.0-test1 on 386.
> This package contains the Linux kernel image for version 2.6.0-test1 on
> 386,
> the corresponding System.map file, and the modules built by the packager.
> It also contains scripts that try to ensure that the system is not left in
> a unbootable state after an update.
> .
> If you wish to update a bootdisk, or to use a bootloader to make
> installing and using the image easier, we suggest you install the latest
> fdutils (for formatting a floppy to be used as boot disk), and LILO, for a
> powerful bootloader. Of course, both these are optional.
> .
> Kernel image packages are generally produced using kernel-package,
> and it is suggested that you install that package if you wish to
> create a custom kernel from the sources.
>
> ciao,
>
> der.hans
(text/plain)