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.
No, it all still responds, it just sits there at the last bit of text I quoted, cursor flashing. Some method of punching the keyboard around the SysRq key produces some output that means very little to me, and the pressing the internet keys on the keyboard produce a message something along the lines of 'key input [hex value] not recognised'
Before I can think about installing this, I need to find out why the hell that happens, and I also need to know how to specify nodma each time I boot once it's installed, else it's even less use than this.
How do I get at that if I can't load the OS? I'm going to have to do it after I've installed it I guess. I don't know very much about working Linuxd yet, hence the newbie forum.
I'm assuming that the UDMA capability was added after 2.4.18-3, and it doesn't work with my device. Why not, and is there anything I can do later to make it work? Failing that, what speed will my disk be running at with it switched off?
Try setting everything in your bios to a fail-safe default. Then make the change in your bios that allows you to boot from CDROM. Then, use the newest CD/RW/DVD drive you have in your system to boot from disc1. When linux fails to install, I would have to suspect a hardware misconfiguration and that is not something you can fix by fussing with the options in the bios. You shouldn't have to disable DMA like that to get linux to install.
I wouldn't recommend turning off plug & play because your windows partitions will need that option to be on.
I had previously suspected a bad IDE cable, but that is only one of a dozen possibilities for a real physical problem. You could have the jumpers on the drives set wrong (trust me this can happen to anyone), or you could be using the wrong kind of IDE cable, or you could be plugging your ATA33 drive into a channel that does not fully support ATA33. It would be helpful to know if you have 2 or 4 IDE channels on your board (2 possibly being higher-speed than the others), and which of these you are using for your drives. Just out of curiosity, which motherboard are you using for your linux machine?
I think I'll abandon this whole idea until someone can sort out their software. It's obviously not my machine due to the volume of other people, including some who have posted to this forum, who have had the same problem and never solved it.
I did want to learn Linux properly, especially as seeing how I'm using it on my Software Engineering degree course at university, but after wasting two days of my life on it I'll stick to using it there.
So, the last question is how do I remove the boot loader (GRUB) from my system and go back to using just Windows?
It would be wise to keep linux on your system now that it's on there. Since you need linux anyway, depending on the quality of your education, you may learn in college how to get x working and load into a gui like a normal install should provide.
It would be even wiser to try and find out why the x server doesn't want to start. Work it out, spend some time on it. Perhaps you can find an answer to this riddle that as you say plagues so many others.
It's not a waste of time, it's knowledge through experience. As a software engineer you can never have too much of that. 2 days is not a lot of time when you're talking about getting something fixed in linux when you haven't even got a clue how to install the OS properly.
What good is a degree going to do you if you can't solve your own problems? If everybody waited until someone else found an answer, then humankind would be sitting in the trees picking flies off each others' backs. Maybe it's not your time to give back to the community, but think about it.
The simplest way I know to get rid of Grub is to re-install Windows. If you search around you may find a better answer.
To get rid of Grub, boot from a win9x boot disk and at the prompt run fdisk/mbr.That will restore your MBR to it's previous state.
PnP in the bios is usually turned off by default on most of the motherboards I've built with and I never turn it on for any OS.
Ive helped people install Linux only to find out, (after discovering somthing like sound isnt working) that PnP was enabled.
I,ve seen MS take charge of system resources and it ain't a pretty site I like letting the bios do that.
I can't believe this can be classed as an operating system, given that it doesn't operate in any shape or form.
I tried installing it again using nodma. The graphical installation stopped working three times, and the one time it did work, it took two hours and the final result was being unable to startx, as I said before.
I tried in text mode, and it installed OK. It won't load. It freezes at checking for new hardware.
Before anyone blames my machine, IT WORKS FINE UNDER WINDOWS, and in fact I have never seen a machine that is working correctly and which meets the minimum specs that doesn't work to at least a basic level under Windows!
I could go back to 7.3 but I'm so pissed with this whole thing that I'm more likely to abandon it altogether. If I do go back, I can't update the kernel because this will happen again. In fact, I won't ever be able to use a later version of Linux!