danleff

When distros started to be released with the 2.6 series of kernels, and the folks used the partitioning utility to set up their Linux install partitions in Fedora Core 1 or 2, or Mandrake 10.0, there was a flurry of activity about the problem. It seems to have been solved in Mandrake 10.1 and Fedora Core 3. If a user used PartitionMagic, or other partitioning utility to make their ext3 or reiserfs partiton ahead of time, there was no issue with the geometry problem. So, any previous distro, like RedHat 9 which used the 2.4 series kernel (pre 2.6 kernel) the geometry issue was not a problem.

Originally posted by iamroot: Quote: Just enter this command at the terminal. sfdisk -d /dev/hda | sfdisk --no-reread -H255 /dev/hda Had this problem a while ago when running a FC2, Win XP config. It's a GRUB problem. This fix is for Fedora Core 2 only. It does not apply to a ReHat 9 installation. See a full explanation at this article. It is also not a grub problem, but how the Fedora disk partitioner alters the geometry, an error using the 2.6 series kernel in Fedora Core 2 and the partitioning utility in Fedora. This is not the problem in RedHat. qadri, this is a RedHat 9 install? The unforunate thing is that sfdisk re-wrote the partition table. I have to think about this. While I do, perhaps someone may have the answer right off. Do you have the Windows install cd for this system? Did you make a boot floppy for RedHat during the install? If not, you have the RedHat install disks handy? What system/motherboard is this? And, this is an IDE drive, not a sata drive in the system? Let's try one thing first. Get into the bios and the section that has settings for the hard drive, see if detection is set to "auto" or "LBA." If set to "auto" change the setting to "LBA" and save the changes, then reboot. See if you can get into Windows and RedHat via grub. If this works, great! If not set the detection to "auto" again and save the changes, then reboot. Post back what you find.

Two questions. Is this the NF7-S2 or NF7-S2G board? The latter has a gigabyte lan system that maybe Suse has not caught up to yet. Second, you do not have the router connected via USB, you do in fact, have the system connected by ethernet only (CAT5 cable)?

Can you be a little more specific? Do you just want to store the packages for KDE 3.4 on the drive, or install KDE 3.4 on a distro already installed on the drive? What distro and version are you using?

Same here. The search function does not like to search using authors of posts, rather subjects and post text.

I looked around and found that Debian does not support the 915 graphics chipset. Previous models with the 855 required special drivers as well. I bet that the drivers that you found are in a gz compressed format? Not a deb package? Can you supply a link to the download page? In this case, you need to have the sarge compilers installed to do the installation of the drivers. Did you install the development packages during the install as well? I'm afraid that I won't be much help here, except to tell you that Vaio laptops are a special problem with many Linux distros. I think it was Fedora that mentioned some special boot settings that are needed for the Vaio as well. Hopefully someone has installed Debian or Linux on this system and will see this post as well. For what it is worth, I saw that Mandrake has released beta 2 for their 10.2 vertsion with 915 chipset support. You may want to wait for the formal release of 10.2.

Try this guide. Of course, the path is relative to whether this site has a Suse 9.2 directory. I have found this mirror to be quite fast. P.S. - if the IP address is OK, then the directory does exist; /pub/suse/i386/9.2

What motherboard (if onboard sound) or sound card are you using? What distro and version of Linux (I forget)? Does other sound play fine (ie; base sound kde or cd disks)?

Try adjusting the balance and see if this has any effect, while playing a MP3 track.

In terms of the ntel board, the drivers are currently being worked on by Intel, according to some sources. AC97 means a bunch of things. It may be that the sound is not turned up all the way for the alsa sound driver. What motherboard or system is this in your system, barticle? Also, try to see if the alsa sound is turned on by typing alsamixer in a terminal window, as root user. Is the graphic bar all the way up on the first bar? Then take a look at kmix and see if the same.

I got to tell you, I used to be a die-hard lilo user. I now use grub...it is much more flexible. We just had a post from another user with the same issue. Apparently, if you choose to make Windows the default OS, it boots directly. He also used RedHat 9 also. Any possibility to post your grub.conf? We can take a look at it and see if we can get it going correctly. If not, I can look up the other post and probably guide you along. There may be one setting (the seconds that grub will pause before booting an OS) to solve the issue. If you have the RedHat install disk #1, then we can probably fix this. To answer your question more directly, yes, you can change to lilo, but I don't have redhat on any of my systems currently and will have to research this (the easy way) vs. the command line option. Did you tell Grub to install itself to the MBR or to the root partition? Did you make a boot floppy by any chance?

Hehe..., Mandrake is a little picky about this. they offer high speed access to the image, IF you are a member. One has to hunt for a valid image that actually shows the correct size that the image should be. My experience is a little narrow on DVD, but I guess there is a file limitation size on Windows (2 gig) for downloads, so linux is the answer. If you have a source for Mandrake, say, the new beta, let me know and I will give it a go!

Do you have ther folder set up in Windows with any special permissions, say to allow only the administrator to access the folder? Exactly how are you trying to access the folder? via the command line, or from the file manager? As superuser, or user?

May I ask a few more questions? Where did you get the fedora CD? Did you download it, or get it off a magazine, as an included trial version? The reason that I ask, is that normally, Fedora has three install cd disks. If this some sort of trial version, then the tools needed (packages) to compile the driver are most likely not provided on a one cd disk install. The second and third cd disk would have some of the compile packages and kernel source package needed to be able to install the driver from source, which is what this driver package is.

Thanks! It is a work in progress, so suggestions are welcome. I thought that it was helpful to get it out to use, but corrections may be needed as we go on.

A quick way to look at this is backwards compatibility. i386 should run on anything that is a 486 system (Pentium 1, or AMD K-5) or older, as long as the speed of the CPU and RAM meets the basic reqirements for the distro. The i586 and i686 should run well (is optimized for) Pentium 3 or 4, or AMD XP or newer chipsets. CPU speed and the amount or RAM in the system are the most important factors. Some distros are coming out with versions that run on 64 bit systems, which would be preferable, if they have one. Not all distros use the designations and have just i386 listed. Some don't at all and the assumption is if they are the latest releases, they will run on the newer processors that are out fine. One could build their own kernel within the distro to optimize it for their specific CPU, but that is another natter. Another assumption that is made, is that the newer the processor in the system, it is expected that the ram is sufficient for the version to run properly. but this is really a bit of an assumption.

Well, either the saleman did not know enough about linux, or he was not being truthful. The easiest solution is to get an external serial modem. DapperDan keeps track of this. See the link to his post on this subject here. The modem should be an external serial, which has it's own controller and does not rely on the computer's CPU and driver software to run. You could also try Fedora Core 2 or 3, the latter is the latest release. RedHat 9 was released in March 2003. Fedora Core 3 in November 2004. Fedora is essentually the newer version of RedHat, under a different name. If you have a cdrw burner,m you can download Fedora or any of the newer distros. If not, they can be had cheap. You don't have where you live on your profile, but if you do not have a burner, one good source is Linux Central. I can't say if the Intel ham is supported, but believe that getting an external modem is still the answer and will avoid a lot of headaches trying to load a driver for this modem, a real hassle, as RedHat does not natively support it.

Just for others to reference, as I am weak on usb modems. The compatibility index is here. The sagem driver page is here. BTW, how many cd disks did you have, 1 or 3?

The one problem that I see is getting the Intel HAM modem running. This is the only issue, as depending what exact model that you have, these are modems designed to run in Windows only, so called "winmodems." Most of the work is done by drivers to use the CPU, as these modems don't have their own controllers. Any reason why you elected RH9, rather than Fedora, which is much more current in terms of hardware support?

OK, you have two posts. Which do you want to do, use lilo or grub? Either one will allow dual boot with Windows or as many other Linux distros that you want. Let us know what other distros that you want to use.

You may want to take a look at my quick quide on burning iso images located here.

You will have to look at what specific video card is in the laptop and compare the support for it here, as well as here.

PK, now that you have a floppy to recover with if something goes wrong (and we know that you have your full Windows XP install disk), get into a terminal window again, as root user. type in; grub-install /dev/hda (hit the enter key). DO NOT...make sure you do not type in by accident grub-install /dev/hda1 Let us know if it works.

I need to copy a Win 98 driver file for a Belkin NIC card on two floppies for my boss, who has a Windows 98 system. Of course, the file comes in at just over 1.5 mb, so it needs to go on two floppies. Anyone know how to do this in Linux? I know, but he wants to add the Windows 98 system to his network at home. Next, I'll try to get him to try Linux.

What about Mplayer? See a post on this subject here.