From: Kevin Tappe <kevin@zerodivide.de>
To: linux-scsi@vger.kernel.org
Subject: g_NCR5380 - 2.6.0 - problem with reloading module
Date: Mon, 5 Jan 2004 23:42:20 +0100 [thread overview]
Message-ID: <20040105224220.GA1168@nihil.tappe.netz> (raw)
Hi,
i hope this is the right emailadress for my problem...
The first time I load the module g_NCR5380 everything works fine:
scsi0 : interrupts not enabled. for better interactive performance,
scsi0 : please jumper the board for a free IRQ.
scsi0 : at port 0x280 interrupts disabled options CAN_QUEUE=16
CMD_PER_LUN=2 release=1 generic options
AUTOPROBE_IRQ AUTOSENSE USLEEP, USLEEP_POLL=1 USLEEP_SLEEP=20
generic release=7
scsi0 : Generic NCR5380/53C400 Driver
Vendor: UMAX Model: Astra 1200S
Rev: V2.9 Type: Scanner ANSI SCSI revision: 02
Attached scsi generic sg0 at scsi0, channel 0, id 5, lun 0, type 6
I can't reload the module g_NCR5380 after an rmmod:
nihil:~# modprobe -v g_NCR5380
insmod /lib/modules/2.6.0/kernel/drivers/scsi/g_NCR5380.ko ncr_irq=255
ncr_addr=0x280 dtc_3181e=1
FATAL: Error inserting g_NCR5380
(/lib/modules/2.6.0/kernel/drivers/scsi/g_NCR53
80.ko): No such device
After a reboot everything is just fine again.
I use a vanilla 2.6.0 kernel. Please let me know if you need any further
information.
-Kevin
--
Think how much fear is going to be required to stop people from passing
along copies of things on their computers. I hope you don't want to live
in a world with that much fear. - Richard M. Stallman
next reply other threads:[~2004-01-05 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 22:42 Kevin Tappe [this message]
2004-01-09 19:26 ` g_NCR5380 - 2.6.0 - problem with reloading module Randy.Dunlap
[not found] ` <20040110193814.GA371@nihil.tappe.netz>
2004-01-11 23:30 ` [PATCH] " Randy.Dunlap
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=20040105224220.GA1168@nihil.tappe.netz \
--to=kevin@zerodivide.de \
--cc=linux-scsi@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