@b-9
There may be various options, depending on how comfortable you are with the
command line.
You could try to build a custom initramfs image with diagnostic tools, boot
from it and dump the necessary info to a USB drive for example. Or clone the
ubuntu kernel git repository and use git bisect
@ishinberg0
The issue ami, crysman and I had was related to a specific NVMe
controller (PCI IDs 126f:2263). 5.4.0-48 fixed it for ami and I at
least. I guess your issue is different; I suggest you file a new bug
report with details about your system (dmesg, lspci output etc.).
--
You received th
@crysman I have a NUC too. Is your nvme controller a Silicon Motion, Inc.
Device 2263 (rev 03) (126f:2263)?
It seems this controller somehow deviates from the specification.
The commit I mentioned above (ea43d9709f) made the driver stricter, causing it
to reject the device.
A fix is available ups
Same problem for me, 5.4.0-45 and -47 kernels fail to detect my nvme drive
while -42 boots fine.
According to git bisect the issue was introduced by commit
e958cbb11ed6f58dac5bbfba481631ff0f567c7d (upstream
ea43d9709f727e728e933a8157a7a7ca1a868281).
** Attachment added: "BISECT_LOG"
https:/
Public bug reported:
I tried some solutions from the web, but it didn't work, e.g using gpt
to make partition table
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersi
Yes, I noticed that one yesterday evening in the mainline repository. I've
just installed your image and it works fine too. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301590
Title:
Syste
I think there is a bug, even in the latest (3.13.0-23.45) revision.
It probably affects any 32-bit EFI system.
One easy way to fix it is to insert the following line in
efi_32.c:efi_map_region():
set_bit(EFI_OLD_MEMMAP, &x86_efi_facility);
This helps ensure that the function efi.c:runtim
Ok, I've cloned the ubuntu-trusty repo, used git bisect and found the
culprit:
dc9c3ed611922e769b1fd595f8f99a93d69c026d is the first bad commit
commit dc9c3ed611922e769b1fd595f8f99a93d69c026d
Author: Borislav Petkov
Date: Thu Oct 31 17:25:08 2013 +0100
x86/efi: Runtime services virtual map
Just tried with nr_cpus=1, still freezes with no message.
On Apr 3, 2014 5:52 PM, "Seth Forshee"
wrote:
> Achille: Could you also try adding "nr_cpus=1" to the boot options and
> see if this allows you to boot?
>
> --
> You received this bug notification be
I have read this page before reporting the bug. As I've written, no
kernel message is displayed.
With the default kernel command line, no message is displayed at all,
the machine freezes with a blank purple screen.
With the "quiet splash $vt_handoff" part removed, the last signs of
life I get befo
/dev/snd/controlC0: achille2265 F pulseaudio
CurrentDesktop: Unity
Date: Wed Apr 2 22:05:04 2014
HibernationDevice: RESUME=UUID=400897eb-e3fd-4d74-9494-e71d1dd2517b
InstallationDate: Installed on 2010-05-01 (1432 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Releas
*** This bug is a duplicate of bug 988509 ***
https://bugs.launchpad.net/bugs/988509
Thanks Mr Khan
I had purged this package a long time ago, and Ive forgotten this bug
report which is actually a duplicate from
https://bugs.launchpad.net/bugs/988509 that is bigger and strongly
discussed.
Re
Public bug reported:
Unattended upgrate failed to upgrade this package.
The package wasn't working fine before the upgrade.
Ubuntu 12.04.02 LTS
arantes@arantes:~$ apt-cache policy samba4
samba4:
Instalado: 4.0.0~alpha18.dfsg1-4ubuntu2
Candidato: 4.0.0~alpha18.dfsg1-4ubuntu2
Tabela de versã
My history.log in /var/log/apt/
COMMENTS IN ALL CAPITAL LETTERS
PROBLEM RELATED TO UPGRADE THAT WAS HAPPENING AFTER SAMBA4 INSTALLATION
Start-Date: 2013-05-25 13:05:01
Commandline: aptdaemon role='role-commit-packages' sender=':1.72'
Upgrade: software-center:amd64 (5.2.5, 5.2.9)
Error: Sub-proce
Public bug reported:
The problem started after I've tried to share files trhougt my Lan using samba.
The nautilus way failled, so I used apt-get install samba4, it worked, but
after this every single package installation ou removal (using software-center
or apt-get) resulted in a error report r
Hello and thanks for your reply!
That problem was solved by dist-upgrading to 9.04. The new kernel does work
well!
Now the lcd doesn't shade when i use battery, and i have not any problem using
the battery.
--
LCD brightness shades off and on cyclically when powered from battery
https://bugs.la
The same for me, on a Samsung Q45, having upgraded to Intrepid Ibex. The
problem didn't exist on the previous versions..
The brightness shade on and off.
--
Brightness applet flickers on Toshiba Satellite A105 (A105-S4254)
https://bugs.launchpad.net/bugs/155030
You received this bug notification
mmm can anyone helps me?
--
LCD brightness shades off and on cyclically when powered from battery
https://bugs.launchpad.net/bugs/325789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Public bug reported:
Binary package hint: gnome-power-manager
Hello everyone
i first want to apologize for my bad english!
I've been looking around the web for hints to fix this problem but i couldn't
do anything in order to solve it. I also have been looking here for this bugs
but i wasn't abl
19 matches
Mail list logo
