using mint 10, now after updates my system is barely working. The programs were no longer showing in the task bar, and the system was running much slower.
This repeated over and over again. My temperature was never to high 40-55, and I found a suggestion to update my kernel to 2.6.37-020637. After doing so there is no longer the thermal limit exceeded error but the computer is still running poorly. The system is slow and again no programs are showing up in the task bar when open.
opensuse 11.2 ,my monitor keeps going to sleep or somthing and this is a problem when im watching videos,ive set screens power setting but they dont seem to be whats doing it.im running a nvidia gtx260 and have installed nvidia drivers for series 6 and up.dont know if its the divers or somthing else.
Basically everything was going fine, and i was enjoying the OpenSuse experience, then downloaded djl (Games Launcher) , installed some games and found that i had a very very very bad frame rate (about 1FPS), and my GPU is a NVIDIA GTS250 (1GB), and runs most games flawlessly under m$, so i went about installing the graphics drivers for my card. I followed the instructions and was under the assumption that i installed the correct ones, but now i cannot boot into any graphical interface. I think that it should be a graphics issue, as this was one of the few things done before rebooting. I have tried booting into the normal mode, and the failsafe, I have read many other "Not booting'' posts, and have tried their solutions without success, there include: Changing the boot parameters Logging in and manually trying to boot up the gui (init 3.... init 5... etc)
When the computer tries to load up OpenSuse in normal mode, it comes up with the normal loading screen, and then about 90% of the way it stops for about 30 seconds, and then switches over to a CLI, asking for a login, going through the log a couple of things fail, did have these noted down (but cannot find and will post along with other commands that i am asked to do) I want to try and avoid a reinstall as it took me a long time to get the WiFi card working.
since the last SuSE online update (last Wednesday?) the X server no longer starts on our notebook (ATI HD 4200) so we only have the consoles available, which limits the WAF heavily . We were using SuSE 11.3 with the Gnome desktop for about one months and it worked smoothly, but since the update (which included a kernel update to 220.127.116.11-0.7) the X server tries to start 5 times and then gives up. All logfiles end with:
Code: ... [ 13.899] Segmentation fault at address 0x3c [ 13.899] Fatal server error:
I used the ati driver ati-fglrxG02-kmp-desktop, version 8.762_k18.104.22.168_12-31.1 from the ATI Suse repository. To solve the problem I already switched to the Xorg driver which lead to a color distorted display but no segmentation fault. But I'd like to get the ati driver running again.
I was using tripleboot system in one hard drive. That included Windows 7,Ubuntu 10.10 and Ubuntu 11.04. And yesterday I decided to added openSUSE 11.3 at another partition. I'm using Ubuntu 11.04 grub2 as bootloader.
At first there was no problem. All OS detected well, but after opeSUSE online updates last night my openSUSE partition won't boot. First, at boot I chose openSUSE and it said "Boot kernel first" and nothing happens. And then I boot to ubuntu and ran update-grub then I saw grub no longer detected openSUSE partition.
Lappy is a Dell XPS M1330 Intel core 2 T7500 2.2Ghz 4gig Ram Nvidia GeForce 8400M GS HDD 320
1 64bit system installs but wont let me do updates so now using 32bit thats ok 2 How do I update drivers? My screen seems to have ghosting around the edges
3 On firefox when scrolling down the page its jerky Ive used firefox on most of my Pcs and never had this problem Im duel booting ubuntu and suse and using the internet on ubuntu so far other than these problems suse is fine
Prior to updating suse was running slow. The desktop would act "weird" . It started after an update on 11.3. thought updating to 11.4 would fix everything. Last night Dled a copy of Suse 11.4 burned, checked for errors and did an update. Everything worked fine and booted to desktop. Nice shiny and new, was very happy for about a minute
Currently I get a terminal login screen when trying to boot Desktop, or failsafe ( network doesn't work on either of these 2). Xen will boot to desktop but toolbar is gone. Hit alt f2 to launch apps ( terminal, firefox, yast) and none show on screen. If I hit alt tab they show up in list.
With zen I hit CTRL+ALT+f2 and did zypper up thinking that would fix the problem. Updated successfully but same problem. Have a Nvidia 7950GTX so I selected zen, did ctrl-alt-f2 again. Launched yast, added the nvidia.com 11.4 repo and installed the 68xx newer driver. ran nvidia-xconfig and still it wouldn't boot to GUI. loaded zen again c-a-f2 - > yast found a second nvidia 68xxnewer driver, installed and now have 6 options to select at startup. 2 desktop, 2 failsafe, 2 xen.
Picked the first one and suse loaded. Yay. Ran nvidia settings to fix resolution, saved. Weird thing was only 2 of the desktops backgrounds would change, other 2 were white. Audio didn't work, usually a reboot fixes the problem so I rebooted and am back to none working except the xen login that gives me a crippled desktop ( can launch programs but none show up).
At first startup after update to 11.4 desktop backgrounds were changing really fast. Right clicked desktop went to click on desktop settings and that's when the tool bar down below disappeared ( it was working prior to that). That is when the desktop became crippled. Second tool bar at top from previous install is still there and can launch folders to open but none show on screen but show in alt - tab.
This morning, I authorized an update as almost every day. I saw that the nvidia driver was on the list but in recent years, I no longer fear these driver updates since everything usually works well...
Except that this time, no! I turn on my pc this afternoon and more 3d effects. I run "Nvidia X Server Settings" which tells me I do not use the nvidia driver and must run as root the command "nvidia-xconfig," what I do. I restart X and no display at all, only the prompt in text mode!
Has anyone tried updating dbus in factory up to level 1.4 under openSuSE 11.3 x86_64 and continue to run KDE 4.4.4 Stable? Just wondering if it causes any issues or if it forces you to go to KDE 4.5.1 Factory. I've tried updating to 4.5.1 without, other thread, and the suggestion was to update dbus to 1.4 to correct speed issues.
I played the apprentice sorcerer trying to install mysql workbench by my own and I messed up the system 11.1 by removing accidentally some libraries and decided to jump on 11.4 by using the update feature from the DVD. It worked all good (it seems at least: I didn't lost any datas and all my servers are running ok) but there is no more X11 server (kde) running for the run level 5.
I checked the inittab file and it is set to 5. I can log on root account and now I'm searching how to install kde on this new 11.4 system. I didn't yet tried the failsafe option at boot. Is there a way to set up kde from the internet, my wifi connection is ok ? I saw that yast was not installed nore zypper nore yum. Do I first try another update to fix it (if possible) from DVD?
In OpenSuSE 11.2 YaST -> Online Update Configuration I can configure how often the system should check for updates (i.e. daily, weekly). Does this operate independently from the Online Update Applet(kupdateapplet)? The reason I ask is that the Applet doesn't always seem to work correctly. However, if the system will check for online updates automatically regardless of the Applet, perhaps this isn't an issue. If I can avoid messing with the Applet, that would be great.
Observed on two host systems both with openSUSE 11.3 32 bit using ext4: When a big files, in this case a 1.2 GB and a 1.7 GB is copied from DVD, usb harddrive or shared folder into a Windows 7 32 bit guest system, the copied file is corrupted. The md5sum has changed and until the guest system has been rebooted successive md5sum tests on the same file comes up with various results... After a reboot md5sum tests show consistent results, but a sum different from the original file.
I have been using SDB:NVIDIA_the_hard_way and have run into a problem. When I run the script, it gives me the following error message: You appear to be running an X server; please exit X before installing
I had, with much delight, accomplished a dual boot install of Ubuntu 9.1.0 and Windows 7 the other day and everything was working perfectly fine. However, I decided to activate the proprietary Nvidia drivers that were available in the drivers menu and my system subsequently no longer operates. After installing and rebooting Ubuntu will no longer work and becomes stuck on a black screen with two white dashes in the top right had of the screen.
This hang up occurs directly after the first white Ubuntu logo appears during the startup and the only key that will work during this screen are Crtl + Alt + F1, which only bring up a second black screen except with a solid white dash in the top right screen. At that point no key will work. I have tried to fix things in recovery mode and used envyng to remove the nvidia drivers as well as other operations, however the same result still appears when I try and run Ubuntu. I own a Sony Vaio Z690C if it makes any difference.
I made a fresh installation of Ubuntu 10.10 (64 bit) on a Sony PCG-81112M, the graphic cards is identified by lspci as "nVidia Corporation GT216 [GeForce FT 330M]". Quite frequently everything but the mouse pointer freezed on the screen, I found no way to recover from these situations but to restart the computer using the power button.
I decided to install the proprietary driver (as this is the recommended driver, I was confident this would solve the problem). As a consequence the system now hangs on boot after showing the Ubuntu 10.10 inial logo/text. I could start in recovery mode, but I'm not sure to which driver I should try to change to. I really need no fancy 3d stuff, just a robust computer to which I can attach and detach an external screen.
I've been trying to get a converted virtual disk running in VirtualBox for the past several days. The VM begins to boot in a window but never gets past a black field. Until today the title bar would always change from "running" to "suspended" and just hang there. Now it just keeps saying "running" but never boots so I'm thinking the virtual disk may have become corrupted from repeated shutdowns without ever booting.
The User Manual at VirtualBox.org is of little help since it appears to assume you're using their packages. They also make references to utilities or scripts like "/etc/init.d/vboxdrv" that aren't even in the latest version so I think it hasn't been updated in a while.
There doesn't appear to be many hints in the Vbox.log either - couldn't find a way to get more verbose logging. Until now I'd get to this point and it wouldn't change until I shut it down:
I'm guessing the reason for the suspension was the message immediately above the notice. Now I just see the "unmapped device" message and the guest window says "running" indefinitely. I've attached copies of logs from a couple of sessions, one where it suspends itself (a vnc session) and another where it just stays running (a console session). Some googling suggested that the "unmapped device" message implies it can't find the boot drive or the boot sector on the virtual disk.
The host is normally accessed through a VNC session to a virtual console but VBox log messages indicate that it cannot determine the keyboard type when accessed this way so I now have to physically sit at the native console. If anyone knows of a way to overcome this limitation I'm all ears.
People don't usually respond to my threads so I'm basically talking to myself outloud here. I'll read it again later an maybe come up with something else to try. For now I'm going to remove all the VBox packages and re-install them, starting from scratch. If that doesn't get it working I'll delete the converted virtual disk and re-convert it from the original. If I still can't get VBox working after that I'll be forced to install VMware Server (resource hog). I'm getting desperate now...
[Background] Until a few weeks ago we were happily using qemu-kvm but encountered a bug when using the "-smb" argument after updating the host from Fedora 9 to 12. (re: F12: qemu-kvm with -smb hangs then dies) In an attempt to get our virtualized MS Windows Server 2003 back up and running I installed VirtualBox-OSE-3.0.10-1.fc12.x86_64 and friends over the Christmas break. I converted the qemu qcow2 image to raw then to vdi format using qemu-img and VBoxManage tools. There were no errors during the install of VirtualBox. In the beginning Bug Buddy notified of a crash whenever we started up VBox but after some digging and experimenting I believe the crashes were caused by running VBox in a VNC session instead of at the console. I haven't seen a crash when starting it in a native console session. Unfortunately, this means I can do very little remotely.
I decided to take centos 5.5 for a testdrive. I download the live cd iso and attempted to boot the system via virtualbox on my mac os 10 system. I get the blue boot screen and choosing either the graphical boot or text boot gets me no where, the blue screen remains and nothing happens). Virtualbox is able to boot other linux systems fine so I am not sure if this is a centos issue or centos/virtualbox issue.
I have the nvidia 121.21 file for XP and Win2K. I have the driver running on this box on a dual boot win2k install. works fine. The same file on my guest win2k VirtualBox install says no driver available for my current hardware setup. My video card has the 8400 GS chip set. It is currently running 3D on This Fedora 12 install. Is the problem the VirtualBox will not allow the 3D driver to be installed. The installation had a comment about no 3D when it started. I also have not been able to get control of a USB port Device I need. There any way to have Virtual and 3D video drivers with a USB port?
I have 13.1 on its own drive and works fine. I installed virtualbox in 64b windoz on a different drive with the same computer so I can play with all the different linux systems. Around 6 weeks ago I installed slack current from alien bobs mirror with no problems. An update a week ago? and kde would not work. KDE failsafe and all other desktops work fine.
I recently installed debian testing, amd64, on my box and I am running the xfce desktop. When I login, I always get a bubble popup telling me that virtualbox is not running. Is it something I should be worried about? I use only Linux on my machine.
I currently run VNC with Gnome to run VirtualBox for my VPS's, but the problem I'm facing is that occasionally, the VNC session will die.
Ubuntu - 11.04 Server Edition.
I mean, randomly just die and then through up an error (specially connection refused 10061). The problem caused by this is that after I reset the VNC session, VirtualBox will have stopped and in turn the VPS's.
Is there any way I could run VirtualBox without being dependent on VNC + Gnome? Or at least, beable to stop VNC is dying on me?
If you require any more information, just ask and I'll reply within 5 minutes.
I am running Debian Squeeze with 2.6.32-5 amd64 kernel with GCC 4.3.5 (the same one used to build the kernel) installed. I have a nVidia GTX 470. I'm trying to install the latest nVidia drivers (260. ...). I've never installed noveau or any other open source nVidia driver. Here's what I've been doing:-Change the "Driver "nvidia"" line in /etc/X11/xorg.conf to "Driver "vesa""-Restart system in single user mode as root, no services running-cd to the directory with nvidia-Linux-x86_64-... .run (what I'll call nvidia.run)-enter "sh nvidia.run --uninstall"-enter "CC="/usr/bin/gcc-4.3" && sh nvidia.run"It starts up and it compiles the kernel 100%. Then it says this:
ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most frequently when this kernel module was built against the wrong or improperly configured kernel sources, with a version of gcc that differs
First I wanted to install the proprietary software Virtualbox-PURE cuz there is usb support, I need.
Added the Repository and installed it (virtualbox-4.0) and dkms. Here is my sources.list $ cat /etc/apt/sources.list # Debian Hauptrepos deb [URL] squeeze main contrib non-free
# Debian Update-Repos deb [URL] main contrib non-free .....
The result of all is: virtualbox is still not running. I use experimental branch flash is not working now. flashplugin was installed, I restarted my browsers, not working. I tested it with opera, chromium and iceweasel.
My questions are: How I ever can go back to stable? How can I make virtualbox run? How can I make flash run?
I'm using debian squeeze with gnome 2.30.5. When you need more infos or results of commands I give it to you. 2 days of work and nothing is running.