danleff

I should have asked this before. What are you looking to do with RHEL? This is really an advanced distro for folks who have experience with Linux, who, say, want to administer a server. It is available for about $179 USD from RedHat. I have no idea where to get valid copies of this distro off the internet. But, if you are new Linux user and are looking for a distro to use as a desktop, this is probably not what you want. In this case, Fedora Core 5 would be a better choice for you. Let us know what you are exactly looking to do with Linux. We can go from there.

SuSE network installations were always interesting to me. If you don't know what to do after getting the menu screen at boot, I suggest that you wait for the final release to come out and burn a cd set to do your installation. SuSE 10.1 is still in release candidate status, so I would wait for the final release before doing anything, To use the net installation method, you need to have an ftp mirror IP address to start the installation. This assumes you know how to do this, have a broadband connection, or if DSL, how to configure your DSL conection to achieve a network installation. Any particular reason why you want to do a network installation, rather than from a cd set? To give you an idea of what steps are required to do a network installation, see this how-to. Realize this is for SuSE 9 and that I am using this as an example.

You jumped one step ahead of what I asked. Now you have the following; 1. The MBR of hds is still the Windows bootloader. 2. The MBR of hdb has Grub as the bootloader. If you want to dual boot off of hda, without changing the bios boot order, then you need to have Grub on hda. However, HP, Compaq and Dell systems sometimes have unique a partition on the Windows drive, that hold recovery and sometimes bios related settings. Before you go any further, can you answer my question about your Windows installation and cd disk media? What I want to see, is if you have a full installation of Windows on this system from a full installation cd of XP, or only the recovery disks for an HP system that includes Windows XP if you recover the system.

So, the magazine had the 5 cd disks for fedora? What volume number of the magazine is this. By step 5, I assume that you mean the partitioning section. From the Fedora installation documentation located here; Quote: Use free space on selected drives and create default layout If the selected drives have capacity that has not been assigned to a partition, this option installs Fedora Core into the free space. This ensures that no existing partition is modified by the installation process. So, this assumes that you have free space on the drive that is NOT partitioned, or used by Windows yet. I will also guess that your system has all of the disk space partitioned as NTFS? In this case, there is no free space to use for Fedora. If this is the case, you need to use a partitioning utility to shrink the Windows partition and leave empty, unpartitioned space for the Fedora installation. This also assumes that there is enough unused space on your drive to shrink the Windows partition and use it for Fedora. You can do this from within Windows XP, I think, but make sure that you defrag. the Windows drive first, to assure that no stray files are located near the end of the Windows partition.

Quote: I have first time installed the FC 5 from 5 cd sets downloaded from web and as per installation instructions from redhat site on my home PC which has XP on hda and new installed FC 5 on hdb, installation went through error free..., rebooted the PC, since hda was the default boot option, I changed the boot order in set up and set it to boot from the hdb and continued, Can you send me a link to the article/instructions that you used? What I want to see, is if the instructions were for installing on a second hard drive. The issue is, that the instructions probably were for installing Fedora on a system with one hard drive. If you change the boot order in the bios to reach Grub on hdb, you confuse Grub, as you changed the boot order, which changes the physical designation of the drives. The default installation options generally assume that you are installing Fedora one a single hard drive, hence, the partitioning utility default option assumes that this is the only drive in the system and makes a /boot partition. Was your XP preinstalled on the system, or did you install XP from a full XP cd disk? In other words, do you have a full copy of XP, or the recovery disks from HP only? We need to know this to decide what to do and if you can recover in case something goes wrong with the proposed fix.

The main question is, how much RAM is on your system? If 512 mb or more, there should be no problem. Or, if you have an older system with limited RAM, then swap is especially useful, as it decreases the need for Fedora to continuiously write to the root partition. If you have a good partitioning program, you can always add swap space, if needed. A re-installation is not really needed, in this case. You can resize one of the existing partitions to make room for swap space. A good article on the subject is located here.

the potential answer lies in another post, located here. Look at the information and tell us what you did exactly. Pay special attention to the following; 1. Did you accept the deafult options to set the partitions on the drive that you installed Fedora to? 2. Where did you tell Fedora to install the Grub bootloader to? The MBR of hda, or the boot partition of hdb? Or, did you accept the defaults. You can't change the bios boot order unless you are sure that Grub was installed correctly on the MBR on hdb, or, if it exists, the /boot partition is the first partition on that drive and set as active (to be the bootloader partition). So, was anything on the hdb drive before you installed Fedora?

You need the kernel-headers package installed to use this package. This is generally not included in a default Fedora installation. Go to Applications-->Add/Remove software-->search and type in the search box kernel-devel Choose the package that matches your kernel version, which you can get by typing in a terminal window, as root user, uname -r Pick the kernel version that exactly matches your kernel version output on uname -r. Install the package and try the wireless drivers package installation again.

Your right, these chipsets are not supported in your release. But it is supported in RHEL4 WS U2. You can't install the rpm until you have a working system. Is it possible to install using the updated version, say like the one located here. Also see the RedHat advisory here. Note the section; Quote: HP xw4300 workstations equipped with the ICH7 chipset will require initial installation through Red Hat Enterprise Linux 4 Update 2 media or the kernel will panic. It is possible to install this system with RHEL4 U0 media, then use the 'up2date' command to update the system to RHEL4 U2. However, this process may result in a kernel panic when booting to the new kernel. RHEL4 U2 updates support the ICH7 chipset and SATA devices and should be used during the primary install to avoid this issue.

The problem with reading other posts, is that folks tend to make the same mistakes that the original post thread author did in setting up their system. Let's take this one step at a time. I gather from your post, that you have a primary partition (FAT32) on the slave drive. Without knowing how you set up Grub makes it a little difficult, but I think that I see the problem. When you do the df command, you should have seen the Linux partitions. It;s important to know their locations, but i will guess; hdb2 = /boot hdb3 = / This command only shows what partitions are mounted, not all your partitons. In Fedora, I think the command should be; /sbin/fdisk -l (that's the letter small case "L") This will show you all the partitions on the drive, which I guess will be; hda1 = FAT32 hdb2 = linux boot partition hdb3 = "/" the root partition Fedora, if you select the default partitioning option, will make a small boot partition and a large root partition. Switching the boot order in the bios does nothing, as the first partition should be the FAT32 one, with no boot data on it. hence, the no OS boot problem message. Grub is installed on the second partition, which is not set active, not the first partiton that the computer finds booting from the slave drive. Doing the command dd if=/dev/hdb2 of=boot.lnx bs=512 count=1 copies the first 512 byres of data from the Linux partition. but, if the Grub reference files are not on that partition, then you likely will get a boot.ini file that is not 512 bytes. If I remember correctly, ths command assumes that grub is on the root filesystem of the linux drive. You have one boot partition (with grub bootloader data on it - hdb2) and hdb3 is the root partition. Not all the data is there. I bet your boot.lnx file is not 512 bytes in size, correct? One question about your Windows installation. Was this from a full Windows XP retail disk, or the recovery software for the Gateway system? How to fix this depends on your response. My solution? Some will argue with me on this point, but Fedora, with the default installation, assumes that it will boot from the MBR of the primary master drive, or that the first partition with a /boot partition is in fact the first partition on the drive that Fedora is installed on. I never accept the default installation partitioning scheme and always install Grub to the MBR of the primary master drive. You most likely chose the /boot partition of the slave drive. If the windows installation is truely new, with no programs and settings added, then I would reinstall Fedora, choose custom partitioning, pick the large Linux root partition to reinstall to and tell grub to be installed to the MBR (hda) of the primary master drive. This way, all the grub files (the bootloader ones form the current /boot partition and the reference files for grub) are on the same partition, the root, or / partition. The best way to do this is to delete the Linux partitions on the slave drive in Windows, then allow Fedora to make one large partition that you will mark as / on the slave drive, using the custom partitioning choice at the Fedora partitioning utility menu during the Fedora installation. You keep the FAT32 partition this way for storing files to be read and edited in both Fedora and Windows (to share files needed using both operating systems).

Quote: Linux:~ # modprobe snd-cs4236 sh: /usr/local/sbin/soundcard-on: Permission denied FATAL: Error running install command for snd_cs4236 The permissions of the file soundcard-on are incorrect. They don't mention in the article how to set them properly. I guess they assume everyone knows how. However, if you saved the script as regular user, this could explain the problem. I assume you have KDE as your GUI? Try going into the file manager as superuser. Navigate to the soundcard-on file and right click-->properties. Look at the permissions. If they are both set as your regular user (in my case it would be, for example danleff) set them for root. It may be a little more complicated than this, but let's see what happens.

Well, i see a bunch of problems. Quote: Copy the previous Fedora .config file from the fedora kernel.src.rpm, this will be your starting point for customizing the kernel and how do i do that? When i look into /usr/src i could not find any config files for kernel to be copied and i m running fedora so what is this? . This file is "hidden" by default. If you go to the file manager and use drop down the menu..-->view-->show hidden files and click on the option to show the hideen files, you will see .config. Quote: Didn't follow those steps but somehow when i reboot kernel and type uname -rm it says 2.6.10 i686 Well, if you did not follow the steps, what do you expect? The idea is to use the .config file to use the modules that are set up by default in the RHEL kernel already. Quote: Note: using kernel source from /lib/modules/2.6.10/build containing kernel version 2.6.10 So, the build used the default kernel .config file from the vanilla kernel that you downloaded, not the RHEL .config file that should have been placed correctly, per the directions. Quote: [root@rdma1 linux-iscsi-4.0.2]# make Did you really just use the [m]make[/b] command, or follow the instructions on the proper series of commands? make mrpoper make oldconfig make all make modules_install make install Of course, the make oldconfig command takes that .config file that you should have placed in the correct kernel build directiory and copies the same configuration to use in the new kernel build.

What application are you looking to start on boot and remind me what distro and version of Linux that you are using?

It looks like these soundcards are a problem. The iissue is how the card is sensed. They appear not to be plug-n-play and detected as ISA cards. Wish I had one of these to look at. My Thinkpad is an R-30 and works fine. Your Thinkpad is older and is bound to have some issues with module support. What exact model of Thinkpad is this? Yes, the 2546-30U extention, as well. Some articles that I found; Installing Fedora Core 4 on the IBM Thinkpad 600E. Suse Pro 9.0 on IBM Laptop 600E. Thinkpad Wiki. Of course, this is probably what you found.

Quote: Question is: Has anyone successfully implement Bind 9.3.2 using SQL server backend (specifically with postgres)? I can start manually with "/usr/sbin/named -f" and all is well. As root of course, however /etc/rc.d/init.d/named start" seems to cause problems ... Anyone know something I am missing? I have to admit that I have no experience with this, but let's see if you get a response from anyone. Veteran contributors have been a little scarce lately. Don't know why. DapperDan has not been around for a while, I hope all is well with him. I agree with your thoughts on FC5. Most distors now are geared toward average computer users, who do not want to mess with code and the terminal window. Understandable. This is why I have followed Linspire for some time, on and off. They have their mainstream version, geared toward users who do not want to mess with, or who do not know how to tweak their systems. They get confused with why things don't work "out of the box" all the time. Linspire also has a "developers version" with all the development tools installed by default. The problem I found with Linspire, is that it always took over with it's own customized lilo to the MBR. I have not tried the new versions lately, for this reason. They moved to grub, so maybe they changed this and added an option not to install a bootloader by default. I must say that I moved my wife's Windows system to Linspire, after she inherited some nasty viruses from a newsgroup for needlework enthusiasts, of all places! She complains about slow bootup times, but her system has been rock solid stable!

OK, on to the hardware, like floppies and such. When you insert a DVD or CD into your drive, it should be mounted and a file manager window should come up after a few seconds. FC5 should be set up to do this automagically. Floppies are a little different. They are not mounted on insertion. Once a floppy disk is in your drive, choose from the menu, Places-->Computer-->floppy drive. This mounts the drive, Hit the floppy drive icon again (if the file manager window does not appear) and the floppy should be mounted and a file manager window should appear, displaying the contents of the floppy. To look at another floppy, you need to unmount it. Close the file manger window that displays the current contents of the floppy. Right click with your mouse on the floppy icon and chose to "unmount volume." Wait a few seconds before removing the floppy for the unmount to finish. A digital camera is also differnt. I have not tried this with FC5 yet, but let me do so and let you know how I think Fedora handles this. In terms of adding things. What are you looking to add? I found a few good resources for intermediate users. See; Personal Fedora Core 5 Installation Guide and; Fedora Core 5 Installation Notes.

Great! I was going one step at a time, to see exactly how your system was set up. My next step would have been to tell you how to recover the bootloader, but you were able to do this on your own. The one minor flaw in Fedora, for many users, is the lack of default utilities that "tweakers" would like to use. Your example makes the point. FC5 is set up for average users. It assumes that you will use FC5 as your main OS and forget about Windows, or other distros. The isntaller does not, by default, install "everthing" unless you tell it to. You can change the boot time fairly easily. I also am just learning Gnome and usually use KDE as my desktop GUI, so my directions may have easier alternatives. What you need, is an editor. Go to Applications--> Add/Remove Software. You will need your root password, that you chose during the installation. Once on the Add/Remove Software screen (it can be a bit slow to come uo), click on "search." Type in mc. Scroll down to the mc - :1.46...."user firendly text console." Choose to install this program. When that is done, get to a terminal window, as root user. Type in su hit the enter key, then insert your root password. Applications-->Accessories-->Terminal. Move to the grub menu file directory. cd /boot/grub Type in mc, then choose the menu.lst file and to edit it by pushing the F4 key. Use your down arrow key to move to the Timeout= line. Change that value to 50. It probably is 10 now. Save the changes (F2), say "yes" and close the editor. The next time that you boot via grub, the menu will stay open for a while longer. In terms of your video card,what is in the system now? Is the MX440 installed now, or do you want to install it?

Quote: as your reply in problem 2, i did mess up in the mbr cause i did not fix it up the MBR for mandrake 9.5, i just straight away install FC 5. maybe thats why. but i already fix the boot manager using recovery console ( CD windows XP). i havent try yet to install again the FC cause i have assignment from my uni. OK, the point is, did you install Grub to the MBR of hda when you installed Fedora? Did you install Fedora to your primary master drive, or the second drive? Did you use the default partitoning settings, or customize the partition setings, say wipe the Mandrake partition first and install to that, or set up the partiton ahead of time, then do the installation? The grub error is related to a partition that does not exist. Either the old Mandrake Grub file was on the MBR, or you did not install Grub from Fedora to the MBR of your primary master drive. What I am getting at, is where did you install grub each time (the Mandrake installation and the Fedora one) and where did you install each distro, to the first or second (empty) drive? Quote: ooh the boot manager is compatible with linux but wont work. i think i wont use it. ...and what boot manager was this? If the boot manager that you used takes over the MBR, or changes the partition scheme in the process of using it, then this can potentually cause problems. Quote: about burning the iso dvd i use 16x, that was the speed in the dvd and my dvd rw rom also compatible to burn in 16x speed. I think you missed the point. You used the correct media for the drive. Good. But, problems with installing from a boot disk burned at too high a speed can result in problems installing or apparently bad rpm files when the install progresses. ISO images need to be burned slowly, as I mentioned in the article and my above post. This could have been the problem that you mentioned with "bad rpm files."

I just installed the same drivers on my system. Mine are also frozen at 1024x768 @ 75, which was the default in the normal FC5 installation. I also noticed that there is a new GUI setting for the NVIDIA drivers, called nvidia-settings. If you run the command as root user, it gives some basic settings, but not what we are looking for. Did you see this article on the subject? Again, it does not mention what we are looking for, but has useful information otherwise.

Interesting article. It does not say specifically what distros the script will work on. Did you add the script soundcard-on (named the same) to /usr/local/sbin/? Did you add the modprobe Configuration lines to the appropriate /etc/modprobe.conf or /etc/modprobe.d/cs4236pnp file. Do either exist? Or are you just trying to run the lines just in a terminal Window? Is fastboot disabled in the bios, or set active?

I wonder.... Here are the specs. for the monitor settings; Max Resolution : 1280 x 1024 / 66 Hz Recomend Resolution : 1024 x 768 / 85 Hz H-Scanning Frequency : 30 - 71 kHz V-Scanning Frequency : 50 - 160 Hz Pixel Frequency : 110 MHz Sync Compability : Separate Video Input : RGB Analog What exact make and model of NVIDIA video card do you have?

Very good question. I never tried any of these cards. Well, it might be challenging. See the Intel site here. Also look here. If the laptop specs are mandated by the Tech. school, have you tried calling them and asking them? Someone may already know the answer, or may give you specific recommendations, based on there experience. Are they going to be using FC4? If not, and this is your wish to install linux on your own, any reason FC4 and not 5, which nmy support the laptops hardware better? I would also check out the laptops compatability with FC4 or 5.

Good question. Can you supply the method that you used, or a link to instructions that you followed to install the NVIDIA drivers? I assume this was an rpm install? If so, your xorg file is probably altered to adapt to the drivers and you would need to do two things. Uninstall the rpm file(s) and revert back to the old xorg file. Before you do this... What settings are available to you now if you go System-->Administration--> display?

Folks are probably tired of hearing this from me, but, you need to have a plan. I suggest that you stop trying to install, uninstall and install different versions of linux. Problem #1 You are trying to install two very different Linux distros, one older (Mandrake 9.2) and one very new (Fedora Core 5). Mandrake 9.2 is older and may not support all your hardware. Before installing any distro (flavor of Linux), you should check to see if your hardware is supported. Problem #2 It looks like you have messed up your MBR, or not configured Grub during your installations correctly. Where have you been telling each distro to install Grub? To the MBR each time? If so, of which drive, your primary master drive (hda) or the second one, which could be hdb, or whatever, depending on how your system is configured with the hard drives and DVD drive. This, or course, depends on how your two hard drives are jumpered and cabled. Realize, that you can't delete or change Linux partitions after you have installed Grub, as Grub needs to reference the root linux filesystem to boot properly. So, if you have Grub installed from say, FC5, and delete Fedora's partition, grub is broke. This could account for the error 22, which means that Grub can't find a valid partition where it is looking for the kernel to boot. Windows will not boot, because the reference files that were located on the Fedora root filesystem are gone. Quote: i try to use many third party boot loader but it wont work at all and when it comes to reboot, it will go straight to XP. What boot managers did you try? Do they support Linux? Also realize that some boot managers, if installed on your hard drive, may alter the partition order, or overwrite the MBR. If they overwrite the MBR and don't support Linux, then Linux will not boot. Problem #3 Quote: i installed it but getting confused in installing the driver and it seems my dvd has corrupt file in the rpm packages Quote: i installed it using dvd iso. but does it matter? Did you verify the integrety of the downloads (allow the installer to check the integrety of the iso burn, or check to see if the md5sum was ok) before trying the installation? Also, what speed did you burn the iso to the DVD? ISO images need to be burned at a slow speed, say 4X or 8X, no faster, to burn to disk correctly. This can account for errors in packages on the disk during the installation. See my article here.

Two things. All commands to recompile the kernel need to be done as root user. Secondly, under the directions for xconfig. it states; Quote: Before using make xconfig, make sure that the Qt library is installed on the host. For a Linux host, the qt-devel-3.1.1-6 and qt-3.1.1-6 packages must be installed. So, these packages must be installed or already present on your system for xconfig to work.