Admiral LSD

I missed your second post, you got it in before mine so I didn't see it. Anyway, you're not going to see NTFS write support in Linux for a long time, read only is the best you're going to get. Enabling write support has the potential to cause serious data corruption which is why the RPMs disable it and a huge warning message appears next to the relevant section in the kernel configurator. If you really need write access, the best you can do is set up a FAT partition which Linux fully supports and move your files there so you can access them in Linux. Another option is to use a program like Partition Magic to convert your NTFS partition to FAT but I wouldn't really recommend that (what you gain in Linux support you'll lose in the overall unreliability of FAT as a file system).

By all accounts, it should be working now. The NTFS module is loaded and the fstab line I posted is correct (assuming you've correctly modified the source device and destination directories to suit your setup and made sure the directory you're trying to mount it into exists). One thing I did notice just now, and it's my fault for not being entirely clear, is that you're putting the lines in the format: Code: mount -t ntfs -r -o umask=0222 /dev/hda1 /mnt/windows into fstab where in actual fact they have to be entered at the command line (as root). Lines in the format: Code: /dev/hde1 /mnt/windows ntfs noauto,ro,users,umask=0222 0 0 are fstab entries and when working right, can be mounted simply by using the destination directory: Code: mount /mnt/windows Once again, this is my fault for not being clear enough and for that I apologise. Now, if you can mount it from the command line then that means everything is set up and working right so we can move on to figuring out just why it won't work when put into fstab.

My memory was better than I thought, this is what I have in my fstab: Code: /dev/hde1 /mnt/windows ntfs noauto,ro,users,umask=0222 0 0 I'm mounting /dev/hde1 because my HDD is connected to an off board ATA133 controller but otherwise the line you need will be identical. The big difference between your setup and mine though is you're loading NTFS as a module whereas I have it compiled into my kernel proper. That shouldn't be a problem as long as you remember to load the ntfs module. To check if the module is indeed loaded, type this: Code: cat /proc/filesystems | grep ntfs If you see the word ntfs appear, it's loaded. Otherwise, type modprobe ntfs and try again. If it still doesn't work you're more than likely using the wrong module for your kernel.

If it's AC'97 audio on there (and theres a fair chance it is), then support for it is generally bundled into the Intel i810 driver for your particular sound architecture. These are the install notes for the ALSA intel-8x0 sound module which is what you should try first.

noauto has to be in the file /etc/fstab like this: Code: /dev/hda1 /mnt/windows ntfs noauto,ro,users,umask=0222 0 0 Unless you have a line like that (I'm not sure if that's entirely correct as I don't have access to my Linux box) in your fstab, mount /mnt/windows won't work, you have to mount it the long way: Code: mount -t ntfs -r -o umask=0222 /dev/hda1 /mnt/windows

If you want SATA, go for an i865 or i875 board that implements the SATA RAID features of Intel's ICH5-R South Bridge. Asus's boards should be avoided as they (stupidly) forego the ICH5-R SATA solution in favour of an in favour of an inferior PCI based solution. If you want decent onboard LAN, get an i875 board and make sure it has the Intel PRO/1000 networking chip on it as this connects straight into the North Bridge for higher performance. Asus's boards are again to be avoided here as is EPoX 4PCA3+ as again they use inferior PCI based solutions. The best i875 board that I'm aware of is Abit's IC7 but these are quite pricey. Intels offering looks pretty good but it'll be light on extra features. Gigabytes offering looked interesting too but I don't know much about it.

It's a module, so you have to modprobe it before it'll work. If you want to avoid that, open up /etc/rc.d/rc.local in your favourite editor and right at the bottom add the following line: Code: modprobe ntfs That will cause the module to be autoloaded at boot but probably not soon enough to allow your NTFS partition to me mounted at boot so add the noauto paramater to it's line in fstab like in my example above and then, if you still want it to want it to be mounted at boot, add mount /mnt/windows to rc.local.

First off, I assume you have the NTFS RPMs for Red Hat 9. If not, you can grab them, along with instructions on how to install and use them here: http://linux-ntfs.sourceforge.net/info/redhat.html As for the line in fstab, it should look something like this: Code: /dev/hda1 /mnt/windows ntfs noauto,ro,users,umask=0222 0 0

I recently converted the partitions on my Gentoo installation to XFS after I stupidly formatted them as reiser and this is how I did it (it should work on RH too): First get the Gentoo LiveCD and follow the instructions I posted in this thread (and are replicated in the Gentoo install guide) to mount your various Linux partitions however instead of mounting them all and then chrooting, mount them one by one and, using another device with enough capacity to hold the rather large tar files created by this process, tar the contents of each partition like so: Code: cd /mnt/gentootar czvf /path/to/temp/device/partitionname.tgz .umount /mnt/gentoomount /next/partition.. Recovering the system is the exact reversal of the backup procedure (with the addition steps of mounting the device holding the tar files) except for one important step: you have to add 'p' to your tar parameters to ensure permissions are restored with the files: Code: tar -zxvpf /path/to/file/partitionname.tgz

Thing is, he's got Win2k booting already or at least thats the impression I got from his last post. His problem then was how to boot Linux again. For that, the method I posted should work. I know, because it's virtually the exact same method used to install a bootloader on Gentoo and I've done that at least twice. I've also used to method to resurrect two Debian installs so I know it works outside Gentoo. Also, to add, I tried fdisk /mbr on Win2k once myself and found that it didn't touch NTLDR afterward. What does affect it is programs that overwrite the DOS volume boot sector, like the DOS/9x sys.com program. What I've surmised from this is that NTLDR is embedded in the DOS VBR and doesn't rely totally on the MBR. However, my boot partition was formatted as FAT32 (a relic of a dual boot excerise that has long been redeundant by the installation of Windows XP on my system) so it may be completely different when NTFS partitions are brought into play.

You don't need a /boot partition, If 2k is booting alright, leave it. Let's see if we can't get Linux booting properly. First up, download the Gentoo Stage 1 LiveCD. I suggest everyone get themselves a copy of this even if they don't plan on installing Gentoo as its only ~70Mb and makes a great troubleshooting aid. Secondly, boot off the LiveCD and mount your Linux partition and activate your swap partition: Code: mount /dev/hda1 /mnt/gentooswapon /dev/hda2 Next, chroot into your RH system by typing: Code: mount -o bind /proc /mnt/gentoo/procmount -o bind /dev /mnt/gentoo/proc (if you use devfs)chroot /mnt/gentoo /bin/bashsource /etc/profile Now you are "in" your RH environment, let's see about getting grub to work. First you need to install GRUB onto the mbr. To do that, type the following: Code: grub(grub will start with a command line, the next few commands have to be typed there)root hd(0,0)setup hd0quit Next, we have to verify that grub.conf is in order. Now, I forget where RH place grub.conf, from memory they place it in /etc but it may also be in /boot/grub. Wherever it is, open it in a text editor and make sure it says something like this: Code: default 0timeout 30splashimage=(hd0,0)/boot/grub/splash.xpm.gztitle=Red Hat Linuxroot (hd0,0) kernel (hd0,0)/boot/bzImage root=/dev/hda3 title=Windows 2000rootnoverify (hd0,4) chainloader (hd0,4)+1 The kernel and root lines will almost certainly look different to this example so don't change them, just verify that they're there and pointed to the correct partitions (I'm fairly certain these would be correct for your setup but tbh, I still can't get my head around the way grub enumerates drives/partitions so get a second opinion to make sure). When it's correct, save the file. To get out of the chrooted environment, type exit. Finally unmount all your partitions: Code: umount /mnt/gentoo/devumount /mnt/gentoo/procumount /mnt/gentoo and then type reboot, remove the Gentoo LiveCD and GRUB should work perfectly.

First off, what you did to stop X loading at system startup was change the systems default runlevel from 5 (I *think*) to 3. To change it back without X you have to open the file /etc/inittab in a text editor (I like to use the one in Midnight Commander, mcedit) and look for the line that reads: Code: id:3:initdefault: and change it so it reads: Code: id:5:initdefault: Then after a reboot the system should load X and your default display manager. As for the second problem, I knew how to do it once but it was a long time ago and things (such as the requirement of isapnptools and all the fun that entailed) are most likely quite different now. Instead, I'll point you to the alsa-project page for their snd-sbawe driver which is probably the best place to start looking for how to set it up on modern distributions.

I'm fairly certain nVidia have Mandrake RPMs for nvnet and nvaudio on their nForce Linux driver page: http://www.nvidia.com/object/linux_nforce_1.0-0261.html Failing that, there's always the source tarballs: Code: cd /usr/srctar zxvf ~/NVIDIA_nforce-1.0-0261.tar.gzcd nforce/nvnetmakemake install followed by the directions in my previous post on how to set up modules.conf and probe the nvnet module.

There's a thread on this forum with links to som RPMs that will enabled NTFS read support (which is all you'll get on Linux for quite some time) on Red Hat 8: http://www.linuxcompatible.org/forums/viewtopic.php?t=131 After they're installed, mounting your NTFS partition is as simple as any other partition type: Code: mount -t ntfs -r -o umask=0222 /dev/hda1 /mnt/windows that assumes /mnt/windows exists on your system. If it doesn't create it with the following command (as root): Code: mkdir /mnt/windows

Change fonts, how you mean? I was just using standard board formatting codes to highlight an area where I thought you were making a mistake. To my knowledge, there is no Linux media player called 'myplayer', the closest I can think of is 'mplayer' (a quick google search turned up something called 'myplayer' but I believe if Windows only, the site was in Japanese sho I can't be sure). This is why I don't bother with RPM or any of the cheap hacks designed to make it more like a decent package management system. Here on Gentoo I just type: Code: USE="dvd" emerge mplayer and everything required to get mplayer (or anything else for that matter) up and running is downloaded, compiled and installed with a minimum of fuss. Not even Debian is this simple.

try yum install mplayer

Are the mobility chips supported in the Sheider Digital fglrx drivers? These work like a charm (after I patched the kernel to allow proper AGPGART support on my nForce2 chipset) for my 9500 Pro.

2.6.0-test1 is out if anyone is interested. I got it through Portage on Gentoo but it should be on kernel.org as well.

heh, I had all that months ago

Why not just do the sensible thing and give Red Hat the flick? RPM: Retarded Package Manager

They aren't really going to call it that, are they?

Before you start, download these and have them somewhere you can access from either the remaining virtual terminals on the LiveCD or the chrooted Gentoo environment. You'll need them if you want any hope of being able to use 3D on your 9700 under Linux. Included in there is a patch to enable AGPGART support on nForce/nForce2 for non-nVidia graphics cards. Also included are drivers for the onboard audio and LAN but don't worry about these as you can emerge the LAN driver later (but preferably after you've compiled the kernel and before you reboot after finishing the chroot install) and the onboard audio, if you use it, will be handled by ALSA (remember to compile sound support into the kernel (as a module) but don't select any of the drivers underneath. After you've booted into your new Gentoo system, go and read the Gentoo ALSA for instructions on how to set ALSA up. If you use the onboard nVidia SoundStorm audio, the driver to use is intel8x0).

All you really need to know is the horizontal and vertical sync ranges. If you can find out your monitors model number (it should be printed on the back of your monitor if you don't have your manual or the box it came in) do a search on it in Google and see what you come up with. As soon as you have the ranges you can run the xf86config script (you shouldn't have to know the path for Xconfigurator btw, you should just be able to type Xconf and press the tab key to complete it followed by enter) to configure XFree86.

Quote: Went wiith 1.4rc4 and all 3 stages tarballz.. I figured why just basic? ..besides might want more.. Stage 1 allows you to fully tailor and customise it to your system as you download compile and install virtually everything to a set of compile flags you specify. The downside is that it takes an absolute age to install, my own install took 3 days but much of that was because I was downloading everything over a 56k modem. The stage 2 and 3 LiveCDs don't contain any more than the stage 1 in terms of packages, they just have more of the base system compiled to save time. The down side to these is that you don't get as much flexibility as you do with Stage 1.

Quote: Recently DLed Gentoo. just one ISO? OK.. My BSD has 4 (I think..) What.. isn't on Gentoo.. Humm maybe I go to Gentoo.org and ask Yep, just the one ~70Mb ISO (assuming you downloaded the Stage 1 ISO). All it has on it is the basic installation kernel and the base file system tarball, you download and compile everything else from source as you go along. It isn't that difficult, everything's quite well documented in the install.txt file in the root of the CD. What I like to do when I'm installing is to set a root password (type passwd as soon as the LiveCD has finished booting and enter your password) so I can access all 4 of the LiveCDs virtual terminals and then have the Install Guide open in nano on one of them while I'm chroot'ed on another so I can keep referring to the install guide as I go along.