danleff

That is one solution that I saw. Depends on how the router is set up. I just installed Madwifi on my Mandrake system using managed mode and WEP. If the wep is written in asci or hex makes a difference how you insert the wep code. I got into my router's config program and found that mine was hex, so just inputing the numbers (in my case) worked fine in managed mode.

A couple of things that I can think of. Did you happen to install Win XP after RedHat and then try to recover lilo afterwards? Did you happen to change the order of the partitions to make room for RedHat atthe beginning of the drive? Is this a Dell or Gateway system with the hidden recovery partition and Win XP was pre-installed??

If you have Mandrake installed on the primary master hard drive along side of XP, ignore the Windows entries after the first that shows. Mandrake tends to find any fat32/NTFS partition that it thnks has any trace of Windows on it and creates an entry for the partition.

Yes you are correct. So called winmodems do not have a controller onboard, but are designed to operate off the motherboard's resouirces. They are made for, and have drivers for Windows. Without knowing what the exact model of the modem is, it is difficult to say if there is any posibility of it working in Fedora. If Fedora did not pick it up, then it is likely not going to work. For someone starting out in Linux, it will save a lot of headaches if you go out and buy a hardware modem. They are harder to come by, but worth the effort. Most external modems will work. Look for modems that do not say winmodem on the box, or that state that they work in Linux. If you buy one at your local computer store, ask a salesperson, telling them you need a modem for Linux. That way if it does not work, you can easily take it back. DapperDan has had some luck in this regard (finding modems that work). I have not used one in quite some time.

What I come up with is the Pragmatic modem. The snapshot was helpful, thanks. This driver is built for the 2.4 series kernel in Linux. I bet you have installed the default 2.6 kernel? If you are not sure, type in uname -r in a console and see if the output is something like... 2.6.xx-mdk. See this article. I do not know what the status of these modems is in Mandrake, perhaps someone else has an idea. But, I bet that there should be a fix somehow.

See the responses on your other thread

Go to a console and sign in as root user. Type in /usr/sbin/alsaconf Follow the directions. See if your card comes up, which should be C-Media CMI8738. Make sure that you then check to see if the volume is turned up, either in kmix (using kde) or alsamixer (again in the console) usr/sbin/alsamixer Pop in a cd and see if the sound comes up.

We need a little more information. Is the Pragmatic the usb, isa or pci version of the modem? The drivers. What is the file name of the driver that you have? Or better yet, where did you get them? The easy answer is to get a linux compatiblr modem, a so called hardware modem. This modem is a soft modem. it may work in linux with some effort, but the easiest solution is to get a hardware driven modem, one with the chipset on the modem itself, rather than one that uses the motherboard resources to drive it.

What I suggest is not worrying about getting the latest in software (packages), but use the ones that are easily installed through the control center's install process. The new version of wine is alpha, so you can expect some problems. Anyway, with wine, you need to uninstall a previous version before trying to install the newer version. The new version is a compiling package, which means that you do it basically by hand. It's best to get comfortable with using Mandrake's rpm version before diving into installing packages from source. What's different about Linux is the menu system. All programs are not installed in a single program section in the menu, rather they are sorted by category. Look around the menu items and you will get the idea. In other than rpm packages, you often have to do what you already did, add a menu item or desktop item, depending on the installer type that you used. What's nice about Linux, is that you have many options foe software (packages). Mozilla, Konqueror, Firefox, among others. BTW, Firefox comes in a Windows version as well, which you may want to try.

And you did the following? If you already have an X config file working with a different driver (such as the 'nv' or 'vesa' driver), then all you need to do is find the relevant Device section and replace the line: Driver "nv" or Driver "vesa" with Driver "nvidia"

Simply put, RedHat 9 is too old of a distro to recognize your onboard hardware effectively. Either upgrade to Fedora Core 3 or buy a pci LAN card. Get a Realtek or Lynksys card, about $10 USD.

Did you boot into a console (non-gui environment) before installing the drivers by editing the /etc/inittab file and rebooting? What lines did you change in the X config file?

I have to agree. I just tried ndiswrapper and had all kinds of issues with getting wlan0 up correctly on my D-link DWL G520. I use the Linuxant driver in my laptop with no problem. The data given for the ndiswrapper by apropos is on target too. But, on reboot in Fedora---nada. Worked the first time, then on reboot no. I'll try both again and post back.

Yes, it is not a problem with RedHat 9, which uses kernel 2.4. In FC2, which uses the 2.6 kernel, there is a bug with the partition utility and how Mandrake sees the geometry of the drive, relative to the adjacent ntfs partition.

Try this. Once you login with your name and password, type in at the prompt; switchdesk kde If this does not work, take a look at this post.

There is also an issue with FC2 and having Windows XP with the NTFS filesystem. Can you boot into XP? How did you install FC2, by using the partitioning utility in FC2 during the install and borrowing space from the XP partition, or by allowing the FC2 partitioning utility to make the FC2 partition(s) next to the NTFS partition?

OldSpiceAP's and paultazzyman's comments are right on the mark. Post some specs. for your system, if possible. If you have a windows based system, such as a Dell Web PC, which runs the mouse and keyboard off of usb, RedHat may have problems with this. Also, boot/install issues can be caused by bad iso images (corrupted or incomplete download) or improperly burned cd's. What cd media are you using, cdrw or cd-r? Also, you need quality media. The speed that the images are burned at can be a factor, also. Yoy need to burn the images at a slow speed, say 4X 0r 8X. The hang that you get can be bios related, hardware (like funky usb mice and keyboards), or a media burn issue. Just for reference, where did you get the iso images from and which iso images (names) did you download?

From what I have read, this is the same issue. older cdrom drive in a desktop, or an incompatible cdrom drive in the laptop that can't lock down the burned cd properly. I also found an interesting read on dma issues here. Although it's an older article, it still is an interesting read, especially for laptops.

You sparked my memory on this. It happens in Mandrake, as well. Laptop cdrom drives are funky about accepting boot cd's at times. I had a 24X in my old lappy that by rights should have worked, but would not boot a boot cd. Switched it out for a 20X cdrom drve and no problems. Same thing with my Thinkpad. Switched the original 24X cdrom drive for the cdrw and it boots an install or bootable cd disk every time. Yes, try the second cdrom first. If you get a Fedora screen that mentions the cd not being an install cd, then swap in cd #1 and hit enter to continue.

Off the top of my head, I may be thing of Fedora, but, at the initial boot screen, are one of the <f> options to set the install screen size? Like <F3> with a default screen size shown? What hardware do you have in the system, in terms of a video card and monitor? Do you know what resolution and screen sizes are supported by your monitor/video card, such as 800X600....? Also, how much ram is in the system?

Wow, that's progress for Dell! I give them one thumbs up Let us know how you make out!

That's what many people say. Wine is fine, except that it supports only a very limited number of windows apps. Even Codeweavers states that it only supports 10 or 11 apps fully. The problem is, that most folks are looking for being able to use fairly complex programs with wine, such as Photoshop and the like. Gaming is coming along and is a work in progress. DapperDan has some tips on Cedega, which is a flavor of wine for gaming. This package seems more promising for gamers. Frank's Corner is a good place to start in able to get a good idea what the status is of various flavors of wine.

Ahh...sata! That makes sense! Sata drives are detected as scsi drives in the bios. I just installed one on my mew board. The filesystem is corrupt, probably based on the improper shutdowns. How your version of Linux detects the sata interface and the drive may be at issue. What filesystem seems to be at issue, ext3, reiserfs? And, what distro are you using? I bet the diagnostic software that you used might be windows based? If so, it may not also like the Linux partitions, or does not recognize them properly. I read in another post that some Dell systems may have issues with the correct detection of sata, at least that sata is not enabled in the bios by default. This would be interesting. I had to enable my sata via a jumper on the motherboard, on my Asus board. Just as a note, my new Maxtor sata drive was giving me headahes setting it up just as a data drive. Maxblast software failed to set it up properly (realize that the software was released in 2003). It rexognized the drive fine (drive id) but failed to format it correctly. I hope Dell will be of some help and not state that they don't support Linux. They do! If the tech tells you this, insist on speaking to a Linux tech.

Your problem most likely is a piece of hardware attached to the system. I have this problem with my dvd drive trying to read dvd disks. Funky cheap drive! In your case, if the i/o errors are limited to the sda drive, then it probably is a usb device attached to the system, not the hard drive (unless you are booting off a usb hard drive). Do you have a usb stick attached to the system? If so, it does not like the file structure on this drive. If you remove the device, then I bet the sluggishness would disappear. The other possibility is a zip drive issue, if one is attached to the system. A malfunctioning drive, or zip disk that it does not like. Remove the zip disk and see what happens.

How did you burn the dvd, as a data disk or did you burn it as an image (in Nero file-->image)? If you are not sure, when you look at the dvd disk's contents, do you see just the iso file, or a bunch of directories and files? The other issue might be that the dvd did not download correctly. What size is the iso image that you have. Finally, what version of Windows are you using? I assume that you downloaded the iso to a directory on the windows drive?