I'm unable to completely shutdown my system after running sudo init 6 or sudo shutdown -reboot This is the system I have, which runs on the Atom x5-Z8350 Cherry Trail CPU.  Previously I installed 20.04 I saw an error while rebooting – part of that error was: > an error BUG: soft lockup - CPU#1 stuck for 22s! Unfortunately I'm not sure where I could have found the entire log file, and now I've installed 21.10. I thought the kernel on 21.10 would have solved my issue.  Things looked well since the verbose was giving me back "[ok]" for everything.  Unfortunately, there were no errors shown on the display, and my display turns off but the system and keyboard stay on, and I'm forced to hold the shutdown button. What commands should I run that could help you guys better understand my hardware plus how can I log or find the logs for the failed reboot? AFAIK errors for reboot/shutdown are not saved since the system dismounts.

watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [shutdown:1]
watchdog: BUG: soft lockup - CPU#1 stuck for 54s! [shutdown:1]
watchdog: BUG: soft lockup - CPU#1 stuck for 104s! [shutdown:1]
[drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:93:pipe C] commit wait timed out
[drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CONNECTOR:107:HDMI-A-2] commit wait timed out
watchdog: BUG: soft lockup - CPU#1 stuck for 131s! [shutdown:1]
[drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:73:primary C] commit wait timed out
[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:93:pipe C] flip_done wait timed out
watchdog: BUG: soft lockup - CPU#1 stuck for 157s! [shutdown:1]
watchdog: BUG: soft lockup - CPU#1 stuck for 183s! [shutdown:1]
watchdog: BUG: soft lockup - CPU#1 stuck for 209s! [shutdown:1]
watchdog: BUG: soft lockup - CPU#1 stuck for 235s! [shutdown:1]
rcu: INFO: rcu_sched self-detected stall on CPU
rcu: ‡1-....: (65719 ticks this GP) idle=9be/1/0x4000000000000000 softirq=9335/9336 fqs=29997 
watchdog: BUG: soft lockup - CPU#1 stuck for 272s! [shutdown:1]
watchdog: BUG: soft lockup - CPU#1 stuck for 298s! [shutdown:1]
watchdog: BUG: soft lockup - CPU#1 stuck for 324s! [shutdown:1]
watchdog: BUG: soft lockup - CPU#1 stuck for 350s! [shutdown:1]
watchdog: BUG: soft lockup - CPU#1 stuck for 376s! [shutdown:1]
watchdog: BUG: soft lockup - CPU#1 stuck for 402s! [shutdown:1]
rcu: INFO: rcu_sched self-detected stall on CPU
rcu: ‡1-....: (110715 ticks this GP) idle=9be/1/0x4000000000000000 softirq=9335/9336 fqs=52497

[[screen image of the above]]

I have an Intel Atom D2700 (Synology NAS DS412+) with 4GB RAM running kernel 3.2.30 x86_64. This unit has a single DIMM slot. One thing I, and other's have found, is that when adding a 4GB DIMM versus a 2GB DIMM, the unit experiences significantly higher CPU usage when under load (for example, 'heavy' Java applications like Minecraft servers, or Plex transcoding, etc). Many users have found that when they drop back to 2GB all of these high load issues disappear. Is this something specific to Linux that may cause this? Or is this an issue with the Atom itself?

With all the distros out there, I'm not up to date on which does what. I have an old Atom D2500 box that I want to get going. It's currently running CentOS8 but that lineage is terminated. So I've been researching options and tried Puppy OS, which can't even install from the ISO image. Oh well. Anybody have any recommendations? I'm looking for small, lightweight, where I can install modern Ruby, gems, etc. Any insight appreciated. Cheers.

I'm using atom to write code in C++. When I compile my code in the terminal using g++ -Wall -std=c++14, it prints and compiles properly in the terminal. Any revisions to my code after the first print however, do not transfer over to my terminal, and when I run the same code, the original always prints. I'm saving my source code in atom everytime I make a revision. If I save the exe file in atom it becomes a binary and does not print anymore. Does anyone know how I can get my source code to update in my terminal when I save it? Any help would be great.

I am new in Linux and debian 10 (KDE) is the first distribution that I am using. But when I'm trying to install atom editor when I use this command It gives me an error : command >> sudo apt-get install atom Output : Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package atom I looked it up in google but i couldn't find anything to fix my problem.

In linux mint, is it possible to run atom editor by command atom? I tried atom Command 'atom' is available in '/snap/bin/atom' The command could not be located because '/snap/bin' is not included in the PATH environment variable. atom: command not found

I'm using Mint 19.1 Tessa. I've installed Atom 1.38 and I can't install any packages on it, bot using wizard inside IDE and in terminal usin apm. Any ideas what might be the problem and how to fix it?

Recently I installed Mint Linux 15 (Olivia) 32 bit on my friends netbook. I am copy pasting the output of *sudo lspci -vk* 00:00.0 Host bridge: Intel Corporation Atom Processor D2xxx/N2xxx DRAM Controller (rev 03) Subsystem: Acer Incorporated [ALI] Device 061f Flags: bus master, fast devsel, latency 0 00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device 061f Flags: bus master, fast devsel, latency 0, IRQ 46 Memory at 86000000 (32-bit, non-prefetchable) [size=1M] I/O ports at 50d0 [size=8] Expansion ROM at [disabled] Capabilities: [d0] Power Management version 2 Capabilities: [b0] Vendor Specific Information: Len=07 Capabilities: MSI: Enable+ Count=1/1 Maskable- 64bit- Kernel driver in use: gma500 So the problem is whenever I try to boot into the system it pops out a notification (not the exact words) Running in software rendering mode. No Hardware acceleration. I have searched the Mint Linux forum and found [this thread] (http://forums.linuxmint.com/viewtopic.php?f=49&t=135578&p=727654) , but it did not help much. I am also attaching the output of *inxi -Fxz* Kernel: 3.8.0-19-generic i686 (32 bit, gcc: 4.7.3) Desktop: Gnome Distro: Linux Mint 15 Olivia Machine: System: Acer product: AOD270 version: V1.06 Mobo: Acer model: JE01_CT Bios: Insyde version: V1.06 date: 03/05/2012 CPU: Dual core Intel Atom CPU N2600 (-HT-MCP-) cache: 512 KB flags: (lm nx sse sse2 sse3 ssse3) bmips: 6383.8 Clock Speeds: 1: 1600.00 MHz 2: 1600.00 MHz 3: 1600.00 MHz 4: 1600.00 MHz Graphics: Card: Intel Atom Processor D2xxx/N2xxx Integrated Graphics Controller bus-ID: 00:02.0 X.Org: 1.13.3 drivers: vesa (unloaded: fbdev) Resolution: 1024x600@60.0hz GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.2, 128 bits) GLX Version: 2.1 Mesa 9.1.1 Direct Rendering: Yes The direct effect of disabled hardware video acceleration is that it is impossible to play video files and since the CPU is engaged with software acceleration, the system is damn too slow.

I installed linux manjaro on Lenovo Miix 320 (Atom x5 z8350) and got mostof it to work except for the battery indicator. It shows 100% all the time, but that is not the problem. The problem is when I shut down or restart the computer, then it gets stuck in some loop and print this all the time: axp288_fuel_gauge acp288_fuel_gauge: capacity measurement not valid axp288_fuel_gauge acp288_fuel_gauge: driver failed to report "charge_now" propery -6 Can I fix or disable the drivers from triggering all this battery related stuff?

drupal@drupal-pc:~$ sudo find / -type f -name "libnode.so" find: ‘/run/user/1000/gvfs’: Keine Berechtigung /opt/atom/libnode.so drupal@drupal-pc:~$ atom atom: error while loading shared libraries: libnode.so: cannot open shared object file: No such file or directory Since myself compiled node js from github, yesterday. atom doesn't launch atom from commandline altough the missing file is on board In addition atom runs perfectly, when launched from the launcher icon. Any ideas!

I was trying to pipe an output url into the open command but found several instances where despite changing the color settings of grep or piping further output through other utils like awk or cut I was still getting special chars in the output. As shown below: The first 2 times I run the open command I get sent two these two urls respectively: You can see the special chars being tacked onto the urls despite being piped through cut, or changing the color settings. This is confirmed with the od command: ➜ ~ apm show vim-mode | grep https | cut -d' ' -f2 | od -atx1 0000000 esc [ 4 m h t t p s : / / g i t h 1b 5b 34 6d 68 74 74 70 73 3a 2f 2f 67 69 74 68 0000020 u b . c o m / a t o m / v i m - 75 62 2e 63 6f 6d 2f 61 74 6f 6d 2f 76 69 6d 2d 0000040 m o d e esc [ 2 4 m nl 6d 6f 64 65 1b 5b 32 34 6d 0a ➜ ~ apm show vim-mode | grep --color=none https | cut -d' ' -f2 | od -atx1 0000000 esc [ 4 m h t t p s : / / g i t h 1b 5b 34 6d 68 74 74 70 73 3a 2f 2f 67 69 74 68 0000020 u b . c o m / a t o m / v i m - 75 62 2e 63 6f 6d 2f 61 74 6f 6d 2f 76 69 6d 2d 0000040 m o d e esc [ 2 4 m nl 6d 6f 64 65 1b 5b 32 34 6d 0a 0000052 The next two outputs try to use awk to strip off the url from apm however they also introduce special chars, and the open command then tries to open them as files. This is confirmed with od: ➜ ~ apm show vim-mode | awk -F' ' '/http/ {print $2}' | od -atx1 0000000 esc [ 4 m h t t p s : / / g i t h 1b 5b 34 6d 68 74 74 70 73 3a 2f 2f 67 69 74 68 0000020 u b . c o m / a t o m / v i m - 75 62 2e 63 6f 6d 2f 61 74 6f 6d 2f 76 69 6d 2d 0000040 m o d e esc [ 2 4 m nl 6d 6f 64 65 1b 5b 32 34 6d 0a The solution has been to use a lovely [sed oneliner](http://www.commandlinefu.com/commands/view/3584/remove-color-codes-special-characters-with-sed) , sed -r "s/\x1B\[([0-9]{1,2}(;[0-9]{1,2})?)?[m|K]//g" that succeeds at stripping off all the special chars. The final open command uses this oneliner and succeeds at going to https://github.com/atom/vim-mode as expected. This is confirmed by od: ➜ ~ apm show vim-mode | awk -F' ' '/http/ {print $2}' | sed -r "s/\x1B\[([0-9]{1,2}(;[0-9]{1,2})?)?[m|K]//g" | od -atx1 0000000 h t t p s : / / g i t h u b . c 68 74 74 70 73 3a 2f 2f 67 69 74 68 75 62 2e 63 0000020 o m / a t o m / v i m - m o d e 6f 6d 2f 61 74 6f 6d 2f 76 69 6d 2d 6d 6f 64 65 0000040 nl 0a 0000041 So this leaves some questions: 1. Why isn't the grep --color=none working? 2. Why are my various other utils tacking on special chars? I suspect it has something to do with my shell settings. I'm using [zim](https://github.com/Eriner/zim) with the [gitster](https://github.com/shashankmehta/dotfiles/blob/master/thesetup/zsh/.oh-my-zsh/custom/themes/gitster.zsh-theme) theme **edit** setting TERM=dumb appears to have no affect: ➜ github-application master ✓ diff <(TERM=dumb apm show vim-mode | od -atx1) <(apm show vim-mode | od -atx1) ➜ github-application master ✓ setting NPM_CONFIG_COLOR=false also appears to have no affect: ➜ ~/w/s/g/m/todo master ✓ diff <(NPM_CONFIG_COLOR=false apm show vim-mode | od -atx1) <(apm show vim-mode | od -atx1) ➜ ~/w/s/g/m/todo master ✓ I think it's because of the underline in the url. I've been exploring it further in [another question](https://stackoverflow.com/questions/40336126/where-does-the-coffeescript-underline-method-come-from)

I am working with an embedded board which includes an **Intel Atom N2600** processor and a GPU **GMA 3600** series based on the PowerVR SGX 545 graphics core (developed by Imagination) [[Link1]][1] . As far as I know, Intel just offers Windows 7 support for its GPU through a driver in Link2 . In my case, I am working under **Linux**, so I need to know if there exists any possibility of enabling the GPU capabilities using any compatible driver loaded when X server is started. Is this impossible? Does the driver just go with a 3.2 Linux kernel, such as in this answer Link3 ?

I'm trying to build a custom distro for a tablet, using the Yocto Project with the meta-intel layer. Everything builds OK and after flashing to the device, it boots but the screen goes blank when the i915 driver is initialised. Sometimes there are a couple of coloured lines across the screen, which looks to me like the device has crashed completely, though I can't be sure as there is only a USB port on it so I can't get a serial TTY to check it. If I add i915.nomodeset=1 to the command line, the system boots up fully, but doesn't initialise DRM, which I need. The kernel version I'm using is 3.19.5. I've managed to grab a picture of the logging output just before the screen goes off: Does anyone know why this might be happening, and how to fix it? **Update** I managed to get a dump from dmesg with the screen off. You can see it here: dmesg dump

I'm trying to set up a custom Linux installation on an Intel Atom (Baytrail) based Android tablet, using Qt 5.5 for device creation. The build system is based on the Yocto project and builds an embedded Linux image. In order to run this image on the tablet (which is originally and Android tablet), I'm replacing the boot partition, with an image containing the kernel, initramfs and initial boot script, and replacing the system partition with the full image, then flashing these to the device with the Intel Manufacturing Tool. So far, I have the device booting into my new kernel with the initramfs, and running the init script. The issue comes when trying to mount the main partition on the embedded flash. The command to mount the system partition fails with "Invalid Argument". A cat proc/filesystems shows that ext4 is supported, and parted -l shows the partitions on the internal MMC are all ext4, with the exception of the first, which is the EFI boot partition. I can't mount any of the ext4 partitions, but I can mount the EFI partition, so I think that means the whole MMC should be accessible. Running fdisk -l only shows the first partition (the EFI boot partition), but I think that is because fsdisk doesn't support GPT. Does anyone know why I wouldn't be able to mount the ext4 partitions? They are all listed in /dev as: mmcblk0 mmcblk0p1 mmcblk0p2 mmcblk0p3 mmcblk0p4 mmcblk0p5 mmcblk0p6 mmcblk0p7 mmcblk0p1 is mountable, and is the EFI boot partition. Sorry I can't post any of the actual output, so this is all from memory, but the battery just died on the device as I started writing this. I should be able to get some actual output from the commands if it's needed once it's charged again. **Update** So I recompiled Busybox, enabling GPT support in fdisk, and fdisk lists the partitions. I also installed TestDisk on the device, and can browse the filesystem using TestDisk. Trying to mount the partitions listed under /dev/mmcblk0p(2 - 7) still doesn't work, but I can successfully mount a partition by getting the start sector from fdisk -l, then setting up a loop device via losetup -o (Start Sector * Sector Size) /dev/loop0 /dev/mmcblk0, then finally mounting /dev/loop0. Why do I have to go through this method instead of being able to just mount /dev/mmcblk0p2 etc.?

I used a LCD monitor with Fedora 10. No problem. Then, I bought a new computer, Intel Atom (Packard Bell) and installed Fedora 20 KDE Plasma and attached the previous LCD monitor Everything fine, except the monitor that now flickers (a steady tremble). This is annoying, especially when I use terminal with black background. Anyone can help?

I have a Intel N2800 motherboard with the PoverVR Cedar Trail GPU. It seemed that it was not possible to make it work other than using some meego kernel patch that works on a specific kernel version. Even the graphical part of the installer did not boot up. To fix this issue I bought a Club 3D PCI-E x1 Nvidia GT-610 graphics card. With this card I was able to install the OS, but still can't get it to work. With the nouveau driver that comes with the F17, the booting gets stuck at the "F" logo. With kmod-nvidia drivers I got to the login screen, but it freezes there. When I installed the nvidia proprietary driver and used nouveau.modeset=0 on the kernel command line to disable the nouveau driver it got stuck at booting after the text messages go past. After the text messages there is a black screen with the white "text cursor" in the top left corner. Every once in a while the screen blinks and show the text boot log that is presumably "below" the black screen. I read that more than one fedora user has resolved this by removing xorg.conf. I tried that too, but it didn't work either. After removing the file it gets stuck on the "F" logo, with yellow stripes and other "artifacts". The motherboard has only a single short x1 pci-e bus connector, so there are not that many other cards that can be tried. There is also a slight possibility of a mb failure, as the USB's seem to get sometimes unresponsive at random. Is there anything software related I could try?

Does anyone know any Atom N270-compatible processors (what I mean is not that they run on the same socket, but that they can share a kernel with nothing going wrong). Btw, this also means that they run the same instruction set, right? (My question is similar to https://unix.stackexchange.com/questions/117495/kernel-configuration-which-processor-family-to-choose-for-celeron-m-cpu-420 , but I'm not making my own kernel; I'm trying to install Chrome OS through http://zzsethzz.blogspot.com/2013/02/install-chromium-upgrade-it-to-chrome.html . Also, the previous link says that the celeron builds should be compatible. Is that true?)