Today, I installed manually :
sudo dpkg -i intel-microcode_3.20180312.0~ubuntu18.04.1_amd64.deb
No change, the freeze
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746200
Title:
Regression in 2017
Today, I installed manually :
sudo dpkg -i intel-microcode_3.20180312.0~ubuntu18.04.1_amd64.deb
No change, the freeze still occurs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746200
Title:
Regr
With or without intel-microcode installed : "journalctl -b | grep ply"
gives no result.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746200
Title:
Regression in 2017-07-07 updates
To manage notif
'text' could be related to 'plymouth'. Maybe a theme is faulty. Please
do check:
journalctl -b | grep ply
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746200
Title:
Regression in 2017-07-07 updat
Some news :
Last week I saw a "grub" package update so I reinstalled the "intel-
microcode" package, the freezing bug is still there on my configuration
but there is one difference.
With the "intel-microcode" package, at boot there is always a message
that appears during approximately 1 second :
Some news :
- Install of Debian 9.3 Stable 31 Jan 2018 (Linux kernel 4.9) : Boot always
works
- Install of Debian Testing 31 Jan 2018 (Linux kernel 4.14) : Random freeze at
boot
So considering my investigations until here, I consider that "intel-
microcode v3.20180108.0+really20170707ubuntu17.1
- There is nothing about Refind into "journalctl -b".
- I am not mixing DEs, I use only Xfce.
- What does "S3 recovery" mean ? Samsung Galaxy S3 recovery ?
- The bug occurs since the first boot of that Xubuntu install (at that
time it was the 20180108 Intel CPU microcode), so I won't try to clea
Grepping journalctl is case sensitive; so 'refind' could be logged with
some uppercases, does not know, so watch 'journalctl -b' to find the
exact spelling.
Mixing different DEs will only add confusion/conflict/headhache ...
Fightting about trouble works the other way: test step by step, the simpl
Some tests I just did :
- "journalctl | grep refind > refind.txt" > Empty file
- Currently, I am booting like that : UEFI > Refind > Grub > Linux
kernel
- Chainloading the UEFI directly to Grub (no use of Refind) : gives the
same random bug
- Chainloading the Refind directly to Linux kernel (no
rEFInd is said 'beta quality' by its own dev
http://www.rodsbooks.com/refind/
and itself rely on rEFIt which has its bugs list :
https://sourceforge.net/p/refit/bugs/ but looks abandonned
http://www.rodsbooks.com/refind/todo.html
To conclude:
intel-microcode can't be blamed at first glance. B
If I boot a “vanilla” Ubuntu live USB, Does the "last CPU firmware" will
be applied at reboot or will it disappear ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746200
Title:
Regression in 2017-0
>
> Additional hints :
> - There is a big chance that I installed Xubuntu from a USB key created with
> UnetBootin (I saw it gives problem with Debian)
> - I am using the rEFInd Boot Manager on top of Grub
So I guess it’s a good idea to try a “vanilla” Ubuntu live USB.
>
> --
> You received t
Thanks for the help,
I have checked the timestamps into the 3 logs : It always corresponds to the
successful boot.
"journalctl -b" gives text I can't interpret, anyway it always
corresponds to the last boot (successful).
The Bios version is the most up to date one : v301 (13 oct 2016)
The "qu
There is nothing into the files above that can explain your issue.
So i propose to :
- remove 'quiet splash' from /etc/deault/grub and then run 'sudo update-grub'
- reboot and enter the bios/uefi to check the activated/deactivated settings
and choose the good ones. Also upgrade the bios/uefi if po
See attached, the output of :
journalctl -b | grep ERROR > ERROR.txt
** Attachment added: "ERROR.txt"
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+attachment/5045552/+files/ERROR.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
See attached, the output of :
journalctl -b | grep intel > intel.txt
** Attachment added: "intel.txt"
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+attachment/5045553/+files/intel.txt
** Description changed:
The version "3.20180108.0+really20170707ubuntu17.10.1"
See attached, the output of :
journalctl -b | grep error > error.txt
** Attachment added: "error.txt"
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+attachment/5045551/+files/error.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Please post the output files of:
- journalctl -b | grep error > error.txt
- journalctl -b | grep ERROR > ERROR.txt
- journalctl -b [ grep intel > intel.txt
** Changed in: intel-microcode (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of U
18 matches
Mail list logo