Suse/NovellThis Forum is for the discussion of Suse Linux.
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 have OS/2 on a P4 system. I installed several versions of Suse-8,9,
and 10.1. They break to kenel panic (unable to sync) and are beyond
CD repair or upgrade-it's a format-reinstall.
This did not happen to Fedora 4, but happens to all Suse versions.
Running 10.1 and 9.3 gives no problems.
Suse is on its own disc, not on one with OS/2.
Anyone know what would cause this?
You may want to check your computer's RAM before doing anything else.
Reboot with your SuSE's installation media and select the option (usually at the bottom of your screen) to check your machine's RAM. If your RAM checks OK (not red-flagged by SuSE's RAM testing utility), proceed to partition your hard disk exclusively with OS/2's partitioning utility. I assume you are using the Logical Volume Management (LVM) available with modern version's of OS/2 - eCS, since the older FDISk version is more Linux compatible (but will not "see" a modern huge hard drive).
Hence, with LVM utility assign a volume to your SuSE and make it bootable --if you are using the LVM enabled Boot manager; do not forget to make another partition for your SWAP file. You may want to analyze the relative position of the volume/partition(s) that you created by pressing F5 before exiting the LVM utility. Note that for the SWAP file you do not need to create a volume --only a partiton. Exit your LVM utility and reboot with your SuSE installation media.
Proceed to install your SuSE in the partition that you confirmed (priorly under OS/2's LVM, when you pressed F5, remember?) and ONLY that partition; also, make sure to install GRUB in that partition --otherwise, you will overwrite your Boot Manager; additionally, select for the SWAP file the partiton that you created priorly. Your SuSE should boot now when selected from your OS/2's LVM enabled Boot Manager.
Notwithstanding if you experience problems booting your OS/2 and/or SuSE again, try the following. Either from within OS/2 or with your OS/2 installation media enter the LVM utility and select your SuSE volume. After pressing the ENTER key, select the option to hide the SuSE volume from OS/2 --this will merely unassign the drive letter to your SuSE partition. Reboot and observe that your LVM enabled Boot Manager still shows your SuSE partition to be booted although no drive letter is assigned.
Thank you for the reply.
This is not a hardware problem-I have run Fedora 4 and Mandrake in the same partition used by Suse.
I have run all three with Warp 4 FP12-no LVM, and with eCS and LVM. The only casualty was Suse, over and
over. FDISK id's the partitons correctly as 82 & 83. I have used bootmanager to boot to Linux in any machine
with both OS's. The Linux installed gets to format its partition.
I just got Mandrake 2007 and am biting the bullet by going with it, but at least it always booted up.
I hope it survives.
My system is mixed SCSI and IDE, dual CPUs (600MHz) --although older than yours.
I used to receive the message that you describe with SuSE --over and over-- until I tested (and subsequently replaced) the RAM. It may not be in vain if you test your RAM with SuSE's utility.
On the other hand, (after testing your RAM) disconnect either of your SATA and/or SCSI drives and attempt the SuSE installation procedure once again. You may also play with the BIOS and/or SCSI LUNs for an indication that allows you to deduce a possible procedure to try.
One piece of advise (if I may, of course), make one change at a time and attempt your SuSE installation. If the change does not provide results undo the change an proceed with another change. When documentation is absent and Internet information is sparse, a methodological approach of trial-and-error is the only option (and a piece of paper to write down the initial configuration BEFORE the actual tinkering on the machine).
I am ALWAYS open to advise.
Since this happens on two entirely different units, RAM is not the culprit-but I have tested it.
I'm leaving Suse in its box as I consider it way to fragile to replace OS/2. Both Fedora and Mandrake
survived when it could not. Unfortunately the unit left with SCSI is at work and I'm not able to tie it up or risk it too much. The home unit is SATA only and runs Suse fine, sans OS/2.
If I get Linux running as well as I have OS/2, I'm going to beat my chest and roar.
I really thank you for the great reply and assistance.