Thanks for the prompt response.
Actually I think I gave too little information about the problem this time.
The pcmcia stuff works just fine.
When I define everything in /etc/pcmcia/config then the drive seems to be
initialised and the modules are loaded correctly.
In that case I get following modules:
# lsmod Module Size Used by
ppp_deflate 40300 1 (autoclean)
bsd_comp 4020 0 (autoclean)
ppp 20908 2 (autoclean) [ppp_deflate bsd_comp]
slhc 4440 1 (autoclean) [ppp]
adlib_card 900 0 (autoclean)
opl3 11304 0 (autoclean) [adlib_card]
sb 34580 0 (autoclean)
uart401 6320 0 (autoclean) [sb]
sound 57432 0 (autoclean) [adlib_card opl3 sb uart401]
soundlow 344 0 (autoclean) [sound]
soundcore 2564 6 (autoclean) [sb sound]
nin_cs 13144 0
ds 6568 2 [nin_cs]
i82365 22128 2
pcmcia_core 45184 0 [nin_cs ds i82365]
serial 42612 2 (autoclean)
memstat 1476 0 (unused)
nls_iso8859-1 2268 1 (autoclean)
But the problem seems to be that the kernel can't communicate with the drive:
# dd if=/dev/scd0 of=/dev/null bs=2048
1+0 records in
1+0 records out
and mounting fails:
# mount /dev/scd0 -t iso9660 -r /cdwriter
mount: wrong fs type, bad option, bad superblock on /dev/scd0,
or too many mounted file systems
But when I don't configure the module in /etc/pcmcia/config and when I load the
module afterwards then everything works just fine, though lsmod shows the same
modules:
PCD-5ND:~ # modprobe nin_cs
PCD-5ND:~ # lsmod
Module Size Used by
nin_cs 13144 0 (unused)
ppp_deflate 40300 0 (autoclean)
bsd_comp 4020 0 (autoclean)
ppp 20908 0 (autoclean) [ppp_deflate bsd_comp]
slhc 4440 0 (autoclean) [ppp]
adlib_card 900 0 (autoclean)
opl3 11304 0 (autoclean) [adlib_card]
sb 34580 0 (autoclean)
uart401 6320 0 (autoclean) [sb]
sound 57432 0 (autoclean) [adlib_card opl3 sb uart401]
soundlow 344 0 (autoclean) [sound]
soundcore 2564 6 (autoclean) [sb sound]
ds 6568 2 [nin_cs]
i82365 22128 2
pcmcia_core 45184 0 [nin_cs ds i82365]
serial 42612 0 (autoclean)
memstat 1476 0 (unused)
nls_iso8859-1 2268 1 (autoclean)
So: my question is:
What was the difference?
And what can I do to avoid typing modprobe blabla every time?
(By the way: I did never recompile this Kernel by now.
I don't have the space for the Kernel-sources on this little Hardisk.;-)
Am Sun, 30 Jul 2000 schrieben Sie:
> On Sun, Jul 30, 2000 at 01:12:28PM +0200, Markus Klein wrote:
>
> > Now I can mount my Drive when I load the module for the pcmcia-scsi adapter
> > after the boot-procedures. When I load the module within the start of my pcmcia
> > initialisation, then I get the problem that I cannot mount the drive. (This
> > happens when I define the appropriate module in /etc/pcmcia/config ).
>
> 1) Normaly the PCMCIA-Modules are loaded automatical if Linux find a
> PCMCIA-Card in the Slot. Then your Computer will beep (one or two times).
>
> 2) If you compile a new kernel you have to compile your PCMCIA-Pakage new.
> Their is the possibility to get errors when you dont recompile your
> PCMCIA-Pakage.
>
> > When I define the module in /etc/pcmcia/config then I get the message
> > executing 'insmod /lib/modules/2.2.14/pcmcia/nin_cs.o'
> > at startup of cardmanager in the boot-procedures.
> > ->Afterwards I can't mount the drive.
> >
> > If I just load the module manualy (without definitions in /etc/pcmcia/config)
> > with 'modprobe nin_cs' then I don't have any problems.
> >
> > My question is:
> >
> > Are there two different modules which are loaded in that two cases?
>
> Yes. There is the pcmcia_core, which is needed for all other pcmcia-modules
> Perhaps you need dummy_cs or ds. After booting your system you can look with
> lsmod which modules are loaded.
>
> Another test you can do is put your card out and then in. If your
> automatical configs from compiling PCMCIA is well, it rmmod unneeded
> modules like at my computer.
>
> Greets
> Volker
> --
> "Community, identity, stability -
> Major instruments of social stability."
