danleff

During the install, Mandrake should have asked you what disks that you had, with an option to de-select the ones that you did not have. But this sounds like a different issue, maybe an x-window issue. What happens when you type startx at the console? What system specs do you have?

From the Linuxant FAQ page; Quote: The driver module is separate from your kernel, but it must have been compiled using the same sources. This means that whenever you upgrade your kernel, you have two possibilities: 1) Download the driver package from Linuxant's web site that corresponds to your new kernel version - if it's a very recent kernel, we might not have released a package for it yet. 2) Use the generic drivers (downloadable from Linuxant's web site) instead of using drivers specific to a single Linux distribution and kernel. To use the generic drivers, the kernel source tree used to build the kernel that you are running has to be installed. When using the kernel supplied by your Linux distribution, you can simply install the "kernel-source" package. With the generic drivers, you can easily recompile the module after upgrading your kernel by running the following command: dldrconfig --kernel Found at DriverLoader FAQ

Do you by chance have Mandrake 10 installed? This happened to me as well. Qtparted also failed, due to the way that Mandrake formatted the partition during it's install. If you have NTFS for your Windows XP install, you must use PartitionMagic, not Qtparted. Trust me on this. Qtparted also has some dependencies that may make it hard to install, depending on your distro. I had to remove Mandrake (PatrtitionMagic was then able to read the drive without errors), re-partition the affected partition(s) with PartitionMagic, then tell Mandrake to use the already existing partition. Let us know what your current situation is in more detail, before proceding.

Sure. The first thing that you do is back-up your current /etc/lilo file to a safe place. Open into a file manager in superuser mode, navigate to /etc/lilo and double click to open it. You may elect to use any editor that you choose, as well. Kate or gedit work fine. Edit the file as you wish. I always just place a hash mark at the beginning of any line that I want lilo to ignore, assuming you know what entries that you want to ignore, or delete. Save the file. Run, as superuser console (root console); /sbin/lilo If the console processes your entires without any error, you are set. If there is a problem, it will show you the line that has an error. NOTE: if you have more than one distro on the system, you must edit the lilo from within the distro that you installed lilo from. For example, if you have both Mandake and Debian on your system, and you installed Mandrake last, telling Mandrake to use lilo at the MBR (usually /dev/hda1), you must edit in Mandrake, as this is the active lilo entry to the mbr. Otherwise, the lilo from whatever distro you are in will over-write with it's own lilo. You may or may not want this. When editing Lilo, you need to remove all the releventlines for the distro that you want to remove, generally 4 or 5 lines of text, belonging to the distro you want to remove. For example, you want to remove the Debian entry; boot=/dev/hda map=/boot/map vga=normal default="windows" keytable=/boot/us.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="linux" root=/dev/hda5 initrd=/boot/initrd.img append="quiet devfs=mount acpi=off" read-only image=/boot/vmlinuz label="Debian" root=/dev/hda6 initrd=/boot/initrd.img append="failsafe devfs=nomount acpi=off" read-only The bold entries would need to be removed. The Label= part of the indented entry tells you which distro that these lines belong to. Of course, the label entry depends on what lilo assigned to it, unless you custom added it yourself. You MUST run /sbin/lilo, or in some systems, just lilo in the console, after the edit and save, or you may render the distro/system unbootable. In other words, be sure of the items that you want to delete, make sure you get no errors after running /sbin/lilo. If you really screw up, just replace the edited lilo with the backup file and run lilo again.

Believe it or not..the same here. Knoppix 3.4 found my D-Link card as ath0, using the ath-hal driver, but no connect! Steady light on the card...no connect. We must be missing something simple!

Yes, of course. You will be running Office in Linux, not Windows! You would need to install it, just as you would any other application. The best way to do ths is to get Crossover Office from Codweavers. Office runs quite well, as does Internet Explorer. But Crossover is not free. What it does do is take the pain out of assuring that the correct ddl files are present to run Microsift Office. Wine creates (if installed correctly) it's own "c" drive (which is really a directory) within Linux. In terms of games, Wine will run some games, like Warcraft 3. For a reference, look Frank's Corner's Warcraft howto. It is possible to run apps in Wine using a Win 98 directory, but not XP. Wine can use Win 98 ddl files, but not those that are native to XP. When wine source is installed and you configure the setup, it will look for a valid Win 98 installation. Otherwise, you choose to run wine straight from Linux, which most will distros have Wine set to run as. It also depends on if Wine is a binary install, or source install. The other issue, of course, is if you have XP installed on an NTFS partition.

Good find! Thanks! I'll give it a go. BTW, what happened to the e-mail notification on threads responded to? I am having a heck of a time keeping track of things. Did I miss something when the forum was upgraded?

Yes, also, make sure that the changes did take place, as DapperDan suggested, by looking at XF86Config. Quote: NOTE: In other distros or versions, take note that you may need to comment out the entries in XF86Config-4 (or XF86Config, if your distro does not have the XF86Config-4 file), such as “load DRI” and “load GLCore.” Fedora, for example, uses a LOAD DRI entry that needs to be commented out (by putting a hash mark # before the entry, on the line that the entry resides on. Also look to see if you commented out any entries related to LOAD DRI and LOAD GLCore (near the top of the file) that can cause these errors to occur.

The differnce in RedHat will be that you may need to mnually edit the inittab file, as supplied by DapperDan. But, the link to the thread is; http://www.linuxcompatible.org/thread654-1.html I also agree with DapperDan. A newer version of RedHat will most likely pick up your exact card.

I´ll tell you right off the bat, based on your system, Mandrake 9.2 will give you problems. Mandrake 10 has issues with sata drives, so I assume 9.2 will also. I will defer to someone who has installed a version of Linux on sata to make a suggestion. The issue is how Mandrake recognizes sata drives vs. ide drives. There is another post about this issue. http://www.linuxcompatible.org/thread27247-1.html The file that you downloaded is not a Mandrake iso file. The file name should have looked like Mandrake91-cd1-inst.i586.iso, where cd1 is the first install cd and so on. there are 3 iso´s to download. They then need to be burned to cd´s using Nero or any cd burning package that supports the ¨burn image¨ function, not just burning the file itself to the cd media. The other issue is the ATI video card. Many flavors of Linux have difficulty with these cards. Let see if someone else has a suggestion for your hardware. Also, are you using Netscape to try the downloads? If so, you need to hold down the shift key, then click on the iso file to download the file correctly.

This is a sata hard drive. There is another post about sata HD issues posted recently. Apparently, Mandrake has problems with these drives. Do you have an ide drive that you could try in the system?

Yep! You have to install Office 2000, or whatever suite that you have first, just as you do in Windows. Are you trying to run the excel exe file it from a win 98 partition? There is a good howto at the following site; http://frankscorner.org/modules.php?op=m...d=20&page=1

I'm currently running Lindows Laptop Edition. Works great, except for the wireless. I may yet try Mandrake or Fedora, but perhaps see if Mepis can pick it up first.

Ah... I think that I get it now. Mandrake only sees the ide drive as the active boot drive, or hde1. Let me think on this one. I bet lilo is on the ide drive. When using raid, for example, Mandrake sees primary or first drive, the ide drive, as hde. I was going to have you try a little experiment. Go into the bios and change the hd0 to hd1 as the primary boot drive.

I share your frustration. I have a D-Link that will not work as well. Of course it is pcmcia. It is supposed to use the madwifi driver. Well, try to find the correct version! If I find anything I will let you know.Then we can share a toast! I assume that you saw the following; http://members.iinet.net.au/~mtriggs/wireless.html Also, do you have WEP or WPA?

I think that I may understand what you mean. If you have a win 98 system, depending on how wine was installed (ie; rpm vs. by source) wine will use the windows directory (fat32) to place/look for the application. However, depending on how wine was installed (again), often the wine "c" directory is placed in your home directory. You may not see this in a file manager. as it often can only be seen as a hiden file. In my system, where wine created the folders in my home directory, "c" is located in /home/danleff/.wine. Note the dot before the wine. If this is the case in your system, then you can view the directory in Konqueror, by going to the top menu view--> show hidden files and you can then view this directory. Again, it depends on the versin of wine, if you have a "valid" win 98 directory that wine can find, or if wine is installed as "stand alone" because you do not have a valid win 98 directory. Wine does not like and hs problems with Windows XP applications, as the dll fikes that are used to run the apps in XP do not play nice with wine.

When running a windows application from console, try to cd into the directory where the application resides. Then, in a console, type the exact exe file that you want to run. For example, if you want to run danleff.exe and resides is in the home directory; cd /home wine danleff.exe Also, the app that you are attempting to run, did you just copy the exe file from a Windows directory, say in win 98, or attempt to install it with wine. Give an example of what exact application that you want to run and where the app resides - your home directory... A good tryout app is solitare. In this cae, you can copy the sol.exe from a win 98 directory to, say, your home directory (ie; /home/danleff), then run wine sol.exe from that directory in Linux. But, in most cases, such as Dreamweaver, you need to install the app with wine first, then run the exe file from the native directory. However, if your win system is win 98, you can run it from the native directory of the windows partition. Not so with Win XP, which wine will have trouble with. I hope that I am clear. Post what you have and we will try to help.

There have been a few posts on this model. Good to hear that you got the drivers to work Try booting with the acpi=off option. Or try noapic. Are you using Grub or Lilo as your bootloader?

First, before installing any flavor of Linux, you need to decide what you are looking to do with Linux. Just to try it out, specific tasks that you want to do... Then determine what distro (flavor) of Linux will meet those needs. Thirdly, does your hardware support the version you would like to install. A Laptop, desktop...Posting some information about the system that you are using would help. Finally, I do not recommend installing Linux to a production system. What I mean is, if this is the first time that you attempt this, do not do it on a system that you expect to use day to day. If something goes wrong, and you have Windows on the system, then you run the risk of trashing the system, or making windows unbootable. I am not trying to scare you, just give you some tips. I would enlist the help of someome who knows how to do this to guide you through the process. They can also share their opinions about is what you are doing is really what you want or expect. A google search is gret to get facts and see what the process is all about. For example; http://www.linuxvoodoo.com/resources/howtos/HOWTO/Installation-HOWTO/ Give is a little background on what you expect to do. There are a lot of great people on this forum that can help. Mandrake generally comes with 3 "iso" files that you download, that contain the install software and applications. You will need access to a cdrw burner to extract the file(s) to cd media. Make sure you downloaded the right one for your system. For example, is your system an "IBM" compatibls system, a MAC...? What exact name is the iso file that you downloaded? There are also several cd based versions of Linux that will run off a cdrom drive and give you a good idea of how the newer Linux versions run, without installing Linux on your hard drive. Then you can make a choice. Let us know what you think. And by the way, welcome!

Some will work and others wont. Some take a bit of work. Let's see what DapperDan has, but for quicktime files, why not try Totem Movie Player? Here is a link for some apps that work; http://mc1soft.com/linux/applications_tested.htm ...and another favorite of mine; http://frankscorner.org/

This often comes up when the rpm file is not compatible with your distro. Are you choosing rpm's specific for your distro and version, or just picking rpm's? Also, are you choosing the US sites or other rpmfind (euro) sites to download the rpm's?

Believe it or not, you should be able to write lilo to the NTFS drive, as it works for me. The issue my be the sata drive. I wish that I had one to test this out on. Is this a nForce chipset motherboard as well? Is this your only (production) system? Otherwise we can try a few things. Lilo looks correct, but this could be a bios issue, as well. See the following thread; http://www.linuxquestions.org/questions/history/162506 If you are up to this, we could try some things that may work. I had a problem with raid and Mandrake 9 like this. Take note of the last post on the link; "I had this sort of trouble with lilo recently. You have to tell DOS that it's actually on the first BIOS drive - in lilo this is "map-drive=0x81 to=0x80". Also, if you have DOS compatibility flag or Boot flag on the IDE drive, turn them off with fdisk." What I wonder about, is the way that the sata drive is set up. Is it set as primary master or cable select? Same question for the ide drive...how is it jumpered?

Did you do; cd /mnt mkdir /usbstick ...first? Then issue the command mount /dev/sda1 /mnt/usbstick. Remember, there is a space between mount and /dev/sda1, as well as sda1 and /mnt/usbstick. This also has to be done as root user.

I'm looking at this now. Are the deleted files in the trash bin?

Well, not knowing much about Morphix....I've only done this with a rescue disk, which automates the process somewhat. Assuming that Mandrake is gone, try using the live cd boot. How you edit lilo (if the live cd allows the edit, as some distros have lilo protected as root) depends if lilo is protected as root or user permissions. Yes, /etc/lilo is the file. Look at that file and make sure that it is indeed there. If so, make sure that at the beginning of lilo, the lines something like lba32 boot=/dev/hda (assuming that hda is the mbr location) The key is the boot=/dev/hda, which signifies installing lilo on the mbr. If it is not installed on the mbr, it will say something different, say if lilo was installed on a boot partition other than the mbr. Edit this if necessary and save the changes. If Morphix Live cd does not auto mount the partition that it is installed on, then at a console, issue the following commands; mount -t ext3 /dev/hdxx /mnt (xx= the partition where Morphix is installed on. If you have not been able to modify lilo, try it after issuing the next command) chroot /mnt /sbin/lilo Just make sure that you look at and modify, if needed, the lilo file to see if the boot= line is correct, before running the /sbin/lilo command. Lilo, unlike Grub, needs this last command to actually write the information on the mbr.