X86 platform drivers
 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: Thu, 02 Nov 2023 14:32:59 +0000	[thread overview]
Message-ID: <bug-218092-215701-CIggyEIeN7@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 #33 from Ertugrul Uyar (ertugruluyar.personal@gmail.com) ---
(In reply to Ertugrul Uyar from comment #32)
> (In reply to Ertugrul Uyar from comment #31)
> > (In reply to Ertugrul Uyar from comment #30)
> > > (In reply to Ertugrul Uyar from comment #29)
> > > > (In reply to Mario Limonciello (AMD) from comment #28)
> > > > > Yeah like I said, you need to install build dependencies.  You can do
> > > them
> > > > > manually one by one or you can use 'sudo apt build-dep
> $SOURCE_PACKAGE'
> > > to
> > > > > do it.
> > > > > 
> > > > > I don't know the name of the source package used for Tuxedo.  It's
> > > > something
> > > > > like this:
> > > > > 
> > > > > # sudo apt build-dep linux-image
> > > > 
> > > > I tried this: https://phoenixnap.com/kb/build-linux-kernel
> > > > sudo apt-get install git fakeroot build-essential ncurses-dev xz-utils
> > > > libssl-dev bc flex libelf-dev bison
> > > > And it's start to build. Then I keep enter to choose default options
> for
> > > > questions.
> > > 
> > > Then I get this and installed the missing deppendency.
> > > 
> > > dpkg-buildpackage --build=binary --no-pre-clean --unsigned-changes
> > > --rules-file='make -f debian/rules' --jobs=1 -r'fakeroot -u' -a$(cat
> > > debian/arch)
> > > dpkg-buildpackage: info: source package linux-upstream
> > > dpkg-buildpackage: info: source version 6.6.0-1
> > > dpkg-buildpackage: info: source distribution jammy
> > > dpkg-buildpackage: info: source changed by ertugruluyar
> > > <ertugruluyar@ertugruluyar-pc>
> > > dpkg-buildpackage: info: host architecture amd64
> > >  dpkg-source --before-build .
> > > dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper
> > > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
> > > aborting
> > > dpkg-buildpackage: warning: (Use -d flag to override.)
> > > make[2]: *** [scripts/Makefile.package:146: bindeb-pkg] Error 3
> > > make[1]: *** [/home/ertugruluyar/Desktop/linux-6.6/Makefile:1538:
> > > bindeb-pkg] Error 2
> > > make: *** [Makefile:234: __sub-make] Error 2
> > 
> > It did things that start CC ... then I get error a few minutes later:
> > make[5]: *** [Makefile:1913: .] Error 2
> > make[4]: *** [Makefile:359: __build_one_by_one] Error 2
> > make[3]: *** [debian/rules:25: build-arch] Error 2
> > dpkg-buildpackage: error: make -f debian/rules binary subprocess returned
> > exit status 2
> > make[2]: *** [scripts/Makefile.package:146: bindeb-pkg] Error 2
> > make[1]: *** [/home/ertugruluyar/Desktop/linux-6.6/Makefile:1538:
> > bindeb-pkg] Error 2
> > make: *** [Makefile:234: __sub-make] Error 2
> 
> Then I did this:
> https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
> sudo apt-get install libncurses-dev gawk flex bison openssl libssl-dev dkms
> libelf-dev libudev-dev libpci-dev libiberty-dev autoconf llvm

I got the same error.

-- 
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-02 14:33 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 [this message]
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
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-CIggyEIeN7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox