Re: yum broken

Spencer Kellis wrote:

I've been trying to get memtest86 up and running and having some problems.

I downloaded, ran make, created /memtest, copied memtest.bin to /memtest. (boot drive is sda1)

in /etc/grub.conf, (from a google find) I entered the following:

title memtest86
root (hd0,0)
kernel (hd0,0)/memtest/memtest.bin

Depending on the path I put into the third line, I either get "File not found" errors or on enter, I get a black (blank) screen for a second or so, and the grub menu returns.

Tony - thanks for the suggestion, and I'll try that as soon as I've got the memtest86 figured out. Do you know where the db is located in the filesystem to delete (or how to find it)?

Spencer

I installed memtest in /boot, just the file "memtest86+-1.26",

then I added the following 3 lines to grub.conf.

title Memtest
        root (hd0,0)
        kernel /memtest86+-1.26


It works for me (TM).

Regards,

John

On 10/5/05, *Tony Nelson* <tonynelson@xxxxxxxxxxxxxxxxx <mailto:tonynelson@xxxxxxxxxxxxxxxxx>> wrote:

    At 4:49 PM +0800 10/5/05, Edward Dekkers wrote:
     >Spencer Kellis wrote:
     >> I would have thought bad memory would be manifest in many more
    ways than
     >> simply yum not working.  My system is otherwise stable, and has
    been up
     >> and operating for a week currently without any other issues.  I
     >> appreciate the idea though, and if you still consider bad memory an
     >> option I'd be interested to hear it (and how & why).
     >>
     >> If there are any other ideas out there, even pointers to what to
    look
     >> through for possible problems on my own, I'd appreciate it.
     >>
     >> Thanks,
     >> Spencer
     >
     >The reason he would have suggested it is because it's probably the #1
     >cause of segmentation faults and signal 11 faults on Linux, together
     >with bad hardware. This isn't Windows and you aren't in Kansas any
    more.
     >
     >Linux is super stable and if it crashes, it is more than likely not
     >actually Linux's fault.
     >
     >Trust the reply to your post - run a memtest86 overnight on full
    testing
     >suite, don't question a perfectly reasonable response. I think the
     >person who replied has been around Linux longer than you from what
    I can
     >see.
     >
     >If the memory tests OK, fine, we'll look at something else, but you
     >really need to eliminate it 100% sure before we go on.

    My own guess is that there is something badly wrong with RPM's database,
    and that --rebuilddb might need some help, such as rm'ing the existing
    database first.  Hopefully someone who knows more about RPM will
    chime in.
    ____________________________________________________________________
    TonyN.:'                       <mailto:tonynelson@xxxxxxxxxxxxxxxxx
    <mailto:tonynelson@xxxxxxxxxxxxxxxxx>>
          '                              <http://www.georgeanelson.com/>

    --
    fedora-list mailing list
    fedora-list@xxxxxxxxxx <mailto:fedora-list@xxxxxxxxxx>
    To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
    <https://www.redhat.com/mailman/listinfo/fedora-list>