Hello, I'm using a HP ZBook Fury 16 G10 Mobile Workstation PC with 13th Gen Intel Core i7-13700HX, however Sculpt OS won't boot on it. It gets stuck at the boot logo screen. I can boot it using the same USB on my Sony Vaio Intel Laptop - Intel Core i7 Q 740. Therefore the USB image is valid. I'm not sure what else to try as I have followed the guide for running Sculpt OS on hardware and I changed all the Bios settings I could. The only one I can't find access to is the Data Execution Protection option in the bios, it doesn't seem to exist as an option to enable or disable in my bios. But the rest of the options I was able to enable such as virtualisation VTX, VTD, Disabling secure boot etc. I can UEFI boot Windows and several Linux distributions on the computer with and without TPM or Secure boot enabled.
Any help is appreciated. Thanks.
Dear,
I have a similar issue on a Razer Blade 15. After looking at the specifications of your computer, I see thatit seems to have an identical configuration to mine: an Intel CPU with an integrated GPU and an additional Nvidia discreet GPU.
Your problem may be the same as mine. You might want to follow this issue [1] on GitHub. And try again later when a fix has been integrated.
[1] https://github.com/genodelabs/genode/issues/5207
Cheers,
Alice Domage
Hello Alice, thanks for the reply. I have followed the issue on github now. Upon reading the github issue, it appears you link to a commit that solves the problem? So is it simply a matter of waiting for it to be merged and included in the next release?
Cheers, Jack
Hello Jack,
I published a image with the fix from Alice (thank you very much!) at [0] which you may try. Alternatively, update your Sculpt installation directly via Sculpt's system update mechanism furl with alex-ab, image 2024-05-05).
Cheers,
Alex.
[0] https://depot.genode.org/alex-ab/images/sculpt_24_04_5207.img
On 05.05.24 12:25, Jack Curran wrote:
Hello Alice, thanks for the reply. I have followed the issue on github now. Upon reading the github issue, it appears you link to a commit that solves the problem? So is it simply a matter of waiting for it to be merged and included in the next release?
Cheers, Jack _______________________________________________ users mailing list -- users@lists.genode.org To unsubscribe send an email to users-leave@lists.genode.org Archived at https://lists.genode.org/mailman3/hyperkitty/list/users@lists.genode.org/mes...
Hello Alexander, thank you for the response! I am messaging you from the Falcon web browser running on Sculpt on the HP Fury Workstation Laptop now! It worked great after using your image. Thanks Alice for the fix! I've never encountered such a quick fix to an OS problem I've had before!
Now that I am using the laptop with Sculpt, the only issue that I've encountered so far is that the touchpad is not recognised/working, even when I enable it in hardware component options. I am able to use my USB mouse as an alternative optin for now. The laptop integrated keyboard and my external USB keyboard and mouse work fine, it's just the laptop integrated touchpad that doesn't work.
This is an issue I have encountered before when installing other operating systems from a fresh ISO image. The touchpad doesn't work until after I have installed the operating system and updated the system post installation in which it seems to download the new touchpad driver needed for my laptop, as it doesn't seem to be included in the base install image.
Cheers, Jack
I can see in the documentation for SculptOS that:
"Touchpad on Intel Gen11+ Touchpads on recent Intel laptops are integrated as I2C HID devices without legacy PS/2 emulation. To support such trackpads, a dedicated driver is needed. Even though Sculpt OS has no built-in trackpad driver, it offers an I2C HID driver as an option in the + menu. Of course, you will need to use a USB mouse to initially activate and configure this option.
The driver needs to know a few platform-specific values that must be manually configured at /config/launcher/trackpad. The configuration is annotated with known values for several laptop models. Adjust the configuration by using the values matching your hardware and restart the touchpad driver to let the new configuration take effect."
I can see in the config options that I can edit the touchpad XML file and it has framework laptop touchpad values already included. So I should be able to edit it and replace it with my laptop's driver values, however I just don't know how to find what values my laptop touchpad uses?
Do you have any guidance on how I would find the necessary values? I am not sure how I would find the GPIO values for my touchpad.
Thanks
Hello Jack,
have you tried out the config options already in the launcher/touchpad file?
On Tue, May 07, 2024 at 03:29:47 CEST, Jack Curran wrote:
Do you have any guidance on how I would find the necessary values? I am not sure how I would find the GPIO values for my touchpad.
I have some hints you may try to disover your Touchpad config attributes. As the following example config demonstrates the current drivers requires the I2C bus address and HID descriptor address/register, which are touchpad device specific and differ between ELAN and SYNAPTICS. Further, we have to identify the GPIO interrupt pin used by the device to gain the drivers attention on input events (as I2C alone is missing such a mechanism).
<config gpio_pin="3" bus_addr="44" hid_addr="32" info="Framework Gen12/Gen13"/>
Let's first hunt for the touchpad-device properties. Please start Linux on the ZBook and gain root privileges. Run "journalctl --dmesg" and search for a line like the following.
# journalctl --dmesg | grep -i touchpad input: PIXA3854:00 093A:0274 Touchpad as /devices/pci0000:00/0000:00:15.3/i2c_designware.2/i2c-3/i2c-PIXA3854:00/0018:093A:0274.0002/input/input7
The output is on Framework 13 and tells us its a PixArt 3854 device that uses the same bus_addr="44" and hid_addr="32" as SYNAPTICS. If your device seems not to match PIXA or SYNA in the output you may go for the ELAN attributes bus_addr="21" and hid_addr="1".
Now we have to look out for the GPIO pin with "grep intel-gpio /proc/interrupts" (or alternatively the device string, e.g., PIXA3854, as search term).
# grep PIXA3854 /proc/interrupts 164: ... intel-gpio 3 PIXA3854:00
The number between intel-gpio and the model identifier specifies gpio_pin="3". After these steps, you hopefully discovered the config attributes of your device.
As you may already anticipate the manual discovery of the touchpad configuration is just an intermediate annoyance with the experimental touchpad support. In the future, these information will be automatically read via ACPI functions.
Regards
I should also add, my Sony Vaio laptop has an Intel i7 CPU with integrated graphics and a dedicated Nvidia GPU, I believe the GT 430M(it's very old). I wonder why I had no issues booting Sculpt OS with that laptop even though it also has a dedicated gpu?
-
Alexander Boettcher -
alice.domage＠gapfruit.com -
Christian Helmuth -
genode＠axioms.info -
Jack .
-
Jack Curran