OpenSUSE Install :: Removing Alt Installed Kernel Safely
Oct 9, 2010
Hoping for some verification before I proceed.An alt kernel was installed side by side with the current mainstream kernel during an experimental NIC driver install. Unfortunately, since the experiment failed I would now like to remove all traces of the alt kernel since it was given a version ahead of the current main version and I would like to avoid all possibilities of contention should a future kernel upgrade use the experimental alt kernel's version number.
Failure to safely remove the USB with the following techniques: 1) umount /dev/sdd and I get the error "umount: /dev/sdd is not mounted (according to mtab)" 2) dolphin > right click the drive icon > safely remove: I get the error message "org.desktop.Hal.Device.Volume.UnknownFailure: Cannot open /media/.hal-mtab" 3) konqueror: sys:/info > click the drive eject button (nothing happens) 4) device notifier > click the drive eject button : I get a ERROR in Plasma Workspace that says "Could not unmount the device. One or more files on the device are open within an application" ... NOTE: this will happen on a fresh reboot with the folders of the USB never accessed, much less files being open on it.I have also noticed something similar when dealing with cds/dvds.... seems like I can only eject on a reboot.
These should be my last pleas for help with regard to Fedora 13. I've been unable to turn off the notifications that appear in the top right corner, despite a decent amount of searching on google. I can't remove any notifications package without removing a bunch of important software along with it. Also, F13 refuses to "Safely Remove" either of my external disks. I have to yank out the usb cord, touching wood each time.
I have a 32-bit laptop running a dual boot with Windows 7 and Ubuntu 10.09 LTS.I've decided that Ubuntu just isn't for me, and I want to remove the partition and restore the extra hard drive space back to Windows 7.
Now, a few months ago, I accidentally deleted my Ubuntu partition through Windows Disk Management, and I ended up not being able to boot up my computer. I can't remember what the exact cause was, but I think it was a problem with the GRUB, and I think I fixed it by reinstalling Ubuntu. Does anyone know how I can safely remove the Ubuntu partition without having to go through all this again?
Cannot safely remove Western Digital 2TB ext hdd. When I right click on drive to unmount, it says: "Unable to stop drive, This file cannot be stopped" Anyone know how to unmount, maybe using the terminal??
I've just installed Squeeze with KDE. I was wondering what is the best way to remove some unwanted apps without breaking everything (I want to get rid of Kopete and a few other apps like Dragon Player as I don't use them)? I tried to: apt-get remove kopete but it said it wanted to remove a whole bunch of other stuff as well. (I'm a recent Fedora convert).
I've been using Gnome for several years and haven't had any real problems with it. Now, however, I find the descriptions of what Gnome 3 and the Gnome Shell quite unsettling. That is, the Gnome devs have added a number of things I don't want, removed things I do want and made it impossible to configure Gnome 3 to work anywhere near what I want without adding unsupported third-party extensions. (Note: this is neither a complaint nor a flame; it's just a statement of my personal taste and any attempts to argue about it will be ignored.)
Currently, I have installed XFCE and am very happy with it on my two F14 boxes. I know that if and when I move to F15 (or F16 if 15 continues to be as problematic as it is so far) the upgrade will include Gnome 3, even though I don't use it. I'd like, therefore, to remove it but without removing any bits and pieces of it that are needed by whatever programs I'm using. What's the safest way to do this?
Let's assume I have a volume group (VG) with six physical volumens (PV) - sdb1, sdb2, sdb3, sdc1, sdc2, sdc3..I want to remove one of the PVs from the group in order to use its space elsewhere - how can I know if it's safe? How can I do that without losing data and without first "pvmove"ing it elsewhere?Reading a bit more, my guess is using the result of pvscan, but I thought I'd ask before removing keeping it safe as I'm not an LVM expert.
I currently have 2.6.31.8 installed on my netbook which causes problems, causing the netbook to freeze.
So, I downgraded to 2.6.31.5 and is working properly. Using Yast, I had marked 2.6.31.8 as do not install but after several days of use (by my kids) 2.6.31.8 mysteriously comes back and the system freeze again
How can I have 2.6.31.8 and 2.6.31.5 both installed on the same system so that I can avoid the trouble to manually reinstall 2.6.31.5?
I'm not sure if this is a bug in Squeeze beta 2 or if it's something I've overlooked. I have a Maxtor 250 GB external USB drive that I use for backups. It gets auto-mounted fine, always in the same place, and from my normal user account I can write to it, even delete directories on it if I want to. But when, from Gnome, I select the "Safely remove" option, I get an error to the effect that it can't stop the device. The weird thing is that the thing actually *is* unmounted. I've checked the mount point and it's no longer there.Is there some package I maybe should've installed but haven't? I'm not really worried about data loss, since I'm sure the drive wouldn't unmount unless it was properly synched; it's just the error message that bugs me.
I have a nightly scheduled script which creates a $vhostname directory under /mnt, mounts a windows box pointing to /mnt/$vhostname then rsyncs (pulls) some files/folders from the mount point. After this, I want to unmount the drive and remove the /mnt/$vhostname directory. Problem is that removing the /mnt/$vhostname directory sometimes ends up deleting all the files on the source! Example of script (stripped out lots of superfluous stuff):
It seems that my umount line isn't disconnecting the mount, leaving the following line to literally delete all directories, recursively. Is there a way of safely just deleting the directory (ie: mount link) without linux accidentally trashing the whole source?
In attempting to install Opensuse 11.X, I have repeatedly encountered a warning I am not sure how to get past safely. The systems I wish to dual-boot Opensuse with will either be primarily Vista, Win 7, or XP, all of which will hopefully also have a third boot option for Windows Server 2008. If there are suggestions of which order to install these operating systems, but I understand if no one wants to waste this thread simply discussing that. When installing Opensuse over a Vista installation, it comes to a point where it finds the previously used partition, which is one a single HD laptop. It will warn, no matter which direction I try to go, that I will lose the entire partition.
This is the step I wish assistance with, as it seems to happen with any option chosen. Otherwise, I am aware that another partition could be created on this single drive, from within Vista, and that one could be chosen during Opensuse installation. I have understanding of the MBR. If someone was to make a reply and mentioned what they know would occur to the MBR, if I chose to install Opensuse to a separate empty partition than the one Windows is using, it would be helpful. A step by step explanation of which option to choose, when all options I've tried keep telling me that the partition will be lost, If someone knows a separate page that lists steps to take at that point of the Opensuse installation, designed to help those that are warned that the partition will be lost, it would be good to mention for novice users like me.
I was hoping that downloading and burning the installation disc would be half the battle for an experienced OS user of 15 years, but it wasn't. I am getting in to Opensuse because it is the alternate OS of choice for IBM, my future dream employer, as I get closer to a Computer Science degree and begin to learn programming. All systems that will use Opensuse will be experimental, and never mission critical, in my education.
Ages ago I installed Linux on a "spare" 40GB disk and I don't remember how, but that disk is where I still boot the computer from, in Bios it's listed as a primary master and HD0.
Over the time my installs moved to the "main" disk where it is now Suse 11.3 alongside Windows.
I want to get rid of that original "spare" disk altogether, physically take it out, but don't know how to move the bootloader to the "main" one.
I'm confused by all the options offered in Yast Boot Loader Location menu.
Can I just tell it to put itself into a custom boot partition and point it to dev/sdb, the current designation of the "main" disk?
Would I need to edit Grub as well? I figure the current "sdb" would be called "sda" after I take the old disk out. Would it be safe to simply rename /sdb entries, things like /sdb4 to /sda4 and so on?
Additional question - I used to play with Win7 demo, deleted that now, but its loader still pops up when I boot into Windows with their "earlier version of operating system" menu. Their offered solution is to run "mbrfix" from a WinXp recovery CD.
My question - what would that mbrfix do to the Linux bootloader and how can I get it to point back to to Grub afterwards?
I am currently running the xen (64 bit) kernel, but want to move to the non xen kernel(64 bit) while retaining my carefully crafted system. I tried this once before by unticking the "virtualisation" and it removed the xen kernel, leaving me with nothing to boot from.
Hey,everyone! I've got Ubuntu 10.10 , when loading I see the following message: "atk: Resources not safely usable due to acpi_enforce_resources kernel parameter" What does it mean and do I need to fix it?
when I open virtualbox OSE and tried to run a vm i get this error
Code:
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing
'/etc/init.d/vboxdrv setup'
as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. So i tried doing what it said and I got this error when i tried to run /etc/init.d/vboxdrv setup (as root)
Code:
Stopping VirtualBox kernel module done Recompiling VirtualBox kernel module, NOT. It has been packaged.Recompiling VirtualBox
[code]....
Then i ran dmesg and there was a ton of stuff that seemed to be unreleated so i ran dmesg -c to clear it. then i ran the vboxdrv this again then checked dmesg again expecting there to be nothing but the vboxdrv stuff but it was still blank.I really dont know what to do at this point I tried uninstalling and reinstalling but that makes no difference
When I start up a virtual machine in Virtualbox on Suse 13.1 I see this message:Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing '/etc/init.d/vboxdrv setup'
as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
I have downloaded vbox from its site and installed it. I created a vm but when I try to start it, I get error: Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing: '/etc/init.d/vboxdrv setup' as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
And when I try 'sudo /etc/init.d/vboxdrv setup', I get: Stopping VirtualBox kernel modules done Uninstalling old VirtualBox DKMS kernel modules done Trying to register the VirtualBox kernel modules using DKMS failed (Failed, trying without DKMS) Recompiling VirtualBox kernel modules failed (Look at /var/log/vbox-install.log to find out what went wrong)
And this is /var/log/vbox-install.log: Makefile:159: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
I did an installation of SUSE 11.2 on a new SCSI hard drive. Keeping the old hard drive separate. I remembered there was some info on the old hard drive I wanted.
I added this to the system and mounted a partition. I then copied the data over. Then I umounted the partition rebooted the machine and removed the hard drive.
However the machine will now not boot without this hard drive even though its not mounted. Not sure what the error message im given means I think it could be trying to fchk it.
Do I need to do something more like remove /dev/sdd ?
I just got it all set up and it has everything I need for what i do on my computer and it does alot better and smoother. So now im convinced linux KDE is where the party is at! HAaha so I want to remove windows 7 from my notebook and have openSUSE as the only OS running on it. Can anybody help me with removing windows 7 and leaving openSUSE on it? I was also hopeing that i'll be able to use the disk space with opensuse that my windows 7 is currently useing.
after removing some programs I'm not able to login (I'm using an other computer now). I'm using opensuse 11.4the boot screen has changed from the normal to a grey one. before login following messages came up:
I'm planning to replace kde with gnome so my plan is to visit Yast pattern view check Gnome Desktopand Gnome Base System then unchecking Kde4 Desktop and Kde base system.i'm seeking stability I know openSUSE has it but no with kde.is this the right way to replace my desktop environment , I will not download the gnome iso and make a new installation
I've reached the point where I rarely need to boot into my physical WinXP install, which is a total mess right now as well ... so I've decided that I want to completely remove it from my system, then create a virtual install of Vista Business Edition.
A few days ago yast did update my computer to a new kernel-desktop 2.6.31.12-0.1.1.
My mainboard is an ASUS P4P800-VM with Intel ICH5 chipset. This new kernel is not able, to poweroff my computer. Older kernels were able to poweroff the computer.
How can I roll back to the older kernel? Yast does only offer the recent kernel.
In /boot there are only files of the recent kernel.
ASUS P4P800 Intel Pentium 4 HT, 3000 MHz, Frontside 800 MHz/Cache 1 MB 3 GB Ram AGP nVidia 7600GS/512 MB, nVidia driver 190.53, installed from yast. PCI WLan TP-Link 951N (Atheros chipset, WLan N, driver ath9 was automatically installed)
I have a Windows 7 OS installed as my main OS, it installed on its own HDD with 3 other data storage drives.
On my 5th drive I installed a copy of OpenSUSE 11.02 to see if I like it. I have decided I don't wish to keep it so I reformatted the drive while in Win7. Of course on restart I got the Grub 1.5 Error 22. All my HDD's are seperate and there are no partitions.
I have had to reinstall OpenSUSE just to get my PC to boot.
All I want to is remove OpenSUSE from my computer without losing my Win 7 install.
My Win 7 install disc fails to recognise my Win 7 so I can not get the recovery command prompt/repair options.
Can someone explain in say 5 simple steps to get back my original MBR so I can boot straight to Windows as I can't seem to find a guide that actually explains what to do. Either by doing it in OpenSUSE 11.02 or Windows 7 Ultimate 64-bit.
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
'/etc/init.d/vboxdrv setup'
as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. I've dkms installed and did a reboot as well.
I can see this error occurring in multiple past versions of suse. The answer seems to involve recompiling the open source version of VBox, but this is surely overkill. Isn't there a way to either a)get the right kernel version of VBox for 11.3 or b)set whatever permissions are required.
In all the answer so far I can't see a solution I can understand for these combinations, sues 11.3 and VBox 3.2.8. The error is consistent, and if the install doesn't work properly (it took my a few attempts even to install it without error messages) then surely its an issue either for Oracle or Suse? It runs ok but hwen trying to fire up a newly created XP VM this error message occurs trying to switch from W764bit to suse11.3 64bit
I am eagerly awaiting my newly purchased lenovo sl510 and once received intend on loading opensuse 11.3 onto it as my primary os. I understand this particular laptop has had some issues with acpi.
Can anyone comment on how this is now with newer kernel releases since the default installed with the opensuse 11.3 DVD.
