Julian Elischer wrote:
>
>
> On Thu, 25 Apr 2002, John Baldwin wrote:
>
> >
> > On 25-Apr-2002 Julian Elischer wrote:
> >
> > kldload sysvipc.ko or compile the SYSV stuff into your kernel.
> > Perhaps the linux kld needs to have a module dependency on
> > the sysvipc modules?
>
> there is no
On Thu, 25 Apr 2002, John Baldwin wrote:
>
> On 25-Apr-2002 Julian Elischer wrote:
>
> kldload sysvipc.ko or compile the SYSV stuff into your kernel.
> Perhaps the linux kld needs to have a module dependency on
> the sysvipc modules?
there is no sysvipc module but this is what I tried..
jul
On Thu, 25 Apr 2002, John Baldwin wrote:
>
> kldload sysvipc.ko or compile the SYSV stuff into your kernel.
> Perhaps the linux kld needs to have a module dependency on
> the sysvipc modules?
I did.. it make no difference.
>
> > julian
>
> --
>
> John Baldwin <[EMAIL PROTECTED]> <>< htt
On 25-Apr-2002 Julian Elischer wrote:
>
>
> after a complete resup, re-checkout and recompile
> on trying to load the linux module:
>
> link_elf: symbol semop undefined
>
>
> Anyone have a quick fix?
kldload sysvipc.ko or compile the SYSV stuff into your kernel.
Perhaps the linux kld ne
after a complete resup, re-checkout and recompile
on trying to load the linux module:
link_elf: symbol semop undefined
Anyone have a quick fix?
julian
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Boris Popov wrote:
>
> On Sat, 3 Jun 2000, Julian Elischer wrote:
>
> > kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon.ko: Exec
> > format error
> > kldload: can't load /usr/local/lib/vmware/lib/modules/vmnet.ko: Exec
> > format error
> > vmware.sh: cannot create /dev/vmnet1: no suc
On Sat, 3 Jun 2000, Julian Elischer wrote:
> kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon.ko: Exec
> format error
> kldload: can't load /usr/local/lib/vmware/lib/modules/vmnet.ko: Exec
> format error
> vmware.sh: cannot create /dev/vmnet1: no such device or address
> jules# dmesg
>
Jeroen Ruigrok van der Werven wrote:
>
> -On [2603 09:30], Julian Elischer ([EMAIL PROTECTED]) wrote:
> >If you use the linux kernel module,
> >you cannot use the vmware module with it.
> >This has changed sometime in the last month or so.
> >the vmware module cannot find a symbol in the linu
cd /usr && mv include include.not && cd src && make includes && rm -fr ../include.not
This worked for me.
> Michael Harnois wrote:
> >
> > On Sat, 03 Jun 2000 00:33:10 -0700, "George W. Dinolt" <[EMAIL PROTECTED]> said:
> >
> > > The following change to /usr/src/modules/linux/Makefile will
-On [2603 09:30], Julian Elischer ([EMAIL PROTECTED]) wrote:
>If you use the linux kernel module,
>you cannot use the vmware module with it.
>This has changed sometime in the last month or so.
>the vmware module cannot find a symbol in the linux
>module that it needs.
The obvious:
which sym
Michael Harnois wrote:
>
> On Sat, 03 Jun 2000 00:33:10 -0700, "George W. Dinolt" <[EMAIL PROTECTED]> said:
>
> > The following change to /usr/src/modules/linux/Makefile will
> > allow one to at least build a workable linux module.
>
> It does, in fact, work now, thanks.
but vmware in
On Fri, 2 Jun 2000 23:58:03 -0700 (PDT), Doug White <[EMAIL PROTECTED]> said:
> You didn't rebuild your modules at the same time.
-current (theoretically) rebuilds the modules when you rebuild the kernel.
--
Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA
[EMAIL PROTECTED]
On Sat, 03 Jun 2000 00:33:10 -0700, "George W. Dinolt" <[EMAIL PROTECTED]> said:
> The following change to /usr/src/modules/linux/Makefile will
> allow one to at least build a workable linux module.
It does, in fact, work now, thanks.
--
Michael D. Harnois, Redeemer Lutheran Church, Wa
On Sat, 03 Jun 2000 00:33:10 -0700, "George W. Dinolt" <[EMAIL PROTECTED]> said:
> Michael: I suspect that you may have
> options COMPAT_LINUX
> defined in your kernel config file.
Nope. Used to have, though.
--
Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA
[EMAIL P
On Sat, 3 Jun 2000, George W. Dinolt wrote:
> Michael:
>
> I suspect that you may have
>
> options COMPAT_LINUX
>
> defined in your kernel config file.
>
> Re your problem with Linux not working. I had the same problem. It seems
> to be related to the changes in the generation of the file
> l
On 2 Jun 2000, Michael Harnois wrote:
> Seems to have happened since I updated and made world and kernel this
> afternoon.
>
> link_elf: symbol LINUX_SIGF_HANDLER undefined
> pid 208 (ldconfig), uid 0: exited on signal 11 (core dumped)
Fixed.
Bruce
To Unsubscribe: send mail to [EMAIL PROTE
Michael:
I suspect that you may have
options COMPAT_LINUX
defined in your kernel config file.
Re your problem with Linux not working. I had the same problem. It seems
to be related to the changes in the generation of the file
linux_assym.h. A new method for generating these kind of symbols was
If you use the linux kernel module,
you cannot use the vmware module with it.
This has changed sometime in the last month or so.
the vmware module cannot find a symbol in the linux
module that it needs.
If you compile in the linux code, then vmware works fine.
--
__--_|\ Julian Elischer
On 2 Jun 2000, Michael Harnois wrote:
> Seems to have happened since I updated and made world and kernel this
> afternoon.
>
> link_elf: symbol LINUX_SIGF_HANDLER undefined
> pid 208 (ldconfig), uid 0: exited on signal 11 (core dumped)
> dc0: promiscuous mode enabled
> link_elf: symbol LINUX_SI
Seems to have happened since I updated and made world and kernel this
afternoon.
link_elf: symbol LINUX_SIGF_HANDLER undefined
pid 208 (ldconfig), uid 0: exited on signal 11 (core dumped)
dc0: promiscuous mode enabled
link_elf: symbol LINUX_SIGF_HANDLER undefined
KLD rtc.ko: depends on linux - n
20 matches
Mail list logo
