Hi Dan,
The first go around it told me to rename the modules directory for
2.2.17 to 2.2.17.old, which I didn't do. Instead I just went ahead and
continued. When I rebooted the machine, I was back into the old 2.2.16
kernel. So I did the dpkg -i (mykernel*..) only this time renaming the
module dire
On Mon, 28 Aug 2000, Dale L . Morris wrote:
> I installed the 2.2.17 kernel over 2.2.16 using the make-kpkg
> option. I'm having a problem getting lilo to boot the 2.2.17 kernel,
> if I 'cd /' then run '/sbin/lilo' the machine boots up without any drivers
> for eth0 or sound. If I run 'lilo -L' fro
I installed the 2.2.17 kernel over 2.2.16 using the make-kpkg
option. I'm having a problem getting lilo to boot the 2.2.17 kernel,
if I 'cd /' then run '/sbin/lilo' the machine boots up without any drivers
for eth0 or sound. If I run 'lilo -L' from / it boots up the old 2.2.16
kernel. The only way
FWIW, the solution was "make-kpkg clean kernel_image modules". I
debugged syslogd to find that it was the socket() call itself that
failed, which is pretty low level, so I figured it must be a kernel or
module problem. I think I may have had some modules compiled against
the stock kernel instea
4 matches
Mail list logo
