danleff

Are you using Debian Woody or Sarge? If Sarge, I bet there is no initrd file and the original install has one. I'll post a solution if I find one.

Actually, I just did it and found a work around. It does work. If you would like, I will post it on my website later this week. Essentually what you do is make the bootsect.lnx file and copy it to a floppy. Then when in XP, copy it to the C: drive (which is usually the boot drive). I altered it a little so that I can boot XP, or go into lilo and boot any of my three distros on my test box.

This is a common problem with this board. RedHat 8 is too old to work with the nForce chipset on the motherboard. I would suggest Trying Fedora, or Mepis first, as Dapper Dan suggested. I'm not sure if nvidia has drivers for this version of RedHat, but I will check. It has been also noted that the bios in this board does not allow you to turn off sata raid, which may be another issue.

I just had the same problem compiling the 2.6.8.1 kernel in Debian. Quote: The error is normal when you need to specify the root partition root="/dev/hd1" but I have that peice in and it boots my 2.6.7 kernel just fine with the same arguments in place. I hope this is just a typo. What is the root partition? Hd1?? Is it hda1, hdb1? What are you using as a bootloader, lilo or grub? Also, what motherboard is this, possibly with an nForce chipset?

Ok, let's dig into this a bit. What exact monitor and video card do you have? Can you post your XF86Config-4 file? If not, copy it to a disk and send it to me at leffingd@yahoo.com.

OK, and the realtek is connected to the router via a cat 5 cable, not directly to the USB modem? I'll look at Mandrake later on. You can try to add another connection in the Control Center. I think that I remember to set it up as lan, but let me look at this more.

Actually Fedora does come with Lilo as an option, I believe. It should be a choice when you get to the bootloader part of the install. I bet it defaults to Grub, but click on the dropdown menu when you get to this part and see if it allows Lilo as an option. I have not tried it with grub or lilo. Maybe I will experiment on my secondary system. If your bios allows booting from a secondary drive, yes, this should work. Just make sure that you choose the correct designation for the second drive when installing lilo. Before doing anything, I would try a live cd based distro like Knoppix to see what the system sees the second drive as, once it is in the system. If you are lucky, it should see it as hdb. Of course, it would need to be formatted first to be seen. I just thought of a possible catch. Is your XP system using NTFS or a fat32 filesystem? The referenced article doesn't mention this as a possible issue, of course, it is an old article.

This should work, depending on what the system sees the hard drive as once it is in the bay. If you use the NT bootloader, just do not pick the Linux option unless the drive is in the bay.

In order to get Mandrake to work, you need to be connected via the realtek card. The system should be like this; DL-514 (main connection)-->Cable modem Mandrake system via Realtek NIC-->DL-514 I assume your ISP uses dynamic assignment of IP? Did you tell Mandrake, during the install, to use DHCP on start? Then you can go into the Mandrake Control Center, which should be start-->System-->Configuration--> Configure-->Configure your Computer-->Network & Internet. Once there, click on Manage Connections.You should see on the first dropdown menu eth0 Realtek|RTL-8139. Is this the case, or does the internet work after connecting the system as mentioned above?

The reason I asked about the kernel upgrade, is that when you use a new kernel from "source" (meaning that you build it from scratch) then I would expect you might run into issues. Not from an "up2date" update! This should not happen, but someone should post a solution when it becomes apparent, Too many people have these cards. You should not be having this issue. But I will keep my eyes open to see what thers have experienced. Martouf should be able to guide you through the steps. Martouf please be gentle! Remember, with knowledge comes great responsibility... Beej, I'm 48 and I'm glad there is someone older than me on this forum!

Two possibilities. Look at your XF86Config-4 file again. Look for the Section "Module". It will look something like; Section "Module" Load "dbe" # Double-Buffering Extension Load "v4l" # Video for Linux Load "extmod" Load "type1" Load "freetype" Load "glx" # 3D layer EndSection If you don't see the Load "glx" line, add it. Finally, if you have Load "dri" or Load "GLcore", remove it. The second issue. What monitor are you using? Make sure that the horiz. and vertical refresh rates match what your monitor is designed for. But Mandrake worked before w/o the nvidia driver, correct? And the config file was changed from Driver "nv" or Driver "vesa" to Driver "nvidia", correct? Finally, are you trying to log into startx as user or root?

Take a look at Canon's faq page on LinuxPrinting.org support page here Look at section 25. Does this help at all?

Actually, you can install mozex as an extension from within Firefox. Tools-->options-->extensions-->get new extensions. Restart Firefox You get the mozex preferences by doing Tools-->options-->extensions-->(highlight mozex)-->Options.

Very nice! Let's hope that squid69 sees this (and others) since he posted last in March.

Quote: I do have hdd=ide-scsi in grub and I have symlinked the "cdrom" to sg0 in /dev/ In FC 2, I can't remember what the default kernel in FC1 is, kernel 2.6 does not use ide-scsi, but ide-cd. I'll have to look at my grub file. So, if you have an append line in Grub for FC2 (oops, I guess append a lilo term) hdd=ide-scsi, this will mess things up. Take it out and see what happens, if this is the case. Oh, just in case. Make sure that the cdrom/dvd drives have the correct designation. You have two drives hooked up at once? So, depending on how many connections to your ide interface there are active, one may be hdc and one hdd. Look at the command dmesg in a console window. See what the drives (if they are recognized) are designated as. Are they hdc or/and hdd? [Edited by danleff on 2004-08-21 07:29:53]

Dan, I found this Does the below section help? Quote: Mozilla & Firebird users, try this: Install Mozex from http://mozex.mozdev.org/ Got to Edit -> Preferences -> mozex (Firebird: Tools -> Preferences -> Extensions -> mozex -> Options) Enter the following information: General [X] Intercept mailto: clicks Commands Mailer: evolution mailto:%A?Subject=%S&Cc=%C&body=%B

Well, I looked at the Firefox help section on their website. In terms of the default browser; Quote: Default Browser On Windows, you can set Firefox as the default browser by clicking Set Default Browser. This will ensure Firefox is used whenever an application is trying to display a web page or when you double-click a HTML file. This feature does not work in Linux or Macintosh.

I think that the issue is compatability, not the firmware issue of the LG drive necessarily. However, the LG issue was with a specific version of Mandrake, probably a little fault on both sides. LG drives are inexpensive, but you suffer from the issue of complete compatability. I have the same issue with a generic dvd burner drive. I bet that if you look further into the issue, you will find that between all the distros that you have, there are various kernel versions on your system. The 2.4 series of kernels handle these drives differently (ide-scsi module) than the 2.6 series kernels (ide-cd module). I also guess that the upgrade from FC1 to 2 was a problem. Linux sees these drives as scsi devices and have to be set up accordingly. So, your Grub or Lilo entries have to reflect this, for each distro and kernel version that is on your system. Choose which distro and version that you want to have as your main working system and we can go from there.

No need to apologize, I did the same thing when installing a Debian system. Did not realize it until I booted into the system. User danieff? The easiest solution would be to keep the back-up drive as a third drive in the system, as I described above. If this is not possible... You can see from the posts, that a lot of folks have different solutions on how to dual boot. There are a lot of options that work. that what is confusing to some. Re-installing Suse will do the same thing that you have now, unless you choose to install it on the same drive with XP. This is one solution. You can make a floppy disk with grub on it, so that you can boot Suse when you want it. This way, you can keep XP as the main OS and use the floppy when you want to use suse. When you get comfortable with it, you can install it as your main bootloader, if you wish. But, be aware, floppies can be unreliable. Of course, i do this all the time. You can buy an external USB enclosure and place the back-up drive in it and just plug the back-up drive into the system when you want to use it in XP and back-up the system. This way you do not have to swap drives or change bios settings to change the first boot device in your system when choosing the OS that you want. You can add Suse to the XP bootloader (boot.ini), but this is a bit more complicated for a new Linux user. Some will disagree with me on this. There is a post on the forums on this that I can look up for you. In any case, you can recover XP as your boot loader now. There are two main ways of doing this, either with the rescue feature via the XP install cd, or via a floppy and restoring the MBR. Again, folks here will have a variety of opinions on this, the documented correct method versus what has worked for them. Decide what you want to do, then we can move to a solution. There are a lot of folks with solutions to this problem that have worked for them.

First, what desktop environment are you using, KDE or Gnome? I can speak for KDE. While I am not sight impaired, KDE has a variety of aides in Mandrake. Recently, there has been work on the K-Mag project. A package is being developed for KDE called kdeaccessibility. It is apparently still in development, but is available as what Linux calls source. A bit difficult to install, but it looks good. I just installed it on my Mandrake system and used kmag. A good place to read up on it is at THIS LINK. Sorry for the small text, I don quite know how to enlarge the fonts yet on the forum. If you want to give it a try, let me know and I will try to walk you through it, or suggest other options. By the way, what packages did you download already, RPM files or BZ extension files?

Let's start with the basics. How did you upgrade the kernel, by "source" (using a kernel from kernel.org) or by up2date (Redhat Network)?

When you installed Grub, did you install it to the root of the second hard drive, or to the MBR? The problem is that when you remove the Suse hard drive, the /boot/grub files on the suse drive are no where to be found and therefore, the boot does not complete. Remember, the Grub menu file and other grub boot files are on the Suse slave drive, which holds the directions of how to boot both Windows and Suse. Why not just add the third backup drive as secondary master or slave and use it when you want to back up data from XP? BTW, you can make XP the default boot option, if you wish.

I never had a need to mount the samba shares from XP Maybe you ca help me out! Anyway, most distros are set up to view XP shares. Just for kicks, this is how I view my XP shares. Make a desktop icon. Go to the desktop, right click and pick Create new -->file-->link to location. Under file name, pick any name you wish. Under Enter link to location: type in smb:/ Click OK. You now have a desktop icon that will show your XP workgroup when clicked on. Click the workgroup and your machine name appears. Click on the machine name and the XP shares come up. To view your shares, click on the share drive that you want without the $ symbol after it.

OldSpiceAP, what method did you use to set up the reiserfs partition for Yoper? Did you create it before the install with PartitionMagic or qtparted, or during the install? And I assume it is Yoper 2.0 or 2.9.2 (beta)?

I should have been more clear. Reiserfs 4 is in the YOPER kernel as an option (support). However, if you look at the 2.6.8 changelog, there is a lot of discussion/fixes regarding reiserfs in general. Anyway, some more discussion about reiserfs 4 is noted on the Yoper forum here.