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 am having a frustrating situation. After updating my motherboard bios, I was unable to dual boot my system. I run Suse 9.3 and Windows XP professional. Both were living in harmony before the bios update but now whenever I try to boot into Windows I recieve the error "Filesystem type unknown 0x7"
Linux, of course, boots fine.
My system consists of 3 hard drives. The first is an EIDE drive, on which I have Suse. The other two are SATA drives (74Gb and 300Gb respectively), the 74Gb being the main Windows hard drive, the other being used as storage for Windows programs.
Here is a copy of my /boot/grub/menu.lst
# Modified by YaST2. Last modification on Fri Jan 13 07:58:44 MST 2006
color white/blue black/light-gray
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 9.3
kernel (hd0,1)/boot/vmlinuz root=/dev/hdc2 vga=0x317 selinux=0 splash=silent console=tty0 resume=/dev/hdc1 showopts
###Don't change this comment - YaST2 identifier: Original name: windows 1###
title windows 1
###Don't change this comment - YaST2 identifier: Original name: windows 2###
title windows 2
###Don't change this comment - YaST2 identifier: Original name: floppy###
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 9.3
kernel (hd0,1)/boot/vmlinuz root=/dev/hdc2 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off iommu=noforce 3
After doing some research online it does appear that other people seem to have had this problem but mainly with Suse 9.1. I tried the driver update that I've seen on other posts but that didn't work, probably because that was for Suse 9.1 and I'm running Suse 9.3.
Any help with this situation would be greatly appreciated.
As far as I can tell, 0x7 is the filesystem code for Windows NTFS. Must have been a faulty bios upgrade. Did you check your bios for any new changes since the old bios? You can also try to reinstall grub and see if it boots. I'm not too familiar with SuSE but checkout YAST and it should have options to configure bootloader.