15:38 <Jackneill> TJ-, for a brief moment i saw 2-3 lines of text, first line
is "error: no video mode activated"
15:38 <Jackneill> was unable to see more.
15:38 <Jackneill> but this is a successful boot no purple screen this time
15:38 <TJ-> Jackneill: so, GRUB_TERMINAL=console was successfully booted to
desktop?
15:39 <Jackneill> TJ-, yes, but its non-determinitsitc so its hard to tell
15:39 <Jackneill> if the error still exists or not
15:39 <Jackneill> requires many boots.
...
15:43 <Jackneill> TJ-, i got a bad boot this time.
15:43 <Jackneill> TJ-, hanging black screen with 2 lines: first is what i said
above, second: 'error: can't find command `hwmatch`'
15:45 <TJ-> Jackneill: the fact you can see the text is a good thing, as it may
point to the issue not being video at all, but possibly something else that is
hanging the entire system
...
15:49 <TJ-> Jackneill: "hwmatch" is part of the GRUB boot-loader, and (is
supposed) to be executed by GRUB at boot-time to check if the GPU is included
in a blacklist: "/boot/grub/grub.cfg:122: if hwmatch
${prefix}/gfxblacklist.txt 3; then ..." - so it appears the hand-over from GRUB
to Linux kernel is failing
So, in GRUB GFX mode, which sets the background colour to the Ubuntu
themed 'purple' mentioned in this bug, the display is cleared when GRUB
hands over to the Linux kernel. If the kernel is not starting for some
reason that purple screen is all the user will see.
With GRUB_TERMINAL=console the display is not in a GFX mode, but text
only, so we get to see some clue at least!
--
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/1829402
Title:
Purple screen hangup during boot
Status in linux package in Ubuntu:
Confirmed
Bug description:
Specs:
Ubuntu 19.04 fresh install, everything updated
Firmware is latest (Bios version 300)
Asus vivobook s14
LVM disk encryption
Steps to reproduce:
- Install ubuntu 19.04/18.10
- Reboot
- Purple screen indefinitely
Setting kernel cmdline args only to ro nomodeset seems solves it.
After some debugging session with #ubuntu with different cmdline args,
it seems now the default one works too. I have not edited anything,
but now i am unable to reproduce it.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-15-generic 5.0.0-15.16
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: markbartos 1778 F.... pulseaudio
Date: Thu May 16 17:15:07 2019
InstallationDate: Installed on 2019-05-16 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 13d3:3526 IMC Networks
Bus 001 Device 002: ID 13d3:56c1 IMC Networks
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X430FA_S430FA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.0.0-15-generic N/A
linux-backports-modules-5.0.0-15-generic N/A
linux-firmware 1.178.1
SourcePackage: linux
StagingDrivers: r8822be
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/22/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X430FA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X430FA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrX430FA.300:bd11/22/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX430FA_S430FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X430FA_S430FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829402/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
