First off, check Intel's FAQ for the AL440LX. You'll find that there are several issues that aren't addressed, and several that are addressed but not answered, but this will give you the "official company line" so that you have a starting point. The faq can be found at: http://support.intel.com/support/motherboards/desktop/al440lx/.
Now, on to the questions!
BIOS QUESTIONS
How do I determine which BIOS version I am using?
I have an OEM version of the AL440LX motherboard from a company such as DELL or NEC. Can I use the BIOS updates from the Intel Site?
I get the following error message when I try to update my BIOS using the BIOS from Intel's site:
(H 48):Invalid reserved string in flash image header
What does this mean and what am I doing wrong?How do I load the BIOS using the BIOS recovery method?
I'm having problems with BIOS P10!
Does BIOS P10 support the ACPI hibernate function?
In the BIOS Setup, what is the AGP Aperture setting and what should I set it to?
What does the "Legacy USB Support" option do?
I'm having problems with the Wake on Ring function of the AL440LX. How is it supposed to work?
OS QUESTIONSHow do I configure my COM and LPT ports for use in DOS?HARDWARE QUESTIONSWhich bus master drivers should I use? How do I determine which drivers I am using?
Where can I get the Yamaha OPL-4 wavetable chip for the AL440LX? Can I get a motherboard with the OPL-4 chip?How do I get my LS-120 drive to work?
I'm having problems with my Adaptec 2940.
During the POST, you should see a BIOS string similar to this:
4A4LL0X0.86A.0019.P07
The BIOS is commonly referenced by the last three digits. In this case, P07 is commonly referred to as BIOS 7. The second string, 86A, is also notable because it indicates that the motherboard is using the Intel version of the BIOS. If the second string is different, it indicates that you are using an OEM version of the BIOS, such as that supplied by Dell, Gateway, or Micron.
Here are some of the BIOS codes for various OEM's which use the AL440LX:
04A Sony
05A Micron
10A Dell
11A NEC
15A Gateway
21A Hewlett Packard
86A Intel
If the BIOS string you see looks nothing like what I have above, chances are your system does not have an AL440LX motherboard.
When the Intel program starts to upgrade the BIOS, it checks the BIOS header. In the header:
4A4LL0X0.86A.0031.P14
The .86A indicates that the BIOS is from Intel. However, on an OEM machine, the BIOS header is different. Here is an example of one of the Dell headers:
4A4LL0X0.10A.0027.P09.9803261356
The .10A indicates that the BIOS is from Dell, and that the BIOS version is P09. Using the normal upgrade utility, you won't be able to upgrade the BIOS because of this check. However, there is a way to bypass this check. The motherboard has a feature that allows it to do an emergency recovery of the BIOS in case something goes wrong. To use this feature, you have to remove the configuration jumper and put the BIOS disk in the drive. When your machine boots, it will start reading from the floppy, and start loading whatever BIOS is on the disk (provided it is a BIOS for the AL440LX) without doing the 86A check. The computer will indicate success with a series of beeps, and there will be no indications on your monitor during this phase. Before I give you the detailed instructions on what you need to do, the disclaimer monster has to rear it's ugly head:
Using the BIOS from Intel will probably void the warranty on your computer from your manufacturer; check with the manufacturer and their policy. You should check with them first for a BIOS update. If your manufacturer hasn't been able to help or hasn't provided any BIOS upgrades, you can use the Intel BIOS; just make sure the BIOS addresses the problem you're having by reading the readme file included with each BIOS upgrade.
Now that that ugliness has been taken care of, first try upgrading the BIOS using the Intel program on the BIOS upgrade disk. If this doesn't work, you can do one of two things: modify the BIOS files using a hex editor, or load the BIOS using the BIOS recovery method. If you know how to use a hex editor, you can edit the four BIOS files ending in .bio, bi1, bi2, and .bi3. The beginning of each file contains the BIOS header. Edit this header to match the maker of your motherboard. So, if you want to load an Intel BIOS on a Dell computer, you would change the .86A to a .10A. This process also works in reverse. If you aren't comfortable using a hex editor to modify the BIOS files, you should use the BIOS recovery method.
Again, you should note that this will probably negate or at least affect
the warranty on your computer from your manufacturer. But, if you've reached
this point they probably haven't been much help so far. And of course,
who is to say that you can't use the same procedure to reflash the OEM
BIOS if something goes wrong? Just a warning.
Create the BIOS disk according to the directions in the BIOS download file. I suggest you create two disks (one as a backup) in case something goes wrong and the disk gets messed up. If you have the manual for your motherboard, use the procedure for recovering the BIOS on page 43:
1. Turn off the computer
2. Remove the configuration jumper to set recovery mode
3. Insert the bootable BIOS disk in A:
4. Turn on the computer and let it boot
5. Listen to the speaker:
2 beeps and the end of activity
in A: indicate successful recovery
A series of continuous beeps
indicates failure. Return to step one and try again.
6. If recovery is successful, turn off the computer.
7. Put the configuration jumper on pins 1 and 2 to set normal mode
for setup
8. Leave the BIOS upgrade disk in A: and turn on the computer.
9. Perform the BIOS upgrade as normal.
Intel's answer:
Intel is currently investigating this issue. In the meantime, please
try the following:
1.Go into BIOS Setup and press (reset to the default BIOS values).
2.Change other Setup options as needed.
3.Go to the Advanced menu and change the "Reset Configuration Data" entry
to 'Yes'.
4.Press and select 'Yes' to save these changes.
You should also verify that you have installed the PIIX4 INF Update Utility (SETUPEX.EXE) into your system.
My Answer:
I've been able to trace most of the problems to Intel's Bus Master IDE
drivers and the second IDE channel. However, if you aren't using these
drivers, there are a few quick fixes that you should try:
2. Some people have been able to solve the problem by putting their HD and CD on separate IDE channels. I have three hard drives in my system and my CD-ROM is the secondary slave drive, so this solution doesn't work on my system.
3. In the BIOS, try enabling USB Legacy Support, especially if you are using Windows 98RC1. This also did not fix the problem on my machine, but it has worked for other people.
4. In the BIOS, change the detection setting for your CD drive from Auto to CD or None. My system still had problems shutting down, but the startup went a lot faster.
5. Try configuring the LPT and COM ports manually via the BIOS.
The real cure is to do a clean installation of Windows. This
will cure all shutdown problems in 90% of the cases I've seen. We all know
it's as fun as a trip to the proctologist, but it will do the trick.
Welcome to the club! :) Check out my BIOS
P10 installation page -- I have answers to most of the common questions
there.
"Select the size of the Accelerated Graphics Port (AGP) aperture. The aperture is a portion of the PCI memory address range dedicated for graphics memory address space. Host cycles that hit the aperture range are forwarded to the AGP without any translation"
Here's the translation:
The AGP can address system memory without going through the processor. Cards on the PCI/ISA bus have to put in a request through the processor to retrieve or store data in memory. This is part of what allows AGP its speed benefit. The aperture size allows you to define how much memory the AGP card is allowed to address for storing video data (texture maps, etc.). The 64MB setting allows the AGP access to the first 64MB, and 256 allows it access to the first 256MB. However, just because the card has access, doesn't mean it will utilize all of that space. Its just a "permission slip." I would leave the setting at 64MB. For the average user, it won't affect performance at all.
Lets say you have 256MB of RAM, and are running some huge graphics applications.
If you set the AGP aperture size to 64MB, the AGP card would only be allowed
that first 64MB, leaving the rest of the system memory for your applications
to use. Theoretically, it should prevent Windows from dumping everything
into the swap file if you were working on something really big. This is
more of a theoretical setting at this point though. I don't know of any
games that use more than 12MB of video memory, so you should be in good
shape.
Intel has provided a good explanation of this in the AL440LX Motherboard
Specification Update:
USB legacy support enables USB keyboards and mice to be used even when no operating system USB drivers are in place. By default, USB legacy support is disabled. USB legacy support is only intended to be used in accessing BIOS setup and installing an OS that supports USB.Additionally, it appears that having USB legacy support enabled in the BIOS cures shutdown problems with Win98 RC1, regardless of whether or not you are using USB devices.This sequence describes how USB legacy support operates in the default (disabled) mode:
1. When you power up the computer, USB legacy support is disabled.To install an operating system that supports USB, enable USB legacy support in BIOS Setup and follow the operating system's installation instructions. Once the operating system is installed and the USB drivers configured, USB legacy support is no longer used. USB legacy support can be left enabled in BIOS setup if needed.2. POST begins.
3. USB legacy support is temporarily enabled by the BIOS. This allows you to use a USB keyboard to enter the Setup program or the maintenance mode.
4. POST completes and disables USB legacy support (unless it was set to Enabled while in Setup).
5. The operating system loads. While the operating system is loading, USB keyboards and mice are not recognized. After the OS loads the USB drivers, the USB devices are recognized.
Notes on using USB legacy support:
If USB legacy support is enabled, don't mix USB and P/S2 keyboards and mice. For example, do not use a USB keyboard and P/S2 mouse, or a P/S2 mouse and USB keyboard.
There are some known problems with the Wake on Ring function of
this motherboard. Enabling it doesn't seem to so much of a problem as disabling
it is. Here is how things work:
For external modems, the Wake on Ring function monitors COM1. If you want your computer to Wake on Ring, your external modem must be connected to COM1. If you're having problems disabling the Wake on Ring function, your best bet is to move your modem over to COM2, since it is not monitored by the Wake on Ring function.
For internal modems, you must use an internal modem that supports the Wake on Ring header. I do not know of any internal modems that have this connector, so if you know of any, please let me know. The Wake on Ring header is used to connect an internal modem to the motherboard, so that the motherboard can sense the ring signal. The modem converts the ring signal from the phone line to an appropriate signal for the motherboard. You need a modem that supports this feature to use the Wake on Ring with an internal modem. You're looking for a modem with a similar two pin connector on it.
I would not suggest attempting to connect your RJ11 phone line to the Wake on Ring header. The voltages on the phone line, while not very strong AMP-wise, are high when you compare them to motherboard voltages. Unless the motherboard has some voltage conditioning circuitry for the Wake on Ring header, you're likely to fry something.
The easiest solution is to go to an external modem.
Note: The wake on ring problems were addressed in BIOS P09.
Intel has produced a good response to this question:
When an IRQ is claimed by an ISA bus add-in card or by a motherboard
resource such as the serial ports this IRQ cannot be shared with other
resources including PCI resources. When an IRQ is steered to the
PCI bus this IRQ can be shared with other PCI devices as long as there
are no ISA cards
attempting to use this IRQ. PCI interrupt request lines are level sensitive
and are asserted low when an interrupt is generated. The PCI chipset has
an internal PCI interrupt router that assigns available IRQ's to the PCI
interrupt request lines. When an IRQ is marked as "Reserved" in the BIOS
Plug and Play configuration, the BIOS will not program the PCI Chipset
Route Control Register to use this interrupt. In the case of a PnP operating
system or the ISA
Configuration Utility, configuration information is stored in the Flash
Memory's ESCD region (system plug and play storage). The BIOS uses this
information to determine which IRQ's can be routed to the PCI bus.
For a detailed description of the PCI Interrupt Routing Map check the
Technical Product Specification on page 53 paragraph 2.6.
http://support.intel.com/support/motherboards/desktop/al440lx/spec.htm
There are two ways to accomplish this: Intel provides a utility
called DOS ICU which is included on the AL440LX CD-ROM in the \Software\DOSICU
directory. However, the easiest way to do this is to simply configure the
ports manually in the BIOS through the Resource Configuration menu.
The Pentium II was released after Windows 95. Microsoft didn't anticipate
the PII while writing their software, so Windows 95 does it's best guess
at what kind of processor you're using. Since the Pentium II and Pentium
Pro are both Family 6 processors, and the Pentium Pro was the only Family
6 processor at Microsoft's press time, Windows 95 assumes you have a Pentium
Pro.
What does this mean for you? Nothing really. This error is purely cosmetic,
and won't have any effect on the performance of your system. Windows 98
properly identifies the processor as a Pentium II.
According to Intel, this is another purely cosmetic problem. Of
course, its one of those things that annoyed the heck out of me, so I sought
out a solution. The missing item is a set of AGP drivers, including VGARTD.VXD.
The best patch I've found comes from Micron PC, and can be found on my AL440LX
Windows 95 Installation Guide.
Conflicting device list:How do you correct this problem? You don't, because it really isn't a problem. One of the selling points for AGP architecture is that the video card is capable of accessing system memory directly. Normally, a PCI or ISA card must access system memory through the processor. Since AGP video cards can access system memory directly, they put a smaller load on the processor, resulting in better overall performance.Memory Range FD000000 - FDFFFFFF used by:
Intel 82443LX Pentium(r) II Processor to AGP Controller
Memory Range F6000000 - F6FFFFFF used by:
Intel 82443LX Pentium(r) II Processor to AGP Controller
Since Windows 95 was written before AGP video cards were released, Windows 95 doesn't understand how the AGP card can access memory without going through the processor. Since it doesn't understand this relationship, it chalks it up as a resource conflict, and reports it as such. This problem is normal and purely cosmetic.
Note: Windows 98 does not report this conflict.
The short answer: Use the Microsoft drivers that are installed with
Windows 95 and Windows 98.
For the longer answer, I have a page dedicated to the
bus master issue.
I currently do not know of any source for the Yamaha OPL-4 chips
for the AL440LX. While the motherboard supports the chip, Intel does not
produce a boxed version of the motherboard that includes the OPL-4 chip.
However, motherboards with the OPL-4 chip are available on the market. Several of the OEMs, including Micron, use boards with the OPL-4 chip. These boards are produced by Intel, but from what I understand are a special fab for the OEMs. Refurbished boards containing the OPL-4 chip are available, and are usually best found on various auction sites such as eBay.
LS-120 drives are supported by this motherboard and the later BIOS versions. The problem is that Intel didn't do a very good job of implementing this support. Your best bet is to use BIOS 5 or 9.There are some known problems with the IDE controller implementation on the AL440LX. The majority of the problems relate to CD-ROM recognition, but unfortunately the LS-120 falls prey to this same problem. The LS-120's work best when configured as the secondary device on the primary IDE controller. If you're running an all SCSI system, you can try jumpering the LS-120 as the slave, even though it is the only device on the IDE channel. This works in some cases, but if it doesn't, you'll need to get an IDE HD to attach as the master device. I agree that it is the "bailing wire and duct tape" approach to fixing the problem, but Intel has been slow to move on this problem.
If you won't be using a true blue floppy drive in your system, make sure to disable the FDD controller in the BIOS. Make sure that the LS-120 is declared as a removable device in the boot menu.
I'm having problems with my Adaptec 2940.
I don't use the Adaptec 2940 first hand, so I won't be able to answer any direct questions. However, it has been reported that BIOS versions 1.31 and 1.32 are not fully compatible with the LX chipset. The problems have been corrected with BIOS version 1.34.3 dated 8/31/98. It is available from Adaptec's website (afuv1343.exe).
Does the AL440LX support IrDA spec 1.0 or 1.2?
There is nothing specific in the AL440LX documentation, but the AL440LX uses the National PC97307 Super I/O Controller to implement the IrDA support. The tech sheet for the controller states:"The Infrared (IR) interface complies with the IrDA 1.0 SIR and SHARP-IR standards, and supports all four basic protocols for
Consumer-IR (TV-Remote) circuitry (RC-5, RC-5 extended, RECS80 and NEC)."So the AL440LX supports the 1.0 standard.
This table describes what you should hear and the meaning of each
beep code for the AL440LX. For example, a 1-3-3-1 beep code will sound
like 1 beep, pause, 3 beeps, pause, 3 beeps, pause, 1 beep.
| 1-2-2-3 | BIOS ROM checksum |
| 1-3-1-1 | Test DRAM refresh |
| 1-3-1-3 | Test 8742 Keyboard Controller |
| 1-3-3-1 | Autosize DRAM (usually indicates bad or incompatible memory) |
| 1-3-3-2 | Initialize POST Memory Manager |
| 1-3-3-3 | Clear 512 KB base RAM |
| 1-3-4-1 | RAM failure on address line xxxx |
| 1-3-4-3 | RAM failure on data bus xxxx of low byte of memory bus |
| 1-4-1-1 | RAM failure on data bus xxxx of high byte of memory bus |
| 2-1-2-2 | POST device initialization |
| 2-1-2-3 | Check ROM copy right notice |
| 2-2-3-1 | Test for unexpected interrupts |
| 2-2-4-1 | Test RAM between 512 and 640 KB |
| 1-2 | Search for option ROMs. One long, two short beeps on checksum failure. |