Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hehe...ok...i jus wanted to use the pengy smiley but anyway...
Problem:
When I boot up my computer it uses GRUB to choose my OS have three choices, two of them are RedHat8. When I choose either or...it begins to load and the last line where it freezes at...it displays this message:
apm: BIOS version 1.2 Flags 0x0b (Driver version 1.16)
does redhat have the same sort of default boot configuration as mandrake? linux and linux-non bf that would i think account for the two redhat entries...then for the rest all i know is it will have something to do wiht the motherboard itself...
apm: BIOS version 1.2 Flags 0x0b (Driver version 1.16)
The problem is with apm. Correct me if I'm wrong, but the error message is telling that there is a difference between the version of apm known to the BIOS and the version of the driver that Linux is trying to load.
I believe the solution is to turn off apm (power management) until you can get the driver difference sorted out. You should be able to do that in the BIOS setup.
APM is an older power managament...newer systems use ACPI. I've searched on the internet on how to remove APM, and I cannot because APM is not installed on my system. In my BIOS, for ACPI settings...basically everything is "turned off' (just no in those exact words ie: disabled or power off).
This is all the line of code visible to me before it freezes its operations and my computer.
__________________________________________________
Page-cache hash table entries 65536 (order: 6,262144 bytes)
CPU: L1 cache: OK, L1 D cahce: 8K
CPU: L2 cache: 256K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU #0.
CPU: Intel(R) Pentium(R) 4 CPU 1400MHz stepping 0a
Enabling fast FPU save and restore... done
Enabling unmarked SIMD FPU exception support... done.
Checking hlt instruction... OK
POSIX conformance testing by UNIFIX
mtrr:v1.40 (20010327) Richard Gooch (rgooch.csiro.au)
mtrr: detected mtrr: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfda95, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
Unknown bridge resource 0:assuming transparent
PCI: Using IRQ router PIIX [8086/2440] at 00:1f.0
isapnp:Scanning for PnP cards...
isapnp:No Plug & Play devices found
speakup initalized device: /dev/synth, node (MAJOR 10, MINOR 25)
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm:BIOS version 1.2 Flags 0x0b (Driver version 1.16)
___________________________________________________
Any help would be greatly appreciated
Encountered a situation similar to yours; the solution I found, which
involved a change to /boot/grub/grub.conf, might help.
Started with a P4-1.5GHz machine whose 80Gb IDE hard disk was fully
occupied by 2 NTFS partions, booting win2ksp2. Shuffled filesystems
around and used a third party partioning program to repartion the drive
thus:
# fdisk -l
Disk /dev/hda: 255 heads, 63 sectors, 9729 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 958 7695103+ 7 HPFS/NTFS
/dev/hda2 1025 3114 16787925 c Win95 FAT32 (LBA)
/dev/hda3 959 1024 530145 83 Linux
/dev/hda4 3115 5466 18892440 f Win95 Ext'd (LBA)
/dev/hda5 3115 3376 2104483+ 82 Linux swap
/dev/hda6 3377 5466 16787893+ 83 Linux
Partition table entries are not in disk order
#
During subsequent installation of Red Hat 8.0 I used Disk Druid to
specify which partions would be used: /dev/hda3 for /boot, /dev/hda5
for swap and /dev/hda6 for /. I also chose the GRUB boot loader (over
LILO) and specified that it be written to the MBR (master boot record)
rather than the boot sector of the /boot partion.
After installation GRUB could successfully boot win2k but not Linux from
the hard drive. As with your machine, the last lines on the console
were something like:
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
I could boot off of the floppy created during installation, however, and
found that the stanza for Linux in the GRUB boot loader configuration file,
/boot/grub/grub.conf, looked a little funny:
title Red Hat Linux (2.4.18-14)
root (hd0,2)
kernel /vmlinuz-2.4.18-14 ro root=LABEL=/ hdc=ide-scsi
initrd /initrd-2.4.18-14.img
The "root" parameter to the GRUB "kernel" command didn't smell right --
something like failure of a variable/template to be expanded. I changed
this stanza to:
title Red Hat Linux (2.4.18-14)
root (hd0,2)
kernel /vmlinuz-2.4.18-14 ro root=/dev/hda6 hdc=ide-scsi
initrd /initrd-2.4.18-14.img
Notice again that /dev/hda6 was the partition containing / (the root
filesystem) on my installation.
After this change Red Hat 8.0 booted just fine from the hard drive.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.