SAS card for G5Quad

[LightBulbFun]

what does the device look like in the PCI section of system profiler?

previously it was clearly just being presented as a generic PCI device, with no FCode ROM loaded

is it still like that or is the name now more formatted indicating that an FCode ROM has been loaded by OpenFirmware and device tree properties populated?

 

[Tratkazir_the_1st]

Guys, if you wait some days - may be I'll return to operational state (seems I've caught a cold if not worse). Got about 3-4 cards for different buses, which I need to check for firmware versions. "Stay tuned" .

 

[flyproductions]

Guys, if you wait some days - may be I'll return to operational state (seems I've caught a cold if not worse). Got about 3-4 cards for different buses, which I need to check for firmware versions. "Stay tuned" .

Nice!

Get well soon!

 

[flyproductions]

what does the device look like in the PCI section of system profiler?

previously it was clearly just being presented as a generic PCI device, with no FCode ROM loaded

No, this was some other card. In post #46 i showed the System Info appearance. It shows up as what it basically is: A SAS-card. In addition i now, as the Fcode has been flashed to it, get the "Fcode 1.00.49" after the firmware version in the "Revision"-line.

 

[Amethyst1]

So assuming we have the right SAS drives( 250MB/s peak capable single SAS drives if they exist? ) connected in RAID 0 4 drive array then we should be able to reach somewhere near the Max theoretical peak throughput with this controller in a 2005 G5 with PCI-E x4 connections?

Forget this controller. This is the solution which allows the Quad to shine.

 

[Tratkazir_the_1st]

Got LSI3081E-R . (Pics later).
What lsiutil tells us about firmware:
root@devuan-storm:~# lsiutil

LSI Logic MPT Configuration Utility, Version 1.56, March 19, 2008

1 MPT Port found

Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC
1. /proc/mpt/ioc0 LSI Logic SAS1068E B3 105 011c0200 0

Select a device: [1-1 or 0 to quit] 1

1. Identify firmware, BIOS, and/or FCode
2. Download firmware (update the FLASH)
4. Download/erase BIOS and/or FCode (update the FLASH)
8. Scan for devices
10. Change IOC settings (interrupt coalescing)
13. Change SAS IO Unit settings
16. Display attached devices
20. Diagnostics
21. RAID actions
22. Reset bus
23. Reset target
42. Display operating system names for devices
45. Concatenate SAS firmware and NVDATA files
60. Show non-default settings
61. Restore default settings
69. Show board manufacturing information
97. Reset SAS link, HARD RESET
98. Reset SAS link
99. Reset port
e Enable expert mode in menus
p Enable paged mode
w Enable logging

Main menu, select an option: [1-99 or e/p/w or 0 to quit] 1

Current active firmware version is 011c0200 (1.28.02)
Firmware image's version is MPTFW-01.28.02.00-IE
LSI Logic
x86 BIOS image's version is MPTBIOS-6.28.00.00 (2009.02.03)
FCode image's version is MPT SAS FCode Version 1.00.49 (2007.09.21)

This card has 2 SFF-8087 connectors.

 

[Tratkazir_the_1st]

Card itself.

 

[Tratkazir_the_1st]

In Mac Os:

 

[Tratkazir_the_1st]

I want to know, how to transfer required drivers to Tiger? Only Tiger Server supports this cards...

 

[Amethyst1]

I want to know, how to transfer required drivers to Tiger? Only Tiger Server supports this cards...

Is copying AppleLSIFusionMPT.kext from Tiger Server not enough? You can probably extract it from the 10.4.11 Server Combo updater if you don’t have a Tiger Server installation.

 

[Tratkazir_the_1st]

Is copying AppleLSIFusionMPT.kext from Tiger Server not enough?

I'll try, but last time when I attempted to do something like this didn't take any desired effect.

(BTW, just installed Debian from latest snapshot - installation to GPT-partitioned drive was just straight forward, even GRUB installed correctly & everything is bootable from OS picker).

 

[flyproductions]

@Tratkazir_the_1st Did you get the chance to dump the ROM from that other card? 😉

Still curious if i can get it to boot, even having found some much advanced option inbetween.

 

[flyproductions]

Card itself.

By the way: Shouldn't this be eight lanes? Looks like.

..or is it just used on a x4 slot?

 

[Tratkazir_the_1st]

It is in second (from upper) slot, I don't remember is it 4x lanes or 8x. About ROM dump - I think it's easier to get latest versions from Broadcom site (they sits well in Mac, don't have any free system to drop in for rom dumping now, sorry). Ah, I'll just drop here what I've got already, if it's technically possible.

 

[Tratkazir_the_1st]

@Amethyst1
Just checked about AppleLSIFusionMPT.kext. Tiger (desktop edition) don't load it... So where I can ask about converting Tiger Server to Tiger Desktop? (Drive checked, Permissions repaired.)

 

[Amethyst1]

So where I can ask about converting Tiger Server to Tiger Desktop? (Drive checked, Permissions repaired.)

I’d just install Tiger Server and not enable any services.

 

[Tratkazir_the_1st]

I’d just install Tiger Server and not enable any services.

Classic not works... (Error -1 at statup)

 

[flyproductions]

It is in second (from upper) slot, I don't remember is it 4x lanes or 8x. About ROM dump - I think it's easier to get latest versions from Broadcom site (they sits well in Mac, don't have any free system to drop in for rom dumping now, sorry). Ah, I'll just drop here what I've got already, if it's technically possible.

Thanks, but these packages i allready had. They don't even contain the fCode-part, which seems to be the most important for PPC-booting. My card now is flashed with some fCode. But it doesn't seem to exactly match. Because, even beeing recognized by System Profiler, it refuses to boot. So there has to be some particular thing in your card's BIOS, which makes it boot. Pitty you don't have no system for dumpig at the moment. 😕

 

[Amethyst1]

Classic not works... (Error -1 at statup)

I see. OK, if you’re feeling adventurous: copy mach_kernel and all kexts from Tiger Server to the client edition and see what happens.

 

[Tratkazir_the_1st]

copy mach_kernel and all kexts from Tiger Server to the client edition

Something makes me to think - it will die .

 

[Amethyst1]

Something makes me to think - it will die .

Will it die
Or merely cry
You won’t know
Until you try

 

[Tratkazir_the_1st]

So, got some HW for tests (not PCI-X cards as for now). Pics - 2 PCI-Ex cards + 1 Intel module, already reflashed to latest version I've got + boot-rom codes. Lsiutil output for all of them:

Spoiler: lsiutil output

root@quadrant-devuan:~# lsiutil

LSI Logic MPT Configuration Utility, Version 1.56, March 19, 2008

3 MPT Ports found

Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC
1. /proc/mpt/ioc0 LSI Logic SAS1068E B3 105 011c0200 0
2. /proc/mpt/ioc1 LSI Logic SAS1064E B3 105 01210000 0
3. /proc/mpt/ioc2 LSI Logic SAS1064E B3 105 01210000 0

Select a device: [1-3 or 0 to quit] 1

1. Identify firmware, BIOS, and/or FCode
2. Download firmware (update the FLASH)
4. Download/erase BIOS and/or FCode (update the FLASH)
8. Scan for devices
10. Change IOC settings (interrupt coalescing)
13. Change SAS IO Unit settings
16. Display attached devices
20. Diagnostics
21. RAID actions
22. Reset bus
23. Reset target
42. Display operating system names for devices
45. Concatenate SAS firmware and NVDATA files
60. Show non-default settings
61. Restore default settings
69. Show board manufacturing information
97. Reset SAS link, HARD RESET
98. Reset SAS link
99. Reset port
e Enable expert mode in menus
p Enable paged mode
w Enable logging

Main menu, select an option: [1-99 or e/p/w or 0 to quit] 1

Current active firmware version is 011c0200 (1.28.02)
Firmware image's version is MPTFW-01.28.02.00-IE
LSI Logic
x86 BIOS image's version is MPTBIOS-6.28.00.00 (2009.02.03)
FCode image's version is MPT SAS FCode Version 1.00.49 (2007.09.21)

Main menu, select an option: [1-99 or e/p/w or 0 to quit] 0

Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC
1. /proc/mpt/ioc0 LSI Logic SAS1068E B3 105 011c0200 0
2. /proc/mpt/ioc1 LSI Logic SAS1064E B3 105 01210000 0
3. /proc/mpt/ioc2 LSI Logic SAS1064E B3 105 01210000 0

Select a device: [1-3 or 0 to quit] 2

1. Identify firmware, BIOS, and/or FCode
2. Download firmware (update the FLASH)
4. Download/erase BIOS and/or FCode (update the FLASH)
8. Scan for devices
10. Change IOC settings (interrupt coalescing)
13. Change SAS IO Unit settings
16. Display attached devices
20. Diagnostics
21. RAID actions
22. Reset bus
23. Reset target
42. Display operating system names for devices
45. Concatenate SAS firmware and NVDATA files
60. Show non-default settings
61. Restore default settings
69. Show board manufacturing information
97. Reset SAS link, HARD RESET
98. Reset SAS link
99. Reset port
e Enable expert mode in menus
p Enable paged mode
w Enable logging

Main menu, select an option: [1-99 or e/p/w or 0 to quit] 1

Current active firmware version is 01210000 (1.33.00)
Firmware image's version is MPTFW-01.33.00.00-IT
LSI Logic
x86 BIOS image's version is MPTBIOS-6.36.00.00 (2011.08.24)
EFI BIOS image's version is 3.22.00.00

Main menu, select an option: [1-99 or e/p/w or 0 to quit] 0

Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC
1. /proc/mpt/ioc0 LSI Logic SAS1068E B3 105 011c0200 0
2. /proc/mpt/ioc1 LSI Logic SAS1064E B3 105 01210000 0
3. /proc/mpt/ioc2 LSI Logic SAS1064E B3 105 01210000 0

Select a device: [1-3 or 0 to quit] 3

1. Identify firmware, BIOS, and/or FCode
2. Download firmware (update the FLASH)
4. Download/erase BIOS and/or FCode (update the FLASH)
8. Scan for devices
10. Change IOC settings (interrupt coalescing)
13. Change SAS IO Unit settings
16. Display attached devices
20. Diagnostics
21. RAID actions
22. Reset bus
23. Reset target
42. Display operating system names for devices
45. Concatenate SAS firmware and NVDATA files
60. Show non-default settings
61. Restore default settings
69. Show board manufacturing information
97. Reset SAS link, HARD RESET
98. Reset SAS link
99. Reset port
e Enable expert mode in menus
p Enable paged mode
w Enable logging

Main menu, select an option: [1-99 or e/p/w or 0 to quit] 1

Current active firmware version is 01210000 (1.33.00)
Firmware image's version is MPTFW-01.33.00.00-IT
LSI Logic
x86 BIOS image's version is MPTBIOS-6.36.00.00 (2011.08.24)
EFI BIOS image's version is 3.22.00.00
FCode image's version is MPT SAS FCode Version 1.00.49 (2007.09.21)

Main menu, select an option: [1-99 or e/p/w or 0 to quit] 0

What I need to do for firmware extraction?

 

[LightBulbFun]

Thanks, but these packages i allready had. They don't even contain the fCode-part, which seems to be the most important for PPC-booting. My card now is flashed with some fCode. But it doesn't seem to exactly match. Because, even beeing recognized by System Profiler, it refuses to boot. So there has to be some particular thing in your card's BIOS, which makes it boot. Pitty you don't have no system for dumpig at the moment. 😕

have you tried imaging OS X to a drive connecting it to said SAS card, removing all other bootable devices and manually booting from OpenFirmware?

if theres an fCode Option ROM, check that its properly loaded in OpenFirmware with a dev / ls and see if everything shows up in the device tree

then just manually type it out and boot from it

I have seen plenty of cases where a device is bootable, but wont show up in the boot picker or start up disk

classic example of this is USB booting, easily done, but not exposed to the user in a friendly manner

 

[flyproductions]

What I need to do for firmware extraction?

There are two files which can be dumped (or have to be flashed) from/to the card. One is the firmware, extension .fw, which seems to have nothing to do with Mac booting. The other is the bios, containing the fCode, extension is .rom. This one is the needed.

You can use the attached flasher "sas-flas". Command to dump is as simple as it gets:

sasflash -ubios (filename).rom

 

[flyproductions]

have you tried imaging OS X to a drive connecting it to said SAS card, removing all other bootable devices and manually booting from OpenFirmware?

if theres an fCode Option ROM, check that its properly loaded in OpenFirmware with a dev / ls and see if everything shows up in the device tree

then just manually type it out and boot from it

I have seen plenty of cases where a device is bootable, but wont show up in the boot picker or start up disk

classic example of this is USB booting, easily done, but not exposed to the user in a friendly manner

You are right. But as far as i get it @Tratkazir_the_1st did none of all that and it just booted. So i would like to first compare his fCode-ROM to the one i'm using, before sinking my hands into the poor Quad's guts again.

Also i 'm curious if this card would be able to boot of opticals...which even the bootable Firmtek-Seritek cards can not! At least the one i flashed with one of these ROMs, which booted fine of HDs/SSDs, refused to boot of the DVD.