All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101029] notebook does not work when not booted using nomodeset AMD APU
Date: Wed, 17 May 2017 02:45:10 +0000	[thread overview]
Message-ID: <bug-101029-502-KTWzyPstO2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101029-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 880 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=101029

--- Comment #7 from Craig <stein12c@gmail.com> ---
(In reply to Craig from comment #6)
> Created attachment 131377 [details]
> Bootup Screenshot

I am running Ubuntu 17.04. Anyways I have checked through the logs (kern.log,
syslog  and it appears that the last time it recorded anything in them was when
I was using "nomodeset" on bootup.  I have attached screenshots of what I get
when I boot up without nomodeset as a parameter.  Is it possible that it is not
writing to disk when I bootup without "nomodeset"? There is no dmesg log in the
/var/log folder. It appears that I could use journalctl -b but that only works
if I am able to boot into the system or the dmesg command but also needs to be
able to boot into it to run that.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1964 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-05-17  2:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-13  7:36 [Bug 101029] notebook does not work when not booted using nomodeset AMD APU bugzilla-daemon
2017-05-13  7:36 ` bugzilla-daemon
2017-05-15  9:16 ` bugzilla-daemon
2017-05-15 13:33 ` bugzilla-daemon
2017-05-16  2:20 ` bugzilla-daemon
2017-05-17  1:30 ` bugzilla-daemon
2017-05-17  1:36 ` bugzilla-daemon
2017-05-17  2:44 ` bugzilla-daemon
2017-05-17  2:45 ` bugzilla-daemon [this message]
2017-05-17  2:48 ` bugzilla-daemon
2017-05-17  2:51 ` bugzilla-daemon
2017-05-17  3:19 ` bugzilla-daemon
2017-05-17  4:29 ` bugzilla-daemon
2017-05-17  4:31 ` bugzilla-daemon
2017-05-17  4:31 ` bugzilla-daemon
2017-05-17  6:25 ` bugzilla-daemon
2017-05-17  8:46 ` bugzilla-daemon
2017-05-17 12:56 ` bugzilla-daemon
2017-05-17 12:58 ` bugzilla-daemon
2017-05-17 23:37 ` bugzilla-daemon
2017-05-18  2:05 ` bugzilla-daemon
2017-05-18  2:40 ` bugzilla-daemon
2017-05-18  2:59 ` bugzilla-daemon
2017-05-18 17:29 ` bugzilla-daemon
2017-05-18 18:35 ` bugzilla-daemon
2017-05-21 14:20 ` bugzilla-daemon
2017-05-22  1:12 ` bugzilla-daemon
2017-05-22 10:25 ` bugzilla-daemon
2019-11-19  8:17 ` 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-101029-502-KTWzyPstO2@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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.