From: "Brad Cramer" <bcramer@callahanfuneralhome.com>
To: <linux-kernel@vger.kernel.org>
Subject: sym53c8xx_2 driver and tekram dc-390u2w kernel-2.6.x
Date: Fri, 13 Feb 2004 10:10:40 -0500 [thread overview]
Message-ID: <004e01c3f243$8eadc7b0$6501a8c0@office> (raw)
I need help, First I am not a kernel hacker or a programmer, but I have
asked this question on the Debian mail lists without any answers and have
also e-mail the writer of the driver but the mail comes back so I am turning
to the kernel-list for some help.
I can not get my scsi hd to work with my tekram dc-390u2w controller and
the sym53c8xx_2 driver under kernel-2.6.2. Everything works great using
kernel-2.4.28 and sym53c8xx driver so I know this is not a hardware issue
with the disk. I have built the sym53c8xx_2 driver into the kernel and have
tried every boot prompt command I could (getting them from the
sym53c8xx_2.txt included with the kernel doc's. This is an external drive
that has /var and /tmp mounted on, so needless to say my system does not
work properly. I have tried Googleing but no luck there either. Could
someone please help shed some light on this as I can't handle to many more
sleepless nights:)
Thanks
Brad
next reply other threads:[~2004-02-13 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 15:10 Brad Cramer [this message]
2004-02-13 22:39 ` sym53c8xx_2 driver and tekram dc-390u2w kernel-2.6.x Guennadi Liakhovetski
2004-02-17 16:23 ` Brad Cramer
2004-02-17 19:17 ` Guennadi Liakhovetski
2004-02-17 21:28 ` Brad Cramer
2004-02-17 23:42 ` Guennadi Liakhovetski
2004-02-18 14:44 ` Brad Cramer
2004-02-18 21:03 ` Guennadi Liakhovetski
2004-02-27 14:47 ` Brad Cramer
2004-02-27 14:59 ` Richard B. Johnson
2004-02-27 15:12 ` Brad Cramer
2004-02-28 18:02 ` Guennadi Liakhovetski
2004-03-11 21:35 ` Guennadi Liakhovetski
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='004e01c3f243$8eadc7b0$6501a8c0@office' \
--to=bcramer@callahanfuneralhome.com \
--cc=linux-kernel@vger.kernel.org \
/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