All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218092] Laptop hanging on black screen, when suspended and woke up!
Date: Fri, 03 Nov 2023 07:16:24 +0000	[thread overview]
Message-ID: <bug-218092-215701-9R4neosxK8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218092-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=218092

--- Comment #43 from Ertugrul Uyar (ertugruluyar.personal@gmail.com) ---
I don't know what happened exactly but it's building .deb files now. I dıd this
things:
https://github.com/openssl/openssl/issues/20293#issuecomment-1461877599 --> I
did make modules then make modules_sign. make modules_sign give error and I did
this: https://askubuntu.com/a/1178467
then, to create signature, I think, click the link:
https://superuser.com/a/1322832 --> In this, I did this: 
"In your linux kernel root folder that you're compiling go to the certs folder
and run:"
openssl req -new -nodes -utf8 -sha512 -days 36500 -batch -x509 -config
x509.genkey -outform DER -out signing_key.x509 -keyout signing_key.pem
Then I tried this: "make modules_sign" and "make modules_install" and get
error, so I decided to disable module signing:
https://stackoverflow.com/questions/29806414/how-to-disable-kernel-module-signing-in-linux
but I didn't change the value from this UI. So I manually change .config file:
CONFIG_MODULE_SIG=n
CONFIG_MODULE_SIG_ALL=n
I was change this and copy to linux6.6/ folder and then run "make -j$(nproc)
bindeb-pkg" then I checked the .config file while is building. In the .config
file that used for last building: 
CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_ALL is not set

NOW, I have this .deb file. How I am gonna install this, do I have to use
command or I just click and open with KDE Discover. And which file should I
install?
-----
dpkg-deb: building package 'linux-image-6.6.0' in
'../linux-image-6.6.0_6.6.0-6_amd64.deb'.
dpkg-deb: building package 'linux-libc-dev' in
'../linux-libc-dev_6.6.0-6_amd64.deb'.
dpkg-deb: building package 'linux-headers-6.6.0' in
'../linux-headers-6.6.0_6.6.0-6_amd64.deb'.
dpkg-deb: building package 'linux-image-6.6.0-dbg' in
'../linux-image-6.6.0-dbg_6.6.0-6_amd64.deb'.
 dpkg-genbuildinfo --build=binary -O../linux-upstream_6.6.0-6_amd64.buildinfo
 dpkg-genchanges --build=binary -O../linux-upstream_6.6.0-6_amd64.changes
dpkg-genchanges: info: binary-only upload (no source code included)
 dpkg-source --after-build .
dpkg-buildpackage: info: binary-only upload (no source included)
-----

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-11-03  7:16 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-218092-215701@https.bugzilla.kernel.org/>
2023-10-31 13:02 ` [Bug 218092] Laptop hanging on black screen, when suspended and woke up! bugzilla-daemon
2023-10-31 13:02 ` bugzilla-daemon
2023-10-31 15:49 ` bugzilla-daemon
2023-10-31 18:25 ` bugzilla-daemon
2023-10-31 18:35 ` bugzilla-daemon
2023-10-31 18:35 ` bugzilla-daemon
2023-10-31 18:38 ` bugzilla-daemon
2023-10-31 18:40 ` bugzilla-daemon
2023-10-31 18:40 ` bugzilla-daemon
2023-10-31 18:45 ` bugzilla-daemon
2023-10-31 19:25 ` bugzilla-daemon
2023-10-31 20:13 ` bugzilla-daemon
2023-10-31 20:48 ` bugzilla-daemon
2023-10-31 20:53 ` bugzilla-daemon
2023-11-01  9:11 ` bugzilla-daemon
2023-11-01  9:11 ` bugzilla-daemon
2023-11-01 17:08 ` bugzilla-daemon
2023-11-01 18:01 ` bugzilla-daemon
2023-11-01 18:02 ` bugzilla-daemon
2023-11-02  6:38 ` bugzilla-daemon
2023-11-02  6:52 ` bugzilla-daemon
2023-11-02  6:53 ` bugzilla-daemon
2023-11-02  7:08 ` bugzilla-daemon
2023-11-02  7:24 ` bugzilla-daemon
2023-11-02 13:27 ` bugzilla-daemon
2023-11-02 13:44 ` bugzilla-daemon
2023-11-02 13:46 ` bugzilla-daemon
2023-11-02 13:53 ` bugzilla-daemon
2023-11-02 13:58 ` bugzilla-daemon
2023-11-02 14:09 ` bugzilla-daemon
2023-11-02 14:11 ` bugzilla-daemon
2023-11-02 14:18 ` bugzilla-daemon
2023-11-02 14:25 ` bugzilla-daemon
2023-11-02 14:32 ` bugzilla-daemon
2023-11-02 14:46 ` bugzilla-daemon
2023-11-02 15:35 ` bugzilla-daemon
2023-11-02 15:42 ` bugzilla-daemon
2023-11-02 15:51 ` bugzilla-daemon
2023-11-02 16:29 ` bugzilla-daemon
2023-11-02 16:30 ` bugzilla-daemon
2023-11-02 16:48 ` bugzilla-daemon
2023-11-02 17:46 ` bugzilla-daemon
2023-11-02 18:04 ` bugzilla-daemon
2023-11-03  7:16 ` bugzilla-daemon [this message]
2023-11-03  9:19   ` Bagas Sanjaya
2023-11-03  9:19 ` bugzilla-daemon
2023-11-03 11:36 ` bugzilla-daemon
2023-11-03 11:42 ` bugzilla-daemon
2023-11-03 11:48 ` bugzilla-daemon
2023-11-03 12:01 ` bugzilla-daemon
2023-11-03 12:05 ` bugzilla-daemon
2023-11-03 13:36 ` bugzilla-daemon
2023-11-03 13:58 ` bugzilla-daemon
2023-11-03 14:04 ` bugzilla-daemon
2023-11-03 14:10 ` bugzilla-daemon
2023-11-03 14:55 ` bugzilla-daemon
2023-11-03 16:31 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-218092-215701-9R4neosxK8@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.