Re: Why Adaptec 1540 bombing?
In message [EMAIL PROTECTED] Darryl Okahata writes: : If he can't, I've got a 1540A somewhere (in theory ;-) that I'd be : willing to lend out (if the address is in the US). It's been years : since I've used it, and so I'm not 100% sure that it still works, : though. Well, I could install 2.2.x onto a disk and see if that works there. Once I do that, I can then know if it works or not. :-) Warner Warner and Darryl. The 2.2.x series seems to work fine on it (what I am using on that machine now). I also have a 1542C controller that I could try. Would that one be expected to be any different from the 1540A? I also have a Future Domain 16xx controller, and a DPT 2012 series controller (the original dos EISA controller that was in the machine). My goal with the machine (a 1993ish Intel EISA board with 32M ram, Phoenix bios, and badged Groupe Bull) was to try the 3.3 and 4.x builds for some play. I have been running 3.2 or 3.3 on all my other boxes, just fine on IDE controllers. Since I ran across these scsi controllers I was thinking of trying them. The DPT did not run at all. The 1540A did not run the 3.3 or 3.2, but came up fine on 2.2.6 or 2.2.8. That got me to thinking that something had changed in the Adaptec driver and query what and why. Any insights are appreciated. If you need the board for testing, I could probably arrange that, or, if you have a test snapshot I could pick up, I could try that too. What specific info would you need from dmesg (assuming it will go far enough to get some messages) or elsewhere? From memory, I think it got as far as listing the controller and/or drives attached, then went off polling for devices and never came back. It did that from the 3.3-RELEASE and the 4.0-19990918 snap (if I have my numbers correct on the snap). I don't think I tried 3.0/3.1/3.2 on it. Thanks Bob To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why Adaptec 1540 bombing?
In message [EMAIL PROTECTED] FreeBSD Bob writes: : The DPT did not run at all. I do not have access to the DPT controllers, nor to a EISA system for testing. : The 1540A did not run the 3.3 or 3.2, : but came up fine on 2.2.6 or 2.2.8. That got me to thinking that : something had changed in the Adaptec driver and query what and why. Yes. CAM happened. :-) The 1540A card had some interesting problems with the setting of residuals which the 1540B and later do not have. CAM requires these transfer counts be accurate or it can get confused. I tried to cope as best I could, but without access to an actual card I couldn't verify that it worked. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why Adaptec 1540 bombing?
In message [EMAIL PROTECTED] FreeBSD Bob writes: : It is a long shot, but I am curious if anyone knows of any problems in : using the Adaptec 1540A on 3.x or 4.x machines? The aha 1540 driver (me) didn't have access to the 1540A cards, so I made changes blind and never tested (nor did those folks that bugged me to make them). If you can send me this card, I can see what I can do about making it work with the aha driver. There are problems with CAM and this hardware's use of transfer residuals which might make it hard to get working. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why Adaptec 1540 bombing?
Warner Losh [EMAIL PROTECTED] wrote: If you can send me this card, I can see what I can do about making it work with the aha driver. There are problems with CAM and this hardware's use of transfer residuals which might make it hard to get working. If he can't, I've got a 1540A somewhere (in theory ;-) that I'd be willing to lend out (if the address is in the US). It's been years since I've used it, and so I'm not 100% sure that it still works, though. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why Adaptec 1540 bombing?
In message [EMAIL PROTECTED] Darryl Okahata writes: : If he can't, I've got a 1540A somewhere (in theory ;-) that I'd be : willing to lend out (if the address is in the US). It's been years : since I've used it, and so I'm not 100% sure that it still works, : though. Well, I could install 2.2.x onto a disk and see if that works there. Once I do that, I can then know if it works or not. :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Why Adaptec 1540 bombing?
Anyone in the current folks know why I might be getting problems with FreeBSD on an Adaptec 1540 controller? The machine works fine on 2.2.8 and 2.2.6, but dies a horrible screeching halt when installing 3.3 or 4.0. It literally just locks up solid when 3.3 or 4.0 probes the machine during the install. No messages, no nothing. Using an IDE controller works fine. The blue screen with the grey probing window comes up and then the machine freezes, as if the probing got stuck somewhere. The machine is an Intel 486/33 with 485 cache board, 32 megs ram, Adaptec 1540 or generic IDE controller. It is a long shot, but I am curious if anyone knows of any problems in using the Adaptec 1540A on 3.x or 4.x machines? Any insights or suggestions are appreciated. Thanks Bob To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
