Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb - Mandriva

This is a discussion on Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb - Mandriva ; Just did that 2009.0 update, but when booting and using the latest stanza at the end of the GRUB menu to use the new kernel, after the Login screen (after which it should go into KDE3) a small window pops ...

+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 20 of 39

Thread: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

  1. Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    Just did that 2009.0 update, but when booting and using the latest
    stanza at the end of the GRUB menu to use the new kernel, after the
    Login screen (after which it should go into KDE3) a small window pops
    up top left with the message:

    "Could not start kstartupconfig. Check your installation."

    and at bottom left was an unusual "Okay" button, which simply
    returns to the Login window.

    Anyone else had this?

    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)


  2. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    Maurice Batey wrote:
    > Just did that 2009.0 update, but when booting and using the latest
    > stanza at the end of the GRUB menu to use the new kernel, after the
    > Login screen (after which it should go into KDE3) a small window pops
    > up top left with the message:
    >
    > "Could not start kstartupconfig. Check your installation."
    >
    > and at bottom left was an unusual "Okay" button, which simply
    > returns to the Login window.
    >
    > Anyone else had this?
    >


    Well, the first thing to check regarding that error is that the permissions
    on your home folder (profile) are correct.



    Thai

  3. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    On Wed, 05 Nov 2008 19:33:43 +0000, Maurice Batey wrote:
    > Just did that 2009.0 update, but when booting and using the latest
    > stanza at the end of the GRUB menu to use the new kernel,



    Hmmmm, usually first stanza uses the links in /boot.
    Those links should point to new install if you have a good update.

  4. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    On Wed, 05 Nov 2008 21:10:19 +0000, Bit Twister wrote:

    > Hmmmm, usually first stanza uses the links in /boot.
    > Those links should point to new install if you have a good update.


    Seems so, because I could find no way to revert to the previous
    kernel with that menu.lst.

    So I reverted 2009.0's GRUB/menu.lst to the 'old' copy and booted
    from that. Result - just the same problem.
    Or does that still give the new kernel via links?

    If not, then the update somehow screwed my 2009.0 terminally, so
    unless there is another way to revert to previous kernel I think I'll
    stop trying 2009.0 and not return until perhaps 2009.1.

    Meanwhiile, back to 2008.0...

    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)


  5. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    On Wed, 05 Nov 2008 22:11:17 +0000, Maurice Batey wrote:
    >
    > So I reverted 2009.0's GRUB/menu.lst to the 'old' copy and booted
    > from that. Result - just the same problem.
    > Or does that still give the new kernel via links?


    Take a look at it.

    $ cat /2009_0/boot/grub/menu.lst
    timeout 5
    color black/cyan yellow/cyan
    default 0

    title linux
    kernel (hd0,12)/boot/vmlinuz BOOT_IMAGE=linux root=LABEL=2009_0 vga=791
    initrd (hd0,12)/boot/initrd.img


    If you see something like /boot/vmlinuz and /boot/initrd.img and

    /boot has something like
    vmlinuz -> vmlinuz-2.6.27.4-desktop-1mnb
    2008-10-30 17:08 vmlinuz-2.6.27.4-desktop-1mnb
    2008-10-02 05:15 vmlinuz-2.6.27-desktop-0.rc8.2mnb
    2008-11-05 15:16 vmlinuz-desktop -> vmlinuz-2.6.27.4-desktop-1mnb

    initrd-2.6.27.4-desktop-1mnb.img
    2008-10-21 12:13 initrd-2.6.27-desktop-0.rc8.2mnb.img
    2008-11-05 15:16 initrd-desktop.img -> initrd-2.6.27.4-desktop-1mnb.img
    2008-11-05 15:16 initrd.img -> initrd-2.6.27.4-desktop-1mnb.img

    then it would still boot *-2.6.27.4-desktop-1mnb*

    You just delete the links and redo them for the old release, or pick
    old release at bottom of new menu.lst.

  6. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    On Wed, 05 Nov 2008 19:33:43 +0000, Maurice Batey wrote:

    > "Could not start kstartupconfig.


    I noticed during the bootup that the sequence lingered for a while
    on the line "USBcomm: registering new interface device: ub", or
    something like that.

    So just wondering if the problem is arising because my 2009.0 is
    installed on an external USB drive, with GRUB in its MBR...
    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)


  7. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    Maurice Bate wrote:

    > Just did that 2009.0 update, but when booting and using the latest
    > stanza at the end of the GRUB menu to use the new kernel, after the
    > Login screen (after which it should go into KDE3) a small window pops
    > up top left with the message:
    >
    > "Could not start kstartupconfig. Check your installation."
    >
    > and at bottom left was an unusual "Okay" button, which simply
    > returns to the Login window.
    >
    > Anyone else had this?
    >


    Luckily the 2.67.4 desktop1 kernel upgrade to 2009 went well here though
    on reboot hung for sometime [30secs?] building the new Nvidia 177.x??
    proprietary video driver into new kernel.

    I boot to login screen then choose either KDE3.5.9-10, Xfce, or IceWin as
    my window managers to work from. I'm starting to like IceWin its so easy
    and fast!


    title desktop 2.6.27.4-1mnb
    kernel (hd0,6)/boot/vmlinuz-2.6.27.4-desktop-1mnb
    BOOT_IMAGE=desktop_2.6.27.4-1mnb
    root=UUID=4cd2aa38-a1ec-4422-abac-4406a015b023 noapic nolapic acpi=ht
    splash=verbose vga=788
    initrd (hd0,6)/boot/initrd-2.6.27.4-desktop-1mnb.img

    --
    Patrick...at
    Latitude: 40.48*
    Longitude:-88.95*

  8. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    Maurice Batey wrote:

    > Just did that 2009.0 update, but when booting and using the latest
    > stanza at the end of the GRUB menu to use the new kernel, after the
    > Login screen (after which it should go into KDE3) a small window pops
    > up top left with the message:
    >
    > "Could not start kstartupconfig. Check your installation."
    >
    > and at bottom left was an unusual "Okay" button, which simply
    > returns to the Login window.
    >
    > Anyone else had this?
    >

    I had that a while back. It is a KDE problem. KDE cannot start. The
    message tells the story. The fix is to copy kstartupconfig from another
    user (e.g., BitTwister's "junk" user), but then the number somewhere has to
    be increased by one. It is all on the Web. Happy googling.

    Doug.
    --
    Be wisely worldly, be not worldly wise.
    - Francis Quarles.


  9. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    On Thu, 06 Nov 2008 23:57:46 +1100, Doug Laidlaw wrote:

    > The fix is to copy kstartupconfig from another user


    Uh!? kstartupconfig is in /usr/bin !

    Do you mean some info that it uses?

    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)


  10. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    Maurice Batey wrote:

    > On Thu, 06 Nov 2008 23:57:46 +1100, Doug Laidlaw wrote:
    >
    >> The fix is to copy kstartupconfig from another user

    >
    > Uh!? kstartupconfig is in /usr/bin !
    >
    > Do you mean some info that it uses?
    >

    So I discovered. And all the other Google links aren't the ones I found
    before.

    Basically, something is wrong with your KDE, and it would seem that there
    are a number of reasons. Fixes I found:

    KDE trying to use /home instead of /home/user
    (http://www.rawiriblundell.com/?p=669;)
    Permissions, e.g. http://ubuntuforums.org/showthread.php?p=5368746 (but you
    know about those anyway.)

    Another suggestion, for a different distro, was to run Rescue or Upgrade,
    but in my experience, that would not help under Mandriva, which tends to
    leave /home alone, and won't automatically fix bootloader errors.

    In my case, which was some time ago, there was a dotfile in the /home
    directory that ended in a number. There is a similar file in every user's
    home directory. The one in my /home directory was corrupted. The fix was
    to copy the one from another user (I had a separate user for BOINC,) but to
    change the number at the end so that it was not the same as the original.
    It had to be different. But I can't recall the name of the file, and I
    can't see one with ls -a. From memory, it wasn't in the .kde subdirectory,
    so deleting ~/.kde and letting it be recreated, is no help. The opensuse
    mailing lists seem to have it most. One user there created a new user
    account, copied all his data across, and used that from then on. That
    would be a permanent fix.

    Looking at the dotfiles, it seems to have been .DCOPSERVER__:0,
    and the 0 was what you had to change, e.g to 1. But :0 is usually the
    DISPLAY variable. I went looking for the one in /home/boinc. It wasn't
    there until I ran Konqueror as a file manager, then one was created. There
    are actually two copies, one ending in 0 and one ending in :0. Only one
    needed to be changed, and I have forgotten which. I suspect that the other
    is a backup. This may be enough for the gurus to work on, otherwise
    persistent googling should turn it up. Other posts suggest that DCOPserver
    can leave empty sockets behind. Plainly, my fix isn't the only one.

    HTH,

    Doug.

  11. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    Here is the output from ls /boot on 2009.0:
    ------------------------
    boot.backup.sdc
    config@
    config-2.6.27.4-desktop586-1mnb
    config-2.6.27-desktop586-0.rc8.2mnb
    gfxmenu
    grub/
    initrd-2.6.27.4-desktop586-1mnb.img
    initrd-2.6.27-desktop586-0.rc8.2mnb.img
    initrd-desktop586.img@
    initrd.img@
    kernel.h@
    kernel.h-2.6.27.4-desktop586-1mnb
    kernel.h-2.6.27-desktop586-0.rc8.2mnb
    System.map@
    System.map-2.6.27.4-desktop586-1mnb
    System.map-2.6.27-desktop586-0.rc8.2mnb
    uk-latin1.klt
    vmlinuz@
    vmlinuz-2.6.27.4-desktop586-1mnb
    vmlinuz-2.6.27-desktop586-0.rc8.2mnb
    vmlinuz-desktop586@
    ------------------------
    > You just delete the links and redo them for the old release, or pick
    > old release at bottom of new menu.lst.


    In the above list, which files?
    What do you mean "redo them for the old release"?!
    New menu.lst has *new* kernel stanza at bottom. Do you mean
    penultimate stanza?

    Here is the new menu.lst:
    ----------------------------------------------
    timeout 10
    color black/cyan yellow/cyan
    gfxmenu (hd0,5)/boot/gfxmenu
    default 0

    title Mandriva 2009.0 'One/Live'
    kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=Mandriva_2009.0_'One/Live'
    root=UUID=d0baa141-4f0f-4a3e-b7ba-af97fb659532
    resume=UUID=024fb1a9-abd0-402e-a0e1-2deed50b79c8 splash=silent vga=788
    initrd (hd0,5)/boot/initrd.img

    title linux-nonfb
    kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=linux-nonfb
    root=UUID=d0baa141-4f0f-4a3e-b7ba-af97fb659532
    resume=UUID=024fb1a9-abd0-402e-a0e1-2deed50b79c8
    initrd (hd0,5)/boot/initrd.img

    title failsafe
    kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=failsafe
    root=UUID=d0baa141-4f0f-4a3e-b7ba-af97fb659532 failsafe
    initrd (hd0,5)/boot/initrd.img

    title Windows XP SP3
    root (hd2,0)
    map (0x81) (0x80)
    map (0x80) (0x81)
    makeactive
    chainloader +1

    title Mandriva Linux (Official)
    root (hd0,0)
    configfile /boot/grub/menu.lst

    title linux
    kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=linux
    root=UUID=d0baa141-4f0f-4a3e-b7ba-af97fb659532
    resume=UUID=024fb1a9-abd0-402e-a0e1-2deed50b79c8 splash=silent vga=788
    initrd (hd0,5)/boot/initrd.img

    title desktop586 2.6.27.4-1mnb
    kernel (hd0,5)/boot/vmlinuz-2.6.27.4-desktop586-1mnb
    BOOT_IMAGE=desktop586_2.6.27.4-1mnb
    root=UUID=d0baa141-4f0f-4a3e-b7ba-af97fb659532
    resume=UUID=024fb1a9-abd0-402e-a0e1-2deed50b79c8 splash=silent vga=788
    initrd (hd0,5)/boot/initrd-2.6.27.4-desktop586-1mnb.img
    ----------------------------------------------------------------
    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)


  12. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    On Fri, 07 Nov 2008 02:23:26 +1100, Doug Laidlaw wrote:

    > it seems to have been .DCOPSERVER_


    Well, there are 2 'DCOP' files in my 2008.0 /home, so tried copying
    those across to 2009.0, but still same problem.

    I can't actually *do* anything on 2009.0, because IceWM's terminal
    denies all knowledge of a /home directory, though I can get into MCC,
    and error msgs like "Config file //.KDE4/share/config/kconsolerc not
    writable" occur.
    (I removed KDE4 before the update; running KDE3...)

    Googling groups shows other distributions having similar problems,
    cured in some cases by doing "chown -R :users /home/", but
    when I tried that in IceWM's terminal it denied there was a /home!

    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)


  13. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    Maurice Batey wrote:
    > On Fri, 07 Nov 2008 02:23:26 +1100, Doug Laidlaw wrote:
    >
    >> it seems to have been .DCOPSERVER_

    >
    > Well, there are 2 'DCOP' files in my 2008.0 /home, so tried copying
    > those across to 2009.0, but still same problem.
    >
    > I can't actually *do* anything on 2009.0, because IceWM's terminal
    > denies all knowledge of a /home directory, though I can get into MCC,
    > and error msgs like "Config file //.KDE4/share/config/kconsolerc not
    > writable" occur.
    > (I removed KDE4 before the update; running KDE3...)
    >
    > Googling groups shows other distributions having similar problems,
    > cured in some cases by doing "chown -R :users /home/", but
    > when I tried that in IceWM's terminal it denied there was a /home!
    >


    Try logging into console only mode alt+N, I think, instead of IceWM. Become
    root and chown -R user:user /home/user (for me I would run chown -R
    thai:thai /home/thai) remove any /home/user/ .DCOPServer .Xauthority and
    ..ICEauthority files. Change back from root to your normal login at the
    console prompt and then attempt to run startx. If there is a different
    problem going on you should at least get a new error message. If you have an
    incomplete upgrade you should still be able to run urpmi --auto-update.



    Thai

  14. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    Hi Maurice,


    Maurice Batey wrote:
    > On Wed, 05 Nov 2008 19:33:43 +0000, Maurice Batey wrote:
    >
    >> "Could not start kstartupconfig.

    >
    > I noticed during the bootup that the sequence lingered for a while
    > on the line "USBcomm: registering new interface device: ub", or
    > something like that.


    I've got the same problem, a long lasting message about a new usb device
    makes bootup need at least 10 times the amount of time it used
    before the kernel was upgraded.


    >
    > So just wondering if the problem is arising because my 2009.0 is
    > installed on an external USB drive, with GRUB in its MBR...


    Well, I don't think so, because my 2009.0 is installed on the internal
    HD. However, I do have a USB scanner and a USB mouse attached and didn't
    try detaching them yet.

    Marja

  15. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    Thai C. Stacy wrote:

    > Maurice Batey wrote:
    >> On Fri, 07 Nov 2008 02:23:26 +1100, Doug Laidlaw wrote:
    >>
    >>> it seems to have been .DCOPSERVER_

    >>
    >> Well, there are 2 'DCOP' files in my 2008.0 /home, so tried copying
    >> those across to 2009.0, but still same problem.
    >>
    >> I can't actually *do* anything on 2009.0, because IceWM's terminal
    >> denies all knowledge of a /home directory, though I can get into MCC,
    >> and error msgs like "Config file //.KDE4/share/config/kconsolerc not
    >> writable" occur.
    >> (I removed KDE4 before the update; running KDE3...)
    >>
    >> Googling groups shows other distributions having similar problems,
    >> cured in some cases by doing "chown -R :users /home/", but
    >> when I tried that in IceWM's terminal it denied there was a /home!
    >>

    >
    > Try logging into console only mode alt+N, I think, instead of IceWM.
    > Become root and chown -R user:user /home/user (for me I would run chown -R
    > thai:thai /home/thai) remove any /home/user/ .DCOPServer .Xauthority and
    > .ICEauthority files. Change back from root to your normal login at the
    > console prompt and then attempt to run startx. If there is a different
    > problem going on you should at least get a new error message. If you have
    > an incomplete upgrade you should still be able to run urpmi --auto-update.
    >
    >
    >
    > Thai

    That is a clue. .KDE4 is not writable. IceWM may be saying that it is not
    readable either. You can get into console mode as root (which you will
    probably need, anyway) by booting into Failsafe mode. BTW, when your
    cursor turns into a cross, that is an X and means that X is running.

    Doug.
    --
    Husbands are like the fire on the hearth - likely to go out if left
    unattended.
    - W.G.P.


  16. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    On Thu, 06 Nov 2008 16:08:47 +0000, Maurice Batey wrote:
    > Here is the output from ls /boot on 2009.0:


    You needed to do a ls -al and you will see what is linked to whom.
    > ------------------------
    > boot.backup.sdc
    > config@
    > config-2.6.27.4-desktop586-1mnb
    > config-2.6.27-desktop586-0.rc8.2mnb
    > gfxmenu
    > grub/
    > initrd-2.6.27.4-desktop586-1mnb.img
    > initrd-2.6.27-desktop586-0.rc8.2mnb.img
    > initrd-desktop586.img@
    > initrd.img@
    > kernel.h@
    > kernel.h-2.6.27.4-desktop586-1mnb
    > kernel.h-2.6.27-desktop586-0.rc8.2mnb
    > System.map@
    > System.map-2.6.27.4-desktop586-1mnb
    > System.map-2.6.27-desktop586-0.rc8.2mnb
    > uk-latin1.klt
    > vmlinuz@
    > vmlinuz-2.6.27.4-desktop586-1mnb
    > vmlinuz-2.6.27-desktop586-0.rc8.2mnb
    > vmlinuz-desktop586@
    > ------------------------
    >> You just delete the links and redo them for the old release, or pick
    >> old release at bottom of new menu.lst.

    >
    > In the above list, which files?
    > What do you mean "redo them for the old release"?!
    > New menu.lst has *new* kernel stanza at bottom. Do you mean
    > penultimate stanza?


    Do a cd /boot
    ls -al and you will see who is linked to which files.

    If I wanted a link back to old boot I would
    rm config initrd.img kernel.h System.map vmlinuz
    ln -s config-2.6.27-desktop586-0.rc8.2mnb config
    ln -s initrd-2.6.27-desktop586-0.rc8.2mnb.img initrd
    ln -s kernel.h-2.6.27-desktop586-0.rc8.2mnb kernel.h
    ln -s System.map-2.6.27-desktop586-0.rc8.2mnb System.map
    ln -s vmlinuz-2.6.27-desktop586-0.rc8.2mnb vmlinuz

    That, I assume, will allow virtualbox to rebuild it's driver
    with the correct files.

    > Here is the new menu.lst:
    > ----------------------------------------------
    >
    > title Mandriva 2009.0 'One/Live'
    > kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=Mandriva_2009.0_'One/Live'
    > root=UUID=d0baa141-4f0f-4a3e-b7ba-af97fb659532
    > resume=UUID=024fb1a9-abd0-402e-a0e1-2deed50b79c8 splash=silent vga=788
    > initrd (hd0,5)/boot/initrd.img


    Look at the above stanza. The files used, will be
    /boot/vmlinuz and /boot/initrd.img

    Whatever they are linked to will be booted.

    >
    > title linux
    > kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=linux
    > root=UUID=d0baa141-4f0f-4a3e-b7ba-af97fb659532
    > resume=UUID=024fb1a9-abd0-402e-a0e1-2deed50b79c8 splash=silent vga=788
    > initrd (hd0,5)/boot/initrd.img


    The above is using the /boot/vmlinuz, /boot/initrd.img links.
    You could change them as follows

    > title linux_old
    > kernel (hd0,5)/boot/vmlinuz-2.6.27-desktop586-0.rc8.2mnb BOOT_IMAGE=linux
    > root=UUID=d0baa141-4f0f-4a3e-b7ba-af97fb659532
    > resume=UUID=024fb1a9-abd0-402e-a0e1-2deed50b79c8 splash=silent vga=788
    > initrd (hd0,5)/boot/initrd-2.6.27-desktop586-0.rc8.2mnb.img



    The following is not using links.

    > title desktop586 2.6.27.4-1mnb
    > kernel (hd0,5)/boot/vmlinuz-2.6.27.4-desktop586-1mnb
    > BOOT_IMAGE=desktop586_2.6.27.4-1mnb
    > root=UUID=d0baa141-4f0f-4a3e-b7ba-af97fb659532
    > resume=UUID=024fb1a9-abd0-402e-a0e1-2deed50b79c8 splash=silent vga=788
    > initrd (hd0,5)/boot/initrd-2.6.27.4-desktop586-1mnb.img


    There you are using actual file names.

  17. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    On Thu, 06 Nov 2008 17:32:12 +0000, Bit Twister wrote:

    > Do a cd /boot
    > ls -al and you will see who is linked to which files.


    Hadn't realised I could do that without being logged in to 2009.0!

    From within 2008.0 "ls -al" shows one line blinking red:

    2008-11-06 16:43 kernel.h -> /boot/kernel.h-2.6.27.4-desktop586-1mnb

    It shows these with cyan-tinted names before the "->":

    2008-11-06 16:42 config -> config-2.6.27.4-desktop586-1mnb

    2008-11-05 18:40 initrd-desktop586.img ->
    initrd-2.6.27.4-desktop586-1mnb.img

    2008-11-05 19:17 System.map -> System.map-2.6.27.4-desktop586-1mnb

    2008-11-05 18:39 vmlinuz -> vmlinuz-2.6.27.4-desktop586-1mnb

    2008-11-05 18:40 vmlinuz-desktop586 ->
    vmlinuz-2.6.27.4-desktop586-1mnb

    Is it just the one beginning "initrd" that should be zapped?

    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)


  18. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    On Thu, 06 Nov 2008 17:50:16 +0000, Maurice Batey wrote:
    > On Thu, 06 Nov 2008 17:32:12 +0000, Bit Twister wrote:
    >
    >> Do a cd /boot
    >> ls -al and you will see who is linked to which files.

    >
    > Hadn't realised I could do that without being logged in to 2009.0!
    >
    > From within 2008.0 "ls -al" shows one line blinking red:
    >
    > 2008-11-06 16:43 kernel.h -> /boot/kernel.h-2.6.27.4-desktop586-1mnb


    Blinking links usually indicate the target no longer exists.


    >
    > It shows these with cyan-tinted names before the "->":
    >
    > 2008-11-06 16:42 config -> config-2.6.27.4-desktop586-1mnb
    >
    > 2008-11-05 18:40 initrd-desktop586.img ->
    > initrd-2.6.27.4-desktop586-1mnb.img
    >
    > 2008-11-05 19:17 System.map -> System.map-2.6.27.4-desktop586-1mnb
    >
    > 2008-11-05 18:39 vmlinuz -> vmlinuz-2.6.27.4-desktop586-1mnb
    >
    > 2008-11-05 18:40 vmlinuz-desktop586 ->
    > vmlinuz-2.6.27.4-desktop586-1mnb
    >
    > Is it just the one beginning "initrd" that should be zapped?


    Version numbers should match. initrd would have to be
    ln -s initrd-2.6.27.4-desktop586-1mnb.img initrd.img

    You indicated kernel.k link was bad. You may need
    /boot/kernel.h-2.6.27.4-desktop586-1mnb installed for some of your
    third party apps to complete compile/linking.

    I know my virtualbox and ATI video driver will detect kernel changes
    and do a rebuild during startup.

  19. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    On Thu, 06 Nov 2008 12:50:16 -0500, Maurice Batey wrote:

    > From within 2008.0 "ls -al" shows one line blinking red:
    > 2008-11-06 16:43 kernel.h -> /boot/kernel.h-2.6.27.4-desktop586-1mnb


    That's because the link is an absolute link, instead of a realative one.

    When you're running 2009.0, that link is pointing to a file in the 2009.0 /boot
    directory. When you're running 2008.0, it's pointing to (a nonexistent) file
    in the 2008.0 /boot directory.

    Regards, Dave Hodgins

    --
    Change nomail.afraid.org to ody.ca to reply by email.
    (nomail.afraid.org has been set up specifically for
    use in usenet. Feel free to use it yourself.)

  20. Re: Problem with latest 2009.0 kernel desktop586-2.6.27-41mnb

    On Thu, 06 Nov 2008 16:02:15 -0500, David W. Hodgins wrote:

    > That's because the link is an absolute link, instead of a realative one.
    >
    > When you're running 2009.0, that link is pointing to a file in the 2009.0 /boot
    > directory. When you're running 2008.0, it's pointing to (a nonexistent) file
    > in the 2008.0 /boot directory.


    Ah, yes, of course. - thanks, Dave!

    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)


+ Reply to Thread
Page 1 of 2 1 2 LastLast