Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
Thank you that worked perfect! Very much appreciated! I think I have enough to help with some documentation for the true beginner. Both laptop and pc, Qubes is running and I’m learning more of the operating system. Great OS, this platform is awesome. I do have a question, adding vpn? Or just running a qube with Tor. Recommendations of adding a vpn Also it seems pointless to adding a Windows Os to. VM I’m Qubes. Just running a template qube seems ideal? Thanks to everyone who has jumped in with help! I hope I will be able to assist others to pay it forward. On Sat, Nov 10, 2018 at 11:18 AM 'awokd' via qubes-users < qubes-users@googlegroups.com> wrote: > LMiller M: > > I got sys-firewall to start green state. I cannot get fedora 26 to > update. > > It crashes. Debain 9 starts and updated as required. Both PC and laptop > > will not let fedora update. Any suggestions? > > > > Yes I would like to contribute to the help documentation. I will look at > > the link and post what I have come across. > > > > Thank you very much for helping. > > On Sat, Nov 10, 2018 at 10:51 AM LMiller M <56lmil...@gmail.com> wrote: > > > >> Stuart! > >> > >> Yes the pci device is my Nic. Thank you.. I didn’t realize sys-Firewall > >> had the Nic assigned to it. I removed t and the firewall started > >> > >> Thank you.. > >> On Fri, Nov 9, 2018 at 7:32 PM Stuart Perkins > > >> wrote: > >> > >>> > >>> > >>> On Fri, 9 Nov 2018 10:45:06 -0500 > >>> LMiller M <56lmil...@gmail.com> wrote: > >>> > Ok back with the laptop. During boot up, dom0 green state, sys-net > green > state. WiFi connection good, and can reboot! Lol > > But with that said nothing else auto loads. I have to start fedora-26 > and > it will. > > When trying to start sys-firewall I get error ( PCI device 02:00.0 is > in > use by driver xenlight domain sys-net > Log: /var/log/libvirt/libxl/libxl-driver.log > > I don’t see this log listed with sys-net, there are no logs with > sys-firewall. I don’t see this listed in the Qubes log either. > > I have looked up help, but others have usb issues. I don’t have any > attached and not trying to do anything with them as stated . > > I tried command qvm-pci attach —persistent —option permissive=True > >>> —option > no-strict-reset > > But I’m missing something so it’s not working. I’m in the right > >>> direction? > I need to reset pci and set no restrictions? > > > On Wed, Nov 7, 2018 at 9:32 PM LMiller M <56lmil...@gmail.com> wrote: > > > Ok so I figured out how to see the logs. > > > > I have been able to figure out why the laptop wasn’t responding to > the > >>> OS > > correctly. Now it’s working and updating as needed. > > > > I will explain more as I learn more. > > > > I do appreciate the guidance. I think there is more that can be > shown, > >>> to > > help newbies. > > > > I’m going to put something together from my view point to see if you > >>> all > > agree. Maybe it can be useful to all new qube users like me. Lol > >>> anyway, I > > wouldn’t have figured it out as fast for myself with out your help. > > > > Thank you for helping me. > > > > I’m still figuring things out, but this build is awesome and so much > to > > learn with it. > > On Tue, Nov 6, 2018 at 4:43 PM LMiller M <56lmil...@gmail.com> > wrote: > > > >> Ok on first boot after install Qubes will show the kernel failure > and > >> bypass and boot into dom0. > >> > >> Once there, in the Qubes manager dom0 has green state. > >> > >> Lol ok don’t laugh too hard. So I checked devices like have been, > >>> sys-net > >> as you mentioned. Both Ethernet and WiFi devices are there. So I > just > >> removed my Ethernet from device selection and bingo sys-net green > >>> state! > >> > >> So I will try now to run system updates for dom0 and fedora. > >> > >> Thanks again for point things out. Sometimes you look at something > so > >> crazy and just need a second thought. > >> > >> So, can you show me how to check logs if I run into issues? Lol > please > >> and thanks > >> On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users < > >> qubes-users@googlegroups.com> wrote: > >> > >>> > >>> LMiller M: > Update: Kernel failure during boot install OS 4.0 > > After the install booted into dom0, checking Qubes kernel package > >>> to > >>> see > what three were stored or available. Mine only list one kernel. > > 4.14.18-1 > > I checked using the rpm -qa ‘kernel-Qubes-vm*’ > > Using the install update option I get: > > Unable to reset pci device :03:00.2: > > Trying to apply the device to the selected box: error: device tab: > >>> can’t >
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
LMiller M: I got sys-firewall to start green state. I cannot get fedora 26 to update. It crashes. Debain 9 starts and updated as required. Both PC and laptop will not let fedora update. Any suggestions? Yes I would like to contribute to the help documentation. I will look at the link and post what I have come across. Thank you very much for helping. On Sat, Nov 10, 2018 at 10:51 AM LMiller M <56lmil...@gmail.com> wrote: Stuart! Yes the pci device is my Nic. Thank you.. I didn’t realize sys-Firewall had the Nic assigned to it. I removed t and the firewall started Thank you.. On Fri, Nov 9, 2018 at 7:32 PM Stuart Perkins wrote: On Fri, 9 Nov 2018 10:45:06 -0500 LMiller M <56lmil...@gmail.com> wrote: Ok back with the laptop. During boot up, dom0 green state, sys-net green state. WiFi connection good, and can reboot! Lol But with that said nothing else auto loads. I have to start fedora-26 and it will. When trying to start sys-firewall I get error ( PCI device 02:00.0 is in use by driver xenlight domain sys-net Log: /var/log/libvirt/libxl/libxl-driver.log I don’t see this log listed with sys-net, there are no logs with sys-firewall. I don’t see this listed in the Qubes log either. I have looked up help, but others have usb issues. I don’t have any attached and not trying to do anything with them as stated . I tried command qvm-pci attach —persistent —option permissive=True —option no-strict-reset But I’m missing something so it’s not working. I’m in the right direction? I need to reset pci and set no restrictions? On Wed, Nov 7, 2018 at 9:32 PM LMiller M <56lmil...@gmail.com> wrote: Ok so I figured out how to see the logs. I have been able to figure out why the laptop wasn’t responding to the OS correctly. Now it’s working and updating as needed. I will explain more as I learn more. I do appreciate the guidance. I think there is more that can be shown, to help newbies. I’m going to put something together from my view point to see if you all agree. Maybe it can be useful to all new qube users like me. Lol anyway, I wouldn’t have figured it out as fast for myself with out your help. Thank you for helping me. I’m still figuring things out, but this build is awesome and so much to learn with it. On Tue, Nov 6, 2018 at 4:43 PM LMiller M <56lmil...@gmail.com> wrote: Ok on first boot after install Qubes will show the kernel failure and bypass and boot into dom0. Once there, in the Qubes manager dom0 has green state. Lol ok don’t laugh too hard. So I checked devices like have been, sys-net as you mentioned. Both Ethernet and WiFi devices are there. So I just removed my Ethernet from device selection and bingo sys-net green state! So I will try now to run system updates for dom0 and fedora. Thanks again for point things out. Sometimes you look at something so crazy and just need a second thought. So, can you show me how to check logs if I run into issues? Lol please and thanks On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users < qubes-users@googlegroups.com> wrote: LMiller M: Update: Kernel failure during boot install OS 4.0 After the install booted into dom0, checking Qubes kernel package to see what three were stored or available. Mine only list one kernel. 4.14.18-1 I checked using the rpm -qa ‘kernel-Qubes-vm*’ Using the install update option I get: Unable to reset pci device :03:00.2: Trying to apply the device to the selected box: error: device tab: can’t attach pci device to VM in pvh mode Does that mode need to be changed? Stupid question but because honestly I don’t know. How do you check the logs? I’m the terminal? I downloaded the new kernel to cd, can install from the cd? I don’t see anything on the Qubes kernel page except download from internet throw Qubes. With internet I can’t. On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com> wrote: So, after looking more into the kernel issue. I see on the Qubes site some instructions for trying to change the kernel. I’m going to do a reinstall of the 4.0 os to get back into Dom0 and try it out. I will post back hopefully with success.. On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com> wrote: Ok so one more if I can please, this is on a Asus K56c laptop and it has a kernel failure on boot with Qubes Os 4.0. On the first install it shows the kernel failure and it boots to the OS don0. If I turn off or reboot it shows my kernel failure and won’t load into the os. Glad you got your other computer working at least! So on this one, where are you getting this kernel failure exactly? If it's booting to dom0, I'm not following where you're having trouble. There's a message on boot about failed to load kernel modules that can be safely ignored. To update dom0, you want to use "sudo qubes-dom0-update". You should rarely need to update the kernel by itself. Is that when you are getting the PCI reset error? Is your sys-net started?
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
I got sys-firewall to start green state. I cannot get fedora 26 to update. It crashes. Debain 9 starts and updated as required. Both PC and laptop will not let fedora update. Any suggestions? Yes I would like to contribute to the help documentation. I will look at the link and post what I have come across. Thank you very much for helping. On Sat, Nov 10, 2018 at 10:51 AM LMiller M <56lmil...@gmail.com> wrote: > Stuart! > > Yes the pci device is my Nic. Thank you.. I didn’t realize sys-Firewall > had the Nic assigned to it. I removed t and the firewall started > > Thank you.. > On Fri, Nov 9, 2018 at 7:32 PM Stuart Perkins > wrote: > >> >> >> On Fri, 9 Nov 2018 10:45:06 -0500 >> LMiller M <56lmil...@gmail.com> wrote: >> >> >Ok back with the laptop. During boot up, dom0 green state, sys-net green >> >state. WiFi connection good, and can reboot! Lol >> > >> >But with that said nothing else auto loads. I have to start fedora-26 and >> >it will. >> > >> >When trying to start sys-firewall I get error ( PCI device 02:00.0 is in >> >use by driver xenlight domain sys-net >> >Log: /var/log/libvirt/libxl/libxl-driver.log >> > >> >I don’t see this log listed with sys-net, there are no logs with >> >sys-firewall. I don’t see this listed in the Qubes log either. >> > >> >I have looked up help, but others have usb issues. I don’t have any >> >attached and not trying to do anything with them as stated . >> > >> >I tried command qvm-pci attach —persistent —option permissive=True >> —option >> >no-strict-reset >> > >> >But I’m missing something so it’s not working. I’m in the right >> direction? >> >I need to reset pci and set no restrictions? >> > >> > >> >On Wed, Nov 7, 2018 at 9:32 PM LMiller M <56lmil...@gmail.com> wrote: >> > >> >> Ok so I figured out how to see the logs. >> >> >> >> I have been able to figure out why the laptop wasn’t responding to the >> OS >> >> correctly. Now it’s working and updating as needed. >> >> >> >> I will explain more as I learn more. >> >> >> >> I do appreciate the guidance. I think there is more that can be shown, >> to >> >> help newbies. >> >> >> >> I’m going to put something together from my view point to see if you >> all >> >> agree. Maybe it can be useful to all new qube users like me. Lol >> anyway, I >> >> wouldn’t have figured it out as fast for myself with out your help. >> >> >> >> Thank you for helping me. >> >> >> >> I’m still figuring things out, but this build is awesome and so much to >> >> learn with it. >> >> On Tue, Nov 6, 2018 at 4:43 PM LMiller M <56lmil...@gmail.com> wrote: >> >> >> >>> Ok on first boot after install Qubes will show the kernel failure and >> >>> bypass and boot into dom0. >> >>> >> >>> Once there, in the Qubes manager dom0 has green state. >> >>> >> >>> Lol ok don’t laugh too hard. So I checked devices like have been, >> sys-net >> >>> as you mentioned. Both Ethernet and WiFi devices are there. So I just >> >>> removed my Ethernet from device selection and bingo sys-net green >> state! >> >>> >> >>> So I will try now to run system updates for dom0 and fedora. >> >>> >> >>> Thanks again for point things out. Sometimes you look at something so >> >>> crazy and just need a second thought. >> >>> >> >>> So, can you show me how to check logs if I run into issues? Lol please >> >>> and thanks >> >>> On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users < >> >>> qubes-users@googlegroups.com> wrote: >> >>> >> >> LMiller M: >> > Update: Kernel failure during boot install OS 4.0 >> > >> > After the install booted into dom0, checking Qubes kernel package >> to >> see >> > what three were stored or available. Mine only list one kernel. >> > >> > 4.14.18-1 >> > >> > I checked using the rpm -qa ‘kernel-Qubes-vm*’ >> > >> > Using the install update option I get: >> > >> > Unable to reset pci device :03:00.2: >> > >> > Trying to apply the device to the selected box: error: device tab: >> can’t >> > attach pci device to VM in pvh mode >> > >> > Does that mode need to be changed? >> > >> > Stupid question but because honestly I don’t know. How do you >> check the >> > logs? I’m the terminal? >> > >> > I downloaded the new kernel to cd, can install from the cd? I >> don’t see >> > anything on the Qubes kernel page except download from internet >> throw >> > Qubes. With internet I can’t. >> > >> > >> > On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com> >> wrote: >> > >> >> So, after looking more into the kernel issue. I see on the Qubes >> site >> some >> >> instructions for trying to change the kernel. I’m going to do a >> reinstall >> >> of the 4.0 os to get back into Dom0 and try it out. I will post >> back >> >> hopefully with success.. >> >> On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com> >> wrote: >> >> >> >>> Ok so one
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
Stuart! Yes the pci device is my Nic. Thank you.. I didn’t realize sys-Firewall had the Nic assigned to it. I removed t and the firewall started Thank you.. On Fri, Nov 9, 2018 at 7:32 PM Stuart Perkins wrote: > > > On Fri, 9 Nov 2018 10:45:06 -0500 > LMiller M <56lmil...@gmail.com> wrote: > > >Ok back with the laptop. During boot up, dom0 green state, sys-net green > >state. WiFi connection good, and can reboot! Lol > > > >But with that said nothing else auto loads. I have to start fedora-26 and > >it will. > > > >When trying to start sys-firewall I get error ( PCI device 02:00.0 is in > >use by driver xenlight domain sys-net > >Log: /var/log/libvirt/libxl/libxl-driver.log > > > >I don’t see this log listed with sys-net, there are no logs with > >sys-firewall. I don’t see this listed in the Qubes log either. > > > >I have looked up help, but others have usb issues. I don’t have any > >attached and not trying to do anything with them as stated . > > > >I tried command qvm-pci attach —persistent —option permissive=True —option > >no-strict-reset > > > >But I’m missing something so it’s not working. I’m in the right direction? > >I need to reset pci and set no restrictions? > > > > > >On Wed, Nov 7, 2018 at 9:32 PM LMiller M <56lmil...@gmail.com> wrote: > > > >> Ok so I figured out how to see the logs. > >> > >> I have been able to figure out why the laptop wasn’t responding to the > OS > >> correctly. Now it’s working and updating as needed. > >> > >> I will explain more as I learn more. > >> > >> I do appreciate the guidance. I think there is more that can be shown, > to > >> help newbies. > >> > >> I’m going to put something together from my view point to see if you all > >> agree. Maybe it can be useful to all new qube users like me. Lol > anyway, I > >> wouldn’t have figured it out as fast for myself with out your help. > >> > >> Thank you for helping me. > >> > >> I’m still figuring things out, but this build is awesome and so much to > >> learn with it. > >> On Tue, Nov 6, 2018 at 4:43 PM LMiller M <56lmil...@gmail.com> wrote: > >> > >>> Ok on first boot after install Qubes will show the kernel failure and > >>> bypass and boot into dom0. > >>> > >>> Once there, in the Qubes manager dom0 has green state. > >>> > >>> Lol ok don’t laugh too hard. So I checked devices like have been, > sys-net > >>> as you mentioned. Both Ethernet and WiFi devices are there. So I just > >>> removed my Ethernet from device selection and bingo sys-net green > state! > >>> > >>> So I will try now to run system updates for dom0 and fedora. > >>> > >>> Thanks again for point things out. Sometimes you look at something so > >>> crazy and just need a second thought. > >>> > >>> So, can you show me how to check logs if I run into issues? Lol please > >>> and thanks > >>> On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users < > >>> qubes-users@googlegroups.com> wrote: > >>> > > LMiller M: > > Update: Kernel failure during boot install OS 4.0 > > > > After the install booted into dom0, checking Qubes kernel package to > see > > what three were stored or available. Mine only list one kernel. > > > > 4.14.18-1 > > > > I checked using the rpm -qa ‘kernel-Qubes-vm*’ > > > > Using the install update option I get: > > > > Unable to reset pci device :03:00.2: > > > > Trying to apply the device to the selected box: error: device tab: > can’t > > attach pci device to VM in pvh mode > > > > Does that mode need to be changed? > > > > Stupid question but because honestly I don’t know. How do you check > the > > logs? I’m the terminal? > > > > I downloaded the new kernel to cd, can install from the cd? I don’t > see > > anything on the Qubes kernel page except download from internet > throw > > Qubes. With internet I can’t. > > > > > > On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com> > wrote: > > > >> So, after looking more into the kernel issue. I see on the Qubes > site > some > >> instructions for trying to change the kernel. I’m going to do a > reinstall > >> of the 4.0 os to get back into Dom0 and try it out. I will post > back > >> hopefully with success.. > >> On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com> > wrote: > >> > >>> Ok so one more if I can please, this is on a Asus K56c laptop and > it > has > >>> a kernel failure on boot with Qubes Os 4.0. On the first install > it > shows > >>> the kernel failure and it boots to the OS don0. If I turn off or > reboot it > >>> shows my kernel failure and won’t load into the os. > >>> > Glad you got your other computer working at least! So on this one, > where > are you getting this kernel failure exactly? If it's booting to dom0, > I'm not following where you're having trouble. There's a message
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
LMiller M: Ok so I figured out how to see the logs. I have been able to figure out why the laptop wasn’t responding to the OS correctly. Now it’s working and updating as needed. I will explain more as I learn more. I do appreciate the guidance. I think there is more that can be shown, to help newbies. I’m going to put something together from my view point to see if you all agree. Maybe it can be useful to all new qube users like me. Lol anyway, I wouldn’t have figured it out as fast for myself with out your help. Thank you for helping me. I’m still figuring things out, but this build is awesome and so much to learn with it. There is definitely a learning curve to Qubes. On some hardware the steepest part can unfortunately be right in the beginning with the install. Glad you're making progress! If you want to help contribute to the documentation, check out https://www.qubes-os.org/doc/doc-guidelines/. -- 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/c018f247-7163-c63b-abbe-2b2d1dd13e69%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
On Fri, 9 Nov 2018 10:45:06 -0500 LMiller M <56lmil...@gmail.com> wrote: >Ok back with the laptop. During boot up, dom0 green state, sys-net green >state. WiFi connection good, and can reboot! Lol > >But with that said nothing else auto loads. I have to start fedora-26 and >it will. > >When trying to start sys-firewall I get error ( PCI device 02:00.0 is in >use by driver xenlight domain sys-net >Log: /var/log/libvirt/libxl/libxl-driver.log > >I don’t see this log listed with sys-net, there are no logs with >sys-firewall. I don’t see this listed in the Qubes log either. > >I have looked up help, but others have usb issues. I don’t have any >attached and not trying to do anything with them as stated . > >I tried command qvm-pci attach —persistent —option permissive=True —option >no-strict-reset > >But I’m missing something so it’s not working. I’m in the right direction? >I need to reset pci and set no restrictions? > > >On Wed, Nov 7, 2018 at 9:32 PM LMiller M <56lmil...@gmail.com> wrote: > >> Ok so I figured out how to see the logs. >> >> I have been able to figure out why the laptop wasn’t responding to the OS >> correctly. Now it’s working and updating as needed. >> >> I will explain more as I learn more. >> >> I do appreciate the guidance. I think there is more that can be shown, to >> help newbies. >> >> I’m going to put something together from my view point to see if you all >> agree. Maybe it can be useful to all new qube users like me. Lol anyway, I >> wouldn’t have figured it out as fast for myself with out your help. >> >> Thank you for helping me. >> >> I’m still figuring things out, but this build is awesome and so much to >> learn with it. >> On Tue, Nov 6, 2018 at 4:43 PM LMiller M <56lmil...@gmail.com> wrote: >> >>> Ok on first boot after install Qubes will show the kernel failure and >>> bypass and boot into dom0. >>> >>> Once there, in the Qubes manager dom0 has green state. >>> >>> Lol ok don’t laugh too hard. So I checked devices like have been, sys-net >>> as you mentioned. Both Ethernet and WiFi devices are there. So I just >>> removed my Ethernet from device selection and bingo sys-net green state! >>> >>> So I will try now to run system updates for dom0 and fedora. >>> >>> Thanks again for point things out. Sometimes you look at something so >>> crazy and just need a second thought. >>> >>> So, can you show me how to check logs if I run into issues? Lol please >>> and thanks >>> On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users < >>> qubes-users@googlegroups.com> wrote: >>> LMiller M: > Update: Kernel failure during boot install OS 4.0 > > After the install booted into dom0, checking Qubes kernel package to see > what three were stored or available. Mine only list one kernel. > > 4.14.18-1 > > I checked using the rpm -qa ‘kernel-Qubes-vm*’ > > Using the install update option I get: > > Unable to reset pci device :03:00.2: > > Trying to apply the device to the selected box: error: device tab: can’t > attach pci device to VM in pvh mode > > Does that mode need to be changed? > > Stupid question but because honestly I don’t know. How do you check the > logs? I’m the terminal? > > I downloaded the new kernel to cd, can install from the cd? I don’t see > anything on the Qubes kernel page except download from internet throw > Qubes. With internet I can’t. > > > On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com> wrote: > >> So, after looking more into the kernel issue. I see on the Qubes site some >> instructions for trying to change the kernel. I’m going to do a reinstall >> of the 4.0 os to get back into Dom0 and try it out. I will post back >> hopefully with success.. >> On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com> wrote: >> >>> Ok so one more if I can please, this is on a Asus K56c laptop and it has >>> a kernel failure on boot with Qubes Os 4.0. On the first install it shows >>> the kernel failure and it boots to the OS don0. If I turn off or reboot it >>> shows my kernel failure and won’t load into the os. >>> Glad you got your other computer working at least! So on this one, where are you getting this kernel failure exactly? If it's booting to dom0, I'm not following where you're having trouble. There's a message on boot about failed to load kernel modules that can be safely ignored. To update dom0, you want to use "sudo qubes-dom0-update". You should rarely need to update the kernel by itself. Is that when you are getting the PCI reset error? Is your sys-net started? Check in Qube Manager. Then, check sys-net's Qube Settings/Devices to see what's attached there and if 03:00.2 is one of the devices. If so, see what it is. --
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
Ok back with the laptop. During boot up, dom0 green state, sys-net green state. WiFi connection good, and can reboot! Lol But with that said nothing else auto loads. I have to start fedora-26 and it will. When trying to start sys-firewall I get error ( PCI device 02:00.0 is in use by driver xenlight domain sys-net Log: /var/log/libvirt/libxl/libxl-driver.log I don’t see this log listed with sys-net, there are no logs with sys-firewall. I don’t see this listed in the Qubes log either. I have looked up help, but others have usb issues. I don’t have any attached and not trying to do anything with them as stated . I tried command qvm-pci attach —persistent —option permissive=True —option no-strict-reset But I’m missing something so it’s not working. I’m in the right direction? I need to reset pci and set no restrictions? On Wed, Nov 7, 2018 at 9:32 PM LMiller M <56lmil...@gmail.com> wrote: > Ok so I figured out how to see the logs. > > I have been able to figure out why the laptop wasn’t responding to the OS > correctly. Now it’s working and updating as needed. > > I will explain more as I learn more. > > I do appreciate the guidance. I think there is more that can be shown, to > help newbies. > > I’m going to put something together from my view point to see if you all > agree. Maybe it can be useful to all new qube users like me. Lol anyway, I > wouldn’t have figured it out as fast for myself with out your help. > > Thank you for helping me. > > I’m still figuring things out, but this build is awesome and so much to > learn with it. > On Tue, Nov 6, 2018 at 4:43 PM LMiller M <56lmil...@gmail.com> wrote: > >> Ok on first boot after install Qubes will show the kernel failure and >> bypass and boot into dom0. >> >> Once there, in the Qubes manager dom0 has green state. >> >> Lol ok don’t laugh too hard. So I checked devices like have been, sys-net >> as you mentioned. Both Ethernet and WiFi devices are there. So I just >> removed my Ethernet from device selection and bingo sys-net green state! >> >> So I will try now to run system updates for dom0 and fedora. >> >> Thanks again for point things out. Sometimes you look at something so >> crazy and just need a second thought. >> >> So, can you show me how to check logs if I run into issues? Lol please >> and thanks >> On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users < >> qubes-users@googlegroups.com> wrote: >> >>> >>> LMiller M: >>> > Update: Kernel failure during boot install OS 4.0 >>> > >>> > After the install booted into dom0, checking Qubes kernel package to >>> see >>> > what three were stored or available. Mine only list one kernel. >>> > >>> > 4.14.18-1 >>> > >>> > I checked using the rpm -qa ‘kernel-Qubes-vm*’ >>> > >>> > Using the install update option I get: >>> > >>> > Unable to reset pci device :03:00.2: >>> > >>> > Trying to apply the device to the selected box: error: device tab: >>> can’t >>> > attach pci device to VM in pvh mode >>> > >>> > Does that mode need to be changed? >>> > >>> > Stupid question but because honestly I don’t know. How do you check the >>> > logs? I’m the terminal? >>> > >>> > I downloaded the new kernel to cd, can install from the cd? I don’t see >>> > anything on the Qubes kernel page except download from internet throw >>> > Qubes. With internet I can’t. >>> > >>> > >>> > On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com> wrote: >>> > >>> >> So, after looking more into the kernel issue. I see on the Qubes site >>> some >>> >> instructions for trying to change the kernel. I’m going to do a >>> reinstall >>> >> of the 4.0 os to get back into Dom0 and try it out. I will post back >>> >> hopefully with success.. >>> >> On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com> wrote: >>> >> >>> >>> Ok so one more if I can please, this is on a Asus K56c laptop and it >>> has >>> >>> a kernel failure on boot with Qubes Os 4.0. On the first install it >>> shows >>> >>> the kernel failure and it boots to the OS don0. If I turn off or >>> reboot it >>> >>> shows my kernel failure and won’t load into the os. >>> >>> >>> Glad you got your other computer working at least! So on this one, where >>> are you getting this kernel failure exactly? If it's booting to dom0, >>> I'm not following where you're having trouble. There's a message on boot >>> about failed to load kernel modules that can be safely ignored. >>> >>> To update dom0, you want to use "sudo qubes-dom0-update". You should >>> rarely need to update the kernel by itself. >>> >>> Is that when you are getting the PCI reset error? Is your sys-net >>> started? Check in Qube Manager. Then, check sys-net's Qube >>> Settings/Devices to see what's attached there and if 03:00.2 is one of >>> the devices. If so, see what it is. >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "qubes-users" group. >>> To unsubscribe from this topic, visit >>>
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
Ok so I figured out how to see the logs. I have been able to figure out why the laptop wasn’t responding to the OS correctly. Now it’s working and updating as needed. I will explain more as I learn more. I do appreciate the guidance. I think there is more that can be shown, to help newbies. I’m going to put something together from my view point to see if you all agree. Maybe it can be useful to all new qube users like me. Lol anyway, I wouldn’t have figured it out as fast for myself with out your help. Thank you for helping me. I’m still figuring things out, but this build is awesome and so much to learn with it. On Tue, Nov 6, 2018 at 4:43 PM LMiller M <56lmil...@gmail.com> wrote: > Ok on first boot after install Qubes will show the kernel failure and > bypass and boot into dom0. > > Once there, in the Qubes manager dom0 has green state. > > Lol ok don’t laugh too hard. So I checked devices like have been, sys-net > as you mentioned. Both Ethernet and WiFi devices are there. So I just > removed my Ethernet from device selection and bingo sys-net green state! > > So I will try now to run system updates for dom0 and fedora. > > Thanks again for point things out. Sometimes you look at something so > crazy and just need a second thought. > > So, can you show me how to check logs if I run into issues? Lol please and > thanks > On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users < > qubes-users@googlegroups.com> wrote: > >> >> LMiller M: >> > Update: Kernel failure during boot install OS 4.0 >> > >> > After the install booted into dom0, checking Qubes kernel package to see >> > what three were stored or available. Mine only list one kernel. >> > >> > 4.14.18-1 >> > >> > I checked using the rpm -qa ‘kernel-Qubes-vm*’ >> > >> > Using the install update option I get: >> > >> > Unable to reset pci device :03:00.2: >> > >> > Trying to apply the device to the selected box: error: device tab: can’t >> > attach pci device to VM in pvh mode >> > >> > Does that mode need to be changed? >> > >> > Stupid question but because honestly I don’t know. How do you check the >> > logs? I’m the terminal? >> > >> > I downloaded the new kernel to cd, can install from the cd? I don’t see >> > anything on the Qubes kernel page except download from internet throw >> > Qubes. With internet I can’t. >> > >> > >> > On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com> wrote: >> > >> >> So, after looking more into the kernel issue. I see on the Qubes site >> some >> >> instructions for trying to change the kernel. I’m going to do a >> reinstall >> >> of the 4.0 os to get back into Dom0 and try it out. I will post back >> >> hopefully with success.. >> >> On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com> wrote: >> >> >> >>> Ok so one more if I can please, this is on a Asus K56c laptop and it >> has >> >>> a kernel failure on boot with Qubes Os 4.0. On the first install it >> shows >> >>> the kernel failure and it boots to the OS don0. If I turn off or >> reboot it >> >>> shows my kernel failure and won’t load into the os. >> >>> >> Glad you got your other computer working at least! So on this one, where >> are you getting this kernel failure exactly? If it's booting to dom0, >> I'm not following where you're having trouble. There's a message on boot >> about failed to load kernel modules that can be safely ignored. >> >> To update dom0, you want to use "sudo qubes-dom0-update". You should >> rarely need to update the kernel by itself. >> >> Is that when you are getting the PCI reset error? Is your sys-net >> started? Check in Qube Manager. Then, check sys-net's Qube >> Settings/Devices to see what's attached there and if 03:00.2 is one of >> the devices. If so, see what it is. >> >> -- >> 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/sEh2LQFiOxI/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/326f794c-5658-c3bb-a8c7-7ed43b1d63ee%40danwin1210.me >> . >> 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/CAOugA3rZoq%3Dhzr9JXrpA%2BahwzTPfY2qSKB9EKeY%2BSTGL%3DJ-mQw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
Ok on first boot after install Qubes will show the kernel failure and bypass and boot into dom0. Once there, in the Qubes manager dom0 has green state. Lol ok don’t laugh too hard. So I checked devices like have been, sys-net as you mentioned. Both Ethernet and WiFi devices are there. So I just removed my Ethernet from device selection and bingo sys-net green state! So I will try now to run system updates for dom0 and fedora. Thanks again for point things out. Sometimes you look at something so crazy and just need a second thought. So, can you show me how to check logs if I run into issues? Lol please and thanks On Tue, Nov 6, 2018 at 4:09 PM 'awokd' via qubes-users < qubes-users@googlegroups.com> wrote: > > LMiller M: > > Update: Kernel failure during boot install OS 4.0 > > > > After the install booted into dom0, checking Qubes kernel package to see > > what three were stored or available. Mine only list one kernel. > > > > 4.14.18-1 > > > > I checked using the rpm -qa ‘kernel-Qubes-vm*’ > > > > Using the install update option I get: > > > > Unable to reset pci device :03:00.2: > > > > Trying to apply the device to the selected box: error: device tab: can’t > > attach pci device to VM in pvh mode > > > > Does that mode need to be changed? > > > > Stupid question but because honestly I don’t know. How do you check the > > logs? I’m the terminal? > > > > I downloaded the new kernel to cd, can install from the cd? I don’t see > > anything on the Qubes kernel page except download from internet throw > > Qubes. With internet I can’t. > > > > > > On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com> wrote: > > > >> So, after looking more into the kernel issue. I see on the Qubes site > some > >> instructions for trying to change the kernel. I’m going to do a > reinstall > >> of the 4.0 os to get back into Dom0 and try it out. I will post back > >> hopefully with success.. > >> On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com> wrote: > >> > >>> Ok so one more if I can please, this is on a Asus K56c laptop and it > has > >>> a kernel failure on boot with Qubes Os 4.0. On the first install it > shows > >>> the kernel failure and it boots to the OS don0. If I turn off or > reboot it > >>> shows my kernel failure and won’t load into the os. > >>> > Glad you got your other computer working at least! So on this one, where > are you getting this kernel failure exactly? If it's booting to dom0, > I'm not following where you're having trouble. There's a message on boot > about failed to load kernel modules that can be safely ignored. > > To update dom0, you want to use "sudo qubes-dom0-update". You should > rarely need to update the kernel by itself. > > Is that when you are getting the PCI reset error? Is your sys-net > started? Check in Qube Manager. Then, check sys-net's Qube > Settings/Devices to see what's attached there and if 03:00.2 is one of > the devices. If so, see what it is. > > -- > 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/sEh2LQFiOxI/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/326f794c-5658-c3bb-a8c7-7ed43b1d63ee%40danwin1210.me > . > 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/CAOugA3paUbTFaWvTxW%2BM%2Bnb0yX9QbTR%3D5qmqpRuuBBeH70OTng%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
LMiller M: Update: Kernel failure during boot install OS 4.0 After the install booted into dom0, checking Qubes kernel package to see what three were stored or available. Mine only list one kernel. 4.14.18-1 I checked using the rpm -qa ‘kernel-Qubes-vm*’ Using the install update option I get: Unable to reset pci device :03:00.2: Trying to apply the device to the selected box: error: device tab: can’t attach pci device to VM in pvh mode Does that mode need to be changed? Stupid question but because honestly I don’t know. How do you check the logs? I’m the terminal? I downloaded the new kernel to cd, can install from the cd? I don’t see anything on the Qubes kernel page except download from internet throw Qubes. With internet I can’t. On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com> wrote: So, after looking more into the kernel issue. I see on the Qubes site some instructions for trying to change the kernel. I’m going to do a reinstall of the 4.0 os to get back into Dom0 and try it out. I will post back hopefully with success.. On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com> wrote: Ok so one more if I can please, this is on a Asus K56c laptop and it has a kernel failure on boot with Qubes Os 4.0. On the first install it shows the kernel failure and it boots to the OS don0. If I turn off or reboot it shows my kernel failure and won’t load into the os. Glad you got your other computer working at least! So on this one, where are you getting this kernel failure exactly? If it's booting to dom0, I'm not following where you're having trouble. There's a message on boot about failed to load kernel modules that can be safely ignored. To update dom0, you want to use "sudo qubes-dom0-update". You should rarely need to update the kernel by itself. Is that when you are getting the PCI reset error? Is your sys-net started? Check in Qube Manager. Then, check sys-net's Qube Settings/Devices to see what's attached there and if 03:00.2 is one of the devices. If so, see what it is. -- 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/326f794c-5658-c3bb-a8c7-7ed43b1d63ee%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
Update: Kernel failure during boot install OS 4.0 After the install booted into dom0, checking Qubes kernel package to see what three were stored or available. Mine only list one kernel. 4.14.18-1 I checked using the rpm -qa ‘kernel-Qubes-vm*’ Using the install update option I get: Unable to reset pci device :03:00.2: Trying to apply the device to the selected box: error: device tab: can’t attach pci device to VM in pvh mode Does that mode need to be changed? Stupid question but because honestly I don’t know. How do you check the logs? I’m the terminal? I downloaded the new kernel to cd, can install from the cd? I don’t see anything on the Qubes kernel page except download from internet throw Qubes. With internet I can’t. On Tue, Nov 6, 2018 at 10:39 AM LMiller M <56lmil...@gmail.com> wrote: > So, after looking more into the kernel issue. I see on the Qubes site some > instructions for trying to change the kernel. I’m going to do a reinstall > of the 4.0 os to get back into Dom0 and try it out. I will post back > hopefully with success.. > On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com> wrote: > >> Ok so one more if I can please, this is on a Asus K56c laptop and it has >> a kernel failure on boot with Qubes Os 4.0. On the first install it shows >> the kernel failure and it boots to the OS don0. If I turn off or reboot it >> shows my kernel failure and won’t load into the os. >> >> I seen something saying I should be able to change the kernel (maybe >> during the install) don’t remember. I found the kernels on the Qubes site >> that are excepted, I just don’t see how the change it. Maybe I’m >> overlooking, I’m not a major Linux person. I know a small bit of ubantu >> >> In this Asus I have the Acronis Loader, I don’t think that has anything >> to do with it. Just putting it out there. >> >> Qubes OS is the only os install on this laptop drive. All virtual options >> are enabled. Boots to my login password then stalls. >> >> Any ideas? >> On Mon, Nov 5, 2018 at 7:37 PM LMiller M <56lmil...@gmail.com> wrote: >> >>> I want to thank you both. Sorry for the late reply I wasn’t able to make >>> the necessary adjustments till now. >>> >>> I feel like a fool, I didn’t think about treating my desktop as a >>> virtual box fresh install. Which completely makes sense because of the >>> Qubes basic idea of the OS! Lol omg... >>> >>> Anyway, seeing there is nothing explaining this. This is the fix for the >>> issue I had with installing 4.0 os and having that main install error. >>> After setting both virtual options in the PC bios everything loaded as >>> needed on reboot. Network connection connected on boot-up. Everything works >>> fine! >>> >>> Thank you and I look forward to being apart the Qubes community! Amazing >>> OS! >>> On Sat, Nov 3, 2018 at 11:57 AM 'awokd' via qubes-users < >>> qubes-users@googlegroups.com> wrote: >>> LMiller M: > Ok doing some research about this as much as I can learn about. I’m redoing > the os 4.0 install. I got the warning that my machine doesn’t have > HVM/VT-x/amd-v. Link from Qubes site. Basically no vms will work with > anything. Can you help explain how I’m supposed virt-type to PV? Or should > I just install the os 3.2? Enable the virtualization options in your BIOS setup. > The main problem I was having was. After running lookup qvm-pci I see my > devices fine. The nic card shows up in the listing. In the network > connections add connection. Everything is grayed out can’t add anything no > vms work 1) Enabling virtualization may fix your sys-net issue. 2) You shouldn't have to add connections manually in most cases. What does connection info say? 3) Like unman said, switch sys-net to use the Debian template (shut sys-net down and change in Qube Setting/General tab). 4) If that doesn't fix it, see if your NIC needs additional firmware, then install that to the template you use for sys-net. -- 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/sEh2LQFiOxI/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/629219b4-1dd6-f9dc-2bd3-805825a02116%40danwin1210.me . 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
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
So, after looking more into the kernel issue. I see on the Qubes site some instructions for trying to change the kernel. I’m going to do a reinstall of the 4.0 os to get back into Dom0 and try it out. I will post back hopefully with success.. On Mon, Nov 5, 2018 at 8:02 PM LMiller M <56lmil...@gmail.com> wrote: > Ok so one more if I can please, this is on a Asus K56c laptop and it has a > kernel failure on boot with Qubes Os 4.0. On the first install it shows the > kernel failure and it boots to the OS don0. If I turn off or reboot it > shows my kernel failure and won’t load into the os. > > I seen something saying I should be able to change the kernel (maybe > during the install) don’t remember. I found the kernels on the Qubes site > that are excepted, I just don’t see how the change it. Maybe I’m > overlooking, I’m not a major Linux person. I know a small bit of ubantu > > In this Asus I have the Acronis Loader, I don’t think that has anything to > do with it. Just putting it out there. > > Qubes OS is the only os install on this laptop drive. All virtual options > are enabled. Boots to my login password then stalls. > > Any ideas? > On Mon, Nov 5, 2018 at 7:37 PM LMiller M <56lmil...@gmail.com> wrote: > >> I want to thank you both. Sorry for the late reply I wasn’t able to make >> the necessary adjustments till now. >> >> I feel like a fool, I didn’t think about treating my desktop as a virtual >> box fresh install. Which completely makes sense because of the Qubes basic >> idea of the OS! Lol omg... >> >> Anyway, seeing there is nothing explaining this. This is the fix for the >> issue I had with installing 4.0 os and having that main install error. >> After setting both virtual options in the PC bios everything loaded as >> needed on reboot. Network connection connected on boot-up. Everything works >> fine! >> >> Thank you and I look forward to being apart the Qubes community! Amazing >> OS! >> On Sat, Nov 3, 2018 at 11:57 AM 'awokd' via qubes-users < >> qubes-users@googlegroups.com> wrote: >> >>> LMiller M: >>> > Ok doing some research about this as much as I can learn about. I’m >>> redoing >>> > the os 4.0 install. I got the warning that my machine doesn’t have >>> > HVM/VT-x/amd-v. Link from Qubes site. Basically no vms will work with >>> > anything. Can you help explain how I’m supposed virt-type to PV? Or >>> should >>> > I just install the os 3.2? >>> >>> Enable the virtualization options in your BIOS setup. >>> >>> > The main problem I was having was. After running lookup qvm-pci I see >>> my >>> > devices fine. The nic card shows up in the listing. In the network >>> > connections add connection. Everything is grayed out can’t add >>> anything no >>> > vms work >>> >>> 1) Enabling virtualization may fix your sys-net issue. >>> 2) You shouldn't have to add connections manually in most cases. What >>> does connection info say? >>> 3) Like unman said, switch sys-net to use the Debian template (shut >>> sys-net down and change in Qube Setting/General tab). >>> 4) If that doesn't fix it, see if your NIC needs additional firmware, >>> then install that to the template you use for sys-net. >>> >>> -- >>> 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/sEh2LQFiOxI/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/629219b4-1dd6-f9dc-2bd3-805825a02116%40danwin1210.me >>> . >>> 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/CAOugA3oGWKmMzyAU0eteLiGTjfcAvj1LwrLT7%3Dw8wqxH2-EggA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
Ok so one more if I can please, this is on a Asus K56c laptop and it has a kernel failure on boot with Qubes Os 4.0. On the first install it shows the kernel failure and it boots to the OS don0. If I turn off or reboot it shows my kernel failure and won’t load into the os. I seen something saying I should be able to change the kernel (maybe during the install) don’t remember. I found the kernels on the Qubes site that are excepted, I just don’t see how the change it. Maybe I’m overlooking, I’m not a major Linux person. I know a small bit of ubantu In this Asus I have the Acronis Loader, I don’t think that has anything to do with it. Just putting it out there. Qubes OS is the only os install on this laptop drive. All virtual options are enabled. Boots to my login password then stalls. Any ideas? On Mon, Nov 5, 2018 at 7:37 PM LMiller M <56lmil...@gmail.com> wrote: > I want to thank you both. Sorry for the late reply I wasn’t able to make > the necessary adjustments till now. > > I feel like a fool, I didn’t think about treating my desktop as a virtual > box fresh install. Which completely makes sense because of the Qubes basic > idea of the OS! Lol omg... > > Anyway, seeing there is nothing explaining this. This is the fix for the > issue I had with installing 4.0 os and having that main install error. > After setting both virtual options in the PC bios everything loaded as > needed on reboot. Network connection connected on boot-up. Everything works > fine! > > Thank you and I look forward to being apart the Qubes community! Amazing > OS! > On Sat, Nov 3, 2018 at 11:57 AM 'awokd' via qubes-users < > qubes-users@googlegroups.com> wrote: > >> LMiller M: >> > Ok doing some research about this as much as I can learn about. I’m >> redoing >> > the os 4.0 install. I got the warning that my machine doesn’t have >> > HVM/VT-x/amd-v. Link from Qubes site. Basically no vms will work with >> > anything. Can you help explain how I’m supposed virt-type to PV? Or >> should >> > I just install the os 3.2? >> >> Enable the virtualization options in your BIOS setup. >> >> > The main problem I was having was. After running lookup qvm-pci I see my >> > devices fine. The nic card shows up in the listing. In the network >> > connections add connection. Everything is grayed out can’t add anything >> no >> > vms work >> >> 1) Enabling virtualization may fix your sys-net issue. >> 2) You shouldn't have to add connections manually in most cases. What >> does connection info say? >> 3) Like unman said, switch sys-net to use the Debian template (shut >> sys-net down and change in Qube Setting/General tab). >> 4) If that doesn't fix it, see if your NIC needs additional firmware, >> then install that to the template you use for sys-net. >> >> -- >> 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/sEh2LQFiOxI/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/629219b4-1dd6-f9dc-2bd3-805825a02116%40danwin1210.me >> . >> 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/CAOugA3q3rrRrjH9iVjYz1kcRrp%3DS1YPp4AgS2auabcrOu0Rbcg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
I want to thank you both. Sorry for the late reply I wasn’t able to make the necessary adjustments till now. I feel like a fool, I didn’t think about treating my desktop as a virtual box fresh install. Which completely makes sense because of the Qubes basic idea of the OS! Lol omg... Anyway, seeing there is nothing explaining this. This is the fix for the issue I had with installing 4.0 os and having that main install error. After setting both virtual options in the PC bios everything loaded as needed on reboot. Network connection connected on boot-up. Everything works fine! Thank you and I look forward to being apart the Qubes community! Amazing OS! On Sat, Nov 3, 2018 at 11:57 AM 'awokd' via qubes-users < qubes-users@googlegroups.com> wrote: > LMiller M: > > Ok doing some research about this as much as I can learn about. I’m > redoing > > the os 4.0 install. I got the warning that my machine doesn’t have > > HVM/VT-x/amd-v. Link from Qubes site. Basically no vms will work with > > anything. Can you help explain how I’m supposed virt-type to PV? Or > should > > I just install the os 3.2? > > Enable the virtualization options in your BIOS setup. > > > The main problem I was having was. After running lookup qvm-pci I see my > > devices fine. The nic card shows up in the listing. In the network > > connections add connection. Everything is grayed out can’t add anything > no > > vms work > > 1) Enabling virtualization may fix your sys-net issue. > 2) You shouldn't have to add connections manually in most cases. What > does connection info say? > 3) Like unman said, switch sys-net to use the Debian template (shut > sys-net down and change in Qube Setting/General tab). > 4) If that doesn't fix it, see if your NIC needs additional firmware, > then install that to the template you use for sys-net. > > -- > 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/sEh2LQFiOxI/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/629219b4-1dd6-f9dc-2bd3-805825a02116%40danwin1210.me > . > 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/CAOugA3rs-dCfHZwH4rLJWNK8uASiNwdA_jaYciM9ObbedFyHOw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
LMiller M: Ok doing some research about this as much as I can learn about. I’m redoing the os 4.0 install. I got the warning that my machine doesn’t have HVM/VT-x/amd-v. Link from Qubes site. Basically no vms will work with anything. Can you help explain how I’m supposed virt-type to PV? Or should I just install the os 3.2? Enable the virtualization options in your BIOS setup. The main problem I was having was. After running lookup qvm-pci I see my devices fine. The nic card shows up in the listing. In the network connections add connection. Everything is grayed out can’t add anything no vms work 1) Enabling virtualization may fix your sys-net issue. 2) You shouldn't have to add connections manually in most cases. What does connection info say? 3) Like unman said, switch sys-net to use the Debian template (shut sys-net down and change in Qube Setting/General tab). 4) If that doesn't fix it, see if your NIC needs additional firmware, then install that to the template you use for sys-net. -- 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/629219b4-1dd6-f9dc-2bd3-805825a02116%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
Ok doing some research about this as much as I can learn about. I’m redoing the os 4.0 install. I got the warning that my machine doesn’t have HVM/VT-x/amd-v. Link from Qubes site. Basically no vms will work with anything. Can you help explain how I’m supposed virt-type to PV? Or should I just install the os 3.2? The main problem I was having was. After running lookup qvm-pci I see my devices fine. The nic card shows up in the listing. In the network connections add connection. Everything is grayed out can’t add anything no vms work https://github.com/QubesOS/qubes-issues/issues/3208 On Fri, Nov 2, 2018 at 12:17 PM unman wrote: > On Fri, Nov 02, 2018 at 07:43:00AM -0700, lifestyle wrote: > > On Friday, November 2, 2018 at 10:33:04 AM UTC-4, unman wrote: > > > On Fri, Nov 02, 2018 at 05:53:15AM -0700, 56lmil...@gmail.com wrote: > > > > On Monday, June 26, 2017 at 12:41:36 PM UTC-4, helpp...@vfemail.net > wrote: > > > > > THIS CONCERNS QUBES 3.2 (latest update, downloaded from the > website 3 > > > > > days ago). > > > > > > > > No Network Connection: Qubes Os 4.0 - HP z230 desktop > > > > hello everyone, there is really not much help on this os version. I > need some assistance please. As i have read this persons post that loves > (!!!) i have been able to see a few things that has helped. > > > > > > > > With my desktop, sys-net has no connection and does see the nic. > When I open the network connection dialog, i'm asked to add connection. > when I select add, choose either. the next page is fully grayed out, can't > select anything. there are no errors that come up when booted. > > > > > > > > > I see that I can use a usb wifi stick. but with that said, i need to > be able to install a fix to get it to work. is that a true statement? > > > > > > > > assistance would be greatly appreciated. > > > > > > > > > > Nothing like a bit of necrophilia. > > > > > > The fact that sys-net does not see the NIC suggests that you are > missing > > > some drivers. Review the boot log in sys-net, and you may see the > > > problem. > > > > > > What card do you have in there? I cant see the spec from the HP site. > > > You could try changing the temaplet for sys-net to Debian instead of > > > Fedora, and see if the right drivers are loaded. > > > > > > I',m not sure what you mean bu "install a fix" - if you use a supported > > > wifi stick, then it should load without further trouble. If you need > > > further drivers for that, then yes, you will need to install them. > > > If you do need drivers then you will have to download them on a > > > different machine or using alive disk. > > > > hello and thank you for the response. i apologize, i meant sysnet sees > the nic device. the nic is intel(r) i217-LM > > > > What you mention about the usb wifi stick loading with out trouble makes > sense. I will check the sys-net log. > > > > most of the support I have seen is mainly for os verion 3.2. I seen > someone mention that if you use a usb wifi stick that you had to build a > cube for it and set a passthrough for it. > > > > Hello > > Check the logs in sys-net, as you say. Post back with any problems that > you see there. > Try using a Debian based sys-net, and see if that helps. > > As to use of wifi, this will depend on whether you have a USBqube set up > (sys-usb), and what ports/connectors you have available. > If you have multiple connectors, then you can connect 1 directly to > sys-net, and the rest to sys-usb. If you only have 1, then you will have > to try USB pass-through. That isnt difficult but again, check the lists > for reports of problems with particular devices. > > best of luck > > unman > > -- > 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/sEh2LQFiOxI/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/20181102161712.5hwxd7mngqc4luyr%40thirdeyesecurity.org > . > 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/CAOugA3o3p4zxu6ed5iQ-U9DO8ov0ZxKK8fmU3Cm6FxHUY9kWiA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
On Fri, Nov 02, 2018 at 07:43:00AM -0700, lifestyle wrote: > On Friday, November 2, 2018 at 10:33:04 AM UTC-4, unman wrote: > > On Fri, Nov 02, 2018 at 05:53:15AM -0700, 56lmil...@gmail.com wrote: > > > On Monday, June 26, 2017 at 12:41:36 PM UTC-4, helpp...@vfemail.net wrote: > > > > THIS CONCERNS QUBES 3.2 (latest update, downloaded from the website 3 > > > > days ago). > > > > > > No Network Connection: Qubes Os 4.0 - HP z230 desktop > > > hello everyone, there is really not much help on this os version. I need > > > some assistance please. As i have read this persons post that loves > > > (!!!) i have been able to see a few things that has helped. > > > > > > With my desktop, sys-net has no connection and does see the nic. When I > > > open the network connection dialog, i'm asked to add connection. when I > > > select add, choose either. the next page is fully grayed out, can't > > > select anything. there are no errors that come up when booted. > > > > > > I see that I can use a usb wifi stick. but with that said, i need to be > > > able to install a fix to get it to work. is that a true statement? > > > > > > assistance would be greatly appreciated. > > > > > > > Nothing like a bit of necrophilia. > > > > The fact that sys-net does not see the NIC suggests that you are missing > > some drivers. Review the boot log in sys-net, and you may see the > > problem. > > > > What card do you have in there? I cant see the spec from the HP site. > > You could try changing the temaplet for sys-net to Debian instead of > > Fedora, and see if the right drivers are loaded. > > > > I',m not sure what you mean bu "install a fix" - if you use a supported > > wifi stick, then it should load without further trouble. If you need > > further drivers for that, then yes, you will need to install them. > > If you do need drivers then you will have to download them on a > > different machine or using alive disk. > > hello and thank you for the response. i apologize, i meant sysnet sees the > nic device. the nic is intel(r) i217-LM > > What you mention about the usb wifi stick loading with out trouble makes > sense. I will check the sys-net log. > > most of the support I have seen is mainly for os verion 3.2. I seen someone > mention that if you use a usb wifi stick that you had to build a cube for it > and set a passthrough for it. > Hello Check the logs in sys-net, as you say. Post back with any problems that you see there. Try using a Debian based sys-net, and see if that helps. As to use of wifi, this will depend on whether you have a USBqube set up (sys-usb), and what ports/connectors you have available. If you have multiple connectors, then you can connect 1 directly to sys-net, and the rest to sys-usb. If you only have 1, then you will have to try USB pass-through. That isnt difficult but again, check the lists for reports of problems with particular devices. best of luck unman -- 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/20181102161712.5hwxd7mngqc4luyr%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
On Friday, November 2, 2018 at 10:33:04 AM UTC-4, unman wrote: > On Fri, Nov 02, 2018 at 05:53:15AM -0700, 56lmil...@gmail.com wrote: > > On Monday, June 26, 2017 at 12:41:36 PM UTC-4, helpp...@vfemail.net wrote: > > > THIS CONCERNS QUBES 3.2 (latest update, downloaded from the website 3 > > > days ago). > > > > No Network Connection: Qubes Os 4.0 - HP z230 desktop > > hello everyone, there is really not much help on this os version. I need > > some assistance please. As i have read this persons post that loves (!!!) > > i have been able to see a few things that has helped. > > > > With my desktop, sys-net has no connection and does see the nic. When I > > open the network connection dialog, i'm asked to add connection. when I > > select add, choose either. the next page is fully grayed out, can't select > > anything. there are no errors that come up when booted. > > > > I see that I can use a usb wifi stick. but with that said, i need to be > > able to install a fix to get it to work. is that a true statement? > > > > assistance would be greatly appreciated. > > > > Nothing like a bit of necrophilia. > > The fact that sys-net does not see the NIC suggests that you are missing > some drivers. Review the boot log in sys-net, and you may see the > problem. > > What card do you have in there? I cant see the spec from the HP site. > You could try changing the temaplet for sys-net to Debian instead of > Fedora, and see if the right drivers are loaded. > > I',m not sure what you mean bu "install a fix" - if you use a supported > wifi stick, then it should load without further trouble. If you need > further drivers for that, then yes, you will need to install them. > If you do need drivers then you will have to download them on a > different machine or using alive disk. hello and thank you for the response. i apologize, i meant sysnet sees the nic device. the nic is intel(r) i217-LM What you mention about the usb wifi stick loading with out trouble makes sense. I will check the sys-net log. most of the support I have seen is mainly for os verion 3.2. I seen someone mention that if you use a usb wifi stick that you had to build a cube for it and set a passthrough for it. -- 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/cc3b29ce-3c18-4f4c-aa50-b30ff4f9f0d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
On Fri, Nov 02, 2018 at 05:53:15AM -0700, 56lmil...@gmail.com wrote: > On Monday, June 26, 2017 at 12:41:36 PM UTC-4, helpp...@vfemail.net wrote: > > THIS CONCERNS QUBES 3.2 (latest update, downloaded from the website 3 > > days ago). > > No Network Connection: Qubes Os 4.0 - HP z230 desktop > hello everyone, there is really not much help on this os version. I need some > assistance please. As i have read this persons post that loves (!!!) i have > been able to see a few things that has helped. > > With my desktop, sys-net has no connection and does see the nic. When I open > the network connection dialog, i'm asked to add connection. when I select > add, choose either. the next page is fully grayed out, can't select > anything. there are no errors that come up when booted. > > I see that I can use a usb wifi stick. but with that said, i need to be able > to install a fix to get it to work. is that a true statement? > > assistance would be greatly appreciated. > Nothing like a bit of necrophilia. The fact that sys-net does not see the NIC suggests that you are missing some drivers. Review the boot log in sys-net, and you may see the problem. What card do you have in there? I cant see the spec from the HP site. You could try changing the temaplet for sys-net to Debian instead of Fedora, and see if the right drivers are loaded. I',m not sure what you mean bu "install a fix" - if you use a supported wifi stick, then it should load without further trouble. If you need further drivers for that, then yes, you will need to install them. If you do need drivers then you will have to download them on a different machine or using alive disk. -- 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/20181102143221.mf4fr37wshcife5s%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!
On Monday, June 26, 2017 at 12:41:36 PM UTC-4, helpp...@vfemail.net wrote: > THIS CONCERNS QUBES 3.2 (latest update, downloaded from the website 3 > days ago). No Network Connection: Qubes Os 4.0 - HP z230 desktop hello everyone, there is really not much help on this os version. I need some assistance please. As i have read this persons post that loves (!!!) i have been able to see a few things that has helped. With my desktop, sys-net has no connection and does see the nic. When I open the network connection dialog, i'm asked to add connection. when I select add, choose either. the next page is fully grayed out, can't select anything. there are no errors that come up when booted. I see that I can use a usb wifi stick. but with that said, i need to be able to install a fix to get it to work. is that a true statement? assistance would be greatly appreciated. -- 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/1c08560d-bc9b-4708-b707-b3cc0387ee12%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
