Answer to David
>I presume that you have unlocked it successfully in the past.
Yes, I have.
>Is there anything on your system(s) that has changed, and could have
>affected how the keyboard language and layout is defined?
>This is particularly important if your passphrase contains accented
On Sat, Aug 28 2021, Cindy Sue Causey wrote:
> On 8/26/21, Roland Winkler wrote:
>> I am running debian 10 (buster with xfce). Graphics works fine
>> initially. Yet after an X screen lock, all colors are messed up.
>> The same hardware was previoulsy running fine when I was xubuntu 16.04.
>>
David Christensen wrote:
> You want to watch the test run, so that you can monitor
> progress, make adjustments, and/or stop it if things
> go badly.
Don't worry about it...
Here are the 20 first lines of the output:
time, governor, processes, CPU temperature C, system load, CPU fan speed RPM,
David Wright wrote:
> On Sat 28 Aug 2021 at 08:36:32 (-0400), songbird wrote:
...
>> just to note that using "bookworm" in your subject line can
>> give the implication that "bookworm" is actually released which
>> it hasn't. it is much better to use the keyword "testing" in
>> the subject line
Did work 15 years ago, but despite a new PCI-E firewire card, does not
now work with kino, no remote controls.
kino does recognize the device in it prefs and calls it by its name, a
DCR-TRV460NTSC.
What do I do to ident the error? It used to work with libraw1394, but
that doesn't seem to be
Did work 15 years ago, but despite a new PCI-E firewire card, does not
now work with kino, no remote controls.
kino does recognize the device in it prefs and calls it by its name, a
DCR-TRV460NTSC.
What do I do to ident the error? It used to work with libraw1394, but
that doesn't seem to be
Hello everybody out there!
On 2021/08/29 at 02:26 am, Roberto C. Sánchez wrote:
> That said, Dan's advice is quite solid: have your mixed environment in a
> VM, chroot, or other virtual environment. When it gets into an unusable
> state (it very likely will at some point, especially as testing
On Sun, Aug 29, 2021 at 02:05:44AM +0200, Yoann LE BARS wrote:
>
> Hello everybody out there!
>
> On 2021/08/29 at 01:25am, Dan Ritter wrote:
> > You can do this. If I didn't care much about the long-term
> > usability of the machine, I would do this.
>
> In other word, this is really not
Hello everybody out there!
On 2021/08/29 at 01:25am, Dan Ritter wrote:
> You can do this. If I didn't care much about the long-term
> usability of the machine, I would do this.
In other word, this is really not recommended, am I right?
Well, the thing is I do care of long-term
Yoann LE BARS wrote:
>
> Usually, I am using Debian stable with backports, and I am quite happy
> with it. However, it turns out I will probably have to test some early
> versions of some software and libraries that are not in backports, such
> as Ardour and SDL2.
>
> Therefore, I
On Sat, 28 Aug 2021 10:19:23 -0400 Jude Informed me about Re:
Network down incorrect
> As part of your reinstall process did you delete all partitions then
> run wipefs -af on the disk? Failure to do so may have left old
> artifacts of the previous system on the drive
Hello everybody out there!
First, I want to thank and congratulate Debian developers for Debian
11. I am about to upgrade to this version.
Usually, I am using Debian stable with backports, and I am quite happy
with it. However, it turns out I will probably have to test some
On Sat, 28 Aug 2021 17:14:29 +0200 Marco Informed me about Re:
Network down incorrect
> On 28.08.21 15:38, Charlie wrote:
> >
> > From my keyboard:
> >
> > Hello all,
> >
> > Since Bullseye went stable, updated on my 12 month old HP
> > laptop. When
On Sat, 28 Aug 2021 10:43:07 -0400 Eike Informed me about Re:
Network down incorrect
> On Samstag, 28. August 2021 09:38:44 -04 Charlie wrote:
> > From my keyboard:
> >
> > Hello all,
> >
> > Since Bullseye went stable, updated on my 12 month old HP
> >
On Sat, 28 Aug 2021 11:39:13 -0500 David Informed me about Re:
Network down incorrect
> On Sat 28 Aug 2021 at 23:38:44 (+1000), Charlie wrote:
> > Since Bullseye went stable, updated on my 12 month old HP
> > laptop. When attempting to bring up the wireless
On 28/08/2021 17:33, Jeffrey Chimene wrote:
Thanks! That was it. I don't know why it never loaded amdgpu; which
forced me to add nomodeset.
Glad I could help! :) So everything is working now, removing this
nomodeset option solved it?
--
With kindest regards, piorunz.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
The problem was that Win10 would constantly overwrite the MBR and blow away
GRUB which forced the computer to boot straight into Windows.
The solution is to go into Windows, open a command prompt/shell as the
Windows administrator and run:
"bcedit /set {bootmgr} path
On Sat 28 Aug 2021 at 15:38:40 -0400, Greg Wooledge wrote:
> On Sat, Aug 28, 2021 at 08:31:56PM +0100, Brian wrote:
> > Nobody should be logging into the web interface as root.
>
> As far as "nobody should...", I don't see the harm. It's not like the
> password is going over a network cable (or
On Sat, Aug 28, 2021 at 08:31:56PM +0100, Brian wrote:
> Nobody should be logging into the web interface as root.
As far as "nobody should...", I don't see the harm. It's not like the
password is going over a network cable (or wireless EM). It's just
loopback.
Also note the official
David Wright wrote:
> On Sat 28 Aug 2021 at 10:34:34 (-0500), Richard Owlett wrote:
>> During the partitioning phase of the install process, the user is
>> given the option of creating dedicated partitions. I chose to do it
>> for /home and swap {depending on machine I may also have a dedicated
>>
On Sat 28 Aug 2021 at 07:11:55 -0700, Peter Ehlert wrote:
>
> On 8/26/21 5:53 AM, Greg Wooledge wrote:
[...]
> > 2) Install cups.
> * cups was not installed by default. The Brother installer did flag that
> first off, easily corrected
A print queue was installed by Sun 22 Aug 2021 05:44:11 AM
On Sat 28 Aug 2021 at 08:36:32 (-0400), songbird wrote:
> Jeffrey Chimene wrote:
>
> just to note that using "bookworm" in your subject line can
> give the implication that "bookworm" is actually released which
> it hasn't. it is much better to use the keyword "testing" in
> the subject line
On Fri 27 Aug 2021 at 21:35:38 (-0500), Intense Red wrote:
>On a new HP Laptop pre-installed with Win10 Home edition installed on an
> SSD. In the laptop's BIOS Secure Boot was turned off.
>
>A fresh copy of Debian 11 was installed into the machine's 1TB HD. After
> reboot, GRUB comes
On Sat 28 Aug 2021 at 10:34:34 (-0500), Richard Owlett wrote:
> During the partitioning phase of the install process, the user is
> given the option of creating dedicated partitions. I chose to do it
> for /home and swap {depending on machine I may also have a dedicated
> project partition}.
>
>
On Sat 28 Aug 2021 at 23:38:44 (+1000), Charlie wrote:
> Since Bullseye went stable, updated on my 12 month old HP
> laptop. When attempting to bring up the wireless interface with
> ifup.
>
> The message on the screen tells me the "network is down", which is
> incorrect.
On 8/28/21 08:56, piorunz wrote:
picasso*.bin files are part of firmware-amd-graphics package.
$ apt-file search picasso_asd.bin
firmware-amd-graphics: /lib/firmware/amdgpu/picasso_asd.bin
These files are present in your system when you package installed.
Their presence doesn't mean that
picasso*.bin files are part of firmware-amd-graphics package.
$ apt-file search picasso_asd.bin
firmware-amd-graphics: /lib/firmware/amdgpu/picasso_asd.bin
These files are present in your system when you package installed.
Their presence doesn't mean that they will get loaded.
I can see in
During the partitioning phase of the install process, the user is given
the option of creating dedicated partitions. I chose to do it for /home
and swap {depending on machine I may also have a dedicated project
partition}.
That the partition phase presents a menu of ~10 choices indicates the
On 8/28/21 07:07, Jeffrey Chimene wrote:
On 8/28/21 07:04, Jeffrey Chimene wrote:
No complaints about missing picasso firmware. I'll try removing the
/lib/firmware to see what happens.
So this doesn't do what I thought it would. It's probably not even
looking for the picasso firmware.
On 28.08.21 15:38, Charlie wrote:
From my keyboard:
Hello all,
Since Bullseye went stable, updated on my 12 month old HP
laptop. When attempting to bring up the wireless interface with
ifup.
The message on the screen tells me the "network is down",
Sembla més aviat el fitxer /etc/ufw/before.rules
que no pas el unit file. Els permisos són els mateixos ?
--
R. Sicart
28 août 2021 16:10:53 Lluís Gras :
> Així sembla ...
>
> Però és que tant en el cas (D10) com en l'altre (D11) el fitxer
> /lib/systemd/system/ufw.service és el mateix
>
>
On Samstag, 28. August 2021 09:38:44 -04 Charlie wrote:
> From my keyboard:
>
> Hello all,
>
> Since Bullseye went stable, updated on my 12 month old HP
> laptop. When attempting to bring up the wireless interface with
> ifup.
>
> The message on the screen tells me
On 8/26/21 5:53 AM, Greg Wooledge wrote:
On Thu, Aug 26, 2021 at 01:37:49PM +0100, Brian wrote:
On Thu 26 Aug 2021 at 13:23:58 +0100, mick crane wrote:
On 2021-08-26 12:59, Peter Ehlert wrote:
On 8/25/21 12:11 PM, Greg Wooledge wrote:
Some people report restarting the browser is enough.
On 8/28/21 07:04, Jeffrey Chimene wrote:
No complaints about missing picasso firmware. I'll try removing the
/lib/firmware to see what happens.
So this doesn't do what I thought it would. It's probably not even
looking for the picasso firmware.
$ sudo update-initramfs -u
update-initramfs:
No complaints about missing picasso firmware. I'll try removing the
/lib/firmware to see what happens.
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for
module r8169
W: Possible missing
As part of your reinstall process did you delete all partitions then run
wipefs -af on the disk? Failure to do so may have left old artifacts of
the previous system on the drive which may be messing up your current
installation.
On Sat, 28 Aug 2021, Charlie wrote:
>
> From my keyboard:
>
On 8/28/21 06:04, piorunz wrote:
On 28/08/2021 13:54, Jeffrey Chimene wrote:
Let me ask more questions, so we all can learn more about your situation
and start suggesting remedies.
Hi,
Thanks for the advice. The problem I'm trying to solve is why the AMD
firmware isn't getting incorporated
On 8/26/21 5:53 AM, Greg Wooledge wrote:
On Thu, Aug 26, 2021 at 01:37:49PM +0100, Brian wrote:
On Thu 26 Aug 2021 at 13:23:58 +0100, mick crane wrote:
On 2021-08-26 12:59, Peter Ehlert wrote:
On 8/25/21 12:11 PM, Greg Wooledge wrote:
Some people report restarting the browser is enough.
Així sembla ...
Però és que tant en el cas (D10) com en l'altre (D11) el
fitxer /lib/systemd/system/ufw.service és el mateix
root@gwbox:~# cat /lib/systemd/system/ufw.service
[Unit]
Description=Uncomplicated firewall
Documentation=man:ufw(8)
DefaultDependencies=no
Before=network.target
From my keyboard:
Hello all,
Since Bullseye went stable, updated on my 12 month old HP
laptop. When attempting to bring up the wireless interface with
ifup.
The message on the screen tells me the "network is down", which is
incorrect. Because on another
Hi piorunz,
Thanks for your interest! I really appreciate your time. Background:
I've been using Debian since Potato. This distro Just Works.
On 8/28/21 06:04, piorunz wrote:
On 28/08/2021 13:54, Jeffrey Chimene wrote:
Let me ask more questions, so we all can learn more about your situation
Bones,
No he fet servir mai ufw, però pel missatge d'error "(nf_tables): Set
Firehol_L1 doesn't exist
" sembla que, quan el servei systemd arranca, Firehol_L1 encara no existeix.
Sort !
signature.asc
Description: PGP signature
El 2021-08-27 a las 10:52 +0200, Roberto Leon Lopez escribió:
> > El 26 ago 2021, a las 18:03, Camaleón escribió:
(...)
> No sé si por precio interesa comprar alguna solución completa de un
> fabricante o montar mi propio NAS.
> >>>
> >>> Este apartado sí que lo tengo claro: montar
On 8/28/21 05:36, songbird wrote:
Jeffrey Chimene wrote:
just to note that using "bookworm" in your subject line can
give the implication that "bookworm" is actually released which
it hasn't. it is much better to use the keyword "testing" in
the subject line instead.
Agreed. However, a
On 28/08/2021 13:54, Jeffrey Chimene wrote:
Let me ask more questions, so we all can learn more about your situation
and start suggesting remedies.
Hi,
Thanks for the advice. The problem I'm trying to solve is why the AMD
firmware isn't getting incorporated in the kernel.
How you assumed
On 8/28/21 05:36, songbird wrote:
Jeffrey Chimene wrote:
just to note that using "bookworm" in your subject line can
give the implication that "bookworm" is actually released which
it hasn't. it is much better to use the keyword "testing" in
the subject line instead.
Agreed. However, a
On 8/28/21 04:28, piorunz wrote:
On 27/08/2021 19:20, Jeffrey Chimene wrote:
Something happened to my amd firmware for a ryzen3 3200g. A few weeks
ago, this machine made an uneventful transition to bookworm.
Great.
I'd
originally installed bullseye and the non-free firmware package to get
Jeffrey Chimene wrote:
just to note that using "bookworm" in your subject line can
give the implication that "bookworm" is actually released which
it hasn't. it is much better to use the keyword "testing" in
the subject line instead.
> Something happened to my amd firmware for a ryzen3
On Sat, Aug 28, 2021, 6:06 AM Joe wrote:
> On Sat, 28 Aug 2021 11:14:28 +0300
> ellanios82 wrote:
>
> > On 28/8/21 Intense Red:
> > > How can Windows be lobotomized
> >
> >
> >- maybe Install VirtualBox, & ONLY run windows inside Linux
> >
> >
>
> The Home version won't be licensed for use
On 27/08/2021 19:20, Jeffrey Chimene wrote:
Something happened to my amd firmware for a ryzen3 3200g. A few weeks
ago, this machine made an uneventful transition to bookworm.
Great.
I'd
originally installed bullseye and the non-free firmware package to get
the firmware for this setup.
On 28/8/21 Intense Red:
How can Windows be lobotomized
- List been real Quiet : No word from the Amazing Polly
.
rgds
.
On 28/8/21 1:06 μ.μ., Joe wrote:
On Sat, 28 Aug 2021 11:14:28 +0300
ellanios82 wrote:
On 28/8/21 Intense Red:
How can Windows be lobotomized
- maybe Install VirtualBox, & ONLY run windows inside Linux
The Home version won't be licensed for use in a VM, and may be
engineered not to
Bones,
Us comento els meus "posters gais" per si algú s'hi ha trobat i em pot
donar un cop de ma, després d'actualitzar a Bullseye em trobo que:
ufw no arrenca i aparentment hauria de fer-ho
lluis@ns:~$ systemctl list-unit-files | grep -i ufw
ufw.serviceenabled
On Sat, 28 Aug 2021 11:14:28 +0300
ellanios82 wrote:
> On 28/8/21 Intense Red:
> > How can Windows be lobotomized
>
>
> - maybe Install VirtualBox, & ONLY run windows inside Linux
>
>
The Home version won't be licensed for use in a VM, and may be
engineered not to work at all in one.
On 8/26/21, Roland Winkler wrote:
> I am running debian 10 (buster with xfce). Graphics works fine
> initially. Yet after an X screen lock, all colors are messed up.
> The same hardware was previoulsy running fine when I was xubuntu 16.04.
> What can be causing this? Thanks!
Hi! I don't have
On 28/8/21 Intense Red:
How can Windows be lobotomized
- maybe Install VirtualBox, & ONLY run windows inside Linux
.
rgds
.
On Fri, 27 Aug 2021 21:35:38 -0500
Intense Red wrote:
>On a new HP Laptop pre-installed with Win10 Home edition installed
> on an SSD. In the laptop's BIOS Secure Boot was turned off.
>
>A fresh copy of Debian 11 was installed into the machine's 1TB HD.
> After reboot, GRUB comes up
Alguien a probado ceph?
https://ceph.com
Saludos.
>
> El 25/08/21 a las 13:07, OddieX escribió:
> > El mié, 25 ago 2021 a las 15:03, OddieX () escribió:
> >> El mié, 25 ago 2021 a las 14:59, JavierDebian
> >> () escribió:
> >>>
> >>>
> >>> El 25/8/21 a las 14:29, Roberto Leon Lopez
On 08/27/2021 09:30 AM, Ottavio Caruso wrote:
> Hi,
>
> $ uname -a
> Linux e130 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64
> GNU/Linux
> $ cat /etc/debian_version
> 10.2
> $ chromium --version
> Chromium 90.0.4430.212 built on Debian 10.9, running on Debian 10.2
>
> For the
59 matches
Mail list logo
