|
hi
Possible bug or 2 related to changing kernel using smxi 1) I moved from Damentz to aptosid Using smxi I deleted old kernels and set up default to new kernel I am booted up into it now 2) I normally manually run :: Code :: su
/etc/init.d/vboxdrv setup but after kernel change it failed with log contents of :: Quote :: Makefile:170: *** Error: /usr/src/linux (version 2.6.36) does not match the current kernel (version 2.6.36-2.slh.1-aptosid-686). Stop.ok so I found an old symlink had not been removed in /usr/src and so made new symlink but that did not solve my issue :: Code :: ls -al /usr/src/linux
lrwxrwxrwx 1 root root 40 Dec 12 07:30 /usr/src/linux -> linux-headers-2.6.36-2.slh.1-aptosid-686 a repeat of my vbox build gave the same error so then I tried using smxi and build the vbox module Unfortunately fbgrab snapshot program has been replaced with fbcat and I can not use my capture command of fbcat -c 1 /root/shot.ppm and not sure how to show the screenshot but roughly it says 3) "building modules failed...look at /var/log/vbox-install AND THEN it says something like success......(when it is a fail) I tried to find this in the smxi log but failed to find it as well....oh well 4) so I tried smxi and install vbox non-free for Lenny with similar result regards Back to top |
|
hi
after a bit of google there appears to be issues with aptosids makefile needing extraversion ? but my attempt to fix that is currently a fail so instead I installed dkms and installed the Debian kernel but symlinks are IMHO still wrong after kernel change :: Code :: ls -al /usr/src
total 32 drwxr-xr-x 8 root root 4096 Dec 12 09:49 . drwxr-xr-x 16 root root 4096 Dec 5 12:05 .. lrwxrwxrwx 1 root root 40 Dec 12 09:23 linux -> linux-headers-2.6.36-2.slh.1-aptosid-686 drwxr-xr-x 4 root root 4096 Dec 12 09:49 linux-headers-2.6.32-5-686 drwxr-xr-x 4 root root 4096 Dec 12 09:49 linux-headers-2.6.32-5-common drwxr-xr-x 21 root root 4096 Dec 12 09:49 linux-headers-2.6.36-2.slh.1-aptosid-686 lrwxrwxrwx 1 root root 26 Dec 12 09:49 linux-kbuild-2.6.32 -> ../lib/linux-kbuild-2.6.32 drwxr-xr-x 2 root root 4096 Dec 5 14:22 sgfxi-downloads drwxr-xr-x 4 root root 4096 Dec 12 09:49 sm-kernel-downloads drwxr-xr-x 3 root root 4096 Dec 12 07:42 svmi-downloads lrwxrwxrwx 1 root root 32 Dec 12 07:50 vboxhost-3.2.12 -> ../share/virtualbox/src/vboxhost 2) In using smxi to change to Debian kernel I found smxi offered me something that did NOT occur for the aptosid change and that is an option to search and update my /etc/fstab due to Debian kernel and IDE devices and UUIDs etc and success using dkms with /etc/init.d/vboxdrv setup 3) So in summary IMHO changing kernel may need beter symlinks? non-free Vbox users who CHANGE kernel streams may need to use DKMS Back to top |
|
I've just be hit by this. I had no issues with kernel upgrades and recompiling vboxdrv with each kernel, including the latest 2.6.35-2.slh.1-aptosid-686. I then upgraded vbox to 3.2.12 from 3.2.10 with smxi and encountered the same failure issue :
:: Code :: Makefile:170: *** Error: /usr/src/linux (version 2.6.36) does not match the current kernel (version 2.6.36-2.slh.1-aptosid-686). Stop.
My solution was here : aptosid.com/index.php?name=PNphpBB2&file=viewtopic&p=2488 . . . . as it must have been when I installed vbox 3.2.10 a few months back! Back to top |
|
If this is an aptosid kernel bug which I believe it is, and if it does not appear with liquorix or debian experimental kerhels, then I suggest you not use kernels where the maintainer ignores bug reports and allow that distro to continue on its downward trajectory since that's clearly what they want to do.
If this is caused by some other issue, then let me know, I have seen zero issues with 2.6.36 and vbox non ose here. Back to top |
|
Maybe you can use one of towos kernels for aptosid. He had brought up the solutions for vbox initiately and might have them implemented (as damentz does for liquorix kernels now).
regards Reiner Back to top |
|
[svmi] xmms: command not found
Hi all,
today i'm upgrading my pc using smxi/svmi and svmi simply does not work anymore: :: Code ::
# svmi Updating svmi now using the default server ./svmi: line 992: xmms: command not found #svmi /usr/local/bin/svmi: line 992: xmms: command not found # I don't use xmms but also instlling xmms2 does not help... blindly "solved" by removing: :: Code ::
for package in $(xmms nano iceweasel kate vim gimp) do time check_install_tools $package i time check_install_tools $package c done;exit ... and running: :: Code ::
svmi -R Back to top |
|
sorry about that, I left in a bad debugger for some changes.
What's even more embarrassing is that the debugger was wrong as well. If you get this error in svmi, do: cd /usr/local/bin && wget -o svmi smxi.org/svmi && chmod +x svmi and you'll be ready to go. Or just start svmi from smxi, and it will get the fixed version. I wasn't actually working with svmi, I just updated it by accident then didn't notice I had done that. the real test, for anyone interested, was this: :: Code :: # in function check_package_status() alternate these:
packageVersion=$( awk 'BEGIN {IGNORECASE=1} /'$statusType'/ && !/\(None\)/ {print $2}' <<< "$cacheData" ) packageVersion=$( grep -i "$statusType" <<< "$cacheData" | cut -d ':' -f 2-4 | cut -d ' ' -f2 | grep -iv '\(none\)' ) ## after function: check_package_status() place: echo start; for package in xmms nano iceweasel kate vim gimp do time check_package_status $package i time check_package_status $package c done;echo stop;exit The purpose was to see if that function had any significant time difference between using the piped grep/cut string and using a single awk thing. The result? There was basically no difference in time at all, so I switched it to the awk. this test was more for smxi, which uses this core function a lot, so the time differences, if any, would be more relevant there. Back to top |
|
LibreOffice Installer
the packages libreoffice-thesaurus-* are not in repositories so smxi give an error. For openoffice.org-thesaurus-* the package still exist. Back to top |
|
thanks, I thought those were in but I guess not yet. Or maybe the package has some other name?
the open/libre logic required making every single ooo/libre tool dynamic, ie, detecting installed/candidate versions, and offering users options based on that. so no surprise to get some bugs. wonder if there will be thesaurus coming? Back to top |
|
package names changed, now smxi will do dynamic detections for installation candidates and only add them if apt has them
new names are: mythes == thesaurus myspell == unchanged myhyph == hyphenation Back to top |
|
All times are GMT - 8 Hours |