danleff

Well, the first question is, do you know how to use the Debian package management system to install packages? What version of Debian are you using? Sarge, Sid, Woody.....? If you have the Synaptic Package Manager installed, it is available. Are you currently connected to the internet? Let us know what the status of your usage of Debian is and we can guide you through the process. Quagga is in the Debian repository, so probably the easiest things to do is install it through Synaptic, or get into a terminal window, as root user and type in; apt-get update Then when the package repository is updated, type in; apt-get install quagga

Let's try two things. i have been reading up on a possible bug in Grub and fedora. After you chroot /mnt/sysimage, try running; grub-install --recheck /dev/hda If that does not work once you reboot (it does not give you the grub menu on reboot), then do the same (get into chroot) and try typing in at the prompt; grub At this point you will get a shell with a > Type; >root (hd1,0) >setup (hd0) >quit Reboot at this point <ctrl> <alt> <del> Then report your results.

Quote: 've a machine which is installed Mandrake 10 using a hard disk cloning method. Can you explain this a little more? What do you mean by a hard disk cloning method? Quote: I wanted to make it dual boot, so I format using fdisk and tried to install Windows XP using a CD. Please explain how you were going to try and make it dual boot. Generally, you would install Windows first, then Linux, so that Grub can configure the system for dual booting. When you say fdisk, are you speaking of fdisk by way of Linux, or the Windows fdisk utility? Windows setup can't read or detect Linux partitions, so this is the reason for the message that you got when trying to install Windows.

Assuming that you have a full Windows XP installation disk.... Windows need to see a fat32 or NTFS partition on the drive for it to start the installation process. It can't read Linux partitions or unformatted drive space. However, if you install Windows now, it will overwrite the MBR and you will only get the ability to boot Windows. The best way to dual boot both, would have been to install Windows first, then Fedora. Then the Fedora installation would have configured grub to dual boot both Windows and Fedora. It is a bit tricky to get both to work if you install Windows last, since Fedora's grub does not know about the Windows installation. Some have done it, but it is not easy for novice users of Linux.

Time for some humor. I just realized the title of your post, "Duel boot Win XP and linux." Was this intentional, or a slip of the keyboard? Duel (as in struggling with) is appropriate, rather than "dual" as in two, or "both."

Which MP3 package did you install? I can have a look at this in the next day or so. Did you use the author's yum configuration setup referred to on the Unofficial Fedora FAQ page? I assume you are using the Gnome desktop GUI. If this is the case, don't install the KDE player.

I found Fedora a little funky about doing this. it all depends, I found, on how you set up the partitions during the installation. Apparently (which has been verified by another user who posted his experience with this) it all depends on if you accepted Fedora to be installed using Logical Volume Management partitions or not. If you format the drive/partitions with the traditional linux partitions, not using LVM, then the USB booting works properly. Fedora is also able to resd the partitions better when you boot into rescue mode and modify the initrd file. I ran into this with FC5 trying such an installation. But, in terms of your system. what are the options in the bios for booting various media? If you go into the bios (F10 at boot time) and navigate to the Advanced Menu-->Enable Multiboot area, what are the media booting options that are offered to you to set? The online users manual is not very specific about this. Or, look at your actual users manual (hard copy). Does it list the possible options under the advanced menu for booting different media? Does it list some options like; USB-HDD USB-FDD USB-ZIP?

Unfortunately, you have made all the common mistakes when installing Fedora. Here is the situation. 1. You installed Fedora, accepting all the default options to install it, so that you have Fedora and the Grub bootloader on the second hard drive. So, the only way to boot Fedora right now, is to change the bios order of the drives, so you boot from the Fedora Drive, not the XP drive. 2. When you install Fedora to a second hard drive, you must tell it to place the bootloader on the master Boot Record of your actual boot drive, the XP drive. If you do not do this, then the Grub bootloader is installed on the second drive, so the only way to boot, is to change the bios boot order of the drives, making the second drive the bootable drive. 3. When you change the boot order to the second drive, you change the logical order of the drives, as detected in the bios. Windows was installed on the first drive, so when you try to invoke the Windows boot.ini file, it is still looking for the Windows information on the current boot drive, which now is not where the files are at, but rather, on the second drive in the boot order in the bios. Windows boot hangs. 4. You change the boot order of the drives in the bios back to the original state. The Windows bootloader is invoked and finds the files where it expects them. 5. Don't worry about the bios boot message when Fedora starts. It is not important right now. 6. You get a command line interface when fedora boots fully, not the graphical login screen, as shown here. This is most likely related to your video card not being supported. You have a PCI-E video card in the system. Fedora probably does not have the proper support for such a new card yet. Your motherboard is probably not fully supported yet, as well. This is a relatively new motherboard. The other difficulty is that you changed the boot order in the bios to try and boot Fedora off the "proper" drive. however, fedora can't find all the files that it needs to boot properly. Theu are not in the places that grub expects. 7. The user ID and password is what you told Fedora to use during the installation. if you can't remember what user ID and password that you chose during the installation, then your stuck. Again, you changed the boot order in the bios and all the proper files to login may not be found where they are expected. Quote: If I boot to Win XP I get the following info on screen: Booting 'Windows XP' rootnoverify (hd1,0) chainloader +1 This is a message from grub saying that it can't find Windows properly. Remember, you changed the boot order in the bios, so grub is confused. It is looking for the Windows boot.ini file on the wrong drive. In terms of how to fix this best, let me think about this. There are some fixes, but this depends on how comfortable you are with messing with command line usage.

OK, when your cack up and running let's see what happens. First, see if the same issue with grub happens once you have a new power supply installed. Quote: It's been a while, but from my best memory, yes. I dedicated an entire 160gb physical drive to Fedora in one big partition. OK, what this does is default (I think also in FC4 as well as FC5) break the drive up into a /boot partition that holds grub and probably Logical Volume Management on another partition. But the effect is that Grub is installed, by default, to the same drive as Fedora is installed to. So, Grub is not on the actual boot drive (hda) but the second drive. Doing grub-install /dev/hda places grub on the MBR of the actual boot drive, hda, which is actually the primary master drive on most systems. I don't know what effect making the mistake of hd0 is, but it appears in your case, the drive designations got mucked up. Why I aksed about he drive order in the bios. if you changed the order of the hard drives at any point, this can muck up the system. Changing the cdrom to boot first has no adverse effect, just the hard drive boot order, say from hdd0 to hdd1. But let's see what happens when the system is back up with the new power supply.

See, I knew I would get it wrong. The second option should read; title Windows rootnoverify (hd1,0) chainloader +1

Quote: I installed Grub on the /boot partition rather than the MBR since I've had too many problems gettings the old Windows MBR back when I wanted to kill my linux install. I did the normal dd trick of copying the boot sectors to a bin file and them mcopy'd them to a file that I put in boot.ini on Windows. However, windows refuses to boot it, I just get a round-trip back through the bios and the same screen. Can you point me to the directions that you used to do this? you can use the boot.ini modifications, if it is done right. Remember, you installed suSE to the IDE drive (which is probably set in the bios as the second boot drive) and the data that you copied over assumes that the IDE drive is first, since placing grub on the second drive's boot partiton assumes that it is the only drive in the system. So now, the boot.ini, when invoked by grub with the modified files that you copied over, is looking for windows in the wrong place. If I have this correctly, you can boot windows from the MBR (you get the windows boot.ini login screen choices}, but when you pick the Linux option, you get the grub menu, but can't boot windows from there? If this is not the case, you mucked up the system. When you boot, do you get the windows boot.ini choices, or pure grub?

Please look over the directions again. They say; Quote: Install the RPM file madwifi-*.i386.rpm (or x86_64 respectively) plus the RPM kernel module packages (kmdl) appropriate for your kernel version and architecture, madwifi-kmdl-*.rpm and madwifi-hal-kmdl-*.rpm. There are a couple of other links that may help. but, what kernel are you running now? The key to finding this out, is running the command uname -r at a terminal window. Is this Fedora Core 4 or 5? They use different versions and builds of madwifi. So the proper command for yum would be, as per the directions; yum install madwifi madwifi-kmdl-`uname -r` as root user in a terminal window. Or possibly; su -c yum install madwifi madwifi-kmdl-`uname -r` in just a non-root terminal window.

When you decide to install Linux anywhere, you ned to have a plan. In your case you found out, after the fact, that your system does not support booting from USB. However, most "new" laptops can boot from USB, so my first question is, what make and model laptop is this? Secondly, no, you can't create symlinks as you describe. what you need to do is have a way to boot your FC4 installation. This topic was covered recently in another thread, but to recap briefly; 1. The default Fedora installation process assumes that you are installing it to an internal hard drive, namely the main hard drive in your system. So, if you accepted all the default options, then FC4 assumed that this was the only hard drive on your system and proceded accordingly. 2. The default FC4 kernel does not load the modules (drivers) needed to boot from an external USB drive. There are special instructions for this. In order to boot from an external USB drive, you need to have some sort of a bootloader, either; 1. The ability to boot from an external USB drive in the bios, 2. An installation of Linux already on the system that has the grub or lilo booloader that your current installation can be added to, or; 3. A boot CD that allows booting a Linux distro. However, your problem is that by choosing the expert mode to install to the external USB drive, the proper modules were loaded to see the drive. That's why they call it "expert mode" - which assumes the user knows what they are doing to set up the installation properly. Once you install to the USB drive, you need to rebuild the initrd file with the USB modules needed to be present during boot to sense the external USB drive and boot that drive properly. The initrd file holds the instructions needed to load the proper modules at boot. But, let's see what you have before we go on. Are you sure that the laptop can't boot from a USB drive?

Quote: Fedora Core installed fine, GRUB on first part of boot sector not MBR, but when I go to set it up it asks for a login name and then a password but I don't think I have set one up, unless it is using one of the two passwords I set up during the install. I assume that you allowed Fedora to use all the defaults that are offered, in terms of partitioning and placing grub in it's own boot partition. When you are asked for a username and password, do you have a graphical login screen (the KDE or Gnome GUI login screen), or just a command line? If you just get a command line, can you post the make and model of computer that you have? If you are getting the Gnome or KDM login screen, you need to input the username and password that you chose during the installation. Quote: My other problem is I can't load WinXP from the linux side, it hangs my system out. Could this be from running a 64 bit and 32 bit OS? When you speak of the "Linux side" what do you mean by this? Are you changing the boot order of the drives in the bios in order to boot one OS or another? I am not asking you to do this, just trying to see what the status of your booting each OS is.

I notice that you started your own thread also. Please post any information on the thread that you started, as posting in more than one place confuses folks who need to respond to your questions. This way we keep all the information about your problem in one place, the thread that you started.

So, it was what I thought. The drive boot order was changed. Has this been the cae all along? In other words, you had installed Windows and fedora with the drive boot order like this? If so, then there is a fix. I always forget the exact syntax, but it can be fixed. let me remember the syntax (in your case) and post back. But, in the grub.conf file, you can reverse the order of the drives, as they are seen by Windows and grub. Why, because the Windows boot.ini file is pointing to the opposite drive now that you have reversed the order in the bios. but the general syntax in the Windows entry is something like; title Windows (it may be "other" as Fedora set it up) map (hd0) (hd1) map (hd1) (hd0) chainloader (hd1,0)+1 or; title Windows rootnoverify (hd0,1) chainloader +1 But, let me check the exact syntax for your issue.

I did not ask you to edit the device.map file, just to tell us what the contents of it are. Quote: What is the actual output of the /boot/grub/device.map file. Is it something like It just occured to me, did you accept all the defaults when setting up Fedora, including partitioning the drive? If so, then grub and the device.map file are most likely on it's own small /boot partition. But to answer your question, when you boot from the Fedora installation disk and get the installation splash screen, you can type in linux rescue. This gets you to the rescue command line, once the booting process finishes. Then you would type in chroot /mnt/sysimage. This gets you to the root of the Fedora installation partition, where you apply any fix commands. But before you do this, did you attempt to change the boot order in the bios at any point of the process, either installing linux or afterwards to try to get it to work? Again, I am not asking you to do this!

Unfortunately, the post you referred to was not the exact same problem that you are having. In that post, the user had a third party boot manager installed that was mucking up the works on his initial installation of Fedora. Once he figured out the issue, he found a solution. Quote: so finally when the cigarettes ran out and i screwed up not only the fedora install but the windows install and the pepto-bismol ran out i gave up and went to bed. hehe You are getting stuck in the same loop that others do. There is not need to keep reinstalling things and the directions that you followed, or seemed to follow that the user tried, missed documenting one important step in the process. Whenyou get into linux rescue, that just finds your Fedora installation and gives you some basic commands to work with. In order to get to the full root partition that Fedora is installed on, you need to tell Linux rescue to put you there. The command would be chroot /mnt/sysimage. Then you can apply any commands to fix the MBR on your actual boot drive, usually hda. Quote: i betting the problem is in the way im installing the GRUB on the MBR, but just can not get the spashscreen to come up no matter what way i try to install now after reading inside the liux boot process. i did want to add when i tried the system-config-boot in the rescue menu i got the response kernel not found. You are most likely not installing Grub into the MBR of your primary master drive, the one that holds your Windows installation. Can you remember where you installed Grub? Remember that hda is the primary master drive (your boot drive) and depending on where you have the second drive jumpered and set to, that drive is your Fedora drive. If you elected to install grub on the second drive during the installation, then this is not your boot drive. Therefore, no Grub on your actual boot drive.

First, see the section on the Unofficial Fedora FAQ about mp3 files and the patent issues. This explains why these packages are not included in Fedora proper. For video, I use Mplayer and the associated plugins. See the article Fedora Installation Notes on the subject.

The best link that i have for this is here. The key is downloading BOTH packages, the madwifi madwifi-kmdl ones. See the directions and let me know if they work for you.

Glad you got it fixed. So, the problem happened before any changes! Goes to show you...I concentrated on the software and all the time it was hardware! This points to the advantage one has actually seeing the system itself and being able to diagnose the problem. Tell your friend, nice job!

Fedora comes with an instant messaging feature called Gaim. See this article in the Fedora Unofficial FAQ on how to do it.

Sorry! Now I'm totally lost. This is why I recommend that folks post all their information on their own thread, rather than on multiple threads. You have an HP computer. Can you point me to the original thread that you posted on, or tell me the model HP that you have? Let's look at things one by one. First the older stuff. I wish that I had an HP to work with! Quote: I did that thinking and I had read up that (hd0,1) would be the same as /dev/hda2. Yes. but depending how the system was set up, the rescue partition may be "hidden" so it can't be touched. So mapping to hda 2 may not be correct. Quote: *** One quick edit, with the current setup I am able to boot in my system restore and FC5, just not Windows. Thanks again! As far as I know, you can't boot to a restore partition. So, you were actually booting to Windows? Quote: So I just booted into FC5, and when I did, it takes me to what looks like a dos screen that says in all text: Fedora Core release 5 (Bordeaux) Kernel 2.6.15-1.2054_FC5smp on an i686 Interesting! Do you have a multi-processor system? The smp suffix means multiprocessor, but I know that Fedora Core 5 has one kernel for both on an AMD64 system. Quote: So I belive my next question is how to I get into the GUI from here. Quote: And yet again it continues!! So I reinstalled FC5 with all most of just the default settings, because I was finally able to get to the grub screen. So I reinstalled this time with out using linux text like I had before, and followed the things I said above, and I still can't boot into windows. But now when I load into FC5 I get the graphical interface, but it hangs when its at the part for probing for new hardware. There is hardware and settings on HP system that may be at issue. I keep mentioning that HP has a lot of proprietary hardware that may not be compatible with Linux and is made for the Windows version installed on the system. This can be one issue. These systems, unless you bought one preconfigured with Linux (where the hardware is designed to be compatible), can be a pain to configure. Knowing the exact model of HP that you have is important. The problems with hardware detection may ne solved in the bios. Look in the bios settings and see if PNP OS is set to "yes." The setting can be in a few places (depending on the bios) such as under PNP Configuration. You may need to set this to "no." So, this install was on a second hard drive, or the same one as Windows? Sorry, but there are too many threads to follow and I can't keep it all straight.

Unfortunately, the devil is in the details. I often find that folks, in their effort to fix a problem, leave out important details. In each subsequent post they make, some more information comes out that is vital to solve the issue. Now we know a little more about your problem. What is important, is that you did not read another post that was not the exact same problem as yours and try a suggested fix. So, 1. you did not change the boot order in the bios at all when you tried any of the solutions? No, I am not telling you to do this! What is the actual output of the /boot/grub/device.map file. Is it something like; (fd0)..../dev/fd0 (hd0)..../dev/hda (hd1)..../dev/hdd Then, the contents of the grub.conf file can be looked at to point to a solution. So seeing the contents of this file is important, as well. It tells a lot about how Grub is set up and where.

To my knowledge, unfortunately,there are none. The old Lexmark Linux printer drivers do not list this multifunction printer as supported. Also, they are quite old, almost three years old. The SuSE hardware compatiility database do not list it as supported. Linuxprinting.org does not show it either. Their database is somewhat dated, as well.