danleff

Nice going! 64 bit? Some day for me!

...and Windows will using from Grub, as it stands now? First of all, thanks for posting this, as it helps me see what Fedora is doing, as several folks have had trouble getting Fedora to dual boot Windows with this particular scheme. Let me clarify a little on what you want to do, as I may have misunderstood. If Windows boots via grub, you have a dual boot system. Are you looking to switch over to the sata drive as the first boot device at some point? if so, I see your point. You can use the Windows bootloader to add Linux later on. Trying to set up the system to add linux to the windows bootloader and boot the system via the ide (pata) drive also is complicated and I would not recommend doing this on your primary system. Usually you do one or the other. There is no reason to do both, unless you intend to change the first boot device to the sata drive at some point.

You missed one step. Did you; sudo depmod -a OR sudo /sbin/depmod -a before doing ndiswrapper -m and modprobe ndiswrapper? This adds the ndiswrapper module to the module tree, so SuSE knows that it is there. I assume you are using ndiswrapper that came with SuSE and did not compile the package from source? Also check to see (if you still have problems) if you have the kernel source package installed. A quick way to find this out is to navigate to the /usr/src directory and see if there is a symbolic link to your kernel there named linux. As for what happens next, consult the ndiswrapper wiki installation page.

There are a number of possibilities of what is wrong. Let's walk through the process. What version of Mandriva is this? Yes, this matters, as some have found that they had to boot from the second cd first, then switch out the cdrom to cd #1 and continue. Is the cdrom an internal cdrom drive, or USB? Some systems have trouble booting from an external cdrom drive. Also, reference my article below. Is the cdrom/cdrw that you are booting the disks from the same one that you burned the disks on? Or is it an older cdrom that you are trying to boot of off? One potential problem is a bad downloaded iso image. How did you download the image--> Via broadband or is this a dialup network? Did you verify that the downloaded images were OK, by checking the md5sum of the images? How did you burn the images exactly? See my article here. You have the bios set to boot cdrom first and are not trying to install Mandriva from Windows? Yes, the cdrom will pop-up the Mandriva install window, if you open it from Windows, which some have tried to do before, rather than booting the system with the cdrom inserted. Some have thought that they could install Linux from Windows when the Mandriva window pops up. Quote: I'm FTPing the ISOs down (again) and will try booting/installing from the hard drive. Why are you doing this if you already have the images on your hard drive? Unless you know that the previous ones were bad downloads by previously checkng the validity of the downloaded images.

There may not be a build for your current kernel available. What is the total output of uname -a? What version of Fedora are you running? BTW, I think that you may mean ther kernel version as 1955, which is not the processor type, which would be something like; i386 i486 where, madwifi-kmdl-2.6.14-1.1644_FC4-0.9.6.0-18.rhfc4.at.i686.rpm The red part is the kernel version and the green part is the processor type.

This is why I don't recommend installing Debian for users not knowledgeable about Linux. It takes a little getting used to. The basic installation will install a GUI, but I bet you missed the step. What flavor/version of Debian did you install, sarge or etch? During the installation, you should have seen a list of packages to install, under Installing and configuring packages, you should have checked off; [*] X window system [*] Desktop environment Let me see if I can find a good tutorial on this. Do you know how to use apt-get? If so, see this link. Look at the section; Installing KDE on Debian

This is a double post. Please see the other thread that you started for more information on your wired connection.

Many folks miss setting up the internet connection during the installation of SuSE. At the main hardware window, during the installation of Suse, you could have set up the internet connection. usually it says "not configured" on the line relating to internet. A good, short tutorial is located here. Only follow the directions above Quote: Now, we just need to get the IP address from our ISP. This is quite painless. Open up a terminal window. As root, restart the network by typing '/etc/init.d/network restart'. This step is shown below for a straight internet connection. Ignore the subject lines starting with this text, as this applies to setting the system as a router. This assumes that you are connecting using a wired ethernet card connected to the router. Is this the case with your system?

Figures! I only ran it to a point and did not actually try to complete the process. I hoped that the demo would allow one recovery. No coffee or sugar at the time. If you are daring and technically inclined, see this article. Unfortunately, the gpart link seems dead. I'll keep looking around. I was also hoping that the partimage package in the SystemRescue CD might see the partitions and allow a recovery.

I assume that you read this page? You either compile alsa to run at startup (when the system boots - into the kernel directly) or as a "module" not inserted into the kernel, but started the system boots up. If you choose to compile into the kernel, then you would need to recpmpile the kernel. However, the instructions say; Quote: Most modern distros come with soundcore compiled as a module. You can check this in numerous ways. The easiest way is to type. modinfo soundcore If this command returns that you have this module, then you don't need to recompile your kernel. So, if soundcore is loaded on your system, you don't need to recompile the kernel. This is the basic sound hardware detection module, built into the kernel itself, in your case, as it shows up in lsmod. Alsa is the package that contains the modules that gets sound working for you, not the module itself. It does contain the module for your sound card, any many others. If you look at the result of lsmod, you would see snd-ca0106 as the module loaded (if it is, of course), not a line with alsa. Quote: If I have to recompile the kernel, how do I integrate the new alsa source into the kernel source code from the SUSE 10.0 distribution CDs? You don't. The kernel is already on your system, if I understand your question correctly. I think you mean the kernel installed on your system currently from the CD? You can either look to see if an updated alsa is available in Yast, if you have Yast set up to search the repositories on the internet for updates, or wait for the new version of SuSe to come out, I believe the release date is about March 15. This version will have the newer version of Alsa that should work correctly.

OK, but the discussion here is about a USB modem, not a wireless device. But yes, the Linuxant solution is fine, if the wireless device is supported. Ndiswrapper also works well, if the chipset is supported. My WUSB54G works well with ndiswrapper, so I agree.

Quote: Is there a recommended way (or a way at all) to setup GRUB and NTLDR (Windows XP) boot loaders such that one can jump between them in either direction? Technically yes, but practically, no. Why? You have Fedora set up on the ide drive set to boot Grub. If I understand your post correctly, you have Windows on sata, where the Windows bootloader resides. If you read the recent posts on this subject, changing the boot order works as you have the system set up now, but the better solution would be to correct grub and not switch the first drive designations in the bios. Changing the first detected drive in the bios confuses Grub, as it needs to detect the different OS' on your system, as Grub was originally configured. Changing the boot order in the bios negates the correct designations Grub has given to your drives and partitions to properly boot the system, as they are mapped by Grub originally. The same goes for the Windows bootloader. The boot.ini file is also set up to detect the booting of the actual Windows partition, dependent on the boot order in the bios when Windows was installed. As you probably saw in the other posts, I am not happy with Fedora's Grub set-up when the default partitioning scheme is selected, namely, a /boot partition is used, rather than altering the MBR. My system currently has the MBR on it's ide drive and Windows on the sata drive. But, I am using the SuSE's Grub to boot my system. If you are up for it, post the contents of your menu.lst or Grub.conf file and the device.map and we can give it a go.

According to the Alsa sound card matrix, the SoundBlaster Audigy LS uses the snd-emu10k1 module, whereas the Audigy SE uses the snd-ca0106 module. Also notice that the version of Alsa that comes with SuSE 10 (version 1.0.9) is known to have the distortion problem that you describe. What happens when you configure the card with the emu10k1 module, per Yast?

There is a fairly good how-to here that is based on the RedHat kernel. For kernel 2.6 upgrades here and here.

I looked this up, you are correct, it should be the ES1371 module. Sound configuration is not one of my strong points. But, how did you delete your soundcard? Did you update alsa or the default kernel, by chance? Let's try something first. Get to a terminal window, as root user. try typing in the following; modinfo soundcore Does this give you any output? If so, then try; modprobe snd-card-ens1371 Do you get any errors, or just a return to the command line, without any errors? If no errors, look and see if loading the sound mixer shows the card. Or, if Yast let's you configure the sound card automatically.

OK, lets take a look at this in more detail. I looked up this brad of modem on their website, but they give little information. I did a little more looking around and found out some interesting things. The make of the modem is 2wire...what is the model number? Different USB routers/modems have various chipsets. It is difficult to know what you have, unless we know the model number, which will determine what chipset that it has. This modem company makes DSL modems for Windows, not Linux. When you set up the modem in Windows, you used an installation cd to get the connection up? This sets all the settings that you need in Windows. This is not the case in Linux, and you need to do some work. I assume that you went to set up the modem in network device control (start-->System Tools-->Network Device Control)? If the modem is recognized there, that is step one. If so, what is the name of the connection, eth0? Again, do you need to login to your provider using a username and password? Was one provided to you by your internet provider? If this is the case, you would have needed to input this information when you set up the modem with the setup cd when you first set-up the system to connect to your provider. If not, this may be pre-set in the modem itself. Apparently, this is the case with some providers. in this senario, you set the modem up as DHCP, to automatically connect at boot. If not, then you must set it up manually by providing information about the IP address and other settings, which is a static connection. Remember, in Windows, the set-up cd does this for you. In Linux, you need to do this manally, as there is no set-up cd to do this for you. If the modem is recognized, as you say, and there is no driver configured by Fedora, then the modem, by way of USB, will not work without perhaps, a lot of work. If this is the case, buying an inexpensive ethernet card is the easiest solution, using this to connect to the modem, rather than USB. If your provider requires you to login (this is not configured into the modem), then, you need to add this information, as well, to Network Control, as ASDL. Fedora, in my opinion, is not the best distro to do this with. Others detect and configure these ASDL connections much easier. I am posting through Fedora on DSL, but it took some work, even through an ethernet card.

This is a test message to see if text formating works correctly; map (hd0) (hd1) map (hd2) (hd1) Ok, there is an issue. I may have overlooked an important point. g0kth, Please post the following, as this is getting too difficult to follow. Let's recap. 1. What is your current boot order, pata or sata? In the bios, the order of disk detection, is it; scsi, ide... or; ide, scsi...? 2. Post your current menu.lst or grub.conf file. 3. Post your device.map file.

What's important to know, is if the soundcard is built in, or if you added a card to the system. According to Dell, the onboard sound is ADI SoundMAX 2.0 Integrated Audio Driver (ADI 1885 chip set). If it is not onboard, it could be one of a number of cards added to the system. These cards are legacy cards built for Dell and can give Linux a real headache. If it is a soundblaster card, there ar dozens of models that it could be. many, as I mentioned are legacy cards that Dell used that were configured for Windows. Look in Yast, under hardware-->Hardware Information. Look under the sound tree. Does Yast note what it thinks the soundcard is? Also, from the command line, you could do; lspci -v -v Look for the soundcard entry and note what the output is for the card.

Yes, I saw the cost, but if the demo works once without purchasing it... Another possibility is TestDisk. I found the link in a fairly technical article about the subject here.

If you have Windows on this system, that is functioning, you could try a demo of this product and see if the demo works for you. I have frequently warned folks about manipulating partitions with qtparted. It is a tool best used to initially set up partitions before installing your Linux flavors. But, it has problems with manipulating certain partitions after the fact. It is heavily dependent on what filesystem packages are installed to support it, especially if you built it from source. The other possibility is SystemRescue CD which may work. Read the manual page for details. Yes, it does have qtparted, but that aside, see if you can pick up the apparently lost partition(s) with it's tools and backup, then restorte to a fresh partition.

This thread is way out of date (note the original post date), so disregard the previous data. What exact make and model DSL modem is this? What tool are you using in Fedora to set up your connection? Most DSL providers require that you use a login name and password. Have you tried to set up ASDL with your username and password, if this is the case?

So, what was the problem that you had with dual booting? Anyway, the answer to your question is located in the RedHat documentation located here. Once you enter the chroot environment with chroot /mnt/sysimage, then run the following (with a dsikette in your floppy drive); mkbootdisk --device /dev/fd0 2.4.20-9 ...where 2.4.20.9 is the kernel version on your system. you can either look at the /boot directory to see the kernel version, or, type at the command line; uname -r to see your currently running kernel version.

Let's step back a bit. Where are you downloading Flash Player from? Is it a Linux version of Flash Player?

Forgive me for asking...I must... Why are you using redHat 9? It is no longer supported. But, give us some more information. Do you have both RedHat and XP on the same drive? Is it the only drive on your system? What trouble did you have dual booting? If all your answers to the hard drive questions are one hard drive on your system, XP was installed first, then RedHat... Look at this thread which will tell you how to do it. Again, this assumes a lot, that there is only one drive on the system and it is jumpered as your primary master. Before you try it, please respond with what you have currently.

Well, you could download the first installation iso of Fedora and burn it to a cdrom disk. That is, if you have access to a cd burner and know how to do this. Better yet, download Mepis Live cd and use qtparted, the partitioning utility that comes with Mepis, to do the job. There are also floppy disks that may do the job. Let us know what you choose to do.