Jump to content

rolf

Members
  • Posts

    129
  • Joined

  • Last visited

Everything posted by rolf

  1. I'll report there is plenty of communication going on between Mandriva and Club members. Adam Williamson has been hired to relay concerns to company personnel and there have been quite a few positive results. Not everyone has smooth sailing but just about everyone who reports a lack of response gets attention and most are getting resolutions.
  2. A couple of places to find explanations of kernel arguments: /usr/src/linux-{version}/Documentation/kernel-parameters.txt /usr/share/doc/HOWTO/HTML/en/BootPrompt/BootPrompt-HOWTO.html The Howto is in howto-html-en in my install.
  3. First of all, if you mix cooker and production packages, you are creating a situation that is 'unsupported'. It is unsupported because it it likely to create problems. The advice has always been to either run only cooker (not for production) or run a pure stable distribution. Many people will dual boot with both types of installation. [rolf@localhost ~]$ urpmq -i gcc3.3 Name : gcc3.3 Version : 3.3.4 Release : 4mdk Group : Development/C Size : 10683210 Architecture: i586 Source RPM : gcc3.3-3.3.4-4mdk.src.rpm Build Host: n2.mandrakesoft.com Packager : Gwenole Beauchesne <gbeauchesne@mandrakesoft.com> URL : http://gcc.gnu.org/ Summary : GNU Compiler Collection Description : A compiler aimed at integrating all the optimizations and features necessary for a high-performance and stable development environment. This package is required for all other GCC compilers, namely C++, Fortran 77, Objective C and Java. If you have multiple versions of GCC installed on your system, it is preferred to type "gcc-$(gcc3.3-version)" (without double quotes) in order to use the GNU C compiler version 3.3.4. 3.3.4 is the version of gcc3.3 that comes with 2005. It is a matter of terminology used by urpmi. Also, you will notice another method for specifying your compiler. As to why urpmi says the package is already installed, I don't know. Sometimes the error will be a clue that the command is faulty. If you use urpmi to install a downloaded package, you must give the full path to the package. That is, if you cd to the directory that contains the downloaded package, named gcc-3.4.3-7mdk.i586.rpm, the command would be: urpmi gcc-3.4.3-7mdk.i586.rpm If the rpm is not in your current working directory, you could give the path: urpmi /path/to/gcc-3.4.3-7mdk.i586.rpm You should already have urpmi sources for main set up at installation, unless you removed them. If you have sources for cooker, that will cause problems. Remove them or disable them in Software Media Manager. Now, unless you have installed cooker packages whose dependencies prevent the simple use of urpmi to install a package from 2005, the following information displays what command/terminology urpmi will need to get gcc installed: $ urpmq -i gcc Name : gcc Version : 3.4.3 Release : 7mdk Group : Development/C Size : 9451626 Architecture: i586 Source RPM : gcc-3.4.3-7mdk.src.rpm Build Host: n2.mandrakesoft.com Packager : Gwenole Beauchesne <gbeauchesne@mandrakesoft.com> URL : http://gcc.gnu.org/ Summary : GNU Compiler Collection [..] This tells me gcc means gcc-3.4.3 to urpmi in 2005 and it ought to install if you simply: urpmi gcc as root. You will probably also need the corresponding -c++ and -cpp packages of that version for certain types of compiling to work. So, what I suggest is to either give the full path to the rpms as the argument to urpmi or use the name for the package in your sources that urpmi will understand. What you have done with your urpmi sources and installation of cooker packages might make this not work. Paste any commands used along with complete error messages, if there is a problem.
  4. There's no need to build a kernel to build a driver. Just make sure the kernel you are running and the kernel-source have the same version. $ rpm -qa | grep kernel nvidia-kernel-2.6.11-6mdk-7174-1mdk kernel-2.6.11.6mdk-1-1mdk <=== kernel-source-2.6-2.6.11-6mdk <===
  5. [rolf@localhost ~]$ urpmq kernel-source no package named kernel-source The following packages contain kernel-source: kernel-source-2.6 kernel-source-stripped-2.6 openafs-kernel-source [rolf@localhost ~]$ uname -r 2.6.11-6mdk The first command gives me a list of known packages (what is in configured urpmi sources) named kernel source. The second command tells me the kernel that is running. The kernel-source package has all the source code needed to build the kernel. The package, kernel-source-stripped, is much smaller but is supposed to contain enough code to build drivers. However, there have been some problems reported with the full source needed to build certain drivers, so I would recommend installing the full source. In this case, since the version of my running kernel is 2.6, I would install it, as root, with urpmi kernel-source-2.6 You could also look in Software Manager for kernel-source packages. If there has been an update to the kernel and kernel-source packages, you will either have to update your kernel or make sure you give urpmi the full version of the kernel-source rpm that matches your running kernel, as urpmi will upgrade to the latest known kernel-source automatically.
  6. I'm inclined to think of problems people have getting the CD reader to boot from a burned CD-R or CD-RW disk, so I will just mention what I have heard makes a difference. Sometimes, a CD-ROM drive can't read correctly CD-RW media. Try CD-R media. Make sure the disk is finalized. Burn the disk at a slower speed. Try a different CD media (theoretically, higher-quality). The reader laser might need to be cleaned or the drive is faililng. If Plug-n-Play OS is selected in the BIOS, unselect it. If it is unselected, try selecting it. Maybe it is none of this but that is all I can think of.
  7. I don't know if your Hardware topic covers this but I am assuming you are using a floppy because your machine won't boot from CD? Are the CD's burned properly from isos that have had the md5sum checked? One level of checking the CD's is to read the contents in a file explorer or list them from a command line. Does CD2 contain this: Boot/ media/ And, under Boot/, do you see: boot.cat cdrom-changedisk.img ?
  8. Two thoughts: Boot CD2 and this gives you alternate kernels, including 2.4, I believe, which might, also result in that kernel being installed as the default kernel. I am not sure as I have not done this, only read about it. During package selection, choose to select your own packages and install the 2.4 kernel, which will give you a choice to boot that kernel in the bootloader menu.
  9. My experience is that gcc and related packages can be installed in parallel. For example: [rolf@localhost ~]$ rpm -qa|grep gcc gcc-c++-3.4.3-7mdk gcc2.96-cpp-2.96-0.83mdk gcc-cpp-3.4.3-7mdk gcc-3.4.3-7mdk gcc2.96-c++-2.96-0.83mdk gcc2.96-2.96-0.83mdk libgcc1-3.4.3-7mdk [rolf@localhost ~]$ urpmq -y gcc cross-ppc-gcc cross-ppc-gcc-cpp cross-ppc-libgcc1 cross-ppc64-gcc cross-ppc64-gcc-cpp cross-ppc64-libgcc1 gcc gcc-c++ gcc-colorgcc gcc-cpp gcc-doc gcc-doc-pdf gcc-g77 gcc-gnat gcc-java gcc-objc gcc2.96 gcc2.96-c++ gcc2.96-cpp gcc3.3 gcc3.3-c++ gcc3.3-cpp gcc3.3-doc gcc3.3-doc-pdf gcc4.0 gcc4.0-c++ gcc4.0-cpp gcc4.0-doc gcc4.0-doc-pdf gccxml libgcc1 Also, for Official sources, there are many versions of gcc and related packages available. Install the version(s) of gcc and related packages you need (rpm -i) and use update-alternatives to configure the default gcc to be used or use build switches and/or Makefile edits to select the version to use. # update-alternatives --config gcc There are 2 programs which provide `gcc'. Selection Command ----------------------------------------------- *+ 1 /usr/bin/gcc-3.4.3 2 /usr/bin/gcc-2.96 Enter to keep the default[*], or type selection number: man update-alternatives
  10. rolf

    urpmi

    If you look on the mirrors, you will see the net-snmp-tools rpm is there, under 10.1, such as: ftp://ftp.sunet.se/pub/Linux/distribution...2-6mdk.i586.rpm As DragonMage said, you could add an ftp 'main' source for 10.1 at EasyUrpmi and have this package available that way. However, I would think it is on your CD's and urpmi is not configured properly for you. To check that, I asked for the output of urpmq --list-media If you look on the CD's, under the media* directories, do you not find this package?
  11. rolf

    urpmi

    OK, I can see the possibilities, now. My experience is limited to my single-user desktop Thanks for the insight!
  12. rolf

    urpmi

    The first part of the advice I agree with. I have never understood, however, why use (sometimes slow or unreliable) bandwidth to get packages that are right at your machine?
  13. rolf

    urpmi

    This is on 10.2, where net-snmp-utils shows to be on CD4 and ethereal has a security update. What do the following commands show on your machine? [rolf@localhost ~]$ urpmq net-snmp-utils net-snmp-utils [rolf@localhost ~]$ urpmq net-snmp-utils --sources /mnt/hd//media/main4/net-snmp-utils-5.2.1-3mdk.i586.rpm [root@localhost rolf]# urpmq --sources ethereal /mnt/hd//media/main4/ethereal-0.10.10-1mdk.i586.rpm ftp://ftp.ciril.fr/pub/linux/mandrakelinux/official/updates/LE2005/main_updates/./ ethereal-0.10.11-0.1.102mdk.i586.rpm [rolf@localhost ~]$ urpmq --list-media simonzone Drivers and Plugins Special Club CD41 Drivers and Plugins Special Club CD42 Drivers and Plugins Special Club CD43 Drivers and Plugins Special Club CD44 Drivers and Plugins Special Club CD45 Installation CD11 Installation CD21 Installation CD31 Silver Club Extra CD51 Silver Club Extra CD61 Silver Club Extra CD62 plf-free plf-nonfree updates contrib club.commercial_x86-32_2005LE
  14. See the urpmf command I gave and read the man page (man urpmf). That shows ac-wrapper.pl is in autoconf2.5. Ordinarily, urpmi would know that one package provides what the other needs and install both. It might be the package was not constructed with the proper information or there is a problem with your urpmi database. To try to install both with one command, as root: urpmi autoconf2.1 autoconf2.5 See man urpmi Another way: rpm -Uvh /path/to/autoconf2.1-2.13-21mdk.noarch.rpm /path/to/autoconf2.5-2.59-6mdk.noarch.rpm See man rpm
  15. [rolf@localhost ~]$ urpmf /usr/share/autotools/ac-wrapper.pl autoconf2.5:/usr/share/autotools/ac-wrapper.pl [rolf@localhost ~]$ rpm -qa |grep autoconf autoconf2.1-2.13-21mdk autoconf2.5-2.59-6mdk [rolf@localhost ~]$ su Password: [root@localhost rolf]# rpm -e --test autoconf2.5 error: Failed dependencies: autoconf2.5 is needed by (installed) kdevelop-3.1.2-10mdk /usr/share/autotools/ac-wrapper.pl is needed by (installed) autoconf2.1-2.13-21mdk Looks like 2.1 requires 2.5. Do you try to install with urpmi autoconf2.1 as root? If that doesn't work trying installing both with the same command, or install 2.5 first....
  16. When you change the slave to master and master to slave, the device names for the partitions in /etc/fstab will change. hda becomes hdb and vice versa, for all instances. Also, in /boot/grub/menu.lst, the device names will have to be changed. Once this has been done and the drives switched, it will be unbootable. You could boot CD1 to command line in rescue mode and install grub from the grub shell. See info grub It will look like this, if your / partition is now hda1: # grub grub> root (hd0,0) grub> setup (hd0) grub> quit # This tells grub where your /boot directory is and to install the bootloader to the MBR.
  17. rolf

    Urpmi

    Don't give up on learning about the commandline urpmi family of tools. After awhile, I find it quicker, easier, and more flexible to use the commands than the gui frontend, Software Manager, for most tasks. See man urpmi and the manual pages of the related commands, listed at the bottom of each man page. There are online resources, such as http://qa.mandrakesoft.com/twiki/bin/view/.../UrpmiResources
  18. rolf

    view hard disc

    The Mandriva install usually sets up mount points for Windows partitions under the /mnt directory and makes entries for them in /etc/fstab such that they are mounted/viewable at boot, without a need to do anything further. If you navigate in a file browser, like konqueror, to the /mnt/directory, do you see any win_*/ directories? That would be typical of a mount point for a Windows partition. If you have that, look in there. Alternatively, what does grep mnt /etc/fstab when issued as a command in console show?
  19. make is usually not the first step of building a program from source. When you unpack the source tarball, there will almost always be readme or install text files describing the process. Also, at the website of the program, there will often be building/installation documentation. Look for this information. Usually, ./configure is the first step.
  20. The typical kernel has gotten too big to fit on a floppy. However, if your bootloader is lilo, you can make an iso, burn it to CD, and use that CD to boot your current default kernel. The command to make the iso is mkrescue --iso See man mkrescue
  21. One more way to run updates is by issuing the command MandrakeUpdate in a console with an active internet connection. If you are root, it will start the updates dialog. If not, you will be prompted for the root password. If no update source is configured, you will be asked to choose from a list of mirrors. Otherwise, you will need to confirm to get the latest list of updates from the mirror. Then, you will be given a list of updates from which to choose or be told there are no new updates. On occasion, a problem will arise due to your updates mirror not accepting connections or going offline. In such a case, you might want to start media manager to remove the updates source, then run MandrakeUpdate to try another one. Over time, I have found learning about and using the urpmi family of tools from the command line to be the quickest, easiest, most flexible way of accomplishing my software management needs. See the man pages and online resources, such as http://qa.mandrakesoft.com/twiki/bin/view/.../UrpmiResources
  22. Well, you've specified the kernel and initrd.img to the bootloader on the MBR, so it loads that. What you need to load another bootloader is called 'chainload' in GRUB, thus my previous advice. Looking at man lilo.conf, I would suggest to make an entry like the following (then run lilo): other=/dev/hda6 label=10.2_lilo
  23. I have had some glitches with diskdrake at install, which might be hardware-related. In my case, formatting reiserfs partitions I created at install did not 'take' (there was no crash of the computer). After rebooting, I could format, sometimes from another install. When formatting with mkreiserfs on the command line, the terminal messages instruct to reboot after fdisk. The suggestion this experience prompts is to do the partitioning in one step, to where 'Partition table is written to disk', and reboot, formatting after the reboot. If possible, try booting CD1 to a command line in rescue mode and perform the partitioning/formatting from there.
×
×
  • Create New...