Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Sep 2007 23:46:22 -0400
From:      Gary Palmer <gpalmer@freebsd.org>
To:        Pankov Pavel <pankov_p@mail.ru>
Cc:        lists@swaggi.com, freebsd-mobile@freebsd.org
Subject:   Re: SD/MMC (ricoh) reader on Thinkpad T61
Message-ID:  <20070916034622.GC927@in-addr.com>
In-Reply-To: <46EBF2C5.60708@mail.ru>
References:  <46EBF2C5.60708@mail.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 15, 2007 at 06:57:09PM +0400, Pankov Pavel wrote:
> >I tried "make depend" but got the same results. I thought the driver
> >would work on -CURRENT, at least that was my impression. Has anyone
> >else tried it on current?
> 
> I managed to compile code from sdmmc-20070627.tar.gz on 7-CURRENT with 
> the help of this simple patch:
> : --- dev/sdmmc/sdshc.c~	2007-06-25 14:25:52.000000000 +0400
> : +++ dev/sdmmc/sdshc.c	2007-09-15 18:14:20.000000000 +0400
> : @@ -343,7 +343,7 @@
> :       */
> :      LOG(0x10, (dev, "Setup Intr\n"));
> :      error = bus_setup_intr(dev, sc->irq, INTR_TYPE_NET|INTR_MPSAFE ,
> : -			   sdshc_intr, sc, &sc->ih);
> : +			   NULL, sdshc_intr, sc, &sc->ih);
> :      if (error != 0) {
> :  	MSG((dev, "could not set up interrupt\n"));
> :  	goto cleanup;
> 
> Unfortunately, I can't load the resulting module:
> : pankbook# kldload -v /boot/modules/sdmmc.ko
> : kldload: can't load /boot/modules/sdmmc.ko: No such file or directory
> Such file definitely exists:
> : pankbook# ls -l /boot/modules/sdmmc.ko
> : -r-xr-xr-x  1 root  wheel  48953 Sep 15 18:41 /boot/modules/sdmmc.ko
> 
> I think this error is related to non-existent sdmmc.ko.symbols file 
> (every .ko file in my /boot/kernel has corresponding .ko.symbols, but 
> sdmmc doesn't). I'm not familiar with kernel modules, so I don't know 
> how to solve this issue. But I'm ready to test any ideas :)

Check dmesg and/or /var/log/messages.  Quite often "No such file or
directory" means that the kernel returned ENOENT.  This typically
happens due to a failure in the in-kernel linker due to a symbol
not being found in the kernel that the module requires.  dmesg will
show any kernel linker message and help you debug the issue.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070916034622.GC927>