Samuel Sieb wrote:
>You will need a null-modem cable or adapter to connect to another
>computer.
Indeed. I've been working with RS232 for decades, though not much for
the most recent decade. I finally cobbled together a set of DB9-DB25,
gender benders, and DB25 null modem adapter to check this. A
I wrote:
>I have a machine running Fedora 41 which has stopped providing video
>for its console. Of course, the problem could be hardware, but there
>is no clear evidence of that.
Well, now there is clear evidence. I followed up by putting a DVI card
in the machine and, using an adapter, connecti
On Wed, Apr 2, 2025 at 2:31 AM Dave Close wrote:
>
> I have a machine running Fedora 41 which has stopped providing video
> for its console. Of course, the problem could be hardware, but there
> is no clear evidence of that. I am able to access the machine with SSH
> so I know it is working. I don
On 4/2/25 3:14 PM, Dave Close wrote:
Roger Heflin wrote:
And you are using ttyS0 for the serial port and that is the first real
hardware serial port, not the first USB serial port and at boot the
first usb serial port may not even actually exist yet...
The serial-to-USB adapter is attached to
Roger Heflin wrote:
>And you are using ttyS0 for the serial port and that is the first real
>hardware serial port, not the first USB serial port and at boot the
>first usb serial port may not even actually exist yet...
The serial-to-USB adapter is attached to ttyS0 on the problem machine.
The USB
On 4/2/25 4:24 PM, Dave Close wrote:
"George N. White III" wrote:
Try booting a Live USB -- if that gives graphics you know the hardware is
working.
Tried that. It doesn't boot. I think the BIOS on this machine requires
some keyboard entry to select the USB boot. Hard to do without video.
I
On Apr 2, 2025, at 15:48, Dave Close wrote:
> Trying to start X through the SSH (-X) connection, I'm told, "Only
> console users are allowed to run the X server". Trying to start Wayland
> doesn't work either but produces voluminous output. If the serial
> connection worked, it would be a console,
And you are using ttyS0 for the serial port and that is the first real
hardware serial port, not the first USB serial port and at boot the
first usb serial port may not even actually exist yet...
On Wed, Apr 2, 2025 at 3:39 PM Roger Heflin wrote:
>
> you might try adding setterm --blank 0 --power
On Wed, Apr 2, 2025 at 7:24 PM Dave Close wrote:
>
> "George N. White III" wrote:
>
> >Try booting a Live USB -- if that gives graphics you know the hardware is
> >working.
>
> Tried that. It doesn't boot. I think the BIOS on this machine requires
> some keyboard entry to select the USB boot. Hard
Jeffrey Walton wrote:
>> Replace the coin battery on the motherboard.
Robert Moskowitz:
> And replacing that battery normally means Bios setting back to
> manufacture defaults, so make sure to go through ALL the setup options.
>
> Of course, you will have no record of what the settings were bef
On 4/2/25 3:12 PM, Dave Close wrote:
Samuel Sieb wrote:
What is the video device? "lspci" output
The display does not appear in that output.
It must. Probably as something like "VGA compatible controller".
Check "journalctl -b" for lines with "drm" or "modesetting".
kernel: [drm] rade
On 4/2/25 8:35 PM, Jeffrey Walton wrote:
On Wed, Apr 2, 2025 at 7:24 PM Dave Close wrote:
"George N. White III" wrote:
Try booting a Live USB -- if that gives graphics you know the hardware is
working.
Tried that. It doesn't boot. I think the BIOS on this machine requires
some keyboard ent
On 4/2/25 12:48 PM, Dave Close wrote:
Looking through the dmesg output on the problem machine and on another
machine (also Fedora 41) with the same monitor attached, I don't find
any references to the monitor at all. It appears that monitor detection
doesn't happen until the normal syslog process
On Wed, Apr 2, 2025 at 8:24 PM Dave Close wrote:
> "George N. White III" wrote:
>
> >Try booting a Live USB -- if that gives graphics you know the hardware is
> >working.
>
> Tried that. It doesn't boot. I think the BIOS on this machine requires
> some keyboard entry to select the USB boot. Hard
"George N. White III" wrote:
>Try booting a Live USB -- if that gives graphics you know the hardware is
>working.
Tried that. It doesn't boot. I think the BIOS on this machine requires
some keyboard entry to select the USB boot. Hard to do without video.
I'm beginning to think adding a video car
Samuel Sieb wrote:
>What is the video device? "lspci" output
The display does not appear in that output.
>Check "journalctl -b" for lines with "drm" or "modesetting".
kernel: ACPI: bus type drm_connector registered
kernel: [drm] radeon kernel modesetting enabled.
kernel: [drm] initializing ker
I wrote:
> Trying to start X through the SSH (-X) connection, I'm told, "Only
> console users are allowed to run the X server". Trying to start Wayland
> doesn't work either but produces voluminous output. If the serial
> connection worked, it would be a console, so maybe Wayland or X could at
> le
you might try adding setterm --blank 0 --powersave no --powerdown=0
I think i have had luck with that making sure when I turn a monitor
back on that the session/screen/output is there and still showing.
I think I have put this sort of stuff in rc.local before to be run at boot.
On Wed, Apr 2,
I wrote:
> I have a machine running Fedora 41 which has stopped providing video
> for its console. Of course, the problem could be hardware, but there
> is no clear evidence of that. I am able to access the machine with SSH
> so I know it is working. I don't find any indication of a problem in
> l
On Wed, 2025-04-02 at 07:17 -0500, Roger Heflin wrote:
> I have had my display disappear and not come back when turning on/off
> a monitor/tv. Sometimes on/off again works, sometimes moving the
> hdmi cable to another monitor port works, and sometimes I have to
> reboot. And in these cases the m
If the machine does not crash then the serial console is not going to
have any information that dmesg from ssh does not have.
The use-case for the serial console(or kdump) is when the machine
stops and you can no longer see dmesg output from that boot.
Likely you will need to find the log file fo
I have a machine running Fedora 41 which has stopped providing video
for its console. Of course, the problem could be hardware, but there
is no clear evidence of that. I am able to access the machine with SSH
so I know it is working. I don't find any indication of a problem in
log files. To help di
22 matches
Mail list logo
