Introduction16 Apr 2003
Here is a brief summary of hardware:
- Intel Mobile Celeron 2.0 GHz, stepping 7
- 256 MB DDR SDRAM
- 14.1 TFT screen
- 30 GB Hitachi DK23EA-30 Hard Disk
- Toshiba SD-C2612 8x DVD Drive
- ALi 5229 (1533 PCI-ISA bridge) ATA-100 IDE Chipset
- ALi M5457 AC-Link Modem (Conexant?)
- ALi USB 1.1 Controller
- ALi M5451 AC-Link Sound Chip
- National Semiconductor DP83815 (MacPhyter) Network Chip
- ATI Radeon IGP 340M (RS200) Graphics Chip, shared memory architecture; 8, 16, 32 or 64 MB video RAM
- ATI AGP Bus
- O2 Micro OZ6912 Cardbus Controller (PCMCIA)
The notebook was shipped with a faulty battery (made by Motorola), so I had to wait for the new one to arrive before I could really use it. Also, the new BIOS 1.73 is available from HP web site. I recommend you get it.
Before ACPI and the new BIOS, every time I'd turn the notebook off, it would get turned on by packets on the network, although those were not wake-on-lan packets. Not sure if this was BIOS or ACPI issue, but it was nonetheless there.
This machine has been upgraded to 768 MB of RAM by using Kahlon 512 MB SO-DIMM.
This notebook has been retired, so any updates to this page are unlikely.
Fedora 7 Live RC2 CD boots fine on this notebook. That's the only testing that's been done with this new code.
Fedora Core 5
Upgrade from FC4 using
yum was performed without issues. Only a few things are worth mentioning here:
- suspend to RAM doesn't work properly; there is now video on resume, but the machine eventually hangs (this is when using built-in
- suspend to disk code is now compiled in, and it used to work properly as of kernel
2.6.15-1.1909_FC5; as of about
2.6.15-1.2032_FC5it is broken again and it occasionally hangs the system on resume; this is using the built-in
pm-utils; given that
suspend2is much faster, reliable and better looking anyway, I recommend that you don't waste your time with vanilla suspend to disk (a.k.a.
- frame buffer console works OK with
radeonfb; to put
radeonfbin your initial RAM disk, place
/etc/sysconfig/mkinitrdfile and rebuild
initrd(this will be done automatically later by the kernel upgrade process)
- suspend2 is your best choice; as usual, get your patches from http://www.tuxonice.net/ (current version is 2.2.7); or, get this patch (based on 2.2.7) for the source kernel RPM currently available (please note that patch for 2145 hasn't been tested on this
notebook yet and patch for 2356 is based on FC6 development kernel, which is
in turn based on 2.6.18-rc1 and suspend2 22.214.171.124 and is also untested):
then build with:
rpmbuild [--sign] -ba --target=i686 kernel-2.6.specand enjoy; I don't supply kernel RPM packages because they are simply too big
- you will also need new
mkinitrdRPM, that actually enables resume functionality in
- you should also get the
suspend2-useruipackage, which provides text mode userspace UI for suspending and resuming:
- and don't forget the
pm-utilsdoesn't work as well; you can download RPM packages from here:
- using PS/2 mouse together with the touchpad isn't recommended - it may crash your X occassionally; use a USB mouse instead
Fedora Core 4
Fedora Core 4 installed nicely on this notebook.
- suspend to memory (from single user mode) does work, but there is no video (there may be usable workarounds, but I didn't explore these much as I prefer suspend to disk anyway); suspend to memory from run level 5 leaves the machine in unusable state after the power is turned back on
- suspend to disk doesn't work with FC4 kernels (not compiled in)
- suspend to disk works perfectly with
suspend2(available from: http://www.suspend2.net/) and kernels provided by Matthias Hensler: http://mhensler.de/swsusp/; make sure you get
hibernateutility as well
- Synaptics touchpad is fully supported and you can use it together with the mouse, if you configure your X to do so
- Radeon driver works in 2D accelerated mode and direct rendering (DRI) is supported
Fedora Core 3
Fedora Core 3 installed nicely on this notebook.
- there is a problem with shutdown up to and including
kernel-2.6.9-1.681_FC3; vanilla kernel 2.6.10 does not have that problem, so we can expect that future FC3 kernel won't have it as well; this is no longer a problem with
- suspend to memory (from single user mode) does work, but there is no video (there may be workarounds, but I didn't explore these much as I prefer suspend to disk anyway); suspend to memory from run level 5 leaves the machine in unusable state after the power is turned back on; this is for vanilla kernel 2.6.10
- suspend to disk doesn't work with FC3 kernels (not compiled in); vanilla kernel 2.6.10 suspends to disk from single user mode (and comes back OK), but that doesn't work from run level 5; attempts to compile suspend to disk
shipped with Fedora kernel
2.6.11-1.14_FC3, resulted in the kernel that crashed the notebook during suspend - I don't recommend using that (I guess Red Hat folk don't as well for similar reasons)
- suspend to disk works perfectly with
suspend2(available from: http://www.tuxonice.net/) and kernels provided by Matthias Hensler: http://mhensler.de/swsusp/; make sure you get
hibernateutility as well
- Synaptics touchpad is now supported
- Radeon driver works in 2D accelerated mode; DRI (direct rendering) works as of
xorg-x11-6.8.2-1.FC3.13, but you'll have trouble with console switching (i.e. Ctrl+Alt+Fn) - the video freezes; also, DRI doesn't work with suspend to disk described above; unless you really, really need it, it is better to disable it for now
Fedora Core 2
Fedora Core 2 installed nicely on this notebook (upgrade from Test 3).
- Radeon chip doesn't get detected, but if you force
radeondriver, it'll work fine; edit the configuration file manually and you should be set; DRI doesn't work with this chip, but the display is reasonably fast; BTW, I haven't had much luck with
VESAdriver - it would occasionally hang the machine; configuration with the
radeongraphics driver and
synapticspad driver is here:
- touchpad only works as a PS/2 mouse; however, if you load
synapticsdriver, it has all the features again; the RPM for the
synapticsdriver is here (Note: RPMS are not signed):
- suspend to memory does work, but the machine won't resume; I've opened a bug for that; suspend to disk does nothing yet
Fedora Core 1
Fedora Core 1 installs cleanly on this notebook and things are looking promising. Here is a brief list of impressions:
- Radeon chip doesn't get detected, but if you force
ATI Radeon (generic)driver, it'll work fine; check
redhat-config-xfree86 --helpif you don't want to edit the configuration file manually
- ACPI is in the kernel, but you have to specify
acpi=onin the kernel boot line to get it up; you also might need to manually load any required modules
- kernel seems to be more snappy
- GUI seems to be more snappy (GNOME)
abiwordwon't start due to some X errors, but you can fix that by running
abiword -geometry 800x600
- I have tried an ancient 33.6 kb/s PCMCIA modem and it was detected and configured without any intervention
- everything else seems to work as before or better (for me)
Red Hat Linux 9
Graphical installation might have a few hickups (read: lockups), so I recommend using the text install (i.e. type
text when prompted for install type). I still fail to understand what's the go with introduction of more points of failure (i.e. GUI install) into the installation process, but it seems marketing is more important these days :-(
Video gets detected as VESA, but you'll have to pick the resolution yourself as the monitor type (i.e. the LCD screen) doesn't get detected. I found "Generic Laptop Display Panel 1024x768" to work just fine. VESA mode works OK and it is reasonably fast for regular work.
From what I've seen on the web, it should be possible to run the Radeon adapter in the native mode, with the Radeon driver and without any patching. A nice article about that is here: http://cybersym.com/linux-ze4100.html.
However, there is a patch for XFree86 version 4.3.0 that properly detects the chip (here is the original URL I found: http://email@example.com/msg03279/x430_radeon_1_igp.diff). I have gone down that road and applied the patches to XFree86 source RPM in order to create the new RPM release of XFree86, in this case release 3. The associated files are here:
Drop the first file into
/usr/src/redhat/SOURCES after you installed
XFree86-4.3.0-2.src.rpm and unpack it. Drop the second one into
/usr/src/redhat/SPECS directory, back up the original spec file and unpack this one. Then run:
rpmbuild -ba XFree86.spec
This is a lengthy process (at least on my 1 GHz Athlon) and requires a few development RPMS, so be patient and persistent. Both the binary and new source RPMS will be built.
redhat-config-xfree86 still won't detect the chip after this patch to the XFree86 RPMS, but you can pick it manually as "ATI Radeon (generic)". You'll have to set the video memory size, as this does not get detected automatically. In my case this was 16 MB. The "Enable Hardware 3D Acceleration" doesn't really matter. As far as I know, the ATI AGP is still not supported by Linux kernel, so even if you pick the option, it won't really work. As the matter of fact, this is explicitly disabled in the patch, so ticking the option might look nice, but does nothing.
I have found Radeon driver to be faster then VESA and cleaner too. There is no framebuffer residue. However, there are some reports on the web about problems with IGP 340M chips under XFree86, even with this patch, so be careful. I haven't had any, but I don't do graphics intensive work.
An interesting piece of software is
xbrightness, which as its name implies, sets the brightness of the screen. It works a bit different then XFree86 supplied
xgamma. If you want to give it a try, the URL is here: http://wildspark.com/xbrightness/. You will need XFree86 developement environment to build it.
ACPI (Advanced Configuration and Power Interface)
The Red Hat Linux 9 kernel is 2.4.20-9 (from the updates) as of this writing and its ACPI support is not up to date. The latest downloads from ACPI project web site http://acpi.sourceforge.net/ are for 2.4.21-rc1 kernel and they don't apply cleanly to this kernel. However, the ACPI patch maintained by Con Kolivas, available here: http://users.on.net/~ckolivas/kernel/, does apply if one line in the patch is changed. The patch for the patch can be found here:
So, if you install the
kernel-source package, apply Con's ACPI patch modified by the above patch and enable ACPI, build and install the custom kernel (it will be called 2.4.20-9custom), things will start to look better. The GNOME provided Battery Charge Monitor will start showing the correct status of your battery.
A sample kernel configuration file (
.config) can be found here:
The options in this file might not be what you want, so unpack it, copy it into
.config in your kernel source, run
make menuconfig and enjoy.
You can get the ACPI deamon from here: http://acpid.sourceforge.net/. It is a relatively small piece of software that listens to ACPI events and is capable of executing whatever you want at those events.
Once you've tried Con's patches (http://users.on.net/~ckolivas/kernel/) that improve interactivity of your desktop, you'll never want to go back. Red Hat supplied kernel is, unfortunately, quite a bit slower in responding to your mouse/keyboard and X/GNOME runs significantly slower on it then on CK (Con Kolivas) kernels, so having a custom kernel is very nice. However, Red Hat kernel does come with NPTL (Native Posix Threading Library) support, which works wonders for threads on Linux. Getting NPTL into a stock 2.4 kernel or into a CK kernel is no trivial task.
Update 07 May 2003: I have been somewhat successful in porting the interactivity changes into Red Hat shipped kernel. Check out the software page for the required patch. This patch includes ACPI stuff as well. The configuration file I used for this kernel is here:
If you go with it, you can skip reading the rest of this section.
Because I wanted to have both the good interactivity and NPTL, I have decided to use a development kernel 2.5.68. It does come with its own set of headaches, but it is worth it. Here is the configuration file I used for ZE4201:
It is worth noting that 2.5.68 kernel comes with decent ACPI support, so all you need to do is enable it (which I did in the configuration file). Again, you probably won't like my kernel options, run
make menuconfig to customise.
The problems with kernel 2.5.x on Red Hat Linux 9 that I have encountered so far are:
- modutils: This package, as supplied by Red Hat, doesn't support all the stuff that's required by 2.5.x kernel. Actually, new
modutilsdoes quite a few things differently and if you are tempted to upgrade, be aware that things might break if you ever want to run 2.4.x kernel again. For instance, upgrading Red Hat kernel RPM with new
modutilsinstalled (http://www.kernel.org/pub/linux/utils/kernel/modutils/v2.4/) will render your
initrdunusable by the upgraded kernel. In other words, you'll most likely get a kernel panic on the next boot. Also the
insmodprogram won't like 2.4.x kernel as well. I have avoided upgrading
modutilspackage by not using modules in 2.5.x kernel.
Somewhat related to this, there will be a few error messages emitted by the old
modprobeduring boot. They are harmless, but if you're pedantic, edit
/etc/rc.d/rc.sysinitfile and redirect standard error into
rc.sysinitfile is here:
rc.sysinitwill attempt to load modules
mousedevinto the kernel. Since there will be no modules to load, you can put this in
alias hid off
alias keybdev off
alias mousedev off
That should suppress the error messages.
- rpm: There is a known issue with
rpm-4.2-0.69under newer 2.5.x kernels. This is related to NPTL stuff and can be avoided by forcing
rpmto use old LinuxThreads instead. To do this, run
LD_ASSUME_KERNEL=2.2.5 rpm ...
I have this in
/etc/bashrcfile to avoid typing it all the time:
# Workaround for rpm vs. kernel 2.5 issues
alias rpm='LD_ASSUME_KERNEL=2.2.5 rpm'
alias rpmbuild='LD_ASSUME_KERNEL=2.2.5 rpmbuild'
/etc/cron.daily/rpmruns a job that builds a list of all kernel packages available on the system and stores everything into
/var/log/rpmpkgs. Again, apply the same:
LD_ASSUME_KERNEL=2.2.5 rpm -qa ...
This trick will get your IBM JDK 1.3.1 working as well. Simply edit
jre/bin/javafile in the JDK, find the
LD_ASSUME_KERNELpart in it and make sure it gets set all the time, not just when certain conditions are met. I have found Sun's JDK 1.3.1_08 to be faster then this JDK on Red Hat Linux 9, so this might not be necessary at all, unless you really want IBM's JDK.
Network card gets detected and works fine under the stock kernel. It also works fine with compiled kernels.
IDE chipset gets properly detected too. It is reported as ALI 15x3, which is fine and works well.
Sound hardware gets detected fine. I don't usually use sound (where I work silence is appreciated :-), but I have tested a few sound applications under GNOME and they all worked OK. The test was done under 2.5.68 kernel with ALSA drivers for ALi 5451 sound chip.
I haven't tested the modem at all because I don't use it. My understanding is that drivers are not part of the kernel, so you are on your own here.
Also, I don't have any PCMCIA cards, so that's not been tested by me either.
As I play with more stuff, I'll report back here. One thing to notice is that I have tried Red Hat Linux 8.0 on this hardware too and it was OK. However, version 9 seems much faster, so if you have it, don't waste your time on 8.0.
Overall, I'm happy with the way this notebook works under Red Hat Linux 9.
Copyright © 2003 - 2007 Bojan Smojver, Rexursive.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the licence is here.