Date: Thu, 2 Sep 2004 18:14:58 +0200 (CEST) From: Joerg Pulz <Joerg.Pulz@frm2.tum.de> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: freebsd-ia64@freebsd.org Subject: Re: another 5.3-BETA2 problem Message-ID: <20040902174321.V50481@hades.admin.frm2> In-Reply-To: <20040901204745.GA10115@dhcp53.pn.xcllnt.net> References: <20040901131932.O50481@hades.admin.frm2> <20040901151653.GA9238@dhcp53.pn.xcllnt.net> <20040901204745.GA10115@dhcp53.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 1 Sep 2004, Marcel Moolenaar 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. while booting, the kernel still shows the backtrace in the ata section but i could install and boot the system. it is running for some hours now without problems. 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. > It's pretty uncommon (from my perspective) to not have SCSI disks > on ia64, so it's definitely something that has gone unnoticed so far. the system came to me a longer period of time ago as pure IDE system. there is no SCSI stuff in there. the next problem is the old EFI-1.02 implementation. EFI isn't recognizing SCSI or SCSI-Raid controller as a block device which makes booting from such devices impossible. as the vendor no longer provides any updates for the system, i have to stuck with 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. 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. regards and thanks Joerg - -- The beginning is the most important part of the work. -Plato -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBN0cFSPOsGF+KA+MRAtsQAJ46lt8ECcX3p8cjeV61v8SqdCOFJwCdGmKa YVhsN1fEGb3aeunyJD/HyCI= =IlUQ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040902174321.V50481>