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.
Have just posted here and solved my problem with partitioning and installing my brand new shiny RH 8.0 and are starting up 4 the first time and boom, back 2 square one...=(
Anyway when i booted for the first time everything was working great until i came to this line:
Uncompressing kernel
.....jada
.......jada
........jada
(This line) amp: BIOS version 1.2 Flags 0x0b (Driver version 1.16)
After thit line, the cursor just stops at the next line and just blinck. Canīt do anything all i can do is rebooting the system??
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
somewhere in the jada jada jada is the _real_ error that locks up your boot process. Post the complete error message and someone here will have better suggestions for you.
BTW, while using phrases like 'gr8' and 'starting up 4 the first time' might make one look 'cool' in a different scenario, please refrain from doing so in a technical forum where it will attract unnecessary attention and discourage people from replying to your post. Proper english is always recommended.
Originally posted by nxny somewhere in the jada jada jada is the _real_ error that locks up your boot process. Post the complete error message and someone here will have better suggestions for you.
BTW, while using phrases like 'gr8' and 'starting up 4 the first time' might make one look 'cool' in a different scenario, please refrain from doing so in a technical forum where it will attract unnecessary attention and discourage people from replying to your post. Proper english is always recommended.
Sorry about the language i only do it beacuse i'm lazy...I'm not trying to look cool...From now on i will use proper english...And i'll post rest of the message when i get home today...
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
Welcome to LQ, s0undLogic.
Quote:
somewhere in the jada jada jada is the _real_ error that locks up your boot process. Post the complete error message and someone here will have better suggestions for you.
I might also mention that I have tried booting into single user mode with grub but I still get suck at that part of the boot process. I was thinking that maybe I should disable apm by using rescue mode but I dont know how.. When I go into rescue mode I dont think im in root cause I cant find the proper directory and file in the /etc folder to disable it.. Maybe im doing something wrong. If anyone responds with any kind of fix please include detailed instructions of commands and whatnot as I'm not good with linux yet... my plan was to get into the GUI and begin learning but I have been stopped in my tracks. Thank you all for your time.
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
Try passing it the apm=off bootparam and see how it goes. If you edited your kernel cmdline to pass it the single option, I assume you probably know how to do this.
Thank you. That worked and I'm finally in linux. Now all I have to do is edit the grub config so that it does that automatically and ill be all set. Who need advanced power management anyway?
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
Good!
If your system doesn't support APM, it probably will work with ACPI. How old/new is it? When you get more familiar with linux, I recommend compiling a custom-configured ( apm off, acpi on ) kernel and running it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.