1 Jun 2007 05:10
4 Jun 2007 23:12
mounting smbfs
Folks,
I'm trying to mount a windows share on my eval board. I added smbfs to
my kernel build and got:
# cat /proc/filesystems
nodev rootfs
nodev bdev
nodev proc
nodev sockfs
nodev pipefs
ext2
cramfs
nodev ramfs
msdos
vfat
nodev nfs
nodev smbfs
# mount -t smbfs //my_ip/my_share /mnt
smbfs: mount_data version 16466812 is not supported
mount: Mounting //my_ip/my_share on /mnt failed: Invalid argument
If I run mount again I get another random version number. Seems like
mount and smbfs are
incompatible?
I also tried smbmount but I had to play games with smb_mount.h and it
looks like the version of smbmount.c
is incompatible with the kernel's smbfs also.
Has anyone had any success mounting smbfs? This is with the latest
petalinux download.
(Continue reading)
6 Jun 2007 00:31
Re: mounting smbfs
Hi Jim, Jim Van Vorst wrote: > I'm trying to mount a windows share on my eval board. I added smbfs to > my kernel build and got: > > # mount -t smbfs //my_ip/my_share /mnt > smbfs: mount_data version 16466812 is not supported > mount: Mounting //my_ip/my_share on /mnt failed: Invalid argument > > If I run mount again I get another random version number. Seems like > mount and smbfs are > incompatible? Let me check this out here and I'll get back to you. Cheers, John
6 Jun 2007 07:11
Re: mounting smbfs
Hi Jim,
I got this going, with minor tweaking. Here's how:
apply the attached patch at p0 from petalinux-dist
$ cd ${PETALINUX}/software/petalinux-dist
$ patch -p0 < samba.patch
$ make menuconfig
Under kernel -> file systems -> network file systems
<*> SMB file system support (to mount Windows shares etc.)
[ ] Use a default NLS
[ ] Enable Unix Extensions
Under user/vendor settings -> filesystem applications
--- SAMBA
[*] samba
[ ] smbd
[ ] nmbd
[*] smbmount
[*] smbumount
[ ] uses shared library
rebuild everything, and boot it up
Here's the commandline I used to mount our local fileserver:
(Continue reading)
6 Jun 2007 08:56
libdl.a not available in microblaze linux
Hi,
I am compiling a program on microblaze linux. The program makes use of dlopen, dlsym, and dlclose functions. To my surprise, when I compile the program with –ldl switch, the libdl.a cannot be found. I search through the petalinux directory, there is no libdl.a as well.
Does it mean microblaze linux is incapable of supporting dynamic linking functions (dlopen, dlsym, dlclose)?
Regards,
Victor Yeo
6 Jun 2007 10:53
Re: libdl.a not available in microblaze linux
Hi Victor, victor-sv_yeo@... wrote: > I am compiling a program on microblaze linux. The program makes use of > dlopen, dlsym, and dlclose functions. To my surprise, when I compile the > program with –ldl switch, the libdl.a cannot be found. I search through > the petalinux directory, there is no libdl.a as well. > > Does it mean microblaze linux is incapable of supporting dynamic linking > functions (dlopen, dlsym, dlclose)? That is correct. The MicroBlaze gcc toolchain lacks the ability to generate position independent code, which is a prerequisite for shared libraries. The workaround doesn't have to be too painful - just build the library as a static .a archive, and statically link. Regards, John
6 Jun 2007 13:02
RE: libdl.a not available in microblaze linux
John, Thank you for your reply. I suppose microblaze linux cannot link against shared libraries, as in "microblaze-uclinux-gcc libc.so myobj.o -o myexec" since microblaze linux cannot generate shared libraries, and thus there is no supply of shared libraries for microblaze linux. Victor -----Original Message----- From: owner-microblaze-uclinux@... [mailto:owner-microblaze-uclinux@...] On Behalf Of John Williams Sent: Wednesday, June 06, 2007 4:54 PM To: microblaze-uclinux@... Subject: Re: [microblaze-uclinux] libdl.a not available in microblaze linux Hi Victor, victor-sv_yeo@... wrote: > I am compiling a program on microblaze linux. The program makes use of > dlopen, dlsym, and dlclose functions. To my surprise, when I compile the > program with -ldl switch, the libdl.a cannot be found. I search through > the petalinux directory, there is no libdl.a as well. > > Does it mean microblaze linux is incapable of supporting dynamic linking > functions (dlopen, dlsym, dlclose)? That is correct. The MicroBlaze gcc toolchain lacks the ability to generate position independent code, which is a prerequisite for shared libraries. The workaround doesn't have to be too painful - just build the library as a static .a archive, and statically link. Regards, John ___________________________ microblaze-uclinux mailing list microblaze-uclinux@... Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
6 Jun 2007 17:58
Re: mounting smbfs
You're the man!
This worked perfectly.
Thanks,
Jim
John Williams wrote:
> Hi Jim,
>
> I got this going, with minor tweaking. Here's how:
>
> apply the attached patch at p0 from petalinux-dist
>
> $ cd ${PETALINUX}/software/petalinux-dist
> $ patch -p0 < samba.patch
>
> $ make menuconfig
>
> Under kernel -> file systems -> network file systems
>
> <*> SMB file system support (to mount Windows shares etc.)
> [ ] Use a default NLS
> [ ] Enable Unix Extensions
>
> Under user/vendor settings -> filesystem applications
>
> --- SAMBA
> [*] samba
> [ ] smbd
> [ ] nmbd
> [*] smbmount
> [*] smbumount
> [ ] uses shared library
>
> rebuild everything, and boot it up
>
> Here's the commandline I used to mount our local fileserver:
>
> # smbmount //raid.itee.uq.edu.au/jwilliams /mnt -o
> username=jwilliams,workgroup=itee
>
> # ls /mnt
>
> ...
>
> I think busybox's mount command is not compatible with smbmount, but
> didn't spend a whole lot of time figuring that out. smbmount seems to
> work fine.
>
> I'll make sure these little tweaks are in the next PetaLinux release.
>
> Cheers,
>
> John
>
>
>
>
> Jim Van Vorst wrote:
>> Folks,
>>
>> I'm trying to mount a windows share on my eval board. I added smbfs
>> to my kernel build and got:
>>
>> # cat /proc/filesystems
>> nodev rootfs
>> nodev bdev
>> nodev proc
>> nodev sockfs
>> nodev pipefs
>> ext2
>> cramfs
>> nodev ramfs
>> msdos
>> vfat
>> nodev nfs
>> nodev smbfs
>> # mount -t smbfs //my_ip/my_share /mnt
>> smbfs: mount_data version 16466812 is not supported
>> mount: Mounting //my_ip/my_share on /mnt failed: Invalid argument
>>
>> If I run mount again I get another random version number. Seems like
>> mount and smbfs are
>> incompatible?
>> I also tried smbmount but I had to play games with smb_mount.h and it
>> looks like the version of smbmount.c
>> is incompatible with the kernel's smbfs also.
>> Has anyone had any success mounting smbfs? This is with the latest
>> petalinux download.
>>
>> Thanks,
>> Jim
>>
>>
>> ___________________________
>> microblaze-uclinux mailing list
>> microblaze-uclinux@...
>> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>> Mailing List Archive :
>> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>>
>>
>
7 Jun 2007 08:33
Trace/BPT trap message
What does this message mean? I started to see it with no particular reason - I just run process, sending packet via UDS socket to another process, waiting for response, printing message's content and leaving: # /home/httpd/cgi-bin/cgi_server # Test Script Name Steps Curr Prcnt ENBL RUN Loops Usage Cntr -------------------------------------------------------------- 1 LEDs_Walk 12 12 100 + - 1 1 1 Module_ID 6 6 100 + - 1 1 2 FPGA_SDRAM 5 5 100 + - 1 1 3 NOR_FLASH 5 5 100 + - 1 1 4 GPIO_SAMPLE 4 4 100 + - 1 1 5 GPIO_WALK_0 32 32 100 + - 1 1 6 GPIO_WALK_1 32 32 100 + - 1 1 7 ETH_PING 1 1 100 + - 1 1 8 CAN_GPIO 2 2 100 + - 1 1 9 MIL_1553_SAMPLE 4 4 100 + - 1 1 Trace/BPT trap Could be some memory violation? Thanks, Leonid.
RSS Feed