John Paul Adrian Glaubitz writes:
> So just passing "console=ttyS0 keep_bootcon" has to work. If it
> doesn't, there might be something incorrectly configured with the
> hardware.
>
> There isn't really anything else that needs to be done to get a serial
> console.
Crap. I'll get back to this wh
On Thu, Jul 20, 2017 at 02:27:48PM +0200, Gabriel Pérez-Cerezo wrote:
> I've attached a log with the console boot option (log) and another one
> without (log2).
It definitely says:
"[ 1951.095382] f02969dc: ttyS0 at I/O 0x0 (irq = 1, base_baud = 115200) is a
SUN4V HCONS^M"
So just passing "cons
Also, I've already tried changing /etc/default/console-setup and it
edits itself back to its former state.
John Paul Adrian Glaubitz writes:
> Can you please provide the full log of boot messages from SILO to when
> the system is finished booting during a normal boot where you cannot
> get a login prompt? There must be something wrong in your
> configuration.
I've attached a log with the console boot
On Thu, Jul 20, 2017 at 02:11:59PM +0200, Gabriel Pérez-Cerezo wrote:
> I've also found this thing here: Will change anything if i add
> /dev/ttyS0 to ACTIVE_CONSOLES?
No, that should not be necessary. I honesly have no idea why it's not
working. I just added "console=ttyS0,115200,8n1 keep_bootcon
John Paul Adrian Glaubitz writes:
> Can you check the contents of /sys/dev/char or /sys/class/tty?
Ok. Here are some outputs.
root@(none):/# ls /sys/dev/char/
10:1 10:62 1:74:12 4:2 4:274:34 4:41 4:49 4:56 4:63 7:0
10:139 10:63 1:84:13 4:20 4:28 4:35 4:42 4:5 4:57
On 07/19/2017 10:11 PM, Gabriel Pérez-Cerezo wrote:
> It may be named ttyHV0, but as much as I have tried it with that name,
> it still doesn't work. However, I've been able to boot to shell
> (bypassing init) and there is no /dev/ttyHV0 in the filesystem. I'll see
> if I can try more stuff tomorro
John Paul Adrian Glaubitz writes:
> Can you check the contents of /sys/dev/char or /sys/class/tty?
I'll do it tomorrow. I'm too tired to continue and I just shut down the
server for the night (it takes really long to boot up).
Cheers,
Gabriel
On 19 Jul 2017, at 21:11, Gabriel Pérez-Cerezo wrote:
> John Paul Adrian Glaubitz writes:
>
>> Are you sure that ttyS0 is the name of your serial device?
>>
>> Check the kernel messages. It might be named differently.
>
> It may be named ttyHV0, but as much as I have tried it with that name,
>
John Paul Adrian Glaubitz writes:
> Are you sure that ttyS0 is the name of your serial device?
>
> Check the kernel messages. It might be named differently.
It may be named ttyHV0, but as much as I have tried it with that name,
it still doesn't work. However, I've been able to boot to shell
(by
On 07/19/2017 08:27 PM, Gabriel Pérez-Cerezo wrote:
> if I only use keep_bootcon, i get until:
> Starting Update UTMP about System Runlevel Changes...
> [ OK ] Started Update UTMP about System Runlevel Changes.
>
> But no login console in neither case.
Are you sure that ttyS0 is the na
John Paul Adrian Glaubitz writes:
> Can you try adding "console=ttyS0,9600,8n1 keep_bootcon"?
keeping the console stuff, I get output until here:
[12194.169207] Btrfs loaded, crc32c=crc32c-generic
[12194.309242] BTRFS: device fsid ddd0fc8f-c6b3-449f-813a-be5503368f34 devid 1
transid 2072 /dev/vd
On 07/19/2017 07:24 PM, Gabriel Pérez-Cerezo wrote:
> I have tried booting it with the workaround (Linux console=ttyS0), but it also
> doesn't show anything (in fact, boot output ends earlier). Does anyone
> know what options I should give to the kernel in order to boot into a
> login screen?
Can
Hi,
I'm running a SPARC Enterprise T5120 with OpenBSD in the primary Logical
Domain. I have installed Debian successfully in an LDOM, however, I
haven't set the recommended options for T5120 in /boot/silo.conf. I have
tried booting it with the workaround (Linux console=ttyS0), but it also
doesn't
14 matches
Mail list logo
