danleff

Simple answer? This motherboard is not supported by Mandrake 9.2. Try Mandrake 10, or you can try adding a qualifier to the install script at boot of the install cd..input linux acpi=ht and hit the enter key. But this can have other issues as well. Is this the P4 S61 motherboard? Does it have a sata hard drive?

Take a look at the forums, specifically... http://sourceforge.net/forum/forum.php?thread_id=1039624&forum_id=67470

Sorry, I do not speak French, but if you can read English, you may want to look at the following thread; http://www.linuxcompatible.org/thread26946.html

Don't know either, but for the Mandrake 9 setup, did you install the nForce chipset drivers from NVIDIA? The sound is an issue, apparently related to what the distro picks up as the sound card. I think that I remember it should using the intel810 sound module. If you are using Mandrake 10, I would be interested to see if the hardware detection is good for this chipset. If so, I will try it on my second box. Mandrake 10 has the 2.6.x kernel, so it should work.

It may be on the Mandrake cd´s. Try there first. Look for libpython or python. I bet the package is python2.3-devel. Go to start--->system--->configuration--->packaging---> install software and do a search. Possibly pythonlib. You may also need the devel. program as well.

What do you want to do, edit photos and slideshow them? If so, Mandrake 10 comes with flphoto. I have not tried it yet, but is is a basic program. Also, there is JAlbum, which is good at the same. I think that they both use gphoto as a backend. This is my next project. To work on some photos. What camera do you have?

I assume that this is a usb model? I don´t know much about these, but we will try. I´ll ask the prelim. questions. Did you compile a kernel image or from source? Which exact kernel version? What distro is this that you are using, Mandrake, Fedora....

This is good news for some users who have these all-in-one systems. Let us know how it comes out.

I'll have to look at my SuSE install, as I have the same version. I wonder if the connection ever did work. Did the install really seem to be downloading something, or did the screen just move to the next option? Did you get an option to set up the network, or did it do so without asking any qualifying questions, such as "automatically assign...DHCP", or, start DHCP on boot?" USB modems are a problem with most distros and give a lot of people headaches. Most of us buy a router and NIC card, connect the NIC to the router and the router to the cable modem. Did you happen to look and see if this modem was listed as compatible with SuSe 9?

The reason that I asked what CD burning software that you used, is that burning cdr's with iso images can be confusing. You do not choose any options to make the CD bootable, as the image burn will lay out the files and automatically make the cd bootable. For example, in Nero, you go to the file menu and just choose the "burn image" option. It is interesting that you got part of the way into the install, until it failed. What can happen is getting a bad download of the iso image. Not common, but it happens. The system will boot the cdr, but fail at some point during the install. Did you verify the iso's that you downloaded (that the checksum was OK)? The other possibility is a funky cdrom drive. If you have 2 drives, one a cdrw and the other a cdrom, try the install using the other drive. The RedHat installer may have a problem identifying/recognizing the cd drive. Have you burned an iso image before and tried an install of any other Linux distro? Even if you burn the image correctly, if you get a bad download, then XP will read the files, but this does not tell you if all the files are really burned to the disk intact. It may look ok (you see a list of directories and filres when you view the disk), but the download resulted in incomplete (bad) iso image and image burn. A common mistake is just to burn the iso as a data cd, which does not sound like this is what you did. The last thought is trying to create an image from the iso to the hard drive, then burning that image to a cdr (such as creating a nero image). The original iso image should be directly burned to the cdr.

Mine went fine, except for no sound or networking! I hate to say it again...Mandrake 10, from what I have been reading, is sensitive to burn speed. Some are saying to burn it at 4X. If you are getting missed packages during the install, this is likely the problem. Either that, or a bad download of the iso's. It does happen. Did you verify the integrity of the downloaded iso files before burning the disks?

You had better luck than me. On my install, the network and sound are not functional. OpenOffice is installed by default. In fact, I did an expert install and deleted it, as I have StarOffice. What is not installed by default, at least for some of the packages that you note, just install from the CD's. Mandrake's control panel/configure computer is pretty good and some improvements have been made that you will like.

Very nice, thank you! I agree with jimf43, the edit..icons need an identifier to clue newer users as to what they are. I had to look at the bottom of my browser screen to id them. Most suers will not get this.

Security, what security? Seriously, if you have the firewall running, you should be fine (don't flame me others). I have had various versions of Linux up for over 4 years now, with no problem. Just don't run as root (you normally run as user anyway). The only other concern is a wireless system, and even with this, I have had no problems. As for XP, well enough said. You may want to download the latest service pack security update...

This is not an uncommon issue. Make sure you try the following; What cd burning software do you have? Did you choose "burn image" for all three disks? What medium did you burn the images on, cdrw disks or cdr disks? Make sure that you burn the images at a slow speed - such as 4X or 8x. The images do not burn correctly if they are burned at too high speed. If you already did not...attempt the install with the same cdrw drive that you burned the images on. If you burned the images on a cdrw drive, then installed on another system, or using a cd drive for the install that is older, they sometimes have trouble with cd's burned on a newer cdrw drive.

If the package installed with no errors at the end, then just go to a console (terminal) and type in /usr/bin/ymessenger, then hit the enter key. Or, go to start--->run command and type the same command in the command space.

Why not just look at the hardware compatability database at the Mandrake site to see what hardware that you have is supported? Look at the following; http://www.mandrakelinux.com/en/hardware.php3 From the Mandrake Community Edition features page; Quote: Hard disks: IDE and SCSI hard disks are supported. Hard disk size: At least 500MB is required, 1GB is recommended. Serial ATA: Most controllers are supported in non-RAID mode. SCSI controllers: most SCSI controllers are supported (Adaptec, Tekram, LSI Logic, Advansys...). RAID controllers: most RAID controllers are supported, excepted for IDE and Serial-ATA. 3Ware IDE and Serial-ATA RAID controllers are supported though. I assume that you did mean sata raid in point #4? If so, Mandrake 9.1 will not work, out of the box. I understand that Fedora Core 2, which should be out in the next several weeks, will have this support.

Hehe... Two Debian installs of woody the first time. Upgraded to kernel 2.6.0 and KDE 3.2. Now for the bad. Mandrake 10 CE failed to grab my via NIC onboard. Just tried a Debian Sarge install, same issue. Must be a MAC address issue with the router/cable modem. I just aquired a DVD and looked to download Debian Sarge. I saw a disclaimer on the Debian site about not being able to use jigdo in Windows to create the images. Quote: Note that you need Linux 2.4 or later to create DVD-sized files. Under Windows, DVD-sized images can't be created at all at the moment because the C++ library of the mingw gcc port doesn't have big file support yet. I also just tried jigdo in Debian and it failed. Apparently it peeks at the sources.list file for apt and attempts to download needed packages from the list. Since I have woody, of course, this failed (I tried to do the sarge download). I also tried it in Fedora and jigdo also complained that it could not download the source files. It also complained of a mismatch between the checksum of the jigdo and template files.

On the icons, what are you trying to change, the desktop icons (theme) or size?

What system do you have? This may be an issue with the bios. Look in the bios and see if PNP is set and turn it off, then try again. This problem is noted on Linuxquestions.org, with the following comment; Quote: Error scenario: Mandrake Linux 8.1 installs flawlessly on systems with K7T266 Pro2 Motherboards, but fails to boot after installation. Error message is "Bad EIP value". Why: The BiosPNP support in kernel 2.4.8 is broken for the KT266A chipset. Solution: Press "ESC" when you see the LILO bootloader screen, and type "linux nobiospnp". The system will boot correctly, giving you the change to edit /etc/lilo.conf. Add the "nobiospnp" option to every "append=" line in lilo.conf, then run /sbin/lilo, and reboot. Since this is a live CD version, try turning of PNP OS in the bios.

Agreed, There are new install downloads on the Debian site for network installs. During the install, they ask you which version of Debian you want to install, sarge or sid. One CD...

OK...we know what video card and monitor that you have. Can you tell us a little more about your system, as Mel said, is it a HP... Also, what version of Mandrake did you try to install? It's hard to tell what the issue is unless we know what version of each distro of linux that you are trying to install and what the system specs. are. For example, if the Mandrake version was older, then it may not support your hardware. What we now know is that you have a x-server problem with the current install. Did you get a graphical installation, or did it default to a text install? Did you choose KDE or Gnome as the default desktop environment? Are there any other messages that you get with the failure, like; No core pointer found or; no usable screen configuration found? How did you try to "repair" the problem? Rescue mode from the cd?

I propose a matrix approach, as each of us has a little of each type in us. Type 5; 1. Get your install just the way you like it. 2. Decide to experiment and try to change things. 3. Get Partimage, install it on another distro and backup the Debian install on a gz file. 4. Trash the perfectly good Debian install while fooling with it. 5. Restore the gz file to the partition and start over.

Ok...do you have samba installed on the SuSe system? I don't have SuSe 7.3 on my system, so I can't give specifics. Maybe someone else can. Getting it to work depends on how much knowledge that you have of linux and networking. If you have limited experience with Linux, then it is not very easy. To give an example, look at the following; http://www.linuxorbit.com/howto/sambahowto.php3 If you are comfortable with all this, good. The issue is that SuSe 7.3 is an older version of this distro and it may take a little work. But, We can try an easy experiment first. Just also realize that you may have trouble sharing files (if this is what you also want to do) with NTFS if this is what the XP filesystem is on your XP system. You may elect to upgrade SuSe to a newer version, if your system will support it. Let me look at my SuSe system and we can give the quick and dirty experiment a try, if someone else doesn't have a good answer for you.

See if this helps; http://www.csparks.com/redhat9Unhoarked.xml