My, Dell Inspiron 15 5570 has i5 8250, 12GB DDR RAM , 1TB SATA HDD. I have
created a bootable Qubes 4.2.0 with dd command in Ubuntu and trying to boot
my Dell Inspiron with it. However it is failing to boot and restarting and
falling back to Ubuntu 23.10. Should I try to boot in legacy BIOS mode
Sorry about the Typos, "I turned off SMT"* which fixed some R4.1 installer
issues but not all. The installer fails to finish boot.
On Saturday, December 9, 2023 at 9:01:36 AM UTC-5 Richard Horan wrote:
> Hi,
>
> I could not post to the forum.qubes-os.org becuse I am a new user, so I
> am posti
On 6/6/23 04:20, 'sonnenfinsternis' via qubes-users wrote:
Do I still have to submit something to be included in the HCl or do I just need
some more patience
It's not you, it's me. Super busy. Will take care soon.
/Sven
--
https://keys.openpgp.org/vks/v1/by-fingerprint/DA5975C9ABC40C833B2F6
After more than a week of intensive use, I haven't noticed any problems so far.
The "cirrus7 nimbini v3" (or presumably all NUC12WSHv5) seemed to be suitable
hardware for anyone who wants to use QubesOS as a desktop system.
Do I still have to submit something to be included in the HCl or do I
I forgot to attach the yml file. Sorry!
--- Original Message ---
On Wednesday, May 24th, 2023 at 11:51 PM, sonnenfinsternis
wrote:
> Here's my review of the cirrus7 nimbini v3, which is largely based on the
> Intel NUC 12 (NUC12WSHv5). QubesOS with the "kernel latest" option runs
> g
OK, after a bit of googling I found this
https://github.com/QubesOS/qubes-issues/issues/7507#issuecomment-1153081021
and adding the config to xorg.conf.d
Section "OutputClass"
Identifier "intel"
MatchDriver "i915"
Driver "intel"
Option "AccelMethod" "sna"
Option "TearFree" "true"
Option "DRI" "3
Another follow-up. The audio (tested via a fedora-based work-qube) is
hilariously distorted. Listening to some music through it made it sound
like some extremely experimental avant-garde stuff.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
Another follow-up:
I now installed kernel version `6.0.7-1.fc32.qubes.x84_64`, and now I
get past the crash at the luks-screen.
I am not 100% sure which kernel fixed it, but ISTR trying with an
earlier 6.0-version a few weeks ago without success.
Going to test a bit more, but looks good so
Hello,
Could it be that current sys-gui-gpu cannot work because of
: https://lists.xenproject.org/archives/html/xen-devel/2022-10/msg01820.html
?
Le jeudi 6 octobre 2022 à 10:14:23 UTC+2, martin...@gmail.com a écrit :
> Follow-up to my last mail, where I posted an image. Here's the
> trans
Follow-up to my last mail, where I posted an image. Here's the
transcribed stack trace, for better indexing by search-engines
```
kernel BUG at mm/slab.h:440!
invalid opcode: [#1] PREEMPT SMP NOPTI
CPU: 9 PID: 717 Comm: udevadm Tainted: G W
5.19.14-1.fc32.qubes.x86_64 #1
Hardware na
Yeah, In the process of trying to get qubes to work I tried 5.19.9-1.fc32
but it kept crashing at the Luks password screen. The only kernel that
seems to work is 5.18.16-1.fc32.qubes.x86_64 but if "sudo qubes-dom0-update
kernel-latest" doesn't work for you then I don't know how else you would
g
Update on this.
I was able to update sys-net to use 5.15.64-1.fc32, and can confirm that
it fixed the wifi issues.
I also updated the dom0, to 5.19.9-1.fc32. However, that didn't go as
well, and the system now crashes on boot -- sometimes I get to enter the
LUKS password, sometimes it crashe
That's odd, since it doesn't seem to work for me.
Related question: I've been searching and haven't found -- where can I
check the most recent packages on the various channels (stable /
unstable / testing / experimental etc) . Would be nice to be able to
check what different kernels are availa
I just entered "sudo qubes-dom0-update kernel-latest"
On 19 September 2022 23:58:42 Martin Holst Swende
wrote:
Well done!
How did you enable the 5.18 kernel? I've tried with 'qubes-dom0-unstable'
and listing the available kernels, but it shows only a few versions of 5.15
as installation cand
Qubes is working for me on Lenovo X1 Carbon gen 10.
To fix graphical glitches Dom0 needs to use kernel
5.18.16-1.fc32.qubes.x86_64 and create file with "sudo nano
/etc/X11/xorg.conf.d/99-intel.conf" and add;
Section "OutputClass"
Identifier "intel"
MatchDriver "i915"
Driver "intel"
Option "Ac
Well done!
How did you enable the 5.18 kernel? I've tried with
'qubes-dom0-unstable' and listing the available kernels, but it shows
only a few versions of 5.15 as installation candidates.
Cheers,
Martin
On 9/20/22 05:36, Arran Lawley wrote:
Qubes is working for me on Lenovo X1 Carbon gen
On Sun, Aug 28, 2022, 1:26 AM Data Python
wrote:
> You may want to keep your i915 driver and try:
> https://github.com/QubesOS/qubes-issues/issues/7507#issuecomment-1153081021
Interesting!
I tried it now, but unfortunately I encounter a core dump, similar to one
person in that issue. However,
You may want to keep your i915 driver and try:
https://github.com/QubesOS/qubes-issues/issues/7507#issuecomment-1153081021
On Monday, August 15, 2022 at 8:46:28 PM UTC+2 martin...@gmail.com wrote:
> To follow up after a bit more experimentation.
>
> - Using the boot param 'module_blacklist=i915'
To follow up after a bit more experimentation.
- Using the boot param 'module_blacklist=i915' makes things work pretty
much ok. No obvious graphics glitches, it's able to play videos without
the fans spinning up like crazy.
- The PCI device for networking seems unsupported, so usb-wifi card i
On Thu, Aug 11, 2022, 3:10 PM Martin Holst Swende
wrote:
>
> On 8/11/22 11:38, Demi Marie Obenour wrote:
>
> 3. Does HVM sys-gui-gpu work? What about PV (not PVH!) sys-gui-gpu?
>
> I don't have a sys-gui-gpu at the moment, but will test that. This page
> (https://www.qubes-os.org/doc/guivm-confi
On 8/11/22 11:38, Demi Marie Obenour wrote:
3. Does HVM sys-gui-gpu work? What about PV (not PVH!) sys-gui-gpu?
I don't have a sys-gui-gpu at the moment, but will test that. This page
(https://www.qubes-os.org/doc/guivm-configuration/) is still the most
relevant/recent description, right?
I t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, Aug 11, 2022 at 11:30:50AM +0200, Martin Holst Swende wrote:
>
> On 8/11/22 10:59, Demi Marie Obenour wrote:
> > On Thu, Aug 11, 2022 at 09:07:22AM +0200, Martin Holst Swende wrote:
> >
> > >>> Happy to try out any suggestion/experiment.
>
On 8/11/22 10:59, Demi Marie Obenour wrote:
On Thu, Aug 11, 2022 at 09:07:22AM +0200, Martin Holst Swende wrote:
>>> Happy to try out any suggestion/experiment.
>>
>> 1. Does i915.enable_psr2_sel_fetch=0 help?
> No, no change that I can see.
Okay, so that is not the problem.
>> 2. What X11
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, Aug 11, 2022 at 09:07:22AM +0200, Martin Holst Swende wrote:
>
> > > Happy to try out any suggestion/experiment.
> >
> > 1. Does i915.enable_psr2_sel_fetch=0 help?
>
> No, no change that I can see.
Okay, so that is not the problem.
> > 2
> Happy to try out any suggestion/experiment.
1. Does i915.enable_psr2_sel_fetch=0 help?
No, no change that I can see.
2. What X11 driver is Xorg using? If it is using Intel, does
modesetting help? If it is using modesetting, does Intel help?
More full logs/notes can be found at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, Aug 10, 2022 at 08:36:33AM +0200, Martin Holst Swende wrote:
>
> On 8/10/22 05:10, Demi Marie Obenour wrote:
> > On Tue, Aug 09, 2022 at 08:11:35PM +0200, Martin Holst Swende wrote:
> > > Some follow-up. I tested also with a Fedora LiveCD, r
On 8/10/22 05:10, Demi Marie Obenour wrote:
On Tue, Aug 09, 2022 at 08:11:35PM +0200, Martin Holst Swende wrote:
> Some follow-up. I tested also with a Fedora LiveCD, results are on
the gist
(here:https://gist.github.com/holiman/83c76e4cd98d087719773486a77d9112#file-fedora-live-txt
> ) .
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, Aug 09, 2022 at 08:11:35PM +0200, Martin Holst Swende wrote:
> Some follow-up. I tested also with a Fedora LiveCD, results are on the gist
> (here:https://gist.github.com/holiman/83c76e4cd98d087719773486a77d9112#file-fedora-live-txt
> ) .
>
Some follow-up. I tested also with a Fedora LiveCD, results are on the
gist
(here:https://gist.github.com/holiman/83c76e4cd98d087719773486a77d9112#file-fedora-live-txt
) .
The Fedora livecd worked flawlessly, both wifi-wise and graphics-wise.
It was a fedora 36 -- whereas dom0 is still on Fed
On 2/11/22 21:24, Sven Semmler wrote:
I also recognized that there are currently 74 reports marked "R4.1" but
(almost) none of them marked with the respective RC number. I will go through them and
reconstruct the RC number by submission date.
[Done](https://github.com/QubesOS/qubes-hcl/commit
Thank you Steffen (aka @TheGardner) for you R4.1 HCL reports, which are online
now:
* [ThinkPad
P50](https://www.qubes-os.org/hcl/#lenovo_thinkpad-p50-20eqs12q35_i7-6820hq_skylake_integrated-graphics-hd-530-quadro-m1000m)
*
[Nitro-PC](https://www.qubes-os.org/hcl/#nitrokey_nitropc_i7-10610u_co
On 2/2/22 14:36, Ymec Holding B.V. | ICT Department wrote:
Please find attached my HCL report for my T480s 40GB RAM.
Furthermore I noticed an error in the HCL.
A T490s is listed as a T470s I noticed because it mentioned a i7 Whiskey lake
CPU and a T490s type # 20nx000gmz (this is a T490s)
So
Thank you Amadeus for your HCL report, which is
[online](https://www.qubes-os.org/hcl/#lenovo_thinkpad-t480s-20l8sa2v00_i5-8350u_kaby-lake_integrated-graphics-hd-620)
now.
In addition I removed the erroneous HCL entry referring to the ThinkPad model
20nx000gmz as T470s as you suggested. The re
On 1/1/22 01:50, IX4 Svs wrote:
On 31 Dec 2021, at 23:42, IX4 Svs wrote:
I have been using Qubes 4.0.x on this laptop for some time with no major issues
(only sleep/wake doesn't work), so I thought I'd install 4.1-rc3 today.
First impression is that most things work (good resolution to ex
On 12/31/21 6:50 PM, IX4 Svs wrote:
Happy user of 4.1-rc3 so far, even sleep and resume seems to work, which is a
welcome improvement from 4.0.4 on this hardware.
Perfect! Thank you for your HCL report, which is
[online](https://www.qubes-os.org/hcl/#dell_precision-m4800_i7-4900mq_haswell_qua
> On 31 Dec 2021, at 23:42, IX4 Svs wrote:
>
>
> I have been using Qubes 4.0.x on this laptop for some time with no major
> issues (only sleep/wake doesn't work), so I thought I'd install 4.1-rc3 today.
>
> First impression is that most things work (good resolution to external 49''
> monit
Thank you Rifa for this HCL report, which is now
[online](https://www.qubes-os.org/hcl/#lenovo_thinkpad-t14-gen-1-20s0s0qf00_i5-10210u_comet-lake_integrated-graphics-uhd-620).
/Sven
--
public key: https://www.svensemmler.org/2A632C537D744BC7.asc
fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63
One more update: I exchanged the 04W3269 (Toshiba) fan with a 04W3270 (Delta)
fan, which is substantially quieter.
Now the machine is perfect, well worth what it cost.
--
public key: https://www.svensemmler.org/2A632C537D744BC7.asc
fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7
I was thinking about utilizing this beast as a Desktop, but using LibreBoot
instead of CoreBoot. Is that a crazy idea? It is exciting that you got
the NVIDIA GeForce GT 710 to work on this bad boy. Kudos on that... is
there any reason you couldn't use a second one? I would be curious to know
On 9/11/21 08:23, Will Lewis wrote:
I'm using a 1TB 870 Pro
A few days ago I replaced the 870 QVO with a 860 PRO ... what a difference!!!
Learned that lesson for sure.
--
public key: https://www.svensemmler.org/2A632C537D744BC7.asc
fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4B
On 9/14/21 06:58, Billy Lewis wrote:
Other than these issues mentioned above, your fhd mod worked smoothly?
Smoother than any other computer I ever used with Qubes OS. You will love it!
--
public key: https://www.svensemmler.org/2A632C537D744BC7.asc
fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B
Hi Sven,
That's great info, thank you!
Other than these issues mentioned above, your fhd mod worked smoothly? As
in, no need to add change anything during the heads build process?
I will certainly let you know how it went although, I will probably be back
asking more stupid questions in the fu
> Sven wrote:
> > Is there any kernel with which VFIO is supported, or is it simply
> > "VFIO not supported"?
>
> Even with 5.12-9 the kernel logs show "AMD IOMMUv2 functionality not
> available on this system",
> although lspci does show a 1022:1631 device, which recent pci.ids
> identify as "Ren
Hi Will,
I basically used whatever was the HEAD revision of the Heads project at that
time. That worked reasonably well, but a few issues remained:
-> A weird seemingly random data corruption issue when restoring backups [1],
which I cannot reproduce any longer. I suspect either the VRAM chang
Oh I see, okay that's a key piece of info, thank you.
I am not aversed to research but Heads is seeming enigmatic, do you have
any suggestions for guides etc. any advice you could give me would be much
appreciated.
Will I have to add my FHD 1080p screen to the build?
Thanks,
Stacey
On Satur
Coreboot comes as part of heads - so you just build heads and flash that to
the 4mb and 8mb chips inside.
On Sat, 11 Sept 2021 at 14:23, Will Lewis
wrote:
> I have to compliment your taste in hardware, I’m building almost exactly
> the same machine as we speak except for the SSD, I'm using a 1TB
I have to compliment your taste in hardware, I’m building almost exactly
the same machine as we speak except for the SSD, I'm using a 1TB 870 Pro.
Although, I’m entirely new to coreboot and am trying to gather as much info
as possible, I’m at the last stage before flashing but I am struggli
Hey, wanted to say thanks for the tips. The settings you provided gave me a
smooth install.
I wanted to come by and say my webcam, USB-C and MIC worked. The USB-C was
a WD19S dock and at first it wasn't working except to charge my laptop.
After running updates through Qubes it worked after a fe
Hi Jolly, could you please give a complete manual on this setup?
How to make the heads firmware, how to flash it (ME will stop you from
using flashrom -p internal).
Some SPI programming experiments with raspi-pi were not successfull at
least for me. It seems
that the unpowered chipset of the comp
Thank you Ken for your HCL report which is now part of this [pull
request](https://groups.google.com/d/msgid/qubes-users/bd38bc6b-97b6-b81b-7c75-15be35af7009%40npamw.neomailbox.ch)
and will be visible on the website soon!
/Sven
--
public key: https://www.svensemmler.org/2A632C537D744BC7.asc
fi
Does this mean Qubes takes advantage of the TPM built into the Librem 15
Version 4?
On Friday, February 15, 2019 at 3:29:56 PM UTC-8 Matt DeVillier wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Purism Librem 15 v4 HCL attached. All devices functions fully working
> (full IOMMU
On 7/12/21 6:01 PM, ydir...@free.fr wrote:
Not sure how this information can fit in the HCL:)
Thank you for updating! This thread is linked from your HCL report so
others who want to install on the same kind of machine will find your
additional information here.
/Sven
--
public key: https
> I was finally able to boot kernel-latest (running 5.12 now), by
> hiding the dGPU
> from the amdgpu module (with "pci-stub.ids=1002:7340"), and
> installing the linux-firmware
> package from current 4.1 snapshot.
Oh and I forgot, resuming after suspend does not work either,
with 5.12 or 5.4. I
I was finally able to boot kernel-latest (running 5.12 now), by hiding the dGPU
from the amdgpu module (with "pci-stub.ids=1002:7340"), and installing the
linux-firmware
package from current 4.1 snapshot.
We can note that this does not give proper GPU support
even for the iGPU, as dom0 Xorg still
Darren - Could you please provide specific details of how you did this;
appreciate your assistance?
Cheers,
Shuaib
On Friday, 5 May 2017 at 04:54:03 UTC+1 raah...@gmail.com wrote:
> On Thursday, May 4, 2017 at 12:57:56 AM UTC-4, Darren Fix wrote:
> > I replaced the standard Broadcom wireless c
Mb i didn't add the 'YES' in works section of the yml file above ..
On Saturday, July 3, 2021 at 2:33:36 PM UTC Muhammad Abdullah wrote:
> Hello,
> I attach the report... This laptop is sold in many variants by many
> resellers mine is branded *Pc Specialist Recoil 2* .. It is also called *XMG
On 6/10/21 3:12 PM, Sven Semmler wrote:
The one I've used is the i7-3740QM which was recommended by @Plexus.
It's a tiny bit less powerful than the i7-3840QM but about half the
price (if you shop right and not just go for the first listing on Amazon
as I did).
Actually at least in the US the
Awesome work Sven and thank you for being the "one hard t430" guide
collaborator and alpha tester. I have so many permutations of T430 in my
home right now its hard to keep track of them all.
I will get the guide finished soon and change the repo to public so the
community can benefit.,
Cheer
On 6/10/21 2:06 PM, BGW wrote:
I see that on the Nitrokey site that they say the i7 73740 is NOT
QUBES compatible? Did I get that right?
There are three chips we should talk about to clarify this:
i7-3632QM (listed by Nitrokey, not compatible with Qubes OS)
i7-3740QM (the one I used, NOT list
I see that on the Nitrokey site that they say the i7 73740 is NOT QUBES
compatible? Did I get that right?
On Thursday, June 10, 2021 at 6:55:02 AM UTC+10 Ulrich Windl wrote:
> On 6/4/21 1:28 AM, Sven Semmler wrote:
> > A dream has come true!
> >
> > * ThinkPad T430
> > * Coreboot/Heads with TO
I forgot to mention the Nitrokey. But a Libremkey or Yubikey will do the
same job. Whatever you already have or suits your wallet / location etc.
/Sven
--
public key: https://www.svensemmler.org/2A632C537D744BC7.asc
fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7
--
You receive
On 6/9/21 3:54 PM, Ulrich Windl wrote:
How many $$$ (€)?
Laptop:
$244.46 ThinkPad T430
$237.62 i7-3740QM 2.70 GHz
$39.75 CPU Cooling Fan Heatsink (04W3269 0B41088 04X3788)
$84.32 Crucial RAM 16GB Kit (2x8GB) DDR3
$219.99 870 QVO 2TB SSD
$115.50 B140HAN01.3 FHD 1920x1080 High Gamut
On 6/4/21 1:28 AM, Sven Semmler wrote:
A dream has come true!
* ThinkPad T430
* Coreboot/Heads with TOTP & HOTP (Nitrokey)
* ME cleaned & disabled
* Qubes OS R4.0.4 all debian-minimal, memory optimized
Upgrades:
* i7-3740QM
* 16 GB RAM
* 2 TB SSD
* Intel Wireless 7260
* 1080p display
Hmm...:
On 4/30/21 5:07 AM, ydir...@free.fr wrote:
Is it useful to add this information to the HCL entry itself ?
Is there any kernel with which VFIO is supported, or is it simply "VFIO
not supported"?
/Sven
--
public key: https://www.svensemmler.org/0x8F541FB6.asc
fingerprint: D7CA F2DB 658D 89BC
Hello Vincent,
How is the P15v holding up with Qubes over the past few months?
Thanks
Bill
On Friday, February 12, 2021 at 5:49:42 AM UTC-5 Vincent Bernaud [FR] wrote:
> Hi,
>
> After hours trying to troubleshoot a black screen before the installer
> shows up (Xen is relinquishing VGA consol
> > The two big issues in this report (aside for the need to modify the
> > config in
> > the install media, which is not obviously transposable to 4.1
> > snapshots) are
> > the lack of detection of TPM and SLAT. Will be happy to help with
> > these.
>
> Another issue is that the default 5.4 ker
> The two big issues in this report (aside for the need to modify the
> config in
> the install media, which is not obviously transposable to 4.1
> snapshots) are
> the lack of detection of TPM and SLAT. Will be happy to help with
> these.
Another issue is that the default 5.4 kernel does not sup
Sven
I just saw your reply. Finally, something that works. I settled on this
configuration, in case it helps anyone else. Thank you very much.
\-> remove \`gnome-settings-daemon\` from template(s)/some dependencies removed
also
\-> in templates add:
/etc/X11/Xresources (Fedora/Dom0) Xft.dpi:
Thank You So Much
I have question Does Sys-usb work!?
On Tuesday, August 20, 2019 at 5:46:41 PM UTC+3 Maximilian Ehlers wrote:
> Everything seems to work fine when setting TPM to `Discrete TPM 1.2` in
> the BIOS.
>
> One note is that the bluetooth is integrated into the Wifi card and
> cant be p
I've resolved the sound issue:
1. I've experimented in a Debian qube with dequbesed pulseaudio (killall
pulseaudio && sleep 1 && pulseaudio --exit-idle-time=-1). After running
`pacmd list-cards`, I read the output and ran pacmd set-card-profile
, which made it working.
2. After whole Qubes re
Update: Everything seems to work now! The system suspends and recovers
correctly. The cursor lag has disappeared. Another problem of slow, choppy
video and no audio has also disappeared. The system has been working
correctly for about 2 months now. I suppose one of the updates resolved the
prob
Always forget the attachments :-[
On 2021-02-13 00:05, KGalante wrote:
Hello All,
System runs pretty smooth once I did the general update and got the
latest kernel. Does not have TPM.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
Hello, I have an XPS9310 and I'm in a very similar situation with AX500.
Any news there?
Also, audio does not work. I'm running qubes 4.0.4 and It used to work
until I upgraded to kernel 5.10.13-1. I have absolutely no experience with
kernel building, any possible further detail you could share
Hello,
I wanted to knife if you could make my device also compatible. Below you
can find with all of my hardware info.
https://jpst.it/2psKG
-AP
Le jeudi 12 octobre 2017 à 18:58:29 UTC, Paul Mosier a écrit :
> Hello,
>
> I'm happy to report that Lenovo 720 will run Qubes. HCL report is
> a
Ok, I just found small solution for stable display without artifacts and
blackouts. But I think hardware rendering is still of. May be I´ll get a
hint here.
For making it stable I found following solution:
https://github.com/QubesOS/qubes-issues/issues/6311
Stephan Hagen schrieb am Mittwoch,
Hello all,
I got it running on Intel NUC10FNH and use already latest kernel and
network is up and find.
Can you give me a hint what you want to tell with
" - check GPU driver provides a better resolution (>= full HD display), "
I have already 4k resolution but only software rendering.
My xorg.0
I might add that at first after installing it gave me a black screen with a
blinking prompt. to fix this issue I had to go in the BIOS and change the UEFI
settings which had a choice between "windows systems" and "others"
De : Stat Pow
Envoyé : 18 janvier 2021 08:
On 1/7/21 10:12 AM, superiorimmunity wrote:
Though it seems that page doesn't exist anymore, there is page with
similar instructions
Thank you! I will point your post with the next update of the HCL.
/Sven
--
public key: https://www.svensemmler.org/0x8F541FB6.asc
fingerprint: D7CA F2DB 658D
On Wednesday, December 30, 2020 1:15 AM, Sven Semmler
wrote:
> On 12/29/20 3:52 AM, Max Parker wrote:
>
> > dell link no longer works:(
>
> @ADW: what do we want to do in such a case? Already checked the internet
> archive and couldn't find any cached versions.
>
> /Sven
>
Though it seems t
if you only have the main qubes repo enabled, running qubes-dom0-update
kernel-latest should install v5.8.16. 5.9 and upcoming 5.10 builds can be
found in current-testing, though the latter has yet to land.
On Tuesday, January 5, 2021 at 7:50:38 AM UTC haa...@web.de wrote:
> On 1/4/21 11:39 PM,
On 1/4/21 11:39 PM, 'awokd' via qubes-users wrote:
tv.f...@gmail.com:
How did you install the 5.8.16 kernel? When I do something like
$ qubes-dom0-update kernel-lateat-5.8.16
it shows me the package, downloads it, but then it tells me "no package
kernel-latest-5.8.16 available" so I'm a bit c
tv.f...@gmail.com:
How did you install the 5.8.16 kernel? When I do something like
$ qubes-dom0-update kernel-lateat-5.8.16
it shows me the package, downloads it, but then it tells me "no package
kernel-latest-5.8.16 available" so I'm a bit confused.
See https://www.qubes-os.org/doc/software
Hey, i was wondering if you had any issues while actually installing qubes
or right after, namely when you go to "reboot" the device right after you
have successfully installed qubes through means of the installer.
On Monday, July 1, 2019 at 9:26:25 PM UTC-5 vjudge one wrote:
> All works great
Actually one more thing - to get the suspend working, I had to add this to
xen.cfg (to the "kernel" line)
mem_sleep_default=deep
regards
On Saturday, January 2, 2021 at 9:27:40 PM UTC+1 tv.f...@gmail.com wrote:
>
> Hi,
>
> I'm successfully running Qubes on the model with i7-9750 CPU and and
>
Yeah,
I think I'm having the same issue - I do see the login screen, but the
upper half of the screen is just black. Switching to console and back fixes
that and I can log in, but then there' are random glitches on parts of the
screen/windows, etc. Disabling compositor mostly fixed that, but no
On 12/29/20 5:15 PM, Sven Semmler wrote:
On 12/29/20 3:52 AM, Max Parker wrote:
dell link no longer works:(
@ADW: what do we want to do in such a case? Already checked the internet
archive and couldn't find any cached versions.
/Sven
If a link is dead and there's no archive.org version,
On 12/29/20 3:52 AM, Max Parker wrote:
dell link no longer works:(
@ADW: what do we want to do in such a case? Already checked the internet
archive and couldn't find any cached versions.
/Sven
--
public key: https://www.svensemmler.org/0x8F541FB6.asc
fingerprint: D7CA F2DB 658D 89BC 08D6 A
dell link no longer works :(
On Friday, November 16, 2018 at 2:18:30 PM UTC-8 Tony Adams wrote:
> I was able to get TPM working by downgrading from the default TPM v2.0
> firmware to TPM v1.2.
>
> [user@personal dom0]$ cat tpm_version.txt
> TPM 1.2 Version Info:
> Chip Version: 1.2.5.81
> Spec Le
yml was corrupt in last post. Here's it in plaintext:
=
---
layout:
'hcl'
type:
'notebook'
hvm:
'yes'
iommu:
'yes'
slat:
'yes'
tpm:
'unknown'
remap:
'yes'
brand: |
HP
model: |
HP ProBook 450 G7
bios: |
S71 Ver. 01.05.04
cpu: |
Attaching HCL Support Files after attempting with the latest development
release of QubesOS at the time of writing = Qubes Release 4.0.4-rc1
All of the same issues are present as with the latest stable release.
QubesOS is *not* compatible with the HP ProBook 450 G7.
--
You received this message
for those with the XPS 13 9370 do you have the Killer Wireless card - and
if so, any driver issues?
On Wednesday, 18 March 2020 at 13:26:13 UTC+1 dcoo...@gmail.com wrote:
> I also have a XPS 13 9370 and running the latest bios and qubes 4.0 but
> suspend does not work ...MORLAN, are you saying
A26 BIOS?!
Are you sure? A16 is more plausible.
Cheers,
Ludwig
On Thursday, December 10, 2020 at 2:29:37 PM UTC Sergey Bezugliy wrote:
>
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving email
I decided to go back and get the "support" file, attached.
I also noticed the recent thread on qubes-users about the kernel 5.4.
However, when I tried this kernel, Qubes OS was completely unusable:
starting from the point where the OS-level boot log would normally
appear ("Starting service X...",
Thank you for your information.
Okay, I will let the HCL maintainer determine.
Thanks and Best Regards,
On Mon, Nov 23, 2020 at 2:37 PM Andrew David Wong wrote:
> On 11/23/20 2:55 AM, Raja Saham wrote:
> > May I know the procedure to add this report into hardware compatibility
> > list ?
>
> T
On 11/23/20 2:55 AM, Raja Saham wrote:
May I know the procedure to add this report into hardware compatibility
list ?
Thank you for your report!
Our HCL maintainer periodically collects all reports sent to this
mailing list and submits them in a pull request to:
https://github.com/QubesOS/q
May I know the procedure to add this report into hardware compatibility
list ?
And whether it is qualified for the list ?
On Monday, November 23, 2020 at 5:44:13 PM UTC+7 Raja Saham wrote:
> Dear Qubes Users,
>
> I have tried Qubes on my System.
> Attached is the report for Hardware Compati
On 10/31/20 11:55 PM, Alex Smirnoff wrote:
I had to update it first. Also, removed rhgb to get around the password
prompt bug.
What an amazing system! I installed it to evaluate if it is suitable for
our company environment and instantly fell in love with it. However, the
answer to my main questi
I had to update it first. Also, removed rhgb to get around the password
prompt bug.
What an amazing system! I installed it to evaluate if it is suitable for
our company environment and instantly fell in love with it. However, the
answer to my main question is still "no" :(. Unless we buy certif
Le 30/10/2020 à 19:52, Alex Smirnoff a écrit :
Now, that's strange! my dom0 is on the latest kernel, but sys-net is
not, so, no network there.
Its normal, all VMs keep the default kernel, not the latest.
You should change the sys-net VM kernel to latest:
- open Qube Manager
- select sys-net
Now, that's strange! my dom0 is on the latest kernel, but sys-net is not,
so, no network there.
>
>
--
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
1 - 100 of 507 matches
Mail list logo
