LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Suse/Novell
User Name
Password
Suse/Novell This Forum is for the discussion of Suse Linux.

Notices

Reply
 
Search this Thread
Old 10-03-2006, 10:33 AM   #1
redoaks
LQ Newbie
 
Registered: Dec 2005
Location: Poughkeepsie,New York
Distribution: Fedora
Posts: 22

Rep: Reputation: 0
OS/2 kills Suse


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?
 
Old 10-03-2006, 06:19 PM   #2
JoseRR
LQ Newbie
 
Registered: Oct 2006
Posts: 3

Rep: Reputation: 3
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.

Good luck!
 
Old 10-03-2006, 09:12 PM   #3
redoaks
LQ Newbie
 
Registered: Dec 2005
Location: Poughkeepsie,New York
Distribution: Fedora
Posts: 22

Original Poster
Rep: Reputation: 0
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.

Thanks again
Louis
 
Old 10-10-2006, 08:11 PM   #4
redoaks
LQ Newbie
 
Registered: Dec 2005
Location: Poughkeepsie,New York
Distribution: Fedora
Posts: 22

Original Poster
Rep: Reputation: 0
I posted this on hardware as my OS/2 is on SCSI and Linux on SATA-so I believe it's a mixed drive problem Suse is sensitive to, not any problems between OS's.
 
Old 10-11-2006, 03:28 AM   #5
JoseRR
LQ Newbie
 
Registered: Oct 2006
Posts: 3

Rep: Reputation: 3
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).

Best of luck!
 
Old 10-11-2006, 06:16 AM   #6
redoaks
LQ Newbie
 
Registered: Dec 2005
Location: Poughkeepsie,New York
Distribution: Fedora
Posts: 22

Original Poster
Rep: Reputation: 0
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.
Louis
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
e1000 kills me gyrus Linux - Hardware 7 11-16-2006 08:26 PM
[SOLVED] Kate kills my system... JZL240I-U Linux - Software 3 02-10-2006 02:55 AM
10.1 - log out kills X Esenthiel Mandriva 6 10-04-2004 10:40 AM
SuSe 9 kills my RAID array? Dee-ehn Linux - Hardware 1 04-09-2004 07:38 PM
aMSN kills linux angustia Linux - General 7 01-09-2004 09:45 PM


All times are GMT -5. The time now is 08:53 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration