Previously have the same problem with 4.19 kernel: cpu freeze at some
point, now the same issue with new 4.19 kernel. I'm already checked the
group and found that other users reported the same behavior. But I think
it will not be superfluous to report this again, because this kernel
update
On Sat, Sep 14, 2019 at 4:55 PM wrote:
> Thanks a lot! That seams way better.
> So one just attach it and I works straight away? With no need to alter
> Qubes or install any software?
>
>
correct
And from and security point of view? Will it add any additional risk
> when connection to a public
It's just that sudo ifconfig -a seems yo show lo and vif2.0 but no WiFi
controller, except the Ethernet driver does not seem to be properly loaded and
wireless is not showing.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from
Also, under basic settings sys-net has networking (none) (current). Any other
attempt says Error:basic tab. Loops in network are unsopported.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving
Network has only the WiFi driver, no ethernet. Journalctl -b under nrteork
manager has :
Network manager[520]
Networking is enabled by state file, and WiFi enabled by radio killswitch;
enabled by state file.
It se es no network ando manually adding a WiFi does not connect.
Sys-net
Anil Eklavya:
>> Next, ISTR others saying USB-C devices are twitchy in Qubes. Try
>> powering everything off, then attaching the Realtek to the hub, hub to
>> laptop, and only then powering on the laptop.
>
> I did that. The device apparently gets attached to sys-net, but it is still
> not
> In dom0, do qvm-pci. Check the USED BY column to make sure the
> appropriate devices are in the appropriate qubes.
>
I tried that. There is no PCI device used by a VM, except wireless adapter
(sys-net) and USB controller (sys-usb).
> Next, ISTR others saying USB-C devices are twitchy in
Anil Eklavya:
>>>
>>> The freezing might have been caused by the PCI device changes you made.
>>> Try to undo them, so your USB controllers (only) are in sys-usb, and
>>> wifi controller (only) is in sys-net.
>>>
>>> Then, verify the Realtek is listed in dom0 under qvm-usb. You _may_ then
>>> be
>>
>> The freezing might have been caused by the PCI device changes you made.
>> Try to undo them, so your USB controllers (only) are in sys-usb, and
>> wifi controller (only) is in sys-net.
>>
>> Then, verify the Realtek is listed in dom0 under qvm-usb. You _may_ then
>> be able to map it to
> On 15-Sep-2019, at 5:32 PM, awokd wrote:
>
> Anil Eklavya:
>>> Can you diagram what you are trying to do? E.g. I think it's:
>>>
>>> Ethernet---Realtek---USB3 hub---sys-usb---sys-net(for networking) ?
> I am simply trying to connect the ethernet adapter to sys-net, instead of
> having
On 15-Sep-2019, at 4:31 PM, Anil Eklavya wrote:
> The system froze again after I attached the ethernet usb device through
> qvm-usb, even though network did not connect and the adapter was not listed
> in sys-net by lsusb.
>
> On rebooting, it froze twice while typing the disk passphrase.
Anil Eklavya:
>
>> Can someone help with this problem, right now just for getting my Qubes
>> installation started, keeping ethernet and other USB devices separate, and
>> with VPN installed somewhere. Detailed documentation can come later.
>
> Right now, I have the wireless device connected
> I have already tried attaching with qvm-usb as the Realtek adapter is listed
> by this command. It apparently gets attached with sys-net, but lsusb in
> sys-net doesn’t show it. Ifconfig also doesn’t list it.
The system froze again after I attached the ethernet usb device through
qvm-usb,
> On 15-Sep-2019, at 3:36 PM, Anil Eklavya wrote:
> Following the documentation USB and PCI devices, I tried the following:
>
> - lsusb in sys-usb to list USB devices
>
> The ethernet device is listed as Bus 003 Device 002, but there is another
> device as Bus 003 Device 001 (Linux
> On 14-Sep-2019, at 11:21 PM, Anil Eklavya wrote:
>
> The ethernet link is down in sys-net. I tried using ip and ifconfig and ifup
> commands to bring it up, but it is still down. On finally giving for now and
> pulling out the ethernet adapter, the system froze completely again, like it
>
I am brand new to QubesOS and hope to be able to update this entry over
time. I'm happy to start with this HCL report. The prospects look quite
promising.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
16 matches
Mail list logo
