Seems the major problem is this: Apr 4 15:22:00 t0024 cardmgr[4941]: no pcmcia driver in /proc/devices Do I need to compile a new kernel, or can this be added to the RH stock kernel? Tim On Fri, 2003-04-04 at 15:24, Tim Ryder wrote: > Still doesnt seem to work. > I get the same error message. > > Tim > > On Fri, 2003-04-04 at 15:04, Joshua Legbandt wrote: > > On Fri, 2003-04-04 at 11:59, Tim Ryder wrote: > > > Different problem, my pcmcia startup script doesnt have the .o on the > > > end of the yetna_socket line. > > > > > > Tim > > > > > My apologies, look for this section: > > if [ -d $PC ] ; then > > echo -n " modules" > > /sbin/modprobe pcmcia_core.o $CORE_OPTS > > /sbin/modprobe $PCIC.o $PCIC_OPTS > > /sbin/modprobe ds.o > > elif [ -d $KD ] ; then > > /sbin/modprobe pcmcia_core > > /sbin/modprobe $PCIC > > /sbin/modprobe ds > > else > > echo $" module directory $PC not found." > > break > > fi > > > > and remove the '.o' from the top section (I think, I added the .o back > > in), I should have said pcmcia_core, $PCIC and ds... > > > > -josh > > > > > > > > > > On Fri, 2003-04-04 at 14:56, Joshua Legbandt wrote: > > > > On Fri, 2003-04-04 at 09:49, Robert P. J. Day wrote: > > > > > On 4 Apr 2003, Tim Ryder wrote: > > > > > > > > > > > After the install of RedHat 9, i get this message when i try to start > > > > > > pcmcia services. > > > > > > > > > > > > Starting PCMCIA > > > > > > services:/lib/modules/2.4.20-8/kernel/drivers/pcmcia/yenta_socket.o: > > > > > > init_module: No such device > > > > > > Hint: insmod errors can be caused by incorrect module parameters, > > > > > > including invalid IO or IRQ parameters. > > > > > > You may find more information in syslog or the output from dmesg > > > > > > /lib/modules/2.4.20-8/kernel/drivers/pcmcia/yenta_socket.o: insmod > > > > > > /lib/modules/2.4.20-8/kernel/drivers/pcmcia/yenta_socket.o failed > > > > > > /lib/modules/2.4.20-8/kernel/drivers/pcmcia/yenta_socket.o: insmod > > > > > > yenta_socket > > > > > > failed > > > > > > /lib/modules/2.4.20-8/kernel/drivers/pcmcia/ds.o: init_module: Operation > > > > > > not permitted > > > > > > Hint: insmod errors can be caused by incorrect module parameters, > > > > > > including invalid IO or IRQ parameters. > > > > > > You may find more information in syslog or the output from dmesg > > > > > > /lib/modules/2.4.20-8/kernel/drivers/pcmcia/ds.o: insmod > > > > > > /lib/modules/2.4.20-8/kernel/drivers/pcmcia/ds.o failed > > > > > > /lib/modules/2.4.20-8/kernel/drivers/pcmcia/ds.o: insmod ds failed > > > > > > cardmgr. > > > > > > > > > > > > I ran the RH Hardware browser and confirmed that i do have a > > > > > > yenta_socket. > > > > > > > > > > > > Has anyone else seen this issue. > > > > > > > > > > yup, i posted about that recently. did that posting not make it out > > > > > to this list? > > > > > > > > > > in a nutshell, after installing on my inspiron 8100, everything > > > > > worked fine -- my pcmcia linksys net card did what it was supposed > > > > > to, etc. > > > > > > > > I ran into the same problem after I recompiled my kernel to turn on > > > > acpi, the easy solution is to modify the init script for pcmcia and > > > > remove the '.o' at the end of yenta_socket.o, ds.o and $PCIC.o > > > > > > > > Restart pcmcia with /etc/init.d/pcmcia restart and it should work (at > > > > least it did for me). I can't verify whether my pcmcia card worked > > > > before the new kernel since I hadn't tried it, but I remember having a > > > > similar problem with pheobe... > > > > > > > > -josh > > > > > > > > -- > > > > Joshua Legbandt <jtlegbandt@xxxxxxxxxxxxx> > > > > > > > > > > -- > > Joshua Legbandt <jtlegbandt@xxxxxxxxxxxxx> > > > > > >
