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
o without video.
If the screen doesn't come up for the BIOS, then you have a hardware
problem. You didn't answer that question earlier. This serial console
thing is just a pointless side track.
--
___
users mailing list -- users@lists.fedorap
on worked, it would be a console, so maybe Wayland or X could at
> least try to start.
If this is the only reason why you’re trying to set up a serial console, then
it won’t help. Neither X11 nor Wayland can use a serial console either.
You’re better off restarting services like GDM to figur
0 21:55 tty1 00:00:00
> > > /sbin/agetty -o -p -- \u --noclear - linux
> > > root 1430 1 0 21:55 ttyS0 00:00:00
> > > /sbin/agetty -o -p -- \u --keep-baud 115200,57600,38400,9600 - vt220
> > > # Again, lines are split and condensed here only
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
s with "drm" or "modesetting".
Of course, the motivation for trying to get the serial console working
is not really the reason for my post. My reason is, why doesn't the
serial console seem to work? What am I missing in the process?
Do you see the options in /proc/cmdl
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
, so maybe Wayland or X could at
> least try to start.
Jonathan Billings wrote:
> If this is the only reason why youâre trying to set up a serial
> console, then it wonât help. Neither X11 nor Wayland can use a
> serial console either. Youâ re better off restarting services
> lik
/sbin/agetty -o -p -- \u --keep-baud 115200,57600,38400,9600 - vt220
> > # Again, lines are split and condensed here only for readability.
> >
> > After all this, I get no output on the putty connection and no response
> > when attempting any entry. I've also tried the oth
n and no response
> when attempting any entry. I've also tried the other listed baud rates.
>
> Is there any obvious step I've missed? Is there a better way to do this?
Roger Heflin wrote:
>If the machine does not crash then the serial console is not going to
>have any inf
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
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
any experts here ?
all is written:
https://ask.fedoraproject.org/t/debugging-a-box-via-serial-console/17649
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of
I have a server set up with Fedora 18, works ok.
I decided to make the root partition encrypted, set that up, works ok.
The machine is remote so I use a serial console to connect, works ok.
Here's the rub, while booting there is a pause to request the passphrase
to unlock the encrypted fs.
On Mon, Jul 9, 2012 at 1:17 PM, Michael Cronenworth wrote:
> I believe GRUB2 uses SHA512. You can even pass a salt.
Thanks!
My concern was that grub2 were still using md5
FC
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedorapr
Fernando Cassia wrote:
> 1. is there an updated tuturial on getting a serial console working in f17?
F17 uses GRUB2. Find any GRUB2 docs for serial terminals online or at
your terminal:
$ info grub2
/Serial[ENTER]
> 2. since that 2007 tutorial used grub, and fedora 17 uses grub2 I
>
s
messages to the serial console. One of the most important things is to
set a password, otherwise anyone can connect a serial cable, edit the
GRUB configuration line while the system is booting (via the "e" key),
and get root access. When a password is set, interactive menu editing
will
On Sat, Dec 24, 2011 at 5:26 PM, Derek Tattersall wrote:
> I am in the process of setting up a router/file server using F16. I would
> like have the boot messages go to the serial console.
>
> How do you do that in F16?
>
> It seems to use a different version of grub than other
I am in the process of setting up a router/file server using F16. I
would like have the boot messages go to the serial console.
How do you do that in F16?
It seems to use a different version of grub than other versions, and
what worked in F14 won't work in F16. I think. Or will it?
T
On 10/24/2011 11:54 AM, Kevin Martin wrote:
> I can't seem to get systemd to spawn a getty on a USB tty. Here's what I've
> done:
>
> # ln -sf /lib/systemd/system/getty@.service
> /etc/systemd/system/getty.target.wants/getty@ttyUSB0.service
> # systemctl daemon-reload
> # systemctl start getty
I can't seem to get systemd to spawn a getty on a USB tty. Here's what I've
done:
# ln -sf /lib/systemd/system/getty@.service
/etc/systemd/system/getty.target.wants/getty@ttyUSB0.service
# systemctl daemon-reload
# systemctl start getty@ttyUSB0.service
When I look at the gettys that are runnin
31 matches
Mail list logo
