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.
I started my linux journey with a great deal of patience. But I feel like I've been had. And what makes me so frustrated is that I actually paid for my linux (Suse 8.1 pro). If I had gotten it for free then I would have nothing to bitch about. However, when you pay $80 for an OS, you expect it to work right.
Here's my problem :
My linux install does not correctly identify my motherboard's ICH4 chip which in turn makes my hard drive run in PIO mode, among other problems which show up in my 'Available Hardware - KDE Control Module' under the 'Unknown' branch.
I have updated my kernel to 2.40.19 . I have also tried recompiling my kernel. Neither of these worked as far as my problem being resolved.
If you ask me, it's way too much trouble. I feel like an idiot for paying for this kind of trouble. Especially when I'm using components which should give me no trouble at all. My mobo is an Asus P4B533 and the proc is Intel P4 1.7g .
If anyone knows how to fix this, please let me know. The Suse manual is not very well written. There are steps which are left out and it confuses someone like me who is new to linux.
Yeah thanks, I'll give it a try. I'm just aggrivated with Suse. I've been trying to solve this for a few days now, and I have tried the things that I have read about such as compiling a new kernel. I don't recieve any errors, and yet I haven't been able to solve the problem. I think that more than likely I am missing something.
I may be having a problem with configuring the kernel. I type # make menuconfig. I make the settings that I understand the meaning of, such as the processor type. Then I exit and save.
Now I think that I'm having a problem with making my config be used as the boot/vmlinuz.config. I look at this file and it is the default setup (not my config).
How do I replace this file with the settings that I made? Don't forget that vmlinuz is a .config file and the one that I made is called config.in, so I can't just rename the one that I want to be used.
Whic kernel is actually running when you boot the machine? 'uname -a'. If you downloaded the kernel source from kernel.org you need to make sure you change either the Makefile ('export INSTALL_PATH = /boot' is usually commented out, so remove the # at the beginning of the line) or make the change in lilo or grub to boot the kernel from the / directory. I usually change the Makefile as I like to keep my kernel image in the /boot dir.
Ok, I added an entry to my grub configuration so that I could be sure that I was booting off of the new kernel.
The problem still exists. In Available Hardware - KDE Control Module, my 'Unknown' branch it will show items such as my chipset :
Asustek 82845 845 (Brookdale) Chipset Host Bridge
When I highlight it and click the 'Details' button it says :
configured : No
available : Yes
needed : No
Does this mean that It could be used if configured ?
I a definitely suspect that I am missing some step in configuration. Even when I boot the new kernel, it still uses the old 'vmlinuz.config' file. I don't know how to make a new vmlinuz.config that reflects the new kernels configuration that I made when I typed # make menuconfig.
I believe that I might see where I went wrong. When you # make menueconfig, I read on a web page that you are supposed to first load the vmlinuz.config file. That is of course after you have hopefully made a backup of your working vmlinuz.config file. I did not do this right. I will start all over from the begining and see if fixing this gets me any closer to success.
No, I didn't check that. My mistake. I'm a C programmer and have used mostly Microsoft stuff up until now. I'm from the school that says if you buy a real motherboard with an Intel chipset and an Intel processor then you should have no issues with compatability. I did that and thought that I was safe buying quality hardware to work with Linux. As I have found out the hard way, those rules do not apply to Suse 8.1 pro Linux. (at least the kernel version that I paid for).
You have to understand that I am of the mentality that if you pay money for an OS, it should work properly if you use it with industry standard hardware.
How is that in any way unreasonable ?
Hopefuly your next post will help in some way snocked.
you bought a MB with an unsupported chipset, then complain that SuSE doesn't own a timemachine to go forward in time, get a kernel that supports your chipset, then go backward in time and install it on the 8.1 release so that your MB will work properly today. no, thats not unreasonable at all.
Bear with me here, I still have a "Microsoft mentality" as I stated before. I know how simple it is in Windows to solve my problem. You just install an inf file and it's fixed. So my world, up until this point has been easy.
Now that you have pointed out that I with my limited knowledge of Linux (IE, newbie) have overlooked the fact that it doesn't work that way in Linux, I see why my thinking is unreasonable.
I am totaly new to this concept of having to rebuild your friggin kernel to solve this problem, or wait until the rpm is released from your distro and install a pre-compiled kernel. To my way of thinking, that is pretty harry stuff we're talking about here.