[qubes-users] Re: syncing config across qubes

2018-09-20 Thread bbrr3332
On Friday, September 14, 2018 at 10:31:26 PM UTC+1, daniel wrote:
> Dear all,
> 
> I am wondering how you all deal with (for example) having an elaborate vim
> or emacs environment built up over several decades, and being able
> to use it in all of your regular everyday qubes (personal, work, untrusted, 
> etc,
> probably leave vault out).  Of course, you expect it to keep evolving as you
> figure out how some package solves a problem for you, or you write some
> vimscript or elisp to stop an annoyance.
> 
> What is the qubes way to do this?  I've considered several solutions from
> the simple to the baroque:
> 
> (simple) do the common config in the template vm (but not in /home
> or /rw or /usr/local) and replace the relevant config files/dirs in the 
> actual-work
> vm's with symlinks to them.
> 
> (also simple) have a "config" qube where you keep the configs you want to 
> sync,
> but do no actual work there and have no net access.  Set up a script to copy 
> the relevant files/dirs to your working qubes.  When you find an annoyance, 
> fix it there, and then run the script.
> 
> (rather complicated) set up a git server (say in its own dvm)
> and have your qubes push commits to it when
> you make changes to one of the files-to-sync.  That way you can make your
> tweaks wherever you happen to be working at the time, and later accept 
> those changes on the server.  Then you can download the updated version
> on your working qubes (perhaps by a script).
> 
> All of these have different convenience levels and data-flow implications.
> But I feel like maybe they are all wrong and I am overlooking something 
> obvious.  Any thoughts appreciated!
> Daniel

You can make use of git without a server:

qvm-run -p VMa "git -C /home/user/config bundle create - " | qvm-run 
-p VMb "cat > /tmp/VMa.bundle"

and setup a pull on VM from /tmp/VMa bundle and vv. Easy to automate to 
reasonable comfort level with a simple script in dom0

-- 
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/4cddaf7e-f9e6-44b4-b47b-ff5c736cbfb7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] HCL - Lenovo Thinkpad T480

2018-09-07 Thread bbrr3332
On Thursday, August 23, 2018 at 2:03:55 PM UTC+1, sagi-qub...@rtsn.nl wrote:
> Hi,
> 
> On 2018-04-14 23:13, bbrr3...@gmail.com wrote:
> > System basically works nicely out of the box with Q4.0. I recommend 
> > the laptop.
> 
> That is my experience as well, save for your next point.
> 
> > The only glitch was consistent crash when resuming from suspend. I 
> > debugged by shutting down service vm's and narrowed it down to 
> > sys-usb. Then detached the second USB controller from sys-usb and 
> > everything seems to work fine.  I did not seem to loose any 
> > devices/ports doing this but did not do an exhaustive test. 
> 
> You may want to track and/or contribute to:
> https://github.com/QubesOS/qubes-issues/issues/3689
> https://github.com/QubesOS/qubes-issues/issues/3705
> 
> In any case, I'd be interested to hear the details of your workaround.

As far as I recall it was simply:

qvm-pci detach sys-usb dom0:3c_00.0

This is the production machine now so can't investigate things further 

-- 
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/e219f65f-5afd-4637-b5ed-5f3e83b4e8d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Lenovo T480 freezes after resume on suspend

2018-05-16 Thread bbrr3332
On Tuesday, May 8, 2018 at 6:51:32 PM UTC+1, mau...@disroot.org wrote:
> I'm also experiencing the same issue.
> Whenever my laptop resumes after have being suspended, the sys-usb is frozen 
> and all USB devices attached to it fail to work. I have to kill the appvm and 
> start it again. This only affects the sys-usb though, the sys-net is working 
> fine during the resume.
> The issue that describes this problem - 
> https://github.com/QubesOS/qubes-issues/issues/3142  - was closed but the 
> problem still persists.
> 
> Any idea how can we resolve this?

Fully working T480 with Qubes 4.0 writing here. I found I needed to remove the 
assignement of one of the USB controllers from sys-usb. See earlier HCL.  My 
debug strategy was to shutdown all service VMs and check if suspend works , 
then narrow the issue.

Note that on my machine it takes about 5secs to become responsive after 
unsuspend.

-- 
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/87f8ee4c-b146-44cc-b3bb-b59eeb31ee52%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - Thinkpad X1 Carbon 6th gen - Qubes 4.0

2018-04-17 Thread bbrr3332
On Monday, April 16, 2018 at 11:14:43 PM UTC+1, fiasc...@gmail.com wrote:
> Summary: Install worked reasonably well and it boots with EFI into the 
> installed Qubes 4.0 nicely. There are a few issues to resolve.
> 
> 1. I have the model with a touch screen and I haven't debugged how to make it 
> work yet (I'll get to that and post back what worked).
> 
> 2. Suspend/resume doesn't work and I have to do a hard reset. A few times 
> (not all) I had to hard reset twice to get it to reboot properly.
> 
> 3. HCL reports no TPM, but I have a dTPM 2.0.
> 
> It's booting with UEFI smoothly. I haven't tested the mic, camera, or ports 
> except USB for storage yet. I'll update once I find fixes for the above. If 
> anyone could point me in the right direction for the suspend freezing issue, 
> let me know. I tried shutting down all VMs, including service VMs after 
> reading this, 
> https://groups.google.com/d/msg/qubes-users/81t26xq4MEI/HrfDEcjeAgAJ but the 
> problem persisted didn't change anything.

Might be worth flashing to most recent BIOS. (I did that straight away on my 
T480 so I'm not sure if that contributed to suspend eventually working well)

-- 
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/c60e2900-f3f4-4c8a-b123-754121a8361e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: HCL - Lenovo Thinkpad T480

2018-04-16 Thread bbrr3332
On Monday, April 16, 2018 at 1:29:24 PM UTC+1, Ivan Mitev wrote:
> On 04/16/2018 02:23 PM, Ivan Mitev wrote:
> > 
> > 
> > On 04/16/2018 01:49 PM, bbrr3...@gmail.com wrote:
> >> On Saturday, April 14, 2018 at 10:13:10 PM UTC+1, bbrr...@gmail.com wrote:
> >>> System basically works nicely out of the box with Q4.0. I recommend the 
> >>> laptop.
> >>>
> >>> The only glitch was consistent crash when resuming from suspend. I 
> >>> debugged by shutting down service vm's and narrowed it down to sys-usb. 
> >>> Then detached the second USB controller from sys-usb and everything seems 
> >>> to work fine.  I did not seem to loose any devices/ports doing this but 
> >>> did not do an exhaustive test. 
> >>>
> >>> I have the high-res screen and text is pretty small. Haven't yet figure 
> >>> out how to scale things up in qubes?
> >>
> >> Thanks. Unfortunately it seems to have no effect:
> >>
> >> echo Xft.dpi: XXX | xrdb -merge 
> >> xterm &
> >>
> >> produces the same size text regardless of XXX
> > 
> > hmm :( I see that the 'Xft.dpi: XXX' setting is indeed ignored on the
> > default fedora-26 template, while it works perfectly in templateVMs I've
> > customized from fedora-26-minimal. There's probably a package in
> > fedora-26 (that I don't have in my templates) which is messing up with
> > the dpi setting; I'll update the doc and I'll reply here if I find out
> > what's causing that.
> 
> Looking at differences between fedora-26-minimal (where Xft.dpi works)
> and fedora-26 (where it doesn't), it seems that gsd-settings (from the
> gnome-settings-daemon package) overrides the dpi setting.
> 
> The following works:
> 
> - in VMs with gnome-settings-daemon:
> 
> gsettings set org.gnome.desktop.interface scaling-factor 2
> gsettings set org.gnome.desktop.interface text-scaling-factor 0.75
> 
> - in VMs without gnome-settings-daemon (or when gsd-settings is
> prevented from starting):
> 
> set the 'Xft.dpi: XXX' xresource
> 
> 
> Note that by default glib applications (like xterm) use non xft fonts,
> so if you want to have scaling in xterm you have to set an xft font like so:
> 
> XTerm*faceName: DejaVu Sans Mono:size=14:antialias=true
> 
> I'm attaching my $HOME/.Xresources file if you want to have a look.
> 
> Please let me know what works and what doesn't so that I update the doc
> and the official issue...

Thanks. Both methods work. I can just kill the gsd process and the Xft resource 
is correctly picked up and gives a nice result.

The gsettings approach also works. I did not look into it in detail but the Xft 
seems to give visually better results.

-- 
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/7eae9d67-98f1-4bec-8f96-782c07b1a27c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - Lenovo Thinkpad T480

2018-04-16 Thread bbrr3332
On Sunday, April 15, 2018 at 4:15:31 AM UTC+1, vel...@tutamail.com wrote:
> Thanks for sharing...my understanding is you can get this Laptop new? Not 
> sure if you know but this can come with either these processors:
> 
> 
> 8th Generation Intel® Core™ i7-8550U Processor (1.80GHz, up to 4.0GHz with 
> Turbo Boost, 8MB Cache)
> 
> or
> 
> 
> 8th Generation Intel® Core™ i7-8650U Processor with vPro (1.90GHz, up to 
> 4.20GHz with Turbo Boost, 8MB Cache)
> 
> Your HCL states you have the vPro...
> 
> Would you or anybody know if you can get all the functionality including AEM 
> with the i7-8550U (with out the vPro)?
> 
> Is there a higher risk of attack with the vPro?
> 
> Thanks for doing this HCL...

Yes, the T480 is brand new. I haven't tried the AEM .

-- 
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/30cf1edc-2ce8-475b-9f82-5f5c41f06dd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - Lenovo Thinkpad T480

2018-04-16 Thread bbrr3332
On Saturday, April 14, 2018 at 10:13:10 PM UTC+1, bbrr...@gmail.com wrote:
> System basically works nicely out of the box with Q4.0. I recommend the 
> laptop.
> 
> The only glitch was consistent crash when resuming from suspend. I debugged 
> by shutting down service vm's and narrowed it down to sys-usb. Then detached 
> the second USB controller from sys-usb and everything seems to work fine.  I 
> did not seem to loose any devices/ports doing this but did not do an 
> exhaustive test. 
> 
> I have the high-res screen and text is pretty small. Haven't yet figure out 
> how to scale things up in qubes?

Thanks. Unfortunately it seems to have no effect:

echo Xft.dpi: XXX | xrdb -merge 
xterm &

produces the same size text regardless of XXX

Is there a good application which definitely should honour this resource that I 
can use to test?

-- 
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/cc4c6705-3a07-42ac-bc7d-baf99ef64d09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - Lenovo Thinkpad T480

2018-04-14 Thread bbrr3332
System basically works nicely out of the box with Q4.0. I recommend the laptop.

The only glitch was consistent crash when resuming from suspend. I debugged by 
shutting down service vm's and narrowed it down to sys-usb. Then detached the 
second USB controller from sys-usb and everything seems to work fine.  I did 
not seem to loose any devices/ports doing this but did not do an exhaustive 
test. 

I have the high-res screen and text is pretty small. Haven't yet figure out how 
to scale things up in qubes?

-- 
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/340b728b-fd1b-47c8-8143-52b4e0f0b2e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-LENOVO-20L6S1RG00-20180414-220504.yml
Description: Binary data


[qubes-users] Re: Qubes and USB Ethernet adapter

2017-06-16 Thread bbrr3332
On Friday, June 16, 2017 at 7:28:53 AM UTC+1, Swâmi Petaramesh wrote:
> Hi,
> 
> I have a new Asus laptop which comes with no integrated Ethernet, but an
> USB Gigabit Ethernet adapter.
> 
> I wonder if this will be compatible with Qubes' Net VM, or if I will
> need to allocate the complete USB controller to the net VM - which would
> be extremely annoying to me...
> 
> Any clue appreciated.
> 
> Kind regards.
> 
> -- 
> Swâmi Petaramesh  PGP 9076E32E

I've tried using an ASUS USB Ethernet adapter (with a Dell laptop in my case, 
but probably not relevant) without luck. I found that an USB Wifi Dongle worked 
better.

-- 
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/dfe4f76f-980c-4ab6-8f28-56715cf0797b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] postfix

2017-05-22 Thread bbrr3332
On Friday, March 10, 2017 at 3:37:24 PM UTC, Ted Brenner wrote:
> On Thu, Mar 9, 2017 at 9:24 PM, Ted Brenner  wrote:
> 
> 
> 
> 
> 
> On Thu, Mar 9, 2017 at 6:57 AM, Unman  wrote:
> 
> 
> On Wed, Mar 08, 2017 at 08:36:11PM -0600, Ted Brenner wrote:
> 
> > On Wed, Mar 8, 2017 at 9:32 AM, Ted Brenner  wrote:
> 
> >
> 
> > > On Wed, Mar 8, 2017 at 9:15 AM, Unman  wrote:
> 
> > >
> 
> > >> On Tue, Mar 07, 2017 at 09:56:02PM -0600, Ted Brenner wrote:
> 
> > >> > Hi all,
> 
> > >> >
> 
> > >> > I'm trying to setup postfix following this guide
> 
> > >> > . But I'm not able to get a few
> 
> > >> > things to work.
> 
> > >> >
> 
> > >> > First, the commands I added to /rw/config/rc.local don't seem to run.
> 
> > >> > Namely, it doesn't appear to be mounting the /usr/local/etc/postfix
> 
> > >> > directory in /etc/postfix. Also postfix doesn't appear to be running on
> 
> > >> > startup. How do we tell if that gets run correctly?
> 
> > >> >
> 
> > >> > Thanks!
> 
> > >> > Ted
> 
> > >> >
> 
> > >>
> 
> > >> Other have pointed out that you need to set the executable bit on
> 
> > >> rc.local.
> 
> > >> You might want to cnsider instead the use of bind-dirs :
> 
> > >> www.qubes-os.org/doc/bind-dirs which provides similar functionality.
> 
> > >>
> 
> > >
> 
> > > Thanks all. Yes, this was the issue. Still can't get postfix to work but
> 
> > > that now appears to be due to missing the aliases.db.
> 
> > >
> 
> > > Is there a reason rc.local isn't executable by default?
> 
> > >
> 
> > > --
> 
> > > Sent from my Desktop
> 
> > >
> 
> >
> 
> > Quick follow up. What user is running rc.local? Is it root or user? I
> 
> > assume it is user since I'm seeing a permission denied when the call to run
> 
> > postfix tries to access the aliases.db file. So should I throw a sudo in
> 
> > front of the command to start postfix in the rc.local file? Or should I
> 
> > change the permissions on aliases.db? Per the instructions I'm also doing a
> 
> > mount command but that succeeds. Which is odd since if I try it as user, it
> 
> > fails saying only root can do it. Which is why I ask which user is running
> 
> > rc.local.
> 
> >
> 
> It's root - you could see this by appending:
> 
> echo `whoami` >> /home/user/rc_perms
> 
> But I suspect you already know this.
> 
> 
> 
> What are the permissions on aliases.db?
> 
> What template are you using and do you have selinux enabled?
> 
> 
> 
> 
> 
> 
> Thanks Unman. I'm using Fedora-24 and selinux is not enabled. aliases.db is 
> owned by root:root with rw-r--r--.  
> 
> 
> -- 
> 
> Sent from my Desktop
> 
> 
> I think the source of my problem was that postfix does some initial 
> configuration on its first launch. This requires the postfix-files file. But 
> that didn't get copied to /usr/local/etc/postfix which is mounted over 
> /etc/postfix. Once I added that file it launched successfully which appears 
> to have properly set up the aliases.db file so now all appears to be well. 
> Perhaps I'll submit a PR to update the postfix page to include copying 
> postfix-files to /usr/local/etc/postfix.
> 

I've come across this too and created a PR for the docs: 
https://github.com/QubesOS/qubes-doc/pull/427

-- 
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/ab7b2861-8891-4b8a-a69a-9eed9fcec3d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Yubikey init failed PCSCD

2017-02-19 Thread bbrr3332
On Sunday, February 19, 2017 at 7:51:45 AM UTC, Robin Lambertz wrote:
> On 02/16/2017 12:30 AM, bbrr3...@gmail.com 
> wrote:
> >
> > I've been able to use my Yubikey 4 on a debian 8 qube successfully. 
> > (Remember to patch the libccid_Info.plist). Might be worth giving it a try?
> >
> 
> Hi,
> 
> What did you patch exactly ?

This is the script 
https://github.com/Yubico/yubioath-desktop-dpkg/blob/master/resources/linux-patch-ccid

But it does sound like this is not what is causing your problem

-- 
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/a611e59a-c594-4993-90b1-f5ee4de04db3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Yubikey init failed PCSCD

2017-02-15 Thread bbrr3332
On Tuesday, February 14, 2017 at 6:49:44 AM UTC, Robin Lambertz wrote:
> Hello,
> 
> I'm trying to make my Yubikey Neo (a PGP smartcard) accessible to my GPG 
> Qube in a split-gpg + sys-usb setup. When attaching the Yubikey to the 
> GPG VM, however, PCSCD doesn't seem to detect my Yubikey (which leads it 
> to being unusable with gpg). I tried both an up-to-date archlinux and 
> the default fedora-23 templates, and in both cases the yubikey neo 
> doesn't show up in `pcsc_scan`.
> 
> I started pcscd with `sudo LIBCCID_ifdLogLevel=0x000F pcscd --foreground 
> --debug --apdu --color | tee log.txt` to get more info. The logs are 
> attached, but the interesting bits are here :
> 
> ```
> 0206 ccid_usb.c:621:OpenUSBByName() Found Vendor/Product: 1050/0111 
> (Yubico Yubikey NEO OTP+CCID)
> 0012 ccid_usb.c:623:OpenUSBByName() Using USB bus/device: 2/4
> 0010 ccid_usb.c:680:OpenUSBByName() bNumDataRatesSupported is 0
> 1997 ccid_usb.c:1244:InterruptRead() before (0)
> 00103904 ccid_usb.c:1290:InterruptRead() after (0) (2)
> 0072 -> 00 65 00 00 00 00 00 00 00 00 00
> 2614 <- 00 81 00 00 00 00 00 00 00 00 00
> 0050 -> 00 65 00 00 00 00 00 01 00 00 00
> 00103063 ccid_usb.c:836:ReadUSB() read failed (2/4): -7 LIBUSB_ERROR_TIMEOUT
> 0224 -> 00 65 00 00 00 00 00 02 00 00 00
> 05002241 ccid_usb.c:797:WriteUSB() write failed (2/4): -7 
> LIBUSB_ERROR_TIMEOUT
> 0242 ifdhandler.c:188:CreateChannelByNameOrChannel() failed
> 0159 ccid_usb.c:879:CloseUSB() Closing USB device: 2/4
> 0151 ccid_usb.c:889:CloseUSB() Last slot closed. Release resources
> 0240 ccid_usb.c:189:close_libusb_if_needed() libusb_exit
> 0476 readerfactory.c:1110:RFInitializeReader() Open Port 0x20 
> Failed (usb:1050/0111:libudev:1:/dev/bus/usb/002/004)
> 0161 readerfactory.c:375:RFAddReader() Yubico Yubikey NEO OTP+CCID 
> init failed.
> ```
> 
> When attaching the yubikey to the VM, ReadUSB returns immediately with 
> the TIMEOUT error (isn't that weird ?), while the WriteUSB times out 
> after 5 seconds. I'm wondering if it was possible the Qubes USB proxy 
> could cause those timeouts ? Anyone knows what else could cause those 
> errors ?
> 
> Thank you for your time :)
> 
> Robin Lambertz

I've been able to use my Yubikey 4 on a debian 8 qube successfully. (Remember 
to patch the libccid_Info.plist). Might be worth giving it a try?

-- 
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/b25b22e7-746e-48a4-8610-5cf39089e5b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Unable to start any VM. Getting: error starting vm: internal error: unable to reset PCI device 0000:

2017-01-25 Thread bbrr3332
On Wednesday, January 25, 2017 at 9:27:10 PM UTC, Pietro Speroni di Fenizio 
wrote:
> Hello,
> we just installed a Qubes in a linux machine I had.
> 
> Unfortunately the system seem to be unable to start any VM.
> 
> I always get the same error:
> ERROR: internal error: unable to reset PCI device :03:00.2
> internal error: Active :03:00.0 devices on bus with
> 000:03:00.2, not doing bus reset
> 
> Can someone point me to the right direction? I seem stuck as anything 
> requires me first to start a VM, but no VM seem to be able to start. In fact 
> when the computer turns on at the beginning only dom0 is active and even 
> sys-net and sys-firewall are inactive.
> 
> Many thanks,
> Pietro

If you run lspci in dom0 you will get the list of devices and their bus 
numbers. If you look for devices on :03:00  this should give clues about 
what is going on.

-- 
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/6d3ffc21-2e6f-421a-9584-2440618c5b39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - Dell XPS 15 9550

2017-01-12 Thread bbrr3332
On Wednesday, January 11, 2017 at 10:34:22 PM UTC, John Doe wrote:
> On Sunday, January 8, 2017 at 10:38:49 PM UTC, bbrr...@gmail.com wrote:
> > In original configuration this laptop suffers from freeze on initial boot 
> > when the system attaches the broadcom wifi card to sys-net. To make 
> > progress needed to disable the wifi card in BIOS, install was then 
> > straightforward. 
> > 
> > Used an USB wifi for initial investigation/updates. Needed to assign the 
> > USB controller to the sys-net VM and allow non strict pci reset. 
> > ThenuUpgraded the fedora23 kernel to the version in unstable repository:
> > 
> > Linux sys-net 4.8.12-12.pvops.qubes.x86_64 #1 SMP Sat Dec 3 19:12:54 UTC 
> > 2016 x86_64 x86_64 x86_64 GNU/Linux
> > 
> > As there is only one USB controller on this board, this is not a great 
> > long-term solution. I then replaced the broadcom wifi card with an Intel 
> > 8265 which works very well with the 4.8 v kernel. Generally everything now 
> > seems to work well: suspend works, touchpad works well, screen dimming, 
> > attaching usb storage. No touchscreen on this model so can't comment on 
> > that.
> 
> Did your 9550 not come with a Killer 1535? At least that's what is listed on 
> the product page, http://www.dell.com/uk/p/xps-15-9550-laptop/pd?ref=PD_OC

No, it came with DW1830 which is a re-badge of Broadcom. It was bought in the 
first half of last year.

-- 
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/ec524cc1-c938-4f4b-9ceb-932028b07c72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Can NOT get Broadcom BCM43602 Wifi Card working , DELL XPS 15 9950- Qubes sys-net freezes/ crashes

2017-01-08 Thread bbrr3332
On Wednesday, August 3, 2016 at 3:05:01 PM UTC+1, Michael wrote:
> Have a Broadcom BCM43602 Wifi Card in my dell xps 15 9950
> 
> and I downloaded Qubes Release 3.2-rc2
> 
> Problem: I can not connect to the internet cause my wifi card is not working 
> with qubes:
> "If BCM43602, the wireless card is disabled in BIOS, installation succeeds, 
> and afterwards it's possible to re-enable BCM43602 in BIOS and boot Qubes. 
> However, subsecuantly adding BCM43602 device to the sys-netvm freezes the 
> computer."
> 
> -my boot setup has
> VT and VT-d options activated
> 
> 
> how can I make my network function ?

I replaced the wifi card in my XPS 9550 with an Intel 8265 and updated the 
fedora 23 template to the kernel from the unstable repository. Wifi now works 
very well (as well as everything else it seems).

-- 
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/eb4a7a8e-a034-400b-b7ac-dc12b2f2cc0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - Dell XPS 15 9550

2017-01-08 Thread bbrr3332

In original configuration this laptop suffers from freeze on initial boot when 
the system attaches the broadcom wifi card to sys-net. To make progress needed 
to disable the wifi card in BIOS, install was then straightforward. 

Used an USB wifi for initial investigation/updates. Needed to assign the USB 
controller to the sys-net VM and allow non strict pci reset. ThenuUpgraded the 
fedora23 kernel to the version in unstable repository:

Linux sys-net 4.8.12-12.pvops.qubes.x86_64 #1 SMP Sat Dec 3 19:12:54 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

As there is only one USB controller on this board, this is not a great 
long-term solution. I then replaced the broadcom wifi card with an Intel 8265 
which works very well with the 4.8 v kernel. Generally everything now seems to 
work well: suspend works, touchpad works well, screen dimming, attaching usb 
storage. No touchscreen on this model so can't comment on that.

-- 
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/7f12f377-2809-4910-bffa-375228ed249d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-Dell_Inc_-XPS_15_9550-20170108-222328.yml
Description: Binary data