Ok, here is... not a machine at all but a piece join...

MB Intel D815EPEA2
Proc Pentium III 1 GHz
Mem 384 MB
HD1 Samsung 80 GB (IDE) ATA 133 (Master)
HD2 Seagate 40 GB (IDE) ATA 133 (Slave)
CD1 DVD-RW Samsung Writemaster (Master)
CD1 Generic CD-ROM 56X (Slave)

if I try to do this changing the floppy by a pen drive, it could works?

By curiosity I make a bootable pen drive with Damn Small Linux.

Perhaps booting from this make possible access the cdrom and then start installation.

Check your bios. Sometimes usb sticks are refered as external hdds so you can select them not in the bios devices boot queue, but in hdds boot queue.

Hi KaTaKoPuS,

I'm convinced that the problem DemetriusCrisco and others
describe is a bios quirk made visible by a change in the
mkisofs options used in making the Slack 11 boot CD from the
options used to make Slack 10.2 and earlier boot CD's.
If you have a floppy drive, using a floppy boot disk is an
easy workaround . If you have a slack 10.2 CD, that's also easy.
Other methods exist --network install, USB stick(see earlier posts).
All the methods listed work because they don't need the bios to
boot a Slack 11 install CD.

But,if nothing else will work, you can create a skeleton boot CD
with the "older" mkisofs options--boot with it, and then remove it
and use the ordinary Slack 11 install CD to complete the install.
This requires a running linux distro on your machine...
It is more complicated than the usual slack install.
So, if you must, here's a description of the "process."

First, create a directory, say "Sboot", then copy the directory
"Isolinux" from the Slack install CD #1 into "Sboot". Next,
create a directory called "kernels" in the Sboot directory,
and copy the default kernel (i.e., bare.i) from the slack install
disk #1 "kernels" directory into the Boot/kernels directory.
With these steps done, use mkisofs with the "older" options to
make an slackware.iso file in /tmp. Finally, use k3b or cdrecord
to burn the iso to a CD.

If your problem is what I believe the original poster's it to be,
then this CD will boot the bare.i kernel, and once that happens,
you'll be able to remove the skeleton boot CD, insert the ordinary
slack install disk #1, and proceed as usual.

So lets suppose you're in the /home directory, and the first slack
install disk is mounted at /mnt/cdrom. Commands like this should get
the job done:

mkdir Sboot
cd Sboot
mkdir kernels
cp -r /mnt/cdrom/isolinux /home/Sboot/
cp -r /mnt/cdrom/kernels/bare.i /home/Sboot/kernels/

If you need a special kernel, substitute it's name for "bare.i"
in the copy command.

Become root
su
<enter password>

Now make the iso with this one long command:

mkisofs -o /tmp/slackware.iso \
-R -J -V "Slackware Install" \
-hide-rr-moved \
-v -d -N -no-emul-boot -boot-load-size 4 -boot-info-table \
-sort isolinux/iso.sort \
-b isolinux/isolinux.bin \
-c isolinux/isolinux.boot \
-A "Slackware Install CD" .

Be sure to include the "." at the end of:
-A "Slackware Install CD" .
This period identifies the current directory as the path for
from which mkisofs creates the iso.
Note the "-boot-load-size 4" option...this is the option that
changed

At this point a slackware.iso file should exist in /tmp
and you can use cdrecord or k3b to burn the iso. K3b is
nice. Using cdrecord with a kernel >2.6.5, the command
would look something like this (dev=hdc points to the recorder):

cdrecord -v -pad speed=1 dev=/dev/hdc /tmp/slackware.iso

With a 2.4.x kernel it would be something like:

cdrecord -v -pad speed=1 dev=0,0,0 /tmp/slackware.iso

Of course, if you have the free disk space (~1.5 Gbyte), you could
copy the entire CD #1 into a directory and run mkisofs on that to
re-burn the whole first install disk.

--Lawrence

ok, I do that and the system boot up normaly.

Another thing I do was install the small version for usb found on the Slackware DVD or CD.

Curiously the same simptom: the boot process ignore the OS on the usb stick and boots Windows normaly.

It realy seems to be a problem like posted and quoted by letitgo:

Hi Lawrence...

Thank's for your time to resolve this. When I posted the reply for your question the last one wasn't visible to me at that time (the time you post is 10 minutes sooner that mine - time zone, perhaps.

I will try your sugestions, soon as possible.

I will inform you (and the others) in case of success... or not.

Thank's to all...

Just in home and directly to the tests...

But something light me up...

Few days ago I was closely to download an update for my MB at the Intel's site.

At that moment something distract me and I did not complete the download. I do not remember what hapens then...

Today, at the first boot and reading the step-by-step sent by letitgo, that scene came back...

I went to the Intel's site and download an update for my MB's bios...

What a surprise...

At the first boot after updating bios the Slackware DVD and/or CD came up and prompt me for the installation.

What you have to do?

For those that have Intel's MB, go to http://www.intel.com/support/motherb...p/chipline.htm and check if your MB is listed. Click on the link access the utilities that will upgrade your MB's bios.

If your MB is not listed, at the end of the page click on http://www.intel.com/support/motherb...op/archive.htm (olders MB). Follow the instructions to get your file.

It will take not more than 2 minutes to all the process - download and uptdate.

I'm happy now... I'm slacking... I hope that this options helps most of you...

Thank's again...

Yep--it's better to fix the problem than to work around it.
And creating a skeleton boot CD is a complicated work around...the only
reason I can think of doing it is to have no other choice. If an update
exists for your bios updating the bios is much, much cleaner.

Happy Slacking KaTaKoPuS

--Lawrence

Thank you all for this discussion.

I was having trouble getting Slack 11.0 to recognize the HDD on a Dell Dimension 4700 (P 4, sata HDD) and you all put me on the right track.

I was starting cfdisk with the wrong switch.

Once I typed "cfdisk /dev/sda" (instead of hda) I was off and running.

Of course, no good deed goes unpunished. Slack's not seeing the network port--doesn't even see it with modprobe, so my next step will be to dig up an old NIC and test it out.

Network port ? You mean NIC ? Post the output of 'lspci'.

Thank you. I learned a new command!

Actually, I think it's an on-board network port as opposed to a physical NIC card, just based on the layout of the back of the box. I haven't had the time to take it apart yet.

I'm planning to use it for my new webserver, but the old one's still chugging along, so I'm taking my time.

Anyway, here's the output from lspci. It does report an ethernet controller, but Slack sure isn't seeing it--all I get from ifconfig is 127.0.0.1. (I configured for DHCP, figuring I can always change that later.)

I also have to say I haven't yet tested the cable, but it seems properly seated. It's a new commercially manufactured cable and all the correct lights are blinking on the hub, but I've still got some hardware troubleshooting to do; I probably won't get to it till this weekend.

Billable hours come first.

00:00.0 Host bridge: Intel Corporation 915G/P/GV/GL/PL/910GL Express Memory Controller Hub (rev 04)
00:01.0 PCI bridge: Intel Corporation 915G/P/GV/GL/PL/910GL Express PCI Express Root Port (rev 04)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3)
00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
01:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]
03:00.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
03:00.1 Input device controller: Creative Labs SB Audigy Game Port (rev 04)
03:00.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)
03:01.0 Communication controller: Conexant HSF 56k Data/Fax Modem
03:08.0 Ethernet controller: Intel Corporation 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller (rev 03)

Thank you for your interest.

This is the controller:
Looks like it is being recognized properly, so it should run fine. Did you run 'netconfig' and set it up as described here:

http://www.slackbook.org/html/book.h...-CONFIGURATION

If you have DHCP, make sure to set that.

I have a Dell E520 with the Intel 82562V 10/100 network connection.
This requires the e1000 kernel module, which is not part of the standard Slack 11.0 installation.
If you upgrade your kernel from slackware-current (together with the corresponding kernel-modules), this module is available.
Otherwise, download the driver source (e1000-7.3.20.tar.gz)from Intel and compile.

Thank you for your suggestions.

I verified that the port on the hub and the cable are both good. The hub sees the connection, but there's no traffic. One light on the port on the back of the computer is lit; not two.

I tried the e1000 driver from sourceforge--no luck.

Guess it's time for me to learn how to compile a kernel.

Thanks again.

Sounds like you're making progress. Good luck:-)

for the dell 4100, you need to:

1. Turn the computer off
2. Insert Linux CD
3. Turn Computer on
4. As soon as you see the bootscreen, start tapping F12
5. Select "CD/DVD ROM"

note: it seems that it doesn't matter how BIOS is configured, you must do this to get it to boot from CD. Thank you Dell Tech Support for this info.

This will get the computer to boot from the CD. I am in similiar situation as the rest of you. I am getting the 4100 to boot from CD, but once the live CD is running, it will not open the installer. It just hangs, and the CD spins indefinately.

-Unsung Boxer