Re: vmware1/linux broken

2000-06-04 Thread Julian Elischer

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 such device or address
  jules# dmesg
  [...]
  link_elf: symbol linux_ioctl_register_handler undefined
  link_elf: symbol linux_ioctl_register_handler undefined
  jules#
 
 Could you check if vmmon and vmnet sources contains the following
 lines:
 
 MODULE_DEPEND(vmmon, linux, 1, 1, 1); , and
 MODULE_DEPEND(vmnet, linux, 1, 1, 1); respectively ?
 
 If not, add one line to the each module and recompile them. I'm
 unsure if vmware1 port was updated to reflect recent changes in the
 kernel. (vmware2 runs fine for me, the only grief is that license will
 expire soon :)


that fixed it ..
I added the lines to:
usr/ports/emulators/vmware/work/vmware-distrib/vmmon-only/freebsd/linux_emu.c
and
/usr/ports/emulators/vmware/work/vmware-distrib/vmnet-only/freebsd/vmnet_linux.c

I'll try figure out how to fix the port.

 
  the symbols are present and the linux module is loaded.
  link-elf is just incapable of seeing symbols in the module,
  only in the actual kernel.
 
 The symbols looked up in the module name space only if dependency
 tag is present. This effectively allows us to have multiple versions of
 kernel interfaces to be loaded simultaneously.
 
 --
 Boris Popov
 http://www.butya.kz/~bp/
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message

-- 
  __--_|\  Julian Elischer
 /   \ [EMAIL PROTECTED]
(   OZ) World tour 2000
--- X_.---._/  presently in:  Perth
v


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



vmware1/linux broken

2000-06-03 Thread Julian Elischer

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
 /   \ [EMAIL PROTECTED]
(   OZ) World tour 2000
--- X_.---._/  presently in:  Perth
v


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: vmware1/linux broken

2000-06-03 Thread Jeroen Ruigrok van der Werven

-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 symbol? =)

-- 
Jeroen Ruigrok van der Werven  Network- and systemadministrator
[EMAIL PROTECTED]VIA Net.Works The Netherlands
BSD: Technical excellence at its best  http://www.via-net-works.nl
Who looks under the surface does so at his own risk...


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: vmware1/linux broken

2000-06-03 Thread Julian Elischer

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 linux
 module that it needs.
 
 The obvious:
 
 which symbol? =)

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
[...]
link_elf: symbol linux_ioctl_register_handler undefined
link_elf: symbol linux_ioctl_register_handler undefined
jules# 

the symbols are present and the linux module is loaded.
link-elf is just incapable of seeing symbols in the module, 
only in the actual kernel.

if you compile with COMPAT_LINUX
it all works fine.

 
 --
 Jeroen Ruigrok van der Werven  Network- and systemadministrator
 [EMAIL PROTECTED]VIA Net.Works The Netherlands
 BSD: Technical excellence at its best  http://www.via-net-works.nl
 Who looks under the surface does so at his own risk...

-- 
  __--_|\  Julian Elischer
 /   \ [EMAIL PROTECTED]
(   OZ) World tour 2000
--- X_.---._/  presently in:  Perth
v


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: vmware1/linux broken

2000-06-03 Thread Boris Popov

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
 [...]
 link_elf: symbol linux_ioctl_register_handler undefined
 link_elf: symbol linux_ioctl_register_handler undefined
 jules# 

Could you check if vmmon and vmnet sources contains the following
lines:

MODULE_DEPEND(vmmon, linux, 1, 1, 1); , and
MODULE_DEPEND(vmnet, linux, 1, 1, 1); respectively ?

If not, add one line to the each module and recompile them. I'm
unsure if vmware1 port was updated to reflect recent changes in the
kernel. (vmware2 runs fine for me, the only grief is that license will
expire soon :)

 the symbols are present and the linux module is loaded.
 link-elf is just incapable of seeing symbols in the module, 
 only in the actual kernel.

The symbols looked up in the module name space only if dependency
tag is present. This effectively allows us to have multiple versions of
kernel interfaces to be loaded simultaneously.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message