SUSE Linux 9.1 problems

[Valdner]

Hello everyone. I recently purchased SUSE Linux 9.1 Personal and have a few... issues with it:

1) There is no 'make' executable file anywhere. I tried getting GNU make 3.8, but it couldn't ./configure because it says there was no C compiler. I tried getting one, QT, but it needs the 'make' file to be installed. Aaahh!!

2) I installed SUSE Linux to act as a dual boot sysytem. It even repartitioned my Hard Drive and everything. But now, whenever I try to boot Windows, I get an UNMOUNTABLE_BOOT_VOLUME error. I tried doing what the SUSE help files suggested, but that didn't do anything. Microsoft suggests I try this: http://support.microsoft.com/default.aspx?scid=kb;en-us;297185 My question is, can I do that without distrupting my Linux and Windows files?

Thank you very much for your time, and please forgive my newbiness.

[bsh152s]

I hear that's the bad thing about the personal version of Suse 9.1--it doesn't contain a compiler. Not sure about your other problem.

[saikee]

Did you let Suse do an automatic install, allow it to re-partition the hard disk and have your Window partition deleted?

My Suse boots 3 copies of XP and so yours should have no problem too.

If your Suse has an entry for booting Windows then you should still have it.

Can you confirm your Window partition by looking at the command fdisk -l?

Suse uses Grub as bootloader. The file that controls your booting is /boot/grub/menu.lst. Post that file and the information from fdisk -l if you still have problem with it.

Couldn't answer your first question as I got Suse professional and I have no need for anything more than already provided.

[Valdner]

I let it do an auto install and didn't change any of the settings. But, I did make sure that it wasn't deleting Windows.

This is what I get when I do fdisk:
Device Boot Start End Blocks Id System
/dev/hda1 1 5 40131 de Dell Utility
/dev/hda2 * 6 2447 19615365 7 HPFS/NTFS
/dev/hda3 2448 3649 9655065 f W95 Ext'd (LBA)
/dev/hda5 2448 2511 514048+ 82 Linux swap
/dev/hda6 2512 3649 9140953+ 83 Linux

And this is from /boot/grub/menu.lst:
color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,5)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title Linux
kernel (hd0,5)/boot/vmlinuz root=/dev/hda6 vga=0x317 splash=silent desktop resume=/dev/hda5 showopts
initrd (hd0,5)/boot/initrd

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
root (hd0,1)
chainloader +1

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
root (fd0)
chainloader +1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe
kernel (hd0,5)/boot/vmlinuz root=/dev/hda6 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3
initrd (hd0,5)/boot/initrd

[pilotgi]

Here's a link to one of the SUSE mirrors that has the kernel-source, gcc, make, automake, etc. It's a long list so you'll have to look a little for what you need.

ftp://mirror.storagetek.com/pub/systems/suse/i386/9.1/suse/i586/

[Valdner]

Excellent; one problem solved.

Thank you very much!

[CoffeeMan]

I had the same problem back in my suse days, and just go to yast and install LSB (Linux Standard Base) always have this, it is a collection of packages including GNU make. I've got your back.
What I don't get, is if is the Linux Standard Base, how come it doesn't default during the install?
Anyway, make and all of the goodies are on those cds, and they even have java runtime environment, flash player, blender, and an outdated version of Firefox. Good Luck.

[saikee]

Valdner,

I got a feeling that you were using a 3rd party bootloader or boot manager, as I am not sure what your de Dell utility is for.

If you were not using Windows own bootloader before then Suse may have difficulties to dual boot because many 3rd boot loaders work by deviating from the standard setup (for example by shifting up the track number).

Your menu.lst appear to have been compiled correctly.

[Valdner]

To my knowledge, I was not using a 3rd party booter. I bought my dell, and from then until now, I have not really done anything having to do with my boot process. Perhaps Dell uses it's own booter?

Also, I have another question. Have any of you gotten KXDocker to work? I tried getting the rpm off the main site (http://www.xiaprojects.com/www/prodotti/kxdocker/main.php?action=download) , but the link is dead, and I tried getting the source code, but when I ./configure, it says I don't have a C compiler. If someone could send me an rpm that would be great. Or, if someone knows of a superior dock program please suggest it. Thank you very much!

[saikee]

Sorry I use Linux on desktop and none of my laptop got a docker.

[Valdner]

Well, should I just do what Microsoft suggests (chdisk /r)? I guess I just want to get an okay from someone first before I do it, because I don't want it to erase anything.

[saikee]

Valdner,

OK The way I look at it is there seems to be a Dell boot manager in your hda1 and it may not have anticipate an installation by Linux.

I would try to see if I can bring Windows back to life by doing a fdisk /mbr aftering booting up the PC with a Win9x bootable floppy with the program fdsik.exe inside.

If you can't bring Windows back to life then proceed what you want to do, delete and re-create hda2.

If you want to get rid of the Dell boot manager you may have to low-level format the disk and install everything again, afterwise you may have to live with a hda1 that doesn't do anything for you. Linux bootloader resides in MBR or the first track of hda1 only.

[paj12]

I got a feeling that you were using a 3rd party bootloader or boot manager, as I am not sure what your de Dell utility is for.
I just got a new Dell laptop and I had the same stuff. hda1 and hda3 are for the Dell Diagnostics. Basically, you boot off of hda1 and it runs the diagnostics off of hda3. This can check out your hardware and see if anything is wrong.
Well, should I just do what Microsoft suggests (chdisk /r)? I guess I just want to get an okay from someone first before I do it, because I don't want it to erase anything.
Well, Linux may not be able to write NTFS, but Windows can't even read Linux filesystems. You should be okay with chkdsk. If that doesn't yield anything, you could try re-running the Windows XP setup with the option to repair the old installation. That's how I got my XP back when I dorked it up.

[Valdner]

Okay, one more quick question:
Where is the kernal kept in SuSE? Because, I'm trying to install a driver patch and it says it's usually in /usr/src/linux. Well, I checked on google to see if that was true for SuSE, and it said it was. However, when I go to /usr/src, there is only 'packages' there. I tried enabling hidden files and folders, but it didn't help.

[paj12]

You need to install the package "kernel-source". This will put the kernel sources in "/usr/src/linux-2.x.xx-xxx" where the x's are the version of your kernel. There will also be a symlink at /usr/src/linux pointing to this kernel.

[-=Gerrit=-]

one solution to get your windows back is:

use the windows XP instal disk

goto restore (you will get comamnd line)

type

fdisk /mbr

this will replace the MBR by the windows MBR (you will lose your Suse Bootloader).

Dell indeed uses a partition of the system for diagnostics and somtimes for the windows XP install/restore files...

Otherwise try changing a litle thing in the bootloader (some names) that will make it remake it... maybe then it will be solved...