When I built the modules, I did the following:
sudo make modules_install M=drivers/usb/serial
This has created a new directory here:
/lib/modules/2.6.35.4/extra/
with the modules (sam-ba.ko and usbserial.ko).
If I try modprobe like so:
t7@nbryan:/lib/modules/2.6.35.4/extra$ sudo modprobe sam-ba
[sudo] password for t7:
FATAL: Module sam_ba not found.
Note that the underscore has replaced the hyphen. Does it need an alias?
Why can modprobe not see the new module? I strongly believe that the
way I built and installed the driver is incorrect. I don't hack
drivers on a daily basis ;-)
But, and it is a big but, my original post shows that the sam-ba
module is present, has connected to ttyUSB0, but fails to transmit
to the SAM-BA boot loader on my Atmel board. As I mentioned, it worked
the first time, but subsequent tries have all failed so it is very
close to working and I believe you guys are careful so the problem
is most likely at my end.
Thanks for any further pointers.
Neil.
--- On Thu, 18/11/10, Greg KH <greg@xxxxxxxxx> wrote:
> From: Greg KH <greg@xxxxxxxxx>
> Subject: Re: SAM-BA patch test on 2.6.35-22-generic failed.
> To: "Neil Bryan" <cambesol@xxxxxxxxxxx>
> Cc: "Johan Hovold" <jhovold@xxxxxxxxx>, linux-usb@xxxxxxxxxxxxxxx
> Date: Thursday, 18 November, 2010, 19:04
> On Thu, Nov 18, 2010 at 05:10:57PM
> +0000, Neil Bryan wrote:
> > Hi Johan,
> >
> > I removed both the sam-ba and usbserial modules and
> then tried the
> > following:
> >
> > t7@nbryan:/data/work/nbryan/sam7/sam-ba_cdc_linux$
> sudo insmod sam-ba.ko
> > insmod: error inserting 'sam-ba.ko': -1 Unknown symbol
> in module
>
> Use 'modprobe' and not insmod.
>
> Or do:
> insmod usbserial.ko
> insmod sam-ba.ko
>
> thanks,
>
> greg k-h
>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
