Jump to content

Greg2

Global Moderator
  • Posts

    2482
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by Greg2

  1. You can't learn it all from any one book or resource. I've been using Linux as my primary OS for over 7 years now, and used it occasionally for 2 years before that... I still learn something new every day I use it. :)

     

    I would suggest for the most complete on-line resource for you to use would be: TLDP

     

    For a book you can purchase or read on-line there's 'Linux in a nutshell'. Here's a link for the cli commands from the book and it contains a link to purchase it or read it on-line: Alphabetical Directory of Linux Commands

     

    Other 'very' good resources are the: wiki.mandrivausers.org and the: wiki.mandriva.com/Docs

     

    And don't forget, we're also here to help! :)

  2. You have to remove that rpm5-manbo-setup package in order to fix this. I'm not sure how or why it was installed in the first place... that is the bug.

     

    OK, I'm going to have you try something else. Copy this

    # This macro will disable the transaction lock on /var/lib/rpm/__db.*.
    # This lock is of no use to us and will also result in errors when trying to
    # install src.rpms as regular user.
    %_rpmlock_path %{_dbpath}/__db.000

    into a text editor and save it as 90rpm5.org-manbo.macros file in your ~/home. Then as root do

    cp 90rpm5.org-manbo.macros /etc/rpm/macros.d/

    and overwrite the other file with it. Now try to remove the package with (as root)

    urpme rpm5-manbo-setup

    please let us know if you can remove that package.

     

    My disclaimer: I've never installed that rpm5-manbo-setup package, nor have I ever tried to remove it this way, so I'm not responsible for any accidents here. :)

  3. [root@localhost roger]# rpm -qa | grep -i rpm5-manbo-setup

    rpm5-manbo-setup-1-1mnb2

     

    ......snip......

     

    I still trying to find the problem on internet

    This is explained in the bug report # 46518 that I've linked in my other post for you. It is a workaround for a bug that has not been fixed yet.

     

    I will try to make it easier for you to do. Copy this file

    %_topdir				%(echo $HOME)/rpm
    %_tmppath			   %(echo $HOME)/rpm/tmp
    
    # If you want your packages to be GPG signed automatically, add these three lines
    # replacing 'Mandrivalinux' with your GPG name. You may also use rpm --resign
    # to sign the packages later.
    # %_signature			 gpg
    # %_gpg_name			  Mandrivalinux
    # %_gpg_path			  ~/.gnupg
    
    # Add your name and e-mail into the %packager field below. You may also want to
    # also replace vendor with yourself.
    %packager			   John Doe <foo@mail.invalid>
    %distribution		   Mandriva Linux
    %vendor				 Mandriva
    
    # If you want your packages to have your own distsuffix instead of mdv, add it
    # here like this
    # %distsuffix			 foo
    
    %_rpmlock_path		  %{_dbpath}/__db.000

    in a text editor like kwrite, and save the file as .rpmmacros in your ~/home directory. Please note the '.' in .rpmmacros, it is needed and will make the file hidden in your ~/home directory. After you have done that, in a terminal (as root) run

    urpme rpm5-manbo-setup

    then delete the .rpmmacros file with (as user)

    rm ~/.rpmmacros

    now you should be able to install and remove software as normal.

  4. An example would look something like this

    %{_kde3_libdir}/kde3/*

    You may also need to edit the build, and you do need to edit the configure sections. I've had some luck with

    %build
    export KDEDIR=%{_prefix}
    %configure_kde3

    or

    %build
    export QTLIB=%qt3dir
    %configure_kde3

    and it's not recommended, but I've also had to edit the /etc/rpm/macros.d/kde3.macros file to complete a build. However save an original kde3.macros file to replace it when you are finished, or it will screw up other builds.

     

    Please note that not all kde3 things will build with this current kde3/kde4 setup properly, simply because of the current location of kde3. As dexter already knows, I've not been able to successfully build krusader1.9 to install to /opt/kde3, but I have successfully built it to install to /usr and /usr/lib/kde3 and it works ok for me.

  5. This is the relevant section of the Mandriva 2009 2.6.27-desktop kernel config file

    # Please see Documentation/ide/ide.txt for help/info on IDE drives
    #
    CONFIG_IDE_TIMINGS=y
    CONFIG_IDE_ATAPI=y
    # CONFIG_BLK_DEV_IDE_SATA is not set
    CONFIG_BLK_DEV_IDEDISK=m
    CONFIG_IDEDISK_MULTI_MODE=y
    CONFIG_BLK_DEV_IDECS=m
    CONFIG_BLK_DEV_DELKIN=m
    CONFIG_BLK_DEV_IDECD=m
    CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
    CONFIG_BLK_DEV_IDETAPE=m
    CONFIG_BLK_DEV_IDEFLOPPY=m
    CONFIG_BLK_DEV_IDESCSI=m
    CONFIG_BLK_DEV_IDEACPI=y
    CONFIG_IDE_TASK_IOCTL=y
    CONFIG_IDE_PROC_FS=y

    as you can see it has been enabled here:

    CONFIG_IDE_ATAPI=y

    but, this has not been enabled

    # CONFIG_BLK_DEV_IDE_SATA is not set

    and Mandriva is using

    CONFIG_BLK_DEV_IDEFLOPPY=m

    m = module in that line.

     

    So if I haven't lost you yet, you could try loading that module (if it's not already loaded) with (as root)

    modprobe ide-floppy

    and see if that works.

     

    If that doesn't work for you, then you would 'probably' need to recompile a custom kernel with IDE_SATA enabled

    CONFIG_BLK_DEV_IDE_SATA=y

    I'm guessing at this because of your Marvell controller, but I'm not positive about it. :unsure:

  6. Don't worry about the code box, I forgot that you must have made 10 (maybe 5?) posts before you can attach something... It's for spam control.

     

    I've done a bit of research for you, and have found that you must determine if your drive is an ATA/IDE or an ATAPI. You can use this page to determine that: zipjaz/atapi

     

    Then you can use this documentation to help set it up: ZIP-Drive

     

    I realize that this documentation is old, but it is all that I can find that my be of help to you. Without having one of these drives to work with, I simply can't offer much more help, I'm sorry. :)

     

    I can only assume that the Ubuntu kernel has some bit of support enabled that the Mandriva kernel does not.

     

    Would you please file a bug report about this? Here: https://qa.mandriva.com/

     

    Because your controller:

    02:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II Controller (rev b1) (prog-if 8f [Master SecP SecO PriP PriO])

    is very similar to another Marvell controller that they are having problems with. Please read: bug #39842

  7. I've never had one of your zip drives, so I'm just 'trying' to sort this out for the first time myself. :)

     

    I would like you to run this (as user)

    lspci -vv > ~/lspci.txt

    that will create a lspci.txt file in your ~/home directory. Please attach that to a post as a txt file for us to look at. It may be large, that is why I ask that you attach it.

×
×
  • Create New...