I have a fresh install of 18.04 SERVER installed on an Advantech SBC. 16.04 Server was working find but on 18.04 Server when I do a:
sudo shutdown -r now
The system starts the shutdown but stops with the last status line:
[ OK ] Stopped LVM2 metadata daemon.
I've tried some different bios configurations with power management but I can't seem to get it to restart. Only option at that point is to physically kill power and power up.
Anyone seen this? Any ideas on what to try?
On my SBC setting the South Bridge USB Configuration for Windows 8.x compatibility resolved this issue. Seems that the V4.15 kernel interactions with hardware are different enough to have caused this problem.
Related
I recently bought the HP Specter x360 and I installed ubuntu 20.04LTS. However, until now I have not enabled the Bluetooth on the laptop, I tried a lot but with no results. Please, there is anything to do in order to enable Bluetooth?
I used GRUB settings at startup:
Restarted Ubuntu and pressed ESC to load “Advanced options for Ubuntu"
Then selected option to enable network
Then option to repair broken packages
Finally "resume reboot".
Bluetooth service was back.
Check https://www.howtogeek.com/196740/how-to-fix-an-ubuntu-system-when-it-wont-boot/#:~:text=Use%20Recovery%20Mode%20If%20You%20Can%20Access%20GRUB&text=Select%20the%20%E2%80%9CAdvanced%20options%20for,the%20submenu%20and%20press%20Enter.
I'm having a bit of a problem and I'm having a really hard time of looking up info on the web.
The problem
When running network-intensive applications from WSL, after a while Windows 10 loses internet connectivity. Restarting LxssManager service restores internet connectivity.
This happens most often when using expo cli. It sometimes also happened with create-react-app server, but recently I haven't had problems with that.
What I've tried
pinging 8.8.8.8 (sometimes works, sometimes errors with Network Unreachable. Even when it works, Windows still doesn't have internet)
Disabling IPv6
Disabling power saving on the WiFi adapter
Running script from cmder (as opposed to the integrated terminal of VsCode)
Running script from WSL Bash
Switching from wireless to ethernet (same problem)
Updating/rolling back all network drivers
Reinstalling WSL, node and related packages
Reinstalling Windows
Environment
Dell Latitude E5570 with Intel Dual Band Wireless AC 8260
Windows 10 version 1809 build 17763.55 (also happened with the previous update)
WSL Ubuntu installed from store
Node.JS versions 8 through 11 (tested on all versions and same behaviour on all)
I don't know if this is an issue with WSL or an issue with my laptop / drivers / config, so I thought it's best to post here before posting an issue on GitHub.
I have a problem and I can't find how to solve it so if anybody can give me a hand I will be gratefull.
After upgrading one of my proxmox vm to debian 8 jessie all worked fine, but when I have restarted the vm doen't load.
I have connected through the VNC of Proxmox and shows this when booting and I can't type or do anything.
systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVININT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
Detected virtualization 'openvz'.
Detected architecture 'x86-64'.
Welcome to Debian GNU/Linux 8 (jessie)!
Sethostname to <srv4>.
Failed to enable kbrequest handling: Invalid argument
Cannot add dependency job for unit rpcbind.service, ignoring: Unit rpcbind.service failed to load: No such file or directory.
Cannot add dependency job for unit display-manger.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
Assertion 'clock_gettime(clock_id, &ts) == 0' failed at ../srv/shared/time-util.c:33, function no(). Aborting.
Caught <ABRT>, dumped core as pid 53.
Freezing execution.
Anybody knows what it's happening?
Thanks for your support.
now I know what has happened.
I installed a new virtual machine (openVZ containter) (CT) with debian 8 and had the same problem at start, I thought that the problem was with the upgrade but having the same problem with a new fresh debian 8 install I have search for new solutions.
The problem it's that I was running Proxmox 3.2 which uses a linux Kernel not compatible with Debian 8.
https://forum.proxmox.com/threads/debian-8.22043/
So be adviced, if you are using Proxmox 3.x don't upgrade your CT's to Debian 8 jessie or your machines will never restart.
Important, after the upgrade all works perfectly until you restart, I was working with Debian 8 for more than one month after the upgrade with any issues, until I needed to restart.
Best!
I'm running a VM in Azure with Ubuntu 14.04. I've installed XFCE and use X2GO to remote desktop to the machine.
I've downloaded the VS Code and unzipped the files. When I run Code from a terminal I get the following error:
WouterDeKort#UbuntuDev:~/tools/web/visual-studio-code$ ./Code
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
WouterDeKort#UbuntuDev:~/tools/web/visual-studio-code$ [ , [Error: channel closed] ]
Any idea what I'm doing wrong?
DISCLAIMER ;-) I'm a total Linux newby. I've just installed Linux for the first time today and I have no idea what I'm doing ;-)
The work-a-round is in issue 3451. After running this, I was able to launch it from Debian Jessie with LXDE over X2Go.
sudo sed -i 's/BIG-REQUESTS/_IG-REQUESTS/' /usr/lib/x86_64-linux-gnu/libxcb.so.1
I have the same problem using X2GO and LXDE. Works okay (but slowly) using MobaXterm so apparently this is a problem specific to X2GO.
For anyone who still wonder what is the best choice if you want to start Visual Studio Code on a headless Ubuntu - the winning combination is:
Ubuntu Server + xfce + nomachine remote desktop
VS Code starts immediately without any hacks, you can set your resolution however you like, and nomachine is blazingly fast.
im running Ubuntu 14.04.1 LTS (desktop), on an embedded device (Odroid U3) and
on boot, my 3G usb modem is seen as a ttyACM0 / ttyACM1 device, which is correct.
Post boot i am able to simply run wvdial..and from there I can get a connection...
I am running my system headless, and would ideally like to get the OS "converted" to more
of a server configuration(smaller) if possible. I have tried running the
the ubuntu server version here viewtopic.php?f=77&t=5123, along with
multiple versions of debian(7 / 7.4) but neither will detect the usb modem correctly on boot.
I am a newbie to linux, and the only thing that I have tried is
trying to force load some of the kernel modules on boot ( /etc/modules ) to try to
alter the detection of the device on boot. (cdc_acm, usbserial, ppp....etc), no luck.
On the ubuntu server version above I even updated the kernel to
version newer than the one currently on the working desktop version, still no luck,
Does anyone have experience with usb 3G modem detection on boot??,
Any ideas why it works on the 14.04.1 LTS desktop version , and not any others?,
thanks a ton...for any suggestions
Appears that there is a patch in 14.04 ubuntu boot that fixes the usb_modeswitch issues. After taking a raw ubuntu , adding usb_modeswitch , its now working just fine.
Did not even have to configure usb_modeswitch.