danleff

Yes, it is an honor! Thanks Philipp and all.

I assume that you put the partition at the end of the drive? If not, you changed the partiton scheme. Additionally, the scheme may change, depending where the partition was put. Three questions. Do you have the PartitionMagic cd, or is is resident on the hard drive as a download version only? I assume also that you did not make the PartitionMagic boot floppys before making the changes? Do you have the Mandrake install disks? You may be able to do a rescue, if this is the case. Let us know what the case is.

You can't put Frozen Bubble on Win 98?

Well the problem is the hardware that IBM puts into the Thinkpads. I have a R-30 and it has an integrated AMR modem that is bust. Ethernet works fine, as does sound, depending on the distro. Some of the older Thinkpads have the trident chipset for video, which can be a problem, just to give some examples. So the distro of Linux that you are using is important as well. But do post the whole model number (eg. R-30 type 2656) and we will try to help. Even the R-30's, depending on the exact model type, have different hardware for sound and the modem.

SoulNothing, just be aware, if you use the 122 mhz system to carefully choose your distro. Mandrake 10 and Fedora have specific hardware requirements to run and install correctly. Some may disagree, but be aware of some issue, such as Mandrake wanting to install in text mode only. Before trying a distro out, check on the requirements first, so you know what to expect. Also, if the box has been sitting in a closet for some time, expect some other issues, such as a dead cmos battery. Easily fixed. You may also find KDE dead slow. You may want to choose IceWM as a desktop environemnt. Dapper Dan uses it all the time. Much less system intensive. There are a variety of cheap computers that can be had with a pre-installed Linux environment. Even WalMart is selling some with Mandrake or Linspire installed, for $299 and up. I know...you may not have the cash. But with your investment in Linux, and willingness to tinker, you may want to save up and get your own reasonable box. It will be worth it!

Take a look at the ATI fax for this issue here. Specifically this document. Finally, for reference this thread

I agree. Let us know if it works. Once you have the new memory, try Windows first and see if the stability improves.

If you have a cdr to spare, burn the 1st disk (after checking the checksum on the original, if it shows bad), at a slower speed. ISO files need to be burned at 4X or 8X, to assure a good burn. I will guess that you have a bad cd burn. You should be able to get the checksum values on the site where you got the iso files.

A few thoughts. What system is this, or what motherboard do you have? Is the mouse being plugged into a primary USB port, or into a usb hub? Thirdly, what speed did you burn the iso's at when you made the cd's?

Random reboots in Windows and freezes in Linux often point to hardware issues. Could be bad ram or a funky power supply, or the power supply is overloaded. An irq issue possibly, but this generally occurs if you have a lot of harware that needs to be assigned an irq, or problems sharing slots in the system. What version of Windows? Post some system specs. and add-ons that you have on the system. Have you recently added ram, or a pci card? Try to trace what may be the issue here. For example, if you did recently add a piece of hardware, such as a pci card, is it located next to the agp (video card) slot? If you just added ram, you should use ram that is the same make and rating. Mixing ram brands can be a problem.

Looks like it is a Abit bios bug with the nForce chipset and linux kernels. See the brief post here.

Take a look at the compatability database here for an idea of what is known to work.

I think that I may have it. Did you create the partition for Linux using PartitionMagic? And if so, did you create the partition as a primary or logical partition? Are you using Grub as your bootloader? If not, what bootloader? You may want to take a look at this thread

What type of SUSE installation is this and what is the source of the cds that you are using? Do you have the ftp install cd, commercial cd package or SUSE Linux Enterprise Server Edition?

I think I may see the problem. Change; /dev/sda1 /mnt/usbstick ext2 user,noauto,umask=0 0 0 to; /dev/sda1 /mnt/usbstick ext2 user,noauto 0 0 I believe the unmask option may be for vfat options only.

Just to clarify, it can be recognized as a usb mass storage device, so that you can plug it into the usb port and get your pictures. Is this what you are looking to do?

What version od KDE are you using? See if the kdeartwork package is installed. If not, install that package.

Sorry, I did not mean to log in as root. Most linux distros have a konqueror superuser mode via the start menu that can be accessed as user, if you know the root password. Other distros don't have this option apparent, but you can make an icon that prompts the user for the root password. This way root permissions remain intact for the directory and available only to the users who have the root password. Otherwise, Dapper Dan's suggestions for setting permissions, depending on what you want to do.

I know nothing about VMware, but what make and model of NIC are you using - through a router I assume?

You have to mount and unmount drives as root user, at least from the command line. To unmount a drive/partition, the command is; umount /dev/whateveritis Not unmount. This is a common mistake. Assuming the second hard drive is recognized correctly. Get into filemanager as superuser mode and you should not have any trouble. Depending on how konqueror or whatever is set up (different distros set it up differently) you can write in normal file manager mode. In others, you need to use superuser filemanager to move and write files.

Most likely you are experiencing one of two problems. The iso images are not burned correctly on the cd disks, as it is recommended that you burn the cd's at 4X or 8X. So, if the cd burn is not good, the packages will not install correctly. Secondly, if you have a newer kernel installed than the kernel-source package that you are trying to install, then Mandrake will give you an error/warning message that you have a newer kernel installed in the system than the source package that you are attempting to install. What we need is some indication of what the messages are that you are receiving while trying the manual install of the package to troubleshoot the issue.

If you have another available slot, try that. Stay away from the PCI slot directly next to any ISA or AGP slot. Some motherboards share resources between the ISA and the adjacent PCI slot and these issues are not uncommon when next to the AGP slot on the motherboard. So what you are probably experiencing is a resource conflict. OEM (Original Equipment Manufacturer) problems are also an issue with these cards. As martouf noted, often they are made for OEM motherboards made for Gateway or Dell systems to work specifically with that boards configuration.

What distro and version are you using? Take a look at the following linux pages about you board; http://www.linuxquestions.org/questions/history/196405 http://www.linuxquestions.org/hcl/showproduct.php?product=950

Originally posted by martouf: Quote: In most cases you must locate the config file used to build your kernel and copy it to /usr/src/linux/.config and then run "make oldconfig && make dep". "make cloneconfig && make dep" is appropriate for distros which save a copy of your kernel config in /boot . While this is true for Suse (as per the instructions), once the Mandrake kernel-source RPM was installed for me, the driver package compiled fine. The issue then is what Dapper Dan found, getting the driver to actually work in Mandrake. I agree, it looks like the company was not very truthful in expressing the complexity of the steps after installing the driver itself.

No need to "extract" the iso image. What cd burning software are you using? If Nero, click on the file dropdown menu and choose the option "burn image." A dialog box will come up and you need to point it to where the iso image for Puppy is on your hard drive. Click OK and choose to burn the image (from the dialog box) to burn at 4X or 8X. This will set up the iso image (extract it, so to speak) to a bootable cd of Puppy. If done correctly, you will see several files on the cd, such as vmlinux, image.gz and a few others. Then try to boot from the burned cd.