SlackwareThis Forum is for the discussion of Slackware Linux.
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.
So it won't but just huge26.s but if you enter the "root=" parameter with your current install it will boot it... have you tried using the other kernels ? Like "sata.i" or "test26.s" ?
What Wolfden is trying to say is that it wont boot the cdrom or dvd he downloaded on his machine. I am Having exactly the same problem here. I now have 3 cd1 slack 11 downloaded by two different mirrors and a torrent and none of them are recognised as a bootable medium by my PC I use for Linux.
Like Wolfden I am trying to figure out a way of forcing the cd's to install using the bootable floppy from 10.2.
Wolfden whats your hardware and Bios revision.
Mine is AMD K6 processor, and bios AMIBIOS A5191MS v1.5 122799
I have Slack 11 too and it booted without any problems whatsoever. One of you two said that if he moves the cd-rom(writer) to another computer the disks are booting. Do both of the computers have the same BIOS or they are different. Post your BIOS on the non-working PC and on the working PC if different.
Make sure your setting up your BIOS settings right. Make your cdrom as the first boot device. Also, some computers require you press down a key during boot in order to boot from a cdrom. My latop makes me hold down the 'c' key.
Download Slackware 11 iso from bittorrent; works fine.. I mean the disk is bootable.
now, let's check out the md5.
My test system is pretty old, pentium 133 classic, intel 440vx chipset.
I had scsi disk before; so I can put my cdrom drive to ide0 as /dev/hda; then choose to boot from cdrom in bios, because I had similar problem with another ide hard drive on this old system.
Okay, we have tried everything suggested from the above. I have been installing OSes for a number of years on different PC's and never come accross this before...so I take it I know how to set the Bios up to boot from a cd drive
If you also read above both of us have tried downloads both from mirrors and bit torrent. How many coasters do you want us to have before were done.
The same PC is now booting a live distro of Kubunto. Then I will try Slack again, if not I will just go for the upgrade.txt option.
Send a mail to volkerdi [at] slackware [dot] com and as I've requested and you haven't answered, don't forget to mention your hardware on the working and non-working PC's especially the BIOS. There might be something with the CD's boot information that your BIOS'es don't understand, or something like that.
There are two different kind of iso, one is created with bootable track, the other is created to pack an entire directory for easy burning cd without missing packages.
I made the same mistake many time before. It all depends how the person created this iso file.
Check the md5sum, it will be different from each other.
If you have a floppy drive and a floppy, try copying
Code:
/isolinux/sbootmgr/sbootmgr.dsk
from CD#1 (or the DVD) to the floppy and boot from that floppy. In the boot menu which appears, select the CD as the next stage boot.
Read the /isolinux/sbootmgr/README.TXT for information about this "Smart Boot Manager" which is meant for exactly this kind of booting problem with the CDROM.
Remove discs or other media
Press any key to restart
If that was all you got with the floppy in the drive, then you did not create the floppy correctly. What you should see is a curses based screen with a boot menu that has the selections "quit to bios" "power off" "reboot" "floppy" harddisk" and "CD-ROM".
There, you should pick "CD-ROM".
To format your floppy, boot into your existing Slackware 10.2 installation and use either Kfloppy (if you have KDE installed and make sure the user you're logged on is added to the 'floppy' group or it will not work) or use the command 'fdformat' (man fdformat) for more info.
All my DL are while running M$xpPRO, as I have been unable to get 2915 WiFI (mini-PCI card) running on LT. Last night had problem as below. On Startup today in safe mode noted CPU went max, then slowed down {abnormal on SU for me}. Using various anti-virus I have scans were OK until Avast 4.7 0640.3 10/05/06 (Just updated) showed my recent DL of Slack 11.0 had 2 viruses in it! Due to filename length not sure if got it all correct. Virus in \0#4037696321, \0#109154491.
Linux is supposed to be virus free, so I suspect this is something caused by my DL w/ XP as O/S. Unwilling to restart BitTorrent 4.04 to finish DL, or allows others to utilize what I have (SEED?) as I might spread this crap. Slkwr 11.0 scan took LONG time, BtT DL info was last @99.9% 0:00 remaining. Still fairly new to BitTorrents, but thought I read it was beneficial to stay on as long as possible for others to use, not to Finish.
Quote:
Originally Posted by digital8doug
snpd/EDIT Was DL of Slackware 11.0 from Linuxtracker, when at 99.9% 0:00 remaining, it caused hang on my LT, mouse response & Screen changes very slow, Not sure if BtT, Linux track or slackware. Just beware.
Anybody shed real good light on this problem? *!*MARA*!* Not sure if this is related to other migrators having boot problems. Or is this just a M$ app/ Linux incompatibility? avast was unable to move to virus chest. Move both if desired, TY d8d
Last edited by digital8doug; 10-05-2006 at 04:08 PM.
Reason: FRIK #26-TY for the Smart Boot Manager info!! Your link worked, read info, but I am getting ~Encountered a 404 error" when I try to actually download it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.