Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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 this is about not being able to install because your cd/dvd is not found.
cd/dvd not found was the message that appeared only in slack 11,when i boot it in sata.i....it would atleast boot till there and i was able to partition ..
here in slack 12, it stops there..
Quote:
How is the drive hooked up ?
i think its connected to IDE bus(hopefully that is what it is called!!!)..
it is a bus that comes with the motherboard which was earliar also used to connect the hard disks apart from connecting optical drives!!!
its a very thick bus...am sure its not sata cable..
i was able to install ubuntu....also windows xp....another fact is that i got the almost similar error while installing suse 10.1. so icouldn'y install 10.1 suse
while I can't tell you what your specific problem is, I can tell you (and it might help others who _can_ help you), that the IDE on that board is not native PATA from the chipset like on older boards - it uses a SATA->PATA converter, down device, since the chipset on that board does not have a PATA port directly off the chipset.
I have used Slack for several years now and have recently built a system and wanted to run Slack 12 on the new box. I'm sure that I am having the same problem as what started this thread. When booting version 12 after a clean install the system hangs at the same "ACPI: PCI Root Bridge [PCI0] (0000:00)" command during the boot sequence. To pass this I appended this command to the kernel on boot.
acpi=off
After appending this to the kernel the system boots to the CLI where I can enter "setup" to begin the install process. After creating my partition, swap space, etc... I am prompted to select my source drive. Auto detect fails, while manual selection fails as well.
I have also appended the "hda=cdrom" during kernel selection and watched the system try desperatly to identify the cdrom only to watch it give up and finish the boot sequence with NO cdrom identified.
It's interesting to see my system boot to DVDRW, slack start the install from the DVDRW, yet watch the system refuse to believe that there is a DVDRW.
Manual mounting via the */dev/ fails also.
fdisk -l fails to list anything outside of SDA1 and SDA2
I am in the process of playing with the DMA variables available during the kernel selection prior to boot. If anyone has any ideas, I would appreciate if you would share with me also. Thanks!
The System
-----------
Slackware 12 OS
4G 800Mhz RAM
Intel Core Duo Quad 2.4
2x Maxtor 500G SATAII/300 drives
* Drive one is on SATA0
* Drive two is on SATA1
Intel Executive Motherboard [DQ35JO]
Sony DVD/RW [DRU-170C]
* The only device connected via IDE [MASTER]
Last edited by alex.pujols; 12-04-2007 at 08:57 PM.
Reason: additional information
Same problem here, and I have the same hardware setup as Alex. I just got Slackware 12 loaded using a USB CDROM. Once loaded I hooked up an IDE CDROM and have successfully booted off it and have also booted into Linux from the hard drives then mounted the IDE CD drive.
I'm not real familiar with how fdisk -l works, but it does not show the drive. However, I can mount it with:
mount /dev/sr0 /mnt
Not sure why it sees it as sr0 though.
Once you get past that you may need to install the e1000 network module from the CD. The e1000 that ships with Slackware 12 did not work for me.
Last edited by jlarsen; 12-07-2007 at 11:16 AM.
Reason: clarity
Okay, after hours of endless research I have things working. Here is how it happened.
The problem lies with the Intel Motherboard listed below. The Intel DQ35JO has serious issues with using the standard IDE/ATAPI framework. I eventually tested another DVD-ROM that I knew worked and I continued to get the same issue when installing Slackware 12. There may be additional support in the current kernel that allows for better hardware negotiation between the kernel and this intel board, but this isn't available in the native kernel included with Slackware 12 install DVD.
I eventually returned the EIDE/ATAPI drive and purchased a SATA DVDR to see if the intel motherboard [being fairly new] had invested in SATA support more heavily than it has IDE. Suprisingly that was the case, after installing the SATA DVD-RW the drive was detected by the auto-scan in the startup script during install.
Oh.. and remember that issue with ACPI and having to append the "ACPI=off" command to the kernel on boot to bypass the lock up on boot... all gone! After going all SATA I no longer have to issue that command, everything works exactly as it should.
The only thing left is to manually install the Intel NIC drivers from source and we are good to go.
During the process of troubleshooting I poured over endless pages of docs and I would like to reference 3 to better help those with similar problems. Understanding how the kernel handles drives is an absolute must if you are going to troubleshoot these things.
PS: If looking over hours of doc's just to get a DVD-RW to work isn't fun to you, you shouldn't be working with slack! Enjoy!
The System
-----------
Slackware 12 OS
4G 800Mhz RAM
Intel Core Duo Quad 2.4
2x Maxtor 500G SATAII/300 drives
* Drive one is on SATA0
* Drive two is on SATA1
Intel Executive Motherboard [DQ35JO]
There are a couple differences in what I was working with, but I'll share my solution as well.
The board being used is an Intel DG33FB with a Intel Core Duo Quad 2.4 processor. Once Slackware was installed I did not install a CDROM. However, I still could not boot without using ACPI=off, but when booting with that kernel parameter the OS only sees one processor.
Finally used pci=nommconf instead and it booted fine and recognized four processors.
I also have a dq35jo motherboard and had problems installing the slackware 12 and gentoo 2007.0.
For install the slackware 12, i used the ubuntu that already comes with support for (PATA marvel) Controller, then I could identify my CD-ROM IDE driver.
Copied the installation files for one partition of my hd and installed the slack from the hard disk. After installation, the kernel of the instalation had controller supports for (PATA MARVEL). So I only had to pass the parameter pci=nommconf so that everything worked.
If you have an opportunity to recompile the kernel to use the following options:
[] Support mmconfig PCI config space access (Off)
<*> Serial ATA (prod) and Parallel ATA (experimental) drivers
<*> SATA AHCI support
<*> Intel ESB, ICH, PIIX3, PIIX4 PATA / SATA support
<*> Marvell PATA support via legacy mode
With these options the drivers pata functioned properly, both in the slack as on gentoo. And now, we dont need to use the pci=nommconf parameter to boot the kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.