Update: in the motherboard settings, under I/O, there's an option "Video
Option ROM Type". This bug occurs when the value is set to UEFI. When
the value is set to Legacy, the bug does not occur. There's a third
possible value, "Disabled" or similar, which I did not try.
Excuse me ignorance. I
Yes, Daniel. The picture is normal at all available rates above 60Hz.
120Hz and 144Hz. Awesome.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852166
Title:
[nouveau] Pixel pattern
It seems that I am able to set the refresh rate to 120Hz and 144Hz.
Feel free to close this.
xserver-xorg-video-nouveau 1:1.0.16-1
Linux shahar-desktop 5.3.0-46-generic #38-Ubuntu SMP Fri Mar 27 17:37:05
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID
Alrighty. Thank you for you attempts, Kai-Heng.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1846214
Title:
Freezes instead of suspending, most times
Status in linux package in
Thank you for responding, Kai-Heng. Attached.
** Attachment added: "dmesg output, no suspend attempt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846214/+attachment/5325221/+files/dmesg-with-nvidia-driver-435-clean-boot.log
--
You received this bug notification because you are a
Thank you for the suggestion, Kai-Heng.
Tried with the nvidia-driver-435 installed, after reboot, and 2 out of 2
failures. I also made sure that `lsmod | grep nvidia` prints some
modules. Not sure which modules exactly I'm looking for. Perhaps looking
at some logs would be better, but I have a
Thank you, Daniel.
>From one boot after the failed one, here it is attached.
** Attachment added: "journalctl -b-1"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1856507/+attachment/5313189/+files/prevboot.txt
--
You received this bug notification because you
Thank you, Daniel. Here it is.
** Attachment added: "lspci -k"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1856507/+attachment/5313153/+files/lspcik.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Summary changed:
- [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (MSI monitor
model 1462)
+ [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI
Optix G24C / model 1462)
--
You received this bug notification because you are a member of Kernel
Thank you for the instructions, Daniel.
When nvidia-driver-435 is not installed, I can get to a console login
prompt from the login screen by pressing CTRL+ALT+F2 through 6. But when
nvidia-driver-435 is installed and I press any of those, I get to a
black screen with a blinking cursor.
Any
Thank you for the instructions, Daniel.
I did uncomment the above line using sudoedit, installed nvidia-
driver-435 and rebooted.
No apparent change. Still no login screen.
Reported:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-435/+bug/1856507
Can progress be made on
Public bug reported:
Attempting to boot after installing nvidia-driver-435, the login screen
does not show up.
I tried editing /etc/gdm3/custom.conf and uncommenting the line:
#WaylandEnable=false
And then rebooting. No apparent change. Still no login screen.
Screenshot attached.
Thank you for following up, Daniel.
With the NVIDIA driver, the login screen doesn't show up.
What would be the appropriate next step, please?
** Attachment added: "Login screen doesn't show up with NVIDIA driver."
Thank you for following up, Kai-Heng.
I downloaded these files:
```
-rw-r--r-- 1 mightyiam mightyiam 11M Dec 12 18:57
temp/linux-headers-5.5.0-050500rc1_5.5.0-050500rc1.201912081930_all.deb
-rw-r--r-- 1 mightyiam mightyiam 1.2M Dec 12 18:42
Thank you for your suggestion, Kai-Heng. I did that in
`/etc/default/grub`. After editing I ran `sudo update-grub` without
trouble. I rebooted and made sure with `lsmod` that `nouveau` is not
loaded. And I still got a freeze.
Is there anything else we could investigate, please?
--
You received
Thank you for following up, Daniel.
Same in an Ubuntu on Wayland session.
I tried setting dithering depth and dithering mode but it doesn't
change.
Should this be reported upstream?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
*** This bug is a duplicate of bug 374105 ***
https://bugs.launchpad.net/bugs/374105
** This bug has been marked a duplicate of bug 374105
linux-image-$ver packages leave cruft behind
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Attachment added: "Output of `journalctl -b -1 -k` after successful
suspend/resume"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846214/+attachment/5303250/+files/journalctl.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
In case it could help, here's the output of the same command after a
successful suspend/resume.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1846214
Title:
Freezes instead of
Thank you for the follow-up, Kai-Heng.
Before altering the value, I checked and `cat /sys/power/mem_sleep`
returned `s2idle [deep]`.
And now the command you suggested seems to have changed it to `[s2idle]
deep`.
I will post this and then run `# systemctl suspend`.
--
You received this bug
Same symptoms. Keyboard backlights are on. Power button LED on. No
suspension. Turned off via power button long press.
Here's the output of `journalctl -b -1 -k`.
** Attachment added: "`journalctl -b -1 -k`"
Thank you for following up, Kai-Heng.
To answer your question, I don't remember ever having a reliable suspend
in this system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1846214
Thank you for your assistance, Kai-Heng. Attached is the output of the
command you specified.
** Attachment added: "Output of `journalctl -b -1 -k`"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846214/+attachment/5301075/+files/journalctl.log
--
You received this bug notification
Public bug reported:
Hi and thank you for all your free software work.
This system usually freezes instead of suspending.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-29-generic 5.0.0-29.31
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux
@mangoo-wpkg, that seems like valuable information upstream. Does anyone
know the procedure to get it upstream, please?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1730331
Hey, I've just upgraded from bionic to cosmic and I seem to be hit by
this. Perhaps. What I experience is that while I have an encrypted root,
with the cosmic kernel I don't get a chance to input my passphrase.
Anything I can do to help debug this? I'm a web developer. I can use git
bisect.
--
The following package from zesty-proposed does not have this crash:
Package: linux-image-4.9.0-15-generic
Priority: optional
Section: kernel
Installed-Size: 67599
Maintainer: Ubuntu Kernel Team
Architecture: amd64
Source: linux
Version: 4.9.0-15.16
Provides:
Crash does not happen with 4.10.0-041000rc5-generic.
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1659268
Title:
Consistent boot time kernel
Joseph, regarding what kernel version this panic starts happening in, I know
two things:
In 4.8.0-32 it does not.
In 4.9.0-12 it does.
Is this enough information?
I will try the mainline build.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: "screen shot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659268/+attachment/4808924/+files/IMG_20170125_123244.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I don't know to provide the necessary crash dump and any other things
that may be required to analyze this.
The crash occured consistently on every boot with this kernel.
I'm currently running 4.8.0-32-generic, which I still have installed.
It does not cause this crash.
I
-4.4.0-2-generic 4.4.0-2.16
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: shahar 2292 F pulseaudio
/dev/snd/controlC0
Does anyone have a workaround, please?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1318111
Title:
Adds more and more copies of ‘crashkernel=384M-:128M’ in
/etc/default/grub
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shahar 2138 F pulseaudio
CurrentDesktop: Unity
Date: Fri Jun 27 20:39:29 2014
Thank you Brian, Chris and everyone sudodus and everyone involved.
נשלח מנייד Sent from mobile
On Mar 3, 2014 8:55 PM, sudodus nio.wikl...@gmail.com wrote:
ERROR: PAE is disabled on this Pentium M
(PAE can potentially be enabled with kernel parameter
forcepae - this is unsupported, may cause
Christopher,
I don't care that the proprietary driver doesn't work because the free
one seems to be working perfectly.
This bug does not affect me.
Blessings,
Shahar
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
/controlC1: shahar 2550 F pulseaudio
/dev/snd/controlC2: shahar 2550 F pulseaudio
/dev/snd/controlC0: shahar 2550 F pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Sun Mar 31 16:34:54 2013
ExecutablePath: /usr
Thank you for running the tests.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/930447
Title:
Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M
x86 Laptop due to
Exactly :-)
Sent from mobile נשלח מנייד
On Jul 18, 2013 3:41 PM, oliver oli...@schinagl.nl wrote:
Chris, I think Shahar's idea is to submit the patch and hopefully gets
merged so that regular users don't have to remove anything to get
everything working.
But yeah, why not, submit a patch
39 matches
Mail list logo