Date: Wed, 23 Apr 2008 05:32:11 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Fernan Aguero <fernan@iib.unsam.edu.ar> Cc: freebsd-gnats-submit@freebsd.org, Mike Meyer <mwm@mired.org>, freebsd-amd64@freebsd.org Subject: Re: amd64/122624: unusable mininal installation of FreeBSD-7.0 Message-ID: <20080422193211.GN92261@server.vk2pj.dyndns.org> In-Reply-To: <20080422190632.GA16867@iib.unsam.edu.ar> References: <20080421182247.GI2974@iib.unsam.edu.ar> <20080421152659.4c0c9a53@mbook-fbsd> <20080422190632.GA16867@iib.unsam.edu.ar>
next in thread | previous in thread | raw e-mail | index | archive | help
--W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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) =3D 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) =3D a24993818d2b888df053428b48a18eac =2E.. >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? =2E.. >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 --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iEYEARECAAYFAkgOPTsACgkQ/opHv/APuIdInwCeJGx6f1JJmmUfjmafQE6UWAAt wlIAoIfG8RVyuYNVF7oyswIn3RAeAq5x =U543 -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080422193211.GN92261>