From owner-freebsd-hackers Thu Dec 12 10:36:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA27081 for hackers-outgoing; Thu, 12 Dec 1996 10:36:42 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA27076 for ; Thu, 12 Dec 1996 10:36:37 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.3/8.8.3) with UUCP id TAA23610 for hackers@freebsd.org; Thu, 12 Dec 1996 19:35:17 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id TAA05198 for ; Thu, 12 Dec 1996 19:32:19 +0100 (MET) Message-Id: <3.0.32.19961212193214.00a34100@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 12 Dec 1996 19:32:16 +0100 To: hackers@freebsd.org From: Eivind Eklund Subject: 2.1.6 on Compaq Prosignia 500 (2.1.5 worked) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm trying to get a 2.1.6 kernel up and running on a Compaq Prosignia 500. To get 2.1.5 running, there were three changes I had to do: (1) Replace i386/isa/pcibus.c with the version from -current, due to PCI V2 handshaking. This seems to work by default in 2.1.6. (2) Move the lnc0 adapter to be detected like this (in config) >device lnc0 at isa? port 0x7000 net irq 3 drq 0 vector lncintr (3) Add >options "MAXMEM=65536" # 64 MB memory due to Compaq (and Dell) using an extremely irritating aspect of the EISA standard, and saying that they have 16MB in RTC-memory. With this in place, it boots fine under 2.1.5. However, under 2.1.6 it detect the ncr0-device in the Prosignia, print >ncr0: restart (scsi reset) and get a kernel trap (supervisor read from address 0x7 at 0xF0176378) On the 2.1.5, it contnues with the next line >ncr0 waiting for scsi-devices to settle I've tried swapping some of the files back to their 2.1.5 counterparts, but this hasn't helped. I've also tried running with the same pcibus.c as I did under 2.1.5 (from -current late August). If this could be of interest, I'm running GCC 2.7.2.1, which I've compiled myself. I haven't yet tried with a GENERIC kernel, as that won't work on this box anyway (I'll loose my network, and as the box is running as a server...) Anybody got any clues? If not, I'll try to track the bug down further, but I don't want to put down the work if somebody know just what's wrong. -- Eivind Eklund gopher://nic.follonett.no:79/0eivind Work: eivind@dimaga.com http://www.dimaga.com/ Home: perhaps@yes.no http://maybes.yes.no/perhaps/ All of the above is a product of either your or my imagination, and not official.