Find the answer to your Linux question:
Results 1 to 10 of 10
So I installed FC10 x64 on my laptop. Sure of it, have the CD right here and it is the x64 Image, and I know when I first brought it ...
  1. 03-26-2009 #1
    cybersmurf
    cybersmurf is offline
    Linux Newbie cybersmurf's Avatar
    Join Date
    Apr 2006
    Posts
    122

    Serious WTF! Kernel changed to i686?

    So I installed FC10 x64 on my laptop. Sure of it, have the CD right here and it is the x64 Image, and I know when I first brought it up it was the x64 image, I look in my /usr/lib, I have lib64. All the sudden now I try to install VMWare and I notice that it says my Kernel is i686. Mur? I dont have the loading screen in which to select kernels to see what is going on, and see if I can select, so wondering how the heck I can revert to my previous x64 build.
    The problem with developing something completely foolproof is underestimating the complete ingenuity of fools ~Unknown
    Reply With Quote Reply With Quote
  2. 03-26-2009 #2
    HROAdmin26
    HROAdmin26 is offline
    Linux Guru
    Join Date
    Nov 2007
    Posts
    1,695
    What does uname say is the kernel?

    Code:
    uname -a
    Reply With Quote Reply With Quote
  3. 03-26-2009 #3
    cybersmurf
    cybersmurf is offline
    Linux Newbie cybersmurf's Avatar
    Join Date
    Apr 2006
    Posts
    122
    Code:
     [root@Roamingstar Desktop]# uname -a
Linux Roamingstar 2.6.27.19-170.2.35.fc10.i686 #1 SMP Mon Feb 23 13:21:22 EST 2009 i686 athlon i386 GNU/Linux
    The problem with developing something completely foolproof is underestimating the complete ingenuity of fools ~Unknown
    Reply With Quote Reply With Quote
  4. 03-26-2009 #4
    HROAdmin26
    HROAdmin26 is offline
    Linux Guru
    Join Date
    Nov 2007
    Posts
    1,695
    Yep - that's a 32 bit kernel. A 64 bit will have something like x86_64 in the uname output.
    Reply With Quote Reply With Quote
  5. 03-26-2009 #5
    cybersmurf
    cybersmurf is offline
    Linux Newbie cybersmurf's Avatar
    Join Date
    Apr 2006
    Posts
    122
    Yes... I know this, how did a x86 kernel get popped in there when I installed a x64 kernel, and how do I get my x64 back? Or do I have to just do an upgrade or re-install.
    The problem with developing something completely foolproof is underestimating the complete ingenuity of fools ~Unknown
    Reply With Quote Reply With Quote
  6. 03-26-2009 #6
    cybersmurf
    cybersmurf is offline
    Linux Newbie cybersmurf's Avatar
    Join Date
    Apr 2006
    Posts
    122
    And if you seriously dont believe me, here are some pictures I happened to take and got lucky enough showed my CLI.

    Computer Stuff Photo Gallery - Photo 1 of 1 by SkitterSmurf - MySpace Photos

    Still digging around trying to figure out wtf happened.
    The problem with developing something completely foolproof is underestimating the complete ingenuity of fools ~Unknown
    Reply With Quote Reply With Quote
  7. 03-26-2009 #7
    HROAdmin26
    HROAdmin26 is offline
    Linux Guru
    Join Date
    Nov 2007
    Posts
    1,695
    ...I am going to go out on a limb here and say it's *very very very unlikely* that the kernel has changed since your install.

    You may want to reconfirm that the uname output isn't the same thing you had after the initial install.

    And what does Grub's menu.lst show?

    Code:
    cat /boot/grub/menu.lst
    Reply With Quote Reply With Quote
  8. 03-26-2009 #8
    cybersmurf
    cybersmurf is offline
    Linux Newbie cybersmurf's Avatar
    Join Date
    Apr 2006
    Posts
    122
    Same thing, all x86. See pic above
    The problem with developing something completely foolproof is underestimating the complete ingenuity of fools ~Unknown
    Reply With Quote Reply With Quote
  9. 03-26-2009 #9
    HROAdmin26
    HROAdmin26 is offline
    Linux Guru
    Join Date
    Nov 2007
    Posts
    1,695
    The only thing the pic shows is a reduced-size desktop with Thunderbird open and a half-covered console window. I do seem to see a Thunderbird package referenced with .x86_64 on the name.

    So the kernel changed and the menu.lst was completely replaced with 32 bit entries as well? I don't think that's anything I've ever seen or heard of...

    Example 64 bit menu.lst:

    Code:
    title Fedora (2.6.27.19-170.2.35.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.19-170.2.35.fc10.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.27.19-170.2.35.fc10.x86_64.img
title Fedora (2.6.27.15-170.2.24.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.15-170.2.24.fc10.x86_64 ro root=UUID=fe8f0e50-4b66-496c-a215-865dcc45723f rhgb quiet
initrd /initrd-2.6.27.15-170.2.24.fc10.x86_64.img
    Are there any "other" kernels left over in /boot? Normally if an updated kernel is installed, the older kernel is left behind as a backup.

    Code:
    ls -alh /boot
    Reply With Quote Reply With Quote
  10. 03-26-2009 #10
    cybersmurf
    cybersmurf is offline
    Linux Newbie cybersmurf's Avatar
    Join Date
    Apr 2006
    Posts
    122
    Yeah I know, I have x64 on my Desktop, Fedora, so I know what it should look like and what it did on this system.

    Sorry that was all I could find a proof of the fact I am not going psycho. it is a consol image I took awhile ago but says x86_64 package everywere on it. Yum doesnt do x64 installs without the x64 kernel
    The problem with developing something completely foolproof is underestimating the complete ingenuity of fools ~Unknown
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules

...