SEO

Wuhoo! Slack 12.1 isos !!!
<http://planet64bit.de/taxonomy/term/4>
(Yes, I DID md5sum them with the slackware.com md5s!)

Wipe old system, begin traditional Slack install procedure...

Uh-oh! No "install from" CDROM found? Huh?

Tried: (with and without hdb=ide-scsi)

* every manual option in the install list
* mounting /dev/hdb
* mounting /dev/sr0
* ls /dev/cd*
* ls /dev/dv*

Something seems to be missing!

Fortunately, I happen to have a working internet connected machine
right next to the install machine, searched and found
(predictably not much, but this)...

http://www.linuxquestions.org/questi...92aaca96bfc73d

....which suggests a possible snafu in the install setup.

As the install search for slackware cdrom fails and then starts
looking for seriously obsolete hardware, but misses out looking for
the kind of hardware folks would have been using for some years now
as standard equipment, it looks as if somebody forgot/missed
something somewhere?

CDROM is a pretty generic cdwdvdr LG thing, and to date has given no
problems. Slack 10.2 loved it. Everything I've thrown at it,
including W98 (it had to be admitted, now I can be at peace) and
FreeBSD just used it without fuss.

Whats missing here? Is it something I need to read somewhere? Or has
somebody been a tad ambitious with the upgrades?

I'm thinking (wild guessing actually) that the huge.s kernel (can't
use the hugesmp.s on a P5a/K6-2 500 machine) might be the culprit
here?

--
\===* www.jonestheweb.myby.co.uk *===/
)8 Data-Pimped by your ISP yet? 8(
(For clues, search "anti phorm")

On May 10, 6:34 pm, Mike <N...@Arizona.Bay> wrote:
> Wuhoo! Slack 12.1 isos !!!
> <http://planet64bit.de/taxonomy/term/4>
> (Yes, I DID md5sum them with the slackware.com md5s!)
>
> Wipe old system, begin traditional Slack install procedure...
>
> Uh-oh! No "install from" CDROM found? Huh?
>
> Tried: (with and without hdb=ide-scsi)
>
> * every manual option in the install list
> * mounting /dev/hdb
> * mounting /dev/sr0
> * ls /dev/cd*
> * ls /dev/dv*
>
> Something seems to be missing!
>
> Fortunately, I happen to have a working internet connected machine
> right next to the install machine, searched and found
> (predictably not much, but this)...
>
> http://www.linuxquestions.org/questi...llation-40/sla...
>
> ...which suggests a possible snafu in the install setup.
>
> As the install search for slackware cdrom fails and then starts
> looking for seriously obsolete hardware, but misses out looking for
> the kind of hardware folks would have been using for some years now
> as standard equipment, it looks as if somebody forgot/missed
> something somewhere?
>
> CDROM is a pretty generic cdwdvdr LG thing, and to date has given no
> problems. Slack 10.2 loved it. Everything I've thrown at it,
> including W98 (it had to be admitted, now I can be at peace) and
> FreeBSD just used it without fuss.
>
> Whats missing here? Is it something I need to read somewhere? Or has
> somebody been a tad ambitious with the upgrades?
>
> I'm thinking (wild guessing actually) that the huge.s kernel (can't
> use the hugesmp.s on a P5a/K6-2 500 machine) might be the culprit
> here?
>
> --
> \===*www.jonestheweb.myby.co.uk*===/
> )8 Data-Pimped by your ISP yet? 8(
> (For clues, search "anti phorm")

try booting (press Enter)and walking away.

Mike wrote:

> Wipe old system, begin traditional Slack install procedure...
>
> Uh-oh! No "install from" CDROM found? Huh?
>
> Tried: (with and without hdb=ide-scsi)

Unless you have your CD drive set up on the same IDE channel as your hard
drive, it's more likely to be /dev/hdc or /dev/hdd than /dev/hdb.

Also I'm assuming you began booting with the CD, if so cannot the install
look for the drive and then mount it?

Responding to Art Clemons...
> Mike wrote:
>
>> Wipe old system, begin traditional Slack install procedure...
>>
>> Uh-oh! No "install from" CDROM found? Huh?
>>
>> Tried: (with and without hdb=ide-scsi)
>
> Unless you have your CD drive set up on the same IDE channel as your hard
> drive, it's more likely to be /dev/hdc or /dev/hdd than /dev/hdb.

Its on /dev/hdb (coz thats where I put it).

> Also I'm assuming you began booting with the CD, if so cannot the install
> look for the drive and then mount it?

No. Tried all the available options on the install options list, and
a few that might have worked on Slack_10.2, like using /dev/hdb,
which couldn't be found.

This is the bit that really annoys, when the running CD tells you it
can't find itself. Grrr! >8(

Keep guessing though, as something might work. 8|

--
\===* www.jonestheweb.myby.co.uk *===/
)8 Data-Pimped by your ISP yet? 8(
(For clues, search "anti phorm")

Mike wrote:
> Keep guessing though, as something might work. 8|

Could you save the output from dmesg somehow and post it here?

Martin

On Sat, 10 May 2008 22:34:48 +0000, Mike wrote:

> Wuhoo! Slack 12.1 isos !!!
> <http://planet64bit.de/taxonomy/term/4> (Yes, I DID md5sum them with the
> slackware.com md5s!)
>
> Wipe old system, begin traditional Slack install procedure...
>
> Uh-oh! No "install from" CDROM found? Huh?

Did you try booting with "ide=nodma"?

Responding to Martin Schmitz...
> Mike wrote:
>> Keep guessing though, as something might work. 8|
>
> Could you save the output from dmesg somehow and post it here?
>
> Martin
>

Er, well, no. I'm currently installing 10.2 on the machine as el
cliente wants to play with it. Should have thought of that Oops!

Another glitch I noticed was that while trying to find what hardware
12.1 had found, it completely missed my 6Gb Fujitsu on /dev/hda, and
defaulted to my second 20Gb Western on /dev/hdc (or 's' something).

For interest sake I grabbed the latest Zenwalker live CD and watched
that struggle with the ide hard disks for while. I'm getting a pretty
strong idea the new 2.6.X kernels don't like old hardware.

--
\===* www.jonestheweb.myby.co.uk *===/
)8 Data-Pimped by your ISP yet? 8(
(For clues, search "anti phorm")

Responding to Mark Madsen...
> On Sat, 10 May 2008 22:34:48 +0000, Mike wrote:
>
>> Wuhoo! Slack 12.1 isos !!!
>> <http://planet64bit.de/taxonomy/term/4> (Yes, I DID md5sum them with the
>> slackware.com md5s!)
>>
>> Wipe old system, begin traditional Slack install procedure...
>>
>> Uh-oh! No "install from" CDROM found? Huh?
>
> Did you try booting with "ide=nodma"?

Nope. (Didn't even know to try that.) Did notice Zenwalker live CD
struggling around with dma for some minutes on boot though. This
really does seem to be a 2.6.x kernel thing.

--
\===* www.jonestheweb.myby.co.uk *===/
)8 Data-Pimped by your ISP yet? 8(
(For clues, search "anti phorm")

On Sun, 11 May 2008 14:28:33 +0000, Mike wrote:

> Responding to Mark Madsen...
>> On Sat, 10 May 2008 22:34:48 +0000, Mike wrote:
>>
>>> Wuhoo! Slack 12.1 isos !!!
>>> <http://planet64bit.de/taxonomy/term/4> (Yes, I DID md5sum them with
>>> the slackware.com md5s!)
>>>
>>> Wipe old system, begin traditional Slack install procedure...
>>>
>>> Uh-oh! No "install from" CDROM found? Huh?
>>
>> Did you try booting with "ide=nodma"?
>
> Nope. (Didn't even know to try that.) Did notice Zenwalker live CD
> struggling around with dma for some minutes on boot though. This really
> does seem to be a 2.6.x kernel thing.


I have the same problem, on not-so-old-hardware.
Same problem Mike has, and my pc is 3 years old.
I don't have hdd and optical drive on the same channel.
The drive is less than a year old Seagate.
Never had problems with slack 10, 10,2, 11 or 12,
so it's was a shock when the installer failed to read the
disc.

At first I thought it was the cheap dvd-r disc problem,
so i tried burning another one, and another one, and finally
another one , and checked the md5sum, which is fine.

Didn't try the "ide=nodma" option, don't have time now.
If someone found the solution, i'd be happy to hear it,
because im short on time lately, otherwise i'd try
playing with it.

Mike wrote:

> This is the bit that really annoys, when the running CD tells you it
> can't find itself. Grrr! >8(

Your "running CD [that] can't find itself" actually is a "running kernel
that can't find the CD". The kernel has been loaded by the BIOS -which
loaded the boot loader from CD- and the boot loader -which loaded the
kernel from CD using only BIOS calls-.
The software involved with the kernel differs a lot from the BIOS,
but yes, the kernel ought to see your CD drive.

Regards,

Kees.

--
Kees Theunissen.