Kernel update today - Suse

This is a discussion on Kernel update today - Suse ; File './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm' not found on medium 'http://download.opensuse.org/update/11.0/' Can't provide file './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm' from repository 'openSUSE-11.0-Updates' What's up with this? -- Claude Hopper ? ? •...

+ Reply to Thread
Results 1 to 19 of 19

Thread: Kernel update today

  1. Kernel update today

    File './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm'
    not found on medium 'http://download.opensuse.org/update/11.0/' Can't
    provide file
    './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm' from
    repository 'openSUSE-11.0-Updates'


    What's up with this?



    --
    Claude Hopper

    ? ? •

  2. Re: Kernel update today

    On Tue, 28 Oct 2008 12:43:28 -0400, Claude Hopper wrote:

    > File './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm'
    > not found on medium 'http://download.opensuse.org/update/11.0/' Can't
    > provide file
    > './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm' from
    > repository 'openSUSE-11.0-Updates'
    >
    >
    > What's up with this?


    For those of us using dual booting, do not forget to edit your
    /boot/grub/menu.lst file to reflect the change if it doesn't happen
    by itself. (mine doesn't do it because the file is on the partition where
    I am still experimenting with Ubuntu.)

    Godzilla

  3. Re: Kernel update today

    Godzilla wrote:
    > For those of us using dual booting, do not forget to edit your
    > /boot/grub/menu.lst file to reflect the change if it doesn't happen
    > by itself. (mine doesn't do it because the file is on the partition where
    > I am still experimenting with Ubuntu.)


    I have placed /boot on a seperate partition and that is read only. Also
    no interactive autoupdates for me.

    This means that I won't get any kernel updates and when I decide to do
    them, I will be getting several errors, until I realize several hours
    later that that partition is read-only.

    Stupid Linux and its security.

    houghi
    --
    This was written under the influence of the following:
    | Artist : Boudewijn de Groot
    | Song : De zwemmer
    | Album : Wonderkind aan het strand (CD 3: Branding)

  4. Re: Kernel update today

    Claude Hopper wrote in
    news:NoudnVfHJ5103ZrUnZ2dnUVZ_ovinZ2d@giganews.com :

    > File './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm'
    > not found on medium 'http://download.opensuse.org/update/11.0/' Can't
    > provide file
    > './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm' from
    > repository 'openSUSE-11.0-Updates'
    >
    >
    > What's up with this?
    >
    >
    >


    I have links like /boot/vmliuz -> /boot/vmlinuz-version-stuff and menu
    options that point both to the link and a specific version. Then if update
    doesn't do it I just repoint the link.

  5. Re: Kernel update today

    Claude Hopper wrote:
    > File './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm'
    > not found on medium 'http://download.opensuse.org/update/11.0/' Can't
    > provide file
    > './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm' from
    > repository 'openSUSE-11.0-Updates'
    >
    >
    > What's up with this?
    >
    >
    >



    --
    Claude Hopper

    ? ? •


    Apparently the update worked. I have vmlinuz-2.6.25.18-0.2-pae in /boot.
    I don't know why the error message.

  6. Re: Kernel update today

    Claude Hopper wrote:
    > File './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm'
    > not found on medium 'http://download.opensuse.org/update/11.0/' Can't
    > provide file
    > './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm' from
    > repository 'openSUSE-11.0-Updates'
    >
    >
    > What's up with this?
    >
    >
    >

    Not sure if the messages were the same but I got some error messages. I
    just looked in /boot and discovered a /boot/boot directory followed by a
    /boot/boot/boot; followed by a /boot/boot/boot/boot/... - appx 75 layers
    down.

    All look to be copies of the /boot directory.

    Can I just delete all the boot directories beneath /boot?

  7. Re: Kernel update today

    Pete Ricksecker wrote:
    > Not sure if the messages were the same but I got some error messages. I
    > just looked in /boot and discovered a /boot/boot directory followed by a
    > /boot/boot/boot; followed by a /boot/boot/boot/boot/... - appx 75 layers
    > down.
    >
    > All look to be copies of the /boot directory.
    >
    > Can I just delete all the boot directories beneath /boot?


    Just checked my laptop and it did the same thing.

  8. /boot/boot ... (was: Kernel update today)

    Pete Ricksecker wrote:

    > Not sure if the messages were the same but I got some error messages. I
    > just looked in /boot and discovered a /boot/boot directory followed by a
    > /boot/boot/boot; followed by a /boot/boot/boot/boot/... - appx 75 layers
    > down.


    It's supposed to be a symbolic link:

    $ ls -l /boot/boot
    lrwxrwxrwx 1 root root 1 dec 2 2007 /boot/boot -> .

    --
    Huibert
    "Hey! HEY! Curious cat, here!" -- Krosp I (GG)

  9. Re: /boot/boot ...

    Huibert Bol wrote:
    > Pete Ricksecker wrote:
    >
    >> Not sure if the messages were the same but I got some error messages. I
    >> just looked in /boot and discovered a /boot/boot directory followed by a
    >> /boot/boot/boot; followed by a /boot/boot/boot/boot/... - appx 75 layers
    >> down.

    >
    > It's supposed to be a symbolic link:
    >
    > $ ls -l /boot/boot
    > lrwxrwxrwx 1 root root 1 dec 2 2007 /boot/boot -> .
    >

    You are correct, Sir.

    But are they supposed to 'drill down' 75 + layers?

  10. Re: /boot/boot ...

    Pete Ricksecker wrote:

    > Huibert Bol wrote:
    >> Pete Ricksecker wrote:
    >>
    >>> Not sure if the messages were the same but I got some error messages. I
    >>> just looked in /boot and discovered a /boot/boot directory followed by a
    >>> /boot/boot/boot; followed by a /boot/boot/boot/boot/... - appx 75 layers
    >>> down.

    >>
    >> It's supposed to be a symbolic link:
    >>
    >> $ ls -l /boot/boot
    >> lrwxrwxrwx 1 root root 1 dec 2 2007 /boot/boot -> .
    >>

    > You are correct, Sir.
    >
    > But are they supposed to 'drill down' 75 + layers?


    You're just chasing you're own tail :-)

    --
    Huibert
    "Hey! HEY! Curious cat, here!" -- Krosp I (GG)

  11. Re: /boot/boot ...

    Huibert Bol wrote:

    >
    > You're just chasing you're own tail :-)
    >


    I didn't do this. It happened when the kernel update was applied.

    Original question was what should I do with this mess? Can I just
    delete /boot/boot ?????

  12. Re: /boot/boot ...

    Pete Ricksecker wrote:
    > Huibert Bol wrote:
    >
    >> You're just chasing you're own tail :-)
    >>

    >
    > I didn't do this. It happened when the kernel update was applied.
    >
    > Original question was what should I do with this mess? Can I just
    > delete /boot/boot ?????


    It's always been there.


    --
    Claude Hopper

    ? ? •

  13. Re: Kernel update today

    Claude Hopper wrote:

    > File './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm'
    > not found on medium 'http://download.opensuse.org/update/11.0/' Can't
    > provide file
    > './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm' from
    > repository 'openSUSE-11.0-Updates'


    One of the many usual (!) things I mean when I say the openSUSE update
    mechanism is really not working good and not inspiring confidence.

    Just wait some days (up to two weeks), they will fix it in the
    repository.

    T.M.

  14. Re: Kernel update today

    On Oct 29, 4:58*am, Torsten Mueller wrote:
    > Claude Hopper wrote:
    > > File './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm'
    > > not found on medium 'http://download.opensuse.org/update/11.0/'Can't
    > > provide file
    > > './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm' from
    > > repository 'openSUSE-11.0-Updates'

    >
    > One of the many usual (!) things I mean when I say the openSUSE update
    > mechanism is really not working good and not inspiring confidence.
    >
    > Just wait some days (up to two weeks), they will fix it in the
    > repository.
    >
    > T.M.


    The update works fine. It might be that you've made a few other
    changes that have triggered off a chain reaction. I also accepted the
    kernel update but the consequence was that my laptop could not power
    off unless I pressed down the power button for some 3-4 seconds.
    Before the update I had had problems with keyboard and touchpad
    recognition so I had modified the kernel line in menu.lst to include
    the options "irqpoll" and "acpi=off". Everything worked fine with
    either acpi=off or acpi=force until the update. Thereafter, acpi=off
    meant I couldn't power off, acpi=force allowed the laptop to power off
    naturally but lost the touchpad while acpi=on allowed everything to
    work well.
    It might be worth reviewing any recent manual changes you've made
    (manual contrasted with changes by yast)

    I have /boot/boot->.
    and that is how it has always been.

  15. Re: Kernel update today

    kiwanuka wrote:

    >>> File './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm'
    >>> not found on medium 'http://download.opensuse.org/update/11.0/'Can't
    >>> provide file
    >>> './rpm/i586/kernel-pae-2.6.25.16_2.6.25.18-0.1_0.2.i586.delta.rpm' from
    >>> repository 'openSUSE-11.0-Updates'

    >>
    >> One of the many usual (!) things I mean when I say the openSUSE update
    >> mechanism is really not working good and not inspiring confidence.
    >>
    >> Just wait some days (up to two weeks), they will fix it in the
    >> repository.

    >
    > The update works fine. It might be that you've made a few other
    > changes that have triggered off a chain reaction.


    I didn't change *anything* on my kernel or boot configuration. But
    this is indeed a fact that doesn't matter at all.

    The above error message (I wonder that nobody did really see this, so
    I explain it now) comes from the openSUSE *updater* - the updater
    wants to update a file from a repository but the file is "not found on
    medium xxxx" and the repository "can't provide file xxxx".

    This is a typical and usual error message while updating something, I
    see it oftenly - I'm just not sure if it comes from the repository
    itself or from the way the updater corresponds with the repository.
    Perhaps the updater gets just a timeout while everything would work
    fine if the timeout would just be a second longer. I don't know the
    concrete reason. But these problems a real and definitly not selfmade.

    T.M.

  16. Re: Kernel update today

    Torsten Mueller wrote:

    > The above error message (I wonder that nobody did really see this, so
    > I explain it now) comes from the openSUSE updater - the updater
    > wants to update a file from a repository but the file is "not found on
    > medium xxxx" and the repository "can't provide file xxxx".


    Something has changed - I saw the same messages yesterday but two other
    machines I did this morning showed no messages other than the "reboot ASAP"
    due to the kernel update.

    --
    Will Honea
    ** Posted from http://www.teranews.com **

  17. Re: Kernel update today

    Will Honea@teranews.com wrote:
    > Something has changed - I saw the same messages yesterday but two other
    > machines I did this morning showed no messages other than the "reboot ASAP"
    > due to the kernel update.


    For that reason alone I do not do interactive updates automaticaly.

    houghi
    --
    Remind me to write an article on the compulsive reading of news. The
    theme will be that most neuroses can be traced to the unhealthy habit
    of wallowing in the troubles of five billion strangers. -- Heinlein

  18. Re: Kernel update today

    On 2008-10-29, houghi wrote:
    > Will Honea@teranews.com wrote:
    >> Something has changed - I saw the same messages yesterday but two other
    >> machines I did this morning showed no messages other than the "reboot ASAP"
    >> due to the kernel update.

    >
    > For that reason alone I do not do interactive updates automaticaly.
    >


    I'm always waiting for a while to see if threads like this one arise.
    I had decided to update the kernel and I already bought a can of air for
    that.

    Now I guess I'll wait another day or two to see what's cooking...

    Oh, the air?
    I always blow the dust with canned air and vacuum my box at kernel updates.
    This is my new procedure with my current super computer that I built

    --
    http://waxborg.servepics.com
    "There will come a time when every evil
    That we know will be an evil...
    That we can rise above" - Frank Zappa

  19. Re: Kernel update today

    Torsten Mueller wrote:

    > The above error message (I wonder that nobody did really see this, so
    > I explain it now) comes from the openSUSE *updater* - the updater
    > wants to update a file from a repository but the file is "not found on
    > medium xxxx" and the repository "can't provide file xxxx".
    >
    > This is a typical and usual error message while updating something, I
    > see it oftenly - I'm just not sure if it comes from the repository
    > itself or from the way the updater corresponds with the repository.
    > Perhaps the updater gets just a timeout while everything would work
    > fine if the timeout would just be a second longer. I don't know the
    > concrete reason. But these problems a real and definitly not selfmade.


    I made best experiences with using one fixed mirror instead of the pool
    provided by download.opensuse.org. Letting the central server choose
    too often results in time out errors for me. Some of these mirrors are
    probably not reliable enough or have a band width problem.

    G√ľnther

+ Reply to Thread