Re: [qubes-users] How do I get Started?

2019-12-06 Thread Claudia 

Qubes User:

Hi everyone,
Thank you for all your help and discussion. I posted the HCL for the device
I'm troubleshooting -- the latest Lenovo Flex 14 with the i5-10210U. You
can find it here:
https://groups.google.com/forum/#!topic/qubes-users/kamMImlGMNQ

I'm guessing the plan is to set up networking, update the templates and
dom0, then troubleshoot the trackpad and external monitor. I plugged in the
monitor with HDMI and it didn't show up under System Tools > Display, and
my touchpad doesn't show up under System Tools > Mouse and Touchpad.


Looking at your lspci, I'm guessing the machine doesn't have any wired 
networking? (I was going to suggest using a wired connection temporarily 
to install updates)


Just to be clear, are you trying to use a USB wireless card, or the 
internal wireless card?




Here are the outputs of some of the suggested commands in my sys-net
terminal. My sys-net is based of Fedora 29.


[user@sys-net ~]$ iwconfig
lono wireless extensions.

vif3.0no wireless extensions.

[user@sys-net ~]$ ifconfig
lo: flags=73  mtu 65536
 inet 127.0.0.1  netmask 255.0.0.0
 inet6 ::1  prefixlen 128  scopeid 0x10
 loop  txqueuelen 1000  (Local Loopback)
 RX packets 1606  bytes 129550 (126.5 KiB)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 1606  bytes 129550 (126.5 KiB)
 TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vif3.0: flags=4163  mtu 1500
 inet 10.137.0.5  netmask 255.255.255.255  broadcast 0.0.0.0
 inet6 fe80::fcff::feff:  prefixlen 64  scopeid
0x20
 ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
 RX packets 1093  bytes 67624 (66.0 KiB)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 170  bytes 15418 (15.0 KiB)
 TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[user@sys-net ~]$ iwlist
Usage: iwlist [interface] scanning [essid NNN] [last]
   [interface] frequency
   [interface] channel
   [interface] bitrate
   [interface] rate
   [interface] encryption
   [interface] keys
   [interface] power
   [interface] txpower
   [interface] retry
   [interface] ap
   [interface] accesspoints
   [interface] peers
   [interface] event
   [interface] auth
   [interface] wpakeys
   [interface] genie
   [interface] modulation


I meant for you to run `iw list`, not `iwlist`, which is a different 
command. Sorry for the confusion. However from the iwconfig & ifconfig, 
I'm fairly certain it won't show up in `iw list` anyways.




[user@sys-net ~]$ lsusb -v

Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Couldn't open device, some information will be missing
Device Descriptor:
   bLength18
   bDescriptorType 1
   bcdUSB   2.00
   bDeviceClass0
   bDeviceSubClass 0
   bDeviceProtocol 0
   bMaxPacketSize064
   idVendor   0x0627 Adomax Technology Co., Ltd
   idProduct  0x0001
   bcdDevice0.00
   iManufacturer   1
   iProduct3
   iSerial 5
   bNumConfigurations  1
   Configuration Descriptor:
 bLength 9
 bDescriptorType 2
 wTotalLength   0x0022
 bNumInterfaces  1
 bConfigurationValue 1
 iConfiguration  7
 bmAttributes 0xa0
   (Bus Powered)
   Remote Wakeup
 MaxPower  100mA
 Interface Descriptor:
   bLength 9
   bDescriptorType 4
   bInterfaceNumber0
   bAlternateSetting   0
   bNumEndpoints   1
   bInterfaceClass 3 Human Interface Device
   bInterfaceSubClass  0
   bInterfaceProtocol  0
   iInterface  0
 HID Device Descriptor:
   bLength 9
   bDescriptorType33
   bcdHID   0.01
   bCountryCode0 Not supported
   bNumDescriptors 1
   bDescriptorType34 Report
   wDescriptorLength  74
  Report Descriptors:
** UNAVAILABLE **
   Endpoint Descriptor:
 bLength 7
 bDescriptorType 5
 bEndpointAddress 0x81  EP 1 IN
 bmAttributes3
   Transfer TypeInterrupt
   Synch Type   None
   Usage Type   Data
 wMaxPacketSize 0x0008  1x 8 bytes
 bInterval   4



Not sure what this is. Googling Adomax, I get a bunch of keyboards, so 
I'm guessing your device's internal keyboard is USB (as opposed to LPC 
or th

Re: [qubes-users] How do I get Started?

2019-12-06 Thread Claudia 

Claudia:
I looked at your HCL report, and given the number of issues you're 
facing, it might be worth trying a R4.1 pre-release build, which is 
based on F29 and Xen 4.12. These builds are considered unstable, but you 
very well might end up with fewer headaches than the older stable releases.


Here is the latest build (click assets tab for ISO): 
https://openqa.qubes-os.org/tests/4428


By the end of the month, the developers plan on releasing an official 
testing ISO for R4.1 based on Fedora 31. 
https://www.mail-archive.com/qubes-users@googlegroups.com/msg31288.html


Otherwise, also worth trying is R4.0.2-rc2, which is newer than the 
4.0.1 you're using. The default kernel is a few versions newer (4.14 -> 
4.19, if I recall correctly). In a few weeks rc2 will either be declared 
stable or a new rc will be released. Either way, most likely you'll just 
have to install updates; there's a very small chance you'll have to 
reinstall from ISO using the new rc ISO.


-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  


--
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/fbacd280-4722-b766-943e-9ea6431dbb1d%40vfemail.net.

Re: [qubes-users] How do I get Started?

2019-12-05 Thread Qubes User 
Hi everyone,
Thank you for all your help and discussion. I posted the HCL for the device 
I'm troubleshooting -- the latest Lenovo Flex 14 with the i5-10210U. You 
can find it here: 
https://groups.google.com/forum/#!topic/qubes-users/kamMImlGMNQ

I'm guessing the plan is to set up networking, update the templates and 
dom0, then troubleshoot the trackpad and external monitor. I plugged in the 
monitor with HDMI and it didn't show up under System Tools > Display, and 
my touchpad doesn't show up under System Tools > Mouse and Touchpad. .

Here are the outputs of some of the suggested commands in my sys-net 
terminal. My sys-net is based of Fedora 29.

> [user@sys-net ~]$ iwconfig
> lono wireless extensions.
>
> vif3.0no wireless extensions.
>
> [user@sys-net ~]$ ifconfig
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1000  (Local Loopback)
> RX packets 1606  bytes 129550 (126.5 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 1606  bytes 129550 (126.5 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> vif3.0: flags=4163  mtu 1500
> inet 10.137.0.5  netmask 255.255.255.255  broadcast 0.0.0.0
> inet6 fe80::fcff::feff:  prefixlen 64  scopeid 
> 0x20
> ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
> RX packets 1093  bytes 67624 (66.0 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 170  bytes 15418 (15.0 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> [user@sys-net ~]$ iwlist
> Usage: iwlist [interface] scanning [essid NNN] [last]
>   [interface] frequency
>   [interface] channel
>   [interface] bitrate
>   [interface] rate
>   [interface] encryption
>   [interface] keys
>   [interface] power
>   [interface] txpower
>   [interface] retry
>   [interface] ap
>   [interface] accesspoints
>   [interface] peers
>   [interface] event
>   [interface] auth
>   [interface] wpakeys
>   [interface] genie
>   [interface] modulation
>
> [user@sys-net ~]$ lsusb -v
>
> Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
> Couldn't open device, some information will be missing
> Device Descriptor:
>   bLength18
>   bDescriptorType 1
>   bcdUSB   2.00
>   bDeviceClass0
>   bDeviceSubClass 0
>   bDeviceProtocol 0
>   bMaxPacketSize064
>   idVendor   0x0627 Adomax Technology Co., Ltd
>   idProduct  0x0001
>   bcdDevice0.00
>   iManufacturer   1
>   iProduct3
>   iSerial 5
>   bNumConfigurations  1
>   Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength   0x0022
> bNumInterfaces  1
> bConfigurationValue 1
> iConfiguration  7
> bmAttributes 0xa0
>   (Bus Powered)
>   Remote Wakeup
> MaxPower  100mA
> Interface Descriptor:
>   bLength 9
>   bDescriptorType 4
>   bInterfaceNumber0
>   bAlternateSetting   0
>   bNumEndpoints   1
>   bInterfaceClass 3 Human Interface Device
>   bInterfaceSubClass  0
>   bInterfaceProtocol  0
>   iInterface  0
> HID Device Descriptor:
>   bLength 9
>   bDescriptorType33
>   bcdHID   0.01
>   bCountryCode0 Not supported
>   bNumDescriptors 1
>   bDescriptorType34 Report
>   wDescriptorLength  74
>  Report Descriptors:
>** UNAVAILABLE **
>   Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81  EP 1 IN
> bmAttributes3
>   Transfer TypeInterrupt
>   Synch Type   None
>   Usage Type   Data
> wMaxPacketSize 0x0008  1x 8 bytes
> bInterval   4
>
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Couldn't open device, some information will be missing
> Device Descriptor:
>   bLength18
>   bDescriptorType 1
>   bcdUSB   2.00
>   bDeviceClass9 Hub
>   bDeviceSubClass 0
>   bDeviceProtocol 0 Full speed (or root) hub
>   bMaxPacketSize064
>   idVendor   0x1d6b Linux Foundation
>   idProduct  0x0002 2.0 root hub
>   bcdDevice4.14
>   iMa

Re: [qubes-users] How do I get Started?

2019-12-05 Thread Claudia 

Bernhard:



By default network cards are assigned to sys-net and are not visible
in dom0 (as far as I know). Open the Qubes Manager -> sys-net -> VM
settings -> Devices tab, and make sure your network card is assigned
to it. So you need to run lsusb or lspci from within sys-net, not
dom0. You should also run `iw list`, `iwconfig`, and/or `ifconfig` in
sys-net.

Let me clarify: PCI network cards are assigned to sys-net and not
visible in dom0 by default, regardless of USB Qube. Other PCI devices
remain in dom0.

I can "see" they exist by typing lspci in dom0 (including network cards,
and the usb controller).  My understanding is that while dom0 can see
them, they cannot see dom0 nor other qubes than the one they are
attached to (and dom0 will not talk to them unless a game-over event
occurred).


Looks like you're right. They still show up in dom0 lspci even when 
assigned to a VM. If you use 'lspci -k', you'll see that the kernel 
driver in use for assigned devices is Xen 'pciback' instead of the 
actual driver.


I also think you're right that they cannot "see" dom0, in the sense that 
they don't have DMA access to any memory owned by dom0 or any other VM. 
On machines with working VT-d at least. On machines without VT-d, the VM 
could in theory infect the device and gain access to all the machine's 
physical memory. But it's still safer to have devices in their own VMs 
such as sys-net and sys-usb, even on machines without VT-d.


The last part, I think you're right, as long as you don't reattach the 
device to dom0. When you un-assign a device from a VM it is not 
automatically reattached to dom0, as a safety feature. You shouldn't 
attach it to any other VMs either, or the device could infect that VM. 
You have to reboot, and then un-assign the device without starting the 
VM it was assigned to. However it should be safe to re-assign devices 
that support the reset command, as long as it is implemented correctly 
by the hardware/firmware. I don't know if I would trust it, personally.


The recent QSB 52 fixed a vulnerability where un-assigned devices could 
still carry out DMA attacks even without being reattached to dom0 by the 
user. If I understand correctly.


https://www.qubes-os.org/doc/pci-devices/
https://www.qubes-os.org/doc/device-handling-security/#pci-security
https://www.qubes-os.org/news/2019/10/31/qsb-052/




You also have the option of combining
sys-net and sys-usb into the same Qube so no passthru is necessary. (Or
is that mandatory when using USB network cards and a USB Qube?)

USB is one attack surface, network another. I would suggest to keep them
apart. In fact, a USB qube does not need any networking at all (not even
internet access). Imagine its becomes victim of a "bad-usb"  then it
still cannot 'break out' and phone home, for example. Actually my


Yeah, it's definitely more secure to have them separate. I think the 
option is there in case you run into trouble passing a USB network card 
from sys-usb to sys-net. Combining them doesn't require any USB 
passthru, just PCI passthru of the USB controllers, so it's simpler and 
more likely to work. That would be my guess anyway. I don't really know 
how USB passthru works. Also useful for machines that don't have much 
ram to spare, maybe.



sys-usb is halted by default unless I really need it (consequence: if
you plug any usb device, nothing happens. just nothing.).



Just curious, when you plug in a flash drive while your sys-usb is off, 
does the flash drive's LED turn on at all for you? I noticed on one of 
my machines, when USB qube is enabled (hide_all_usb), my devices aren't 
recognized, and when I plug in a flash drive the LED blinks very briefly 
and then turns off. The same flash drive on other OSes, or with USB qube 
disabled, the LED normally stays on, and blinks when you access the 
drive. (I currently don't have a Qubes machine with a working USB qube I 
could try this on.)


-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  


--
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/f1c8a59a-7b35-0ccd-eacb-fe722878cb7a%40vfemail.net.

Re: [qubes-users] How do I get Started?

2019-12-04 Thread Bernhard 




By default network cards are assigned to sys-net and are not visible
in dom0 (as far as I know). Open the Qubes Manager -> sys-net -> VM
settings -> Devices tab, and make sure your network card is assigned
to it. So you need to run lsusb or lspci from within sys-net, not
dom0. You should also run `iw list`, `iwconfig`, and/or `ifconfig` in
sys-net.

Let me clarify: PCI network cards are assigned to sys-net and not
visible in dom0 by default, regardless of USB Qube. Other PCI devices
remain in dom0.

I can "see" they exist by typing lspci in dom0 (including network cards,
and the usb controller).  My understanding is that while dom0 can see
them, they cannot see dom0 nor other qubes than the one they are
attached to (and dom0 will not talk to them unless a game-over event
occurred).


If using a USB Qube: all USB devices are assigned to sys-usb and not
visible in dom0. I assume USB network cards are automatically passed
thru to sys-net from sys-usb.

I never checked that. Maybe you need to pass them over by hand. That is
what I would expect at least.

You also have the option of combining
sys-net and sys-usb into the same Qube so no passthru is necessary. (Or
is that mandatory when using USB network cards and a USB Qube?)

USB is one attack surface, network another. I would suggest to keep them
apart. In fact, a USB qube does not need any networking at all (not even
internet access). Imagine its becomes victim of a "bad-usb"  then it
still cannot 'break out' and phone home, for example. Actually my
sys-usb is halted by default unless I really need it (consequence: if
you plug any usb device, nothing happens. just nothing.).

--
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/0bc7459b-6110-4b93-b3d7-a8cd9ed16cf9%40web.de.

Re: [qubes-users] How do I get Started?

2019-12-04 Thread Claudia 

Claudia:

By default network cards are assigned to sys-net and are not visible in 
dom0 (as far as I know). Open the Qubes Manager -> sys-net -> VM 
settings -> Devices tab, and make sure your network card is assigned to 
it. So you need to run lsusb or lspci from within sys-net, not dom0. You 
should also run `iw list`, `iwconfig`, and/or `ifconfig` in sys-net.


Let me clarify: PCI network cards are assigned to sys-net and not 
visible in dom0 by default, regardless of USB Qube. Other PCI devices 
remain in dom0.


If using a USB Qube: all USB devices are assigned to sys-usb and not 
visible in dom0. I assume USB network cards are automatically passed 
thru to sys-net from sys-usb. You also have the option of combining 
sys-net and sys-usb into the same Qube so no passthru is necessary. (Or 
is that mandatory when using USB network cards and a USB Qube?)


If not using a USB Qube: all USB devices live in dom0, and USB network 
cards are passed thru to sys-net the same way they would be from sys-usb 
if it were present. Therefore, USB network cards should be visible in 
dom0 lsusb, but not dom0 ifconfig, and they should be visible in sys-net 
ifconfig but not sys-net lsusb.


I think, at least. Can anyone else verify if this is correct?

-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  


--
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/1e625031-af5d-63f0-6270-56c8ffafdea1%40vfemail.net.

Re: [qubes-users] How do I get Started?

2019-12-04 Thread Claudia 

Qubes User:

Thank you for your help.



Happy to do what I can.

First, if you can, please generate an HCL report on the machine and send 
it to the mailing list. This will tell us some basic info about your 
machine so we have a better idea what we're troubleshooting. (It also 
helps the Qubes developers improve compatibility.)


Here's how:
https://www.qubes-os.org/doc/hcl/


When I click the applet, I see:
Ethernet Network
device not managed
VPN Connections >
I don't see my WiFi networks. When I launch network manager in sys-net, I
tried
to manually input the information for my WiFi (with the SSID and
WPA2/Personal),
but it doesn't connect after.

When I run "lsusb" in the dom0 terminal, I get:
Realtek Semiconductor Corp
VIA Labs, Inc.
Linux Foundation 3.0 root hub
blank
Chicony Electronics Co., Ltd
VIA Lbs, Inc.
Logitech, Inc. Unifying Receiver (for my usb mouse)
Terminus Technology Inc.
VIA Labs, Inc.
Intel Corp.
Linux Foundation 2.0 root hub
None of these are my network cards, right?


By default network cards are assigned to sys-net and are not visible in 
dom0 (as far as I know). Open the Qubes Manager -> sys-net -> VM 
settings -> Devices tab, and make sure your network card is assigned to 
it. So you need to run lsusb or lspci from within sys-net, not dom0. You 
should also run `iw list`, `iwconfig`, and/or `ifconfig` in sys-net.


Off the top of my head, the realtek device could be a wireless network 
adapter, wired ethernet adapter, or soundcard. There are several others 
in that list I don't know what they are. Use `lsusb -v` to show more 
information including the device class.


If you still can't find it, next step would probably be to post the 
output of `journalctl -k -b` from both dom0 and sys-net. Also, as 
another user mentioned, open the **template** for sys-net (probably 
fedora-29, or such -- look in the template column of sys-net in the 
Qubes Manager) and make sure your wireless card firmware is installed. 
Don't attempt to install it in sys-net directly, because it will be lost 
on reboot.


Some info about wireless firmware:
https://fedoraproject.org/wiki/Firmware
https://wiki.debian.org/WiFi#USB_Devices

Info about how templates work in Qubes, if you're not familiar:
https://www.qubes-os.org/doc/templates/
https://www.qubes-os.org/doc/software-update-domu

  


2. How do I use an external display with HDMI? (just plugging it in

doesn't

work for me)


What do you see when you plug it in? "No signal"? Blank screen?

You might have to do some configuration in XFCE. Look under system tools
for monitor/screen settings. Otherwise, you could try installing KDE.

https://www.qubes-os.org/doc/kde/

Note that a lot of hardware features don't always work in Qubes. HDMI is
not tested very often by Qubes users, so I don't know if HDMI usually
works or not.

Does it work when running a Fedora 25 live CD? Did you have it working
on this machine on any other operating systems?


When I plug in my HDMI, nothing happens. On Windows, the external display
works when I plug it in. I can try running Fedora on a live usb to see what
happens.


Let us know if it works in Fedora, preferably Fedora 25 as that's what 
Qubes 4.0.x is based on. If it doesn't work in F25, try it in F31. You 
may want to try each of those in the XFCE flavor as well 
(https://spins.fedoraproject.org/xfce/download/index.html), because 
Qubes uses XFCE.


You could also try a newer dom0 kernel. 
https://www.qubes-os.org/doc/software-update-dom0/#kernel-upgrade


Also, just wanted to add, it would be helpful for us to know what GPU 
you're using.





3. How do I reduce the lag on my USB mouse?


I'm afraid I don't know much about this. Are you using dom0 or sys-usb?
Is anything else laggy? Does the touchpad (if any) work alright?

You can try temporarily disabling sys-usb so devices are attached to
dom0. See if it works any better that way.
https://www.qubes-os.org/doc/usb-qubes/#removing-a-usb-qube


I don't think I have usb-qubes enabled. I wasn't able to enable them after
installation,
maybe because I have a USB keyboard.
However, my touchpad/trackpad doesn't work. What can I do about that?


That I'm also not real sure about. It's been a while since I've had to 
troubleshoot a touchpad. Typically they are USB devices, I think. Does 
it show up in dom0 lsusb? Do you see anything in `journalctl -k -b | 
grep -i input`? Do you know what touchpad you have (e.g. Synaptics, 
ALPS, Elantec)?


Here are some basic, non-Qubes tips to start with. Follow these and let 
us know what you get.

https://wiki.ubuntu.com/DebuggingTouchpadDetection

Also, once again, boot a Fedora live CD and make sure the touchpad works 
there. Try 25 first, and if it doesn't work try 31. This will help 
narrow it down.


You can also try a newer kernel, as mentioned above.

-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net

ONLY AT VFEmail! - Use our Metadata Mitigator to

Re: [qubes-users] How do I get Started?

2019-12-04 Thread haaber 

When I click the applet, I see:
Ethernet Network
device not managed
VPN Connections >
I don't see my WiFi networks. When I launch network manager in sys-net,
I tried
to manually input the information for my WiFi (with the SSID and
WPA2/Personal),
but it doesn't connect after.


Try lspci in dom0 and look for your wireless adapter (try "lspci |grep
-i wireless" if you are lazy). Then go in the sys-net template (! not
sys-net itself) and verify the firmware for your hardware is installed.
Then reboot sys-net and have a look again. Also check that the hardware
is accessible to sys-net via the "devices" tab of the qubes settings.

--
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/2f734aa6-9019-9359-18f0-3dae118629b1%40web.de.

Re: [qubes-users] How do I get Started?

2019-12-03 Thread Qubes User 
Thank you for your help. 

On Tuesday, December 3, 2019 at 12:10:11 PM UTC-8, Claudia wrote:
>
> Qubes User: 
> > I just installed Qubes on a new laptop. I'm trying to do some basic 
> things 
> > not listed on https://www.qubes-os.org/getting-started/ 
> > 
> > 1. How do I get connected to my wi-fi? 
>
> The networkmanager applet should appear in the task tray (next to the 
> clock). Just click on that and select a network. Make sure sys-net is 
> running. Can you manually launch networkmanager in sys-net? Do you see 
> your network card in iwconfig, ifconfig, lsusb, lspci, in sys-net? 
>
> When I click the applet, I see: 
Ethernet Network
device not managed
VPN Connections >
I don't see my WiFi networks. When I launch network manager in sys-net, I 
tried
to manually input the information for my WiFi (with the SSID and 
WPA2/Personal), 
but it doesn't connect after. 

When I run "lsusb" in the dom0 terminal, I get:
Realtek Semiconductor Corp
VIA Labs, Inc.
Linux Foundation 3.0 root hub
blank
Chicony Electronics Co., Ltd
VIA Lbs, Inc.
Logitech, Inc. Unifying Receiver (for my usb mouse)
Terminus Technology Inc.
VIA Labs, Inc.
Intel Corp.
Linux Foundation 2.0 root hub
None of these are my network cards, right? 
 

> > 2. How do I use an external display with HDMI? (just plugging it in 
> doesn't 
> > work for me) 
>
> What do you see when you plug it in? "No signal"? Blank screen? 
>
> You might have to do some configuration in XFCE. Look under system tools 
> for monitor/screen settings. Otherwise, you could try installing KDE. 
>
> https://www.qubes-os.org/doc/kde/ 
>
> Note that a lot of hardware features don't always work in Qubes. HDMI is 
> not tested very often by Qubes users, so I don't know if HDMI usually 
> works or not. 
>
> Does it work when running a Fedora 25 live CD? Did you have it working 
> on this machine on any other operating systems? 
>
When I plug in my HDMI, nothing happens. On Windows, the external display
works when I plug it in. I can try running Fedora on a live usb to see what 
happens. 

>
> > 3. How do I reduce the lag on my USB mouse? 
>
> I'm afraid I don't know much about this. Are you using dom0 or sys-usb? 
> Is anything else laggy? Does the touchpad (if any) work alright? 
>
> You can try temporarily disabling sys-usb so devices are attached to 
> dom0. See if it works any better that way. 
> https://www.qubes-os.org/doc/usb-qubes/#removing-a-usb-qube

I don't think I have usb-qubes enabled. I wasn't able to enable them after 
installation,
maybe because I have a USB keyboard. 
However, my touchpad/trackpad doesn't work. What can I do about that?

>
>
> - 
> This free account was provided by VFEmail.net - report spam to 
> ab...@vfemail.net  
>   
> ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of 
> the NSA's hands! 
> $24.95 ONETIME Lifetime accounts with Privacy Features!   
> 15GB disk! No bandwidth quotas! 
> Commercial and Bulk Mail Options!   
>

-- 
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/38321cc0-496a-4811-9cf7-46249e16ee4b%40googlegroups.com.

Re: [qubes-users] How do I get Started?

2019-12-03 Thread Claudia 

Qubes User:

I just installed Qubes on a new laptop. I'm trying to do some basic things
not listed on https://www.qubes-os.org/getting-started/

1. How do I get connected to my wi-fi?


The networkmanager applet should appear in the task tray (next to the 
clock). Just click on that and select a network. Make sure sys-net is 
running. Can you manually launch networkmanager in sys-net? Do you see 
your network card in iwconfig, ifconfig, lsusb, lspci, in sys-net?



2. How do I use an external display with HDMI? (just plugging it in doesn't
work for me)


What do you see when you plug it in? "No signal"? Blank screen?

You might have to do some configuration in XFCE. Look under system tools 
for monitor/screen settings. Otherwise, you could try installing KDE.


https://www.qubes-os.org/doc/kde/

Note that a lot of hardware features don't always work in Qubes. HDMI is 
not tested very often by Qubes users, so I don't know if HDMI usually 
works or not.


Does it work when running a Fedora 25 live CD? Did you have it working 
on this machine on any other operating systems?



3. How do I reduce the lag on my USB mouse?


I'm afraid I don't know much about this. Are you using dom0 or sys-usb? 
Is anything else laggy? Does the touchpad (if any) work alright?


You can try temporarily disabling sys-usb so devices are attached to 
dom0. See if it works any better that way. 
https://www.qubes-os.org/doc/usb-qubes/#removing-a-usb-qube


-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  


--
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/dec7d491-1378-5b0b-98c8-a3630daeba86%40vfemail.net.

[qubes-users] How do I get Started?

2019-12-02 Thread Qubes User 
I just installed Qubes on a new laptop. I'm trying to do some basic things 
not listed on https://www.qubes-os.org/getting-started/

1. How do I get connected to my wi-fi?
2. How do I use an external display with HDMI? (just plugging it in doesn't 
work for me)
3. How do I reduce the lag on my USB mouse?

-- 
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/a48b2391-9159-46b3-b465-9ba3b6066938%40googlegroups.com.