Quote:
Is this what you want?
Ralink RT2561/RT61 802.11g PCI
|
Yes, now it will take a little research to find out what drivers will work with this card under linux.
Quote:
|
I ran the command /sbin/lspci and again with switch.
|
If you ran that from a konsole, ( a BASH shell ) the output is sent to the screen. Cut and paste it from there. You can send the output to a file, if you do something like this.
'/sbin/lspci > /home/username/output-file.txt'
That will create a file in your home directory called output-file.txt. You could open that with any editor on your system.
Quote:
|
Now the problem is I cant' communciate with ntfs/fat32 filesystems
|
This is really two separate problems. Communicating with a fat32 file system is easy enough. NTFS is a much longer story.
To access your fat32 partitions, you need to do three things.
1. Create a mount point in your file system.
2. Edit /etc/fstab and add an entry for each new partition.
3. Run the mount command.
The mount point is just a directory where you want to add the file system. Most distros will have a /mnt directory. This is where I suggest you add a directroy ( folder ) as the mount point. Open a konsole, and do a 'su' and enter the root password when prompted.
Now do a 'cd /mnt' This will put you in the /mnt directory. At this point do a 'mkdir win-d'. This will create a folder called win-d. You can call it anything you like. I like th e names to make sense, so I know where I am; win for windoze and d for the d drive. So now we have a structure /mnt/win-d. This will be the mount point.
You need to edit /etc/fstab as root. Do a 'cd /etc' That will put you in the /etc directory. Now open you favorite editor from the command line. Backup the fstab BEFORE you muck with it. If you screw it up, you just copy back the backup to return to normal. To back it up do a 'cp /etc/fstab /etc/fstab.bak' No news is good news, it worked if you don't get an error message. Do a 'ls -l fstab.*' to see the new file.
I use kate, so to open the file type 'kate fstab' Substitute the name of your editor, if you don't have kate. You will get a "command not found" response from the system if you do not have kate.
You will have a few lines of stuff in this file. Here is what a line will look like for a fat32 partition.
Code:
/dev/hda1 /mnt/win_c vfat umask=0,iocharset=iso8859-15,codepage=850 0 0
OK.. so what is this stuff? First part, /dev/hda1 is the partition, as linux knows it. In windoze speak, this is "C drive". hda is the first installed hard drive. The 1 is the first partition. The second hard drive would be 'hdb'. The numbering part is dependent on the partitioning.
Next part, '/mnt/win_c' This is the mount point. I created this the way you are going to in step 1. In your case, you will need to make any changes to match your system.
'vfat' tells linux the type of file system. Fat can be fat12, ( on floppy drives ) fat16 or fat32. Linux can read and write any of them.
The rest of the stuff are options. Watch the syntax. The first three fields are separated by spaces. The option string is separated by ',' ( commas ). Make sure the ' 0 0' is at the end.
To test it, as root in the konsole, run the command 'mount /dev/hda1' If you get no error messages it worked! Then do a 'cd /mnt/win_c' and then do a 'ls -l' to see your directories and files in the root of your 'C drive'.
You can try and mount your NTFS partition as well. Same process as above, except the file system type is ntfs. This will be READ ONLY. To make it writeable, there is an experimental driver for NTFS. I would not recommend you try it until you gain some linux experience.
I will look into the network card, and see if there is a driver, and how to best approach getting it working.
