I looked at /etc/apt/and considered adding there: rpm redhat/9/en/i386 os updates extra rpm-src redhat/9/en/i386 os updates extra as the pointer to the update site.
But ended up commenting these lines out and keepintg the pointer to the original site given in the file, i.e.,: # Red Hat Linux 9 rpm os updates freshrpms rpm-src os updates freshrpms since it up-to-date. The original site for updates, which was suggested in the docs ( rpm ftp://apt-rpm.tuxfamily.org/apt redhat/9/en/i386 os updates extra rpm-src ftp://apt-rpm.tuxfamily.org/apt redhat/9/en/i386 os updates extra is unfortunately quite stale. In this case, I started with the original RH9 distribution and it was Aug. apt-get update (run twice -- they say it is safer to run it twice...) apt-get check apt-get upgrade (it takes a while) The "apt-get" will not upgrade kernel.
acpi_force_32bit_fadt_addr force FADT to use 32 bit addresses rather than the 64 bit X_* addresses.
Some firmware have broken 64 bit addresses for force ACPI ignore these and use the older legacy 32 bit addresses.
For some new users this left their machines outdated or without applications they needed. Now Linux is exponentially more user friendly - to the point where so much is automatic and ¬†that today's Linux hardly resembles yesterday's Linux.
Of course, at the time, most everyone trying their hand at Linux knew they were getting into something that would require some work. But even though Linux has evolved into the user-friendly operating system it is, there are still some systems that are fundamentally different than their Windows counterparts.
This you need to do yourself manually (later in this writeup).
thinkpad_acpi, sony_acpi, etc.) instead of the ACPI driver.
In version 6 Red Hat moved to glibc 2.1, egcs-1.2, and to the 2.2 kernel.
Version 7 was released in preparation for the 2.4 kernel, although the first release still used the stable 2.2 kernel.
acpica_no_return_repair [HW, ACPI] Disable AML predefined validation mechanism This mechanism can repair the evaluation result to make the return objects more ACPI specification compliant.
This option is useful for developers to identify the root cause of an AML interpreter issue when the issue has something to do with the repair mechanism.