Results 1 to 9 of 9

Thread: Slackware Problem

  1. #1
    Senior Member
    Join Date
    Mar 2003
    Posts
    170

    Question Slackware Problem

    Hi everyone,

    I've been having a problem trying to get slackware on my computer.

    Well I downloaded the slackware ISO file, burned it with Nero and burned it as an image and all that. Now when its finished I put it in my CD-ROM drive and reboot. But it won't boot straight to the disc.(when I installed RedHat it just booted straight to the installing part). I'm wondering if this is something to do with my disc, burning software, my computer... or whatever. If someone could tell me what I'm doing wrong or if I'm doing it right could someone tell me how I can do it another way.

    Thanks for anyones help.
    [glowpurple]NooNoo\'s [/glowpurple]

  2. #2
    Elite Hacker
    Join Date
    Mar 2003
    Posts
    1,407
    Did you check the md5 sums when you downloaded the iso files. You may have gotten a bad download. It also could have messed up during the burning process. I have always had trouble burning iso's for some reason. I think it was the configuration of my drives though since I had two cdrom drives. It also could have been a bad disc. Check for scratches on the disc. Also, for redhat did you download the files and burn them with the same process, or did you buy the discs or have a friend do it? If you did the same with redhat, I would say that it's not your software or burner, but just a bad download, corrupt file, or a messup in the burning process. When you're burning the iso's, don't do anything else in the background, just set it to burn and come back in about 8 minutes.
    Hope I helped

  3. #3
    Senior Member
    Join Date
    Mar 2003
    Posts
    170
    I tried all different downloads, and tried burning it about 5 different times. Burn process always said finished sucessfully. And I did the same process with redhat, downloaded the ISO files and burned it.
    [glowpurple]NooNoo\'s [/glowpurple]

  4. #4
    Elite Hacker
    Join Date
    Mar 2003
    Posts
    1,407
    Try starting the install from boot floppies. The install boot floppy images are located in this directory at this ftp site:
    ftp://distro.ibiblio.org/pub/linux/d...-9.1/rootdisks
    Just download install 1 and 2 and use rawrite to write the boot floppies. if you already have linux use the dd command:
    dd if=path/to/image of=/dev/fd0 bs=36b
    I got that command syntax from the suse site so it might be wrong. You might need to change the bs part of it. I have seen this command used other ways, like bs=1kb or something like that, so maybe someone else can help you with the syntax. Anyways, after you have those, go to this directory and download the old_cd.i file which should contain cdrom drivers you can load at boot. Here is the directory:
    ftp://distro.ibiblio.org/pub/linux/d...-9.1/bootdisks
    Hope this helped.

    edit
    I'm editing this because I don't think it's old_cd.i you want. Read the following for details.
    sorry this is so long but this is off the slackware howto found here:
    ftp://distro.ibiblio.org/pub/linux/d...lackware-HOWTO

    First, the "IDE" kernels (so named because they do not have drivers for
    any SCSI controllers built in):

    bare.i This is a kernel to use for installation on most
    IDE based PCs, with support for nearly all IDE
    controllers and support for IDE/ATAPI CD-ROM/DVD
    drives. Most CD-ROM drives made today fall into
    this category.

    jfs.i A version of bare.i with support for IBM's Journaled
    Filesystem. This required patches to the kernel which
    you can find in source/k/jfs/ if you need to rebuild
    the kernel.

    lowmem.i This is a really stripped-down Linux kernel which might
    be useful for installing on IDE systems with a low
    amount of RAM (less than 8MB). If bare.i runs into
    problems, you might try this. NOTE: On systems with
    extremely low memory (4MB), ZipSlack plus the
    fourmeg.zip add-on (found in the zipslack directory)
    may boot and run even in cases where lowmem.i doesn't.
    If use have to use lowmem.i to install, you'll then
    probably have to compile a custom kernel with the
    minimal additional features that your machine requires.

    old_cd.i This is a version of bare.i with additional support
    for old CD-ROM drives on non-standard proprietary
    interfaces. The CD-ROM drives supported by this
    kernel are:
    Aztech CDA268-01A, Orchid CD-3110, Okano/Wearnes CDD110,
    Conrad TXC, CyCDROM CR520, CR540.
    Sony CDU31/33a CD-ROM.
    Sony CDU531/535 CD-ROM.
    Philips/LMS cm206 CD-ROM with cm260 adapter card.
    Goldstar R420 CD-ROM (sometimes sold in a 'Reveal
    Multimedia Kit').
    ISP16/MAD16/Mozart CD-ROM drives.
    (Boot time command line options (or 'append=' options
    in /etc/lilo.conf) are:
    isp16=<port>,<irq>,<dma>,<drive_type>
    Valid values for drive_type include: Sanyo, Panasonic
    (same as Sanyo), Sony and Mitsumi. Default values are:
    port=0x340, irq=0, dma=0, drive_type=Sanyo.)
    NON-IDE Mitsumi CD-ROM support.
    Optics Storage 8000 AT CD-ROM (the 'DOLPHIN' drive).
    Sanyo CDR-H94A CD-ROM support.
    Matsushita, Kotobuki, Panasonic, CreativeLabs
    (Sound Blaster), Longshine and Teac NON-IDE CD-ROM
    support.

    pportide.i This is an extended version of bare.i with support for
    a wide variety of parallel-port IDE devices. Supports
    parallel-port products from MicroSolutions,
    Hewlett-Packard, SyQuest, Imation, Avatar, and other
    manufacturers.

    speakup.i This is like the bare.i (standard IDE) kernel, but has
    support for Speakup. Speakup provides access to Linux
    for the visually impaired community. It does this by
    sending console output to a number of different
    hardware speech synthesizers. It provides access to
    Linux by making screen review functions available.
    For more information about speakup and its drivers
    check out http://www.linux-speakup.org.
    To use this, you'll need to specify one of the
    supported synthesizers on the boot prompt:
    speakup.i speakup_synth=synth
    where 'synth' is one of the supported speech
    synthesizers:
    acntpc, acntsa, apolo, audptr, bns, decext, dectlk,
    dtlk, ltlk, spkout, txprt

    usb.i This kernel is the same as the generic bare.i kernel,
    but adds built-in support for USB to allow installing
    on machines with USB keyboards.

    xt.i MFM (very very old) hard drive support.


    Then, the SCSI kernels (these also support IDE):


    adaptec.s This kernel supports most Adaptec SCSI controllers,
    including these models:
    AHA-1510, AHA-1520, AHA-1522, AHA-1522, AHA-1740,
    and AHA-2825. The AIC7xxx models, which include the
    274x EISA cards; 284x VLB cards; 2902, 2910, 293x,
    294x, 394x, 3985 and several other PCI and motherboard
    based SCSI controllers from Adaptec. This kernel
    also supports all of Adaptec's I2O based RAID
    controllers as well as the DPT SmartRaid V cards.
    In addition, drivers for OEM Adaptec RAID controllers
    used by HP and Dell, and Adaptec branded AAC964/5400
    RAID controllers are also included.

    ibmmca.s This is a kernel which supports MicroChannel
    Architecture, found in some IBM PS/2 machines and
    laptops. It is a bus system similar to PCI or ISA.
    Support for most MCA SCSI, Ethernet, and Token Ring
    adapters is included.

    raid.s This is a kernel with support for some hardware SCSI
    and IDE RAID controllers. The installer now has
    preliminary support for these controllers as well. The
    drivers included are:
    3ware Hardware ATA-RAID controllers.
    AMI MegaRAID 418, 428, 438, 466, 762, 490
    and 467 SCSI host adapters.
    Compaq Smart Array controllers.
    Compaq Smart Array 5xxx controllers.
    Highpoint 370 IDE RAID.
    Promise Fasttrak(tm) IDE RAID.
    IBM ServeRAID hardware RAID controllers.
    Mylex DAC960, AcceleRAID, and eXtremeRAID controllers.
    Many of these controllers will require some degree of
    do-it-yourself setup before and/or after installation.

    scsi.s This is a SCSI kernel with support for various
    controllers. Note that this kernel does not include
    Adaptec support any longer -- you must use the adaptec.s
    kernel for that.
    This kernel supports these SCSI controllers:
    AdvanSys SCSI support (supports all AdvanSys SCSI
    controllers, including some SCSI cards included with
    HP CD-R/RW drives, the Iomega Jaz Jet SCSI controller,
    and the SCSI controller on the Iomega Buz multimedia
    adapter)
    AM53/79C974 PCI SCSI support
    BusLogic SCSI support
    EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant
    boards) support
    Generic NCR5380/53c400 SCSI support
    Initio 91XXU(W) and Initio 91XXU(W) support
    NCR53c406a SCSI support
    NCR53c7,8xx SCSI support
    SYM53C8XX Version 2 SCSI support
    Qlogic ISP SCSI support
    Qlogic QLA 1280 SCSI support

    scsi2.s This is a SCSI kernel with support for various
    controllers not supported by scsi.s.
    This kernel supports these SCSI controllers:
    Western Digital 7000FASST SCSI support
    ACARD 870U/W SCSI host adapter support
    Always IN2000 SCSI support
    Compaq Fibre Channel 64-bit/66Mhz HBA support
    Domex DMX3191D SCSI Host Adapters
    DTC 3180/3280 SCSI Host Adapters
    EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST,
    Olivetti, Alphatronix) support
    EATA-PIO (old DPT PM2001, PM2012A) support
    Future Domain 16xx SCSI/AHA-2920A support
    Intel/ICP (former GDT SCSI Disk Array) RAID
    Controller support
    NCR53c710 based SCSI host adapters
    NCR53C8XX SCSI support
    PAS16 SCSI support
    PCI2000I EIDE interface card
    PCI2220i EIDE interface card
    PSI240i EIDE interface card
    Qlogic FAS SCSI support
    QLogic ISP FC (ISP2100 SCSI-FCP) support
    Seagate ST01/ST02, Future Domain TMC-885/950 SCSI
    support.
    SYM53c416 SCSI host adapter
    Tekram DC390(T), DawiControl 2974 and some onboard
    PCnet (Am53/79C974) controllers based on the
    Am53C974A chipset
    UltraStor 14F, 24F and 34F SCSI-2 host adapters

    speakup.s This is the scsi.s (standard SCSI) kernel with support
    added for Speakup. Speakup provides access to Linux
    for the visually impaired community. It does this by
    sending console output to a number of different
    hardware speech synthesizers. It provides access to
    Linux by making screen review functions available.
    For more information about speakup and its drivers
    check out http://www.linux-speakup.org.
    To use this, you'll need to specify one of the
    supported synthesizers on the boot prompt:
    speakup.s speakup_synth=synth
    where 'synth' is one of the supported speech
    synthesizers:
    acntpc, acntsa, apolo, audptr, bns, decext, dectlk,
    dtlk, ltlk, spkout, txprt

    speakup2.s This is the scsi2.s with Speakup support.

    speakaha.s This is the adaptec.s with Speakup support.

    usb.s This kernel is the same as the scsi.s kernel, but adds
    built-in support for USB to allow installing on machines
    with USB keyboards.

    usb2.s This is the scsi2.s kernel with USB support.

    usbaha.s This is the adaptec.s kernel with USB support.


    You'll want to choose a kernel from the list that supports your
    installation media (such as a CD-ROM drive) and the hard drive you'll be
    installing to. For example, to install from an IDE CD-ROM drive to an IDE
    hard drive, you'd use the bare.i kernel. Or, for a system with an NCR
    53c810 SCSI controller, SCSI CD-ROM, and SCSI hard drive, you'd use either
    the scsi.s or scsi2.s kernel (since they each have an NCR driver).

  5. #5
    Senior Member gore's Avatar
    Join Date
    Oct 2002
    Location
    Michigan
    Posts
    7,177
    With nero, when you go to burn the ISO and it has the lil check box saying "Burn as Image file" DONT CLICK THAT. Try another one, and dont click that part, then burn it and ittl be fine.

  6. #6
    Senior Member
    Join Date
    Aug 2002
    Posts
    547
    i had that problem once what i did is just extracted all the content of the iso with isobuster and copied it into a folder and burned from there and i had no trouble, i also recommend using winiso or Alcohol 120%

  7. #7
    Trumpet-Eared Gentoo Freak
    Join Date
    Jan 2003
    Posts
    992
    Errmm

    You sure about your BIOS boot order ? Just a simple thought.

    Greetz,
    Come and check out our wargame-site @ http://www.rootcontest.org
    We chat @ irc.smdc-network.org #lobby

  8. #8
    Senior Member
    Join Date
    Mar 2003
    Posts
    245
    Hi kilerboots,

    I have had the __exact__ same problem with every Slackware release since 7.0... I actually have
    four x86 machines, only one of which will not boot a Slackware iso disk. Each box is either a PII or PIII machine, three with standard IDE CDROM's (el torito compliant, blah blah yada yada), and one with an NEC 16x IDE DVD-ROM; all have Intel mobo's, and just for the record they are Micron PC Client Pro's.

    The machine with the NEC DVD won't boot a slackware disk (7.0 - 9.1), but will boot anything else under the sun that I have tried (x86 Solaris, RH, Debian, SCO, etc.). The same Slackware disk boots just fine in the other three boxes.

    The ultimate kicker is that the NEC DVD placed in one of the other boxes boots the Slackware iso just fine... It _could_be_ a bios update or something on the one machine, a wierd or more strict manner in which slackware iso images are built, or some kind of black magic, who knows.

    That may not have helped much kilerboots, but at least you know you're not alone, and that it _most_likely_ is not the way you burned the disk...

    -- spurious
    Get OpenSolaris http://www.opensolaris.org/

  9. #9
    Senior Member
    Join Date
    Oct 2003
    Posts
    111
    If you have a high speed connection, you could always try installing it from FTP :P I find this helpful sometimes when hardware doesn't like to cooperate.

    If you're going to do that in this case, you'll have to do as h3r3tic says, and install via the boot floppies.
    Creating further mindless stupidity....through mindless automation.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •