Hey John,
On 1/16/19 8:20 PM, John Goold wrote:
> I want to say thank you to those members of Qubes Users who have had the
> patience to answer my questions and solve my problems getting Qubes up and
> running. I have been particularly pleased that this is a forum where there
> are few, if
> Having just installed Qubes 4.0.1 I am not able to get my 10Gb Intel X540-AT2
> network card to work. It worked out of the box in Qubes 3.2.
>
> This is what I get in the net-vm:
>
> $ sudo dmesg |grep ixgbe
> [2.737931] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver -
> version
The following problem happened only on Qubes R3.2.1
Following the steps on
https://www.qubes-os.org/doc/macbook-troubleshooting/#7-fix-system-freezes-due-to-broadcom-bcm43602
sudo su -
xl pci-assignable-list
echo 03:00.0 > /sys/bus/pci/drivers/pciback/permissive
qvm-start sys-net
xl pci-attach
Qubes OS version:
Qubes 3.2.1
Affected component(s):
Qubes R3.2.1 System Network manager
Steps to reproduce the behavior:
Following the steps on https://www.qubes-os.org/doc/macbook-troubleshooting/#7-fix-system-freezes-due-to-broadcom-bcm43602;>this
sudo su -
xl pci-assignable-list
echo
### Qubes OS version:
Qubes 3.2.1
### Affected component(s):
Qubes R3.2.1 System Network manager
### Steps to reproduce the behavior:
Following the steps on
[this](https://www.qubes-os.org/doc/macbook-troubleshooting/#7-fix-system-freezes-due-to-broadcom-bcm43602)
```
sudo su -
xl
On Wed, Jan 16, 2019 at 01:19:54PM -0800, John Goold wrote:
> I encountered an "interesting" phenomenon which could be a defect (bug) or
> expected behaviour (an odd "feature"). If a defect, it could be in the file
> manager under Debian (Nautilus?).
>
> If I attempt to rename a file in
I encountered an "interesting" phenomenon which could be a defect (bug) or
expected behaviour (an odd "feature"). If a defect, it could be in the file
manager under Debian (Nautilus?).
If I attempt to rename a file in ~/local/share/applications/ when I save the
change, ".desktop" is appended
I want to say thank you to those members of Qubes Users who have had the
patience to answer my questions and solve my problems getting Qubes up and
running. I have been particularly pleased that this is a forum where there are
few, if any, unhelpful responses to questions and few
On Wednesday, January 16, 2019 at 1:14:45 AM UTC-6, Ivan Mitev wrote:
> On 1/15/19 11:04 PM, John Goold wrote:
> > On Tuesday, January 15, 2019 at 9:08:48 AM UTC-6, Ivan Mitev wrote:
> >> On 1/15/19 2:42 PM, unman wrote:
> >>> On Tue, Jan 15, 2019 at 09:26:31AM +0200, Ivan Mitev wrote:
>
>
Hey, I am having an Issue putting a qubes 4.0.1-x86_64.iso image onto a Flash
Drive. The laptop I am using is Lenovo X1 Carbon Gen 6. I am using the method
described here https://www.qubes-os.org/doc/thinkpad-troubleshooting/. Here is
my output of the command:
[liveuser@localhost ~]$ sudo
roup, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/85e.5c3f59e3%40qubes-os.info.
For more options, visit https://groups.google.com/d/optout.
Qubes-HCL-Dell_Inc_-Inspiron_5379-20190116-155614.yml
Description: B
Difficult to setup due to the "I219-LM" Network controller needing
permissive=true and no-strict-reset=true and unable to install latest nvidia
cuda drivers. Kernel-latest and/or Xen 4.8 does not support the Intel UHD GPU
even when disabling nouveau - must use Nvidia only for now.
Sleep not
sys-usb option is disabled during install due to keyboard being USB. Suspend
not working due to known Lenovo BIOS issues (they removed S1 and S3).
Very simple install overall. Touchscreen/pen input acts as normal mouse like
most other touchscreens.
Sleep issue is a known issue of all the
Simple install. Most things working except Suspend and "Yoga Mode" not
disabling the trackpad nor flipping the monitor. Sleep not working with BIOS
1.17
Sleep issue is a known issue of all the latest Lenovo Thinkpad models since
they removed S1 and S3 from BIOS). There are some ACPI hacks
I have not been successful in accessing VMApp files from
dom0. So I have bowed to the inevitable and placed my script
in the template. Now it works.
Thanks for your help, uman.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from
Worked like a charm!
Opened up "Konsole" in my whonix-14-gw and -ws templates
Ran this command:
sudo apt install python-concurrent.futures
I can now use the Sun/update icon to update my templates.
It seemes the benefits are:
Starts and stops each template automically, one at at a time
Can
I posted a couple of days ago about trying to install a dual boot KDE neon and
Qubes OS 4.0.1 on an HP laptop with a hybrid disk system -- 256G SSD and 1T
SATA. I had originally thought the problem was solved by installing Qubes
first and then KDE neon, since both would come up that way.
On Wed, Jan 16, 2019 at 08:31:37AM +0200, Ivan Mitev wrote:
>
>
> > Not really a Fedora person. Probably not. :-(
> > On the other hand, I *do* find a GUI way of setting the key under System
> > Settings/Keyboard in KDE, and in Xfce, under
> > SystemTools-Keyboard-Layout.
>
> Oh, you're right -
On Wed, Jan 16, 2019 at 04:22:32AM -0500, Dave Albiston wrote:
> Thanks for your patience, uman
>
> It is the exec line that is the problem. In the work domain
> I can run the script using:
>
> sh /home/Scripts/myscript.sh
>
> I guess that the menu exec statement is being run in dom0.
> So how
Having just installed Qubes 4.0.1 I am not able to get my 10Gb Intel X540-AT2
network card to work. It worked out of the box in Qubes 3.2.
This is what I get in the net-vm:
$ sudo dmesg |grep ixgbe
[2.737931] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version
5.1.0-k
[
Thanks for your patience, uman
It is the exec line that is the problem. In the work domain
I can run the script using:
sh /home/Scripts/myscript.sh
I guess that the menu exec statement is being run in dom0.
So how can the statement be changed to point to a file in
the work domain? Or,
21 matches
Mail list logo
