LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 03-02-2017, 10:18 PM   #16
qunying
Member
 
Registered: Jun 2002
Distribution: Slackware
Posts: 105

Rep: Reputation: 37

What's your Macbook Pro version? Do you still have the OS X partition? If you could not boot back to OS X, you may try to reset it to its factory default. Then you could try to boot from refind (install refind from OS X on to an EFI partition).
You may still need to install Slackware under legacy mode, but don't install other boot manager and manually copy the kernel to the EFI partion and setup bootup script accordingly. Then boot with refind with kernel option "video=efifb".
 
Old 03-18-2017, 11:52 AM   #17
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Ubuntu MATE
Posts: 137
Blog Entries: 2

Original Poster
Rep: Reputation: 16
Hey guys, thanks for both suggestions. Just an update:

* I don't have the OS X partition any more. I tried a recovery but when I had to select which drive to install OS X to, there weren't any drives to choose! Whatever I did to get Ubuntu on this machine, it's removed the ability for the Mac recovery software to detect the drive.

* I've found a live version of Slackware (Liveslak, under the theory that it's a video problem, maybe getting a live version running will allow the install to complete). So the live version runs, but when I try to install it runs out of disk space. The filesystem partition is like ~450 G, so something strange is happening with the install script. Maybe it's trying to install to the /boot/efi partition...?

So, next I'm going to get Ubuntu back on there and try to install reFIND to the EFI partition from Linux. I'll report back.
 
Old 03-18-2017, 12:00 PM   #18
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware64-14.2
Posts: 181

Rep: Reputation: 55
If you are trying to reinstall OS X you might need to reformat the drives using the OS X install media's disk utilities. As far as using the Slackware live to install, I have no exp. I still think you would have an easier time if you used refind or refit to boot the standard Slackware install media.

For whatever it is worth, when I try to boot elilo directly on my macbook pro with stock Slackware install media I have video issues, but booting the Slackware install media with reind fixes those issues. I think elilo could be tweaked to work right but I just have an easier time using refind.

Last edited by khronosschoty; 03-18-2017 at 12:03 PM.
 
Old 03-18-2017, 02:33 PM   #19
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 3,589

Rep: Reputation: 1733Reputation: 1733Reputation: 1733Reputation: 1733Reputation: 1733Reputation: 1733Reputation: 1733Reputation: 1733Reputation: 1733Reputation: 1733Reputation: 1733
Quote:
Originally Posted by thethinker View Post
* I've found a live version of Slackware (Liveslak, under the theory that it's a video problem, maybe getting a live version running will allow the install to complete). So the live version runs, but when I try to install it runs out of disk space. The filesystem partition is like ~450 G, so something strange is happening with the install script. Maybe it's trying to install to the /boot/efi partition...?
First off, just some clarification, it is called Slackware Live. liveslak is the collection of scripts used to generate the ISOs, but is not the actual "distro" (if you want to call it that). I've seen Eric correct that on the forum before, so I just wanted to give you the heads up.

And if you install Slackware from within Slackware Live, you'll pretty much end up with a regular Slackware install, so you shouldn't see any difference from using a regular Slackware install disc.

As to the actual problem you're having, while Eric will sometimes respond on the forum to support his projects, he prefers bug reports to be reported on his blog (probably because Slackware Live isn't an official Slackware project... at least, not yet). So if you continue to run into issues with the installation script, I would post a comment on his blog to see if he can help you out.

Good luck
 
2 members found this post helpful.
Old 03-18-2017, 06:16 PM   #20
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
First off, just some clarification, it is called Slackware Live. liveslak is the collection of scripts used to generate the ISOs, but is not the actual "distro" (if you want to call it that). I've seen Eric correct that on the forum before, so I just wanted to give you the heads up.
Thank you!

Quote:
Originally Posted by bassmadrigal View Post
And if you install Slackware from within Slackware Live, you'll pretty much end up with a regular Slackware install, so you shouldn't see any difference from using a regular Slackware install disc.
Yes, but the issue is the installation process - it blackscreens at the start of it. At least when using the Slackware Live installation, the windows manager is already running so my hope is that whatever setting that made that happen will get copied to the installation.
 
Old 03-19-2017, 09:16 PM   #21
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Ubuntu MATE
Posts: 137
Blog Entries: 2

Original Poster
Rep: Reputation: 16
Alright - I have a solution.

Short answer: I believe the problem would have been fixed long ago by installing using the full "terse" install. When the system was apparently hanging, it was actually installing, but incompletely. Using the 1 line per package install allowed the prompts at the end to be entered correctly and the system installed correctly.

Longer: To make it actually work I figured out how to recovery the Mac install (disk recovery), and then used rEFInd. Additionally, after a dual OS X / Ubuntu boot, I had to remake the hybrid MBR to ensure Slackware could see the partition (just using the GPT table was not enough). I added the Mac partition, the Ubuntu partition, and the Slack partition to the hybrid MBR, and made them all bootable.

However, the short answer might have been fine all along - I'm not sure the extra work in the long answer would have been required if I hadn't been screwing with the partition table in the first place when I removed OS X.

Thanks for everyone's help - all your explorations lead me to the right answer!
 
Old 03-19-2017, 09:52 PM   #22
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware64-14.2
Posts: 181

Rep: Reputation: 55
Quote:
Originally Posted by thethinker View Post
Alright - I have a solution.

Short answer: I believe the problem would have been fixed long ago by installing using the full "terse" install. When the system was apparently hanging, it was actually installing, but incompletely. Using the 1 line per package install allowed the prompts at the end to be entered correctly and the system installed correctly.

Longer: To make it actually work I figured out how to recovery the Mac install (disk recovery), and then used rEFInd. Additionally, after a dual OS X / Ubuntu boot, I had to remake the hybrid MBR to ensure Slackware could see the partition (just using the GPT table was not enough). I added the Mac partition, the Ubuntu partition, and the Slack partition to the hybrid MBR, and made them all bootable.

However, the short answer might have been fine all along - I'm not sure the extra work in the long answer would have been required if I hadn't been screwing with the partition table in the first place when I removed OS X.

Thanks for everyone's help - all your explorations lead me to the right answer!
I cannot think of one "valid" reason why using the "full terse" option would solve "the issue".

Edit: I just wanted to make a note here so that its known I posted this comment as a "red flag", to indicate that there might be other "issues" at play here.

Last edited by khronosschoty; 03-19-2017 at 10:26 PM.
 
Old 03-19-2017, 11:30 PM   #23
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 khronosschoty View Post
I cannot think of one "valid" reason why using the "full terse" option would solve "the issue".

Edit: I just wanted to make a note here so that its known I posted this comment as a "red flag", to indicate that there might be other "issues" at play here.
All that is fine, if you think appropriate - I'm just saying "the issue" was that "when trying to install Slackware on a Mac, I got a weird blackscreen with flickering edges".

Then, I did a bunch of random things with partitions, OS X installs, and MBR recoveries.

I tried to install Slackware again, and again got a weird blackscreen with flickering edges.

Then, I rebooted, but noticed that *something* got installed as "Slackware" on that partition. It wouldn't boot, but it was something.

So, I reinstalled with line-by-line package list (i.e. "terse" install), and it worked fine, now I have a running install of Slackware.

I can't confirm anything because I didn't install on the same system I started with, but the issue was identical ("weird blackscreen with flashing edges during install") and the problem was immediately solved after switching to a terse install.
 
Old 03-19-2017, 11:39 PM   #24
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware64-14.2
Posts: 181

Rep: Reputation: 55
Quote:
Originally Posted by thethinker View Post
All that is fine, if you think appropriate - I'm just saying "the issue" was that "when trying to install Slackware on a Mac, I got a weird blackscreen with flickering edges".

Then, I did a bunch of random things with partitions, OS X installs, and MBR recoveries.

I tried to install Slackware again, and again got a weird blackscreen with flickering edges.

Then, I rebooted, but noticed that *something* got installed as "Slackware" on that partition. It wouldn't boot, but it was something.

So, I reinstalled with line-by-line package list (i.e. "terse" install), and it worked fine, now I have a running install of Slackware.

I can't confirm anything because I didn't install on the same system I started with, but the issue was identical ("weird blackscreen with flashing edges during install") and the problem was immediately solved after switching to a terse install.
I'm going to guess there might be some kind of disk issue going on, but its just a wild guess.

But switching to "terse" is not intended as a fix for anything, as far as I know.

Last edited by khronosschoty; 03-19-2017 at 11:41 PM.
 
  


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 12:24 PM.

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