another 5.3-BETA2 problem
Marcel Moolenaar
marcel at xcllnt.net
Thu Sep 2 09:42:52 PDT 2004
On Thu, Sep 02, 2004 at 06:14:58PM +0200, Joerg Pulz wrote:
>
> >Can you try setting the hw.ata.ata_dma tunable to 0 in the loader
> >before booting the kernel. Like:
> >
> > OK set hw.ata.ata_dma=0
> > OK boot
> >
> >This currently required on sparc64 and we may also need it on ia64.
>
> i tried this and it seems to work.
Thanks, that's good to know.
> i can remember that the latest snapshot (20040810) you provided was
> working without setting hw.ata.ata_dma=0, so the source of this problem
> could be in the latest changes to the ata subsystem 2-3 weeks ago.
Yes, that's correct. A fix is being worked on...
> the system as it currently is but i surely will connect some external
> disks to an "Adaptec SCSI Raid 2200S" using the aac(4) driver. Maybe it
> would be a good idea to replace the definitely not working asr(4) with
> aac(4) in GENERIC.
Yes. asr(4) has already been removed on HEAD. I think it makes sense to
remove it from the RELENG_5 branch as well. I don't know if aac(4) works
on ia64, though.
> but anyway, i also tried to install the system onto a SCSI disk connected
> to a "Tekram DC-390U2W" controller to check if an installation would be
> possible. the kernel recognized the controller correctly as 'sym0'. the
> connected disk was also found and registered as 'da0'. but unfortunately
> sysinstall complains about no disk to install the system.
If the disk contains a valid MBR, then it's currently rejected. The point
of which is that we would destroy the disk otherwise. Try if clobbering
the first sector on the disk makes a difference.
FYI,
--
Marcel Moolenaar USPA: A-39004 marcel at xcllnt.net
More information about the freebsd-ia64
mailing list