danleff

Yes, check the alsamixer settings to see if the sound is not muted, or set the volume up all the way. Is is a nForce motherboard. correct? Look at the following thread, especially the last post on the thread. http://www.linuxquestions.org/questions/showthread.php?s=&threadid=137883&highlight=a7v8x

Are you using a USB keyboard or PS2 keyboard?

What version of SuSe are you running? Try this first. Put the NIC in another PCI slot, at least one slot away from the video card and one slot away from an ISA slot, if your system has one. Sometimes the system shares resources with an adjacent ISA slot, or problems occur when placed next to the video card slot. In other words, try another PCI slot. See if the boot completes. If you are using an older version of SuSe, then you may need to install the tulip driver. See the following; http://www.linksys.com/support/support.asp?spid=25#otherdist

Do a Google search on amsn and gnomemeeting and look to see if video conferencing is supported. Can you install RedHat RPM packages in your distro?

Because the 3D drivers probably are not in the stock kernel. The newer ATI cards are a pain and the kernels, except for the latest do not have 3D acceleration enabled. Yea, this is why it's good to investigate the distro that you are planning to use to see if your hardware is supported. To give you some examples; http://www.desktop-linux.net/ati.htm and... http://www.gmpf.de/english/ finally... http://www.linuxquestions.org/questions/...mp;pagenumber=1 In your case, the card is supported, but some work needs to be done to enable 3D. Perhaps we have someone who has done this or has a simple solution in SuSe. To make you feel better, or worse, I read some posts where people are also having issues with your modem in Windows XP.

OK, I'm as little confused, but I think that I got it. Don't create anymore filesystems or swap space. Where exactly is root for RedHat now - This is the installation we are talking about, right? Both entries for grub and fstab need to point to the proper root directory for the kernel to boot. This is probably why you are getting the grub error message, it can't find vmlinuz...or what the kernel file is. You have swap space from another installation, so this can be used. Just make sure that one of the partitions for swap space is in fstab. If you can determine where root is, then you need to modify the grub.conf or menu.list to reflect where the root is now, so the kernel is found correctly, when grub attempts to boot. Since you changed partitons, we need to make sure that we have the correct one. Sounds like you are getting good at this, so let's go one step at a time. This is the issue, since you have multiple partitions and linux installations, you need to point to where root for RedHat is currently. And, yes, you can extend the partition later on, with either PartitionMagic or a linux utility, such as qtparted. I prefer these, as they give you a graphical representation of what the disks and partitions look like. But please, don't do this now.

Please be a little more specific about the problems that you are having. In terms of the modem. I hate to say, it will not work in Linux. This, I believe, is a softmodem and is designed to work in Windows only. Many have tried and Motorola no longer has drivers for Linux. There linux driver page is gone. Do a search on Google linux Motorola speakerphone and you will hit a bunch of links. Anybody else have a solution? Maybe someone can prove me wrong. Also, look at the following for more information; http://www.linmodems.org/

Sounds like your root (/) partition designation may be off too in fstab? Is it the root partition that got changed in the process? First stop changing the partitions and determine what your Redhat partitions are. Originally, during the RedHat install, did you set up just one partition for everything, or do you have multiple partitions for RedHat? Post what the partitions are, so we can take a look at them. Make sure fstab points to the correct partitons for each. Boot normally and see what happens. If you added single to the grub menu of config file, remove it, so that the system will try to login to the GUI.

Good question. You are not alone. The soundblaster sound card comes in many flavors, with a number of legacy models. There is a soundblaster module in the kernel, I believe, but whether it will work with your legacy card is the question. There are just to many versions out there. Sorry that I could not be more help.

Yes you can. I did find a little quirk in the install process though. How about giving a little more information on your system. You just need to be a little cautious. Do you have raid on the system? Do you have a linux partiton on the third drive ready to be populated? I found the best way to do this is when the first cd loads, you get a boot prompt. type in expert then hit the enter key. This will accomplish a few things. One it will prevent Mandrake from trying to use any other linux partitions that you may have, assigned to another distro, as the root partiiton for Mandrake, on the other drives. Go though the install process until you get to the partitioning menu. Choose custom partitioning. Look at the diagrams, which will list your drives and partiitons. Highlight the partition that you want to use (or empty space) and either let Mandarke divide the space automatically, or choose the mount point yourself and assign root to the partition, as the mount point. This should go well, but if you find that Mandrake won't let you assign root as the mount point, or that root has been assigned to another partition on the first or second drive, back out of the partitioning scheme and try again. If you don't chose the auto partitioning scheme, make sure that you assign some swap space on the third drive, usually 2X the ram that is installed on the machine. If this goes well, allow the partiitons to be formatted and go form there. I also found that Mandrake sometimes fails to make a boot floppy outside of the expert mode in myltiple drive systems. This is another reason why to use expert mode. This can be confusing if you have a raid system enabled in the bios, as the drive designations will be different. Make sure that you chose to make a boot floppy, when prompted, just in case. Remember, you need to tell Mandrake if it is OK to insert a bootloader (lilo or grub) to the MBR, If you have another OS, like windows, realize that your windows MBR will be written over, but a windows boot option will be available to you with grub or lilo, when you boot the system. Ask any questions that you may have, so we can help with the process. If unsure, back out of the install process and ask a question. Others may have had an easier solution, but I found the above relevent to my system, which has three hard drives.

Be careful with the kernel upgrade. If you have experience with the 2.6.0 kernel and compiling the drivers/options in the kernel, as well as the package dependencies, good luck and let us know how it works. But, before you do all that, if this board has the nForce chipset, why not install the NVIDIA drivers first and see if this fixes the problems? See this discussion; http://www.linuxquestions.org/hcl/showproduct.php?product=70 as well as this one... http://linuxquestions.org/questions/history/140154

First of all, nice troubleshooting! Secondly, I'm sure there is a way to set the default. I'll have to look and see where it is. The possible issue is where KDE 3.2 placed the sound config utility and where it is now in the menu system. Before I upgrade, I'll look around and try to find it.

Have you seen the following site? http://www.counter-strike.net/linux_full.html

Thanks for the link! The answer has to be on the tip of my mind. Can you still boot to the older kernel, and if so, do you get the same message? What I am thinking is that it may have been the kernel upgrade and the addition or absence of headers for the kernel version, although the modules et al should have been added during the kernel upgrade process. Now that I thnk of it, I may have done the same thing. The ideal would be to know if the sound disappeared after the kernel upgrade or the KDE upgrade. It would be a shame if you have to re-install the NVIDIA drivers after the kernel upgrade. One more thought. Did you do the install from a console window or Gnome, or though the old KDE?

Yes, you can remove the lines that you do not want. Just be careful to keep the linde structure and only remove the items that you do not want, seperated by a blank space. Make a backup of the menu list before you do this, just in case. Also, realize that the extra option to get into the old kernel is there just in case the new kernel fails. This way you have the old kernel menu item as a backup.

You may help me out with this one. It seems to be a KDE 3.2 issue. Same thing happened to me when I installed KDE 3.2 in Debian. Got to be a KDE issue. What happens when you login to root? Does the sound work w/o the message? By the way, how did you install kDE 3.2? Via the console or is there an apt/yum repository?

Have you seen the minidiscs yet? Are they the real minidiscs, or the Sony plastic encased ones?

Ok, then I assume that you have your drives/partitions that you want to share in Win 2000 marked for sharing. I never used this distro, but let's try something. Right click on the desktop and make a link to URL. In the url box, type in smb:/ yes, that is one slash. Then double click on the icon and see if your workgroup comes up for the Win 2000 box. If so, double click on the workgroup name and see if the share drives come up.

If you want to order the CD's, I just did following a link from distrowatch. Cost me $17.50 with shipping. http://www.linuxcd.org/view_distro.php?&typed=1&id_distro=46

I have never installed from a hard drive, but right off I see some potential issues. Could you give us a link to where you got the fedora ISO's? Just putting the iso files on a hard drive does not make them bootable/usable. I would think that you would have to extract the files to a hard drive, so that the floppy boot disk can find the actual boot files on the hard drive, with a program such as isobuster If I am correct, the boot.iso file is a CD boot file. Point to the instructions, as well when you send the link - where the hard drive install instructions are found, and I will take a look. I assume that you do not have a CD burner?

Take a look at the following and see if it helps; http://lists.suse.com/archive/suse-linux-e/2003-Sep/2886.html

Yes it is, beta 2 right now, which I have installed on my system. Unfortunately, mine is not sata raid, so I can't be of much help here.

Don't think that it does. I looked around and the kernel apparently does not support it. SATA raid, correct? Are you usng sata hard drives, or just one hard drive - non-sata? If the latter, try disabling raid and sata in the bios and see what happens. Supposedly Mandrake 10 or Fedora supports it.

I'm no networking guru, but I believe what you want to do is have everying connect to the router. Not machine to machine. If you connect all the systems to the router, you should be OK. The onboard NIC will be the default, probably unless you disable it in the bios. So, if you are trying just to connect to the web, try the scheme that I outlined. One card in each box (of course not in the one that has the onboard NIC) all to the router. Linux only likes to be connected to a router (except for the real network experts). I had the same issue. If I tried two cards, I had to set the default card in the network manager and disable my nForce onboard card in the bios.

OK, what distro are you using and what scanner(s) do you have? I'm 48, so not to far behnd...