... almost, that is :evil:
I got off eBay for $100 an IBM Netfinity 3500 M10. Here's the specs:
CPU: Pentium III 550MHz (Slot 1) = (WORKS!)
MoBo: 4xPCI, 1xISA, 1xAGP = (WORKS!)
Chipset: Intel 440LX = (WORKS!)
RAM: 320MB SDRAM ECC = (WORKS!)
SCSI: Adaptec Integrated AIC-7895 Ultra2 Wide SCSI (Dual) = (WORKS!)
HDD: Seagate 36GB Ultra-320 SCSI 10,000 RPM = (WORKS!)
HDD: IBM-PSG DNES-318350W SCSI 7,200 RPM = (WORKS!)
CD: LG CD-ROM IDE = (WORKS!)
Floppy: 3.5" 1.44MB Floppy Drive = (WORKS!)
TO BE TESTED:
Video: Number 9 S3 Savage4 8MB VRAM AGP (REPLACED)
Sound: Cirrus Logic CS 4236B, Sound Blaster 16/Pro, Sound Blaster compliant
Network: Intel 82557-based Integrated Ethernet PCI 10/100
I added the following hardware which I managed to scavenge:
CPU2: Pentium III 550MHz (Slot 1) = (WORKS, but OS4.2 does not use it)
SCSI: Adaptec AHA-2940UW PCI controller = (WORKS!)
Video: Matrox Millenium II 8MB PCI = (WORKS!)
The hardware seems like a perfect match since all of it has drivers.
The Netfinity is also a black box with matching black keyboard and mouse. All I need is a nice NeXT label to attach to the front of it :lol:
Installed OS4.2 on an IDE drive to help debug the system. I use Laurent's walkthrough since using PIIX drivers require a little hack to get the driver copied to the hard disk (it's a script bug on the OS4.2 install CD).
Here is a Linux 'lspci' (used Slax on a 200MB CD-R) output to sort out the PCI devices:
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
Flags: bus master, medium devsel, latency 32
Memory at e4000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 1.0
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
Memory behind bridge: f7f00000-f7ffffff
Prefetchable memory behind bridge: e8000000-f7cfffff
00:02.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 05)
Subsystem: IBM: Unknown device 00d7
Flags: bus master, medium devsel, latency 64, IRQ 15
Memory at e3fe7000 (32-bit, prefetchable) [size=4K]
I/O ports at 7060 [size=32]
Memory at f7e00000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [dc] Power Management version 1
00:03.0 SCSI storage controller: Adaptec AHA-2940U/UW / AHA-39xx / AIC-7895 (rev 04)
Subsystem: Adaptec AHA-2940U/2940UW Dual AHA-394xAU/AUW/AUWD AIC-7895B
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 7400 [size=256]
Memory at f7dfe000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 20020000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 1
00:03.1 SCSI storage controller: Adaptec AHA-2940U/UW / AHA-39xx / AIC-7895 (rev 04)
Subsystem: Adaptec AHA-2940U/2940UW Dual AHA-394xAU/AUW/AUWD AIC-7895B
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 7800 [size=256]
Memory at f7dff000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 1
00:04.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
Flags: bus master, medium devsel, latency 0
00:04.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [Master])
Flags: bus master, medium devsel, latency 32
I/O ports at fff0
00:04.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI])
Flags: bus master, medium devsel, latency 48, IRQ 11
I/O ports at ff00 [size=32]
00:04.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
Flags: medium devsel, IRQ 9
00:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74)
Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC
Flags: bus master, medium devsel, latency 80, IRQ 10
I/O ports at 7080 [size=128]
Memory at f7dfdf80 (32-bit, non-prefetchable) [size=128]
Expansion ROM at 20000000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
00:0e.0 Communication controller: 3Com Corp, Modem Division WinModem
Subsystem: 3Com Corp, Modem Division: Unknown device 007b
Flags: medium devsel, IRQ 15
Memory at e3fe6fc0 (32-bit, prefetchable) [size=64]
Memory at e3ff0000 (32-bit, prefetchable) [size=64K]
Memory at e3fe8000 (32-bit, prefetchable) [size=32K]
Capabilities: [40] Power Management version 2
01:00.0 VGA compatible controller: S3 Inc. Savage 4 (rev 02) (prog-if 00 [VGA])
Subsystem: Number 9 Computer Company SR9 8Mb SDRAM
Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 9
Memory at f7f80000 (32-bit, non-prefetchable) [size=512K]
Memory at e8000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at f0000000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 1
Capabilities: [80] AGP version 2.0
PCI ID here:
00:00.0 Class 0600: 8086:7190 (rev 03)
00:01.0 Class 0604: 8086:7191 (rev 03)
00:02.0 Class 0200: 8086:1229 (rev 05)
00:03.0 Class 0100: 9004:7895 (rev 04)
00:03.1 Class 0100: 9004:7895 (rev 04)
00:04.0 Class 0601: 8086:7110 (rev 02)
00:04.1 Class 0101: 8086:7111 (rev 01)
00:04.2 Class 0c03: 8086:7112 (rev 01)
00:04.3 Class 0680: 8086:7113 (rev 02)
00:0d.0 Class 0200: 10b7:9200 (rev 74)
00:0e.0 Class 0780: 12b9:1006
01:00.0 Class 0300: 5333:8a22 (rev 02)
I don't think the Savage4 has drivers, but the VBE 2.0 drivers should work.
If it's a physical AGP card, I'd look for a Matrox G200 or G400, or an ATI Xpert @ Work/Play card, either with 32MB VRAM.
Looks like a nice box - I remember being thoroughly impressed with the performance of a 500-600MHz PIII, and that 10K RPM drive should really make it fly!
Quote from: "itomato"I don't think the Savage4 has drivers, but the VBE 2.0 drivers should work.
If it's a physical AGP card, I'd look for a Matrox G200 or G400, or an ATI Xpert @ Work/Play card, either with 32MB VRAM.
Looks like a nice box - I remember being thoroughly impressed with the performance of a 500-600MHz PIII, and that 10K RPM drive should really make it fly!
I fooled around with an 120GB (but using only 8GB) IDE hard drive (HD as primary master with the CD-ROM as primary slave) but got stuck on that dreaded "cannot mount root" panic. I had used EIDE and ATAPI device controller (v4.01) for CD-ROM and PIIX for the HD.
You shouldn't have any problems with this chipset. Try the "Primary and secondary EIDE controller" (or whatever the name was) for both devices. You might have problems with the optical drive - use a CD-ROM drive (not a writer, DVD or combo) - the oldest one you can find.
Quote from: "iDork"You shouldn't have any problems with this chipset. Try the "Primary and secondary EIDE controller" (or whatever the name was) for both devices. You might have problems with the optical drive - use a CD-ROM drive (not a writer, DVD or combo) - the oldest one you can find.
Hah... the PIIX driver didn't get copied to the hard disk during install due to a bug on the rc.cdrom of the OPENSTEP USER CD. Had to do the install using Laurent Julliard's custom device floppy disk and trick. OS4.2 is now running perfectly on a 2GB partition from the 120GB disk.
Now with a running system, I checked /private/adm/messages and saw that the actual value seen by OS4.2 was:
"0x78959004/0x78959004" (two values due to being dual SCSI controller)
Adaptec AIC-7895 successfully detected but partially working. OS4.2 detects the controller and SCSI hard disk but is incapable of initializing the disk. Installation did not succeed because it complains that it did not find a hard drive to install the OS.
"OPENSTEP cannot be installed on any disks.
You must have a 512 byte/sector disk with at least 120MB of free space.
No disks found."
Waiting for my new PCI cards to arrive, Adaptec AHA-2940UW and Matrox Millenium II PCI 8MB, in order to continue doing some tests.
Cards arrived.
Replaced my S3 Savage4 AGP video card with the Matrox Millenium II PCI 8MB and installed the Adaptec AHA-2940UW PCI card (and disabled the onboard AIC-7895 SCSI controller).
Installing OS4.2 failed with the following message:
"OPENSTEP cannot be installed on any disks.
You must have a 512 byte/sector disk with at least 120MB of free space.
No disks found."
Same problem as above with the on-board SCSI controller. Deduction: the hard drive is fine, it must be something else because AHA-2940UW is very well supported.
After much searching and testing, the solution to this problem was:
1) When asked for CD-ROM driver, install the 2940UW driver.
2) When asked for the hard drive driver, install the IDE/ATAPI driver.
This allows /dev/sd0 to go to the hard drive and /dev/sd1 to the CD-ROM. I believe that /dev/sd0 is reserved only to the boot drive. Another possibility is that the installer is hard-wired to install on /dev/sd0 and nothing else. When the CD-ROM takes /dev/sd0, the installer reads that as a hard drive with 0 space left.
Everything installed normally.
Now back to making the on-board AIC-7895 controller work.
Took a small break from SCSI-land...
I wanted better video resolution so I decided to get the video card to work. I used Mirko's 0.93 Matrox MGA driver and set the resolution to 1280x1024x16 (32 bit color didn't work) and at first it didn't work. I had to remove the SVGA Default driver which was creating conflicts.
Now I have beautiful large and colorful working space!
Next Up: Adaptec AIC-7895 SCSI on-board controller
I re-tried installing OS4.2 from the internal AIC-7895 controller using the 78XX driver reversing the order of drivers (78XX first, then IDE/ATAPI second) and it detected the SCSI hard disk and installed the first part without problems *BUT* upon rebooting it failed...
WHY? Because when it rebooted, it did not have the 78XX driver to load first, so it loaded the IDE/ATAPI driver (which gave /dev/sd0 to the CD-ROM) and then asked for the floppy disk with the 78XX driver... of course that gave /dev/sd1 to the hard disk and generated a system panic (usually happens when changing rootdev).
THE PROPOSED SOLUTION:
Use Laurent Julliard's installation method (boot into single user mode before installation begins) to run a custom rc.cdrom script with a section which copies the 78XX driver into the new system prior to rebooting. The idea being that with the 78XX driver already installed, it will be loaded before the IDE/ATAPI driver thus giving the SCSI hard drive the /dev/sd0.
THE FINAL VERDICT:
It works as predicted! Just for fun I decided to use PIIX driver for CD-ROM but that generated an IRQ conflict. PIIX uses IRQ 14/15 for both channel (dual) and IRQ 15 is needed for my SCSI controller. So I had to use the normal IDE/ATAPI driver which is single channel, thus only uses IRQ 14.
I now have a method to install OS4.2 directly into my SCSI drive from the on-board Adaptec AIC-7895 (dual channel) controller. In other words, this controller is compatible and works just fine!
I might edit System.config and make sure the IDE/ATAPI is loaded last, especially when adding/removing drivers using Configure.app.
Next Up: on-board sound