danleff

Did you install via the rpm or source code?

Ahh...as long as you have booting from cd in the bios set ahead of booting from the hard drive (which it looks like you have), then the problem is the burn. Look at the cd (pop the 1st install cd in after booting to Windows) and what do you see on the cd when you view it, one ISO file or a bunch of directories and files? Double check this. If you see the iso file only, you just burned the iso file on the cd, rather than the image. If you used Nero, you must choose the "burn Image" option located in the "file" dropdown menu. Burn the image at no faster than 4X or 8X speed, as iso images do not like to be burned any faster, to burn correctly. At this point, if the image attempts to boot, but gives an error about not being a Mandrake install cd, then try booting from cd #2, then when the error occurs, pop in disk one and allow it to run.

Also, what router, make and model, do you have?

In Nero, burn that image at 4X 0r 8X, no faster. Then try the install. ISO files do not burn correctly at high speeds. Are you using cdrw or cdr disks?

Booting directly from the cd drive would be better, but this is a common problem with the Mandrake install cd's. Is there a reason that you are not booting from the cd directly? It is good that you are installing Mandrake to a second hard drive. This should prevent the issue with corrupting/improper reading of the Windows partiton that we have seen with kernel 2.6 installs on the same drive as Windows is on. Try booting with the second Mandrake cd in the drive and when prompted that it is not a Manrdake install cd, switch to the first cd and see if the install process continues.

Good deal. I remember seeing this before. I could not remember the correct chroot command to get to root of the rescue system. And hda is correct, as you wanted to write to the MBR of the primary master drive, not a partition, when usng the grub-install command. Nice troubleshooting!

Very nice directions, Dan. Hunting down some of the repositories is sometimes a pain, but well worth it. Once you get a good set of repositories, it works very well, with some exceptions. Mplayer, for example, is not ready for Fedora Core 2, but all of the basics are there. Some web sites, such as K3b, even offer apt repository directions on their web page. So, everybody is getting the idea.

OK, I got kernel 2.4.25 up and running. I did find a location for the source kernel RPM. The modem driver DOES install on this kernel version. Of course, I do not have one to test to see if it actually works.

Dan, save some of that scotch for me! I looked at Mandrake. It seems that the kernel source package is not included for 2.4.25 in the install cd´s. Only for the 2.6 series. I tried to install the drivers on kernel 2.5 with the source installed. All kinds of errors, as I suspected. I found the source for kernel 2.4.25 and am downloading it now. Urpmi was very slow and I aborted (over 2 hours on the server, using broadband). I´ll let you all know how it goes.

I looked at this and yes, you can install kernel 2.4.25 as an option. The other point is that to install the modem driver, the kernel sources must be installed as well. The modem install script apparently uses the kernel source to build and create the proper environment and directories that he needs, If the sources are not installed, then the modem script fails. He can pop in the install CD and once the prompt comes up, hit the F2 key, then type in alt1 (then hit the enter key). This should run and install the 2.4 kernel on the system. He should also know where the install partition is located, so he can choose the proper partition to re-install to. Once the system is up, then the kernel source rpm needs to be installed. Of course, I would assume that the kernel source package can be installed during the distro install, as long as he picks this package, during the install packages process. Once the kernel source is installed on the system, the install script should run for the modem drivers.

Sounds like a video problem to me. Laptops can be an issue with their video cards, auch as the ATI video cards built into laptops. Are you logging in as user or root? When you did the install, you should have been asked for a user name and password, as well as a password to use for root. I am streching my memory, but try the following; 1. Log in as user and type in startkde 2. If this does not work, change to root user; Type in su then your root password. Try then typing in startx Let us know what happens. especially if you get a message that no usable screen can be found.

Two possible issues as I see it. One is that the driver package requires the kernel source to be installed on the system. I bet the Mandrake installation process does not do this, unless you specifically told it to do so when you installed Mandrake. This can be solved easily. The second thing is that the drivers seem to be built based on the 2.4 kernel series, not the 2.6 series. I would contact the company and ask about support in the 2.6 kernel series, since the install documentation does not list Mandrake 10 as supported. I would assume that the package has not been tested with the upgraded kernel series in Mandrake 10. So, I would e-mail them first and ask about this. If they reply that it does work in the 2.6 kernel series, then you probably need to install the kernel source package. we can walk you through this.

first, and it seems simple, but often overloooked, make sure that the sound is turned up all the way in kmix or aumix. If you have alsa as the sound modules, then type in as root user in a console alsamixer. Make sure that the graph bars are turned up. If you are using Fedora Core 2, type in, again as root user, in the console, system-config-soundcard. This should give you a small dialog window that will show your soundcard, if configured. Play the test sound sample and see if you get sound. Or you can go to start-->System Tools-->Info center-->sound ...and see if the sound card is listed there. One other problem occurs with the bios. If you have an onboard sound card and also a PCI sound card, the onboard sound needs to be turned off in the bios, for the add-on card to work. Also, often PNP OS (in the bios) should be turned off when using linux. Often these issues are the cause of sound problems. If sound is not detected on your system, post what sound card (or motherboard) that you have (if this is onboard sound) and we will try to help. Motherboards with the nForce chipset are new and the onboard sound and NIC often are troublesome. You can expect that only the newest released distro versions have support for such hardware out of the box, since most of this hardware was released after the distro version was. Otherwise, you will need to compile drivers or kernel support directly for the newest hardware.

Well, that is odd! What site did you download from? Also, what browser are you using to download the image with? This sometimes makes a difference on how the iso is downloaded. I know that some versions of Netscape did this, unles you pressed the shift key, then clicked on the image to download it.

I took a quick look at the distro page. From what I gathered, this distro needs a bit of tweaking to get things to work. I think that you might might want to look at the tech forums and look around to see if this distro will be usable to you. USB devices, in your case wanting to hotplug (plug in the hardware after the system is already up) seems limited in this distro. In gerneral, this has been a weakness of many distros, until very recently. In terms of the sound issue, look here. I number of the USB drivers (modules in Linux lingo) do not seem to be compiled directly in the stock kernel. So, this requires what is called compiling the kernel to have support for many of the hardware devices that you speak of. Bouncing back and forth between kernels will not be helpful, so you may want to look at which kernel is offering your the best support for your devices (hardware) and work from there to get the other hardware working. In any case, let us know what you think and feel free to ask questions when you get stuck. while this forum may not have all the answers relevent to this distro, we can offer general quidance and advice. I would also post on the forums there, as they seem to have a number of helpful folks there that may be able to offer you more specific advice, relevent to that distro.

I think that you have the answer. I recently worked on an older Gateway and it did not want to read cdrw disks that I burned on my writer. It would read a cdr disk, as long as I finalized the disk after the burn...well sometimes. The issue is whether the cdrom drive was made to recognize the format of burned cd disks that are not burned professionally. Try the slower speed on one cdr - I would not waste much effort on burning too many, as they may not work on the old system.

I think that you have the answer. I recently worked on an older Gateway and it did not want to read cdrw disks that I burned on my writer. It would read a cdr disk, as long as I finalized the disk after the burn...well sometimes. The issue is whether the cdrom drive was made to recognize the format of burned cd disks that are not burned professionally. Try the slower speed on one cdr - I would not waste much effort on burning too many, as they may not work on the old system.

I hate to sound like a broken record (or cd), but what speed are you burning the images at? Are you attempting the install from the same cdrw drive that you burned the images on, or another cdrom or dvd drive? Did you check the media integrity of the disks before the actual install attempt? Finally, what media are you using? CDRW or CDR disks?

I just order the Novell disks also! Is the image burned on the DVD, or is the iso file itself on the dvd? What type of drive are you using for the burning, a cdrw, or dvd/cdrw burner combo?

Please stick with one topic, so we can follow the information that we need to reply, Choose new reply, not new topic and this will allow the thread to continue. Any reason why you do not want to use the 2.4 kernel at boot? If this works with your hardware, I would stick with it. Once you get comfortable with the distro in general, you can experiment later on. Your motherboard has common issues with onboard sound and NIC, as I believe that it is an nForce chipset. It seems that the version of the 2.4 kernel available is supporting the hardware. I would not attempt to upgrade, unless you have a good reason to do so at this point. The 2.6 kernels use slightly differnt modules to load at boot and this may be the source of the problem. I will look at the distro specs. later on, but is it running off a cd completely (live cd version), or is it a hard drive install. I bet the 2.4 kernel is using the standard audio (OSS) and kernel 2.6 is trying to use Alsa, which may not be set up on the distro correctly, if at all. Is your onboard NIC working?

This is a very common problem. Burn the iso images at a slow speed (4X or 8X) on a quality cdr media. Most of these problems occur after burning the iso at too fast a speed. Do not use the top speed of the cdrw drive. What burning software are you using? And you are using the option to burn image, not just burning the iso to the disk, so that there is just the iso file visable on the cd? There should be several directoroes and files on the cd after the burn. Secondly if this does not work, post what general hardware that you have on the system, paying attention to the make and model of motherboard and the video card on the system.

First of all, thank you for posting all the specs. on the system. This tells us something about the problem. But do me a favor. Post the exact make and model of the motherboard, or if it is a Dell or whatever, the make and model of the system. This will also tell us how to exactly get into the bios, if needed. It will also tell us something about the onboard NIC card. I see that Win XP is preinstalled, so do you have the XP cd disks? If not, I would not use the system as your test bench for Linux. Some of these systems have a small partition written with bios and system informations (like Dell and Gateway systems) that you want to avoid mucking up the works, especially with any partitioning issues. You should not have had to manually set the NIC card. But depending on the motherboard/system that you have, RedHat may not have been properly detecting the onboard NIC. I assume that you are connected to the internet through high speed cable or DSL? Through a router or directly to a cable modem? ...and I assume internet has been working with your current OS? The issue with the partitioning problem is with Win XP installed in a dual boot situation, but I suspect that the partitioning issue would crop up later when/if you attempt to install another OS. If you want to have XP on your system, then do not delete XP, as it needs to be installed first before Fedora. You cant go back and install XP later on. So, if this is on your main system, you want to make sure that you have a working OS operating on it in either case.

Originally posted by quantz: Quote: when i click ignore the installion run normally but when i boot the computer there is no boot loader to choice either to boot with xp or fedora, before that i have win xp on my computer, i plan to use 2 OS, xp and linux, so how can i solve this problem The problem here, if quantz is articulating his problem correctly, is that he has no bootloader at all? Writing zeros to the MBR - does this not wipe the MBR and leave one with no bootloader? You still have to have a way to install a bootloader, be it Grub or Lilo, or to use the XP recovery console to re-write the bootloader to the MBR? I may be off on this one. Dapper Dan, I too ran into troubles with Qtparted. The problem is a catch 22. Finding a method to create a proper ext3 or whatever filesystem to install Fedora to before pointing Fedora to install on the pre-fomatted partition. PartitionMagic gave me the corrupted drive errors and bombed out. I have to think how I to did this. Upgrading Fedora is not problematic, as it uses the already existing partiton to upgrade to. No partition creating with the Fedora's utility, therefore no problem with the apparent partition corruption (or whatever we want to call it).

That is what you get for switching to the 2.6 kernel! What version of RedHat is this...and do you know what sound system that you have active with the 2.4 kernel, OSS or Alsa? What motherboard model is it? Is it an nForce chipset?

I have this card in my box with Fedora Core 2 and it should work out of the box in Fedora. I assume that you have it currently working in Windows or another OS? I also assume that it is an onboard NIC? If so, is onboard LAN enabled in the bios? Also PNP OS in the bios should be set to NO. Is this a nForce chipset motherboard? When you did the install, did you set DHCP active for the connection (find ip address automatically using DHCP)? If not, you will have to set it in the Network Configuration Tool. Fedora has a network config utility that you can look at. Go to start-->System Settings-->Redhat Network Configuration. See if the connection to the card is set as active. Post back what you find, then we can configure the card from here.