The bazzite ASUS laptop images seems to support ASUS Republic Of Gamers model GL702VSK, for bazzite-asus-nvidia-stable-amd64.iso but I did notice some dmesg kernel errors, included in my second post here

I am wondering whether I should download either the bazzite-asus-nvidia-stable-amd64.iso or the bazzite-gnome-asus-nvidia-stable-amd64.iso for the ASUS Republic of Gamers laptop model GL702VSK. Is it included in the supported ASUS laptop image? I currently have the bazzite-nvidia-stable-amd64 installed on it, as seen in these screenshots. I was wondering if the bazzite ASUS laptop images support this laptop as one of the recognized ASUS hardware or if there is any reason to use the ASUS image instead of the NVIDIA legacy images. I am fairly certain that the NVIDIA open images do not work on this laptop, nor do the bazzzite Steam Deck beta NVIDIA images. I have a few ISO images on my USB drive, but I can add an ASUS image if it is better to use it for the laptop, provided it is recognized in bazzite ASUS laptop software.

for ASUSTeK COMPUTER INC. GL702VSK/GL702VSK? 'Republic Of Gamers

below is its windows 10 software page for this laptop, I think firmware bios was last updated in 2018. this laptop model does not support windows 11 because its intel i7 processor is not in the support windows 11 list, it does have the TPM 2.0 chip in this laptop. with rufus windows 11 can be installed but its slow compared to windows 10 on this laptop.

GL702VSK - Support

I asked copilot these questions tonight, I tried to see if it had any answers for me about if this laptop is supported.

what ASUS laptops are reconsized on the bazzite linux distro?

Bazzite Linux is designed to be compatible with a wide range of hardware, including many ASUS laptops. While there isn’t a specific list of ASUS models, Bazzite focuses on supporting most x86_64 PCs from the last decade. This means that if you have a relatively recent ASUS laptop, it should work well with Bazzite.

For the best experience, make sure your laptop meets the following minimum system requirements:

  • Architecture: x86_64
  • Firmware: UEFI (CSM Support should be disabled if available)
  • Processor (CPU): 2GHz quad-core processor or better
  • System Memory (RAM): 4GB
  • Graphics: A graphics card that can utilize Vulkan 1.3+
  • Storage: 64GB free on an internal solid-state drive
  • Network: Stable internet connection with no bandwidth caps

If you want to check specific hardware compatibility, you can visit the Bazzite Documentation for more detailed information.

Is there a particular ASUS model you’re curious about?

ASUS Republic of Gamers laptop model GL702VSK supported in their ASUS laptop images for the nvidia version?

The ASUS Republic of Gamers GL702VSK is a powerful gaming laptop that should work well with Bazzite Linux, especially with the NVIDIA version. This model features a GTX 1070 GPU, which is compatible with the NVIDIA drivers supported by Bazzite.

For the best experience, make sure to:

  • Disable Secure Boot in the BIOS settings.
  • Use the latest NVIDIA drivers available for Linux.
  • Ensure your system firmware is up to date.

You can find more information about the GL702VSK on the ASUS support page.

If you have any specific concerns or need further assistance, feel free to ask!

bazzite linux supports secure boot on, that’s not needed? the ASUS support page does not talk about linux, it only has windows 10 software on it.

You’re right! Bazzite Linux does support Secure Boot, but you need to enroll their key during or after installation. So, you don’t necessarily need to disable Secure Boot, but you will need to follow the instructions to enroll the key.

As for the ASUS support page, it’s true that it primarily focuses on Windows. However, many users have successfully run Linux on ASUS Republic of Gamers laptops, including the GL702VSK. While official support might be limited, the Linux community often provides solutions and workarounds for compatibility issues.

If you encounter any specific problems, feel free to ask, and I’ll do my best to help!

I was able to install thier desktop nvidia legacy bazzite image on the laptop, what I want to know is if the ASUS laptop downloads under bazzite support my model laptop or not.

Great to hear that you successfully installed the NVIDIA legacy Bazzite image on your ASUS GL702VSK! According to the Bazzite Documentation, Bazzite Linux is designed to support a wide range of hardware, including many ASUS laptops. While there isn’t a specific list of supported ASUS models, Bazzite focuses on compatibility with most x86_64 PCs from the last decade.

Given that your GL702VSK meets the general hardware requirements, it should be supported by Bazzite. If you encounter any specific issues, the Bazzite community and documentation can be valuable resources for troubleshooting and finding solutions.

If you have any other questions or need further assistance, feel free to ask!

Also asked copilot what the difference betwen bazzite asus image and bazzite desktop images were?

what software is included in the asus laptop images that not in the bazzite desktop images for the nvidia hardware? what’s the difference between the versions?

The ASUS laptop images and Bazzite desktop images for NVIDIA hardware have some differences in the software they include. Here’s a breakdown:

ASUS Laptop Images

ASUS laptop images typically come with a suite of software designed to enhance the user experience on Windows. Some of the common software included are:

  • ASUS Armoury Crate: A centralized software for managing system performance, lighting, and other settings.
  • MyASUS: A utility for system diagnostics, updates, and customer support.
  • ASUS WebStorage: Cloud storage service for backing up and syncing files.
  • ASUS ZenUI Support: A customer service app providing in-device assistance.
  • Various Drivers and Utilities: Specific to the hardware components of the laptop, such as audio, network, and graphics drivers2.

Bazzite Desktop Images for NVIDIA Hardware

Bazzite desktop images, on the other hand, are designed for a gaming-focused Linux experience. They include:

  • KDE Plasma or GNOME Desktop Environments: Users can choose between these two popular desktop environments.
  • Steam Gaming Mode: An option for a console-like gaming experience, particularly useful for HTPC setups.
  • Gaming Utilities: Pre-installed gaming packages and utilities like Steam, MangoHud, and OBS VkCapture.
  • NVIDIA Drivers: Support for NVIDIA graphics cards, ensuring optimal performance for gaming4.

Key Differences

  • Operating System: ASUS images are Windows-based, while Bazzite images are Linux-based.
  • Pre-installed Software: ASUS images include proprietary ASUS software and utilities, while Bazzite images focus on gaming utilities and open-source software.
  • User Interface: ASUS images use the Windows interface, while Bazzite offers KDE Plasma or GNOME, with an optional Steam Gaming Mode for a console-like experience.
  • System Updates: Bazzite images receive system and application updates automatically in the background, while ASUS images rely on Windows Update and ASUS utilities for updates4.

I hope this helps clarify the differences! If you have any more questions or need further assistance, feel free to ask.

I did notice some dmesg kernel errors, included in my second post here, in the bottom of the second post, included the text, and a hardwareinfo.txt file upload to a readable website since its too big to post here if that helps. one I think needs a patch is the one that says 38.984216] Unpatched return thunk in use. This should not happen!, not sure about the blutooth since it seems to work fine even with that error.

So, I was able to get it working with the ASUS install image, I don’t really see any difference that I can notice between it and the desktop version, maybe a few things in kernel that show in the startup kernel, right before wayland starts, not sure if that stuff worked or got errors, otherwise it does seem to run the same.

there is one thing, I think both have incommon, bluetooth reading supported features failed in both the asus image and the desktop image if I recall it has an error (-16) the blutooth hardware seems to work fine under linux even with that error I ran dmesg command to see some of them from the kernel bootup.

I executed the dmesg command and redirected its output to a hardwareinfo.txt The output is too extensive to post in this, so I have to a text file sharing page for you to review the hardware information of this laptop.

a few things that show up under laptop, not sure if they need fixing or not in a ujust update etc… if these need patches or something I think some of this would be in both asus laptop image and bazzites desktop image for this laptop.

  141.513271] asus 0003:0B05:1837.0002: Unmapped Asus vendor usagepage code 0xec
[  175.409260] asus 0003:0B05:1837.0002: Unmapped Asus vendor usagepage code 0xec
[  177.225271] asus 0003:0B05:1837.0002: Unmapped Asus vendor usagepage code 0xec
[  177.233251] asus 0003:0B05:1837.0002: Unmapped Asus vendor usagepage code 0xec
[  428.767747] evm: overlay not supported
[  432.089075] asus 0003:0B05:1837.0002: Unmapped Asus vendor usagepage code 0xec
[   38.984213] ------------[ cut here ]------------
[   38.984216] Unpatched return thunk in use. This should not happen!
[   38.984218] WARNING: CPU: 2 PID: 910 at arch/x86/kernel/cpu/bugs.c:3063 __warn_thunk+0x2a/0x40
[   38.984224] Modules linked in: wl(PO+) intel_uncore_frequency intel_uncore_frequency_common intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp coretemp snd_soc_avs snd_soc_hda_codec snd_hda_ext_core snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine iwlmvm mac80211 libarc4 binfmt_misc iwlwifi iTCO_wdt processor_thermal_device_pci_legacy kvm_intel intel_pmc_bxt snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic iTCO_vendor_support snd_hda_scodec_component snd_hda_intel snd_intel_dspcfg overlay kvm snd_intel_sdw_acpi intel_rapl_msr processor_thermal_device processor_thermal_wt_hint processor_thermal_rfim snd_hda_codec ee1004 processor_thermal_rapl mei_pxp intel_rapl_common snd_hda_core mei_hdcp processor_thermal_wt_req processor_thermal_power_floor cfg80211 processor_thermal_mbox snd_hwdep rapl asus_nb_wmi intel_soc_dts_iosf snd_seq uvcvideo snd_seq_device btusb asus_armoury btintel btbcm btrtl btmtk bluetooth firmware_attributes_class uvc intel_cstate snd_pcm snd_timer intel_uncore videobuf2_vmalloc
[   38.984271]  videobuf2_memops snd videobuf2_v4l2 soundcore videobuf2_common int3400_thermal intel_pch_thermal i2c_i801 acpi_thermal_rel pcspkr wmi_bmof mei_me int3403_thermal int340x_thermal_zone intel_wmi_thunderbolt i2c_smbus mei vfat fat idma64 r8169 acpi_pad asus_wireless intel_pmc_core realtek intel_vsec pmt_telemetry pmt_class joydev tcp_bbr sch_fq vhba(O) loop nfnetlink lz4 zram lz4hc_compress lz4_compress hid_asus crct10dif_pclmul crc32_pclmul asus_wmi crc32c_intel hid_multitouch polyval_clmulni polyval_generic ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 sparse_keymap platform_profile rfkill i2c_hid_acpi i2c_hid serio_raw mxm_wmi nvidia_uvm(PO) nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) amdgpu amdxcp drm_exec gpu_sched drm_suballoc_helper drm_ttm_helper i915 drm_buddy video wmi i2c_algo_bit drm_display_helper cec ttm vfio_pci vfio_pci_core vfio_iommu_type1 vfio iommufd v4l2loopback(O) videodev mc uhid kvmfr(O) gcadapter_oc(O) fuse i2c_dev
[   38.984327] Unloaded tainted modules: nvidia_peermem(PO):1
[   38.984331] CPU: 2 UID: 0 PID: 910 Comm: (udev-worker) Tainted: P           O       6.12.12-207.bazzite.fc41.x86_64 #1
[   38.984335] Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
[   38.984336] Hardware name: ASUSTeK COMPUTER INC. GL702VSK/GL702VSK, BIOS GL702VSK.311 04/19/2019
[   38.984338] RIP: 0010:__warn_thunk+0x2a/0x40
[   38.984341] Code: 66 0f 1f 00 0f 1f 44 00 00 80 3d f8 e5 b8 02 00 74 05 c3 cc cc cc cc 48 c7 c7 e0 80 e4 86 c6 05 e3 e5 b8 02 01 e8 06 b1 08 00 <0f> 0b c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00
[   38.984343] RSP: 0018:ffffb32d00e0bac0 EFLAGS: 00010286
[   38.984345] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027
[   38.984347] RDX: ffff9b0eb2b21908 RSI: 0000000000000001 RDI: ffff9b0eb2b21900
[   38.984348] RBP: ffffb32d00e0bb10 R08: 0000000000000000 R09: 0000000000000000
[   38.984349] R10: 746f6e20646c756f R11: 216e657070616820 R12: ffffffffc95d1bd8
[   38.984351] R13: ffffb32d00e0bb58 R14: 00007f95c11503bd R15: ffffb32d00e0bbe8
[   38.984352] FS:  00007f95c1203bc0(0000) GS:ffff9b0eb2b00000(0000) knlGS:0000000000000000
[   38.984354] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   38.984356] CR2: 00007f012fd93938 CR3: 00000001059a6005 CR4: 00000000003726f0
[   38.984358] Call Trace:
[   38.984359]  <TASK>
[   38.984361]  ? __warn_thunk+0x2a/0x40
[   38.984364]  ? __warn.cold+0x93/0xfa
[   38.984367]  ? __warn_thunk+0x2a/0x40
[   38.984371]  ? report_bug+0xff/0x140
[   38.984374]  ? handle_bug+0x58/0x90
[   38.984378]  ? exc_invalid_op+0x17/0x70
[   38.984380]  ? asm_exc_invalid_op+0x1a/0x20
[   38.984385]  ? __warn_thunk+0x2a/0x40
[   38.984387]  warn_thunk_thunk+0x1a/0x30
[   38.984391]  getvar+0x20/0x70 [wl]
[   38.984431]  ? orc_header+0x1554/0x1554 [wl]
[   38.984465]  wl_module_init+0x17/0xa0 [wl]
[   38.984499]  ? do_one_initcall+0x58/0x310
[   38.984504]  ? do_init_module+0x90/0x260
[   38.984507]  ? __do_sys_init_module+0x17a/0x1b0
[   38.984511]  ? do_syscall_64+0x82/0x160
[   38.984514]  ? __mod_memcg_lruvec_state+0xd8/0x1d0
[   38.984518]  ? __lruvec_stat_mod_folio+0x83/0xd0
[   38.984521]  ? set_ptes.isra.0+0x41/0x90
[   38.984524]  ? do_anonymous_page+0xfc/0x8d0
[   38.984526]  ? __pte_offset_map+0x1b/0x180
[   38.984529]  ? __handle_mm_fault+0xb28/0xf80
[   38.984532]  ? __count_memcg_events+0x77/0x130
[   38.984536]  ? count_memcg_events.constprop.0+0x1a/0x30
[   38.984538]  ? handle_mm_fault+0x21b/0x330
[   38.984541]  ? do_user_addr_fault+0x55a/0x7b0
[   38.984545]  ? exc_page_fault+0x7e/0x180
[   38.984547]  ? entry_SYSCALL_64_after_hwframe+0x76/0x7e
[   38.984552]  </TASK>
[   38.984553] ---[ end trace 0000000000000000 ]---

  34.878632] Bluetooth: Core ver 2.22
[   34.878668] NET: Registered PF_BLUETOOTH protocol family
[   34.878671] Bluetooth: HCI device and connection manager initialized
[   34.878678] Bluetooth: HCI socket layer initialized
[   34.878682] Bluetooth: L2CAP socket layer initialized
[   34.878689] Bluetooth: SCO socket layer initialized
[   34.975258] Using default CPU limits. Please report if these are not correct.
[   34.976811] usbcore: registered new interface driver btusb
[   34.979413] Bluetooth: hci0: Firmware revision 0.0 build 14 week 44 2021
[   34.982393] Bluetooth: hci0: Reading supported features failed (-16)
[   34.982408] Bluetooth: hci0: Error reading debug features
[   34.982423] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
[   35.043137] usb 1-4: Found UVC 1.00 device USB2.0 HD UVC WebCam (0bda:57fa)
[   35.048264] asus_wmi: Initialization: 0x1
[   35.048346] asus_wmi: BIOS WMI version: 9.0
[   35.048402] asus_wmi: SFUN value: 0x21
[   35.048409] asus-nb-wmi asus-nb-wmi: Detected ATK, not ASUSWMI, use DSTS
[   35.053618] usbcore: registered new interface driver uvcvideo
[   35.056327] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input15
[   35.059251] audit: type=1131 audit(1740612796.669:54): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.072748] asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -19
[   35.072960] asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -19
[   35.073139] asus_wmi: fan_curve_get_factory_default (0x00110032) failed: -19
[   35.076474] ACPI: battery: new extension: ASUS Battery Extension
[   35.086493] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 655360 ms ovfl timer
[   35.086498] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[   35.086500] RAPL PMU: hw unit of domain package 2^-14 Joules
[   35.086501] RAPL PMU: hw unit of domain dram 2^-14 Joules
[   35.133130] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   35.133508] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   35.133649] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   35.282619] r8169 0000:04:00.0 enp4s0: renamed from eth0
[   35.290369] audit: type=1130 audit(1740612796.900:55): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.444473] ee1004 8-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
[   35.445834] ee1004 8-0052: 512 byte EE1004-compliant SPD EEPROM, read-only
[   35.606505] intel_rapl_common: Found RAPL domain package
[   35.606517] intel_rapl_common: Found RAPL domain core
[   35.606523] intel_rapl_common: Found RAPL domain dram
[   35.862674] systemd-journald[830]: Received client request to flush runtime journal.
[   35.884976] systemd-journald[830]: Creating journal file /var/log/journal/050b86d4c91545bd805b2e188291c94b/system.journal on a btrfs file system, and copy-on-write is enabled. This is likely to slow down journal access substantially, please consider turning off the copy-on-write file attribute on the journal directory, using chattr +C.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.