Re: [OpenIndiana-discuss] OI new user questions - 2
Yes, but it seems quite messy with little to no help or docs. I think it is much easier to install Solarish in BIOS on one disk, and Win10 on another disk. I will try out OmniOS, and if is has the same problems, then the error might be in illumos? Or? Solaris 11.3 does not have this error, On Thursday, December 17, 2020, 08:07:12 PM GMT+1, John D Groenveld wrote: In message <752081985.1212170.1608221081...@mail.yahoo.com>, Kalle Anka via openindiana-discuss writes: >Even if it does work, I am not really keen on running of my iGPU. Wasn't your goal to use your on-board Intel GPU for OI and then dedicate the nVidia GPU to your Windows Gamer VM running on bhyve? If so, I would enable the Intel GPU in the BIOS, install OI via the text installer: https://www.openindiana.org/download/> John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
In message <752081985.1212170.1608221081...@mail.yahoo.com>, Kalle Anka via openindiana-discuss writes: >Even if it does work, I am not really keen on running of my iGPU. Wasn't your goal to use your on-board Intel GPU for OI and then dedicate the nVidia GPU to your Windows Gamer VM running on bhyve? If so, I would enable the Intel GPU in the BIOS, install OI via the text installer: https://www.openindiana.org/download/> John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
@Gary Mills, I have tried to boot VESA or non VESA, Bios, legacy, etc etc. It doesnt work. You also suggested that I might try with using the iGPU instead of my external Nvidia GPU? Even if it does work, I am not really keen on running of my iGPU. So, I cannot get OI to install on my hardware: Supermicro X10-SAT motherboard, Xeon E3-1245v3, ECC RAM. Therefore I will not pursue this OI direction any further. I will instead install Solaris 11.3 (I cannot get 11.4 to work, because graphics does not work). I will try out OI in the next update, and hope it will work. Meanwhile, I would be interested in leaving a bug report, if that is possible. I dont know how to do a bug report though. Can I create a ticket on my problem? Or are there slim chances this bug will be fixed? A last question: do you know if OI software packages will install on Solaris 11.3? Thanx all for your help, guys! I hope to see you again in the next version of OI. Solarish rocks. :) ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
On Mon, Dec 14, 2020 at 04:20:49PM +, Kalle Anka via openindiana-discuss wrote: > > @Gary Mills, > the "hal service" has started and runs fine. I get the same output as you. Okay, hal is running. That is good to know. > However, there are several posts from Linux users, having the same > problems as I do. For instance: > https://unix.stackexchange.com/questions/152418/x-server-started-by-kdm-dies-during-startup-because-of-keymap-couldnt-be-loaded > http://forums.debian.net/viewtopic.php?f=10=107337 > https://bbs.archlinux.org/viewtopic.php?id=54015=2 > It seems that this problem can be fixed by reinstalling > "x11-xkb-utils" or "xkbcomp " if you read the threads. So I dont > really understand how to do that on OI? That solution is too magical for me. The OI USB image should have everything that it needs. > I also tried to dabble with BIOS settings > EHCI > XHCI > Legacy USB > ... > but I still get the same Xorg error messages as usual. How can I > fix the xkbcomp software on OI? You may be chasing the wrong fox. It seems to me that the real problem is that something is telling Xorg not to use hal. You can't do that. Near the beginning of the Xorg log is the statement: [44.620] (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. Your Xorg seems to search for the keyboard without the aid of hal. It should not be compiling a keymap at all. Perhaps the command does not exist. Perhaps it's looking in the wrong place. In any case, the error is here. > BTW, I dont use the integrated graphics of Intel HD4600, I have > shut it off. I only use the Geforce GTX 1070 Ti. And Vesa driver. How do you specify the VESA driver? Xorg does that itself if it finds that the other drivers don't work. Could you try not specifying the VESA driver for a test? In fact, try booting the OI USB image without making any changes. It should be a BIOS boot. Maybe you've already tried that. You could even try enabling the built-in Intel video and disabling the external video in the BIOS setup. Maybe the OI boot will work correctly then. The video output will be on a different connector, of course. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
I read all answers, so thanx for your help guys! However, I do not receive every reply mail so I can not reply to the correct mail. I reply to the mail I get. And now I reply to John D Groenvald. @Gary Mills, the "hal service" has started and runs fine. I get the same output as you. However, there are several posts from Linux users, having the same problems as I do. For instance: https://unix.stackexchange.com/questions/152418/x-server-started-by-kdm-dies-during-startup-because-of-keymap-couldnt-be-loaded http://forums.debian.net/viewtopic.php?f=10=107337 https://bbs.archlinux.org/viewtopic.php?id=54015=2 It seems that this problem can be fixed by reinstalling "x11-xkb-utils" or "xkbcomp " if you read the threads. So I dont really understand how to do that on OI? I also tried to dabble with BIOS settings EHCI XHCI Legacy USB ... but I still get the same Xorg error messages as usual. How can I fix the xkbcomp software on OI? BTW, I dont use the integrated graphics of Intel HD4600, I have shut it off. I only use the Geforce GTX 1070 Ti. And Vesa driver. Here is the tail of dmesg and Xorg.0.log 122.271] (--) VESA(0): Virtual size is 1024x768 (pitch 1024) [ 122.271] (**) VESA(0): *Built-in mode "1024x768" [ 122.271] (**) VESA(0): *Built-in mode "800x600" [ 122.271] (**) VESA(0): *Built-in mode "640x480" [ 122.271] (==) VESA(0): DPI set to (96, 96) [ 122.271] (**) VESA(0): Using "Shadow Framebuffer" [ 122.271] (II) Loading sub module "shadow" [ 122.271] (II) LoadModule: "shadow" [ 122.271] (II) Loading /usr/lib/xorg/modules/amd64/libshadow.so [ 122.271] (II) Module shadow: vendor="X.Org Foundation" [ 122.271] compiled for 1.19.7, module version = 1.1.0 [ 122.271] ABI class: X.Org ANSI C Emulation, version 0.4 [ 122.271] (II) Loading sub module "fb" [ 122.271] (II) LoadModule: "fb" [ 122.271] (II) Loading /usr/lib/xorg/modules/amd64/libfb.so [ 122.271] (II) Module fb: vendor="X.Org Foundation" [ 122.271] compiled for 1.19.7, module version = 1.0.0 [ 122.271] ABI class: X.Org ANSI C Emulation, version 0.4 [ 122.271] (==) Depth 24 pixmap format is 32 bpp [ 122.271] (II) Loading sub module "int10" [ 122.271] (II) LoadModule: "int10" [ 122.271] (II) Loading /usr/lib/xorg/modules/amd64/libint10.so [ 122.271] (II) Module int10: vendor="X.Org Foundation" [ 122.271] compiled for 1.19.7, module version = 1.0.0 [ 122.271] ABI class: X.Org Video Driver, version 23.0 [ 122.271] (II) VESA(0): initializing int10 [ 122.276] (II) VESA(0): Primary V_BIOS segment is: 0xc000 [ 122.372] (II) VESA(0): VESA BIOS detected [ 122.372] (II) VESA(0): VESA VBE Version 3.0 [ 122.372] (II) VESA(0): VESA VBE Total Mem: 16384 kB [ 122.372] (II) VESA(0): VESA VBE OEM: NVIDIA [ 122.372] (II) VESA(0): VESA VBE OEM Software Rev: 134.4 [ 122.372] (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation [ 122.372] (II) VESA(0): VESA VBE OEM Product: GP104 Board [ 122.372] (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev [ 122.372] (II) VESA(0): virtual address = fc7fea80, VGAbase = fc7feed6 physical address = 0xd100, size = 16777216 [ 122.385] (II) VESA(0): Setting up VESA Mode 0x118 (1024x768) [ 122.527] (==) VESA(0): Default visual is TrueColor [ 122.527] (==) VESA(0): Backing store enabled [ 122.527] (==) VESA(0): DPMS enabled [ 122.527] (==) RandR enabled [ 122.530] (II) AIGLX: Screen 0 is not DRI2 capable [ 122.530] (EE) AIGLX: reverting to software rendering [ 122.542] (II) IGLX: enabled GLX_MESA_copy_sub_buffer [ 122.542] (II) IGLX: Loaded and initialized swrast [ 122.542] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 122.575] (EE) Error compiling keymap (server-0) executing '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "/var/run/xkb/server-0.xkm"' [ 122.575] (EE) XKB: Couldn't compile keymap [ 122.575] (EE) XKB: Failed to load keymap. Loading default keymap instead. [ 122.597] (EE) Error compiling keymap (server-0) executing '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "/var/run/xkb/server-0.xkm"' [ 122.597] (EE) XKB: Couldn't compile keymap [ 122.597] XKB: Failed to compile keymap [ 122.597] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. [ 122.597] (EE) Fatal server error: [ 122.597] (EE) Failed to activate virtual core keyboard: 2(EE) [ 122.597] (EE) Please consult the Project OpenIndiana support at http://openindiana.org for help. [ 122.597] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 122.597] (EE) [ 126.248] (EE) Server terminated with error (1). Closing log
Re: [OpenIndiana-discuss] OI new user questions - 2
On Thu, Dec 10, 2020 at 10:56:42PM +, Kalle Anka via openindiana-discuss wrote: > [ 137.882] (EE) Error compiling keymap (server-0) executing > '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD > keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are > not fatal to the X server" "/var/run/xkb/server-0.xkm"' > [ 137.882] (EE) XKB: Couldn't compile keymap > [ 137.882] (EE) XKB: Failed to load keymap. Loading default keymap instead. > [ 137.903] (EE) Error compiling keymap (server-0) executing > '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD > keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are > not fatal to the X server" "/var/run/xkb/server-0.xkm"' > [ 137.904] (EE) XKB: Couldn't compile keymap > [ 137.904] XKB: Failed to compile keymap > [ 137.904] Keyboard initialization failed. This could be a missing or > incorrect setup of xkeyboard-config. > [ 137.904] (EE) > Fatal server error: > [ 137.904] (EE) Failed to activate virtual core keyboard: 2(EE) > [ 137.904] (EE) > Please consult the Project OpenIndiana support > at http://openindiana.org > for help. > [ 137.904] (EE) Please also check the log file at "/var/log/Xorg.0.log" for > additional information. > [ 137.904] (EE) > [ 141.548] (EE) Server terminated with error (1). Closing log file. I did some testing with the OI-hipster-gui-20201031.usb USB image on one of my systems. It uses an Intel CPU with built-in Intel graphics. It booted the image's copy of OI to produce the usual desktop with a few additional icons. The portion of the /var/log/Xorg.0.log file that shows the keyboard configuration was like this: [ 141.103] (II) config/hal: Adding input device hotkey [ 141.104] (II) LoadModule: "hotkey" [ 141.104] (II) Loading /usr/lib/xorg/modules/input/amd64/hotkey_drv.so [ 141.108] (II) Module hotkey: vendor="X.Org Foundation" [ 141.108]compiled for 1.19.5, module version = 1.0.0 [ 141.108]Module class: X.Org XInput Driver [ 141.108]ABI class: X.Org XInput driver, version 24.1 [ 141.108] (II) Using input driver 'hotkey' for 'hotkey' [ 141.108] (**) hotkey: always reports core events [ 141.108] (II) XINPUT: Adding extended input device "hotkey" (type: KEYBOARD, id 6) [ 141.109] (**) hotkey_events_init and pipe open succeeded [ 141.110] (II) config/hal: Adding input device keyboard [ 141.111] (II) LoadModule: "kbd" [ 141.111] (II) Loading /usr/lib/xorg/modules/input/amd64/kbd_drv.so [ 141.111] (II) Module kbd: vendor="X.Org Foundation" [ 141.111]compiled for 1.19.5, module version = 1.9.0 [ 141.111]Module class: X.Org XInput Driver [ 141.111]ABI class: X.Org XInput driver, version 24.1 [ 141.111] (II) Using input driver 'kbd' for 'keyboard' [ 141.112] (**) keyboard: always reports core events [ 141.112] (**) keyboard: always reports core events [ 141.112] (**) Option "Device" "/dev/usb/hid1" [ 141.112] (II) keyboard: Opened device "/dev/usb/hid1" [ 141.112] (**) Option "XkbRules" "base" [ 141.112] (**) Option "XkbModel" "sun_type6_usb" [ 141.112] (**) Option "XkbLayout" "us" [ 141.112] (WW) Option "XkbVariant" requires a string value [ 141.112] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1043_8694_14/device_8/keyboard_0_if0_1_logicaldev_input" [ 141.112] (II) XINPUT: Adding extended input device "keyboard" (type: KEYBOARD, id 7) [ 141.112] (**) Option "StreamsModule" "usbkbm" [ 141.112] (--) keyboard: Keyboard type: USB (6) [ 141.112] (--) keyboard: Keyboard layout: 0 Note that hal is used to obtain the keyboard device in my case. I wonder if the hal service has failed in your case. Here's how it looks to me: jack@openindiana:/jack$ svcs -l svc:/system/hal:default fmri svc:/system/hal:default name Hardware Abstraction Layer daemon enabled true stateonline next_state none state_time Sun Dec 13 10:38:42 2020 logfile /var/svc/log/system-hal:default.log restartersvc:/system/svc/restarter:default contract_id 41 dependency require_all/none svc:/system/filesystem/minimal (online) dependency require_all/none svc:/system/device/local (online) dependency require_all/none svc:/system/dbus (online) dependency require_all/none svc:/system/sysevent (online) dependency optional_all/none svc:/system/keymap (online) -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
Am 11.12.20 um 03:43 schrieb Gary Mills: On Thu, Dec 10, 2020 at 10:56:42PM +, Kalle Anka via openindiana-discuss wrote: Gary Mills,How far the boot process goes? Well, I booted into BIOS and it boots until X11, which will not start. At that point, it is actually running a version of OI, coming from the USB image. Here is the Xorg.0.log file. I tried another keyboard, and also I tried it in USB2 and USB3 ports. But still it doesnt work to boot X11. It seems to be an error with the keyboard? I dont get it, I have a Sun keyboard. And I tried another cheap keyboard. I have two systems with Sun keyboards running OI. They are both USB keyboards. Something is wrong with your keyboard, though. The log file below indicates that. Do you have a BIOS setting that says something about a legacy keyboard? You may have to change that. I have a Geforce GTX 1070 Ti gpu, so I instead used VESA driver. And ACPI. According to the log file below, it is an NVIDIA card. That should be supported. Normally you are better off not to specify the VESA driver, but let Xorg figure it out. The graphics card is probably too new for our old NVIDIA driver. You should download a recent driver from here: https://www.nvidia.com/en-us/drivers/unix/solaris-display-archive/ and simply run the downloaded file as root. It should install all necessary files then. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
On Thu, Dec 10, 2020 at 10:56:42PM +, Kalle Anka via openindiana-discuss wrote: > Gary Mills,How far the boot process goes? Well, I booted into BIOS > and it boots until X11, which will not start. At that point, it is actually running a version of OI, coming from the USB image. > Here is the Xorg.0.log > file. I tried another keyboard, and also I tried it in USB2 and USB3 > ports. But still it doesnt work to boot X11. It seems to be an error > with the keyboard? I dont get it, I have a Sun keyboard. And I tried > another cheap keyboard. I have two systems with Sun keyboards running OI. They are both USB keyboards. Something is wrong with your keyboard, though. The log file below indicates that. Do you have a BIOS setting that says something about a legacy keyboard? You may have to change that. > I have a Geforce GTX 1070 Ti gpu, so I instead used VESA driver. > And ACPI. According to the log file below, it is an NVIDIA card. That should be supported. Normally you are better off not to specify the VESA driver, but let Xorg figure it out. > X.Org X Server 1.19.7 [...] > [ 137.678] (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation > [ 137.678] (II) VESA(0): VESA VBE OEM Product: GP104 Board > [ 137.678] (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev > [ 137.678] (II) VESA(0): virtual address = fc7fea80, VGAbase = > fc7feed6 > physical address = 0xd100, size = 16777216 > [ 137.691] (II) VESA(0): Setting up VESA Mode 0x118 (1024x768) > [ 137.834] (==) VESA(0): Default visual is TrueColor > [ 137.834] (==) VESA(0): Backing store enabled > [ 137.834] (==) VESA(0): DPMS enabled > [ 137.834] (==) RandR enabled > [ 137.837] (II) AIGLX: Screen 0 is not DRI2 capable > [ 137.837] (EE) AIGLX: reverting to software rendering > [ 137.849] (II) IGLX: enabled GLX_MESA_copy_sub_buffer > [ 137.850] (II) IGLX: Loaded and initialized swrast > [ 137.850] (II) GLX: Initialized DRISWRAST GL provider for screen 0 > [ 137.882] (EE) Error compiling keymap (server-0) executing > '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD > keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are > not fatal to the X server" "/var/run/xkb/server-0.xkm"' > [ 137.882] (EE) XKB: Couldn't compile keymap > [ 137.882] (EE) XKB: Failed to load keymap. Loading default keymap instead. > [ 137.903] (EE) Error compiling keymap (server-0) executing > '"/usr/bin/xkbcomp" -w 1 "-R/usr/share/X11/xkb" -xkm "-" -em1 "The XKEYBOARD > keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are > not fatal to the X server" "/var/run/xkb/server-0.xkm"' > [ 137.904] (EE) XKB: Couldn't compile keymap > [ 137.904] XKB: Failed to compile keymap > [ 137.904] Keyboard initialization failed. This could be a missing or > incorrect setup of xkeyboard-config. > [ 137.904] (EE) > Fatal server error: > [ 137.904] (EE) Failed to activate virtual core keyboard: 2(EE) > [ 137.904] (EE) > Please consult the Project OpenIndiana support > at http://openindiana.org > for help. > [ 137.904] (EE) Please also check the log file at "/var/log/Xorg.0.log" for > additional information. > [ 137.904] (EE) > [ 141.548] (EE) Server terminated with error (1). Closing log file. I left the portion of the X11 server log file that shows the errors. Mine is quite different. Here's the keyboard portion: [43.648] (II) Using input driver 'kbd' for 'keyboard' [43.648] (**) keyboard: always reports core events [43.648] (**) keyboard: always reports core events [43.648] (**) Option "Device" "/dev/usb/hid1" [43.648] (II) keyboard: Opened device "/dev/usb/hid1" [43.648] (**) Option "XkbRules" "base" [43.648] (**) Option "XkbModel" "sun_type6_usb" [43.648] (**) Option "XkbLayout" "us" [43.648] (WW) Option "XkbVariant" requires a string value [43.648] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/pci_0_0/pci1043_8694_14/device_8/keyboard_0_if0_4_logicaldev_input" [43.648] (II) XINPUT: Adding extended input device "keyboard" (type: KEYBOARD, id 7) [43.648] (**) Option "StreamsModule" "usbkbm" [43.648] (--) keyboard: Keyboard type: USB (6) [43.648] (--) keyboard: Keyboard layout: 0 -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
In message <23563143.4281443.1607641002...@mail.yahoo.com>, Kalle Anka via open indiana-discuss writes: >y try it out. But first I must migrate off my data so I can format the disk. I I would install OI to a virgin disk as was recommend in the earlier thread about the perils of dual booting, perhaps to an external USB drive, while I consulted Microsoft and Oracle forums to figure out how to overcome the barriers to exit. Happy hacking, John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
John Groevald,Yes, it is a good idea to use the text install! I will definitely try it out. But first I must migrate off my data so I can format the disk. I can not write my Windows data from my Windows NAS to my Solaris folders (I need to shuffle data around so this step is necessary) though. I dont know why. Maybe something with write permissions? When I have done this, I will try the text install. Thanx! :) --- Gary Mills,How far the boot process goes? Well, I booted into BIOS and it boots until X11, which will not start. Here is the Xorg.0.log file. I tried another keyboard, and also I tried it in USB2 and USB3 ports. But still it doesnt work to boot X11. It seems to be an error with the keyboard? I dont get it, I have a Sun keyboard. And I tried another cheap keyboard. I have a Geforce GTX 1070 Ti gpu, so I instead used VESA driver. And ACPI. [ 137.121] X.Org X Server 1.19.7 Release Date: 2019-03-02 [ 137.121] X Protocol Version 11, Revision 0 [ 137.121] Build Operating System: SunOS 5.11 i86pc [ 137.121] Current Operating System: SunOS openindiana 5.11 illumos-06524cf4e4 i86pc [ 137.121] Build Date: 24 September 2020 02:36:42PM [ 137.121] Solaris ABI: 64-bit [ 137.121] Current version of pixman: 0.38.0 [ 137.121] Before reporting problems, check http://openindiana.org to make sure that you have the latest version. [ 137.121] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 137.121] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 10 20:08:07 2020 [ 137.121] (==) Using config file: "/etc/X11/xorg.conf" [ 137.121] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 137.121] (==) No Layout section. Using the first Screen section. [ 137.121] (==) No screen section available. Using defaults. [ 137.121] (**) |-->Screen "Default Screen Section" (0) [ 137.121] (**) | |-->Monitor "" [ 137.122] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 137.122] (**) | |-->Device "Card0" [ 137.122] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 137.122] (==) Automatically adding devices [ 137.122] (==) Automatically enabling devices [ 137.122] (==) Not automatically adding GPU devices [ 137.122] (==) Max clients allowed: 256, resource mask: 0x1f [ 137.122] (==) FontPath set to: catalogue:/etc/X11/fontpath.d [ 137.122] (==) ModulePath set to "/usr/lib/xorg/modules/amd64,/usr/X11/lib/modules/" [ 137.122] (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. [ 137.122] (II) Loader magic: 6f9020 [ 137.122] (II) Module ABI versions: [ 137.122] X.Org ANSI C Emulation: 0.4 [ 137.122] X.Org Video Driver: 23.0 [ 137.122] X.Org XInput driver : 24.1 [ 137.122] X.Org Server Extension : 10.0 [ 137.125] (--) PCI:*(0:1:0:0) 10de:1b82:10de:119d rev 161, Mem @ 0xeb00/16777216, 0xc000/268435456, 0xd000/33554432, I/O @ 0xe000/128 [ 137.125] (II) LoadModule: "glx" [ 137.125] (II) Loading /usr/lib/xorg/modules/extensions/amd64/libglx.so [ 137.128] (II) Module glx: vendor="X.Org Foundation" [ 137.129] compiled for 1.19.7, module version = 1.0.0 [ 137.129] ABI class: X.Org Server Extension, version 10.0 [ 137.129] (II) LoadModule: "vesa" [ 137.129] (II) Loading /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so [ 137.130] (II) Module vesa: vendor="X.Org Foundation" [ 137.130] compiled for 1.19.5, module version = 2.4.0 [ 137.130] Module class: X.Org Video Driver [ 137.130] ABI class: X.Org Video Driver, version 23.0 [ 137.130] (II) VESA: driver for VESA chipsets: vesa [ 137.130] (++) using VT number 7 [ 137.130] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 137.130] (II) Loading sub module "vbe" [ 137.130] (II) LoadModule: "vbe" [ 137.130] (II) Loading /usr/lib/xorg/modules/amd64/libvbe.so [ 137.130] (II) Module vbe: vendor="X.Org Foundation" [ 137.130] compiled for 1.19.7, module version = 1.1.0 [ 137.130] ABI class: X.Org Video Driver, version 23.0 [ 137.130] (II) Loading sub module "int10" [ 137.130] (II) LoadModule: "int10" [ 137.130] (II) Loading /usr/lib/xorg/modules/amd64/libint10.so [ 137.130] (II) Module int10: vendor="X.Org Foundation" [ 137.130] compiled for 1.19.7, module version = 1.0.0 [ 137.130] ABI class: X.Org Video Driver, version 23.0 [ 137.130] (II) VESA(0): initializing int10 [ 137.134] (II) VESA(0): Primary V_BIOS segment is: 0xc000 [ 137.231] (II) VESA(0): VESA BIOS detected [ 137.231] (II) VESA(0): VESA VBE Version 3.0 [ 137.231] (II) VESA(0): VESA VBE Total Mem: 16384 kB [ 137.231] (II)
Re: [OpenIndiana-discuss] OI new user questions - 2
On Thu, Dec 10, 2020 at 05:54:12PM +, Kalle Anka via openindiana-discuss wrote: > Yes I tried to boot the usb stick both in UEFI and BIOS mode. Both > fail. In what way? I see some error messages in the dmesg output. I > have pasted that long dmesg output in a reply here with date: Wed > Dec 9 20:47:35 UTC 2020, you can read that mail for more > information. But it seems that X11 does not start. The screen > flickers thrice and then exits to command line. OI only works in BIOS mode, although the OI loader works in both. I was confused by that difference. So, use BIOS mode. How far does the boot get? Do you get the countdown from the loader? I assume the loader worked but when it attempted to boot openindiana, X11 failed. In that case, the file /var/log/Xorg.0.log should tell you why it failed. You should be able to log in on the command line to see that file. What graphics adapter are you using? -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
In message <390850911.4192241.1607622852...@mail.yahoo.com>, Kalle Anka via ope nindiana-discuss writes: >Yes I tried to boot the usb stick both in UEFI and BIOS mode. Both fail. In wh >at way? I see some error messages in the dmesg output. I have pasted that long > dmesg output in a reply here with date: Wed Dec 9 20:47:35 UTC 2020, you can I would try installing using the text installer. http://dlc.openindiana.org/> Then I would # pkg update # pkg install mate_install John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
> Did you switch from UEFI to legacy BIOS boot mode?> In what way does it fail? Yes I tried to boot the usb stick both in UEFI and BIOS mode. Both fail. In what way? I see some error messages in the dmesg output. I have pasted that long dmesg output in a reply here with date: Wed Dec 9 20:47:35 UTC 2020, you can read that mail for more information. But it seems that X11 does not start. The screen flickers thrice and then exits to command line. On Wednesday, December 9, 2020, 01:40:51 AM GMT+1, John D Groenveld wrote: In message <964006845.3629689.1607454331...@mail.yahoo.com>, Kalle Anka via ope nindiana-discuss writes: > blogs, it seems that Bhyve does support GPU passthrough, but do not support U >SB passthrough, which means it is problematic to use keyboard and mouse in the Your existing mainboard might have multiple embedded USB controllers in which case you could dedicate one for your gamer VM. Or you could add an additional USB controller.` > VM. So I want to investigate this more, either OI + Bhyve, or OI + KVM, for G >PU passthrough and Windows gaming. Happy hacking, John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
On Thu, Dec 10, 2020 at 10:12 AM Kalle Anka via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > Thanx for your answer! Yes, my mobo might have several USB controllers. I > need to check it up. (I read all answers, but do not answer, because I do > not want to clutter up the mail lists with lot of "thank you" replys) > However, I can not boot OI usb on my PC. So I think I have to wait until > next OI release and see if that one works on my hardware instead of > 2020.10. I have to use Solaris 11.3 until then. So I now have two Solaris > 11.3 questions instead. > 1) I tried to copy files from my Windows NAS to my home directory but it > failed. It was a question of time out. Can it be something with write > permissions? I can write Solaris data to my NAS and copy it back to another > home directory. But i can not write original NAS data to my Solaris home > directory. Why? Anyone have a clue? > This seems to be a Solaris + Windows question, not an OI one ;) 2) I tried to install Solaris 11.3 packages, such as Firefox, but IPS > upgrade does not work. Why is that? Is the 11.3 IPS packages locked down, > in favour of 11.4? Anyone knows? > Also a Solaris question? > I will check the next OI release. I hope it will work with my hardware, > because I really want to migrate to OI! :) > On Wednesday, December 9, 2020, 01:40:51 AM GMT+1, John D Groenveld < > groenv...@acm.org> wrote: > > In message <964006845.3629689.1607454331...@mail.yahoo.com>, Kalle Anka > via ope > nindiana-discuss writes: > > blogs, it seems that Bhyve does support GPU passthrough, but do not > support U > >SB passthrough, which means it is problematic to use keyboard and mouse > in the > > Your existing mainboard might have multiple embedded USB controllers > in which case you could dedicate one for your gamer VM. > Or you could add an additional USB controller.` > > > VM. So I want to investigate this more, either OI + Bhyve, or OI + KVM, > for G > >PU passthrough and Windows gaming. > > Happy hacking, > John > groenv...@acm.org > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
In message <903650305.4158594.1607616713...@mail.yahoo.com>, Kalle Anka via ope nindiana-discuss writes: >However, I can not boot OI usb on my PC. So I think I have to wait until next Did you switch from UEFI to legacy BIOS boot mode? In what way does it fail? John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
Thanx for your answer! Yes, my mobo might have several USB controllers. I need to check it up. (I read all answers, but do not answer, because I do not want to clutter up the mail lists with lot of "thank you" replys) However, I can not boot OI usb on my PC. So I think I have to wait until next OI release and see if that one works on my hardware instead of 2020.10. I have to use Solaris 11.3 until then. So I now have two Solaris 11.3 questions instead. 1) I tried to copy files from my Windows NAS to my home directory but it failed. It was a question of time out. Can it be something with write permissions? I can write Solaris data to my NAS and copy it back to another home directory. But i can not write original NAS data to my Solaris home directory. Why? Anyone have a clue? 2) I tried to install Solaris 11.3 packages, such as Firefox, but IPS upgrade does not work. Why is that? Is the 11.3 IPS packages locked down, in favour of 11.4? Anyone knows? I will check the next OI release. I hope it will work with my hardware, because I really want to migrate to OI! :) On Wednesday, December 9, 2020, 01:40:51 AM GMT+1, John D Groenveld wrote: In message <964006845.3629689.1607454331...@mail.yahoo.com>, Kalle Anka via ope nindiana-discuss writes: > blogs, it seems that Bhyve does support GPU passthrough, but do not support U >SB passthrough, which means it is problematic to use keyboard and mouse in the Your existing mainboard might have multiple embedded USB controllers in which case you could dedicate one for your gamer VM. Or you could add an additional USB controller.` > VM. So I want to investigate this more, either OI + Bhyve, or OI + KVM, for G >PU passthrough and Windows gaming. Happy hacking, John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
Thanx for your suggestion, I will look into that! I like to write and have contributed to several texts on wikipedia. I like to write long posts in the Solaris forums which problem I faced and how I solved it. I might contribute to the manual for OI? That sounds fun. Maybe document how you can do GPU passthrough? Or install Sunray? But most probably I would need help for those things. I also have a Master in comp sci, so that might be helpful if I get more involved in the OI community. But this is a later question. Right now I can not boot into OI. I get lot of error messages. I have tried to boot again, this time using "ACPI" and "VESA" driver and using 1080p (earlier I booted into 1440p). This time I get these dmesg messages. Anyone have a clue what can be the problem? --- Wed Dec 9 20:33:01 GMT 2020 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] acpinex16 is /fw/sb@0/usbroothub@XHC_/port@17 Dec 9 20:31:20 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@9, acpinex17 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] acpinex17 is /fw/sb@0/usbroothub@XHC_/port@9 Dec 9 20:31:20 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@10, acpinex18 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] acpinex18 is /fw/sb@0/usbroothub@XHC_/port@10 Dec 9 20:31:20 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@11, acpinex19 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] acpinex19 is /fw/sb@0/usbroothub@XHC_/port@11 Dec 9 20:31:20 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@12, acpinex20 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] acpinex20 is /fw/sb@0/usbroothub@XHC_/port@12 Dec 9 20:31:20 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@13, acpinex21 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] acpinex21 is /fw/sb@0/usbroothub@XHC_/port@13 Dec 9 20:31:20 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@14, acpinex22 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] acpinex22 is /fw/sb@0/usbroothub@XHC_/port@14 Dec 9 20:31:20 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@15, acpinex23 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] acpinex23 is /fw/sb@0/usbroothub@XHC_/port@15 Dec 9 20:31:20 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@18, acpinex24 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] acpinex24 is /fw/sb@0/usbroothub@XHC_/port@18 Dec 9 20:31:20 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@19, acpinex25 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] acpinex25 is /fw/sb@0/usbroothub@XHC_/port@19 Dec 9 20:31:20 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@20, acpinex26 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] acpinex26 is /fw/sb@0/usbroothub@XHC_/port@20 Dec 9 20:31:20 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@21, acpinex27 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] acpinex27 is /fw/sb@0/usbroothub@XHC_/port@21 Dec 9 20:31:20 openindiana scsi: [ID 365881 kern.notice] /pci@0,0/pci8086,c09@1,2/pci1028,1f1c@0 (mpt_sas0): Dec 9 20:31:20 openindiana mptsas0 supports power management. Dec 9 20:31:20 openindiana scsi: [ID 365881 kern.notice] /pci@0,0/pci8086,c09@1,2/pci1028,1f1c@0 (mpt_sas0): Dec 9 20:31:20 openindiana mptsas0 supports power management. Dec 9 20:31:20 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: dtrace0 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] dtrace0 is /pseudo/dtrace@0 Dec 9 20:31:20 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: fasttrap0 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] fasttrap0 is /pseudo/fasttrap@0 Dec 9 20:31:20 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: fbt0 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] fbt0 is /pseudo/fbt@0 Dec 9 20:31:20 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: fcp0 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] fcp0 is /pseudo/fcp@0 Dec 9 20:31:20 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: fcsm0 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] fcsm0 is /pseudo/fcsm@0 Dec 9 20:31:20 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: fct0 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] fct0 is /pseudo/fct@0 Dec 9 20:31:20 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: llc10 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] llc10 is /pseudo/llc1@0 Dec 9 20:31:20 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: lockstat0 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] lockstat0 is /pseudo/lockstat@0 Dec 9 20:31:20 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: lofi0 Dec 9 20:31:20 openindiana genunix: [ID 936769 kern.notice] lofi0 is
Re: [OpenIndiana-discuss] OI new user questions - 2
In message <964006845.3629689.1607454331...@mail.yahoo.com>, Kalle Anka via ope nindiana-discuss writes: > blogs, it seems that Bhyve does support GPU passthrough, but do not support U >SB passthrough, which means it is problematic to use keyboard and mouse in the Your existing mainboard might have multiple embedded USB controllers in which case you could dedicate one for your gamer VM. Or you could add an additional USB controller.` > VM. So I want to investigate this more, either OI + Bhyve, or OI + KVM, for G >PU passthrough and Windows gaming. Happy hacking, John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
Thanx for the suggestion! Bhyve seems promising. As I understood it, it is basically a stripped down QEMU/KVM to only allow passthrough and not much else. It is therefore faster than KVM, and has less and cleaner code. I got the impression that Joyent will focus on Bhyve, and not KVM anymore? If one read other blogs, it seems that Bhyve does support GPU passthrough, but do not support USB passthrough, which means it is problematic to use keyboard and mouse in the VM. So I want to investigate this more, either OI + Bhyve, or OI + KVM, for GPU passthrough and Windows gaming. --- Proxmox is basically a bunch of perl scripts on a Debian distro with KVM for passthrough. This is basically what I am considering, but using OI and Bhyve instead of Linux, because Solaris is more stable. --- However, I now have some problems. I tried to boot the OI usb, but it did not succeed. I had a bunch of errors. I tried both UEFI and BIOS, and the errors were similar. I also saw 100s of lines on the screen looking like this. They are not included in dmesg, WARNING: audiohd#0: timeout when get response from codec: wid=4, verb=0x0f02, param=0x0002... WARNING: audiohd#0: timeout when get response from codec: wid=4, verb=0x0f00, param=0x0012 Below is the verbose dmesg output. Are there any other log files I could attach to help identify why OI does not boot on my hardware? I have a Geforce GTX1070Ti, which has no Nvidia drivers for UEFI Solaris, therefore I used VESA driver. I have a Supermicro X10SAT motherboard, and Xeon E3-1245v3 and ECC RAM. Tue Dec 8 19:23:44 GMT 2020 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] acpinex19 is /fw/sb@0/usbroothub@XHC_/port@11 Dec 8 19:21:48 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@12, acpinex20 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] acpinex20 is /fw/sb@0/usbroothub@XHC_/port@12 Dec 8 19:21:48 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@13, acpinex21 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] acpinex21 is /fw/sb@0/usbroothub@XHC_/port@13 Dec 8 19:21:48 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@14, acpinex22 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] acpinex22 is /fw/sb@0/usbroothub@XHC_/port@14 Dec 8 19:21:48 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@15, acpinex23 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] acpinex23 is /fw/sb@0/usbroothub@XHC_/port@15 Dec 8 19:21:48 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@18, acpinex24 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] acpinex24 is /fw/sb@0/usbroothub@XHC_/port@18 Dec 8 19:21:48 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@19, acpinex25 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] acpinex25 is /fw/sb@0/usbroothub@XHC_/port@19 Dec 8 19:21:48 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@20, acpinex26 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] acpinex26 is /fw/sb@0/usbroothub@XHC_/port@20 Dec 8 19:21:48 openindiana acpinex: [ID 328922 kern.notice] acpinex: port@21, acpinex27 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] acpinex27 is /fw/sb@0/usbroothub@XHC_/port@21 Dec 8 19:21:48 openindiana scsi: [ID 365881 kern.notice] /pci@0,0/pci8086,c09@1,2/pci1028,1f1c@0 (mpt_sas0): Dec 8 19:21:48 openindiana mptsas0 supports power management. Dec 8 19:21:48 openindiana scsi: [ID 365881 kern.notice] /pci@0,0/pci8086,c09@1,2/pci1028,1f1c@0 (mpt_sas0): Dec 8 19:21:48 openindiana mptsas0 supports power management. Dec 8 19:21:48 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: dtrace0 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] dtrace0 is /pseudo/dtrace@0 Dec 8 19:21:48 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: fasttrap0 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] fasttrap0 is /pseudo/fasttrap@0 Dec 8 19:21:48 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: fbt0 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] fbt0 is /pseudo/fbt@0 Dec 8 19:21:48 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: fcp0 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] fcp0 is /pseudo/fcp@0 Dec 8 19:21:48 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: fcsm0 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] fcsm0 is /pseudo/fcsm@0 Dec 8 19:21:48 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: fct0 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] fct0 is /pseudo/fct@0 Dec 8 19:21:48 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: llc10 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] llc10 is /pseudo/llc1@0 Dec 8 19:21:48 openindiana pseudo: [ID 129642 kern.notice] pseudo-device: lockstat0 Dec 8 19:21:48 openindiana genunix: [ID 936769 kern.notice] lockstat0 is
Re: [OpenIndiana-discuss] OI new user questions - 2
In message <436895180.3297382.1607349045...@mail.yahoo.com>, Kalle Anka via ope nindiana-discuss writes: >I install OI on bare metal. Then I use KVM and Qemu to install Win10 as a Virt >ual Machine, and I do passthrough of my Geforce GTX 1070 Ti. I have a Xeon E3- >1245v3 cpu which has integrated graphics, namely HD P4600. This way, OI gets t >he IGP running VESA driver - which is totally fine as I only work in OI. Win10 > VM will get the GeForce GTX 1070 Ti when I want to game. This setup might be >less problematic than Q3? >Is this setup possible? Are there limitations specific to OI that I should kno >w, for instance, maybe OI KVM does not allow passthrough of GPUs? I believe you can configure the nVidia graphics card as a passthru device and then pass it to your Windows VM running on bhyve. https://www.cyber-tec.org/2019/05/29/using-bhyve-pci-passthrough-on-omnios/> John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
On Mon, Dec 7, 2020 at 9:43 AM Judah Richardson wrote: > > > On Mon, Dec 7, 2020 at 7:51 AM Kalle Anka via openindiana-discuss < > openindiana-discuss@openindiana.org> wrote: > >> Thanx for all your help, guys. I have read all your answers, but need to >> check a few things up before finally migrating to OI. >> Question 1) I have messed up my email settings to this group. But as I >> understood it: when someone replies to my question, I will get an email and >> I just "reply to all", and my answer will show up in the OI mail list for >> everyone to see? Is this correctly understood? (I am not used to mail >> lists). >> > Yes, hitting Reply All works for me in Gmail. > > Question 2) Just to double check: Does OI support UEFI installations? In >> the manual it says OI only supports BIOS installations. > > You should believe the manual. And my own experience when I last tried it > this year. The *installer* supports (requires?) UEFI, but the actual OS > requires legacy boot. > > Can someone confirm? This might be useful to record, for futures questions >> from users. >> Question 3) It is still unclear to me if I could install OI as BIOS by >> removing all disks except one. After the OI installation, I remove all >> disks except one and install Win10 as UEFI. Then I insert all disks and >> choose via boot menu (F11) to boot Win10 UEFI, or OI BIOS. Has anyone >> tested this? If not, I totally understand! :) >> > Based on our discussion so far, at this point you're best off trying that > yourself if you want to find out if it works. > > Question 4) It seems that it is problematic to dual boot OI BIOS, and >> Win10 UEFI, even on different disks on the same PC. It should be avoided if >> possible. >> > Correct. > > Therefore I came up with an alternative solution instead. The main thing >> is, I want to use OI as a backend (because Solaris is more stable than any >> other OS I tried), and then use Win10 for gaming. Instead of dual bootingh >> as in Q3), maybe this setup is possible instead: >> I install OI on bare metal. Then I use KVM and Qemu to install Win10 as a >> Virtual Machine, and I do passthrough of my Geforce GTX 1070 Ti. I have a >> Xeon E3-1245v3 cpu which has integrated graphics, namely HD P4600. This >> way, OI gets the IGP running VESA driver - which is totally fine as I only >> work in OI. Win10 VM will get the GeForce GTX 1070 Ti when I want to game. >> This setup might be less problematic than Q3? >> > I don't know. As far as home virtualization is concerned, r/homelab is the > best place to ask that question IMO. > Forgot to add: you can also use Proxmox to run both Windows 10 and OI in separate VMs with GPU passthrough for Windows 10. I do believe that's possible, but I don't know exactly how to do it because I have no firsthand Proxmox experience. You can ask at r/homelab or r/Proxmox on Reddit. > > Is this setup possible? Are there limitations specific to OI that I should >> know, for instance, maybe OI KVM does not allow passthrough of GPUs? >> > See above. > > Question 5) @Peter Tribble, so you are saying that this will also fail?- >> Create a zpool in Solaris 11.3 (zpool version 28, ZFS version 5)- Import >> the zpool into OI 2020.10- Copy data to the zpool using zfs send recv- >> Import zpool into Solaris 11.3. Will this last step also fail? >> > You can try this in the OI live USB and see how it goes. > >> ___ >> openindiana-discuss mailing list >> openindiana-discuss@openindiana.org >> https://openindiana.org/mailman/listinfo/openindiana-discuss >> > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI new user questions - 2
On Mon, Dec 7, 2020 at 7:51 AM Kalle Anka via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > Thanx for all your help, guys. I have read all your answers, but need to > check a few things up before finally migrating to OI. > Question 1) I have messed up my email settings to this group. But as I > understood it: when someone replies to my question, I will get an email and > I just "reply to all", and my answer will show up in the OI mail list for > everyone to see? Is this correctly understood? (I am not used to mail > lists). > Yes, hitting Reply All works for me in Gmail. Question 2) Just to double check: Does OI support UEFI installations? In > the manual it says OI only supports BIOS installations. You should believe the manual. And my own experience when I last tried it this year. The *installer* supports (requires?) UEFI, but the actual OS requires legacy boot. Can someone confirm? This might be useful to record, for futures questions > from users. > Question 3) It is still unclear to me if I could install OI as BIOS by > removing all disks except one. After the OI installation, I remove all > disks except one and install Win10 as UEFI. Then I insert all disks and > choose via boot menu (F11) to boot Win10 UEFI, or OI BIOS. Has anyone > tested this? If not, I totally understand! :) > Based on our discussion so far, at this point you're best off trying that yourself if you want to find out if it works. Question 4) It seems that it is problematic to dual boot OI BIOS, and Win10 > UEFI, even on different disks on the same PC. It should be avoided if > possible. > Correct. Therefore I came up with an alternative solution instead. The main thing > is, I want to use OI as a backend (because Solaris is more stable than any > other OS I tried), and then use Win10 for gaming. Instead of dual bootingh > as in Q3), maybe this setup is possible instead: > I install OI on bare metal. Then I use KVM and Qemu to install Win10 as a > Virtual Machine, and I do passthrough of my Geforce GTX 1070 Ti. I have a > Xeon E3-1245v3 cpu which has integrated graphics, namely HD P4600. This > way, OI gets the IGP running VESA driver - which is totally fine as I only > work in OI. Win10 VM will get the GeForce GTX 1070 Ti when I want to game. > This setup might be less problematic than Q3? > I don't know. As far as home virtualization is concerned, r/homelab is the best place to ask that question IMO. Is this setup possible? Are there limitations specific to OI that I should > know, for instance, maybe OI KVM does not allow passthrough of GPUs? > See above. Question 5) @Peter Tribble, so you are saying that this will also fail?- > Create a zpool in Solaris 11.3 (zpool version 28, ZFS version 5)- Import > the zpool into OI 2020.10- Copy data to the zpool using zfs send recv- > Import zpool into Solaris 11.3. Will this last step also fail? > You can try this in the OI live USB and see how it goes. > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] OI new user questions - 2
Thanx for all your help, guys. I have read all your answers, but need to check a few things up before finally migrating to OI. Question 1) I have messed up my email settings to this group. But as I understood it: when someone replies to my question, I will get an email and I just "reply to all", and my answer will show up in the OI mail list for everyone to see? Is this correctly understood? (I am not used to mail lists). Question 2) Just to double check: Does OI support UEFI installations? In the manual it says OI only supports BIOS installations. Can someone confirm? This might be useful to record, for futures questions from users. Question 3) It is still unclear to me if I could install OI as BIOS by removing all disks except one. After the OI installation, I remove all disks except one and install Win10 as UEFI. Then I insert all disks and choose via boot menu (F11) to boot Win10 UEFI, or OI BIOS. Has anyone tested this? If not, I totally understand! :) Question 4) It seems that it is problematic to dual boot OI BIOS, and Win10 UEFI, even on different disks on the same PC. It should be avoided if possible. Therefore I came up with an alternative solution instead. The main thing is, I want to use OI as a backend (because Solaris is more stable than any other OS I tried), and then use Win10 for gaming. Instead of dual bootingh as in Q3), maybe this setup is possible instead: I install OI on bare metal. Then I use KVM and Qemu to install Win10 as a Virtual Machine, and I do passthrough of my Geforce GTX 1070 Ti. I have a Xeon E3-1245v3 cpu which has integrated graphics, namely HD P4600. This way, OI gets the IGP running VESA driver - which is totally fine as I only work in OI. Win10 VM will get the GeForce GTX 1070 Ti when I want to game. This setup might be less problematic than Q3? Is this setup possible? Are there limitations specific to OI that I should know, for instance, maybe OI KVM does not allow passthrough of GPUs? Question 5) @Peter Tribble, so you are saying that this will also fail?- Create a zpool in Solaris 11.3 (zpool version 28, ZFS version 5)- Import the zpool into OI 2020.10- Copy data to the zpool using zfs send recv- Import zpool into Solaris 11.3. Will this last step also fail? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
