[Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell.

2018-02-11 Thread daniel CURTIS
Hi. I can not enter mentioned command, because during system boot plymouth freezes and keyboard is unresponsive. After several seconds plymouth disappears and BusyBox v1.22.1 "console" appears (here, keyboard does not work and does not respond either). The only solution is to use hard reboot and ch

[Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell.

2018-02-11 Thread daniel CURTIS
Please see "Ubuntu Kernel Bot (ubuntu-kernel-bot)" comment and answer. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748710 Title

[Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

2018-02-13 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix t

[Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

2018-02-14 Thread daniel CURTIS
Good day, Mr Salisbury. Yes, I can test the latest kernel, but I have a few very naive questions (I just want to be sure for one hundred percent etc.) So, because it's an i386/x86_32 architecture I should: ✗ download 'linux-headers-4.16.0-041600rc1-generic_4.16.0-041600rc1.201802120030_i386.deb'

[Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

2018-02-14 Thread daniel CURTIS
Here is a new, separate bug report about 'kASLR' and system booting issues (v4.4.0-113.136 - v4.4.0-115-generic kernel versions): ● https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748936 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to U

[Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

2018-03-15 Thread daniel CURTIS
Hello. I apologize for not testing the latest v4.16 kernel, but I've decided to wait for an update to the v4.4 kernel used in "Xenial". And it seems, that everything is okay now and 'kaslr' option is working again. After update Linux kernel to the v4.4.0-117-generic (v4.4.114) version, system boot

[Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

2018-02-11 Thread daniel CURTIS
** Summary changed: - Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell. + Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs). ** Description changed: Hello. On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LT

[Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

2018-02-12 Thread daniel CURTIS
Hello. There is the same problem with a new, latest Linux 4.4.0-115-generic kernel (updated today). I've tried to boot system with 'nosplash' option (set via GRUB etc.) and it seems, that there is a problem with: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline)

[Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

2018-02-12 Thread daniel CURTIS
** Description changed: Hello. On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to the 4.4.0-113.136 version (xenial-proposed). However, after reboot, plymouth freezes during start, and keys on an USB keyboard were in- active. After several seconds, the BusyBox shell