Hello,
I am trying to figure out a problem with my UEFI boot not working
anymore using snapshots. I am able to UEFI boot from USB install disk,
but at first boot from the main disk the sequence stops at efi0 entry.
Can someone, please, explain why efi0 is not detected on boot from the
USB install
On Fri Dec 2, 2022 at 5:52 PM CET, Sven F. wrote:
> On Fri, Dec 2, 2022 at 11:33 AM Stuart Henderson
> wrote:
> >
> > On 2022-12-02, Sven F. wrote:
> > > Hello,
> > >
> > > Main problem is the kernel goes into a loop and never break,
> > > so no ddb
> > > I have similar setups (same driver and st
On 12/2/22 16:17, rsyk...@disroot.org wrote:
echo 1 | tee $(tty) | sed 's/1/2/'
Not 100% sure, but probably some timing/subshell issue.
This works:
tty=$(tty) && echo 1 | tee $tty | sed 's/1/2/'
best /m
On Fri, Dec 2, 2022 at 11:33 AM Stuart Henderson
wrote:
>
> On 2022-12-02, Sven F. wrote:
> > Hello,
> >
> > Main problem is the kernel goes into a loop and never break,
> > so no ddb
> > I have similar setups (same driver and stack) , and this one only
> > is more prone to the error, even if the
On 2022-12-02, Sven F. wrote:
> Hello,
>
> Main problem is the kernel goes into a loop and never break,
> so no ddb
> I have similar setups (same driver and stack) , and this one only
> is more prone to the error, even if the virt / qemu driver is partly
> responsible
> the kernel should not loop
rsyk...@disroot.org writes:
> Dear list,
>
> ...
>
> but this does not work:
>
> odin:~$ echo 1 | tee $(tty) | sed 's/1/2/'
> 2
> odin:~$
>
> I do not understand why...
The position of the tty command in the pipeline means that its
standard input is not the terminal:
$ echo $(tty)
Martijn van Duren wrote:
> >
> > odin:~$ echo 1 | tee $(tty) | sed 's/1/2/'
>
> tty(1) is one of the shorter applications, so it's easy to see what it
> does:
> t = ttyname(STDIN_FILENO);
> if (!sflag)
> puts(t ? t : "not a tty");
>
> Since $(tty) is part of the
On Fri Dec 2, 2022 at 3:54 PM CET, Sven F. wrote:
> Hello,
>
> Main problem is the kernel goes into a loop and never break,
> so no ddb
> I have similar setups (same driver and stack) , and this one only
> is more prone to the error, even if the virt / qemu driver is partly
> responsible
> the ker
On Fri, 2022-12-02 at 16:17 +0100, rsyk...@disroot.org wrote:
> Dear list,
>
>
> I needed to show the stdout of a command as well as pass
> it to another command's stdin. This works:
>
> odin:~$ echo 1 | tee /dev/stderr | sed 's/1/2/'
> 1
> 2
> odin:~$
>
> and this works, too:
>
> odin:~$ echo
Dear list,
I needed to show the stdout of a command as well as pass
it to another command's stdin. This works:
odin:~$ echo 1 | tee /dev/stderr | sed 's/1/2/'
1
2
odin:~$
and this works, too:
odin:~$ echo 1 | tee /dev/ttyp8 | sed 's/1/2/'
1
2
odin:~$
where /dev/ttyp8 is the result of the tty
Hello,
Main problem is the kernel goes into a loop and never break,
so no ddb
I have similar setups (same driver and stack) , and this one only
is more prone to the error, even if the virt / qemu driver is partly responsible
the kernel should not loop the `scsi_xfer pool exhausted`
message for eve
On Fri, Dec 02, 2022 at 10:05:12AM -, Stuart Henderson wrote:
> On 2022-12-02, Heppler, J. Scott wrote:
> > I'm shopping for a faster (300mbps +) PCIe wireless card. Although I'm
> > leaning intel, realtek's base firmware is an advantage.
> > V2 of the TP-LINK TL-WN881ND uses rtl8192ee chipse
On 2022-12-02, Heppler, J. Scott wrote:
> I'm shopping for a faster (300mbps +) PCIe wireless card. Although I'm
> leaning intel, realtek's base firmware is an advantage.
> V2 of the TP-LINK TL-WN881ND uses rtl8192ee chipset which was in the
> separate sysutils/firmware builds:
>
> @comment $Open
On Fri Dec 2, 2022 at 12:14 AM CET, Joel Carnat wrote:
> Hi,
>
> About once a week, Xorg freezes while I'm using my ThinkPad A485 with OpenBSD
> 7.2. I've tried switching the window manager (XFCE, Gnome, WindowMaker, cwm)
> but it still happens. I only have a few apps opened (Firefox ESR, a term
14 matches
Mail list logo
