OK, I updated the BIOS. That got rid of the microcode error, alright. However,
it still hangs.
I now get the error:
[2.040734] Couldn't get size: 0x8 0e
[2.527013] usb 1-1:string descriptor 0 read error-71
Just for giggles, I tried a different usb port for my flash drive. On the
second
Thanks, I'll give it a try. Now I just have to figure out how to update my
BIOS. Once I look that up, I'll report back...
--
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
Yeah, I'll do that. On the other hand, it may be a Fedora thing. Just for
giggles, I downloaded F26, and it won't install, either -- it times out, though
it gives a different error when it does.
I use these cheap flash drives I buy in bulk off ebay. I'll go get a pricey
one and see if it
On Wednesday, November 1, 2017 at 7:43:42 PM UTC-4, [799] wrote:
> I've migrated my USB drives to only one Modell:
> SanDisk
> https://www.amazon.com/gp/aw/d/B01NARBPI7/
>
> It has a good performance (I have installed Qubes on of those to showcase it
> to friends and colleques.
>
> [799]
On Monday, October 30, 2017 at 7:29:55 PM UTC-4, bill...@gmail.com wrote:
> Don't know what this means, but I downloaded the new 4.0 RC2, put it on a
> flash drive, and tried to install it on my new Dell laptop. It froze early
> on, with the messages:
>
>
> Firmware Bug: TSC_DEADLINE
Don't know what this means, but I downloaded the new 4.0 RC2, put it on a flash
drive, and tried to install it on my new Dell laptop. It froze early on, with
the messages:
Firmware Bug: TSC_DEADLINE disabled due to errate. Please update microcode to
version 0xb2 (or later)
2.035271 Could
I tried to send this question from the email address I used to subscribe to the
user group, but it's been about two hours and it hasn't shown up. I'm assuming
it's a Google thing, but I apologize if this question shows up twice.
So, here I go again. I'm a newbie with Qubes, but I love the
Thanks so much for your reply and your help. I installed using legacy boot and
it worked fine -- in fact, I'm responding from "untrusted firefox" right now!
I don't know if qubes comes up in the grub menu yet. I just got this
installed, and ran it from the BIOS boot sequence Legacy-USB
I had a similar issue with installing Qubes 4 rc3 on an external drive for
triple boot on a Dell laptop. The response by "yuraeitha" in that thread ("Can
I install qubes 4.0 rc3 on an external hard drive") was very informative. My
current workaround, at least until I decide to install on the
Thanks for you help --- again. Your widget discussion is what did it. In KDE,
I didn't see the widget for adding disks to VMs, but it's there in the XCFe
desktop. So instead of using the widget in KDE, I did everything by hand from
the command line. Since the SATA disk partitions
Makes sense. Thanks.
--
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
I have installed Qubes 4 rc3 on a usb external hard drive. I have Neon linux
and Windows on my internal hard drive. I decided I wanted to copy some files
from my home directory on my internal hard drive to my Qubes home directory in
the fedora26vm.
Unfortunately, I simply can't figure out
That was it! Thanks, folks. Problem is solved.
billo
--
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
I recently installed Qubes 4 rc3 on my Dell laptop, and it seems to working
well. However, there's a little bit of a problem with my networking. It comes
up fine when I reboot the machine, and runs like a charm... but when I close
the laptop lid, networking turns off, and I can't figure out
I installed Qubes 4 rc3 yesterday and am having a great time exploring it. I'm
kind of a KDE person, so I installed KDE, and it works pretty much like a
charm, though I'm having a bit of an issue personalizing it.
If anybody can give me some aid, I'd appreciate it.
First, while KDE seems to
I downloaded and installed KDE today, and it went fine. Now I am upgrading the
default fedora-25 template to fedora-26. I've gone through the downloading and
all, and am now at the "change default template" part.
So... I click on Applications-> System Tools -> Qubes Global Settings and
On Saturday, January 27, 2018 at 6:23:54 PM UTC-5, Yuraeitha wrote:
> On Friday, January 26, 2018 at 8:45:43 PM UTC+1, bill...@gmail.com wrote:
> > Thanks so much for your reply and your help. I installed using legacy boot
> > and it worked fine -- in fact, I'm responding from "untrusted
Thanks all, for your replies. So, it's a feature, not a bug :-). That's cool
-- I mostly just need to know to stop trying to fix it. For the moment, it's
not a big deal. Most of my work does not involve fancy 3D graphics, and I can
easily boot into something else for that.
--
You received
I'm in a slightly similar situation. I am a very new Qubes user and am in the
process of getting used to it. My impression is that Qubes right now is a
little like linux in general in the 1990s. I can remember running linux on my
boxes and I could do about 70% of what I needed to do, but
On Friday, February 16, 2018 at 1:38:32 AM UTC-5, [799] wrote:
> Additional Info:
>
> I have tested the screenshot tool in an unchanged Fedora 26 template, no
> content is shown after screenshoting.
> Instead of my first post, the screenshot is only shown as a white (not black)
> area.
>
> The
On Tuesday, February 20, 2018 at 10:27:24 AM UTC-5, Tom Zander wrote:
> So, knowing that your API is actually based on 8-bit characters and not 7
> bits which you are limiting yourself to, my suggestion is to take something
> above 127 and below 256 as a special char.
> Most fun one would be
On Wednesday, February 28, 2018 at 1:34:28 PM UTC-5, Chris Laprise wrote:
> Hi,
>
> The macchanger section of the doc hasn't worked for a long time (search
> the mailing list to see issues) and it never did work correctly, IMO.
>
> > What should i do?
> >
>
> You should use the MAC
On Thursday, March 1, 2018 at 12:08:19 AM UTC-5, Chris Laprise wrote:
> On 02/28/2018 08:23 PM, 'awokd' via qubes-users wrote:
>
> BTW, as an example of Qubes-specifics in this issue, on sleep/wake
> networkVMs don't process the normal array of events and system states
> that bare-metal Linux
Update:
Sound works fine.
Youtube video works fine in disposable debian vm.
--
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
Just as a data point, I installed RC4 on my Dell laptop as part of a triple
boot setup (Win 10, Netrunner linux, Qubes 4.0), and it installed fine with one
exception (which I'll get to below). I have the BIOS set to UEFI with secure
boot disabled.
I had to install three times, but the third
I don't know if this will be of any help, but with R4 rc4, I installed it on a
Dell laptop and had a similar problem with dual boot (though I installed Qubes
on a second external hard drive). The UEFI stuff just didn't work. My solutions
was to install Qubes in legacy mode, but left Windows in
Oh, one more thing. If I *don't* hit F12 during boot, and I have the external
hard drive detached, then it comes up with the "no boot device" error. It will
boot through the USB using legacy mode by default, but will crump if the drive
isn't plugged in. Then I have to hit return (which
Looks like I have a couple of hours of fun ahead. Thanks for the pointer.
Since it will be that much effort, I probably won't get to it for a couple of
days so I have a block of time to devote to it, but I'll report back and see if
it works.
Thanks for the reply!
--
You received this
So, I recently installed R4 on my laptop and things seem to be going smoothly.
I'm ready to get my VPN working.
I use mullvad, and I'm having trouble connecting the instructions in the
documentation with how mullvad works -- as least as far as using the GUI.
Before I screw something up, I
Heh. It seems to me that the "Reasonable" in Qubes "A reasonably secure
operating system" has differing values of "reasonable" depending on the user.
I have qubes on a triple boot machine (one hard drive).
The fact is that there is, and always will be, an inverse relationship between
Thanks everybody for the replies. I apologize for the delay in responding --
I've been traveling and just got off the plane on the last leg of the trip.
I had not installed any updates in Qubes, afaik, but did install upgrades in
both Netrunner and Windows. Yes, my troubleshooting failed
So, I had installed Qubes 4 on a triple boot laptop (Win 10, Netrunner linux,
Qubes OS). It had installed fine, and I had booted up in Qubes three or four
times, played with the VMS, ran firefox, poked around a little, and was happy.
Then I got busy with some other stuff and set it aside, and
I posted a couple of days ago about trying to install a dual boot KDE neon and
Qubes OS 4.0.1 on an HP laptop with a hybrid disk system -- 256G SSD and 1T
SATA. I had originally thought the problem was solved by installing Qubes
first and then KDE neon, since both would come up that way.
> Boot Qubes from rescue mode on the USB. Rebuild Qubes' grub and
> initramfs. It will be something like "sudo grub2-mkconfig -o
> /mnt/sysimage/boot/grub2/grub.cfg". Then reboot and try the Qubes option
> again from the grub menu.
Thanks for the reply! I tried that, and got different
On Monday, January 14, 2019 at 1:40:12 PM UTC-5, bill...@gmail.com wrote:
> > Boot Qubes from rescue mode on the USB. Rebuild Qubes' grub and
> > initramfs. It will be something like "sudo grub2-mkconfig -o
> > /mnt/sysimage/boot/grub2/grub.cfg". Then reboot and try the Qubes option
> > again
The problem has been solved.
It turned out that Qubes is tolerant of KDE Neon, but KDE Neon is not tolerant
of Qubes. My solution was to delete both installations, install Qubes first,
and KDE Neon second. Now both boot fine. So, I did it again in the reverse
order, and I replicated my
The other thing I did wrong was to use the usb writer in a mode other than
"dd." It doesn't sound like you made that mistake, since you got as far as you
did, but that caused me a few hours of amusement also.
--
You received this message because you are subscribed to the Google Groups
It is the only OS on the drive? I gotta tell you, I had nothing but headaches
trying to do a dual boot installation, either with Windows 10 or Fedora 29.
Since I have a hybrid disk machine, I ended up creating two MBRs, two
/boot/efi's, etc, one on the SSD and on on the SATA drive. One of
I recently installed 4.0.1 on my laptop and it seems to be working great,
though I'm still working through some of the how-do-you-copy-files stuff and
some of the networking stuff. But, it's just a different way of doing things,
and that can be learned.
I followed the directions in the qubes
Folk,
I am trying to install 4.0.1 on a new HP laptop model 15t-da000. It has one
250G SSD and one 1 TB SATA drives, i7 cpu, intel graphics. I have overwritten
the Windows 10 default installation with KDE neon (ubuntu based), using about
100G of the 250G SSD. I am trying to make a dual
Thanks everybody. The problem was solved with setting the locale. The only
"trick" was that I kept banging on localectl, and it seemed to accept the
command, but I kept getting the error and it didn't seem to "take" -- until I
rebooted. Doh.
--
You received this message because you are
On Sunday, January 27, 2019 at 12:22:03 PM UTC-5, unman wrote:
>[snip]
> Qubes provides a framework for using software - it doesn't take away the
> onus on users to use that software properly, and to ensure they are aware
> of good practice. (As an aside I'm always baffled by people querying
>
I am sure this is a silly issue, but I've been searching in the archives and
can't see the answer.
I have a laptop with 1 SSD and 1 SATA drive. I installed Qubes on the SSD, and
have a couple of data partitions on the SATA drive. I want to make one of
those partitions available to my work vm
On Sunday, March 24, 2019 at 7:22:30 PM UTC-4, awokd wrote:
>
>
> Most flexible way to use the secondary drive would be to backup the data
> somewhere else, then https://www.qubes-os.org/doc/secondary-storage/. If
> you want to assign sda3 to a VM, you'd have to unmount it from dom0
> first,
On Wednesday, February 6, 2019 at 11:36:12 AM UTC-5, unman wrote:
> On Wed, Feb 06, 2019 at 10:15:54AM -0600, John Goold wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > On 2/6/19 1:12 AM, 'awokd' via qubes-users wrote:
> > > kitchm via Forum:
> > >
> > ...
> > >> It is
the maximum security that I can achieve
> > and stay below my maximum hassle tolerance. Qubes is nice because it
> > adds a big uptick in transparent security with only a small uptick in
> > hassle -- at least for someone who is fairly conversant with sysadmin
> > st
Well, I guess I'm pretty useless, then. Sorry. I sympathize. It took me
about five attempts of reinstalling Qubes and/or KDE neon to get them both to
work. I swear that Qubes partitioned automatically on installation, but I guess
my memory was wrong. That's always the problem when you bang
Thanks for the info! I won't worry about it, then.
--
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
I should add that, by the way, I connect fine. It just an irritating message.
--
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
I have recently installed 4.0.1 with KDE Plasma as my Desktop. I tried to ssh
to another computer through my "untrusted" domain, and received the following
error. I don't have trouble talking to the site for other stuff -- it's my
personal virtual server that I use for email and such, and my
On Thursday, January 31, 2019 at 9:47:37 PM UTC-5, kitchm wrote:
> The basic concept here is clarify what is being discussed.
> There appears to be two things; one is how a mail-list works
> and the other is how a mail-list is not as good as a forum.
> [snip]
Maybe I'm not getting something
I am trying to install the Brave browser in my debian template VM it
requires that I add a repository with the command:
curl -s https://brave-browser-apt-beta.s3.brave.com/brave-core-nightly.asc |
sudo apt-key --keyring /etc/apt/trusted.gpg.d/brave-browser-beta.gpg add -
When I try the first
So, for my "untrusted" qube, I decided I wanted Debian, and I changed it in
the Qubes settings. That worked fine. However, when I did that, Firefox
stopped coming up when I clicked on untrusted:Firefox (though it came up
fine from the terminal when I typed "firefox").
So... I went back to
So, this is odd. I installed 4.0.2rc2 and:
1) Changed the template for untrusted: to debian-10. That seemed to work
fine.
2) Went to the debian 10 template and installed Blender. That seemed to
work fine -- blender will run if I invoke it from the debian-10 template
terminal
3) Restarted
I installed KDE . The installation went fine, though of course the
touchscreen doesn't work (which has been written about before). The
graphical interaction for blender was actually better in KDE than it was in
Xfce. However... after a minute or two, the left mouse button became
On Thursday, November 7, 2019 at 8:01:41 AM UTC-5, bill...@gmail.com wrote:
>
> Just a quick data point. Installed without a hitch on my HP laptop with
> 256G SSD and a 1TB SATA (installed on my SSD only). The SSD makes it a
> *lot* more snappy.
>
Actually that's a 15t-da000, not 5t. Bad
My error. I forgot to turn off and turn on the template VM for
debian-10. Once I did that and then turned on the template based vm, it
came up. Sorry for the newbie mistake.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe
The proxy worked fine. It's all good. Thanks!
billo
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this
Thanks for the reply. I went the proxy route below, since it was simpler,
but I appreciate the help.
billo
--
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
I'm a relatively new user, too. I played with Qubes for a month or so a
year or two ago, installing it on an external hard drive for a test run.
It was too slow loading for me. I got a new laptop and put it on my SSD
drive a month ago, and it's been working great.
I had the same issue with
I'm using a VPN, and constructed VMs for them using the Mullvad
instructions. I have two vpn domains, mullvadus and mullvaddenmark, both
of which are in turn attached to the default sys-firewall. My "untrusted"
domain is attached to the vpn going to Denmark, and my "work" domain is
>
> Is there actually anyone working on the hidden OS option for the
> linux? Would be very much appreciated.
>
>
Hah. I actually did something like this by accident the first time I
installed Qubes. I had KDE neon installed, and I couldn't get it to dual
boot correctly. It turned out
No, it's been consistent for a few weeks now, so I'm not going to worry
about it. I did find another way to screw up, though. I attached the
drive persistently to my "untrusted" VM, and then put the mount in
/etc/fstab in the debian-10 template, so it would persist also. That
worked fine
Yeah, there are ways to fake an OS, but that really wasn't my question. I
was wondering whether or not folk have noticed that having an OS like Qubes
would result in greater scrutiny than Windows or MacOS. I'm not trying to
sneak anything across the border; I just don't want to spend an
I think that you are not supposed to use one of those make-a-bootable-drive
apps. Instead, as I remember, you just dd the thing onto the usb and plug
it in. See:
https://www.qubes-os.org/doc/installation-guide/
Look at the section "Copying the ISO onto the installation medium"
When I first
So, here's an update:
I've figured out how to attach the device automatically, using "qvm-device
block attach --persistent untrusted dom0:sda3" in the dom0 command line.
However, I can't seem to get it to mount on bringing up the VM. My
"untrusted" VM is debian based. My /etc/fstab entry
On Thursday, December 12, 2019 at 2:36:01 PM UTC-5, bill...@gmail.com wrote:
>
> So, here's an update:
>
> I've figured out how to attach the device automatically, using "qvm-device
> block attach --persistent untrusted dom0:sda3" in the dom0 command line.
> However, I can't seem to get it
Doh. I just noticed the "noauto" option. Sigh. Deleted it and it works
fine.
--
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
I will be doing some international travel in the upcoming months. In the
past, I have had to turn on my laptop, and once I had to bring the system
fully up and allow people to see my desktop -- though nobody has actually
seized and gone through my computer as yet. Has anybody gotten
I have an HP laptop with 4.0.2.rc2 installed. Everything works well, with
the exception of a couple of small things I've asked about previously.
Now I'm trying to tune it a bit. I have a 256G SSD where qubes is
installed, and a 1TB traditional hard drive. I want to attach the hard
drive
I need to add swap space to a VM, but it's not clear to me how to do it.
If this were "normal" linux, I'd just add a swap file, but I don't know if
I need can do that in dom0, and if that translates to available swap space
in my VMs. The last time I played with memory things in dom0, I
Thanks to all for the replies. It worked!
billo
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this
Qubes folk,
So, I have a debian-based untrusted vm that is attached to a mullvad
vpn through Sweden; the mullvad vpn gets its networking from sys-
firewall (i.e. sys-net -> sys-firewall -> mullvad-vpn -> untrusted vm.
I have another "local" vm that is directly attached to sys-firewall
(i.e
As an aside, these are the instructions I used to set up the mullvad vpn.
https://mullvad.net/en/help/qubes-os-4-and-mullvad-vpn/
--
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,
Well, I tried again and the upgrade worked. I don't get it. I changed the
size of the template yesterday, and it didn't work. Today, I didn't change
anything, and it did. The only thing that changed this time was that I
hard-power-cycled the machine, where before I had merely shut down the
I got a ping saying there was an update for my fedora-30 template VM, So,
I started the Qubes updater. I then get the error that it needs an
additional 34 MB to install the kernel image. No problem, I think. So I
go to the documentation and look up how to increase the size of the
Thanks. That worked for me, too.
Loading the firmware into Debian and using that for sys-net did *not* work
-- because it uses the same kernel. I found a router to plug into an
downloaded the firmware for the debian template. I switched from not
having the right firmware to replicating the
>
> I did a search on this. There have been a number of folk complaining of
> it on the fedora groups. It seems to have been a problem with a recent
> kernel update.
>
It's happened to me, too. On the fedora boards, it is fixed by installing
the newest kernel update. My problem is that I
You might try changing the template for sys-net from fedora to debian.
However, for me, it turns out that the debian template has old firmware for
my wireless device, and so I can't get wireless with it, either. But at
least it's a different error
--
You received this message because
79 matches
Mail list logo
