amd64/122624: unusable mininal installation of FreeBSD-7.0
John Baldwin
jhb at freebsd.org
Wed Apr 23 14:10:03 UTC 2008
The following reply was made to PR amd64/122624; it has been noted by GNATS.
From: John Baldwin <jhb at freebsd.org>
To: freebsd-amd64 at freebsd.org
Cc: Peter Jeremy <peterjeremy at optushome.com.au>,
Fernan Aguero <fernan at iib.unsam.edu.ar>,
freebsd-gnats-submit at freebsd.org,
Mike Meyer <mwm at mired.org>
Subject: Re: amd64/122624: unusable mininal installation of FreeBSD-7.0
Date: Wed, 23 Apr 2008 09:45:51 -0400
On Tuesday 22 April 2008 03:32:11 pm Peter Jeremy wrote:
> On Tue, Apr 22, 2008 at 04:06:32PM -0300, Fernan Aguero wrote:
> >This time I was able to login and check libcrypto:
> >MD5 (/lib/libcrypto.so.5) = ee943528c8046145b60359f50f45fbf4
> >
> >And as suggested by Gavin, I rebooted and checked things
> >again.
> >
> >Upon reboot, the error was now different (relocation type changed),
> >and the checksum for libcrypto.so.5 changed!
> >MD5 (/lib/libcrypto.so.5) = a24993818d2b888df053428b48a18eac
>
> ...
>
> >Maybe it's a problem with the disk driver in FreeBSD-7 for
> >this chipset? (dmesg attached) ... it seems like reading and
> >writing to disk is the problem ... but this only happens
> >with FreeBSD-7.0. Any suggestion as to how I can further debug this?
>
> ...
>
> >atapci0: <ServerWorks HT1000 SATA150 controller> port
> > 0xecb0-0xecb7,0xeca0-0xeca3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem
> > 0xefdfe000-0xefdfffff irq 6 at device 14.0 on pci3
>
> There are a number of threads in -current discussing the brokenness of
> that chipset. The impression I get is that 7.0-RELEASE will never work
> for you but there are some fixes in 7.0 post -RELEASE. A sample is:
> http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084272.html
> http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084075.html
The 'SWKSMIO' part of the patch I posted might fix the issues with PATA-mode.
--
John Baldwin
More information about the freebsd-amd64
mailing list