On Mon, 2023-01-23 at 19:54 -0800, Matthew McAllister wrote:
> Coincidentally, this is also exactly when the bluetooth on my motherboard
> stopped working. (The WiFi is on the same MT7921K chipset and still works
> weirdly).
>
> Can you suggest any steps other than straight-up RMA'ing the mobo?
On Mon, 2023-01-23 at 19:54 -0800, Matthew McAllister wrote:
> > Also, looking at old kernel logs from back when it was working
> > would be useful (/var/log/kernel.N.gz where N if the biggest number
> > there is). Hopefully that will show what device is on usb 1-5
> > (though I believe port number
Hi,
piorunz wrote:
> Today, kernel 5.10, Debian 11 Bullseye, and problem still exists :D
>
> $ lsblk -b -o VENDOR,MODEL,SIZE /dev/sr0
> VENDOR MODELSIZE
> hp hp_DVDRW_GUE1N 1073741312
Now that's a strange size: 1 GiB - 512 bytes.
The readable data capacity of an optical dr
On Mon, 2023-01-23 at 19:54 -0800, Matthew McAllister wrote:
> > Also, looking at old kernel logs from back when it was working
> > would be useful (/var/log/kernel.N.gz where N if the biggest number
> > there is). Hopefully that will show what device is on usb 1-5
> > (though I believe port number
Greg Wooledge wrote:
> On Mon, Jan 23, 2023 at 01:51:08PM +, Richmond wrote:
>> I didn't test it for the reason I stated. I think it would be better for
>> OP to test it as he won't do any more damage than he has already done.
> Here's how you can reproduce the problem without having to worry
>
Le 1/19/23 à 7:50 PM, Mario Marietto a écrit :
[...] Do you know if the boot environments of FreeBSD include a graphical boot
menu ? Because this is the added value that I'm looking for. I would like to
skip and save some time by avoiding some command line tasks.
I have no idea on that topic,
a
On Tue, 2023-01-24 at 11:52 +0100, Yassine Chaouche wrote:
> Le 1/19/23 à 7:50 PM, Mario Marietto a écrit :
> [...] Do you know if the boot environments of FreeBSD include a
> graphical boot menu ? Because this is the added value that I'm
> looking for. I would like to skip and save some time by av
Jeff wrote:
>On Sun, Jan 22, 2023 at 9:51 PM Russell L. Harris wrote:
>
>> 2) So I turn on Secure Boot?
>
>I recommend turning SecureBoot off.
>
> - UEFI
> * GPT = on
> * SecureBoot = off
>
>And legacy modes, like BIOS legacy = off.
>
>In SecureBoot, the only thing that is attested are th
On Tue, Jan 24, 2023 at 12:12:53PM +, Steve McIntyre wrote:
[...]
> >The biggest accomplishment SecureBoot achieved under Windows 8 was
> >locking out other operating systems. And that did not last very long.
>
> Sigh. Secure Boot also does a reasonable job of blocking persistent
> pre-boot
For the time being,
here are the proposed solutions :
1. opensuse's snapper
2. Guix
3. nixos
4. Amanda
5. Ubuntu with ZoL (ZFS on Linux)
6. ZFS boot menu
Mario, Anssi, Christoph, David, DdB, Gene, Jeffrey:
Thank you all for your providing feedback!
Best,
--
yassine -- sysadm
+213-779 06 06 23
Yassine,if you think that you will not love FreeBSD only because you have
seen your friend put his hands in his hair,you are interpreting the
situation too severely. FreeBSD is a good OS,easier than Linux and which
doesn't have all the unnecessary superstructure that Linux has, but offers
almost al
On 2023-01-22 23:27:11 -0600, David Wright wrote:
> On Mon 23 Jan 2023 at 04:15:38 (+0100), Vincent Lefevre wrote:
> > On 2023-01-21 23:04:30 -0600, David Wright wrote:
> >
> > > In this case, if I paste the large file, I do see almost the start
> > > of the file (I seem to lose just the first lin
Le 1/24/23 à 3:20 PM, Mario Marietto a écrit :
Yassine,if you think that you will not love FreeBSD only because you have seen
your friend put his handsin his hair,you areinterpreting the situation too
severely. FreeBSD is a good OS,easier than Linux andwhich doesn't have all the
unnecessarysup
On 2023-01-22 23:27:27 -0600, David Wright wrote:
> On Mon 23 Jan 2023 at 03:17:43 (+0100), Vincent Lefevre wrote:
> > On 2023-01-22 11:33:57 +0100, Sven Joachim wrote:
> > > This might be a limitation of Linux's pty(7) subsystem. The xterm
> > > manpage mentions the following:
> > >
> > > ,
On 2023-01-22 15:35:08 -0500, Greg Wooledge wrote:
> It doesn't work, presumably for the same reason that Ctrl-C doesn't work.
> The xterm's pty's input buffer is full, and it simply ignores all keyboard
> input from that point forward.
They are actually not ignored, but delayed by the terminal em
On 2023-01-24 10:03:31 +, Richmond wrote:
> No that wasn't the entire point of the thread. The OP didn't know the
> cause, it was presumed by David Wright that it was caused by the buffer
> filling up. But it could have been caused by some spurious character in
> the file, e.g. ctrl-s.
I know
On Tue 24 Jan 2023 at 17:18:17 (+0100), Vincent Lefevre wrote:
> On 2023-01-22 15:35:08 -0500, Greg Wooledge wrote:
> > It doesn't work, presumably for the same reason that Ctrl-C doesn't work.
> > The xterm's pty's input buffer is full, and it simply ignores all keyboard
> > input from that point
On Tue 24 Jan 2023 at 10:03:31 (+), Richmond wrote:
> Greg Wooledge wrote:
> > On Mon, Jan 23, 2023 at 01:51:08PM +, Richmond wrote:
> >> I didn't test it for the reason I stated. I think it would be better for
> >> OP to test it as he won't do any more damage than he has already done.
> >
On Tue 24 Jan 2023 at 16:17:32 (+0100), Vincent Lefevre wrote:
> On 2023-01-22 23:27:27 -0600, David Wright wrote:
> > On Mon 23 Jan 2023 at 03:17:43 (+0100), Vincent Lefevre wrote:
> > > On 2023-01-22 11:33:57 +0100, Sven Joachim wrote:
> > > > This might be a limitation of Linux's pty(7) subsyste
On Tue 24 Jan 2023 at 15:34:49 (+0100), Vincent Lefevre wrote:
> On 2023-01-22 23:27:11 -0600, David Wright wrote:
> > On Mon 23 Jan 2023 at 04:15:38 (+0100), Vincent Lefevre wrote:
> > > On 2023-01-21 23:04:30 -0600, David Wright wrote:
> > >
> > > > In this case, if I paste the large file, I do
On 2023-01-24 10:34:01 -0600, David Wright wrote:
> On Tue 24 Jan 2023 at 17:18:17 (+0100), Vincent Lefevre wrote:
> > On 2023-01-22 15:35:08 -0500, Greg Wooledge wrote:
> > > It doesn't work, presumably for the same reason that Ctrl-C doesn't work.
> > > The xterm's pty's input buffer is full, and
On Tue, Jan 24, 2023 at 10:34:01AM -0600, David Wright wrote:
> On Tue 24 Jan 2023 at 17:18:17 (+0100), Vincent Lefevre wrote:
> > On 2023-01-22 15:35:08 -0500, Greg Wooledge wrote:
> > > It doesn't work, presumably for the same reason that Ctrl-C doesn't work.
> > > The xterm's pty's input buffer
On 2023-01-24 10:36:05 -0600, David Wright wrote:
> On Tue 24 Jan 2023 at 15:34:49 (+0100), Vincent Lefevre wrote:
[...]
> > For instance, if I paste the following 3 lines
> >
> > foo1
> > foo2
> > foo3
> >
> > in dash, I get:
> >
> > $ foo1
> > foo2
> > foo3
> > sh: 1: foo1: not found
> > $ sh:
On Mon, 23 Jan 2023, Celejar wrote:
Thank you - the plot thickens. I tried radvdump, and I was indeed
receiving IPv6 advertisements. I inspected my router (an OpenWrt box)
more carefully, and lo and behold, the router *thinks* that it has IPv6
connectivity: it reports that it has configured its
Hi,
the log messages about "unaligned transfer" would be explained if indeed
the block size of the drive would be mistaken as 512 bytes rather than
2048 bytes.
So it might be interesting to let lsblk report "sector" sizes as perceived
by the kernel:
lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SE
On Tue, Jan 24, 2023 at 06:41:56PM +, Tim Woodall wrote:
> On Mon, 23 Jan 2023, Celejar wrote:
>
> > Thank you - the plot thickens [...]
> It's depressingly common to find people who block icmp for 'security
> reasons'. While you can mostly get away with that in ipv4, ipv6 breaks
> catastroph
On Tue, 24 Jan 2023 18:41:56 + (GMT)
Tim Woodall wrote:
> On Mon, 23 Jan 2023, Celejar wrote:
>
> > Thank you - the plot thickens. I tried radvdump, and I was indeed
> > receiving IPv6 advertisements. I inspected my router (an OpenWrt box)
> > more carefully, and lo and behold, the router *t
On Tue, 24 Jan 2023, to...@tuxteam.de wrote:
On Tue, Jan 24, 2023 at 06:41:56PM +, Tim Woodall wrote:
On Mon, 23 Jan 2023, Celejar wrote:
Thank you - the plot thickens [...]
It's depressingly common to find people who block icmp for 'security
reasons'. While you can mostly get away wit
Also, just try booting using linux 6.0 to see if that fixes anything. That
still seems to available, so if you uninstalled it, it can be reinstalled.
That is great advice, but before starting the thread I had already tried
booting 5.10, 5.19, 6.0, and 6.1 to no avail.
I was running 6.0.0-4-am
On Tue, Jan 24, 2023 at 09:24:25PM +, Tim Woodall wrote:
> On Tue, 24 Jan 2023, to...@tuxteam.de wrote:
[...]
> > IPv4, too, does funny things when dropping ICMP. Path MTU discovery,
> > breaks, for one.
> >
> Indeed. Hence the --clamp-mss-to-pmtu magic in iptables.
More magic :)
Cheers &
I am having trouble with php8.1-fpm commanded from nginx on a bullseye
system
php8.1-fpm reports access denied when opening a specific file for the
application. The file has universal rwx permissions (after attempting to
fix problem). I am not running selinux but I do see some references to
a
On Wed, Jan 25, 2023 at 02:51:05PM +0800, jeremy ardley wrote:
[...]
> 0.41 lstat("/var/www/grammartiste.com/web/vendor/autoload.php",
> 0x7fffdc580970) = -1 EACCES (Permission denied)
> 0.34 lstat("/var/www/grammartiste.com/web/vendor/autoload.php",
> 0x7fffdc57f900) = -1 EAC
On 25/1/23 15:33, to...@tuxteam.de wrote:
On Wed, Jan 25, 2023 at 02:51:05PM +0800, jeremy ardley wrote:
[...]
0.41 lstat("/var/www/grammartiste.com/web/vendor/autoload.php",
0x7fffdc580970) = -1 EACCES (Permission denied)
0.34 lstat("/var/www/grammartiste.com/web/vendor/a
On 25/1/23 15:44, jeremy ardley wrote:
On 25/1/23 15:33, to...@tuxteam.de wrote:
On Wed, Jan 25, 2023 at 02:51:05PM +0800, jeremy ardley wrote:
[...]
0.41
lstat("/var/www/grammartiste.com/web/vendor/autoload.php",
0x7fffdc580970) = -1 EACCES (Permission denied)
0.34
ls
34 matches
Mail list logo
