Closed mxsur closed 5 months ago
Thanks for trying out MAX and Mojo! As of today, Ubuntu is officially supported for MAX. Please check out the getting started guide.
@ehsanmok thanks for a prompt reply. Actually I followed it and used curl -s https://get.modular.com | sh -
. As the result - see the error above. Modular is installed successfully but modular install max
fails
@mxsur we're digging into this a bit -- would you be willing to send over the result of modular config-list
?
@sparadiso pls see below
❯ modular config-list
max.cache_dir = /home/maksym/.local/share/modular/.max_cache
max.enable_compile_progress = true
max.enable_model_ir_cache = true
max.engine_lib = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib/libmodular-framework-common.so.19.0git
max.graph_lib = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib/libmof.so.19.0git
max.name = MAX Platform
max.path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max
max.torch_ext_lib = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib/libmodular-framework-torch-ext.so.19.0git
max.version = 24.2.0
mojo-max.compilerrt_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib/libKGENCompilerRTShared.so.19.0git
mojo-max.compilerrt_static_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib/libKGENCompilerRT-static.a
mojo-max.driver_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/bin/mojo
mojo-max.import_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib/mojo,/home/maksym/.local/share/modular/pkg/packages.modular.com_max/pkg
mojo-max.jupyter_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib/libMojoJupyter.so.19.0git
mojo-max.lldb_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/bin/mojo-lldb
mojo-max.lldb_plugin_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib/libMojoLLDB.so.19.0git
mojo-max.lldb_visualizers_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib/lldb-visualizers
mojo-max.lldb_vscode_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/bin/mojo-lldb-dap
mojo-max.lsp_server_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/bin/mojo-lsp-server
mojo-max.mblack_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib/mblack/mblack
mojo-max.orcrt_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib/liborc_rt.a
mojo-max.python_lib = /home/maksym/miniconda3/lib/libpython3.12.so.1.0
mojo-max.repl_entry_point = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib/mojo-repl-entry-point
mojo-max.system_libs = -lrt,-ldl,-lpthread,-lm,-lz,-ltinfo
mojo-max.test_executor_path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max/lib//__w/modular/modular/.derived/build-release/bin/mojo-test-executor
package_packages_modular_com_max.package_name = MAX Platform
package_packages_modular_com_max.path = /home/maksym/.local/share/modular/pkg/packages.modular.com_max
package_packages_modular_com_max.short_name = max
package_packages_modular_com_max.state = installing
package_packages_modular_com_max.version = 24.2.0
modular install mojo loc("#M.target
":1:50): error: duplicate or unknown struct parameter name: cpu [2426:2426:20240330,115425.961693:ERROR file_io_posix.cc:144] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2) [2426:2426:20240330,115425.961732:ERROR file_io_posix.cc:144] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2) Please submit a bug report to https://github.com/modularml/max/issues and include the crash backtrace along with all the relevant source codes. Stack dump:
- Program arguments: modular install mojo
0 0x000055b0fd644427 (/usr/bin/modular+0x1544427)
1 0x000055b0fd6420de (/usr/bin/modular+0x15420de)
2 0x000055b0fd644aaf (/usr/bin/modular+0x1544aaf)
3 0x00007f47423d8520 (/lib/x86_64-linux-gnu/libc.so.6+0x42520)
4 0x000055b0fda68914 (/usr/bin/modular+0x1968914)
5 0x000055b0fda67e3c (/usr/bin/modular+0x1967e3c)
6 0x000055b0fda5381c (/usr/bin/modular+0x195381c)
7 0x000055b0fda51fa0 (/usr/bin/modular+0x1951fa0)
8 0x000055b0fd58c55d (/usr/bin/modular+0x148c55d)
9 0x000055b0fd589ff2 (/usr/bin/modular+0x1489ff2)
10 0x00007f47423bfd90 (/lib/x86_64-linux-gnu/libc.so.6+0x29d90)
11 0x00007f47423bfe40 __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x29e40)
12 0x000055b0fd5896ae (/usr/bin/modular+0x14896ae)
Segmentation fault uname --all Linux xxxxxxxx 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Hi @mxsur, can you check that MODULAR_HOME is set in your shell? In your case since you are on distro with XDG User Directories it should be set to something like:
export MODULAR_HOME=/home/maksym/.local/share/modular/
You have to do modular auth
again after it's set. Then try to run modular clean
and modular install max
again.
Little background, some of our recent docs changes now tell users to set MODULAR_HOME later when installing mojo or max and not before doing modular auth
which is a mistake (https://docs.modular.com/engine/get-started/). If you are on a distro that has adopted the XDG Base Directories specification (https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html) things will not probably work right now since we don't fully support XDG Base Dir just yet. To overcome that you have to explicitly set MODULAR_HOME before interacting with with modular tool.
In your case for you what is likely happening is that /home/maksym/.local/share/modular/
contains part of your modular files and /home/maksym/.config/modular/
contains the other part of your install (like your modular config), and since they are not the same directory later Mojo and MAX package scripts still expect all the files in one folder like they are on older distros that don't use XDG yet. We are working towards eventually supporting XDG Base Directory spec support in new packages but for now MODULAR_HOME has to be set to keep all your modular related files in the same directory together.
Hi @zbowling , thanks! That solved my issue.
@runbikeswim I'm closing this ticket. Pls reopen a new one if your issue is still unaddressed.
Bug description
Installing both
max
andmojo
fails with the same errorSteps to reproduce
modular install max && modular install mojo
System information