Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
I've just installed Fedora Core 6 on my Fujitsu N5000 series Lifebook (Pentium 4 processor). The keyboard is not functioning properly (some of the keys don't work, eg: R, T, F, G, and B) so I'm using a generic USB keyboard as a workaround.
I am experiencing several problems one of which is this: At bootup time this system seems to go through all of the initialization routines the last one being HAL. At this point all I see is a blue screen. I have tried several workarounds. First attempt is to interrupt the initialization and reply "n" to all the prompts. This allows the system to startup X-Window and I'm able to login. To avoid having to go through the interrupt processing at bootup, I have changed the startup parameter in the inittab from 5 to 1. So, now the system boots up in single user mode.
I also tried to bootup on runlevel 3. And ran into more problems. First few attempts, the system did not recognize the interrupt requests but continues with the initialization process. Then comes HAL. I see the following messages on the screen:
Starting HAL daemon: hda: dma_timer_expiry: dma status = 0x24
hda: DMA interrupt recovery
hda: lost interrupt
hda: dma_timer_expiry: dam status = 0x24
hdc: lost interrupt
hda: DMA interrupt recovery
...
And so on.
Can someone suggest what might be my problem.
[Note: Several years ago I installed Red Hat Linux 9 and I can still boot that system up with no apparent problem.]
Try adding acpi=off to your kernel boot parameters and see if that helps. This was a widely reported problem early in the days of 2.6 kernels if memory serves.
I appended the "acpi=off" to the "kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb quiet" line in the /etc/grub.conf. Rebooted to run level 2 and now I get the following message: "unknown bus type 2." [The same message is repeated over and over.]
I was able to do more searches on this problem and ran across i586 vs. i686 issues. I decided to run modprobe as follows.
#modprobe acpi-cpufreq
FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.18-1.2798.fc6/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device
I didn't notice this error message during the boot process. I'm not sure how to address this problem. Do I need to use a different kernel? If so, how would I go about doing it?
Following is the uname -all report:
#uname --all
Linux fanihi 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 i686 i386 GNU/Linux
[I have a Fujitsu N5000 Notebook series, Pentium 4 Processor. I don't remember how to get that info from fedora but from Windows/XP I have this info: Processor Type: x86 Family 15 Model 2 Stepping 9, Processor Vendor: GenuineIntel, Number of Processors: 2, Physical Memory: 510 MB]
You can't load any of the acpi modules if you have acpi=off as a kernel parameter... If everything else appears to be working you might want to consider trying to use apm instead of acpi.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.