On this page you will a find a short guide on how to use Linux on a Compaq Armada 1750 laptop.
I wrote it so others don't have to collect all the information from many different sources in the internet (as I had to).
All comments, suggestions etc. are welcome. Please contact me at email@example.com.
This was the topic I had most problems finding information and working
First you should check that the sound-device is activated at all in the 'BIOS'.
Boot from the Setup-Disk which you can download from Compaq's
homepage. ([direct link]
/ www.compaq.com - Software & Driver Downloads -- Search for armada 1750 --
select your model)
Once the 'BIOS' is installed on harddisk, you can enter it by pressing F10
when you see the cursor blinking in the upper right corner of the screen.
You have only a few seconds time, so be quick.
I read somewhere on the net that one can reset the 'BIOS'-Settings by pressing
Fn+F11 at boot-time so the laptop boots from floppy disk again if
this was disabled before. Fortunately I never had to test this. ;-)
Enter the Compaq-Setup-Utility.
Goto Audio - ESS 1869 Plug and Play Audio Drive
Configure the Resources like this:
Interrupt request number 5
Direct Memory Access Channel 0
Direct Memory Access Channel 1
Input/Output range 0x0220 - 0x022F
Input/Output range 0x0388 - 0x038B
Input/Output range 0x0330 - 0x0331
Make sure there are no Conflicts listed below.
In System Features - System Management disable ACPI. IMO ACPI only causes
problems. With ACPI deactivated even APM suspend to RAM works (more or less).
For kernel 2.6.x with ALSA
In the kernel you need ALSA-Support and the ES688 / ES1688 ESS AudioDrive
# CONFIG_SND_DYNAMIC_MINORS is not set
Use alsamixer to unmute the necessary channels
Use aplay to play a soundfile (here this doesn't work yet).
esd can be loaded, too
For kernel 2.4.x with OSS
In the kernel you need sound-Support (sound.o,
soundcore.o) and the Soundblaster-module (sb.o)
Run sndconfig (the card is not detected automatically) and select manually
If you use Debian, run update-modules.
In /etc/modules.conf (in Debian: /etc/modutils/sndconfig and /etc/modules.conf)
you will find the following lines (of course you can insert them by hand
without using sndconfig).
alias sound-slot-0 sb
options sound dmabuf=1
alias synth0 opl3
options opl3 io=0x388
options sb io=0x220 irq=5 dma=0 mpu_io=0x330
The following two lines are not necessary, if you don't need the mixer or load
the settings in any other way.
This is my XF86Config-4.
As a pointer-device I use the PS2-device, not gpm, because gpm often runs amok
and I don't lose any functionality because there is no third mousebutton.
The display is switched off by DPMS when the lid is closed. Go to a virtual
console and run chvt 7 && xset dpms force on -display :0 to switch
it back on.
I tried to use one of the One-Touch-Buttons and hotkeys to do this
but it didn't work (see hotkeys). If you manage to
automate the waking up of the display, please send me an e-mail.
Run it from the command-line or via ~/.xinitrc or
~/.xsessionrc each time you start the X-Server.
Add to/Modify /etc/hotkeys.conf:
NB: the third key (keycode 113) interferes with the AltGr-Key, so each time the
AltGr-Key is pressed it is recognized as keycode 113 and the corresponding
program is being started. Since I need the AltGr-Key I disabled this
The same problem exists with the right Control-Key and
keycode 109 but I rather want to use the first Hotkey than the right
Control-Key (and btw, to start an Eterm by pressing the right Control-Key is
very comfortable :-) )
This is affected by the Xkb-Settings of the X-Server, so you can perhaps find a
better solution for your needs by playing around a bit with
XkbModel and XkbVariant.
With ACPI disabled (and APM-Support in the kernel) I can activate an APM-Mode
by pressing the oval button in the middle of the keyboard. I suppose the laptop
enters the suspend-to-RAM-state.
When waking up again I have to unload and load again the module for my network
card, then I have to bring the interface up again.
See below my scripts doing all the APM stuff.
If you use gpm you would have to restart it several times in order not to make
it run amok. That's one of the reasons why I am not using gpm on this laptop.
---- /etc/apm/suspend.d/everything ----
# switch from the X-server to a text-console
# if the X-server display is active when suspendig or shutting the display it
# can only be woken up with 'xset dpms force on' by a User who is logged in via
# for that the X-server display has to be active and the DISPLAY-variable set
# to ':0' (or whatever number the X-display is)
# Stop the PCMCIA-subsystem
---- /etc/apm/suspend.d/everything ----
My PCMCIA-Card needs the modules removed and reloaded by hand.
With other cards it should be enough to take out the card before resuming and
to plug in the PCMCIA-cards after the pcmcia restart (this works eg with my
WLAN-card perfectly well).
Do not switch back to X autmatically in the resume-script as this will clutter
up the screen with funny coloured dots and will require a reboot or at least
Once I tried ACPI. The fan would only run at every second boot or even less
often (with all necessary modules loaded, of course). The CPU even got that hot
that the laptop was switched automatically. After that I knew why I used APM.
With a 2.6 kernel I don't have those problems when ACPI is compiled in the
kernel, but it doesn't work neither.