John Rogers wrote:
> /boot/kernel/aic.ko
> ...
> /boot/kernel/zlib.ko
It looks like lots of kernel modules weren't installed (or, more likely,
were installed but glitched when the system rebooted). If you don't
expect to use any of these modules, it's probably safe to ignore this;
otherwise, you'
"freebsd-update IDS" found the following. Do I need to grab the
kernel files for 6.1? If so, how? I did not find them in
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.1-RELEASE/kernels/
Thank you,
The following files, which are distributed as part of the binary
release, have been modified
John Rogers wrote:
> Before I saw your reply, I just manually created those old-index etc
> by following upgrade.sh, and ran the rest of the upgrade.sh from the
> "Removing schg flag from existing files..." part. After that I have
> ran portupgrade, portsnap etc, and so far don't see problem. Do
Hi, you are right - there was indeed the following messages:
kernel: ad0: FAILURE - READ_DMA status=51
error=40
And this message appeared starting from the date I ran CFS, an
encrypted filesystem. It's a half year old WesternDigital250GB disk.
I now disabled dma (was UDMA100 actually) by adding
John Rogers wrote:
> Installing new kernel into /boot/GENERIC... done.
> Moving /boot/kernel to /boot/kernel.old... done.
> Moving /boot/GENERIC to /boot/kernel... done.
> Removing schg flag from existing files...
>
> Then my connection to the server froze and I found the server rebooted
> itself.
Wow, I did not expect Colin's direct reply - and so prompt! Thanks,
and great to know binary updates will be foreseeable.
I actually already did it again, since it doesn't make sense to binary
upgrade all those source files, I renamed /usr/src to something else,
and this greatly reduced the numb
Oops, I forgot to edit the subject line before hitting 'Send' -- for
some reason, SpamAssassin thought that John's original email needed
to be marked as **SPAM**.
Colin Percival
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mail
