New answers tagged

0

Finally, I got the solution and now the system works fine. Reboot the system by typing reboot command Choose an Ubuntu recovery mode while startup if a faulty disk is shown in error messages like /dev/sda1 or something, just run the command fsck /dev/sda1 -y, here /dev/sda1 is faulty disk in my system, you might have an error with some other disk. Now, ...


0

I solved the same problem, I'll try to explain below what I did. First use $ sudo apt-get remove virtualbox $ sudo apt-get remove virtualbox-dkms Next step: open bios setup, and security boot should be disabled. Then install VirtualBox again via the terminal.


1

The easiest way I find to report bugs is ubuntu-bug <package> (which does assume you know the package, but because you believe it's a kernel issue you already have that), refer https://help.ubuntu.com/community/ReportingBugs. See the "Reporting a crash in the stable release" section (or search for ubuntu-bug). This is a support site, and bugs belong ...


0

I know it's a little late to reply but I hope this is helpful for friends. “mice” contains mouse input data, but to find the file related to the keyboards we need to check the files in folder “by-path”, keyboards file names end with “event-kbd”. We need to find the links to the keyboards, and then we can find the keyboards event file. The following commands ...


0

I have edited the file systemd-tempfiles-clean.timer and changed the OnUnitActiveSec=1d to 60d That should do until I find what's in the temp files that makes the Ubuntu to hang.


0

It may be worth checking to see where the bottle neck is with perf. Install with: sudo apt-get install linux-tools Record events, say for 20 seconds at 1000 samples per second: sudo perf record -a -F 1000 sleep 20 ..and see where the bottle neck is occurring: sudo perf report Refer to https://perf.wiki.kernel.org/index.php/Tutorial for more details ...


0

I have got the similar issue. After reboot my VirtualBox machine. It won't boot to GUI but the terminal in "emergency mode". It just can't go into default mode. I have got 5.0.0.25 and 5.0.0.23, both doing the same thing. I have got the problem solved. It appears that the attached USB devices (bluetooth and external HD) and their relevant settings are ...


0

For me, re-binding the USB bus is helpful for Dell Venue 11 on the kernel 5.2.0-8.2-liquorix-amd64 (on 4.15.0-58-generic the touchpad operates normally). If somthing wrong, computer can loose interface (!!!) if there are no alternative input devices (ps/2, touchscreen). Please, use it at your own risk! To find the proper kernel module, run lspci -k. Find ...


2

1) how can I clean up these media controller devices (device controller nodes) manually (ideally from terminal) in a proper way? You can remove all you want in /dev/ but on the next reboot it is all recreated. Basically that is how Linux can get away with a system that is as universal as possible: those /dev/ entries are created on the fly and as needed by ...


0

Writing to /proc/sysrq-trigger won't work due to the restriction.Press Alt-Sysrq-x on an attached keyboard.


0

@enzotib's answer didn't work for me, but one of the packages which include the kernel version is bound to get the correct report. You can use this to figure out which one works: $ dpkg -l | awk "\$2 ~ /$(uname -r)/ { print \$2 }" | xargs -n1 -t apt changelog And in my case all except linux-image-${version}-generic worked. $ dpkg -l | awk "\$2 ~ /$(...


1

From the comments... I strongly suspect that your problem booting with the 5.x.x kernels is due to you possibly having an older BIOS that needs updating. Boot to the 4.18.0-25 kernel, and in the terminal type sudo dmidecode -s bios-version to get the current BIOS version. Then go to the Acer web site and see if there's a newer BIOS for your computer. ...


0

On my PC it was due to a missing package, the reason being that the guide instructs to run: sudo apt-get install libncurses-dev flex bison openssl-dev libssl-dev dkms libelf-dev which fails because the package "openssl-dev" does not exist on recent versions of Ubuntu, and then none of the packages get installed. Therefore you need to run the command ...


0

The kernel you mis is on your system. linux-image-4.15.0-55-generic 4.15.0-55.60 amd64 Signed kernel image generic sudo update-grub Then reboot. Change boot device in Bios so the harddrive of bionic installation is the 1. Device. Or boot xenial and run sudo update-grub where.


2

Byobu is the program containing the script purge-old-kernels (it was taken from earlier program bikeshed) According to Byobu maintainer Dustin Kirkland: purge-old-kernels has been deprecated, in favor of "apt autoremove". If you have problems, please file bugs against apt. (2017-04-27 https://bugs.launchpad.net/byobu/+bug/1646276) Which is a similar ...


2

I had disabled Intel SpeedStep® Technology in the BIOS, which was preventing the CPU from switching power states. Enabling it brought the kernel load time to about 3 seconds.


2

How can I troubleshoot this? The first step is to find out what PCI device is generating the error: pcieport 0000:04:00.0: Refused to change power state, currently in D3 My system doesn't have a 0000:04:00.0 but it does have 0000:03:00.0 so I would use: $ cd /sys/bus/pci/devices/0000:03:00.0 $ ls -la total 0 drwxr-xr-x 5 root root 0 Aug 8 17:15 . ...


3

Enable HWE or the Hardware Enablement Stack DESKTOP sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 SERVER sudo apt-get install --install-recommends linux-generic-hwe-18.04 source: https://wiki.ubuntu.com/Kernel/LTSEnablementStack fyi: If you install Ubuntu 18.04 using 18.04.2 or later ISOs, the HWE kernel ...


0

No need to enable CSM Legacy BIOS Support on your J3455 Apollo Lake motherboard or manually rebuild installation images anymore Format your USB key with GPT partition table, create a FAT filesystem on it, then burn 64bit Ubuntu onto a USB key with Unetbootin. In my case i used 19.04 Server alternative iso. https://ubuntu.com/download/server -> alternative ...


0

Please check with this link https://github.com/moby/moby/issues/33689 if you don't find it helpful then check with the fresh installation steps(please consider as it is written, you have to add docker repo not docker ubuntu16.04 repo , it had worked for me) Add gpg key Add docker repository to the APT sources Update your system apt-cache policy docker-...


0

You can simply check the missing symbols in dmesg using dmesg | tail. If you want to check if the symbols are actually in your symbol table, check using cat /proc/kallsyms | grep <function_name> Similar issue: https://ubuntuforums.org/showthread.php?t=1360950


1

You need to purge and reinstall VirtualBox. Back up your virtual machines somewhere safe. Purge Virtualbox: $ sudo apt purge virtualbox* Get rid of old deps and configs: $ sudo apt autoremove $ sudo apt autoclean Install a shiny new VBox There are two options for installing VBox. From standard repos (Option 1) or from a PPA (Option 2). Do one or the ...


0

I'm similar to you mate, but I am running 5.2.5 (haven't installed 5.2.6 yet) on Ubuntu. Ukuu is a great tool for installing up-to-date kernels, can be installed as follows. sudo add-apt-repository ppa:teejee2008/ppa sudo apt-get update && sudo apt-get install ukuu


1

Even without considering manually installed kernels, a Ubuntu 18.04 LTS system can be in one of three kernel "families": General Availability: The metapackage installed is linux-generic or linux-lowlatency. As of this writing, the kernel version is 4.15.0-55-generic for the first option. HWE: The metapackage installed is linux-generic-hwe-18.04 or linux-...


1

Ubuntu 18.04 LTS (installed via Ubuntu 18.04 LTS or Ubuntu 18.04.1 LTS ISOs/media) came with the 4.15 kernel, with the option to use the HWE kernel when it came out. Ubuntu 18.04 LTS installed with 18.04.2 or later ISOs/media (or prior installations with HWE kernel option enabled) use the 18.10, 19.04, 19.10 and 20.04 kernels so which kernel depends on ...


16

From the article About WSL 2 of Microsoft Docs: Brief overview of the WSL 2 architecture WSL 2 uses the latest and greatest in virtualization technology to run its Linux kernel inside of a lightweight utility virtual machine (VM). However, WSL 2 will NOT be a traditional VM experience. A traditional VM experience can be slow to boot up, is ...


1

It seems that graphics off functionality is not working properly (see phoronix forum). Usage of kernel parameter amdgpu.ppfeaturemask=0xffff3fff fixed the issue for me.


0

If you want non-HWE kernels you should install either Lubuntu 18.04 or Lubuntu 18.04.1. All ISO's from .2 onwards have HWE enabled by default (I, along with others are in the process of QA-testing the .3 ISO currently, it should be released Thursday 8 August 2019 though will use the HWE kernel too). You can sudo apt full-upgrade either 18.04/18.04.1 or 18....


0

This screenshot shows a test system of mine running the 5.0.0-23 kernel. It has an Nvidia GeForce 8200M card and is running the 340.107 driver from the graphics ppa. (This happens to be a 19.04 system, but it's running the same kernel as the new one in 18.04 LTS HWE. It's a 64 bit Ubuntu system with the LXDE desktop installed.)


1

Yeah, NVIDA binary drivers will need to be updated to a version that supports kernel 5. Check out this thread for more information and some solutions, most of which are to boot back to your previous working kernel. https://www.reddit.com/r/linux_gaming/comments/ax3msr/beware_of_kernel_50_nvidia/ You can do this easily following these instructions: https://...


0

According to [Redhat's Knowledgebase][1] for RHEL6, updated January 2017, "please specify mtrr_gran_size/mtrr_chunk_size" means: These messages are not a problem and are simply warnings. They can be ignored. Adding disable_mtrr_cleanup disable_mtrr_trim to the kernel parameters in /boot/grub/grub.conf will disable the code path that initiates ...


0

I did have internet access but DNS was somehow misconfigured. I was able to reconfigure it as described here with sudo dpkg-reconfigure resolvconf I was then able to follow the instructions here for reinstalling nvidia drivers. My home directory was available from a user login.


0

The kernel ring buffer is line buffered, which means it's not flushed until it encounters a newline. Add a \n to the end of your printk strings: printk(KERN_INFO "Hello, world - this is the kernel speaking\n"); You also might consider using the printk formatting macros, as I believe these are preferred over specifying KERN_INFO directly: pr_info("Hello, ...


1

Following up on @mikewhatever's comment, and this thread, I ran make in the tools/firewire subdirectory of the kernel source tree. If there are no errors (see below) that will result in a nosy-dump executable that you can run. Your nosy device might not be /dev/nosy as written in the code so you can change that before compiling or use the -d flag. In my case ...


-1

I, too, received the 5.0.0-23-generic kernel today, after doing my typical sudo apt-get update No black screen, however. So far, everything seems to work.


1

TL;DR: use an Ubuntu kernel, either 4.15.xxx or the series of supported HWE kernels. Security is important, and kernel updates are critical to security. So you should use a kernel that gets regular updates. As you know, ukuu == Ubuntu Kernel Update Utility. As noted at Does Ubuntu update kernels upgraded by ukuu? - Ask Ubuntu, you have to periodically do a ...


0

Here's the default /etc/apt/sources.list for Ubuntu 16.04: https://gist.github.com/rohitrawat/60a04e6ebe4a9ec1203eac3a11d4afc1 Check through this file to see where yours is misconfigured. Make sure to run sudo apt-get update after you make any changes.


2

I managed to solve it. I pressed Ctrl + C to stop the process and then I saw: File to patch: ^Cdpkg: error processing package ros-kinetic-librealsense (--configure): subprocess installed post-installation script was interrupted dpkg: dependency problems prevent configuration of ros-kinetic-realsense-camera: ros-kinetic-realsense-camera depends on ros-...


0

This processes belongs to a scsi device on your system. You can use hwinfo or find /sys -name \*0000:06:00.0\* or lsscsi -v on your system to identify it. I have (no ubuntu) 0000:08:00.0 processes and it is a Tape Drive: # ps axuww | grep 0000:08:00.0 root 659 0.0 0.0 0 0 ? S< Jul30 0:00 [0000:08:00.0_ev] root 660 0.0 ...


0

/etc/default/grub: blinking: not found erase in /etc/default/grub blinking cursor. sudo -H gedit /etc/default/grub Then run sudo dpkg --configure -a && sudo apt -f install


0

Find where your build-essentials are kept find / | grep include/generated/autoconf.h Mine returned /usr/src/linux-headers-4.19.0-5-amd64/include/generated/autoconf.h If you followed the guides online and they didn't work, replace /lib/modules/`uname -r`/build With the result from above - in my case /usr/src/linux-headers-`uname -r` So, in total obj-...


0

Jackkobec's Answer describes a method of viewing grub.cfg and scrolling through source code to find a menu number. An easier way is with this script: Grub Version: 2.02~beta2-36ubuntu3.22 ┌───────────┤ Use arrow, page, home & end keys. Tab toggle option ├────────────┐ │ Menu No. ----------- Menu Name ----------- ...


1

Immediately after the BIOS/UEFI splash screen during boot, with BIOS, quickly press and hold the Shift key, which will bring up the GNU GRUB menu. (If you see the Ubuntu logo, you've missed the point where you can enter the GRUB menu.) With UEFI press (perhaps several times) the Esc key to get to the GRUB menu. Sometimes the manufacturer's splash screen is a ...


2

@https://askubuntu.com/users/730868/neeraj-bhatt I think you should remove old linux kernels because your /boot drive is out of space. Follow the steps as below :- 1) boot to grub and click on “Advanced options” 2) Select a previous kernel (should boot fine) 3) login and enter command 4) $ df (See if your /boot directory is 100% used) 5) Remove old linux ...


0

I'd just do a soft reinstall. make a live usb of 18.04 or 19.04 and choose the option to keep all your installed packages but reset config files. Should be least painful way to solve imo.


1

Just to document the solution... From the comments... Figured out what the problem was. And I was right in thinking that it was a memory conflict of some sort. In BIOS, I had XMP enabled which automatically set my ram to run at it's maximum speed of 1600 (a bit of overclocking in a sense). I've toned it back down to 1333 and now when I boot up using the ...


1

This is how I solved the issue for an HP 250 G5 laptop. Open the terminal and then run: $ cd /etc/default Now edit the grub file, which you can find in the default folder: $ sudo nano grub Inside the grub file, which should be now opened in a text editor, change the GRUB_CMDLINE_LINUX_DEFAULT from whatever it is to: GRUB_CMDLINE_LINUX_DEFAULT="quiet ...


0

If you don't have any manually installed drivers like nvidia or wifi drivers, then you can run the following command to update your kernel and headers to the newest version: sudo apt update sudo apt install linux-generic The package linux-generic is a "meta package" which means that the package is only a group of dependency packages. This meta package has ...


0

check your motherboard BIOS version with sudo dmidecode -s bios-version and then go to the manufacturer's web site and see if there's a newer version. check for a firmware update for the NVMe. run a memory test. Go to https://www.memtest86.com/ and download/run the free memtest to test your memory. Get at least one complete pass of all the tests to confirm ...


0

You need to verify the ISO, or if it's valid, write it again to thumb-drive or your install media as either of them was flawed as shown by squashfs read errors in your picture. For information on verifying your install media, please see https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-ubuntu To use the check-media-for-defects option you can ...


Top 50 recent answers are included