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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Well, I installed FC3 without any problems, then a friend helped me with making the wireless work (he changed kernel i think). my computer ran fine (exept that my sound wasnt working) so i tried to fix it. I downloaded the alsa thingy but didnt get it to work (well i really didnt try much i just made ./configure and then make install gave error)
then, i saw that someone had fixed his sound by adding snd-intel8x0m or something to the hotplug blacklist, i thought: It may work for me! and i tried. while rebooting my computer got stuck, the last line was (about the second ok i think.)
storage network audio
I tried a few times it didnt work, then i tried one other kernel in grub, it booted fine exept i had no network coz it was the kernel without the fix.
Booted windows and found out i could get past this problem by doing acpi=off in the bootline.
now im wondering, why wont linux boot normally even when i removed the line from the blacklist and what is acpi?
ps. if anyone knows how to fix my sound also id be happy (SoundMax Integrated Digital Audio)
Advanced Configurable Power Interface...
And you've learned the first rule of a newbi...
Do not, ever, under any circumstance change even one letter, in one config file, until you properly research the problem and figure out what might be wrong.
You may have to re-install to make things work properly now, but that's jsut practice.
If you take some time to reasearch your hardware and look up the specs, you'll probably find it used acpi to control some of the hardware, and the sound card, and that you'll need to enable it in order for everything to work.
right, now im searching for info on the blacklist thingy but all i get is other ppl's hotplug blacklists, anyone know a good word to add to the search so i find what the thing does and how to undo it? (still thinks its weird that it wont boot even when i removed the line from the blacklist)
there is really no reason why taking the word out didn't fix the problem
i would imagine the thing uses returns in that file to look for new modules to leave out
so try and make sure there are no returns or blank lines
everyone is having a time adjusting to using the new udev package and it sounds to me like fedora boot scritps have bugs but that is only a guess.
putting the device in the hotplug blacklist file so udev does not make it's device nodes in order to make it work ?? wtf? that also sounds like these scripts may not be doing what they think they are doing.
basically the way to use udev is kernel modules are loaded at boot and hotplug events are cued but not run so then later when udev starts it can process the hotplug events and populate /dev
tip: it's alot easier to just compile support for devices into the kernel rather than trying to load modules
till someone gets this bootscrpit mess working -- that way everything just will work