You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my work machine (Debian 12.2, Gnome, Kitty/Fish, no wine installed), it runs flawlessly
On my home machine (Arch, Gnome, Kitty/Fish, wine installed), it seems to be automatically be detected as a Windows binary, tries to run via wine, and crashes:
20:41:24 ~ ./llamafile-server-0.1-llava-v1.5-7b-q4
0088:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000142
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb" failed to start: 1114
00b0:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
00a8:err:sync:RtlpWaitForCriticalSection section 7BD9A2C0 "../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 00a8, blocked by 00b0, retrying (60 sec)
003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"WineBus" failed to start: 1053
003c:err:service:process_send_start_message service L"PlugPlay" failed to start
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"PlugPlay" failed to start: 1053
00b0:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
00b0:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
00b0:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0154:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
wine: configuration in L"/home/ronj/.wine" has been updated.
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: Bad EXE format for Z:\home\ronj\llamafile-server-0.1-llava-v1.5-7b-q4.
If instead of ./llamafile-server-0.1-llava-v1.5-7b-q4 I simply sh ./llamafile-server-0.1-llava-v1.5-7b-q4, things work well.
Is this a known glitch, or a problem with my machine? Can something be done by llamafile packaging / binary build to "de-prioritize" running via wine and prefer running as native Linux? Should README usage suggestion be updated to tell users to sh ./llamafile instead of just ./llamafile ?
The text was updated successfully, but these errors were encountered:
Today I tried simonwillison's llamafile example on 2 machines:
wine
installed), it runs flawlesslywine
installed), it seems to be automatically be detected as a Windows binary, tries to run viawine
, and crashes:If instead of
./llamafile-server-0.1-llava-v1.5-7b-q4
I simplysh ./llamafile-server-0.1-llava-v1.5-7b-q4
, things work well.Is this a known glitch, or a problem with my machine? Can something be done by llamafile packaging / binary build to "de-prioritize" running via wine and prefer running as native Linux? Should README usage suggestion be updated to tell users to
sh ./llamafile
instead of just./llamafile
?The text was updated successfully, but these errors were encountered: