6580 i845pe and Adaptec 2940UW

Adaptec 2940UW card hangs at POST, updated to the latest BIOS version for the 6580 i845pe Max and Adaptec card - problem still exists.
example:
"Device 1 - plextor cd
Device 2 - toshiba 32x ..
SCSI BIOS NOT INSTALLED ! "
now, system is hung.
terminations are correct, moving the 2940UW to different slots and removing all cards except video doesn't help, I suspect a problem in the 6580's bios. Same scsi rig has no trouble in 3 other systems I tested on. I've also tried with scsi bios enabled - same results. Please advise !

Hmmm.... I dunno.
Adaptec says this:
The BIOS of the SCSI card is used as the bootstrap loader to link hard drive(s) (INT13 devices) through the Interrupt vector table into the system BIOS.
If there are no hard drives connected to the SCSI card, the message is normal.
The Bios looks for hard drives at ID's 0,1,2 and if none are found the message: " BIOS not installed " is displayed. The primary reason for a BIOS is when you have a bootable SCSI hard drive.
To prevent the message from being displayed, "Disable" the BIOS function in SCSI Select: Press Ctrl+A to enter SCSISelect, and go into Configure/View Host Adapter Settings, then go to Advanced Configuration and where is says Host Adapter BIOS or SCSI Controller Int-13 Support set this option to Disable or Disable Scan Bus depending on the BIOS revision and the SCSI card.
Note: This is not an error message, but a BIOS display message only, stating the BIOS was not loaded into memory and all control of device, will be done through the driver.
So you might try disabling INT-13 support?

Similar Messages

Trouble installing w/ Adaptec 2940UW and Seagate ST19101WC

I am running a home built PC w/ an Adaptec 2940UW SCSI card and a Seagate ST1901WC SCSI hard drive. I have loaded and removed Redhat 6.1, Windows 2000, Windows 98 SE. I know that the hardware is installed properly. When I try to load Solaris 8 for Intel, it goes into the Webstart and after I select the language to install in, it looks for a volume to install to and tells me that no supported disk device is installed. Please check hardware, or select different install method. The SCSI card is listed in Suns' Compatibility list and the drive is a high end 9.1 Gbyte Seagate, which I would imagine works fine with Solaris 8. I checked on Adaptecs' Knowledge Base and found no known problems with this card in Solaris 8 (Intel) I did the same for Seagate.
Can anyone think of any possible reason this is not allowing me to install.

I think there are special requirements for using the new java based
"Webstart Installation" cdrom.
Don't use the "Installation" cdrom. Install from the "Software 1 of 2" cd - with or without the DCA floppy.

Adaptec 2940UW bootable with G4 933 (Quicksliver 2002)

Hello,
I am setting up a second machine in OS 9 native like my blue and white G3 for some legacy applications. I was able to boot from SCSI drives fine in my blue and white G3 with the Adaptec 2940UW and 2940U2W cards. I now have a 10 gig Cheetah SCSI drive in the G4 connected to the 2940UW, and it won't seem to boot. The Cheetah is mounted and I was able to install system sofware, copy files etc., but I can't seem to boot from it. The internal apple drive will boot fine, so I'm wondering if this card is not bootable in the newer machine? Any thoughts or help would be greatly appreciated.
Cheers,
Jeff

Not sure what your exact issue might be but I know for a fact that some of the later G4 towers had issues with SCSI cards. Specifically Adaptec cards.
If you look around on xlr8yourmac you will find something. I remember it being the Digital Audio and QS that had the issues.

Solaris 10 x86 and Adaptec 2400a

Hello,
Are there any plans to add support for Adaptec 2400a (IDE RAID Controller) to Solaris 10 x86?
Thank you,
Jakob

Hello Jakob,
this is the wrong forum because it's about Sun Hardware and only user-to-user.
I would suggest that
you use your service-plan and contact Sun
or
join the Solarisx86 group on Yahoo, browse the previous posts and then re-post on this maillist.
Please check the Links page before posting:
http://groups.yahoo.com/group/solarisx86/links
Post message: [email protected]
UNSUBSCRIBE: [email protected]
Btw. even the RAID functionality of the integrated RAID controller of Sun x64 systems isn't supported under Solaris 10 (only RHEL) ...
Michael

MS-6580 845PE and PCI Radiolink Mediaforte

I have MSI-6580 Ver 2.0 with latest BIOS Ver 3.7. I installed PCI Radiolink from Mediaforte. After booting this mainboard recognised only PCI Radiolink and Sound card on mainboard is not working /is disabled/, its not possible to use. Problem seems similar as was described by somebody else, that its not possible to use two sound cards. I tried all BIOS version from WEB inclusive older one, I have changed PCI RadioLink in different slots, but no result. Similar problem I had before with new MS 865PE NEO-LS, but problem was resolved with newest Beta Version of BIOS.
Knows somebody solution for this problem?

Hi dalibor,
Hummmhh... 2 sound cards on 845 mobo... Have not tried before but you can check for IRQs conflicts to see if this 2 devices are conflicting each other
All the Best... :D!!!

MSI 8348 CD-RW and Adaptec software

Can anyone help me out? I have fitted an MSI 8348 CD-RW drive. Its installed on the same IDE cable as the other CD drive, but set as master. I have loaded up the Adaptec Easy CD Creator 4.0 and direct CD 3.0. When I reboot and windows has launched, the little icon in the bottom right of the screen is indicating that there is no supported CD-R/RW drive supported. Anyone else come across this and if so is there a fix for it?
Cheers

Check for the latest updates for your Roxio (previously Adaptec) Software - it's likely that it just doesn't recognize your drive - patches are released to update the drive list. However, your version 4 is old and may no longer being receiving updates that will recognize your drive.
(did you receive that version of Easy CD with your drive?)
http://www.roxio.com/en/support/software_updates.jhtml
Actually, I've just checked:
http://rpp.roxio.com/drives/?page=supported_drives&ltr=M
and you'll see that your drive only received support with version 5.3.0.83 of Easy CD Creator basic. Version 4 won't work for you.

K7D Master and Adaptec 2100S RAID not working

I have the K7D Master with 2 AMD 1900+ MP cpu's and 1 GB RAM. I can not get the Adaptec 2100S RAID SCSI card to work with this mainboard. I have taken out all of my PCI cards, and I have tried to place the 2100S in all of the PCI ports, but the card will not work. It seems that the bios of the K7D do not like the bios of the Adaptec card. The Adaptec works fine with the K7NPro motherboard, so it is nothing wrong with the card. I have just bought 2 x 15.000 rpm scsi disks, and I was really looking forward in having SCSI RAID with this excellent motherboard.
Does anybody have the same problem, or does anyone have a solution - it will be highly appreciated.

I am using anAdaptec 29160N with 3 scsi drives and this works like a charm. It is just the Adaptec 2100S which doesn't work, and the problem is related to the AGP port. I tried to remove my AGP card and installed a PCI video card - then suddenly the 2100S worked. It was assigned an IRQ and I could also get inside the bios/menu of the card.
I therefore decided to test different AGP cards - I tried Creative Banshee (3DFX chip), Creative GeForce 2 Ultra, Leadtek GeForce 3 Ti 500 and 3DFX Voodoo 3. The Adaptec card would not boot no matter what AGP card I tried. The machine hangs when the bios of the Adaptec is showing. I then tried 3 different PCI video cards (Geforce 2MX, ATI Rage3D and Matrox), and the 2100S worked with all of them.
So it seems that the Adaptec 2100S will not boot (hangs during bios message) as long as the AGP port is being used on the k7D - the question is: can MSI come up with a new bios that resolves this problem or do I have to live without my 2100S ?

Solaris 8 and Adaptec 19160 SCSI controller

Hello !
I'm sorry for my bad English.
Mashine configuration
processor P4 1,5
mainboard Abit BW7 (I845)
SCSI Controller Adaptec 19160
SCSI hard drive futjitsu 18 Gb
EIDE WD 60 Gb
Ethernet Controller Surecom EP-320X-S (Realtec 8139)
Video NVIDEO TNT 2 PRO
Huge trouble: Adaptec 19160 SCSI contoller detected but not detect SCSI hard drive.
Ethernet Controller not worked, net protocol only lo0
What can I du to resolve this problems?

Ethernet Controller Surecom EP-320X-S (Realtec 8139)This can probably be solved with realtek's solaris driver:
http://www.realtek.com.tw/htm/download/driver.asp?model=RTL8139(A/B/C/8130)/810X%20Family&category=2

ADAPTEC 2940UW SCSI on Solaris 8_x86

Solaris 8_x86 is able to recognize the AHA2940UW SCSI card but during bootup, the OS kept probing the card from id 0 to 15 (apd0) in an endless loop, returning timeout; reset target; target 0 lun 0......
Tired the solutions in Solaris Device Configuration Guide but no avail.
Please advice.
Thanks

Tried that....the card was recognized...tried changing the values of the SCSI advanced setting during bootup (CTRL A)...but no avail.
Please advice n thanks.

Scsi controller not recognized during ftp install

Hi all,
As you can tell, this is my first post and my first attemp to install arch. I downloaded the latest ftp install floppies "Arch Linux 0.5 (Nova)" and I am trying to install arch on a PII system with and Adaptec 2940UW controller and no cdrom. I can boot from Tom's recue disk:
http://www.toms.net/rb/
and the controller is recognized and I can use fdisk to partition the drive.
However, when I boot from the arch install floppies, the controller is not recognized. When I manually load the module for the controller, ie. aic7xxx, lsmod shows it as unused.
After looking at the boot log using dmesg, I noticed the following, which I don't understand:
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno=2
Is this a kernel issue and does anyone have any pointers for me?
Thanks
Kevin
PS: I tried my best to search for a related topic.

Thanks for the reply. It still doesn't work for me.
I noticed that the floppy images have been updated -- the md5sum's have changed. I will give them a try.
As an aside, the listed md5sum's for the new images don't match the downloads. I downloaded from several mirrors and I get the same sums, which don't match the sums listed.
$ md5sum *.img
99683b5a119e6332cd8f2185a24083cf boot.img
d2501030749fa2629582de1f02846056 modules.img
97fb96d7b1d858cb260ea8b1005e071b root.img
$ cat md5sums
2d172ab879f1487f0a381cf432173c26 boot.img
ce6408f0e4051656ddf9c2df3356f1f8 modules.img
97fb96d7b1d858cb260ea8b1005e071b root.img
Thanks
Kevin

MSI 845PE Max2 (MS-6580 v2.0) Help Please!

OK... I'm confused ?(
Well... I got the MSI 845PE Max2 - L (MS-6580 v2.0) on
order. Now I'm reading that alot of peeps having so
many problems with it! 8o
I just read a reply from Assaf saying that the board was SUED?
First off, what does this mean?
Should I return this board when it arrives or keep it?
Also, Im a little unclear of the difference between the
845PE Max2 (MS-6704) & the 845PE Max2 (MS-6580 v2.0)
Why are there 2 Different models that both say 845PE Max2?
NOTE:
I plan on using my Crucial DDR 333 (2 x 256MB) & a PIV 2.40 (533MHz FSB).
My other Specs are below.....
Any help will be appreciated.
I rather not even open the box if this board has MAJOR problems.[/color]

Uhmm i think you are mixing boards
There is no such board (at least not yet) as a 845pe-max2 version 2.0 there is a 845pe-max version 2. There is some difference between the max and the max2 board. The max version only has room for two dimms, no bluetooth/raid and gigabit support. So you are talking about two completely different boards but with very similar names I'm not a motherboard expert but i have tried the max2 version (6704) and i wasn't completely satisfied, cpu temp is way off, bios upgrade caused wierd problems, when using my adaptec 2940uw controller raid bios disappers. I think this is a result of the companies releasing their products to soon, as far as i can tell (and i have been reading a bit ) all 845pe based motherboards have their problems. When you ask what to buy everyone is saying asus p4pe, i for one think that asus is overpriced and i really don't wanna waste money on a serial ata solution which has no future. Their onboard audio isn't suported by freebsd. I have not decided quite yet, i was actually rather satisfied with my msi 845pe max2, it has a lot of nice features and i like msi liveupdate, the board runs perfectly with other os's than windows, but i will see some response from msi regarding those problems there is,
and currently i'm awating to see if msi will release a bios that perhaps will fix those problems i (and alot others) had with this board.
Regards
Maynard

Solaris 7 Adaptec 294x Cards

My copy osf Solaris 7 does not see the Adaptec 2940UW Pro Card installed in the sytem, even though the BIOS does
Any ideas ?
cheerz
Steve

I am also having difficulty installing solaris 2.7 using the same controller. I went through the process of using the patch diskette and when the system rebooted, I received the following error:
run-time error R6003
- integer divide by 0
Has anyone experienced this?
[email protected]

K7T M6347 onboard SCSI and XP problems

I have a M6347 based system with the following:
Matrox G400 vid
4 * 9GByte SCSI drives
40GByte IDE
60GByte IDE
CDROM
CDRW
Promise IDE Controller
DVD-ROM
Adaptec 2940UW
9GByte SCSI
SBLive card
3com905tx NIC
Generic 56k modem
XP booted from drive0 on the onboard AIC 7892 controller, and everything was fine.
I pulled the system apart and put in another case, and XP wouldn't boot. It hangs at 'kdcom.dll', which is the kernel-mode debugger.
I've tried a few things, and this is where I am now.
I've pulled everything out, and put a temp 13GByte drive in there, and installed XP on it, and set the system to boot from the 13GByte IDE drive. With nothing but the video card in the system, XP gives me a code 12, and complains it can't allocate enough resources for the AIC-7892. It doesn't, unfortunately, tell me what resources it needs. It's almost as if the hardware's gotten stuck in a particular configuration, and I can't reset it.
I'm assuming this non-recognition under the temp XP installation is why my original XP installation isn't booting.
Any ideas would be appreciated.
patscc

Initially, I put everything back in the same slots. That's when the original installation hung. That's when I started resetting ESCD, and pulling cards in hopes of getting the original installation back up, and when that didn't work, put in a different drive and temporary XP installation so that I ( in theory ) could fix the original one.
I had the problem of the original installation hanging on boot the first time I installed XP on the board. At that time I moved cards around, reset ESCD several times until XP was happy.
What I've done in the meantime is use the temporary XP installation to load the system hive and disable the AIC 7892 driver of the original installation. When I boot, it goes further, this time it's mupped. ( Hangs at Mup.sys ). Haven't done much with trying to resolve the mupped issue. Now, the temporary XP installation still can't load the resources for the AIC 7892, and XP still isn't telling me what resources it wants.
Just out of curiosity, is there any way to disable the onboard SCSI ? I couldn't find anything in the bios, and couldn't find anything in the manual.
Any other ideas ?
patscc

Unable to Install Windows Server 2012 R2; system aborts and reboots after first blue Windows logo appears

System: Dell PowerEdge sc1420 with dual xeon and Adaptec 2420SA SATA RAID (supported by OS); 10 GB memory (2x4, rank 2, organization x4, in DIMM1 & DIMM2; 2x1, registered, organization x8, in DIMM3 & DIMM4)
This computer is currently running Windows Server 2008 R2 Enterprise which was installed with no problems.
Objective: clean install of Windows Server 2012 R2 Standard on an otherwise unused RAID array disk set.
All attempts to boot from DVD result in loading of files (grey progress bar on bottom of screen), brief dark screen, then black screen with a blue windows logo for about 2 seconds and then a flash of about 10 lines of error notifications on a black screen
for about 1/4 second (unreadable), and then a reboot of the computer.
Coreinfo.exe confirms that cpus DO support NX and PAE; do NOT support VMX (virtual machine enhancements).
Attempts to run memtest.exe from boot disk tool-menu startup result in an error message that the memtest.exe file is corrupt.
Running memtest.exe from Windows 2008 R2 install disk results in all memory tests passed!
Attempted booting with multiple DVD's (some +R, some -R, all verified) burned from .iso. These DVD's were used successfully to install Windows Server 2012 R2 on an HP Pavilion. Also changed DVD drives just to rule out DVD hardware.
Running CHKDSK from Windows 2012 R2 on HP Pavilion shows no problems; running CHKDSK from Windows 2008 R2 on the Dell system on the same disks shows some problems. Running checkdisk on the Windows 2008 R2 install disk from the Windows 2008 R2 installed
system shows no problems. All disks burned and verified on same system.
Also attempted to boot from USB thumbdrive with copy of DVD on it. Same results: system loads files then reboots at first Windows logo. So that would rule out disk quality issues per se??
Started to try an upgrade rather clean install to see if any errors were announced. None were announced as the system went through much of the process. I aborted somewhere along the way before committing to the upgrade because 1) the most likely
outcome was it would not boot after install (I don't really need the practice in restoring); and 2) even if it did reboot, having a system that can't be repaired by booting the install disk is pointless.
All disks and raid arrays are recognized and usable by RAID controller card and by Windows Server 2008 R2. Disks are within spec for use with Adaptec 2420SA (1TB @ 300).
Is VMX (aka VT-x) actaully required for ANY install even though Hyper-V is not intended to be used? If so, it is too bad that the Microsoft system requirements (
http://technet.microsoft.com/en-us/library/dn303418.aspx ) don't make that clear. And lack of VMX support really doesn't explain the memtest.exe "corruption" issue.
Or is it maybe something unique about the files on 2012 R2 disk (or disk image on USB) that are causing some problem with the chipset processing? But why?
My vote would be for the latter of the issues, but I have no clue why or if it is remediable. Suggestions?

So here is what I think is the final understanding of this problem:
First, one additional piece of important information: The computer successfully moves into and through the Windows Boot Loader phase and succeeding phase ONLY for Windows 8.1 32-bit, but NOT for Windows 8.1 64-bit nor for Windows
Server 2012 R2 (only 64-bit).
The Windows Boot Manager phase (which precedes the Windows Boot Loader phase) is either 32-bit or 64-bit (64 –bit for this case) and is loaded by the 16-bit stub program (Bootmgr) which starts in real mode.
Windows Boot Loader of course runs in either 32-bit or 64-bit (64 –bit for this case) according to the product being installed.
By inference, the essential problem is occurring in conjunction with the loading of a WIM file to start the Windows Boot Manager.
The boot manager starts ok and generally shows its essential screens (Windows Boot Manager; Advanced Boot Options) or proceeds to load files for transition into Windows startup in the succeeding Windows Boot Loader phase (that doesn’t “boot” but rather
loads the system). This is best confirmed by the announced corruption of the memtest.exe file when selecting Windows Memory Diagnostic from the Windows Boot Manager Screen.
If allowed to continue loading files to pass control to the Windows Boot Manager, the type of abort and resulting immediate restart that occurs is that which you would associate with unhandled cpu exceptions (invalid instruction, memory out of range,
wild interrupt, etc.) that most of us have not commonly seen for 20 years (since beginning to use well behave OS’s from Windows NT 3.1 and on).
So, the problem obviously is due to a failure to properly mount the WIM file and/or properly access it (probably the latter) when running in 64-bit protected mode.
This is independent of the hardware on which the install disk is actually mounted (DVD or USB-flash), so it is NOT a hardware problem
per se.
Since the WIM is mounted early in the process, Boot Manager may well have loaded it using BIOS routines to access the physical device on which it resides rather than loading 32-bit or 64-bit drivers of its own.
Hence, if the BIOS does not “mount” the WIM in a way that is later fully compatible with access from the 64-bit systems being loaded, it could cause apparent file corruption.
If it is only partially incompatible some functionality may appear quite usable (like loading files) until later detected.
This is vague on my part, because the exact nature of the incompatibility cannot be readily determined from the information available.
But the consequence is the same: the system cannot boot from the install disk, either for initial installation or repairs.
Incidental conclusion: The 64-bit boot manager code for Windows Server 2008 does not exhibit this faulty behavior, but the 64-bit code for Windows Server 2012 does.
So the problem is not inherent with loading 64-bit server OS’s.
Expectations: If the system were to be upgraded using the features of the install disk while running an installed OS, say Windows Server 2008 R2, it might well succeed and yield a fully functional system upgraded to Windows Server 2012
R2 (because the installed operating system is started from discrete files, not from a WIM file).
However, in order to perform a disaster recovery using Windows resources (such as image backups from Windows Server Backup), one would have to presumably boot from a Windows Server 2012 64-bit install disk or Windows Server USB recovery drive.
Of course we know that the Windows Server install disk will not boot and we can be fairly sure that the problem will migrate to any Windows Server USB recovery drive that is created.
My inspection of a Windows 7 System Repair CD shows that is based exclusively on boot.wim, not discrete files!
Of course a generated image for a WIM for Windows 2012 USB recovery drive
might not have the flaw that drives this behavior, but it probably would.
Problem conclusion: A BIOS upgrade would be required for compatibility with Windows Server 2014 clean installation
and any maintenance; and none is available from the OEM.
Problem not resolved, but understood for future reference.
Thanks to Tim whose comments helped me focus my thinking.

Will OSX support Adaptec PCI Express scsi cards in an early 2008 Mac Pro?

I need to move my scsi interface scanner from a G4 machine and the old PCI Adaptec AHA 2930 CU card won't fit. I was using Snow Leopard on the G4 unit - it still supported the Adaptec card and all was good. My 23" Cinema display then bit the dust and I replaced it with with a 24" Cinema display with the mini display port connector. I purchased an adapter from Kanex to make it compatible, but the adapter was defective - so I returned it. Their reviews aren't very good - seem to have a lot of D.O.A. adapters - not sure I want to deal with the frustration, but it would be the least expensive option.
I do have, however, an early 2008 Mac Pro that I can use, provided that it supports the newer PCI Express scsi cards that Adaptec makes. I'm not sure which one to get yet, either. I'd rather not buy one and find out it won't work. I can make a partition on the boot drive for Snow Leopard in case scsi isn't supported in later versions of OSX. In case you're wondering, I did use a scsi to firewire adapter to run the scanner on my laptop for a while - but it stopped working and I can't locate any replacements (or the company - 2nd Wave Technologies - for that matter). I haven't tried locating a scsi to usb adapter, but from what I can see, they are getting pretty scarce. I'd replace the scanner, but it is fairly pricey and the newest model retails at the price of a small car - so that really isn't an option at this point.
Thanks in advance for any info.
Message was edited by: Jakob Richardt
Changed name of display adapter manufacturer.

Thanks for the response - I guess the question I should have asked is "Will OSX support scsi cards in an early 2008 Mac Pro and if so, which ones?" I didn't realize Apple and Adaptec weren't working together - my G4 tower arrived with an Adaptec card in it when I bought it in 2000 (from a third party vendor, not directly from Apple). It came with either OS 8.* or OS 9. When I updated to OSX, everything continued working, so I didn't think much about it until I pondered using the Mac Pro for the scanner - at some point the G4 is going to stop working - need to have a solution before that happens. The manuals I've been reading refer to the slots in the G4 machines as PCI. The manual for the Mac Pro refers to the slots as PCI e. These slots have fewer connectors, so I thought that the "Express" part of the name referred to this particular card configuration when compared to the longer card connectors in the G4 type of machines.
Can you tell me what scsi card brands will work in the Mac Pro? I'd still like to pursue this option. As I mentioned in my original post, buying a new scanner isn't in the cards right now - it costs more than the computer, so, although pricey, the card option is still less expensive.
Thanks!

6580 i845pe and Adaptec 2940UW

Similar Messages

Maybe you are looking for