| 29 Oct 2023 |
 @tejing:matrix.org | it's honestly the only keyboard-focused web-browsing solution I've found that doesn't have huge caveats. extensions don't have enough UI control to make it work, things like qutebrowser have too many integration issues. the electron path just seems to work the best | 17:39:46 |
| @tejing:matrix.org | * it's honestly the only keyboard-focused web-browsing solution I've found that doesn't have huge caveats. extensions don't have enough UI control to make it work as it really should, things like qutebrowser have too many integration issues. the electron path just seems to work the best | 17:40:03 |
 @rikudou:lemmings.world | Gonna have to trust you on that, it's so far from my use-case that I can't really form an opinion | 17:41:50 |
|  jacekpoz | 17:43:48 |
| jacekpoz | 17:43:57 |
| jacekpoz | 17:45:01 |
 @atemu12:matrix.org | In reply to @tejing:matrix.org
see https://github.com/Jelmerro/Vieb That looks interesting. Is there something like that but based on Gecko/Spidermonkey? Don't really want to give Google more market share. | 18:01:29 |
| @atemu12:matrix.org | In reply to @tejing:matrix.org
see https://github.com/Jelmerro/Vieb * That looks interesting. Is there something like that but based on Gecko/Spidermonkey? Don't really want to give Google more market share/control over the web. | 18:01:37 |
| @tejing:matrix.org | In reply to @atemu12:matrix.org
That looks interesting. Is there something like that but based on Gecko/Spidermonkey? Don't really want to give Google more market share/control over the web. Not that I'm aware of. | 18:02:42 |
 @2xsaiko:tchncs.de | the only way to use gecko without firefox that I'm aware of is https://github.com/sailfishos/qtmozembed | 18:07:50 |
 K900 | Gecko is, sadly, a huge pain to embed | 18:09:06 |
| @2xsaiko:tchncs.de | mhm | 18:09:16 |
| @rikudou:lemmings.world | In reply to @2xsaiko:tchncs.de
the only way to use gecko without firefox that I'm aware of is https://github.com/sailfishos/qtmozembed I've used SailfishOS until recently, quite nice OS | 19:17:49 |
 ShivaAU | > That looks interesting. Is there something like that but based on Gecko/Spidermonkey? Don't really want to give Google more market share/control over the web.
Ungoogled-Chromium is an option. | 20:44:25 |
| jacekpoz | 20:54:22 |
| jacekpoz | 20:54:33 |
| @atemu12:matrix.org | ShivaAU: That's precisely not an option for that specific case. As long as everyone uses chromiums, Google has control over the web | 20:55:34 |
| @tejing:matrix.org | Atemu: debatable, imo, given chromium is completely forkable if there was sufficient motivation to do so | 21:00:18 |
| @tejing:matrix.org | at any rate, I don't really worry about it because of that | 21:00:35 |
| K900 | Forking Chromium isn't really the problem | 21:07:15 |
| K900 | The problem is the influence Google has on web standards through Chromium | 21:07:28 |
| 30 Oct 2023 |
| K900 | I think someone asked about linux-firmware updates here | 18:49:03 |
| K900 | https://github.com/NixOS/nixpkgs/pull/264420 | 18:49:03 |
| K900 | Here's a linux-firmware update | 18:49:07 |
| 31 Oct 2023 |
| @rikudou:lemmings.world | Anyone knowledgeable about virt-manager, GPU passthrough and all that stuff? I'm trying to setup a Windows VM, I've successfully made the GPU passthrough, now I'm trying to setup looking glass, but as soon as I add the looking glass shared memory, it crashes with qemu: hardware error: vfio: DMA mapping failed, unable to continue | 13:16:46 |
| K900 | There should be more logs around that | 13:17:29 |
| @rikudou:lemmings.world | 2023-10-31 13:10:11.327+0000: Domain id=18 is tainted: high-privileges
char device redirected to /dev/pts/4 (label charserial0)
2023-10-31T13:10:17.898532Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2023-10-31T13:10:17.898596Z qemu-system-x86_64: vfio_dma_map(0x564a7fb7c4a0, 0x383800000000, 0x100000000, 0x7fbae0000000) = -2 (No such file or directory)
2023-10-31T13:10:17.902474Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2023-10-31T13:10:17.902493Z qemu-system-x86_64: vfio_dma_map(0x564a7fb7c4a0, 0x383900000000, 0x2000000, 0x7fbbe5000000) = -22 (Invalid argument)
2023-10-31T13:10:18.062247Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2023-10-31T13:10:18.062272Z qemu-system-x86_64: vfio_dma_map(0x564a7fb7c4a0, 0x383800000000, 0x100000000, 0x7fbae0000000) = -22 (Invalid argument)
2023-10-31T13:10:18.064794Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2023-10-31T13:10:18.064803Z qemu-system-x86_64: vfio_dma_map(0x564a7fb7c4a0, 0x383900000000, 0x2000000, 0x7fbbe5000000) = -22 (Invalid argument)
2023-10-31T13:10:18.068928Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2023-10-31T13:10:18.068942Z qemu-system-x86_64: vfio_dma_map(0x564a7fb7c4a0, 0x383902000000, 0x2000000, 0x7fbc0dffe000) = -22 (Invalid argument)
qemu: hardware error: vfio: DMA mapping failed, unable to continue
| 13:18:40 |
| @rikudou:lemmings.world | Then something like this for every CPU:
CPU #0:
RAX=0000000000000000 RBX=0000000000000003 RCX=0000000000708004 RDX=0000000000000000
RSI=00000000b0708004 RDI=0000000000708004 RBP=000000007fef66df RSP=000000007fef64b0
R8 =0000000000000000 R9 =000000007fef65ff R10=0000000000000001 R11=0000000000000001
R12=0000000000708004 R13=0000000000000003 R14=0000000000000002 R15=0000000000708004
RIP=000000007f230f8b RFL=00000246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
CS =0038 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
SS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
DS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
FS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
GS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
LDT=0000 0000000000000000 0000ffff 00008200 DPL=0 LDT
TR =0000 0000000000000000 0000ffff 00008b00 DPL=0 TSS64-busy
GDT= 000000007f9dc000 00000047
IDT= 000000007f269018 00000fff
CR0=80010033 CR2=0000000000000000 CR3=000000007fc01000 CR4=00000668
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000d00
FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
XMM00=0000000000000000 0000000000000000 XMM01=0000000000000000 0000000000000000
XMM02=0000000000000000 0000000000000000 XMM03=0000000000000000 0000000000000000
XMM04=0000000000000000 0000000000000000 XMM05=0000000000000000 0000000000000000
XMM06=0000000000000000 0000000000000000 XMM07=0000000000000000 0000000000000000
XMM08=0000000000000000 0000000000000000 XMM09=0000000000000000 0000000000000000
XMM10=0000000000000000 0000000000000000 XMM11=0000000000000000 0000000000000000
XMM12=0000000000000000 0000000000000000 XMM13=0000000000000000 0000000000000000
XMM14=0000000000000000 0000000000000000 XMM15=0000000000000000 0000000000000000
| 13:18:59 |
| @rikudou:lemmings.world | In reply to @rikudou:lemmings.world
2023-10-31 13:10:11.327+0000: Domain id=18 is tainted: high-privileges
char device redirected to /dev/pts/4 (label charserial0)
2023-10-31T13:10:17.898532Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2023-10-31T13:10:17.898596Z qemu-system-x86_64: vfio_dma_map(0x564a7fb7c4a0, 0x383800000000, 0x100000000, 0x7fbae0000000) = -2 (No such file or directory)
2023-10-31T13:10:17.902474Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2023-10-31T13:10:17.902493Z qemu-system-x86_64: vfio_dma_map(0x564a7fb7c4a0, 0x383900000000, 0x2000000, 0x7fbbe5000000) = -22 (Invalid argument)
2023-10-31T13:10:18.062247Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2023-10-31T13:10:18.062272Z qemu-system-x86_64: vfio_dma_map(0x564a7fb7c4a0, 0x383800000000, 0x100000000, 0x7fbae0000000) = -22 (Invalid argument)
2023-10-31T13:10:18.064794Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2023-10-31T13:10:18.064803Z qemu-system-x86_64: vfio_dma_map(0x564a7fb7c4a0, 0x383900000000, 0x2000000, 0x7fbbe5000000) = -22 (Invalid argument)
2023-10-31T13:10:18.068928Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2023-10-31T13:10:18.068942Z qemu-system-x86_64: vfio_dma_map(0x564a7fb7c4a0, 0x383902000000, 0x2000000, 0x7fbc0dffe000) = -22 (Invalid argument)
qemu: hardware error: vfio: DMA mapping failed, unable to continue
I get these even without the shared memory block and the VM starts well, it's only when I add the shmem block that it crashes:
<shmem name="looking-glass">
<model type="ivshmem-plain"/>
<size unit="M">32</size>
<address type="pci" domain="0x0000" bus="0x10" slot="0x01" function="0x0"/>
</shmem>
| 13:21:25 |
| K900 | Might be some IOMMU nonsense | 13:21:51 |
