LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
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 01-23-2015, 10:02 AM   #1
badbetty
Member
 
Registered: Jan 2014
Posts: 159

Rep: Reputation: Disabled
Slackware 14.1 'isolinux prepared' confusion


This is probably yet another tedious topic about installing Slackware (14.1 in this case) on to a computer, from a USB flash drive.

Looking through some of the help files on t'internet, I noted a comment saying that Slackware 14.1 .iso is pre-processed using isolinux so it can be written directly to a usb stick for instance.

Other sources, give a more elaborated (and probably how it should be done if you need to understand things) approach using files such as usbboot.img, extracting iso or using a package tree and other things. These seem related to earlier releases however.

In the past with other distros, I have been able to 'dd' the .iso to the formatted usb device and just boot and install.

Please will someone clear up my mind-melt and confirm if it is possible to write the slack14.1 .iso to the usb (e.g dd if=slack.iso of=/dev/sdb etc..), put the stick in the machine and install from it ?

Or, is it still the more elaborated affair in which case what is the statement about Slack 14.1 and the pre-processed with isolinux etc ?

A few links - the first one seems incomplete and mentions syslinux but not what you do with it before writing the .iso .

http://slackwiki.com/Install_Slackwa...SB_Flash_Drive
http://docs.slackware.com/slackware:install


Thank you for your guidance and comments.
 
Old 01-23-2015, 10:27 AM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,059

Rep: Reputation: Disabled
Slackware ISOs are not post-processes, that's right.

Type this:
Code:
isohybrid -h 255 -s 63 /path/to/the/ISO
Then insert your USB stick, triple check its device name then run dd.

Alternatively you can use one of the Slint ISOs available here as they are already post-processed.

Details about installation are there.

Last edited by Didier Spaier; 01-23-2015 at 10:29 AM.
 
Old 01-23-2015, 10:40 AM   #3
badbetty
Member
 
Registered: Jan 2014
Posts: 159

Original Poster
Rep: Reputation: Disabled
@Didier

Quote:
Originally Posted by Didier Spaier View Post
Slackware ISOs are not post-processes, that's right.

Type this:
Code:
isohybrid -h 255 -s 63 /path/to/the/ISO

Are you sure?

Because in one of the links I posted (from docs.slackware.com) is the following:

"..Starting with the 14.1 release, Slackware ISO images (both the ones available online as well as the discs sent out from the Slackware store) have been processed using isohybrid. This ..."

Hence my confusion and this thread.

Thank you
 
Old 01-23-2015, 10:43 AM   #4
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,059

Rep: Reputation: Disabled
No I am not sure, I didn't check recently. Just try to dd the ISO image directly then.

PS But then, the files /isolinux/README.TXT in the file trees of Slackware version 14.1 have not been updated to reflect that change as they still state:
Quote:
As an additional step, the ISO image may be processed to make it bootable
when written to a USB stick. This processing will not impact the ISO's
ability to boot from DVD media. Use the following command to do this:

isohybrid /tmp/slackware-dvd.iso
PPS In, case you wonder, setting the number of heads to 255 and the number of sectors to 63 (maximum allowed in both cases) is just to prevent having more than 1024 cylinders, not allowed by old BIOS.

Last edited by Didier Spaier; 01-23-2015 at 11:08 AM. Reason: PPS added.
 
Old 01-23-2015, 12:08 PM   #5
badbetty
Member
 
Registered: Jan 2014
Posts: 159

Original Poster
Rep: Reputation: Disabled
@Didier

Thank you. I will explore some more along the lines you advised.

I did try 'dd' the 14.1 iso to a usb before my OP, but it wouldn't boot.

If any one else is able to have a go and see if 'dd' to usb of the 14.1 iso successfully boots to the install process, that would be useful to know.

Thank you for any comments on that.
 
Old 01-23-2015, 12:56 PM   #6
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,059

Rep: Reputation: Disabled
Well, I just checked and the file slackware-14.1-install-dvd.iso _is_ pre-processed, so I assume that you can't boot off your USB installer for another reason.
  1. Is it 32-bit or a 64-bit edition?
  2. Did you check the integrity of the ISO with md5sum?
  3. Are you sure that your firmware (BIOS or UEFI) is properly set up to boot off an USB drive?

I remind that in case of an UEFI firmware set to boot off an UEFI equipped device only, you should use a 64-bit Slackware 14.1

Last edited by Didier Spaier; 01-23-2015 at 01:08 PM.
 
Old 01-23-2015, 01:35 PM   #7
moisespedro
Senior Member
 
Registered: Nov 2013
Location: Brazil
Distribution: Slackware
Posts: 1,223

Rep: Reputation: 195Reputation: 195
I've always installed Slackware using a USB stick. dd always worked.
 
Old 01-23-2015, 01:43 PM   #8
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,059

Rep: Reputation: Disabled
Quote:
Originally Posted by moisespedro View Post
I've always installed Slackware using a USB stick. dd always worked.
This information doesn't help to solve the OP's issue. You most probably don't the same hardware and firmware.

Last edited by Didier Spaier; 01-23-2015 at 01:55 PM.
 
Old 01-23-2015, 04:38 PM   #9
saulgoode
Member
 
Registered: May 2007
Distribution: Slackware
Posts: 288

Rep: Reputation: 155Reputation: 155
Quote:
Originally Posted by Didier Spaier View Post
PPS In, case you wonder, setting the number of heads to 255 and the number of sectors to 63 (maximum allowed in both cases) is just to prevent having more than 1024 cylinders, not allowed by old BIOS.
A little off-topic, but isn't that concern only for BIOSes older than 1998? Is this still an issue?
 
Old 01-23-2015, 05:11 PM   #10
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,059

Rep: Reputation: Disabled
Quote:
Originally Posted by saulgoode View Post
A little off-topic, but isn't that concern only for BIOSes older than 1998? Is this still an issue?
Not sure about that but at least that prevents to get a warning like:
Code:
isohybrid: Warning: more than 1024 cylinders: 1045
I hope that no one will open the USB stick to count the rotating platters
 
Old 01-24-2015, 09:35 AM   #11
badbetty
Member
 
Registered: Jan 2014
Posts: 159

Original Poster
Rep: Reputation: Disabled
good day to all

As suggested above, I have verified the Slack 14.1 iso with md5sum after download.

I have tried to install the Slack iso on various machines. The iso is documented on slackware as having been prepared with isolinux so it can be installed directly off a USB flash stick (well that's how I understand it).

It was written to the USB stick using 'dd'. The stick was previously cleared with cfdisk to a partition of type 'b', made bootable and formatted with 'mkfs.vfat -F 32' just to reset it so to speak. Then 'dd' was issued to write it using dd if=slack.iso of=/dev/sd(x) bs=1M .

It failed to boot to install from 3 different machines (one intel, one amd etc all with different specs).

So, I downloaded a Mageia iso and repeated all the above steps. This worked fine.

I'm not sure what to conclude just yet, so I will try download a different Slack iso and try.


Thank you

Last edited by badbetty; 01-24-2015 at 09:36 AM.
 
Old 01-24-2015, 09:36 AM   #12
j_v
Member
 
Registered: Oct 2011
Distribution: Slackware64
Posts: 364

Rep: Reputation: 67
I'm curious about the system (both hardware and system software) that the OP is working from. Seems like mostly guess work trying to figure out the error message.

EDIT:
I must have been typing when you posted your last. What was the system that gave the cylinders error?

Last edited by j_v; 01-24-2015 at 09:38 AM.
 
Old 01-24-2015, 09:56 AM   #13
badbetty
Member
 
Registered: Jan 2014
Posts: 159

Original Poster
Rep: Reputation: Disabled
[solved]

Oh dear, I must apologise for wasting time on this!

I am a first class idiot.

I mounted the iso as a loop device to see what was in it. It turned out to be the source DVD iso !!! arrghhh

I had renamed the files I had downloaded (to make it shorter) and had not realised I was using the wrong one. I am sorry. How embarrassing and deserve to be mocked :-) Feel free.


Lesson learned.
 
Old 01-24-2015, 09:56 AM   #14
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,059

Rep: Reputation: Disabled
Quote:
Originally Posted by badbetty View Post
The stick was previously cleared with cfdisk to a partition of type 'b', made bootable and formatted with 'mkfs.vfat -F 32' just to reset it so to speak. Then 'dd' was issued to write it using dd if=slack.iso of=/dev/sd(x) bs=1M
It is completely useless to partition the USB stick with cfdisk and create a file system in this case. My guess is when using the dd command you wrongly wrote to a partition (the one you created) instead of the device itself.

Instead, plug in your USB stick then issue following command (I show also its output in my system):
Code:
~$ lsblk -o name,size,type,model,fstype,mountpoint
NAME     SIZE TYPE MODEL            FSTYPE MOUNTPOINT
sda    931,5G disk WDC WD10JPVX-22J        
├─sda1   800G part                  ext4   /archives
└─sda2    25G part                  ext4   /64-14.1
sdb    111,8G disk KINGSTON SMS200S        
├─sdb1   100M part                  ntfs   
├─sdb2  43,3G part                  ntfs   
└─sdb3  68,4G part                  ext4   /
sdc      7,6G disk                         
└─sdc1   7,6G part                  ext2   
sr0     1024M rom  DVDRAM GT50N            
~$
I check that my USB stick is /sdc: it has the right size and is bears the type "disk", not "part". So I issue following command:
Code:
dd if=slack.iso of=/dev/sdc bs=4M; sync
Replace /dev/sdc with the actual name of your device but not for instance /dev/sdc1.

PS I didn't see your last post before posting. Maybe this can help others.

Last edited by Didier Spaier; 01-24-2015 at 10:16 AM. Reason: Added the MODEL field in the lsblk command.
 
Old 01-24-2015, 10:07 AM   #15
badbetty
Member
 
Registered: Jan 2014
Posts: 159

Original Poster
Rep: Reputation: Disabled
@Didier

Quote:
Originally Posted by Didier Spaier View Post
It is completely useless to partition the USB stick with cfdisk and create a file system in this case.
Yes I agree. I was just mentioning I reset it to a formatted working stick so to speak, before trying again.

Thank you for your info in any case. It is not wasted. Sorry for my utterly stupid mistake.
 
  


Reply



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
mkisofs: Error - boot image './isolinux/isolinux.bin' has not an allowable size. ogross74 Red Hat 3 05-05-2016 02:22 AM
Ready, but not prepared! Dabaser LinuxQuestions.org Member Intro 1 09-29-2014 08:48 AM
LXer: What Are You Prepared To Do? LXer Syndicated Linux News 0 09-10-2009 01:31 PM
Isolinux error during Slackware 9 install Boot RadicalGrande Slackware 3 07-09-2003 02:13 PM
ISOLINUX 1.75 2002-06-14 isolinux failed to get sector size tihe Linux - General 13 12-16-2002 04:55 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:35 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
Open Source Consulting | Domain Registration