> On 15-Sep-2019, at 5:32 PM, awokd <aw...@danwin1210.me> 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 network directly in sys-usb (which seems to be against the design of > Qubes, I think). I tried with qvm-sub, but it didn’t work, so I tried with > qvm-pci, but that also doesn’t work (it is not even supposed to, I think, if > the adapter is listed as a USB device). > > So, yes, the above diagram is basically correct, except that it is USB 3.1 > (type C) hub. The laptop has no ethernet port. > > About freezing, it also coincided with upgrading to a larger nvme drive from > a different company. That is why I had asked earlier if the drive can cause > the freezing, or perhaps the firmware in the drive is not reliable. Should I > go back to previous drive and see it freezing still happens. I don’t know > exactly what is happening, but given the fact that I have been using > computers of various kinds with different OS’s since 1994 as a power user (at > least), my instinctive response is that it is something malicious. At what > level it is occurring, that I don’t know. > > This is a costly laptop (with costly upgrades) and I can’t afford to buy > another laptop right now and to dispose of this one. I would like to try to > make it work if it can be made to work with Qubes. > > It was working (without freezing) earlier, but with legacy boot and with a > different drive, but I am not sure if it was compromised even then. More > importantly, it was working with sys-usb and sys-net combined. > > As an aside, the pen drive (HP class 10) I had use earlier after upgrading to > this larger nvme to update the BIOS, got bricked apparently for no reason, > without being attached to anything else. I noticed that only when I tried to > use it again for updating the BIOS again.
>> I am simply trying to connect the ethernet adapter to sys-net, instead of >> having network directly in sys-usb (which seems to be against the design of >> Qubes, I think). I tried with qvm-sub, but it didn’t work, so I tried with >> qvm-pci, but that also doesn’t work (it is not even supposed to, I think, if >> the adapter is listed as a USB device). >> >> So, yes, the above diagram is basically correct, except that it is USB 3.1 >> (type C) hub. The laptop has no ethernet port. > > 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 sys-net with qvm-usb a sys-net [Realtek]. > I will try that out. >> About freezing, it also coincided with upgrading to a larger nvme drive from >> a different company. That is why I had asked earlier if the drive can cause >> the freezing, or perhaps the firmware in the drive is not reliable. Should I >> go back to previous drive and see it freezing still happens. I don’t know >> exactly what is happening, but given the fact that I have been using >> computers of various kinds with different OS’s since 1994 as a power user >> (at least), my instinctive response is that it is something malicious. At >> what level it is occurring, that I don’t know. > > You shouldn't have to go back to the previous drive. > > PS Did you mean to drop the list from your reply? No, I just replied in the mail client and forgot to include to list mail id. I have added the missing part in the quote above for reference. -- 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/47B17116-21E9-4A24-BC53-AE719F39F149%40gmail.com.
