danb
01-13-2009, 09:33 AM
Hi everybody, I'm having trouble booting up an old IBM P2. I tried to (re)install Linux on the machine over the weekend, but it seems to have developed more serious problems. I started a thread about the OS install here (http://support.zenwalk.org/viewtopic.php?f=10&t=20547). The current problem is that when the machine powers up, the console looks something like this:
PXE-M04: Hooking bootstrap interrupt 18h.
L 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99
99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99
99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 9
9 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99
99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99
Actually, there are more 99s, about 2-300 in total.
The BIOS is (or was) set to try to boot off the CDROM first, and the "L 99" text appears both with and without a Linux install CD in the drive. I don't know what's currently installed on the hard drive, because there were also some problems with the installation process before the machine ran into the L-99 problem.
As I tried several times to redo the install, more and more of the packages couldn't be loaded because of some kind of corruption. At some point when the OS was (imperfectly) installed, the graphical Linux screen said "cannot open tty output" in the lower left-hand corner, and during later installation attempts, the menus to install the Linux boot loader (LILO) didn't seem to be working right (see the Linux thread for details). I made a new ISO image from the install CD, and its md5 sum matches the one on the site I downloaded it from, so I'm not sure where the corruption could have come from.
The most relevant hardware events that occurred are probably that the CDROM was used for the first time in months, and I had to power cycle the machine several times because it doesn't know how to wake up a crt monitor in power-saving mode. Also, a couple partitions on the hard drive were reformatted.
Other than having to power cycle instead of rebooting, the machine seemed to be running okay on the old OS a few days ago. Can anyone guess what broke? It doesn't seem to be working very well.
PXE-M04: Hooking bootstrap interrupt 18h.
L 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99
99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99
99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 9
9 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99
99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99
Actually, there are more 99s, about 2-300 in total.
The BIOS is (or was) set to try to boot off the CDROM first, and the "L 99" text appears both with and without a Linux install CD in the drive. I don't know what's currently installed on the hard drive, because there were also some problems with the installation process before the machine ran into the L-99 problem.
As I tried several times to redo the install, more and more of the packages couldn't be loaded because of some kind of corruption. At some point when the OS was (imperfectly) installed, the graphical Linux screen said "cannot open tty output" in the lower left-hand corner, and during later installation attempts, the menus to install the Linux boot loader (LILO) didn't seem to be working right (see the Linux thread for details). I made a new ISO image from the install CD, and its md5 sum matches the one on the site I downloaded it from, so I'm not sure where the corruption could have come from.
The most relevant hardware events that occurred are probably that the CDROM was used for the first time in months, and I had to power cycle the machine several times because it doesn't know how to wake up a crt monitor in power-saving mode. Also, a couple partitions on the hard drive were reformatted.
Other than having to power cycle instead of rebooting, the machine seemed to be running okay on the old OS a few days ago. Can anyone guess what broke? It doesn't seem to be working very well.