Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by viking777

  1. I just hope you have Nvidia graphics!! (or Intel)
  2. Hey scarecrow, I would like to thank you very much for looking into that for me. Obviously it is not just a problem for me. I have no idea how to apply the patch you linked to, and it doesn't really matter that much, the point of the post was firstly to see if it was solely my problem, which it obviously isn't, and secondly to ascertain if there was a problem with the kernel files themselves, which there may well be, but at least if that is the case it hasn't gone unnoticed. Thanks again.
  3. Can anyone tell me why every time I boot kernel-desktop586-2.6.29-0.rc5.1mnb it tries to install vboxdrv and fails? I ran /etc/init.d/vboxdrv setup In a terminal and go the following error: Building module: cleaning build area.... make KERNELRELEASE=2.6.29-desktop586-0.rc5.1mnb -C /lib/modules/2.6.29-desktop586-0.rc5.1mnb/build M=/var/lib/dkms/vboxdrv/2.0.4/build....(bad exit status: 2) Error! Bad return status for module build on kernel: 2.6.29-desktop586-0.rc5.1mnb (i586) Consult the make.log in the build directory /var/lib/dkms/vboxdrv/2.0.4/build/ for more information. Failed to install using DKMS, attempting to install without Makefile:153: *** Error: /usr/src/linux (version 2.6.29-0.rc5.1mnbcustom) does not match the current kernel (version 2.6.29-desktop586-0.rc5.1mnb). Stop. There is no such folder as /usr/src/linux/2.6.29-0.rc5.1mnbcustom so why is it looking for a makefile in a non-existant folder? As the error suggested I also looked in /var/lib/dkms/vboxdrv/2.0.4/build and it says: DKMS make.log for vboxdrv-2.0.4 for kernel 2.6.29-desktop586-0.rc5.1mnb (i586) Tue Mar 3 10:23:34 GMT 2009 make: Entering directory `/usr/src/linux-2.6.29-0.rc5.1mnb' WARNING: Symbol version dump /usr/src/linux-2.6.29-0.rc5.1mnb/Module.symvers is missing; modules will have no dependencies and modversions. LD /var/lib/dkms/vboxdrv/2.0.4/build/built-in.o CC [M] /var/lib/dkms/vboxdrv/2.0.4/build/linux/SUPDrv-linux.o /var/lib/dkms/vboxdrv/2.0.4/build/linux/SUPDrv-linux.c: In function ‘VBoxDrvLinuxCreate’: /var/lib/dkms/vboxdrv/2.0.4/build/linux/SUPDrv-linux.c:650: error: ‘struct task_struct’ has no member named ‘euid’ /var/lib/dkms/vboxdrv/2.0.4/build/linux/SUPDrv-linux.c:663: error: ‘struct task_struct’ has no member named ‘uid’ /var/lib/dkms/vboxdrv/2.0.4/build/linux/SUPDrv-linux.c:664: error: ‘struct task_struct’ has no member named ‘gid’ make[1]: *** [/var/lib/dkms/vboxdrv/2.0.4/build/linux/SUPDrv-linux.o] Error 1 make: *** [_module_/var/lib/dkms/vboxdrv/2.0.4/build] Error 2 make: Leaving directory `/usr/src/linux-2.6.29-0.rc5.1mnb' Does that mean there is some kind of error in these kernel-sources? I don't know enough about it to work that out.
  4. I was referring to the kernel-source packages in that quote (then I got sidetracked into talking about -devel pacakages). Long and short of it the kernel-source packages for kernel 2.6.29.x are already there, have been since Mar 1st.
  5. Absolutely not a problem - I just thought I was missing something!
  6. Never was a truer word spoken - I use nothing else but XFCE now (actually not quite, I still use KDE 3.5.10 on suse 11, for two reasons, first it is the only KDE distro that hasn't self-destrtucted by trying to make KDE4 work and secondly because XFCE won't work on Suse 11 - not for me anyway). Truth is I hardly ever use Suse anyway, the only reason I haven't deleted it is because it is the only one of my 4 distros on which the BBC Iplayer desktop will work properly (ie. will save programs to disk as well as stream them). Something to do with Kwalletmanager I think.
  7. There is a screenshot of Xfce 4.6 window manager settings. Please tell me how to add an 'always on top' button from there. If I am in the wrong screen then could you possibly direct me to the correct one. Ta very much viking777
  8. OK here we go then. I have just installed: kernel-desktop586-2.6.29-0.rc6.1.1mnb I also have: kernel-desktop-devel-2.6.29-0.rc6.1.1mnb and: nvidia-current-kernel-2.6.29-desktop586-0.rc6.1.1mnb and: nvidia-current-kernel-desktop586-latest and: dkms and: dkms-nvidia-current But I have no graphics because I do not have any kernel-headers for this kernel, but even when I do, dkms will not compile the Nvidia driver for me, I will have to do it myself, I know this from past experience as recent as today. For a long time now I have had: kernel-desktop586-2.6.29-0.rc5.1mnb on my system along with all the other related packages that I have listed above, but I could never boot it because I didn't have the kernel-headers package, that only arrived today, as soon as it did I installed it and tried to boot - it failed. I install the Nvidia drivers myself and it works, but never with dkms. It is only Cooker that behaves this way, 2009.0 is fine with dkms. So you are absolutely right that Nvidia is supposed to compile with the 'kernel-devel' package, but it never does, at least not for me, I always have to have the 'headers' package as well and even then dkms won't do it (on Cooker). I don't know if this is how it is supposed to work, but it is how it works for me.
  9. Arrived this morning for me (about a fortnight after the kernel!!) (assuming you are talking about kernel 2.6.29-desktop586-0.rc5.1mnb). I have never booted it before because I have never been able to compile the Nvidia driver (dkms one didn't work - very rarely does with new kernels on cooker). One thing I have noticed already with it is that it wont compile the vboxdrv module either - it tries on every boot but fails each time.
  10. I didn't even have to wait that long, it installed properly this evening. I don't see a lot to get excited about though, correction, I don't see anything to get excited about. 2 years of development and they can't even manage to get an 'always on top' button to go on the window border!! It must be me, virtually every 'improvement' I read about is of no consequence to me whatsoever. I sometimes wonder if I am on the same planet as everyone else : :unsure:
  11. It doesn't install though I just tried it and it fails (usual thing, missing dependency but I can't remember what it was). I'll leave it a day or so, it will probably come right.
  12. It always mystifies me why so many distro makers put themselves through this self imposed deadline hell - because the others do it is the nearest explanation I can come up with. I am sure their commercial customers don't want this, they will nearly always buy LTS versions anyway, and as for simple users like myself well I would far rather wait 9 months for a distro that is fully working than have a half working one in 6 months. Mind you if they are waiting for KDE4 to come right they will wait forever.
  13. Forget it, it is because I was using Fish. When I changed the shell back to bash it worked. But if anyone can tell me how to make it work in Fish I would love to know. It is a more 'friendly' shell. Edit: apart from this problem obviously.
  14. If I type: echo $PATH as user I get: /bin /usr/bin /usr/local/bin /usr/games /usr/lib/qt4/bin /usr/bin /opt/kde3/bin I then type: export PATH=$PATH:/opt and I get: Unknown command “export†If I su to root and run: export PATH=$PATH:/opt that is accepted but it changes roots PATH not mine. How in hell do I change my user PATH variable to include /opt??? NB I only want to do it on a per session basis not permanently.
  15. This from Microsoft Help and Support. Which effectively means that Fat 16 partition size limit is 2Gb without partitioning, not 4Gb.
  16. Nail on the head xboxboy. It can't be done properly any more and it is one of the reasons I am now an XFCE user not a KDE user. I even posted a bug about the the Device Notification Icon not working as I believe it should (ie like KDE3 storage media) and I was told (quite rudely I felt) that that is the way it is supposed to work and I would have to get used to it or go elsewhere - well, I wen't elsewhere :P .
  17. Ian Yes you are right I did it via the syslinux route. I'll have a look at that program you mentioned. EDIT: Just did have a look at it, that is fascinating, I have got to have a go with that. I think I will use an old machine though in case I screw up! Scarecrow. You are right I suppose, if it were on ext2 you would not be able to access it from a windows machine, but then again it is a bootable rescue medium so the implication is that if it is running then windows (or linux for that matter) won't be, therefore you won't be needing to access it. It is just that the thought of running Debian (that is what clonezilla is based on) on a FAT32 disk makes me shudder, in fact I am surprised it actually works, but it obviously does, I have done 4 images and 1 restore with it already, all perfect and certainly no slower than running from CD.
  18. Yesterday I decided to transfer my Clonezilla/SystemRescue CD onto a bootable USB key. Their website has a tutorial for that purpose and I simply had to adapt it to my circumstances and the result was successful. One thing struck me as strange about it though, the tutorial was very insistent on this so I followed their advice, but they didn't say why this should be, so I wondered if anyone here can enlighten me. Here is an extract from the tutorial: These instructions were Linux specific, not windows instructions that I adapted. I understand the reason for not having a journalling filesystem on a USB key like ext3, but why not ext2? In fact this morning, flushed with my success of yesterday, I decided to transfer Puppy Linux onto USB key as well (which was also successful btw). Their installer specifically recommended ext2 as opposed to any FAT file system, so why would the Clonezilla people advise otherwise?
  19. Neddie, I have just done an experiment with the code you suggested and I must say it worked faultlessly and instantaneously. There are only two problems with it. Firstly I didn't know it when I wanted it and secondly I will never remember it the next time I want it - so can I have your phone number :lol2: Seriously though, respect, if I carry on learning stuff like that I might become a cli lover!!
  20. Amazing! I didn't think my little post at the start would generate such an interesting discussion, but the subsequent posts have been most interesting. Thanks to everyone.
  21. I see what you are getting at neddie, but the point about it is (and I didn't say this in the original post because I thought it would just complicate it ) these fies were on a usb key so moving them was not as quick as you might think (there were 350Mb worth). Another thing I should perhaps make clear is that I have already done what I wanted to do, the point of this post was simply to learn if there was perhaps a better way to achieve what I wanted instead of the way I chose to do it.
  22. No, No, No, you have misunderstood me there Ian. Under no circumstances do I want to remove the files inside /B I only want to remove the folder itself - definitely not the files as well!
  23. Is there some clever command line way to remove a 'containing' folder without removing the files within it? Example - My directory structure is A/B/files, but what I want is A/files ie get rid of /B. The only way I know how to do it at the moment is to move '/files' from /B to /A then delete the folder /B. I presume this is the only way to do it? It is just that if /files is large it takes a long time to move them and I wondered if there was a better way? It would be a lot quicker to be able to just delete /B and have the files magically appear under /A. I have a feeling this isn't possible. :unsure:
  24. Obviously not just me then. Thanks for that.
  • Create New...