Re: reportbug - don't know what package to cite

2023-07-29 Thread Brian
On Sat 29 Jul 2023 at 11:35:00 -0500, Will Stites wrote:

> Hi. I tried to use reportbug to um, report a bug, but I don't know what
> package is at fault.

Maybe it's a bug; maybe it's not. I have three similar thin clients (t630)
and other ones that do not give any problem.. I would concentrate on getting
yours into shape.
 
> Briefly, I installed Debian 12 using debian-12.0.0-amd64-netinst.iso on a
> Hewlett-Packard T620 thin client. The installation went all right and the
> system booted into Bookworm. After doing some setup, I shut down
> (correctly). Next time I started the machine, it indicated a hardware
> failure. Machine would not respond to keys to invoke system info, BIOS
> setup, or self-tests.
> 
> Tried again with a second instance of the T620. Same result, except this
> time after the apparent hardware failure, I was able to reach the BIOS setup
> and on the advice from an expert on Debian User Forums ("lewulff"),
> installed Debian 11, D-11 is working great. lewulff said that he has noticed
> a difference in how Debian 12 vs. 11 works with UEFI.
> 
> I believe that the developers will want to fix this - maybe they're already
> aware of the issue, but I don't know how to tell.

D-11 works. Upgrade it to D-12 and see what happens.

-- 
Brian.



Re: reportbug - don't know what package to cite

2023-07-29 Thread piorunz

On 29/07/2023 17:35, Will Stites wrote:

Hi. I tried to use reportbug to um, report a bug, but I don't know what
package is at fault.

Briefly, I installed Debian 12 using debian-12.0.0-amd64-netinst.iso on
a Hewlett-Packard T620 thin client. The installation went all right and
the system booted into Bookworm. After doing some setup, I shut down
(correctly). Next time I started the machine, it indicated a hardware
failure. Machine would not respond to keys to invoke system info, BIOS
setup, or self-tests.

Tried again with a second instance of the T620. Same result, except this
time after the apparent hardware failure, I was able to reach the BIOS
setup and on the advice from an expert on Debian User Forums
("lewulff"), installed Debian 11, D-11 is working great. lewulff said
that he has noticed a difference in how Debian 12 vs. 11 works with UEFI.

I believe that the developers will want to fix this - maybe they're
already aware of the issue, but I don't know how to tell.

Best regards,
Will Stites



If you power cycle for a minute, does it work again? Or it is
permanently broken?
If you remove storage media (HDD or SSD or whatever you have there),
does anything change?
This could be a BIOS bug in older hardware, PC is hanging if put in
"incorrect" state, and it remains in it until power cycled. Old PCs
often have trouble recognizing UEFI installs and other more modern
things, I've seen weird PCs hanging completely on BIOS screen when USB
stick with UEFI liveCD distro is inserted.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄



reportbug - don't know what package to cite

2023-07-29 Thread Will Stites
Hi. I tried to use reportbug to um, report a bug, but I don't know what 
package is at fault.


Briefly, I installed Debian 12 using debian-12.0.0-amd64-netinst.iso on 
a Hewlett-Packard T620 thin client. The installation went all right and 
the system booted into Bookworm. After doing some setup, I shut down 
(correctly). Next time I started the machine, it indicated a hardware 
failure. Machine would not respond to keys to invoke system info, BIOS 
setup, or self-tests.


Tried again with a second instance of the T620. Same result, except this 
time after the apparent hardware failure, I was able to reach the BIOS 
setup and on the advice from an expert on Debian User Forums 
("lewulff"), installed Debian 11, D-11 is working great. lewulff said 
that he has noticed a difference in how Debian 12 vs. 11 works with UEFI.


I believe that the developers will want to fix this - maybe they're 
already aware of the issue, but I don't know how to tell.


Best regards,
Will Stites