danleff

cable modem---->the first (primary) cat5 port on the router. NIC card---->second port on the router. Your user documentation should have instructions on this. Are you going to be usng wireless at some point?

imroot, another user on this forum, had the same problem. Try plugging in the usb stick before booting into FC4. Just for reference, what filesystem is on the stick? Did you alter the filesystem at all, or does it still have the fat16 resident on it that it came with?

...and it did not work after rebooting? What make and model Laptop is this? You may need to disable the touchpad in the bios (since you are not using it anyway). On some laptops, you also need to play with the "Legacy USB" setting in the bios. By default, during your install, Mandrake picked up the touchpad, as a PS/2 mouse. At the hardware summary screen, you could have added the usb mouse. This is not apparent to most users installing Mandrake. Do you have more than one USB port on the laptop? See this example for the Vaio.

Oops! Looks like ndiswrapper is already installed in this distro? See the ndiswrapper wiki Ubuntu page.

RedHat 9 is too old to do the wireless easily. It would help if you could give us some more information to work on. 1. What system/motherboard is this? In other words, what onboard LAN do you have? If you have a newer motherboard, with say Gigabyte or NVIDIA LAN, Redhat 9 will not detect it. 2. Make, model and version number of the wireless card? To even venture a guess on wireless, we need to know excatly what model and version you have, as there are dozens of chipsets used in each make and model. Yes, even the same model may have a different chipset, depending on what version it is. Have you considered Fedora Core 4 as an alternative? Support is much better for both.

It should work and you should not need drivers. Was the mouse present during installation, or is it an add-on? Anyway, go to Start-->System-->Configuration-->Configure my Computer. You should be able to add it from within that configuration menu.

What happens when you type in as root user; modprobe -r ehci-hcd then try to access the drive?

Quote: How can i tell the version of the adapter? Look at the back of the case and see if it tells you. Say, wusb54g v4. Or, just give us the name of the .INF file for the adapter. Quote: So far i downloaded the ndiswrapper did the make distclean and make and make install but when i type ndiswrapper -i it says command not found Are you doing this a root user? If so, sometimes you have to find the relative path and use that. As root user, type; whereis ndiswrapper If it outputs something like /sbin/ndiswrapper, then type in as root user; /sbin/ndiswrapper -i <the name of the inf file> But during the build, did you get any error messages? The issue here is that the kernel headers or source need to be installed. See the directions. I'm not sure if this distro has either included in the base installation. Once we know these answers, I can refer you to some resources.

Which version of the WUSB54G do you have, version 1, 4? They have different chipsets. I don't know if ubuntu has the wireless tools package installed, as well as the kernel headers or source packages, but can you tell us what you did so far? Did you read the installation wiki page?

Yes, Redhat 9 support would be difficult. I know that Fedora Core 4 or Mandriva 2005 will work easily, out of the box. I have the same sata drive, the 80 gig version.

This seem to be a problem with this model of the ATI card, among others. I don't use ATI cards, but you could try to change the /etc/X11/xorg.conf file entry to vesa to get it up and running; Section "Device" Identifier "Videocard0" Driver "nv" VendorName "Videocard vendor" BoardName "NVIDIA GeForce 2 MX (generic)" Note, that this is for my card, but change the; Driver "ati" entry to Driver "vesa" Save the file and try startx again. This does not solve the main problem, but it may get the card up and running in basic mode.

Don't know if Gnome works the same way to extract a .gz file easily, but the package should work, once the directory is created. You can extract the gz file by doing; tar -zxvf qcad-2.0.4.8-1-demo.linux90.x86.tar.gz This should extract the files into the above named directory. Then you should be set to move to that directory and invoke the startup command.

What partition was grub installed to? Reference

This is an older package, designed to run under older versions of RedHat, but it does work. First, I assume that you downloaded the demo version? If you use KDE, open the file manager (the home icon on your desktop) and right click on the package. Then choose to "extract here." This should create the folder qcad-2.0.4.8-1-demo.linux90.x86 You need the package compat-libstdc++-33-3.2.3-47.fc4.i386.rpm, to get the old compatible libraries, which can be found here. Click on one of the download links and allow Fedora to install the package. Then get into the qcad directory in Konqueror. Choose in the menu, Tools-->open terminal. type in the terminal window, ./qcad_demo

Exactly! Now I'm getting to understand Boot Magic. In theory, and I have not used Boot Magic, this is one way to go. As each distro is installed, you should be able to add the newest grub to hdb0. If each distro picks up the previously installed distros, then you should get an option for each. But, the other way is the one that you are trying. Installing grub into / (root) of each new distro that you install should give you all the options for the previously installed distros. Again, this is in theory, assuming that each new distro picks up the boot options that it sees. Or, you can choose unbutu as the main Grub boot loader and add the boot lines from each new distro installed to the /boot/menu.lst file (or grub.conf, if that is what unbutu uses)manually. So, as you have it right now, if you point Boot Magic to the SuSE /boot/grub/whatever file, you should see unbutu, SuSE and Windows as options. This is why it is important to remember the partitions and what distro is on each. Try installing grub on a floppy from SuSE as a backup, in case something goes wrong. When you install each distro, do the same thing. As you get more confident, you can choose which grub install to boot all your distos (and Windows) from. The newer versions of Linux distros are more intuitive and more likely to pick up previously installed distros, as a boot option. But don't assume this. Be safe and have floppy grub backups, just in case. Search on Google on multiple boot via grub and you will get the idea. The difference here is that you have Boot Magic installed and probably know how to recover, if something goes wrong. Nice work so far. I have learned something also, in the process.

First of all, from the ATI Linux driver faq page; Quote: What computer architectures are supported by this driver? A3: Systems using 32-bit processors from Intel (Pentium III and later) and AMD (Athlon and later) are currently supported. 64-bit drivers are under development, and should be available in a future release. PowerPC, Alpha, and others are not currently supported. You seem to be trying to do 2 different things. Are you trying to install the run package, or the rpm driver package? They are two different driver sets. According to the faq page 64 bit drivers are still under development. Does anyone have more information on this?

Interesting! I thought that FC4 no longer had a problem with the kernel stack size. Anyway, see if KWiFiManager is installed (start-->Internet--> KWiFiManager). This will assist you in getting up the 256 bit WEP.

Kover. I believe that it is included on one of the Fedora cd disks.

Originally posted by zenarcher: Quote: Hey Danleff, Yes, you are talking about RAID1. There are different RAID configurations and RAID1 mirrors, so you actually have a backup. RAID0, which I am trying to do puts data on both drives...so actually, you are combining the drives (i.e. 80GB plus 80GB= 160GB. The concept is that the drives can access data much more quickly. Of course, if either drive dies, everything crashes with RAID0. Now i understand the concepts mush better between the types, from the link that you gave to SuSE 9.3. So, your purpose is to access the data quicker, rather than have a complete mirror image on both drives. Quote: If I'm understanding you correctly, concerning the two drives, I think I can do this. I can partition the first drive (sda) as I normally would...deciding on my partition sizes, etc. Then, I can partition the second drive (sdb)...using the entire drive size as ./home (probably Ext3) and when I install Mandriva, everything for ./home will automatically go to the second drive (sdb). I wouldn't have to do anything special, beyond just naming the partitions. Is that correct? zenarcher Yes, this is correct. In this senario, the /etc/fstab file will reference the location of each partition. In your case, the /home partition will be located on the second sata drive and occupy the whole drive, or a partition on the drive that you customize to a size to fit your needs. This is always useful for those who do not want to lose their data files (usually kept in the home folder) if they decide to reinstall or use another Linux distro. This multi-partition" scheme allows you to use a different partition for each main directory, /usr, /var... allowing you to more fully customize how large each partition is.

Interesting stuff! But a little over my head, I'm afraid. I aways thought of the whole idea of raid is to "mirror" the drives, so that if one goes south, you have the other drive as a backup. But, if you decide to just split the drives, this should work fine. When you install Mandriva, you should choose the "expert" option in the partitioning utility during the Mandriva installation. This way, you can assign the partitions the way that you want to. You can assign everything to /, or choose multiple partitions for say, /usr, /home...etc. So, you could assign, for example, / for everything, then assign the second sata drive (either in whole or as a limited space partition) to /home. You just highlight the partition(s) that you want to assign, hit the edit button and choose what designation that partition is to be. I think the choices are; / /boot /usr /home /var ...and so on. this way you can split the assignments to either drive and/or partition that you want. Once you assign a mount point, then that option is not repeated or allowed when you edit and assign the next partition, to prevent errors.

I wonder where Blackpage is as well. This is what makes this forum useful, everyone has an area of expertise. I saw your post on Mandrivausers as well. I have never set up sata raid in Linux, but maybe this will bump a potential answer. The problem is that sata raid is fairly new in Linux. There is nil to find using Google.

I'm in SuSE right now, but are you using Firefox? If so, go into the Edit menu-->Options/Preferences-->Advanced-->Security. Make sure that all the SSL preferences are checked, including SSL2.0 & SSL3.0.

I have PartitonMagic, but do not use Boot Magic, as any Linux distro will find the Windows installation. I currently have 10 distros working on my system, all configured with Grub. But, i would be interested to see how it works. You do have your two OS' configured correctly. How to add another? First, see the PowerQuest article here. Let me look at this further, but, the following should apply. But, let me ask first, what Linux bootloader did you use, Lilo or Grub? I suggest making as many logical partitions on the second drive as you will need for the task. This means as many ext3 partitions that you need for each distro. Keep track of the location of each partition. If you have trouble with this, you can use the current Linux distro that you have to tell you what the logical partitions are and their names. Only use PartitionMagic for this, do not allow each distro to format the partition during it's installation. Tell it to use the already existing partition that you created with PartitionMagic. No need for multiple swap partitons, as each distro will use the one that it finds, the original one that you created. Once we see how Boot Magic does it's work and if you are using Lilo or Grub, we can go further.

Originally posted by Switch_X3: Quote: i want to mount a seagate 80gb with a bunch of important stuff that i had from my windows install... ive been told to re-install mandrake and format the other hard drive but i cant afford to loose the the files i have on the disc... how do i go about mounting it without loosing everything... also this is only my 3rd day of using linux so, plz dont flame me for being a newb Who told you to reformat the drive and do a reinstall? Obviously, you do not want to reformat the hdb drive. This is the data that you want to access. First, let me ask a few questions. Is the version that you are using Mandriva Limited Edition 2005? I bet that you elected to keep security at "high" during the installation? This shows up as default, unless you changed it to standard. This means that you are only able to access the windows partition as administrator. Let me look at my install and see if there is an easy way to do this. I assume that the hdb drive was in the system when you did the Mandriva installation? ...and the windows partition, is it a fat32 partition or NTFS? If you are not sure, was the drive a Windows XP drive or Windows 98/ME partition? The partition should be mounted already, if you picked standard security. In the File manager, look under the /mnt directory. It should be labeled as win_d, or something like that. See what happens when you click on that directory. If it is blank, we need to change permissions.

Originally posted by barticle: Quote: Now there's no sound at all. I have tried changing sound drivers. Alsamixer doesn't seem to be there. The Kmix icon keeps saying "muted" even though "Mute" is not checked. What do you mean that you changed the sound drivers? Could you explain more? Are you using the onboard sound on the motherboard, or a PCI card? By any chance, did you upgrade the kernel?