Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The link in spiky's post above is for the 32-bit version of Slackware 14.0. The torrent you referenced in your first post was for the 64-bit version. I just wanted to point that out. The 64-bit direct ISO download from the Slackware mirror site is http://mirrors.slackware.com/slackwa...re64-14.0-iso/.
Have you verified that the burned DVD matched the ISO? Most burner software has an option you can specify to tell it to verify the burn. You can also use cmp or you can compare the md5sum of the DVD and the ISO. For example:
I have burned dozens of *.ISOs and there was the time long after I should have known better that I forgot to use the "burn image" tool and ended up with yet another copy of the *.ISO file instead of a replication of the optical disk.
I have burned dozens of *.ISOs and there was the time long after I should have known better that I forgot to use the "burn image" tool and ended up with yet another copy of the *.ISO file instead of a replication of the optical disk.
thanks Frank: my mistake was different, but similarly fundamental: i burned the whole package, *not* the iso, to my target....
covered in momentary shame,
but braced in spirit and girded in loins by the salutary effect of self-accusation,
It is well said that a group of wise men will unwisely let a wittle witless wanker into their midst, but, in this case you guys have avoided that mistake and admitted an inversely precocious linux prodigy into your fellowship:
I burned the whole package!!!!! not thinking to open up what i had downloaded and, you know, take a look inside the nice little package first ....
red-cheeked but not ruinously,
re-committing myself to the arduous assault on Mount Slack (or die in the attempt)
The link in spiky's post above is for the 32-bit version of Slackware 14.0. The torrent you referenced in your first post was for the 64-bit version. I just wanted to point that out. The 64-bit direct ISO download from the Slackware mirror site is http://mirrors.slackware.com/slackwa...re64-14.0-iso/.
Have you verified that the burned DVD matched the ISO? Most burner software has an option you can specify to tell it to verify the burn. You can also use cmp or you can compare the md5sum of the DVD and the ISO. For example:
cmp /dev/dvd /path/to/foo.iso
or
md5sum /path/to/foo.iso
md5sum /dev/dvd
Kindly read my responses to other contributions to this thread; awfully good of you to respond Z!
Cheers,
T
Is it possible that the sandisk is not linux compatible?
Okay, Z, Frank and Spikey:
-I've made a usb iso from the 2.4GB file and checked with md5sum and confirmed that it is all good.
- I have rechecked my bios settings (earlier the device in question had been default set as "excluded" from the "startup" list)
-I set it in second place, just after my first and only CD drive
Still!!!!!! no go!!!!!!!!!arhghghghghg
I'm really trying here, really working with you guys: and i respectfully acknowledge your budha like magnanimity and equanimity if you continue to help...
but please! what else could it be??
Here are the specs for the device
Device: 32GB Thumb Drive
Model: SanDisk Cruzer Slice (1.20)
Edit: i'm going to buy me some old-fashioned 3.7GB discs and get to the botty of this problem. Meanwhile, guys, any asserverations, deliberations -yea, commiserations- or contributions would be, as I said above, most welcome (and kharmicly good for you)
How did you create the bootable USB thumb drive? Slackware ships with a file called usbboot.img in the usb-and-pxe-installers folder. It boots into the Slackware installer. It doesn't include the packages to be installed, so you'll need to be able to reference a copy on your hard drive, or loop mounted ISO. The README_USB.TXT file in that directory has full instructions.
There are other tools you could use to create a bootable USB thumb drive, like UNetbootin, isotousb, LinuxLive USB Creator, and probably others, but since you are trying to install Slackware, you might as well use the supplied USB boot image.
How did you create the bootable USB thumb drive? Slackware ships with a file called usbboot.img in the usb-and-pxe-installers folder. It boots into the Slackware installer. It doesn't include the packages to be installed, so you'll need to be able to reference a copy on your hard drive, or loop mounted ISO. The README_USB.TXT file in that directory has full instructions.
There are other tools you could use to create a bootable USB thumb drive, like UNetbootin, isotousb, LinuxLive USB Creator, and probably others, but since you are trying to install Slackware, you might as well use the supplied USB boot image.
Addendum to usb problem.
I have just finished installing Slack 14 off an image i burned to a DVD.
Toward the end of install process, I got the option to plug a usb in and have it made a bootable device "for taking me directly to the partition holding my slackware installation"; after plugging it in and hitting enter, I got message saying that usb wasn't recognized.
Could this be a definitive answer as to why usb efforts have all been in vain: usb device itself is either unrecognizable under linux or is broken?
Another problem now:
again, toward end of install, at Lilo option, I opted out, thinking that since grub controlled my other OS (mint 14) on adjacent partition, that it might also give me option to boot into Slack....
no such luck...
I reboot, up pops grub, with the old options but still, STILL!, no slackware...
I will go hunting for a solution; meanwhile, anyone reading this with an answer, I would greatly appreciate it.
You have to make Grub aware of the Slackware installation, boot into your Mint install and run
Code:
sudo update-grub
It will scan your disk(s) and add all installations it recognizes to the boot-menu.
Thanks.
Now I have mint and slack installed, with lilo in control.
Which is fine, except that now, when lilo loads mint, i have no mouse nor keyboard.
I suspect this is due to an option i selected in slack install to do with mouse use in terminal.
I have also to get an internet connection happening, nor have i worked out how to get the gui: xfce, which i bargained for.
So many questions...
Thanks for the suggestion re Grub; i may have to go back to it.
But i've spent hours in the install/re-install process; i think i must draw a line in the sand and work out my problems at the command line with man pages.
Thanks for help everyone.
I have finally got a gui working in slackware 14, with an internet connection which kde netmanager set up for me like a gracious valet.
Now let the work and the fun begin!
Tex
edit: Just to note, that after dozens of installs, each time electing NOT to install lilo, and not succeeding, I finally submitted and took the lilo option, et voila!, I was at home base with a gui tweaked to my humble needs and an internet connection the next day.
thx again for all help
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.