Installation problems on AMD64
Dear Group, when trying to install the current 4.4 from th iso image in a AMD64 machine I get following error: panic: pci_make_tag: bad request is that due to some faulty H/W? Just for the records, I was using that box with a debian install without any problems! Thanks Tony
Re: Installation problems on AMD64
On Sat, 28 Mar 2009 20:13:30 +0100 Tony Berth wrote: > Dear Group, > > when trying to install the current 4.4 from th iso image in a AMD64 > machine I get following error: > > panic: pci_make_tag: bad request > > is that due to some faulty H/W? > Please see http://www.openbsd.org/report.html See if the same problem occur on 4.5-current.
Re: Installation problems on AMD64
On Sat, Mar 28, 2009 at 9:23 PM, Thomas Pfaff wrote: > On Sat, 28 Mar 2009 20:13:30 +0100 > Tony Berth wrote: > > Dear Group, > > > > when trying to install the current 4.4 from th iso image in a AMD64 > > machine I get following error: > > > > panic: pci_make_tag: bad request > > > > is that due to some faulty H/W? > > > > Please see http://www.openbsd.org/report.html > > See if the same problem occur on 4.5-current. > I couldn't follow the 'report' procedure cause the system wasn't installed yet! I git that problem right after inserting the CD with the immage! Anyway, via 'boot -c' and 'disable acpi' I was able to finish the installation! Just a quick (non really relevant) question. What is the best tool to check the integrity of SATA HDs? To check if they have bad sectors or other problems? Thanks for your prompt help Tony
Re: Installation problems on AMD64
On Mon, 30 Mar 2009 15:06:59 +0200, Tony Berth wrote > Just a quick (non really relevant) question. What is the best tool > to check the integrity of SATA HDs? To check if they have bad > sectors or other problems? I like the smartmontools package, which communicates with SMART electronics on the drives. The built-in atactl(8) can also communicate with SMART, but I prefer smartmontools for two reasons: * Automatic short and long offline tests with e-mailed trouble reports are easy to set up. * The status reports are readable by humans. Smartmontools only communicates with SMART electronics, and its tests do not write sectors. If you want to write test patterns to sequences of sectors -- typically desired after sector failures in order to force the drive to assign spares -- the badblocks program included with the e2fsprogs package works very well.
