LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-09-2016, 01:00 PM   #1
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Ubuntu MATE
Posts: 137
Blog Entries: 2

Rep: Reputation: 16
Unhappy Slackware 14.2 Installation hangs on Macbook Pro


Hey All,
I'm having trouble installing the latest Slackware on my Macbook Pro. Previously, this Mac ran OSX and Xubuntu, although I corrupted the boot process in some way so that it just booted right into Xubuntu, not even going to any rEFInd or GRUB manager. Anyway, I don't think that's the problem because I can't even get through the Slack installation.

After booting from a DVD, I set up partitions and the installation starts fine. Then, at some point, the screen goes into a strange blinking state. It's essentially black except for some flickering colored lines on one side. My guess is some video issue, but anyway it hangs there for at least ~30 min, with no HD noise before I give up.

Anyone have any thoughts? Is there maybe some video fix I can pass to the kernel at boot, or a package I can avoid installing that is maybe doing this?

Thanks!

(I've since successfully installed Ubuntu GNOME on this machine, with the same boot behavior. So whatever kind of witchcraft I did with rEFInd, it seems persistent and harmless :-) )
 
Old 07-09-2016, 01:40 PM   #2
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: Slackware
Posts: 7,219

Rep: Reputation: 2627Reputation: 2627Reputation: 2627Reputation: 2627Reputation: 2627Reputation: 2627Reputation: 2627Reputation: 2627Reputation: 2627Reputation: 2627Reputation: 2627
Maybe checksum-verify the DVD you burned?
 
1 members found this post helpful.
Old 07-09-2016, 02:56 PM   #3
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Ubuntu MATE
Posts: 137
Blog Entries: 2

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by dugan View Post
Maybe checksum-verify the DVD you burned?
Verified. Although I don't know about such things, I downloaded HashCheck on Windows and ran the .iso.md5 file through it, and it verified the iso as matching. I suppose there could have been a burning problem, so maybe I'll try that again, but I have no reason to think that happened.

EDIT: Just reburned with "verification" (whatever that means on Windows) and getting the same behavior. I noticed that it happens in different places during the installation process, and not at a single package install.

Last edited by thethinker; 07-09-2016 at 04:26 PM.
 
Old 07-09-2016, 05:40 PM   #4
Gerard Lally
Senior Member
 
Registered: Sep 2009
Location: Ireland
Distribution: Slackware64, Crux64, NetBSD64
Posts: 1,118

Rep: Reputation: 658Reputation: 658Reputation: 658Reputation: 658Reputation: 658Reputation: 658
Quote:
Originally Posted by thethinker View Post
Verified. Although I don't know about such things, I downloaded HashCheck on Windows and ran the .iso.md5 file through it, and it verified the iso as matching. I suppose there could have been a burning problem, so maybe I'll try that again, but I have no reason to think that happened.

EDIT: Just reburned with "verification" (whatever that means on Windows) and getting the same behavior. I noticed that it happens in different places during the installation process, and not at a single package install.
It might be an idea to eliminate bad memory first. Run a memtest, or else remove one stick of memory at a time till you find the culprit. Yes, the Ubuntu installation sailed past with flying colours, but memory errors are random. Like London buses, you might not see one for ages, and then they all come together.
 
1 members found this post helpful.
Old 07-09-2016, 06:58 PM   #5
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Ubuntu MATE
Posts: 137
Blog Entries: 2

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by gezley View Post
It might be an idea to eliminate bad memory first. Run a memtest, or else remove one stick of memory at a time till you find the culprit. Yes, the Ubuntu installation sailed past with flying colours, but memory errors are random. Like London buses, you might not see one for ages, and then they all come together.
memtest passed - which is probably good, since this is a Macbook and having the ability to change the memory is not something iJobs wants you to have. Anyway, apparently not a RAM issue.

Last edited by thethinker; 07-09-2016 at 07:15 PM.
 
Old 07-09-2016, 07:45 PM   #6
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 3,592

Rep: Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738
Maybe you could try adding nomodeset to the boot options to see if it is a kms issue.
 
1 members found this post helpful.
Old 07-09-2016, 10:54 PM   #7
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Ubuntu MATE
Posts: 137
Blog Entries: 2

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by bassmadrigal View Post
Maybe you could try adding nomodeset to the boot options to see if it is a kms issue.
Same result :-/ I don't have much experience here, but what I did is just when the installer went to boot (before the automatic timeout to huge.s) I passed the commands

Code:
huge.s nomodeset
Everything else proceeded exactly the same - random hang in the middle with crazy graphical artifacts. And I've now installed Xubuntu as well - I'm confident this is something the Slackware installer is doing differently then the Ubuntu installer. I would love Slackware over Ubuntu!! Any thoughts?
 
Old 07-09-2016, 11:43 PM   #8
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 3,592

Rep: Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738
What video hardware do you have on there? Also, what is Ubuntu's kernel append line for booting? I'm wondering if it's passing something different than what Slackware is passing (which is likely nothing other than the kernel, since Slackware doesn't want to assume certain hardware setups).
 
1 members found this post helpful.
Old 07-10-2016, 11:27 PM   #9
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Ubuntu MATE
Posts: 137
Blog Entries: 2

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by bassmadrigal View Post
What video hardware do you have on there? Also, what is Ubuntu's kernel append line for booting? I'm wondering if it's passing something different than what Slackware is passing (which is likely nothing other than the kernel, since Slackware doesn't want to assume certain hardware setups).
Great questions! Exactly why I come here.

Code:
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
To me, this seems pretty generic and not likely the cause.

I like your idea about passing things to the kernel, mimicking something that works (Ubuntu). We are getting out of my comfort zone, but here is everything inside of /etc/default/grub which is not commented out:

Code:
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
To me, I think the answer to your question is "only quiet splash".

Unfortunately, I am out of town and won't be able to work on this for ~1 week, but I appreciate everyone's attention, and I will return to it. I'm been missing my Slackware, and I'm forced into Mac hardware for political/economic reasons, so this is important to me!
 
Old 07-11-2016, 06:43 AM   #10
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 3,592

Rep: Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738
Ok, let's try to get a bit more detail on this. What is the output of the following two commands?

Code:
lspci -k | grep -iA3 video
cat /proc/cmdline
It'd probably be beneficial to run them on both Slackware and Ubuntu so we can compare the output.
 
Old 07-12-2016, 09:17 AM   #11
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Ubuntu MATE
Posts: 137
Blog Entries: 2

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by bassmadrigal View Post
Ok, let's try to get a bit more detail on this. What is the output of the following two commands?

Code:
lspci -k | grep -iA3 video
cat /proc/cmdline
It'd probably be beneficial to run them on both Slackware and Ubuntu so we can compare the output.
Well, I can't install Slackware at all, so I can't run them there. I know there is Slackware Live Edition, so when I can get around to getting that up and running I will. For now, here's what happens when I run these in Xubuntu:

Code:
$ lspci -k | grep -iA3 video
$
Literally nothing - so I guess "video" is not found as output from lspci.

Code:
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0cd15a88-63ed-40b8-aa6f-18963737ca23 ro quiet splash vt.handoff=7
That tell us anything?
 
Old 07-12-2016, 09:33 AM   #12
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 3,592

Rep: Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738Reputation: 1738
Quote:
Originally Posted by thethinker View Post
Well, I can't install Slackware at all, so I can't run them there. I know there is Slackware Live Edition, so when I can get around to getting that up and running I will. For now, here's what happens when I run these in Xubuntu:

Code:
$ lspci -k | grep -iA3 video
$
Literally nothing - so I guess "video" is not found as output from lspci.

Code:
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0cd15a88-63ed-40b8-aa6f-18963737ca23 ro quiet splash vt.handoff=7
That tell us anything?
Sorry, that should be

Code:
lspci -k | grep -iA3 vga
As for not being able to install Slackware, you should still be able to do the lspci command from a terminal when you boot off the installation disc before you run setup. /proc/cmdline will probably also be available, although, it will probably be pretty sparse.

Unfortunately, I don't see anything that stands out with the cmdline, so I'm not sure if there's any appends that could help.
 
1 members found this post helpful.
Old 07-12-2016, 10:02 PM   #13
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Ubuntu MATE
Posts: 137
Blog Entries: 2

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by bassmadrigal View Post
Sorry, that should be

Code:
lspci -k | grep -iA3 vga
As for not being able to install Slackware, you should still be able to do the lspci command from a terminal when you boot off the installation disc before you run setup. /proc/cmdline will probably also be available, although, it will probably be pretty sparse.

Unfortunately, I don't see anything that stands out with the cmdline, so I'm not sure if there's any appends that could help.
Alright take #2. You've got the cmdline output, now the correct lspci thing:

Code:
$ lspci -k | grep -iA3 vga
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
	Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller
	Kernel driver in use: i915
	Kernel modules: i915
As for the Slackware version, I did as you said and ran it after booting into the install disk, I've got a dropbox link (I can't put images right into messages, right?):

https://dl.dropboxusercontent.com/u/...712_224926.jpg

If the image doesn't jive with you, it appears Slackware recognizes the hardware correctly but either can't list the driver/modules or doesn't know/have them. Not sure what else to say, except that the kernel is indeed getting passed the "nomodeset" at startup, so that's likely not the problem. I also notice a ".efi" on the kernel name in the Xubuntu version, but I thought huge.s was supposed to have that kind of stuff activated.

Another piece of information: I was successful in making a 32-bit live USB drive and booting into it, but for several reasons I decided to make a 64 bit one. Both attempts (the standard 14.2 and then with the XFCE desktop) failed. I got a "GRUB!" line, but instead of options it simply gave me an error:

Code:
alloc magic is broken at <memory address blah blah blah>
I can't imagine this matters, I'm running 64 bit Xubuntu right now, but anyway...

Last edited by thethinker; 07-12-2016 at 10:03 PM. Reason: Including some EFI info
 
Old 02-26-2017, 11:56 AM   #14
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Ubuntu MATE
Posts: 137
Blog Entries: 2

Original Poster
Rep: Reputation: 16
Some possible more information on this issue, if anyone is still listening...

This laptop is now running Ubuntu MATE (and previously ran Xubuntu with no install issues), and I noticed something similar about the Slackware failed install and the startup process that happens under MATE: When the Slackware install failed, I was getting a not *quite* blackscreen, but a blackscreen with just a hint of some horizontal lines around the outside. It appears that I get this same screen when I *start* Ubuntu MATE (and possible Xubuntu). So my thought is that Ubuntu is setting something on startup to fix some issue with the screen that Slackware, during the install, is *not* setting.

So, can someone help me figure out what kinds of graphics setup commands Ubuntu is using? I suspect this is *before* X11 starts up, but I can't guarantee that because it's happening in the middle of the Slackware install, but after I select packages.
 
Old 03-01-2017, 03:00 PM   #15
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware64-14.2
Posts: 181

Rep: Reputation: 55
Maybe try using something like refind or refit to boot the Slackware install media? that is if you have not already tried that. Possible in combination with refit and refind try bios emulation mode too if your macbook has that mode. These are just things I would try out if I was having issues with a macbook.

Last edited by khronosschoty; 03-03-2017 at 01:18 AM.
 
  


Reply

Tags
installation, macbook pro, slackware 14.2


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Gentoo Installation on Macbook Pro wamj Gentoo 2 01-31-2016 11:48 PM
Installer Hangs on MacBook Pro [Video showing problem] cody.lilley Slackware - Installation 5 05-07-2014 03:33 PM
[SOLVED] Slackware on a 17" Macbook Pro ger579 Slackware 6 12-29-2013 07:23 AM
Slackware 12 on MacBook Pro geoff.cardamone Slackware 14 01-19-2012 08:44 AM
Slackware 13.0 Apple MacBook Pro Zackney Linux - Laptop and Netbook 2 10-24-2009 12:09 PM


All times are GMT -5. The time now is 03:33 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration