Re: [qubes-users] Re: [HCL] ThinkPad T430
Hi Sven, That's great info, thank you! Other than these issues mentioned above, your fhd mod worked smoothly? As in, no need to add change anything during the heads build process? I will certainly let you know how it went although, I will probably be back asking more stupid questions in the future before it's finished lol Thanks, Stacey On Sunday, September 12, 2021 at 11:46:21 PM UTC+1 sv...@svensemmler.org wrote: > Hi Will, > > I basically used whatever was the HEAD revision of the Heads project at > that time. That worked reasonably well, but a few issues remained: > > -> A weird seemingly random data corruption issue when restoring backups > [1], which I cannot reproduce any longer. I suspect either the VRAM change > (see below) or the switch to the 4.19 kernel (see below) or maybe a > combination of both fixed it. > > -> Distorted graphics (looked like random data in the video buffer) for > the first 1-2 seconds when booting. This went away after setting > 'gfx_uma_size=224M' in cmos.default and 'select USE_OPTION_TABLE' and > 'select STATIC_OPTION_TABLE' in Kconfig. I use an external 4K screen and > never checked if this is also an issue without it being connected. You > might not need to do this. > > -> Random freezes of the system ... this is clearly connected to the 5.4 > kernel and never happens when using the 4.19 kernel. As long as the 4.19 > kernel is supported I feel no pressure to do anything about it and hope > that when the day comes, the newer kernel at that time will not have this > issue anymore. There is some talk about this being connected to the i915 > driver. > > -> Some warnings about the CPU having issues when booting... that's a bug > in Coreboot you can simply ignore. If you however want to fix it, just > apply this fix [2] manually. > > Good luck and let us know how it went! > > /Sven > > [1] https://github.com/QubesOS/qubes-issues/issues/6227 > [2] https://review.coreboot.org/28443 > > -- > public key: https://www.svensemmler.org/2A632C537D744BC7.asc > fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7 > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/dcd8f6b3-c8f7-42ae-8816-253bc3b2d388n%40googlegroups.com.
Re: [qubes-users] Re: [HCL] ThinkPad T430
Oh I see, okay that's a key piece of info, thank you. I am not aversed to research but Heads is seeming enigmatic, do you have any suggestions for guides etc. any advice you could give me would be much appreciated. Will I have to add my FHD 1080p screen to the build? Thanks, Stacey On Saturday, September 11, 2021 at 3:58:31 PM UTC+1 Plexus wrote: > Coreboot comes as part of heads - so you just build heads and flash that > to the 4mb and 8mb chips inside. > > On Sat, 11 Sept 2021 at 14:23, Will Lewis wrote: > >> I have to compliment your taste in hardware, I’m building almost exactly >> the same machine as we speak except for the SSD, I'm using a 1TB 870 Pro. >> >> >> >> Although, I’m entirely new to coreboot and am trying to gather as much >> info as possible, I’m at the last stage before flashing but I am struggling >> to understand some of the config options. >> >> If at all possible, could I have a look at your config file Sven as our >> builds are almost identical. >> >> >> >> Also did you flash Coreboot with seabios and then internally flash heads? >> >> >> >> Thanks, >> >> Stacey >> >> >> On Saturday, June 12, 2021 at 10:48:01 PM UTC+1 sv...@svensemmler.org >> wrote: >> >>> On 6/10/21 3:12 PM, Sven Semmler wrote: >>> > The one I've used is the i7-3740QM which was recommended by @Plexus. >>> > It's a tiny bit less powerful than the i7-3840QM but about half the >>> > price (if you shop right and not just go for the first listing on >>> Amazon >>> > as I did). >>> >>> Actually at least in the US the price difference is basically >>> non-existent and I can't stand the fact that I *could* have a faster >>> CPU. So I ordered the i7-3840QM and will pop it in / resubmit the HCL >>> when it arrives. >>> >>> /Sven >>> >>> -- >>> public key: https://www.svensemmler.org/2A632C537D744BC7.asc >>> fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7 >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "qubes-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to qubes-users...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/qubes-users/672ae672-3d5f-421b-90dd-cdea3c1888b3n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/qubes-users/672ae672-3d5f-421b-90dd-cdea3c1888b3n%40googlegroups.com?utm_medium=email_source=footer> >> . >> > > > -- > Kind Regards, > > Simon Newton > > E: simon@gmail.com > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c5846fb4-4a4a-4064-a890-4245c279f576n%40googlegroups.com.
Re: [qubes-users] Re: [HCL] ThinkPad T430
I have to compliment your taste in hardware, I’m building almost exactly the same machine as we speak except for the SSD, I'm using a 1TB 870 Pro. Although, I’m entirely new to coreboot and am trying to gather as much info as possible, I’m at the last stage before flashing but I am struggling to understand some of the config options. If at all possible, could I have a look at your config file Sven as our builds are almost identical. Also did you flash Coreboot with seabios and then internally flash heads? Thanks, Stacey On Saturday, June 12, 2021 at 10:48:01 PM UTC+1 sv...@svensemmler.org wrote: > On 6/10/21 3:12 PM, Sven Semmler wrote: > > The one I've used is the i7-3740QM which was recommended by @Plexus. > > It's a tiny bit less powerful than the i7-3840QM but about half the > > price (if you shop right and not just go for the first listing on Amazon > > as I did). > > Actually at least in the US the price difference is basically > non-existent and I can't stand the fact that I *could* have a faster > CPU. So I ordered the i7-3840QM and will pop it in / resubmit the HCL > when it arrives. > > /Sven > > -- > public key: https://www.svensemmler.org/2A632C537D744BC7.asc > fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7 > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/672ae672-3d5f-421b-90dd-cdea3c1888b3n%40googlegroups.com.
[qubes-users] Asus Touchpad - Mouse pointer movement weirdness
Hi all. I posted this HCL, which should help us to answer this particular question as well; https://groups.google.com/forum/#!searchin/qubes-users/HCL$20-$20ASUSTeK_COMPUTER_INC_-GL553VD$2020190519%7Csort:date/qubes-users/QDLjiYT6pEI/COi35_WxAwAJ This machine came to me with Windows 10 on it, which had no issues with the touchpad, suggesting that whatever is going on isn't hardware related. On qubes, however, I've used xev to identify that the touchpad doesn't send pointer movement events (generally speaking), unless I also hold a finger over either the left or right touchpad mouse buttons. If I do place a finger on either button, no matter how light or hard I press, the pointer will move as I like. It will also operate as desired if I place a finger somewhere else on the touchpad, but less reliably than on the buttons. Tap to click (left and right), and multifinger scrolling work perfectly no matter what. Holding the left/right mouse buttons of my external usb device doesn't influence whether it works or not, so perhaps the button press isn't as important as having a larger surface area to complete an electrical circuit? I've also tried using the synaptics driver, but it actually seems less functional than the libinput default. The only exception to the rule is that, rarely, the pointer will catch a movement request and jump before immediately reverting to being nonresponsive. This doesn't seem entirely dependent on "sweet spots" as I originally though, but I still think there is some correlation between it deciding to work and where I try from on the touchpad. All help is appreciated, and if I can provide more information, please just let me know. Much thanks, Adam -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAD78PXj6FrKb14BXiUtWdH1hsnTazrMMh9jb%3DSbLWzaE3%2BPa9A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - ASUSTeK_COMPUTER_INC_-GL553VD 20190519
Key changes required to get working were to set the following boot arg for both the installer USB and the live system * efi=no-rs The installer USB also required the nouveau blacklist args: 1. nouveau.modeset=0 2. rd.driver.blacklist=nouveau 3. video=vesa:off The final iso to USB method used was the Fedora Media Writer with Qubes R4.0.1 iso onto an HP 32 GB usb. Many USBs and writing methods were used, but I can't say which would have worked if I'd gotten my boot args right initially. Altering boot args was difficult, since mounting the /dev/sdX2 partition didn't allow direct manipulation of the BOOTX64.cfg file. Upon advisement from #qubes on freenode irc, I copied the file, altered it, and then moved it back in place on the USB partition, which worked well. Post installation, Qubes configuration after initial boot had to be done with TABs, because the mouse did not appear to work properly. After configuration, I found that the touchpad behavior seemed to depend on using a very specific section (top right corner, it seems). USB mouse was a preferred alternative, but it may be true that the initial configuration could have been done with the touchpad mouse if I'd known about the sensitive areas. Without efi=no-rs, post install allowed LUKS decryption before going black and freezing. Thanks to all who helped me figure this out, and hopefully this is sufficient payback for the support I got :), Adam/ilsonno -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAD78PXg8nokmXP5YQOh-92U-mHqLMJkgrs_6LGwb7Ehh%2BDkqbQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-ASUSTeK_COMPUTER_INC_-GL553VD-20190519-175119.yml Description: application/yaml Qubes-HCL-ASUSTeK_COMPUTER_INC_-GL553VD-20190519-175119.cpio.gz Description: application/gzip
Re: [qubes-users] Qubes R4.0.1 Installer - The name org.freedesktop.UDisk2 was not provided by any .service files
Thanks for the response. Rereading my messages, it's clear that I was lacking some information about what my current state was, so I apologize for that. Issues were primarily occurring during installation from a live usb, before even getting the chance to select a storage device. I've done some screwing around and am working on submitting an HCL now. I did run into post installation issues, but those were due to a typo in my boot args, and correcting nouveau.modeset=0 (was nouveau.nomodeset=0) cleared that bit up for me. Thanks again. On Sat, May 18, 2019 at 7:51 PM awokd wrote: > Adam Lewis: > > Tried using YUMI per a similar Asus HCL report, but that was also > > unsuccessful. Using MBR rather than GPT/UEFI showed a little more info, > > though; > > "Problem description: failed to getinitiator name from iscsi firmware". > > This error can be traced to > > > https://github.com/QubesOS/qubes-installer-qubes-os/commit/3acd47647ee3284df548cc62d79a75e71efdd7e9#diff-dcea6ef93dbd70a795aab33230d481f5R55 > > > > On Fri, May 17, 2019 at 7:43 PM Adam Lewis wrote: > > > >> Manually transcribed errors, so typos are entirely possible. Attempting > to > >> install Qubes R4.0.1 on Asus ROG Strix GL753-RS71 Intel Core i7-7700HQ > >> Geforce GTX 1050 TI. > >> Attempted inst.text in boot args, blacklisting nouveau driver, and > >> commenting out noexitboot=1 and mapbs=1 lines with no changes apparent. > The > >> USB bypasses GRUB entirely and immediately launches anaconda installer, > >> with the following error shown in the Logs tab of anaconda. > > Just a guess, but if you're installing to an NVMe, try setting it to > SATA compatible mode if possible. Could also try installing to an actual > SATA drive of some type. > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAD78PXikxi_CbacToEwze3F4nGPDHYWeXe-SFKqCLgw1fbsD%2Bw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes R4.0.1 Installer - The name org.freedesktop.UDisk2 was not provided by any .service files
Tried using YUMI per a similar Asus HCL report, but that was also
unsuccessful. Using MBR rather than GPT/UEFI showed a little more info,
though;
"Problem description: failed to getinitiator name from iscsi firmware".
This error can be traced to
https://github.com/QubesOS/qubes-installer-qubes-os/commit/3acd47647ee3284df548cc62d79a75e71efdd7e9#diff-dcea6ef93dbd70a795aab33230d481f5R55
On Fri, May 17, 2019 at 7:43 PM Adam Lewis wrote:
> Manually transcribed errors, so typos are entirely possible. Attempting to
> install Qubes R4.0.1 on Asus ROG Strix GL753-RS71 Intel Core i7-7700HQ
> Geforce GTX 1050 TI.
> Attempted inst.text in boot args, blacklisting nouveau driver, and
> commenting out noexitboot=1 and mapbs=1 lines with no changes apparent. The
> USB bypasses GRUB entirely and immediately launches anaconda installer,
> with the following error shown in the Logs tab of anaconda.
>
> """"""""""""""""""""""""""""""""
> Traceback
> File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 147 in
> call_sync
> DEFAULT_DBUS_TIMEOUT, None
> GLib.GError: g-dbus-error-quark:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name
> org.freedesktop.UDisk2 was not provided by any .service files
> Traceback
> File "/usr/lib/python3.5/site-packages/blivet/iscsi.py" line 159 in
> __init__
> initiatorname =
> self._call_initiator_method("GetFirmwareInitiatorName")[0]
> File "/usr/lib/python3.5/site-packages/blivet/util.py" line 1105 in
> decorated
> if self.check_avail(onetime=just_onetime)
> File "/usr/lib/python3.5/site-packages/blivet/util.py" line 1093 in
> check_avail
> self._avail = self._check_avail()
> File "/usr/lib/python3.5/site-packages/blivet/iscsi.py" line 113 in
> _check_avail
> if not safe_dbus.check_object_available(STORAGED_SERVICE,
> STORAGED_MANAGER_PATH, MANAGER_IFACE)
> File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 194 in
> check_object_available
> intro_data = call_sync(service, obj_path, DBUS_INTRO_IFACE,
> "Introspect", None)
> File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 151 in
> call_sync
> raise DBusCallError(msg)
> blivet.safe_dbus.DBusCallError: Failed to call Introspect method on
> /org/freedesktop/UDisk2/Manager with None arguments:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name
> org.freedesktop.UDisk2 was not provided by any .service files
> """""""""""""""""""""""""""""""""""""
> https://pastebin.com/dAihmU2t
>
> *Attached txt, pastebin link, and above text are all identical.
>
> Much thanks, and please let me know if I can provide any additional
> information that would be useful,
>
> Adam
>
> PS Accidentally posted in qubes-devel initially. Sorry about that.
>
> --
> You received this message because you are subscribed to the Google Groups
> "qubes-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to qubes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to qubes-users@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/qubes-users/a63e5379-8e0b-4082-aa63-103e888aa97f%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/CAD78PXjrnGVk_ypaD2QfD7DWC0rKy7NE5a8HjS0iz_-S-Zypxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes R4.0.1 Installer - The name org.freedesktop.UDisk2 was not provided by any .service files
Manually transcribed errors, so typos are entirely possible. Attempting to
install Qubes R4.0.1 on Asus ROG Strix GL753-RS71 Intel Core i7-7700HQ
Geforce GTX 1050 TI.
Attempted inst.text in boot args, blacklisting nouveau driver, and commenting
out noexitboot=1 and mapbs=1 lines with no changes apparent. The USB bypasses
GRUB entirely and immediately launches anaconda installer, with the following
error shown in the Logs tab of anaconda.
Traceback
File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 147 in
call_sync
DEFAULT_DBUS_TIMEOUT, None
GLib.GError: g-dbus-error-quark:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name
org.freedesktop.UDisk2 was not provided by any .service files
Traceback
File "/usr/lib/python3.5/site-packages/blivet/iscsi.py" line 159 in __init__
initiatorname = self._call_initiator_method("GetFirmwareInitiatorName")[0]
File "/usr/lib/python3.5/site-packages/blivet/util.py" line 1105 in decorated
if self.check_avail(onetime=just_onetime)
File "/usr/lib/python3.5/site-packages/blivet/util.py" line 1093 in
check_avail
self._avail = self._check_avail()
File "/usr/lib/python3.5/site-packages/blivet/iscsi.py" line 113 in
_check_avail
if not safe_dbus.check_object_available(STORAGED_SERVICE,
STORAGED_MANAGER_PATH, MANAGER_IFACE)
File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 194 in
check_object_available
intro_data = call_sync(service, obj_path, DBUS_INTRO_IFACE, "Introspect",
None)
File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 151 in
call_sync
raise DBusCallError(msg)
blivet.safe_dbus.DBusCallError: Failed to call Introspect method on
/org/freedesktop/UDisk2/Manager with None arguments:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name
org.freedesktop.UDisk2 was not provided by any .service files
"
https://pastebin.com/dAihmU2t
*Attached txt, pastebin link, and above text are all identical.
Much thanks, and please let me know if I can provide any additional information
that would be useful,
Adam
PS Accidentally posted in qubes-devel initially. Sorry about that.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/a63e5379-8e0b-4082-aa63-103e888aa97f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Traceback
File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 147 in
call_sync
DEFAULT_DBUS_TIMEOUT, None
GLib.GError: g-dbus-error-quark:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name
org.freedesktop.UDisk2 was not provided by any .service files
Traceback
File "/usr/lib/python3.5/site-packages/blivet/iscsi.py" line 159 in __init__
initiatorname = self._call_initiator_method("GetFirmwareInitiatorName")[0]
File "/usr/lib/python3.5/site-packages/blivet/util.py" line 1105 in decorated
if self.check_avail(onetime=just_onetime)
File "/usr/lib/python3.5/site-packages/blivet/util.py" line 1093 in
check_avail
self._avail = self._check_avail()
File "/usr/lib/python3.5/site-packages/blivet/iscsi.py" line 113 in
_check_avail
if not safe_dbus.check_object_available(STORAGED_SERVICE,
STORAGED_MANAGER_PATH, MANAGER_IFACE)
File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 194 in
check_object_available
intro_data = call_sync(service, obj_path, DBUS_INTRO_IFACE, "Introspect",
None)
File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 151 in
call_sync
raise DBusCallError(msg)
blivet.safe_dbus.DBusCallError: Failed to call Introspect method on
/org/freedesktop/UDisk2/Manager with None arguments:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name
org.freedesktop.UDisk2 was not provided by any .service files
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
On Friday, January 18, 2019 at 10:31:33 AM UTC-5, Mike Keehan wrote: > On Fri, 18 Jan 2019 07:17:00 -0800 (PST) > scott wrote: > > > On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote: > > > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote: > > > > Thanks but unfortunately I don't know that issue helps, as those > > > > who were able to resolve it did so by updating which I cannot do > > > > since sys-net fails to start. > > > > > > > > This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , > > > > seems to cover that problem but nothing's mentioned about net & > > > > firewall failing to start. > > > > > > > > > > > > On Fri, Jan 18, 2019, 07:22 Mike Keehan > > > > > > > > On Thu, 17 Jan 2019 16:42:28 -0800 (PST) > > > > > scott wrote: > > > > > > > > > > > Hello, I apologize in advance if this has already been > > > > > > addressed but searching for "sys-net" & "libxl" give many > > > > > > confusing results, I don't see any that match both not > > > > > > working, and I'm completely new to Qubes. My problem is that > > > > > > after 2 different installs of the same version, 4.01, I keep > > > > > > getting the same problems: When I get into Qubes I cannot > > > > > > update dom0, and sys-net & sys-firewall both fail to start > > > > > > even though my NIC is correctly listed in devices for -net. > > > > > > > > > > > > Basic info: > > > > > > Dell Optiplex 780, bios= A15 as recommended in HCL. > > > > > > Qubes 4.01, sigs checked good. > > > > > > Install 1 done by USB, created in windows, had same issues as > > > > > > described below. Re-installed by DVD thinking I'd muffed > > > > > > something (think I read on reddit that USB installs made from > > > > > > windows had issues) and the behavior is exactly the same. > > > > > > > > > > > > Behavior observed: > > > > > > (anything in [xxx] is me telling you the variation, as I get > > > > > > this for 2 VM's, 2 error codes, etc.) > > > > > > * Dom0 starts and runs, but -net & -firewall will not. > > > > > > * When I attempt to manually start either, I get this error > > > > > > message: "ERROR: Start failed: internal error: libxenlight > > > > > > failed to create new domain 'sys-net' [or sys-firewall], > > > > > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > > > > > > > > > When I less the log, I get these errors dozens of time with > > > > > > timestamps ranging from date of install to today: 1: > > > > > > "[date:time]: libxl: > > > > > > libxl_create.c:610:libxl_domain_make:domain creation fail: > > > > > > Operation not supported" 2: "[date:time]: libxl: > > > > > > libxl_create.c:982:initiate_domain_create:cannot make domain: > > > > > > -3" Those errors and nothing else. > > > > > > > > > > > > I've tried to update dom0 by command as found in docs, as > > > > > > well as through GUI without success. I found a page elsewhere > > > > > > that described temporarily putting NIC in firewall or another > > > > > > VM to see if it worked, but I must be doing it wrong as I > > > > > > always get loopback errors when trying to save. It always > > > > > > tells me failed, regardless. No wonder if network isn't > > > > > > working. > > > > > > > > > > > > Under sys-net, I see the correct name and model of my NIC, > > > > > > but I can't seem to figure out how to see if the NIC is > > > > > > operational since sys-net isn't working (new to qubes > > > > > > sorry!), however I verified my router is not showing an IP > > > > > > assigned, though link LED is on. > > > > > > > > > > > > If anyone can help me try to figure this out, I'd really > > > > > > appreciate it. I'm still a bit green on linux but I learn > > > > > > fast, I recently gave up on Windows (I hate 10 so much I > > > > > > could scream) so I'm trying to dive in with qubes (deep end > > > > > > of the pool I think) as it best suits my needs with the VM > > > > > > implementation. > > > > > > > > > > > > I'd post the log itself, but I can't seem to figure out how > > > > > > to make USB copy work yet since I've been beating my head on > > > > > > the networking issue. > > > > > > > > > > > > Thanks, and sorry in advance if this duplicated another > > > > > > thread. > > > > > > > > > > Similar issues in the past were raised in this bug report - > > > > > > > > > > https://github.com/QubesOS/qubes-issues/issues/3125 > > > > > > > > > > It might give you some pointers. > > > > > > > > > > (I found it by searching for "Qubes libxl_domain_make:domain > > > > > creation fail: Operation not supported" in google.) > > > > > > > > > > Mike. > > > > > > > > > > > Test whether issue is with NIC by removing the card from sys-net > > > and confirming that sys-firewall starts (after sys-net). > > > Shutdown both. > > > Re-attach NIC to sys-net. > > > Report back. > > > > > > > > > You can extract logs from dom0 by creating a qube with NO netvm, and > > > using qvm-copy-to-vm to transfer the log to that qube. Attach USB > > > device to the
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
On Friday, January 18, 2019 at 10:17:01 AM UTC-5, scott.lewi...@gmail.com wrote: > On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote: > > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote: > > > Thanks but unfortunately I don't know that issue helps, as those who were > > > able to resolve it did so by updating which I cannot do since sys-net > > > fails > > > to start. > > > > > > This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , seems to > > > cover that problem but nothing's mentioned about net & firewall failing to > > > start. > > > > > > > > > On Fri, Jan 18, 2019, 07:22 Mike Keehan > > > > > > On Thu, 17 Jan 2019 16:42:28 -0800 (PST) > > > > scott wrote: > > > > > > > > > Hello, I apologize in advance if this has already been addressed but > > > > > searching for "sys-net" & "libxl" give many confusing results, I > > > > > don't see any that match both not working, and I'm completely new to > > > > > Qubes. My problem is that after 2 different installs of the same > > > > > version, 4.01, I keep getting the same problems: When I get into > > > > > Qubes I cannot update dom0, and sys-net & sys-firewall both fail to > > > > > start even though my NIC is correctly listed in devices for -net. > > > > > > > > > > Basic info: > > > > > Dell Optiplex 780, bios= A15 as recommended in HCL. > > > > > Qubes 4.01, sigs checked good. > > > > > Install 1 done by USB, created in windows, had same issues as > > > > > described below. Re-installed by DVD thinking I'd muffed something > > > > > (think I read on reddit that USB installs made from windows had > > > > > issues) and the behavior is exactly the same. > > > > > > > > > > Behavior observed: > > > > > (anything in [xxx] is me telling you the variation, as I get this for > > > > > 2 VM's, 2 error codes, etc.) > > > > > * Dom0 starts and runs, but -net & -firewall will not. > > > > > * When I attempt to manually start either, I get this error message: > > > > > "ERROR: Start failed: internal error: libxenlight failed to create > > > > > new domain 'sys-net' [or sys-firewall], > > > > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > > > > > > > When I less the log, I get these errors dozens of time with > > > > > timestamps ranging from date of install to today: 1: "[date:time]: > > > > > libxl: libxl_create.c:610:libxl_domain_make:domain creation fail: > > > > > Operation not supported" 2: "[date:time]: libxl: > > > > > libxl_create.c:982:initiate_domain_create:cannot make domain: -3" > > > > > Those errors and nothing else. > > > > > > > > > > I've tried to update dom0 by command as found in docs, as well as > > > > > through GUI without success. I found a page elsewhere that described > > > > > temporarily putting NIC in firewall or another VM to see if it > > > > > worked, but I must be doing it wrong as I always get loopback errors > > > > > when trying to save. It always tells me failed, regardless. No wonder > > > > > if network isn't working. > > > > > > > > > > Under sys-net, I see the correct name and model of my NIC, but I > > > > > can't seem to figure out how to see if the NIC is operational since > > > > > sys-net isn't working (new to qubes sorry!), however I verified my > > > > > router is not showing an IP assigned, though link LED is on. > > > > > > > > > > If anyone can help me try to figure this out, I'd really appreciate > > > > > it. I'm still a bit green on linux but I learn fast, I recently gave > > > > > up on Windows (I hate 10 so much I could scream) so I'm trying to > > > > > dive in with qubes (deep end of the pool I think) as it best suits my > > > > > needs with the VM implementation. > > > > > > > > > > I'd post the log itself, but I can't seem to figure out how to make > > > > > USB copy work yet since I've been beating my head on the networking > > > > > issue. > > > > > > > > > > Thanks, and sorry in advance if this duplicated another thread. > > > > > > > > > > > > > Similar issues in the past were raised in this bug report - > > > > > > > > https://github.com/QubesOS/qubes-issues/issues/3125 > > > > > > > > It might give you some pointers. > > > > > > > > (I found it by searching for "Qubes libxl_domain_make:domain creation > > > > fail: Operation not supported" in google.) > > > > > > > > Mike. > > > > > > > > Test whether issue is with NIC by removing the card from sys-net and > > confirming that > > sys-firewall starts (after sys-net). > > Shutdown both. > > Re-attach NIC to sys-net. > > Report back. > > > > > > You can extract logs from dom0 by creating a qube with NO netvm, and > > using qvm-copy-to-vm to transfer the log to that qube. Attach USB > > device to the qube (using devices widget) and copy log off system. > > Thanks Mike, here's the results: > * Trying to start the USB VM results in error: ERROR: Start failed: internal > error: libxenlight failed to create new domain 'USBlogs', see > /var/log/libvirt/libxl/libxl-driver.log for details (at least
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote: > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote: > > Thanks but unfortunately I don't know that issue helps, as those who were > > able to resolve it did so by updating which I cannot do since sys-net fails > > to start. > > > > This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , seems to > > cover that problem but nothing's mentioned about net & firewall failing to > > start. > > > > > > On Fri, Jan 18, 2019, 07:22 Mike Keehan > > > > On Thu, 17 Jan 2019 16:42:28 -0800 (PST) > > > scott wrote: > > > > > > > Hello, I apologize in advance if this has already been addressed but > > > > searching for "sys-net" & "libxl" give many confusing results, I > > > > don't see any that match both not working, and I'm completely new to > > > > Qubes. My problem is that after 2 different installs of the same > > > > version, 4.01, I keep getting the same problems: When I get into > > > > Qubes I cannot update dom0, and sys-net & sys-firewall both fail to > > > > start even though my NIC is correctly listed in devices for -net. > > > > > > > > Basic info: > > > > Dell Optiplex 780, bios= A15 as recommended in HCL. > > > > Qubes 4.01, sigs checked good. > > > > Install 1 done by USB, created in windows, had same issues as > > > > described below. Re-installed by DVD thinking I'd muffed something > > > > (think I read on reddit that USB installs made from windows had > > > > issues) and the behavior is exactly the same. > > > > > > > > Behavior observed: > > > > (anything in [xxx] is me telling you the variation, as I get this for > > > > 2 VM's, 2 error codes, etc.) > > > > * Dom0 starts and runs, but -net & -firewall will not. > > > > * When I attempt to manually start either, I get this error message: > > > > "ERROR: Start failed: internal error: libxenlight failed to create > > > > new domain 'sys-net' [or sys-firewall], > > > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > > > > > When I less the log, I get these errors dozens of time with > > > > timestamps ranging from date of install to today: 1: "[date:time]: > > > > libxl: libxl_create.c:610:libxl_domain_make:domain creation fail: > > > > Operation not supported" 2: "[date:time]: libxl: > > > > libxl_create.c:982:initiate_domain_create:cannot make domain: -3" > > > > Those errors and nothing else. > > > > > > > > I've tried to update dom0 by command as found in docs, as well as > > > > through GUI without success. I found a page elsewhere that described > > > > temporarily putting NIC in firewall or another VM to see if it > > > > worked, but I must be doing it wrong as I always get loopback errors > > > > when trying to save. It always tells me failed, regardless. No wonder > > > > if network isn't working. > > > > > > > > Under sys-net, I see the correct name and model of my NIC, but I > > > > can't seem to figure out how to see if the NIC is operational since > > > > sys-net isn't working (new to qubes sorry!), however I verified my > > > > router is not showing an IP assigned, though link LED is on. > > > > > > > > If anyone can help me try to figure this out, I'd really appreciate > > > > it. I'm still a bit green on linux but I learn fast, I recently gave > > > > up on Windows (I hate 10 so much I could scream) so I'm trying to > > > > dive in with qubes (deep end of the pool I think) as it best suits my > > > > needs with the VM implementation. > > > > > > > > I'd post the log itself, but I can't seem to figure out how to make > > > > USB copy work yet since I've been beating my head on the networking > > > > issue. > > > > > > > > Thanks, and sorry in advance if this duplicated another thread. > > > > > > > > > > Similar issues in the past were raised in this bug report - > > > > > > https://github.com/QubesOS/qubes-issues/issues/3125 > > > > > > It might give you some pointers. > > > > > > (I found it by searching for "Qubes libxl_domain_make:domain creation > > > fail: Operation not supported" in google.) > > > > > > Mike. > > > > > Test whether issue is with NIC by removing the card from sys-net and > confirming that > sys-firewall starts (after sys-net). > Shutdown both. > Re-attach NIC to sys-net. > Report back. > > > You can extract logs from dom0 by creating a qube with NO netvm, and > using qvm-copy-to-vm to transfer the log to that qube. Attach USB > device to the qube (using devices widget) and copy log off system. Thanks Mike, here's the results: * Trying to start the USB VM results in error: ERROR: Start failed: internal error: libxenlight failed to create new domain 'USBlogs', see /var/log/libvirt/libxl/libxl-driver.log for details (at least I know why I couldn't get it to work the 1 time I tried before OP). * Trying to start -net resulted in the same error, with the NIC removed. * Trying to start -firewall resulted in the error saying -net couldn't start, pointing to libxenlight's log also. Other things I observed again
Re: [qubes-users] sys-net & sys-firewall fail to start, new install
Thanks but unfortunately I don't know that issue helps, as those who were able to resolve it did so by updating which I cannot do since sys-net fails to start. This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , seems to cover that problem but nothing's mentioned about net & firewall failing to start. On Fri, Jan 18, 2019, 07:22 Mike Keehan On Thu, 17 Jan 2019 16:42:28 -0800 (PST) > scott.lewis.engin...@gmail.com wrote: > > > Hello, I apologize in advance if this has already been addressed but > > searching for "sys-net" & "libxl" give many confusing results, I > > don't see any that match both not working, and I'm completely new to > > Qubes. My problem is that after 2 different installs of the same > > version, 4.01, I keep getting the same problems: When I get into > > Qubes I cannot update dom0, and sys-net & sys-firewall both fail to > > start even though my NIC is correctly listed in devices for -net. > > > > Basic info: > > Dell Optiplex 780, bios= A15 as recommended in HCL. > > Qubes 4.01, sigs checked good. > > Install 1 done by USB, created in windows, had same issues as > > described below. Re-installed by DVD thinking I'd muffed something > > (think I read on reddit that USB installs made from windows had > > issues) and the behavior is exactly the same. > > > > Behavior observed: > > (anything in [xxx] is me telling you the variation, as I get this for > > 2 VM's, 2 error codes, etc.) > > * Dom0 starts and runs, but -net & -firewall will not. > > * When I attempt to manually start either, I get this error message: > > "ERROR: Start failed: internal error: libxenlight failed to create > > new domain 'sys-net' [or sys-firewall], > > see /var/log/libvirt/libxl/libxl-driver.log for details". > > > > When I less the log, I get these errors dozens of time with > > timestamps ranging from date of install to today: 1: "[date:time]: > > libxl: libxl_create.c:610:libxl_domain_make:domain creation fail: > > Operation not supported" 2: "[date:time]: libxl: > > libxl_create.c:982:initiate_domain_create:cannot make domain: -3" > > Those errors and nothing else. > > > > I've tried to update dom0 by command as found in docs, as well as > > through GUI without success. I found a page elsewhere that described > > temporarily putting NIC in firewall or another VM to see if it > > worked, but I must be doing it wrong as I always get loopback errors > > when trying to save. It always tells me failed, regardless. No wonder > > if network isn't working. > > > > Under sys-net, I see the correct name and model of my NIC, but I > > can't seem to figure out how to see if the NIC is operational since > > sys-net isn't working (new to qubes sorry!), however I verified my > > router is not showing an IP assigned, though link LED is on. > > > > If anyone can help me try to figure this out, I'd really appreciate > > it. I'm still a bit green on linux but I learn fast, I recently gave > > up on Windows (I hate 10 so much I could scream) so I'm trying to > > dive in with qubes (deep end of the pool I think) as it best suits my > > needs with the VM implementation. > > > > I'd post the log itself, but I can't seem to figure out how to make > > USB copy work yet since I've been beating my head on the networking > > issue. > > > > Thanks, and sorry in advance if this duplicated another thread. > > > > Similar issues in the past were raised in this bug report - > > https://github.com/QubesOS/qubes-issues/issues/3125 > > It might give you some pointers. > > (I found it by searching for "Qubes libxl_domain_make:domain creation > fail: Operation not supported" in google.) > > Mike. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "qubes-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/qubes-users/mGvt8QW2mBQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > qubes-users+unsubscr...@googlegroups.com. > To post to this group, send email to qubes-users@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/20190118122156.4973a340.mike%40keehan.net > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CA%2B4dudfOdZL6RMom8P3JRTz76xakMiexidUmHFWE0k_HoD8F9w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] sys-net & sys-firewall fail to start, new install
Hello, I apologize in advance if this has already been addressed but searching for "sys-net" & "libxl" give many confusing results, I don't see any that match both not working, and I'm completely new to Qubes. My problem is that after 2 different installs of the same version, 4.01, I keep getting the same problems: When I get into Qubes I cannot update dom0, and sys-net & sys-firewall both fail to start even though my NIC is correctly listed in devices for -net. Basic info: Dell Optiplex 780, bios= A15 as recommended in HCL. Qubes 4.01, sigs checked good. Install 1 done by USB, created in windows, had same issues as described below. Re-installed by DVD thinking I'd muffed something (think I read on reddit that USB installs made from windows had issues) and the behavior is exactly the same. Behavior observed: (anything in [xxx] is me telling you the variation, as I get this for 2 VM's, 2 error codes, etc.) * Dom0 starts and runs, but -net & -firewall will not. * When I attempt to manually start either, I get this error message: "ERROR: Start failed: internal error: libxenlight failed to create new domain 'sys-net' [or sys-firewall], see /var/log/libvirt/libxl/libxl-driver.log for details". When I less the log, I get these errors dozens of time with timestamps ranging from date of install to today: 1: "[date:time]: libxl: libxl_create.c:610:libxl_domain_make:domain creation fail: Operation not supported" 2: "[date:time]: libxl: libxl_create.c:982:initiate_domain_create:cannot make domain: -3" Those errors and nothing else. I've tried to update dom0 by command as found in docs, as well as through GUI without success. I found a page elsewhere that described temporarily putting NIC in firewall or another VM to see if it worked, but I must be doing it wrong as I always get loopback errors when trying to save. It always tells me failed, regardless. No wonder if network isn't working. Under sys-net, I see the correct name and model of my NIC, but I can't seem to figure out how to see if the NIC is operational since sys-net isn't working (new to qubes sorry!), however I verified my router is not showing an IP assigned, though link LED is on. If anyone can help me try to figure this out, I'd really appreciate it. I'm still a bit green on linux but I learn fast, I recently gave up on Windows (I hate 10 so much I could scream) so I'm trying to dive in with qubes (deep end of the pool I think) as it best suits my needs with the VM implementation. I'd post the log itself, but I can't seem to figure out how to make USB copy work yet since I've been beating my head on the networking issue. Thanks, and sorry in advance if this duplicated another thread. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/824bf0e0-d47b-47ff-8f01-cf9dd92febd5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Y480
Here's the basics, everything seemed to work correctly out of the box, although there was an initial hiccup when installing from USB stick, I suspect it had to do with missing hardware support. I had to turn on bios features for virtualization, but otherwise it worked correctly. The only other issue on installation I wasn't asked for timezone, so it now assumes I am in UTC-0 and I don't see a way to change that for all (or any) of my VM's. Some applications like Blender use the Intel GL stack correctly, but other apps want the internal NVIDIA gpu, which so far I haven't had working. I've run a variety of linux kernels but haven't tried the Windows instance yet. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAD9ijYP_bP-dB4Bh%2BRC67MOxxt70bqso2qf2Vg8r1KizPCdD5g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-LENOVO-2093-20170309-015510.yml Description: application/yaml
