danleff

You installed too many packages. Quote: NVIDIA_nforce-1.0-0261.rh90up_2.4.20_9.athlon.rpm, NVIDIA_nforce-1.0-0261.rh90up_2.4.20_6.athlon.rpm, NVIDIA_nforce-1.0-0261.src.rpm , NVIDIA_nforce-1.0-0261.tar.gz these are the drivers i tried to no avail any more info needed jst ask The RedHat packages that have "2.4.20" are for that kernel version, which you do not have. The Athlon package is optimized for Athlon processors. You have Fedora's packages, which means that you probably should use the source package, with the tar.gz extension. From the nvidia installation instructions; Quote: Nvidia has provided precompiled binary RPMs for several versions of RedHat and Mandrake. You should select the RPM appropriate to your current kernel version. You can check what kernel your machine is running by checking the output of 'uname -r'. If you are using a different version of Red Hat or Mandrake, a modified kernel, or a different rpm-based distribution, you should use the SRPM to build an RPM appropriate for your system. If you are using the SuSE RPM, see NOTE: SuSE INSTALLATIONS, below. If you are using a non-RPM based system, or if you prefer not to use RPM, you should download and install from the source tarballs. Did you try to look at the /etc/modules.conf file to see if the nvnet driver is being loaded there? It should say on one line, alias eth0 nvnet As noted in the other post, did you try to do the following at a console? /sbin/modprobe nvnet If this does not give you an error and just returns to a prompt, this is good. Then make sure that the alias eth0 nvnet is in the modules.conf file. If you getno error onthe modprobe and the line is present in the modules.conf, then reboot and see if you see a line during boot like; eth0.....................................................success.

Do you have vnc-server and client installed on the XP system? Are you using vnc to view the Linux system from tne XP box, or XP's network setup?

This is a long thread. Can I ask for a recap? Fedora is the current distro? You are using the stock kernel that came with Fedora, not an upgraded 2.6.x kernel? The stock kernel should be 2.4.22. If it is the 2.4.x series; You installed the nForce CHIPSET drivers, not the nvidia video drivers? The current nForce drivers do not support kernel 2.6.x yet, so they will not work in that series, if you upgrades the kernel. Rather, they should be built into the source kernel. If all the answers are yes, then I will have to research this. But, I understand that Fedora Core 2 will have nForce chipset support, as well as NTFS read and write capability. You may want to wait for this.

Most likely Knoppix is at sarge. If I remember, it may be a combination of stable and sarge, that the Knoppix development team came up with. How to tell is look at your /etc/apt/sources.list file. The entries will have a qualifier in them. Woody will be designated as "stable" Sarge as "testing" Sid as "unstable" Upgrading woody's kernel is a pain. I found some backports for this on this web site, but they failed to be fetched. The 2.6.x kernel, in Debian, depends on Coreutils, which is not readily available in woody. At least I could not find it. In Knoppix, as root in a console, do uname -r This will tell you the kernel version, probably 2.4.xx.

Wow, lively thread! I just installed Mandrake 10 CE. Failed to configure my network connection (via-rhine). this should not happen, since Beta did OK with it. I have to look into this. Alsa also failed on my sound card. The Lilo error LiLilLi.. is usually due to a geometry mismatch problem. Remember, lilo sees the partitions differently than grub. For example, in lilo hda1 is hda1 and in Grub it is hd(0,0). See the following; http://sdb.suse.de/sdb/en/html/kgw_lilo_errmsg.html Also, different distros may map differently. Believe it or not! I also like the ability that Mandrake has to change the bootloader from Lilo to Grub and back. This helped me learn a bit about Grub. What I found, is that Mandrake will only detect distros installed using Mandrakeś lilo. So, for example, if I install Win XP, then Mandrake with Lilo, it picks up XP. If I add other distros to the Mandrake lilo later on, then then Mandrake will probably pick them up on an UPGRADE. Since I just did a fresh install, Mandrake only picked up XP, not my other distros. The lilo that I currenlty have is from Lindows. Mandrake picked up all of my fat32 partitions in fstab, but only ONE ext3 partition out of the five distros that I have. So, I will have to add them by hand. For swap, if you custom partition, you can tell Mandrake to use a former swap file, such as from a RedHat install. Mandrake auto installed entries into the fstab for the three swap files I have on 3 seperate drives. You can tell Mandrake to install lilo or grub on an existing boot partition, but whether it will pick up RedHat is anybodyś guess. I don know. I have mine on the MBR and it did not. Again, if you had Mandrakeś lilo or grub previously installed and did an upgrade, it looks like it would. Good question. If the vmlinuz and initrd entries are all in your root /boot directory, you can probably add them with the boot utility on Mandrake later on. They should show up as options. I have them elsewhere, so this did not happen for me. I have them all in seperate sub-directories under my Lindows install, in THAT rootś boot directory. My experience with upgrades is not good with Mandrake, They have all failed. Since I have 2 installs of Mandrake perviously, Cooker and RC1, I am going to try an upgrade later on the cooker install, since I don use it. Iĺl let you know how it goes. Finally, I have also tried debian and Knoppix. If you know synaptic and apt-get, itś a pretty good system, if you know how to add entires to the apt repository. You just have to make sure that you stick with the version that you have, be it woody, sarge or sid. Mixing versions is not good, unless you know a lot about dependencies. Mandrakeś self contained package installations is very good. The issue comes up when you try to install a package that is not pure Mandrake. Additions from the repository is very good, if you know how to add them. Best example, KDE 3.2. If you download all the needed pakages and point rpmdrake to the downloaded local folder or ftp repository, OK. Just make sure that you have valid entries. The issue comes up when you add a package that is not normmally included in Mandrake, or a newer version than what was originally designed for your version, say cooker. This is when dependency problems make you search for updated packages that are needed to satisfy the newer packages needs. I going to get some rest now...later!

I don't know about White Box, but there is another thread about this, which I will try to find. You may want to follow this thread and see how it went for the user and consult with him/her. This is a common issue for ATI Radeon users. Many linux distros have problems properly identifying the card correctly. What I do know, is that if the kernel source and header packages are not installed by default, you have to add them. How far you want to go with this depends on how much experience that you have with Linux. The other suggestion is to check out the White box web site to see if they have an answer for your issue. The other thread is located at the following; http://www.linuxcompatible.org/forums/viewtopic.php?t=1460 Also, here are the install instructions, that will give you an idea what you need to do. http://www.ati.com/support/infobase/linuxhowto-ati.html Another thread that discusses the problem; http://manhunt.thegoodtimes.ca/forums/index.php?act=ST&f=3&t=2961

Sure, but you are using Grub? This is the issue as I see it. Having Mandrake set not to overwrite the existing redhat partitions is easy. When you go to do the Mandrake install, at the install prompt (when the 1st cd boots to the install prompt), type in expert, then hit the enter key. This will allow Mandrake to let you make all the decisions about the install, as well as customize the packages that you want to install. Where this is important, is when you get to the partitioning scheme. Choose the option to allow you to manually set the partitions. If you allow Mandrake to do a normal install, then choose to allow manual partitioning, it still will try to overwrite the first linux partition that it finds. Choosing expert mode, prevents this from happening. Set up your custom partitioning scheme, or your free space. This is the part that I am not sure of. The home directory in some distros has app. programs attached to it. Wheteher this will cause a problem, I don't know. I would allow some space to be allocated to a home directory and complete the install. Then, once the install is done, edit the fstab in Mandrake and change the home directory line to match the one in RedHat. The other option, or course, is to add the RedHat home directory to fstab in Mandrake and allow Mandrake to keep it's own home directory. Again, since apps. are housed in the home directory, I would leave the RedHat directory exclusive to Redhat and allow one for Mandrake, then just add the home directory for RedHat to Mandrake's fstab. This way, you can share data files in the Home directory between the two. However, I think Mandrake will automatically set up other Linux partitions for you, so look to see if it is not already added to the fstab in Mandrake before making the fstab changes. I got Mandrake 10 CE this morning and am home with strep throat, so I thought about doing the install today. For dual booting, I just choose to install the newest distro's grub or lilo to a floppy, until I test it out. Of course, this depends on your system. If you already have multiple distros on the system, then you may want to retain your old bootloader and just add to it. This way, you don't take the chance of loosing your other distros, if mandrake doesn't automatically add them to grub or lilo. So, booting from a floppy is safer..just add the lines to your existing lilo or grub when your satisfied all is well with the install. I will also let you know what I find out.

It's probably overloaded. I tried it this am and downloaded disk 3. Of course, I treied it straight as a web site. It is probably wise to try it during low usage times, such as early in the am. Or, if you are using a download utility, try username anonymous and the same for a password.

It looks like the kernel source code and headers need to be installed for the kernel version on Mandrake 10. what kernel is running? Type uname -r in a console and see if it is kernel 2.6.x or 2.4.x. You then need to install the kernel source and header rpm packages from the install cd, if they are not already installed. Did you see the following link; http://www.ati.com/support/infobase/4475.html Quote: The ATI driver package includes a few bundled versions of this kernel module to work with most systems. If your system matches one of these configurations, then a pre-packaged kernel module should be installed for you and the information below should not be necessary. However, if your system does not match any of these configurations, then the installer will try to build a custom module for you from scratch. This process will require the following software to be installed: Kernel source code Kernel header (include) files GCC compiler Make Utility It also looks like you will need to make the symbolic link to the kernel, as mentioned in the article, if it is not there after you install the kernel header and source rpm files. Look under the section: Creating a symbolic link /usr/src/linux

Bully! :x Nice going! I don't use an MSN messenger, but what about the following; http://amsn.sourceforge.net/modules.php?name=About_Amsn

First, you did not mention what version of RedHat that you installed...9? Fedora...? Once you know that, you can go from there. Before installing any Linux Distro, you should check the web page of that distro to see if your hardware is supported. For example, if the version of RedHat that you installed is older than your hardware, you can expect some problems. This is true of any OS. So, what version are you running? You also do not mention what the exact hardware is that RedHat did not detect. What make and model sound card and video/tv card? Accessing a vfat partition (windows partition) should not be problematic, but then again, let us know what version that you are using, so we can provide you with some specifics. To give an example, if you are using RedHat 9 , see the following link; http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/getting-started-guide/s1-q-and-a-windows.html Then we can start!

Same here. If someone has the answer, let me know. Searching the web produced others having the same issue, but no resolution was suggested. I did find that if you click OK on the small popup window that comes up with the message, then KDE starts normally. Did you find that this was the case as well?

Try the following at a decent speed; ftp://mirror.cs.wisc.edu/pub/mirrors/linux/Mandrake/iso/

When you install packages (programs) from the install cd's, you will notice that you get prompted to switch disks to disk #2... Each package that you install, such as Amaya, may have other packages or libraries that it depends on. Using rpmDrake, or whatever the package installer is in Mandrake (I got so many, I can't keep track), you notice that it may want to install more support packages than the original package that you picked. This is called a dependency. Amaya depends on other packages to work. When you install a package, like Amaya, independent from the auto-install feature in Mandrake (that installs and attempts to meet the dependencies for you), the same thing happens. But, you need to know what other packages are needed to make Amaya work properly. If you don't, rpmfind is a web based rpm repository that can help to sort this out, to some extent. When you get the message trying to install Amaya, that a dependency is not met (as you did), then Mandrake tries to tell you what is missing. The resultant message does not always make sense to the average user. So, if you go to the link that I provided, that shows the Amaya package, and scroll down to the dependency section, chances are that you can ID the missing library package, in your case librdf.so.0. Click on that and hopefully you find an rpm package, for Mandrake, that meets that dependency. Amaya may depend on other packages, as well. That's when folks call this dependency hell!

If you look at the Amaya link and scroll down to the dependencies section, you will find a reference to librdf.so.0. Click on this and it brings up the dependency package that the libraries are contained in. This is the tradeoff with installing independent packages not found on the Mandrake CD's. You need to track down the dependency issues. Some call it dependency hell. Of course, there is apt4rpm and yum that works on some distros that take care of this for you, provided you find the correct repositories!

That would be my guess, as well. I'm glad you said it first, Dapper Dan. You can't see Linux partitions from Windows, so it looks like the install got as far as creating an ext2 or ext3 partition, on what was partition F: Give us a little information on how you burned the iso's and on what media.

You are missing the libraries for libredland0. This is a dependency error. What about the Mandrake CD's? Is there a version on one of the three install and rpm cd's? If you want to try this, get libreadland0, but there may be more. http://rpms.mandrakeclub.com/linux/rpm2html/search.php?query=librdf.so.0 Start at rpmfind for Amaya and check any other dependency errors that you may get. http://rpms.mandrakeclub.com/rpms/mandrake/9.2/contrib/i586/amaya-8.1a-2mdk.i586.html

Mandrake 10 RC1 has been rock solid for me. I agree. The mouse issue is gone. Also, all the mandrake 9 packages that I have installed work fine. Cooker, as well.

It usually means that the cd drive is having trouble reading the cd. This can be caused by a number of factors. Are you usng the packaged set of cd's or did you burn your own? If you burned your own; 1. An older cd drive that has trouble reading cd's burned by a cdrw drive (yes I know, but the first was read by the bios at boot). Laptop drives can also cause issues like this. 2. Funky or cheap cdrw or cdr media. 3. Failure to burn the iso's at a slow enough speed. Despite the rating of the cdrw drive, iso's have to be burnt at a slow speed (8X or less) to burn properly. 4. Sometimes, cdrw media act funky with iso images. Then they work fine with cdr media. 5. Failure to burn all the iso files as image files, in other words, just burning them as data files. If this is a boxed set, sometimes you have to coax the cd drive by reinserting the media again and trying to remount (get the drive to read the cd again).

This show you the variable results with different distros and their development of winmodem drivers. According to the Mandrake hardware database, the Lucent chipset is not supported directly, but there is a driver. First verify what kernel you are running. It should be 2.4.21-0.13.mdk, if you made no changes to it. If so, you can try the cooresponding drivers at the following; http://www.heby.de/ltmodem Scroll down to the Mandrake binary section and choose a mirror, Canada or Germany.

Quote: i need to set up a network through the onboard nforce 2 mobo im using the ethernet from it to go to a belkin router and the belkin router is thus hooked to a cable modem i cant get it set up actually it cant activate i need to reinstall fedora because some reason win updates killed it ill go for redhat 8.0 first anyway i can activate the exact account ill post the exact error message later Remember, RedHat 8 is an older distro and was made before support for the nforce chipsets. If you want to use the onboard LAN, you will need to get the drivers from NVIDIA.

I like Bluefish and Quanta Plus. lot's of options and utlities. Amaya is a good basic WYSIWYG.

Yes, these are the directions for compiling a 2.4.xx kernel, NOT the 2.6.xx series. There are differences. You need to assure that you have updated packages, such as modutils and module-init-utils, which is different from compiling the older kernels. See the following links; http://kerneltrap.org/node/view/799 http://thomer.com/linux/migrate-to-2.6.html http://linux-sxs.org/upgrading/migration26.html

This is great if you can get it to work! Could you post where you got the driver from? Your XP partition...is it a NTFS partition? If so, you can't write from that partition. I'm not sure if RedHat 9 will see the NTFS partition. If if is vfat, then you can look at the link below. You need to know where the vfat partition is relative to Linux. If it is vfat and it is on the first partition on the drive, then do the following at a console, as root user. Type in the console; mkdir /mnt/vfat (hit the enter key) mount -t vfat /dev/hda1 /mnt/vfat (hit the enter key) Then use the file manager to navigate to the partition at /mnt/vfat. For more detail, see; http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/getting-started-guide/s1-q-and-a-windows.html

Thanks for posting the notebook model that you have. Exactly when does it freeze? During install? At the GUI screen? Please give more specifics. Reference; http://mikeycal.com/HP_ze5500.html