rolf

whatever. I see people asking how to do something; I see people saying there is some sort of underhanded thing going on about the Club; I know it can be done. I have done it. Many times. No problems. There might be easier ways but I don't know of them. I have practiced a method that has worked for years and don't feel much need to find another one because whiners can't be bothered to apply themselves. It takes a little effort. It takes a bit of effort to write the howto and a bit more to make a post about it. There seem to be more and more trolls to deal with and that really doesn't justify the effort, does it? [edited by spinynorman]

I've done an hd install of 2005 LE from downloaded isos extracted to hard drive. I have been doing this for several years and, although the hd_grub image has changed a little, the basic procedure has been like the one in this -> Howto.

HD install Howto. Also, http://qa.mandrakesoft.com/twiki/bin/view/...Network_with_No

Assuming you get the Mandriva lilo boot menu, press Esc to get a command prompt and boot with linux single This should get you a prompt in single user mode. Type passwd and press Enter to get a prompt for the password. Give a root password and confirm it after you press Enter. That is your root password. Then, try for the desktop with init 5 If you get into the desktop, open a terminal and type userdrake to start a program for adding a user. I think that will work.

CD's that won't boot can be due to burning too fast (try slower), not using the burning program properly (choose burn image in Nero, or see here for other Windows soft: http://www1.mandrivalinux.com/howtos/iso/howtoisoen.html ), sometimes, booting with linux ide=nodma will help with a cdrom reader problem (press F1, F2, according to the CD splash screen, if it boots this far, to see the help messages). If you extract good isos to the hard drive, you can do a hard drive install: http://home.mindspring.com/~rolfpedersen/M...%20Install.html

There are howtos posted on the web for using the nt bootloader. Some might have already been linked in a previous post to this thread. I have used the nt bootloader in XP following along the lines of this one: http://www.plugnpray.co.uk/linux/lilo-nt/1.html

Also, for a general method of finding packages in your configured media that provide missing files: [root@localhost envelope]# urpmf libdns_sd.so libmDNSResponder1:/usr/lib/libdns_sd.so.1 libmDNSResponder1-devel:/usr/lib/libdns_sd.so [root@localhost envelope]# urpmq --sources libmDNSResponder1-devel ftp://ftp.ciril.fr/pub/linux/mandrakelinux/official/2005/i586/media/contrib/libmDNSResponder1-devel-98-4mdk.i586.rpm This shows the rpm in contrib/, so you would need to have a contrib/ source added to find this out. Whether this method will produce an rpm that satisfies the needs of a third-party rpm is another question.

I don't know about installing from isos. It used to be only the first iso could be used by the installer. Now, I see reports that Mandriva 2005 will successfully install from all the isos. Using boot.iso to install from isos You must check the md5sum of the downloaded isos. Here is an outline of how, for some years, I have installed from hard disk after extracting the isos. Should be no need to redownload if you have good isos on your disk: Mandriva Hard Disk Install

http://reviews.cnet.com/5208-6129-0.html?f...essageID=142069

I would say you have configured sources for main (Installation CD) contrib (Contrib CD) and update_source (updates) twice, plus jpackage, jpackage sources, and Contrib Sources are probably not needed. Go you the mirror you are using and look in official/10.0/i586/Mandrake/. The RPMS directory is main or Installation CD, RPMS2 is contrib/, and RPMS3 is for the jpackage rpms. I think jpackage are java-related packages for java development, so I don't think you need that. If you ever wanted to rebuild a source rpm (contains human-readable/writable source code) to the binary rpm (contains the compiled, machine-executable code, the actual program, libraries, config files, plus docs files, etc.), you could probably download it from the mirror as you need it. In other words, I don't think you need it as a Software Manager source. Up to you. IIANM, updates is the source for the automatic update applet and update_source is what MandrakeUpdate calls the update repository. Both are the same, security rpm updates plus, occasionally, bugfixes. I started out using MandrakeUpdate and ran afoul of the automatic applet service, so I discontinued the automatic update service. Again, up to you. If I am correct about the duplicates, I would keep 7. update_source 9. main 10. contrib and use MandrakeUpdate (called like that from a root command prompt or called something like Mandrakelinux Update in the menu) for security updates. You can do everything you can do in the gui from the command line and more. The gui is a frontend to the urpmi set of commands, which are an extension to the rpm command. For example, get a list of what your media names are: $ urpmq --list-media Now, to verify which of your sources contain which rpms, go to the mirror and choose the name of one of the packages in one of the directories, for example: .../official/10.0/i586/Mandrake/RPMS2/acid-0.9.6b23-3mdk.noarch.rpm Now, urpmi and urpmq usually want to know only the package name, not all the versioning or path, so, to check if the acid package is part of the contrib source, do: # urpmq --sources --media contrib acid and, if this command gives you the path to a directory, you know that directory is the contrib source. I will recommend you run the --sources switch to urpmq as root. At some point, 10.1, I believe, this requires root privileges because some sources are set up with a password and, for security in a multi-user system, only root should see the password. You could verify all your sources this way to see which are duplicates and remove duplicates. You could remove in Media Manager or on the command line: # urpmi.removemedia Contrib CD \(ftp3\) or whatever is the name given by urpmq --list-media. The parentheses will have to be "escaped" with a backslash to be read by the shell (command processor). See man urpmi, man urpme, man urpmq, man urpmf, man urpmi.addmedia, man urpmi.removemedia, man urpmi.update, man rpm and the following sites for more info: http://qa.mandrakesoft.com/twiki/bin/view/.../UrpmiResources http://www.rpm.org/max-rpm/

The only experiences I have had that might be related to your situation are: 1. Re-installing the kernel-source has led to a successful build of the nvidia driver where it did not build before. 2. For hangs, I seem to solve that by adding the following to the Device section of xorg.conf: Option "nvagp" "0" There is so much hardware variation that it is impossible to say what works for one will work for another. If you didn't know already, there is an nvidia forum here: http://www.nvnews.net/vbulletin/forumdispl...p?s=&forumid=14

Kristi, there was a problem with Mandrake's guarddog and 2.6 kernels where the guarddog firewall rules were not getting loaded at boot. You only have to open guarddog and OK to get the rules loaded. Simon Edwards, who writes guarddog, made a Mandrake rpm that got around that problem and I have been using it since. Not sure if this is your situation as I am not monitoring Mandrake's guarddog package. Simon has an rpm and urpmi source at his web page: http://www.simonzone.com/software/guarddog/#download About 2.6.11-2mdk, I have loaded it and run it, mostly because I have trouble with my Plextor sata dvd-rw not working on my silicon image 3112 onboard chip, except it works fine in XP, so I hope for improvements from the kernel. They don't seem to be there in this one and alsa stopped working for me. The oss driver works, though.

FWIW, there have been a couple of times when the build of the nvidia module failed for me, the latest involving "nvidia.ko" is missing, IIRC, and I got success by removing the kernel source and reinstalling it. Since I have been building kernels against sources, I thought it might have had something to do with the sources being 'not pristine'. I did 'make clean' and 'make mrproper' against the used sources but that did not help.

In Mandrake, the windows install is usually mounted at /mnt/win_c. You could ls /mnt to see if there is something like that there and cd to it. You will have to cd along the path to where the rpm is located in windows. For example, on my machine, with XP installed: cd /mnt/win_c/Documents\ and\ Settings/rolf/Desktop gets me to the desktop. What Steve says to do, urpmi kernel-source-2.6, ought to work, if urpmi sources have been set up for you by install, as they should be. If not, you can put the cd in your reader and install from there. You need to know what the mount point of your reader is. Check that with grep cdrom /etc/fstab Look for something like /mnt/cdrom and that is the mount point. I've got that kernel-source rpm on CD2, BTW, under media/main2/kernel-source-2.6-2.6.8.1-12mdk.i586.rpm So, the path would be: /mnt/cdrom/media/main2/kernel-source-2.6-2.6.8.1-12mdk.i586.rpm and rpm -ivh /mnt/cdrom/media/main2/kernel-source-2.6-2.6.8.1-12mdk.i586.rpm or urpmi /mnt/cdrom/media/main2/kernel-source-2.6-2.6.8.1-12mdk.i586.rpm using the mount point of your reader should do the install. You can use tab completion to make it easier to navigate. That is type part of the command, for instance: ls /mnt/cdrom/ and press Tab to see what the options are. Type a little more of the path and press Tab again to complete more of the command, until you get what you want, then press Return to execute the command. If the CD can't be viewed with the ls command, it might be you need to mount the cdrom first. Do this, as root, with mount /mnt/cdrom or whatever the mount point of your reader is.

Angelina, I'll just try to deal with the problem installing the kernel-source rpm. Are you in the directory where that rpm is located when you give the urpmi command? In other words, when you list the directory contents, by typing ls and Return, do you see kernel-source-2.6.8.1-12mdk.rpm? If not, you have to use the 'change directory' command, cd, to get to that directory, first. If you are in that directory, check that the downloaded file is ok with rpm -K kernel-source-2.6.8.1-12mdk.rpm To avoid typos, you can just type the first part of the file name and press Tab to auto-complete the command. If the rpm checks out ok, let's see what are your configured urpmi sources with urpmq --list-media HTH

Angelina, Write down what you have done and what you have trouble with. If a command or step isn't working, write down exactly what you tried and what is the result, including error messages.

In order to give you the comprehensive instructions you request, comprehensive information from you is needed. That you have no gui is a biggie. I'll suggest a few things and ask a few questions to try to get headed in the direction of a solution. The configuration programs require root privileges, so log in to the text mode as root, when you boot Mandrake. You could try to build the nvidia commercial driver, at this point, or you could try to get a driver installed that will give you a gui, which should make things a lot easier, so I will start with that. I don't know whether only having CD1 will limit your choices but to try to get a basic gui working, logged as root, start the Mandrake X configuration gui with: XFdrake In this wizard in text mode, navigate between buttons with Tab, move through lists with the arrow keys, press Enter to push a button. With the graphics card item selected, use Tab to get the focus to 'Do' and press enter. Navigate the list to nv and press Enter. This is the XOrg open source nvidia driver and should work for your card. Make some reasonable settings acording to your monitor specs in the other parts of the wizard and test your choices to see if they will work. Don't make choices that exceed your monitor's capabilities as it could be damaged, although it seems the program is able to back out of most overamped configuraions with a failure to start the X server. If nv doesn't work, choose vesa for the driver. It is a lower-performance generic driver that should work in most any case. If this strategy works, it ought to be easier to get things installed and work in the gui to configure your computer. When, in linux, you type uname -r What is the version of the kernel you are running, as shown by the output to this command? What is the exact name of the kernel-source rpm you have downloaded? It is important that the versions match. What patch? The instructions you link to seem clear enough, although I am running the nVidia commercial driver built without changing it on 10.1, so you might want to try by downloading, printing, and following the instructions from the nVidia site, without editing the source files, at first. You should be able to install the kernel-source rpm (I have not tried installing an rpm stored on a windows partition but I guess it would work) from text mode, if you want to go that way. As root, when you navigate to where the rpm is. It should be this: kernel-source-2.6-2.6.8.1-12mdk.i586.rpm and uname -r should tell you kernel-2.6.8.1.12mdk If they don't match, don't even try. If they match, do urpmi kernel-source-2.6-2.6.8.1-12mdk.i586.rpm If that works, you have the kernel sources installed for your running kernel. BTW, pressing Tab completes partially-typed commands or file names, so you might want to save some typing with that feature. If you got this far, navigate to where the nVidia driver is and follow the instructions to build it. If it builds, you have to edit the X server configuration file and I don't know if it will be configured well enough without running XFdrake at least once, so do that first. Use the instructions about vi that are in your link. You might have to urpmi vi in case it is not installed. Open the config file in vi with: vi /etc/X11/xorg.conf There will be a section that looks similar to this: Section "Module" Load "dbe" # Double-Buffering Extension Load "v4l" # Video for Linux Load "extmod" Load "type1" Load "freetype" Load "glx" # 3D layer #Load "/usr/X11R6/lib/modules/extensions/libglx.a" EndSection The # sign precedes a 'comment' in this type of file, meaning it is there for documentation and is not used by the program. If the Load "glx" # 3D layer line is commented, remove the comment. In the next section, Section "Device" Identifier "device1" Driver "nvidia" Option "DPMS" Option "nvagp" "0" EndSection edit the Driver statement to be "nvidia". The Option "nvagp" "0" solves problems for some buggy cards. You can leave that out for the first try. Exit insert mode and save as is explained in the instructions you link. Open another config file with vi /etc/modprobe.preload At the bottom, add nvidia on a line by itself. Save the file. Edit: I missed a step here. After the module is built, it isn't loaded. Your config file edits will get it loaded automatically at boot time but, before you init 5 this first time, you have to load the module with modprobe nvidia Also, you might have a video driver already loaded from a previous X configuration, so check if you do and remove that before loading the nvidia module. To see what drivers are loaded, do lsmod|less The output is too long for the screen, so the pager, less, is piped to the command with the | symbol. Use the arrow keys to view the output and type q to quit. If you see the vesa or nv driver, remove it with modprobe -r nv for example. Your monitor and mouse should already be configured by running XFdrake, so start the gui with init 5 It's hard to imagine your exact situation, so ask questions if this does not compute. In text mode, you can learn a lot about commands by reading the manual pages. For example, type man urpmi man xorg.conf etc. There are man pages for almost every command/program and many configuration files. Quit the man page by typing q

I don't like the looks of 'modprobe ide-floppy in the the middle of if/fi statements. Put your custom commands all the way at the end of the file and add a carriage return as, once, I had trouble without the empty new line at the end of a config file. Beyond that, I thought I read that you have to mount the floppy after ide-floppy is loaded. You can check if it is loaded by typing lsmod as root or you can load it manually by typing modprobe ide-floppy as root. I don't know exactly what you need to do, I have a zip I have never been able to use, I was just reacting to the placement of the 'modprobe' line in rc.local :)

I am interpreting that you haven't been able to install Midnight Commander (mc). This is on a Power Pack download: # urpmq --sources mc file://mnt/hd//media/main4/mc-4.6.0-13mdk.i586.rpm I'm not sure the download edition includes mc. Can you check your sources with that command? If it is there, as root, urpmi mc ought to install it and it can be opened as any user with mc If it is not in your sources, you could get it on the mirrors containing 10.1 official under: pub/linux/mandrakelinux/official/10.1/i586/media/main/ Or, you might want to add a 10.1 main urpmi source by following the directions at Easy Urpmi. Or, I might not have interpreted correctly :P

You can install the mm kernel from the same directory that had the mm source.

This does not fix my nvidia.ko missing problem. any ideas? tia Kristi <{POST_SNAPBACK}> Would you confirm for me that, in line 43 pos 194 of file /usr/src/linux/include/linux/rhconfig.h, you removed one && where there were two in a row, saved the file, and tried to build the nVidia module with 2.6.10 running? :) Also, I have not heard of, nor have I used the step, "run make prepare-all against the source." How do you come to believe this step is necessary and could it be creating the problem? Just to throw out some ideas. Once I have built against a kernel-source, there have been some occasions where it seemed I needed to replace the sources with a fresh copy before I could successfully build again. Once, the module would not build on one attempt but, after I did modprobe -r nvidia to unload the module, it built. I just got my first nVidia card, so this is all pretty new to me. Have you looked around at the nvnews Linux forum?

As adamw and I have said, there is a problem with the kernel-source that comes with beta 3. It is a typo, which can be fixed. The link I gave describes how. It will not work unless you edit a file in the source. It does not matter by which method you install the source; it will have that typo. The kernel-multimedia-source rpm is in the contrib section of cooker, along with the multimedia kernel. Look on your mirror in mandrakelinux/devel/cooker/cooker/media/contrib/

Do you have the -devel package(s) for gnomemm installed? This is on 10.2 beta3, for example: # urpmq gnomemm The following packages contain gnomemm: libgnomemm-1.2_9 libgnomemm2.6_1 libgnomemm2.6_1-devel

There is a typo in the kernel-source-2.6.10 that comes with 10.2 beta 3 and stops the nvidia driver build. There is some info about what to do (worked for me) in this post -> a post.