public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup.s kernel and SCSI disks
Date: Thu, 31 Mar 2005 19:05:32 -0700 (Mountain Standard Time)	[thread overview]
Message-ID: <Pine.WNT.4.62.0503311905110.2556@merlin> (raw)
In-Reply-To: <20050330190328.GA28363@gmx.net>

Alex,
There was an error in my vsftpd configuration. Try it again. Sorry.

Equal causes can produce very unequal effects.
Joseph C. Lininger
jbahm@pcdesk.net
Verification: 5eab38a77ac40416e075be8f50607ff7

And so it came to pass that on Wed, 30 Mar 2005, Alex Snow said

> Hi. I just tried to download that iso from you but the link seems to
> be broken. the only directory on ftp.pcdesk.net appears to be
> gentoo-portage.
> thanks for the help.
> On
> Wed, Mar 30, 2005 at 09:31:09AM -0700, Joseph C. Lininger wrote:
>> Alex,
>> Looking at the readme.txt file, it would appear that the adaptec SCSI
>> cards are not supported by the speakup.s kernel. The kernel you need
is
>> adaptec.s. The standard iso image of Slackware 10.1 does not include
>> support for Speakup in the adaptec.s kernel. However, if you download
my
>> speakup modified iso image:
>>
>> ftp://ftp.pcdesk.net/slackware/speakup-modified-10.1
>>
>> You should be able to boot adaptec.s using speakup with no problems.
>>
>> Equal causes can produce very unequal effects.
>> Joseph C. Lininger
>> jbahm@pcdesk.net
>> Verification: 5eab38a77ac40416e075be8f50607ff7
>>
>> And so it came to pass that on Tue, 29 Mar 2005, Alex Snow said
>>
>>> Hi all. I'm trying to install slackware 10.1 on an hp Netserver
lx/pro
>>> (quad pentium pro/1gb ram/adaptech aha-?? pci ultra-wide SCSI) using
>> the
>>> speakup.s kernel on the install cd. However when I boot the cd
>> speakup.s
>>> doesn't find any of the scsi controlers. When It starts the SCSI
>>> subsystem I get something to the effect of error executing
>>> /sbin/modprobe scsihostadapter. I've had this same problem with
>>> slackware 10.0 and 9.1 on a couple of different boxes. does anyone
>> know
>>> what could be wrong here? is SCSI support broken in this kernel? I
>> know
>>> the controler is there and working because I could see it when
booting
>>> tomsrtbt.
>>>
>>> --
>>> "Linux was made by foreign terrorists to take money from true US
>> companies
>>> like Microsoft." - Some AOL'er.
>>> "To this end we dedicate ourselves..." -Don
>>> 	-- From the sig of "Don", don@cs.byu.edu
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>
>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> --
> LILO, you've got me on my knees!
> 	-- David Black, dblack@pilot.njin.net, with apologies to Derek
and the
> Dominos, and Werner Almsberger
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



      reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Alex Snow
 ` Joseph C. Lininger
   ` Alex Snow
     ` Joseph C. Lininger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.WNT.4.62.0503311905110.2556@merlin \
    --to=jbahm@pcdesk.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).