Tag Info

Hot answers tagged

4

I had EXACTLY the same problem with NVIDIA drivers. Your problem probably is related to these bugs (they all have the same symptoms): https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762 http://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314871 Unfortunately it is ...


4

I worked out a solution myself: Quick answer Assuming that your drive is /dev/sdX: Run dd if=/dev/zero | cmp - /dev/sdX to spot the first non-zero byte of the device: in my case it was byte 742300476649 Calculate to which block does the first non-zero byte belong to: ...


3

Chrome 40.0.2214.93-1 was released and the problem seems to be gone much better now. Similar symptoms still occur some times but much less frequently. It seems that this problem only affected started with the 40.0.2214.91-1 release. So if you're running that version do sudo apt-get update && sudo apt-get upgrade to update to a more current version.


3

Got the same issue ever after the Chrome 40.0.2214.91 release, and though I haven't tried the .93, I can at least confirm the issue is 100% gone in Chrome 41 Beta. Strongly considering sticking to the beta until 41 becomes stable, or at least until it's 100% confirmed a point release fixed the issue.


2

As you're familiar with Ctrl+Alt+F1, I suppose you're more technical then the reputation 1 you have here would suggest... The standard Ubuntu NVidia drivers generate some problems on slightly older and slightly newer NVidia hardware. If you want more then the standard Ubuntu repository drivers, install the xorg.edgers PPA. As the xorg.edgers group ask not ...


2

According to this bug report I solved it adding following lines vm.dirty_background_ratio = 5 vm.dirty_ratio = 10 into /etc/sysctl.conf and running sudo sysctl -p


2

According to your dmesg output there's a bug in the WiFi driver. Let's take a closer look: the most recent wakeup event is at [22500.127146] ACPI: Waking up from system sleep state S3 and the wakeup finishes ~5 s later: [22505.833530] PM: Finishing wakeup. The system then takes another ~5s to re-initiate the PS/2 interface (for keyboard and touch ...


2

I had similar behaviour in 14.04: freezing screen and need to log-in after alt-tab. not always, but frequently enough to be annoying. Seems to be solved now: Installed compiz config Under 'desktop', swithed off the Ubuntu Unity Plugin, directly re-enabled this plugin Compiz now complained about a conflict ('Show desktop plug-in', if I rembember well) and ...


2

The standard Ubuntu Nvidia drivers generate some problems on slightly older and slightly newer Nvidia hardware. If you want more then the standard Ubuntu repository drivers, install the xorg.edgers PPA. As the xorg.edgers group ask not to give installation instructions directly without linking to their page, this is the best I can do. If you don't know ...


2

I suggest you remove all the instances you mention above. The correct way is: sudo -i echo "options forcedeth msi=0 msix=0" > /etc/modprobe.d/forcedeth.conf exit Upon reboot, the parameters will be applied. Whether they fix your exact issue is another question.


2

Maybe light locker is installed on his system. Try uninstalling light locker if so: sudo apt-get remove light-locker And install xscreen saver instead of it: sudo apt-get install xscreensaver xscreensaver-gl-extra xscreensaver-data-extra See here for more info: Ubuntu forums


2

Press Alt+PrtSc and while holding on these two keys type REISUB. for more information you can found you answer here.


1

The cause was indeed a specific add-on. In my case it was an add-on called MEGA which supported downloads from the MEGA cloud drive service. I suspect the reason is the change of the URL.


1

This is not because of Ubuntu or windows, it's because your HDD has some bad sectors, try to run a HDD test app like HDD Scan 3.3 to test it, then after you find the bad sectors use and app Like HDD Regenerator(free) to fix it. if the bad sector is unrepairable, you can try to cut the part of HDD that has it, Make it unallocated. If all the above doesn't ...


1

If the DE has frozen, switch to a different run-level by using ctrl-alt-f3 and login to the terminal presented. You can kill any offending processes by using kill or killall, if the DE has gone into hardlock it may be worthwhile to kill xorg by sudo killall Xorg to restart the DE (usually drops you back to the DM to login),switch back to the graphic ...


1

After reporting my issue on the Xorg and the Linux kernel Bugzilla, I was invited to test a kernel patch (this is the patch, posted for this bug). After compiling and installing the patched kernel, the problem looks gone, and the dynamic turn on/off of the discrete graphic card is working again. I have to thanks kernel developers for pointing me to the ...


1

You are using an open source "radeon" driver for your video adapter. It may not perform well. I suggest installing a proprietary AMD driver. You can do it by running in terminal sudo apt-get install fglrx and reboot. Same task can be done in GUI. You can go to System Settings -> Software & Updates -> Additional Drivers and find there drivers for ...


1

Looks to me like you have a problem with your disk drive sda1. It's formatted as an ext4 file system and the file system is spitting out errors. Probably one way of fixing it would be by copying as much data as you can from the drive and then discarding the drive and putting the data on another one. Expensive and time-consuming. You can try other things, ...


1

Probably some sort of hardware incompatibility with some versions/distros. You could try searching for your exact laptop & someone else might already know what will work for it, but I think it might be a boot option... Tried some boot options that might help? The live iso has some listed under it's F6 "Other Options" menu. Like nomodeset, noacpi, ...


1

So after 1,5 years of testing it seems I've finally solved this problem. All it took was sheding some light into the issue. Literally. This is what I was only able to see after putting some bright, direct light into my PCIe slot: I'm guessing this happened when I first inserted my video card into that slot. The card may have pushed a couple of pins ...


1

Your video card drivers version should be 340.46. I am sure you can open nviida-settings and check out version, and also adjust all related power-management fields in nvidia-settings. In Kubuntu default power management, make sure you check your settings for all of the 3 sections present in there, namely AC POWER, ON BATTERY, ON LOW BATTERY. Disable Dim ...


1

This solved for me: sudo su apt-get update apt-get install --reinstall ubuntu-desktop apt-get install --reinstall unity apt-get remove --purge nvidia* apt-get install nvidia-current reboot


1

By any chance, are you using a touch pad? If so, changing the touch pad to work as a normal usb mouse will correct issues with a 'unresponsive screen.' Unfortunately, you will not be allowed to use the tap to click feature or scroll using the pad.


1

This is a known bug. Fortunately, there is a fix now (but you'll need to compile packages yourself). See https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1220426.


1

Three possible problems: Memory HD controller (or driver) HD itself. Two possible solutions: As grub is still working, do the MemTest86+ Take the HD out of the computer, (that way you bypass the HD controller + driver) put it in an enclosure and hook it up to someone elses Linux PC and run fsck without mounting the drive! If you need exact commands, ...


1

When the grub menu loads (you need to hold shift after the bios screen), I select my kernel image and press 'e' to edit the boot parameters. At the end of the line beginning with "Linux" I append the option "i915.modeset=0". Turns out I can omit the "xforcevesa" option.


1

When you chroot into your system, regenerate your initial RAM-disk. It is likely that modules are missing causing this problem to occur. update-initramfs -k all -c Before chrooting, mount /dev, /proc and /sys inside chroot: mount -t proc /proc /mnt/proc mount -o bind /dev /mnt/dev mount -o bind /sys /mnt/sys I'm assuming here that you mounted your ...


1

You can check whether you are hit by this bug. In my case it helped to inactivate the virtual keyboard "Onboard".


1

Deleting the .config/chromium folder and seems to have solved the issue.



Only top voted, non community-wiki answers of a minimum length are eligible