danleff

I use gftp with KDE all the time. However, you may also be interested in the following from KDE.news; http://dot.kde.org/1034719627/1034978411/

Sure. At least for data files, like downloading those large iso files. Each distro usually has one included. I use gftp. What distro are you using?

If you updated the kernel, I bet you have 2 possible choices on the menu, I for the old kernel and one for the new. I'm also guessing. You updated from RedHat 9 to Fedora, and I bet that the two choices could also be one for RedHat and one for Fedora. Does choosing one (highlighting one with the arrow keys) and hitting the enter key) bring up Fedora? Probably the first one is Fedora and the second RedHat. Try choosing the first, as noted above and do you get KDE or a graphical interface (desktop)?

Mandrake 10 beta 1 has kernel 2.6.1 and KDE 3.2. I just installed it and it looks pretty good. See the story in the news archives; http://www.linuxcompatible.org/story25854.html

We can try. First, you mean that Fedora ate your Win ME MBR, so that you are not able to boot directly into Windows, correct? When you installed/upgraded to Fedora, what bootloader did you choose, or which are you usuing, lilo or grub? Do you know what partiton(s) Fedora is on? I'll have to look at my Fedora disc to see if they have a rescue option, But probably tou need to know what partition Fedora root was installed on. P.S. I just looked at the Fedora disc. You have an option to rescue the system, but make sure that you have the partition location that Fedora is on. It did not find my Fedora install, but my situation is a multi-boot system. Also take a look at the following excellent article on Fedora installation; http://www.informit.com/isapi/product_id...nt/articlex.asp Pop in the 1st Fedora disc. When you get the initial Fedora screen, choose F5 to get the rescue menu. Then type in linux rescue as per the instructions. If given the option during the recue, also choose to make a boot floppy. Make sure that the floppy is a clean, formatted disk. Let us know how it goes. Let us know how it goes.

If you were able to read other burned data or images made with the original (self built system) media, then you are probably looking at a media burn issue. For example, iso images burned at faster than 8X. This is a common issue that produces varying results and can be difficult to pin down. Double check the instructions for the CDRW drive for their suggestions on how to set the jumpers. Some drives suggest master or slave, some suggest cable select. I ran into this before. The remote possibility is a bad ide cable. Consider this as well. Also, consult the motherboard's web site to see if they have any faq's on CDRW or CDROM issues. This may reveal some possibilities.

Qtparted should already be on the Knoppix live CD version. Go to a root konsole and type qtparted.

For kernel 2.6.0, you need the module-init-tools package, not modutils, although having the latest modutils package prevents any possible dependency problems when installing module-init-tools.

Not the CD-RW drive but the media. Well, at least if you made sure that you attached the CDRW drive the same way that you had it in the other system, namely if it was jumpered correctly for the cable that it was attached to. In other words, if jumpered for master, that it was on the secondary IDE cable, at the primary connection to the cable (master). Or if set for slave, to the secondary connection on either the primary or secondary IDE. Usually, the issue is funky media. Inexpensive discs. Or, just luck that it worked the first time and not the second. CD-RW media, I have found can be quirky. So, if I keep a disc, or set, I burn them on CD-R media.

Sure, but be aware that the probelm may not be with hardware, but an installation failure. If you would like to post some more information about your system and the install, maybe we can save you some time. By the way, what did you do to clear the hard drive? Kernel failures often are due to lilo or grub not being able to find vmlinuz or a configuration error. Here is a link for the iso images; http://ftp.linuxarkivet.nu/pub/iso/mandrake/9.0/

One or the other. Either it does not like the monitor (which my guess is) or the video card. Sounds like it is trying to configure the wrong vert. or horiz. frequency for the monitor. This is an evaluation copy of SuSe, which I hear is not designed to be placed on the hard drive. If you want to try a CD based version (more up to date) of Linux, try Mepis or Knoppix. Both can be installed on a hard drive if you like it. If one of these run well, then you know the answer is that the SuSe version did not support you hardware properly. If you have the same issue, then you know that using Linux with this monitor will be a problem. But, I'm willing to bet that Mepis or Knoppix will work. Let us know if either one works, then we can go from there.

Good! You know about the possibility of a modem problem. Everything else looks OK. I would suggest the following, since you have access to broadband and a burner. I don't think you would have the best experience with the version of SuSe that you have. It is too old. You can try a few things. If you want to try out a CD based live version of linux to see how it works with your system, get Mepis or Knoppix. Burn the iso image and make sure that the system is set to boot from CDROM first. Give it a test drive and see how it goes. make sure that you burn the image with your writing software, not just the file to a CD-R. They both run off the CDROM drive, so you get a good feel for things. Also, this will telll you if your board is functional in Linux. I just have to say, that some boards, depending on the brand, even with the same chipset, run Linux better that others. Secondly, I would suggest, if you are daring, to try Debian. it's a good distro and Knooppix and Mepis are based on it. Since you have the latest version, you should enjoy the graphical interface. Sometimes, Debian requires a little work to get it the way that you want it. But, it is very stable. If you want to get the system up and running easily, Try Mandrake 9.0 or Redhat 9. Given the hardware that you have, I think that you would like the newer graphical KDE or gome interface in Mandrake 9.0 or RedHat much better than the SuSe version that you have. These newer versions should support the hardware that you have much better. Dapper Dan suggests this all the time, if you have access to broadband - buy a NIC card, such as a Realtek ($10-15) and hook it up via a CAT5 cable to your router. Each distro should pick up the internet connection easily. Good luck and let us know how you make out!

Did you install the module-init-tools package before compiling the kernel? This is a common gotcha in 2.6.0. The 2.4.X kernels use the package modutils and 2.6.0 uses module-init-tools. Also, take a look at; http://www.linux-sxs.org/upgrading/migration26.html

At a console, type su then hit the enter key. type in the root password -> enter key

There you have it!

Hmm...to many variables. So, will the system boot from the floppy? Will it boot from lilo or grub via tha hard drive (without the floppy)? If no, I'm going out on a limb. Go into the bios and disable PNP OS. This is usually found in the bios menu under PNP/PCI Configuration or something like this. Linux has trouble with this setting in the bios. Save the settings and allow a reboot. See if you can boot and at least get a console screen. The problem may also be the monitor settings, which I doubt. If the monitor settings, which should match your monitor's specs., is incorrect, you should at least be able to get to a console. If you get a consile only, log in to root user and then type halt and allow the system to shutdown. Then report back. Memory. It may have worked before, but if different brands or quality/types are used in a system, Linux can have problems with this also. You could be lucky in this regard, though.

I have. If he has PartitionMagic, this would be the preferred utility. I note using the end of the drive, as it is easier to figure out what the swap space partition designation is. Using PartitonMagic assures that partitionmagic is able to read the partiitons later on if needed. You may recall, I did have trouble with qtparted corrupting the partitions, at least seemingly so, resulting int PartitionMagicbeing unable to read the drive. So, if he knows that the last ext3 partition is hda6, for example, then the swap space partition hopefully will be hda7. Adding it elsewhere sometimes changes the partition designations Whatever utilities that he has to view the partitons on the system could be used to id the swap space. I use Linux fdisk very little, but I would guess that doing and fdisk /dev/hda (if this is the drive), then "p" to show the partitons will verify which is the swap. Then add the usual to his fstab. Can't remember the correct utilities/commands right off.

Most likely. Was this system working prior to the redhat install? What monitor do you have? Did you happen to make a boot floppy during the install? Is the ram good quality - is each stick the same name/brand and type?

One thins that I can think of right off. Get Knoppix and use qtparted. Resize the last partition on the drive (from the end), create a swap partition at the end of the drive and add it to the fstab. Is it an ext3 partiton at the end of the drive?

It's still holding! Good luck!! I have one of these on my wife's system. I bought it because it is a hard modem (controller built in). I also have a Diamond Supra Express 56e (external serial connect - NOT the MAC version) which worked very well. Problem is, they are hard to come by. I am fortunate enough to have broadband now, which is great in Linux. If this doesn't work out, I noticed that Computergeeks has an external modem for the same price. It is certified by them to work in Linux.

OK, let me try again. I saw this page also. What would be nice to know, is what CPU and hardware obokos currently has, so that he can choose the right distro to fit the system and his/her needs. Also, this would make sure that he does not have any incompatible hardware, like a video card, or insufficient RAM, so that he can have a positive experience during his install. I find that many problems are caused by funky motherboards that are not Linux friendly, things like insufficient RAM for a distro, or a piece of hardware that is known not to work in Linux. Example, a Win Modem. It's better to know this up front, so he can be prepared for any potential issues.

If I remember fdisk correctly (Windows fdisk, correct?) it is unable to see your Linux partition. So, my guess is that you still have unclaimed space that Windows is unable to see, PartitionMagic will tell you this and allow you to re-claim that space again.

Not unless you want to get rid of Windows. I think, if I understand the problem with sata drives and Linux, it's the ability to recognize the drive in general. In Mandrake, and I believe this also holds true with RedHat installs, you have tqo options. You can allow the install to auto configure unused space. Or choose to use a utility like PartitonMagic to pre-format the partitions. If you want to have a dual boot, system, then you would resize the Windows partiton and you could create an ext3 partition on the remaining space. Then tell the Mandrake or RedHat install to use the ext3 partition that you made. But again, the issue here seems to be the ability of Linux to recognize the sata drive at all. Again, I believe that you can turn sata off in the bios, but you should decide what you want to do before the Windows and Linux install. Either way, back up your important data on the Windos deive before you do an install. This is always a good idea, in case something does go wrong. Also make sure that you run defrag in Windows before making any changes to the partitions, such as resizing, so that you don't screw up and data that might be hanging around near the end of a fragmented Win partition. So, the idea is to have a game plan from the start, depending what you want to achieve, Perhaps someone who has sata drive experience can clarify this more.

Never saw this board before, but I use VIA based boards without any problem. How about giving us an idea about some of the system specs...processor type and speed, amount of RAM, hard drive size, modem make and model and what other hardware that you have on the system. Debian is fine, if you have some knowledge of linux. I would skip the SuSe version that you have and if possible, either download (if you have broadband) the newer version to install off the net... Or you may want to try Mandrake 9.0, if you have enough ram, say ideally 128 mb or more. Its not crucial to have 128, but the system will run better. But, let's see what you have first. Also, will you be using linux exclusively, or a dual boot with Win 98 or Win XP?

Dapper Dan, your going to have to give me a Grub primer. I always wanted to use it, but have my Lilo set up to boo too many distros.