problems, custom kernel

Discussion in 'Linux, BSD and Other OS's' started by donkey42, Mar 13, 2008.

  1. donkey42

    donkey42 plank

    Likes Received:
    9
    Trophy Points:
    38
    right, when i installed the newer custom HWF kernel, i stupidly[ot]i know, i know[/ot]anyway i forgot uninstall the the old custom kernel and i must have done it again because uname -r returns: 2.6.23.14.p4.desktop.64gb.02, and it didn't appear to be a problem, but, now, i DLed the deb for Vbox & it can't find my kernel sources

    in the meantime the custom kernel has being updated again i got it but never got round to installing it (i got image & headers dated 15/2/2008

    so, to help me out of the sh1t i caused, how can i rename the image & headers or do i have to uninstall the 2.6.23.14.p4.desktop.64gb.02 & install the newer (15/2/2008)

    BTW: yes i am a plank & stupid
     
  2. Anti-Trend

    Anti-Trend Nonconformist Geek

    Likes Received:
    118
    Trophy Points:
    63
    If I was you, I'd install the latest kernel & source from the repo, boot to it, then rebuild your virtualbox drivers. After you're sure it's working correctly you can remove the old one.

    P.S. - You're not stupid. :) Come on, you're running a better OS than what 90% of people use, and you're running a custom kernel on it. Give yourself some credit man!
     
  3. donkey42

    donkey42 plank

    Likes Received:
    9
    Trophy Points:
    38
    well, true, but it was funny

    surely the new kernel will be automatically renamed to 2.6.23.14.p4.desktop.64gb.03

    am i right ?
     
  4. Anti-Trend

    Anti-Trend Nonconformist Geek

    Likes Received:
    118
    Trophy Points:
    63
    No, the kernel won't be renamed. The new kernel is called 2.6.23.17.hwf.$CPU.$REV
     
  5. donkey42

    donkey42 plank

    Likes Received:
    9
    Trophy Points:
    38
    you've updated them again, i've got the ones dated 15/2/2008, no big deal i'll just DL them again, :beer:
     
  6. donkey42

    donkey42 plank

    Likes Received:
    9
    Trophy Points:
    38
    vbox installs ok, but, i think i may have installed the custom kernel wrong because vbox runs ok, but will not start a VM, upon starting a VM, vbox the following error,
    [​IMG]
    vboxdrv contains
    Code:
    Makefile:75: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
    uname -r returns: 2.6.23.17.hwf.p4.01

    to install the custom kernel i simply executed the debs, as i usually do

    BTW: ive searched google & [noparse]vbox.org[/noparse] unsuccessfully, so, i'm relying on you guys (again)

    Edit: and sudo /etc/init.dvboxdrv start returns:
    [​IMG]

    please help, TIA
     
  7. Anti-Trend

    Anti-Trend Nonconformist Geek

    Likes Received:
    118
    Trophy Points:
    63
    That means the symlinks that are supposed to point towards /usr/src/`uname -r` didn't work. If you type (or copy/paste) these two lines as root, it should fix it:
    Code:
    ln -s /usr/src/`uname -r` /lib/modules/`uname -r`/build
    ln -s /usr/src/`uname -r` /lib/modules/`uname -r`/source
    Then you can ask the vbox driver to rebuild:
    Code:
    /etc/init.d/vboxdrv setup
     
  8. donkey42

    donkey42 plank

    Likes Received:
    9
    Trophy Points:
    38
    i'm a plank, i didn't even have the sources installed :doh: downloading them now :doh:
     
  9. Anti-Trend

    Anti-Trend Nonconformist Geek

    Likes Received:
    118
    Trophy Points:
    63
    OK, let me know how it works out.
     

Share This Page