Re: Ultra320 drivers?
Actually no- they're not, yet. Sorry for the false positive. I also managed to kill your system :-( On Fri, 6 Sep 2002, Matthew Jacob wrote: Things are looking a bit better- I have your system at a comfortable clip with multiple tasks. I'll leave some tests over the weekend, but I think I nailed it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ultra320 drivers?
Matthew Jacob wrote: That's damned odd. Can you get into the configuration menu and make sure it has 'large BIOS' or whatever the LSI term is enabled? The Dell BIOS, or the LSI config menu? I don't think either has a LSI Config - ^C. OK, I'm in the LSI config screen, and here's what I have in the first screen: LSI Logic MPT SCSI Setup UtilityVersion MPTBIOS-5.02.00 Boot Adapter List Global Properties LSI Logic Host Bus Adapters Adapter PCI Dev/PortIRQ NVM BootLSI Logic Bus FuncNumber Order Control LSI1030 3 60 DC0011 Yes 1 Disabled LSI1030 3 61 D80011 Yes 0 Enabled I disabled one of them, since the drives hang off the other one and this shaves a few seconds off reboot times. Under Boot Adapter List, the only things I can change are the boot order and the status (enabled/disabled) of the two adaptors. Under Global Properties, I have: Pause When Boot Alert Displayed [No] Boot Information Display Mode [Verbose] Negotiate with devies [Supported] Video Mode [Color] Support Interrupt [Hook interrupt, the Default] Under the enabled device LSI1030 3 61, I have: Adapter Properties Adapter PCI Dev/ Bus Func LSI1030 3 61 Device Properties Host SCSI ID[ 7] SCSI Bus Scan Order [Low to High (0..Max)] Removable Media Support [None] CHS Mapping [SCSI Plug and Play Mapping] Spinup Delay (Secs) [ 2] Secondary Cluster Server[No] Termination Control [Auto] Under Device Properties, it shows some details about the connected drives and let me force them to a lower speed, etc. The only thing that comes close to large BIOS would be the CHS Mapping, but either setting (SCSI Plug and Play Mapping or Alternate CHS Mapping) doesn't boot. Or am I looking at the wrong thing? Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: Ultra320 drivers?
I was thinking that the CHS mapping had changed from your original settings when you loaded new f/w. On Sat, 31 Aug 2002, Lars Eggert wrote: Matthew Jacob wrote: That's damned odd. Can you get into the configuration menu and make sure it has 'large BIOS' or whatever the LSI term is enabled? The Dell BIOS, or the LSI config menu? I don't think either has a LSI Config - ^C. OK, I'm in the LSI config screen, and here's what I have in the first screen: LSI Logic MPT SCSI Setup Utility Version MPTBIOS-5.02.00 Boot Adapter List Global Properties LSI Logic Host Bus Adapters Adapter PCI Dev/PortIRQ NVM BootLSI Logic Bus FuncNumber Order Control LSI1030 3 60 DC0011 Yes 1 Disabled LSI1030 3 61 D80011 Yes 0 Enabled I disabled one of them, since the drives hang off the other one and this shaves a few seconds off reboot times. Under Boot Adapter List, the only things I can change are the boot order and the status (enabled/disabled) of the two adaptors. Under Global Properties, I have: Pause When Boot Alert Displayed [No] Boot Information Display Mode [Verbose] Negotiate with devies [Supported] Video Mode [Color] Support Interrupt [Hook interrupt, the Default] Under the enabled device LSI1030 3 61, I have: Adapter Properties Adapter PCI Dev/ Bus Func LSI1030 3 61 Device Properties Host SCSI ID[ 7] SCSI Bus Scan Order [Low to High (0..Max)] Removable Media Support [None] CHS Mapping [SCSI Plug and Play Mapping] Spinup Delay (Secs) [ 2] Secondary Cluster Server[No] Termination Control [Auto] Under Device Properties, it shows some details about the connected drives and let me force them to a lower speed, etc. The only thing that comes close to large BIOS would be the CHS Mapping, but either setting (SCSI Plug and Play Mapping or Alternate CHS Mapping) doesn't boot. Or am I looking at the wrong thing? Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ultra320 drivers?
Matthew Jacob wrote: I was thinking that the CHS mapping had changed from your original settings when you loaded new f/w. Good and bad news: Good: Found the boot problem. Turns out that I moved BIOS boot devices before the SCSI drives in the BIOS, to boot of the LSI firmware floppy. That made an ATA drive the first drive to be probed. Even though I cycled through the boot loader chain to the right (SCSI) disk, it then wouldn't boot. I moved the SCSI drives before the BIOS devices again, and now it boots fine. (Still strange, since all drives have the 4.6 boot loader installed, but anyway, it boots again.) Bad: I still get timeouts with the 1.00.12 firmware. And, unlike before, my drives only attach at 80MB/s - and this is with the patch to scsi_all.c that I initially forgot yesterday. At boot time, the 1.00.12 firmware detects my drives as 80MB/s but posts a note along the lines of these drives will support 320MB/s once the OS is loaded. The older version detected them as 320MB/s at boot, and so did FreeBSD. Windows XP with the 1.00.12 firmware, on the other hand, runs the drives at 320MB/s (according to the LSI utility). mpt0: LSILogic 1030 Ultra4 Adapter port 0xdc00-0xdcff mem 0xff6a-0xff6b,0xff6c-0xff6d irq 18 at device 12.0 on pci3 mpt1: LSILogic 1030 Ultra4 Adapter port 0xd800-0xd8ff mem 0xff66-0xff67,0xff68-0xff69 irq 19 at device 12.1 on pci3 ... da0 at mpt1 bus 0 target 0 lun 0 da0: SEAGATE ST336732LW 2223 Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) da1 at mpt1 bus 0 target 1 lun 0 da1: SEAGATE ST336732LW 2223 Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: Ultra320 drivers?
Peter Wemm wrote: Lars Eggert wrote: We just got a bunch of Dell machines that have this controller as well. Any news about support in sym? No, you want the 'mpt' driver that Matt Jacob recently committed. The 1030 has nothing in common with sym. I backported the mpt driver from -STABLE to 4.6-RELEASE, and it is recognized correctly: mpt0: LSILogic 1030 Ultra4 Adapter port 0xdc00-0xdcff mem 0xff6a-0xff6b,0xff6c-0xff6d irq 18 at device 12.0 on pci3 mpt1: LSILogic 1030 Ultra4 Adapter port 0xd800-0xd8ff mem 0xff66-0xff67,0xff68-0xff69 irq 19 at device 12.1 on pci3 However, my drives aren't attached as Ultra-320 but at much lower speeds: da0 at mpt1 bus 0 target 0 lun 0 da0: SEAGATE ST336732LW 2223 Fixed Direct Access SCSI-3 device da0: 62.500MB/s transfers (31.250MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) da1 at mpt1 bus 0 target 1 lun 0 da1: SEAGATE ST336732LW 2223 Fixed Direct Access SCSI-3 device da1: 62.500MB/s transfers (31.250MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) When I hook them up to the Ultra-160 onboard Adaptec chip, things look better: ahc0: Adaptec aic7892 Ultra160 SCSI adapter port 0xd400-0xd4ff mem 0xff6fe000-0xff6fefff irq 14 at device 14.0 on pci3 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ... da0 at ahc0 bus 0 target 0 lun 0 da0: SEAGATE ST336732LW 2223 Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) da1 at ahc0 bus 0 target 1 lun 0 da1: SEAGATE ST336732LW 2223 Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) Any ideas on how to make mpt use Ultra-320 to talk to the drives? Thanks, Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: Ultra320 drivers?
On Fri, Aug 30, 2002 at 12:11:12 -0700, Lars Eggert wrote: Peter Wemm wrote: Lars Eggert wrote: We just got a bunch of Dell machines that have this controller as well. Any news about support in sym? No, you want the 'mpt' driver that Matt Jacob recently committed. The 1030 has nothing in common with sym. I backported the mpt driver from -STABLE to 4.6-RELEASE, and it is recognized correctly: mpt0: LSILogic 1030 Ultra4 Adapter port 0xdc00-0xdcff mem 0xff6a-0xff6b,0xff6c-0xff6d irq 18 at device 12.0 on pci3 mpt1: LSILogic 1030 Ultra4 Adapter port 0xd800-0xd8ff mem 0xff66-0xff67,0xff68-0xff69 irq 19 at device 12.1 on pci3 However, my drives aren't attached as Ultra-320 but at much lower speeds: da0 at mpt1 bus 0 target 0 lun 0 da0: SEAGATE ST336732LW 2223 Fixed Direct Access SCSI-3 device da0: 62.500MB/s transfers (31.250MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) da1 at mpt1 bus 0 target 1 lun 0 da1: SEAGATE ST336732LW 2223 Fixed Direct Access SCSI-3 device da1: 62.500MB/s transfers (31.250MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) When I hook them up to the Ultra-160 onboard Adaptec chip, things look better: ahc0: Adaptec aic7892 Ultra160 SCSI adapter port 0xd400-0xd4ff mem 0xff6fe000-0xff6fefff irq 14 at device 14.0 on pci3 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ... da0 at ahc0 bus 0 target 0 lun 0 da0: SEAGATE ST336732LW 2223 Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) da1 at ahc0 bus 0 target 1 lun 0 da1: SEAGATE ST336732LW 2223 Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) Any ideas on how to make mpt use Ultra-320 to talk to the drives? Did you also backport rev 1.35 and 1.36 of scsi_all.c? You may need that as well. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ultra320 drivers?
On Fri, Aug 30, 2002 at 12:50:14 -0700, Lars Eggert wrote: Kenneth D. Merry wrote: Did you also backport rev 1.35 and 1.36 of scsi_all.c? You may need that as well. Good catch, I missed that file. After applying that patch, they now seem to be detected correctly: da0 at mpt1 bus 0 target 0 lun 0 da0: SEAGATE ST336732LW 2223 Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) da1 at mpt1 bus 0 target 1 lun 0 da1: SEAGATE ST336732LW 2223 Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) The bad news is that any kind of extended disk activity (e.g. kernel building), results in a ton of unhealthy messages like this: mpt1: time out on request index = 0xe4 sequence = 0x0cad mpt1: Status 0001; Mask 0001; Doorbell 2400 request state On Chip SCSI IO Request @ 0xff807f34 Chain Offset 0x00 MsgFlags 0x00 MsgContext0x00e4 Bus:0 TargetID1 SenseBufferLength 32 LUN: 0x0 Control 0x0100 WRITE SIMPLEQ DataLength0x4000 SenseBufAddr 0x0005d9e0 CDB[0:10] 2a 00 01 3f e1 9f 00 00 20 00 SE32 0xdc3c2830: Addr=0xd0f3000 FlagsLength=0x14001000 HOST_TO_IOC SE32 0xdc3c2838: Addr=0xd034000 FlagsLength=0x14002000 HOST_TO_IOC SE32 0xdc3c2840: Addr=0xd136000 FlagsLength=0xd5001000 HOST_TO_IOC LAST_ELEMENT END_OF_BUFFER END_OF_LIST mpt1: mpt_done: corrupted ccb, index = 0xe4 seq = 0x0cad request state Timeout mpt_request: SCSI IO Request @ 0xff807e88 Chain Offset 0x00 MsgFlags 0x00 MsgContext0x00e4 Bus:0 TargetID1 SenseBufferLength 32 LUN: 0x0 Control 0x0100 WRITE SIMPLEQ DataLength0x4000 SenseBufAddr 0x0005d9e0 CDB[0:10] 2a 00 01 3f e1 9f 00 00 20 00 SE32 0xdc3c2830: Addr=0xd0f3000 FlagsLength=0x14001000 HOST_TO_IOC SE32 0xdc3c2838: Addr=0xd034000 FlagsLength=0x14002000 HOST_TO_IOC SE32 0xdc3c2840: Addr=0xd136000 FlagsLength=0xd5001000 HOST_TO_IOC LAST_ELEMENT END_OF_BUFFER END_OF_LIST mpt_done: context reply: 0x00e4 Did I miss any more pieces? Nothing under sys/cam seemed recent enough. I don't think there are any other missing pieces. Does this work under a stock version of -stable? That could help you figure out whether this is a problem with your backport. Make sure you get an up-to-date -stable, including version 1.14.2.8 of scsi_all.c. You might also want to talk to Matt Jacob [EMAIL PROTECTED] and see if he can help you out. (dunno if he reads -hackers, thus the reason you might want to send mail directly) Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ultra320 drivers?
[ cc list trimmed ] [ I guess I got unsubscribed from hackers, so I missed the front end of this. Every time I try and sort out majordomo at FreeBSD, it fails for me (like trying ask what am I subscribed to) and all requests to postmaster seem to bitbucket. Oh well. ] This isn't good. Part of it just the chip later presenting the completion for a command that I had already timed out. But basically, we never got a response to a command, so we timed it out. Later, the chip presented us with the comamnd as being done- and being done with no errors (hence the 'context reply'). Can you say if there was a perceptible period of time between the first and second barfings? -matt The bad news is that any kind of extended disk activity (e.g. kernel building), results in a ton of unhealthy messages like this: mpt1: time out on request index = 0xe4 sequence = 0x0cad mpt1: Status 0001; Mask 0001; Doorbell 2400 request state On Chip SCSI IO Request @ 0xff807f34 Chain Offset 0x00 MsgFlags 0x00 MsgContext0x00e4 Bus:0 TargetID1 SenseBufferLength 32 LUN: 0x0 Control 0x0100 WRITE SIMPLEQ DataLength 0x4000 SenseBufAddr0x0005d9e0 CDB[0:10] 2a 00 01 3f e1 9f 00 00 20 00 SE32 0xdc3c2830: Addr=0xd0f3000 FlagsLength=0x14001000 HOST_TO_IOC SE32 0xdc3c2838: Addr=0xd034000 FlagsLength=0x14002000 HOST_TO_IOC SE32 0xdc3c2840: Addr=0xd136000 FlagsLength=0xd5001000 HOST_TO_IOC LAST_ELEMENT END_OF_BUFFER END_OF_LIST mpt1: mpt_done: corrupted ccb, index = 0xe4 seq = 0x0cad request state Timeout mpt_request: SCSI IO Request @ 0xff807e88 Chain Offset 0x00 MsgFlags 0x00 MsgContext0x00e4 Bus:0 TargetID1 SenseBufferLength 32 LUN: 0x0 Control 0x0100 WRITE SIMPLEQ DataLength 0x4000 SenseBufAddr0x0005d9e0 CDB[0:10] 2a 00 01 3f e1 9f 00 00 20 00 SE32 0xdc3c2830: Addr=0xd0f3000 FlagsLength=0x14001000 HOST_TO_IOC SE32 0xdc3c2838: Addr=0xd034000 FlagsLength=0x14002000 HOST_TO_IOC SE32 0xdc3c2840: Addr=0xd136000 FlagsLength=0xd5001000 HOST_TO_IOC LAST_ELEMENT END_OF_BUFFER END_OF_LIST mpt_done: context reply: 0x00e4 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ultra320 drivers?
Oh, yes- let me know if you've upgraded to the latest LSI 53c1030 f/w (that'd 1.0.12). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ultra320 drivers?
Matthew, Matthew Jacob wrote: This isn't good. Part of it just the chip later presenting the completion for a command that I had already timed out. But basically, we never got a response to a command, so we timed it out. Later, the chip presented us with the comamnd as being done- and being done with no errors (hence the 'context reply'). Can you say if there was a perceptible period of time between the first and second barfings? there is a longish (30 seconds?) pause before the first message, then I get them all in one swoop. E.g. I type make buildworld, make seems to hang, and then I get these messages 30 seconds later. Oh, yes- let me know if you've upgraded to the latest LSI 53c1030 f/w (that'd 1.0.12). No, I was running a Dell-branded 1.0.0. I grabbed the update from LSI and installed it, but now none of my partitions likes to boot anymore (FreeBSD and Windows XP). Also, the LSI firmware prompt used to show all drives as Ultra-320, now it shows them as Ultra-80 with a note saying should support Ultra-320 when the OS is loaded. Is this to be expected, i.e. do I need to reinstall everything with the new firmware? I'm trying to find the original Dell-branded firmware somewhere, but so far, no luck. Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: Ultra320 drivers?
On Fri, 30 Aug 2002, Lars Eggert wrote: Matthew, Matthew Jacob wrote: This isn't good. Part of it just the chip later presenting the completion for a command that I had already timed out. But basically, we never got a response to a command, so we timed it out. Later, the chip presented us with the comamnd as being done- and being done with no errors (hence the 'context reply'). Can you say if there was a perceptible period of time between the first and second barfings? there is a longish (30 seconds?) pause before the first message, then I get them all in one swoop. E.g. I type make buildworld, make seems to hang, and then I get these messages 30 seconds later. In some sense this sounds like an interrupt issue. The timeout is 30 seconds, and it looks like we give up on the command but it's done instantaneously afterwards. Oh, yes- let me know if you've upgraded to the latest LSI 53c1030 f/w (that'd 1.0.12). No, I was running a Dell-branded 1.0.0. I grabbed the update from LSI and installed it, but now none of my partitions likes to boot anymore (FreeBSD and Windows XP). Also, the LSI firmware prompt used to show all drives as Ultra-320, now it shows them as Ultra-80 with a note saying should support Ultra-320 when the OS is loaded. Is this to be expected, i.e. do I need to reinstall everything with the new firmware? *sputter* That's damned odd. Can you get into the configuration menu and make sure it has 'large BIOS' or whatever the LSI term is enabled? I'm trying to find the original Dell-branded firmware somewhere, but so far, no luck. *groan* I might have an image somewhere around... hang on... check my directory on hub- there's 1.0.6 there... -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ultra320 drivers?
Matthew Jacob wrote: In some sense this sounds like an interrupt issue. The timeout is 30 seconds, and it looks like we give up on the command but it's done instantaneously afterwards. Hm. I don't know much about the PCI code, so maybe what follows won't make any sense and may not be related: The card is PCI64, and there's an unknown device in the dmesg that is an Intel 82806AA I/O APIC Device according to its device ID. Would that matter at all? No, I was running a Dell-branded 1.0.0. I grabbed the update from LSI and installed it, but now none of my partitions likes to boot anymore (FreeBSD and Windows XP). Also, the LSI firmware prompt used to show all drives as Ultra-320, now it shows them as Ultra-80 with a note saying should support Ultra-320 when the OS is loaded. Is this to be expected, i.e. do I need to reinstall everything with the new firmware? *sputter* That's damned odd. Can you get into the configuration menu and make sure it has 'large BIOS' or whatever the LSI term is enabled? The Dell BIOS, or the LSI config menu? I don't think either has a setting that sounds similar, but I'll double-check tomorrow. I'm trying to find the original Dell-branded firmware somewhere, but so far, no luck. *groan* I might have an image somewhere around... hang on... check my directory on hub- there's 1.0.6 there... That'd be great. I also emailed Dell and LSI. Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: Ultra320 drivers?
Peter Wemm wrote: Jonathan Lemon wrote: I have an IBM box that has a dual LSI 53c1030 controller on the motherboard. Our SYM driver doesn't appear to have support for this device; under Linux it is supported by a Fusion/MPT driver from LSI. Any chance of getting a driver for this chip? I have an IA64 box with a 1030 as well. :-/ We just got a bunch of Dell machines that have this controller as well. Any news about support in sym? Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: Ultra320 drivers?
Lars Eggert wrote: This is a cryptographically signed message in MIME format. Peter Wemm wrote: Jonathan Lemon wrote: I have an IBM box that has a dual LSI 53c1030 controller on the motherboard. Our SYM driver doesn't appear to have support for this device; under Linux it is supported by a Fusion/MPT driver from LSI. Any chance of getting a driver for this chip? I have an IA64 box with a 1030 as well. :-/ We just got a bunch of Dell machines that have this controller as well. Any news about support in sym? No, you want the 'mpt' driver that Matt Jacob recently committed. The 1030 has nothing in common with sym. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Ultra320 drivers?
Peter Wemm wrote: Lars Eggert wrote: We just got a bunch of Dell machines that have this controller as well. Any news about support in sym? No, you want the 'mpt' driver that Matt Jacob recently committed. The 1030 has nothing in common with sym. I just saw the message on cvs-all :-) Thanks, Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: Ultra320 drivers?
Jonathan Lemon wrote: I have an IBM box that has a dual LSI 53c1030 controller on the motherboard. Our SYM driver doesn't appear to have support for this device; under Linux it is supported by a Fusion/MPT driver from LSI. Any chance of getting a driver for this chip? I have an IA64 box with a 1030 as well. :-/ Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
