Display blacking out on boot (Macbook Linux)
Clash Royale CLAN TAG#URR8PPP
(Please note that I am breaking this out as a separate question from this one I asked earlier: How exactly do the Linux display device files work?)
I have a Linux From Scratch system that I've built (including the kernel) and installed on an Apple Macbook 2,1 (just a basic text console, no X server). The system was working fine until about a month ago, when I started experiencing problems with the display. Now, when I boot the system, the GRUB menu shows up and at that point, the display seems absolutely fine - no flicker, nothing. Perfect. However, when I go to boot LFS (in debug mode), I see a load of boot messages fly past and then the screen goes blank. I know the system is booting up, as I can login and execute commands 'blind'.
I suspected the problem may lie with the i915 GPU driver (which I've heard is notoriously buggy), so I've rebuilt the kernel to exclude the modules for i915 and drm. Basically, I just want to use the framebuffer (i.e. efifb or vesafb) and bypass the GPU entirely. However, the black screen problem keeps happening and won't go away. I've tried a lot of things and I have been digging through the logs and init files and it seems to be happening once udev loads up and starts handling uevents. I've been tinkering with the udev rules files, but can't seem to identify the particular rule that is causing the problem.
Does anyone have any idea what might be causing this? The frustrating thing is that the display seems to work perfectly when the GRUB menu comes up - it seems like if I could just get Linux to leave the display setup alone when it boots, there wouldn't be any issue.
(I should also mention that I have Libreboot installed on this Macbook, which is a version of coreboot that only includes free firmware)
boot macintosh display lfs framebuffer
asked Jan 14 at 16:48
Time4TeaTime4Tea
1,094322
|
show 6 more comments
(Please note that I am breaking this out as a separate question from this one I asked earlier: How exactly do the Linux display device files work?)
I have a Linux From Scratch system that I've built (including the kernel) and installed on an Apple Macbook 2,1 (just a basic text console, no X server). The system was working fine until about a month ago, when I started experiencing problems with the display. Now, when I boot the system, the GRUB menu shows up and at that point, the display seems absolutely fine - no flicker, nothing. Perfect. However, when I go to boot LFS (in debug mode), I see a load of boot messages fly past and then the screen goes blank. I know the system is booting up, as I can login and execute commands 'blind'.
I suspected the problem may lie with the i915 GPU driver (which I've heard is notoriously buggy), so I've rebuilt the kernel to exclude the modules for i915 and drm. Basically, I just want to use the framebuffer (i.e. efifb or vesafb) and bypass the GPU entirely. However, the black screen problem keeps happening and won't go away. I've tried a lot of things and I have been digging through the logs and init files and it seems to be happening once udev loads up and starts handling uevents. I've been tinkering with the udev rules files, but can't seem to identify the particular rule that is causing the problem.
Does anyone have any idea what might be causing this? The frustrating thing is that the display seems to work perfectly when the GRUB menu comes up - it seems like if I could just get Linux to leave the display setup alone when it boots, there wouldn't be any issue.
(I should also mention that I have Libreboot installed on this Macbook, which is a version of coreboot that only includes free firmware)
boot macintosh display lfs framebuffer
asked Jan 14 at 16:48
Time4TeaTime4Tea
1,094322
Recently my sis-in-law had a similar issue when she dropped her Macbook. Boot fine, no graphics upon boot. It was repaired...
– Rui F Ribeiro
Jan 14 at 17:20
@RuiFRibeiro ok, that's interesting. Do you know what they did to repair it?
– Time4Tea
Jan 14 at 17:44
It is quite possible that there may be a hardware issue, perhaps with the graphics chip. The booting behavior seems inconsistent and, as I mentioned, this issue seems to have developed suddenly, by itself. However, if that were the case, it seems strange that during boot, the graphics are absolutely fine, but only once Linux starts to load up that I see the problems.
– Time4Tea
Jan 14 at 17:48
1
@Time4Tea In your case I would use the other distro to mount and chroot into your problematic one. There you can install sshd and play with it remotely. Also I have a macbook 2,1 , it has 3 OSes, but... it was a good lesson to put Apple next to m$ on my boycott list.
– peterh
Jan 14 at 19:57
1
@Time4Tea You can also use some virtualization to boot the working distro, start the problematic one in a VM and play with it realtime.
– peterh
Jan 14 at 20:00
|
show 6 more comments
(Please note that I am breaking this out as a separate question from this one I asked earlier: How exactly do the Linux display device files work?)
I have a Linux From Scratch system that I've built (including the kernel) and installed on an Apple Macbook 2,1 (just a basic text console, no X server). The system was working fine until about a month ago, when I started experiencing problems with the display. Now, when I boot the system, the GRUB menu shows up and at that point, the display seems absolutely fine - no flicker, nothing. Perfect. However, when I go to boot LFS (in debug mode), I see a load of boot messages fly past and then the screen goes blank. I know the system is booting up, as I can login and execute commands 'blind'.
I suspected the problem may lie with the i915 GPU driver (which I've heard is notoriously buggy), so I've rebuilt the kernel to exclude the modules for i915 and drm. Basically, I just want to use the framebuffer (i.e. efifb or vesafb) and bypass the GPU entirely. However, the black screen problem keeps happening and won't go away. I've tried a lot of things and I have been digging through the logs and init files and it seems to be happening once udev loads up and starts handling uevents. I've been tinkering with the udev rules files, but can't seem to identify the particular rule that is causing the problem.
Does anyone have any idea what might be causing this? The frustrating thing is that the display seems to work perfectly when the GRUB menu comes up - it seems like if I could just get Linux to leave the display setup alone when it boots, there wouldn't be any issue.
(I should also mention that I have Libreboot installed on this Macbook, which is a version of coreboot that only includes free firmware)
boot macintosh display lfs framebuffer
asked Jan 14 at 16:48
Time4TeaTime4Tea
1,094322
(Please note that I am breaking this out as a separate question from this one I asked earlier: How exactly do the Linux display device files work?)
I have a Linux From Scratch system that I've built (including the kernel) and installed on an Apple Macbook 2,1 (just a basic text console, no X server). The system was working fine until about a month ago, when I started experiencing problems with the display. Now, when I boot the system, the GRUB menu shows up and at that point, the display seems absolutely fine - no flicker, nothing. Perfect. However, when I go to boot LFS (in debug mode), I see a load of boot messages fly past and then the screen goes blank. I know the system is booting up, as I can login and execute commands 'blind'.
I suspected the problem may lie with the i915 GPU driver (which I've heard is notoriously buggy), so I've rebuilt the kernel to exclude the modules for i915 and drm. Basically, I just want to use the framebuffer (i.e. efifb or vesafb) and bypass the GPU entirely. However, the black screen problem keeps happening and won't go away. I've tried a lot of things and I have been digging through the logs and init files and it seems to be happening once udev loads up and starts handling uevents. I've been tinkering with the udev rules files, but can't seem to identify the particular rule that is causing the problem.
Does anyone have any idea what might be causing this? The frustrating thing is that the display seems to work perfectly when the GRUB menu comes up - it seems like if I could just get Linux to leave the display setup alone when it boots, there wouldn't be any issue.
(I should also mention that I have Libreboot installed on this Macbook, which is a version of coreboot that only includes free firmware)
boot macintosh display lfs framebuffer
boot macintosh display lfs framebuffer
asked Jan 14 at 16:48
Time4TeaTime4Tea
1,094322
asked Jan 14 at 16:48
Time4TeaTime4Tea
1,094322
asked Jan 14 at 16:48
Time4TeaTime4Tea
1,094322
asked Jan 14 at 16:48
Time4TeaTime4Tea
1,094322
asked Jan 14 at 16:48
Time4TeaTime4Tea
1,094322
1,094322
Recently my sis-in-law had a similar issue when she dropped her Macbook. Boot fine, no graphics upon boot. It was repaired...
– Rui F Ribeiro
Jan 14 at 17:20
@RuiFRibeiro ok, that's interesting. Do you know what they did to repair it?
– Time4Tea
Jan 14 at 17:44
It is quite possible that there may be a hardware issue, perhaps with the graphics chip. The booting behavior seems inconsistent and, as I mentioned, this issue seems to have developed suddenly, by itself. However, if that were the case, it seems strange that during boot, the graphics are absolutely fine, but only once Linux starts to load up that I see the problems.
– Time4Tea
Jan 14 at 17:48
1
@Time4Tea In your case I would use the other distro to mount and chroot into your problematic one. There you can install sshd and play with it remotely. Also I have a macbook 2,1 , it has 3 OSes, but... it was a good lesson to put Apple next to m$ on my boycott list.
– peterh
Jan 14 at 19:57
1
@Time4Tea You can also use some virtualization to boot the working distro, start the problematic one in a VM and play with it realtime.
– peterh
Jan 14 at 20:00
|
show 6 more comments
Recently my sis-in-law had a similar issue when she dropped her Macbook. Boot fine, no graphics upon boot. It was repaired...
– Rui F Ribeiro
Jan 14 at 17:20
@RuiFRibeiro ok, that's interesting. Do you know what they did to repair it?
– Time4Tea
Jan 14 at 17:44
It is quite possible that there may be a hardware issue, perhaps with the graphics chip. The booting behavior seems inconsistent and, as I mentioned, this issue seems to have developed suddenly, by itself. However, if that were the case, it seems strange that during boot, the graphics are absolutely fine, but only once Linux starts to load up that I see the problems.
– Time4Tea
Jan 14 at 17:48
1
@Time4Tea In your case I would use the other distro to mount and chroot into your problematic one. There you can install sshd and play with it remotely. Also I have a macbook 2,1 , it has 3 OSes, but... it was a good lesson to put Apple next to m$ on my boycott list.
– peterh
Jan 14 at 19:57
1
@Time4Tea You can also use some virtualization to boot the working distro, start the problematic one in a VM and play with it realtime.
– peterh
Jan 14 at 20:00
Recently my sis-in-law had a similar issue when she dropped her Macbook. Boot fine, no graphics upon boot. It was repaired...
– Rui F Ribeiro
Jan 14 at 17:20
Recently my sis-in-law had a similar issue when she dropped her Macbook. Boot fine, no graphics upon boot. It was repaired...
– Rui F Ribeiro
Jan 14 at 17:20
@RuiFRibeiro ok, that's interesting. Do you know what they did to repair it?
– Time4Tea
Jan 14 at 17:44
@RuiFRibeiro ok, that's interesting. Do you know what they did to repair it?
– Time4Tea
Jan 14 at 17:44
It is quite possible that there may be a hardware issue, perhaps with the graphics chip. The booting behavior seems inconsistent and, as I mentioned, this issue seems to have developed suddenly, by itself. However, if that were the case, it seems strange that during boot, the graphics are absolutely fine, but only once Linux starts to load up that I see the problems.
– Time4Tea
Jan 14 at 17:48
It is quite possible that there may be a hardware issue, perhaps with the graphics chip. The booting behavior seems inconsistent and, as I mentioned, this issue seems to have developed suddenly, by itself. However, if that were the case, it seems strange that during boot, the graphics are absolutely fine, but only once Linux starts to load up that I see the problems.
– Time4Tea
Jan 14 at 17:48
1
1
@Time4Tea In your case I would use the other distro to mount and chroot into your problematic one. There you can install sshd and play with it remotely. Also I have a macbook 2,1 , it has 3 OSes, but... it was a good lesson to put Apple next to m$ on my boycott list.
– peterh
Jan 14 at 19:57
@Time4Tea In your case I would use the other distro to mount and chroot into your problematic one. There you can install sshd and play with it remotely. Also I have a macbook 2,1 , it has 3 OSes, but... it was a good lesson to put Apple next to m$ on my boycott list.
– peterh
Jan 14 at 19:57
1
1
@Time4Tea You can also use some virtualization to boot the working distro, start the problematic one in a VM and play with it realtime.
– peterh
Jan 14 at 20:00
@Time4Tea You can also use some virtualization to boot the working distro, start the problematic one in a VM and play with it realtime.
– peterh
Jan 14 at 20:00
|
show 6 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494457%2fdisplay-blacking-out-on-boot-macbook-linux%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494457%2fdisplay-blacking-out-on-boot-macbook-linux%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Recently my sis-in-law had a similar issue when she dropped her Macbook. Boot fine, no graphics upon boot. It was repaired...
– Rui F Ribeiro
Jan 14 at 17:20
@RuiFRibeiro ok, that's interesting. Do you know what they did to repair it?
– Time4Tea
Jan 14 at 17:44
It is quite possible that there may be a hardware issue, perhaps with the graphics chip. The booting behavior seems inconsistent and, as I mentioned, this issue seems to have developed suddenly, by itself. However, if that were the case, it seems strange that during boot, the graphics are absolutely fine, but only once Linux starts to load up that I see the problems.
– Time4Tea
Jan 14 at 17:48
1
@Time4Tea In your case I would use the other distro to mount and chroot into your problematic one. There you can install sshd and play with it remotely. Also I have a macbook 2,1 , it has 3 OSes, but... it was a good lesson to put Apple next to m$ on my boycott list.
– peterh
Jan 14 at 19:57
1
@Time4Tea You can also use some virtualization to boot the working distro, start the problematic one in a VM and play with it realtime.
– peterh
Jan 14 at 20:00