[opensuse] booting with "console=ttyS0,115200,8n1" and without
I have a dual-Opteron box that refuses to boot unless I specify: console=ttyS0,115200,8n1 on boot-up. If I don't, the boot-up grinds to a halt somewhere in PCI initialisation. Trying to grab some diagnostics with a serial console only leads to the system booting just fine :-) I guess I can leave it with "console=ttyS0,115200,8n1" ... -- Per Jessen, Zürich (24.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
I have a dual-Opteron box that refuses to boot unless I specify:
console=ttyS0,115200,8n1
on boot-up. If I don't, the boot-up grinds to a halt somewhere in PCI initialisation. Trying to grab some diagnostics with a serial console only leads to the system booting just fine :-)
I guess I can leave it with "console=ttyS0,115200,8n1" ...
software - openSUSE 13.2 64bit xen host. -- Per Jessen, Zürich (24.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
I have a dual-Opteron box that refuses to boot unless I specify:
console=ttyS0,115200,8n1
on boot-up. If I don't, the boot-up grinds to a halt somewhere in PCI initialisation. Trying to grab some diagnostics with a serial console only leads to the system booting just fine :-)
I guess I can leave it with "console=ttyS0,115200,8n1" ...
software - openSUSE 13.2 64bit xen host.
I ran into something like that back in OS 8-9 timeframe. It made debugging oot-time issues impossible --- i.e. system would randomly not boot if I used the initrd boot, AND it completely shut off output when it used the initrd boot (no splash -- just a blank screen). If I was lucky, I'd see the login prompt if it hadn't died that time. So I switched to disk boot -- where, at least if it hung, I could see where. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-08-28 10:33, Per Jessen wrote:
Per Jessen wrote:
I have a dual-Opteron box that refuses to boot unless I specify:
console=ttyS0,115200,8n1
on boot-up. If I don't, the boot-up grinds to a halt somewhere in PCI initialisation. Trying to grab some diagnostics with a serial console only leads to the system booting just fine :-)
I guess I can leave it with "console=ttyS0,115200,8n1" ...
software - openSUSE 13.2 64bit xen host.
I know very little about XEN, but a wild guess. Maybe the guest is trying to send something to the host, via serial port. I can't, and hangs. Makes any sense? :-? I do know that, under vmware, you can configure this to happen. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXgj4cACgkQja8UbcUWM1zC0QD/bft3Bx5BGBuhApdrSsdJLD5I nxtODe/bbFLFrKx6Z5kA/R28ycMzcI5G1tAzKkWwDFBSVF3W0NYOVKLQgMtTQ5Ne =s3Le -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-08-28 10:33, Per Jessen wrote:
Per Jessen wrote:
I have a dual-Opteron box that refuses to boot unless I specify:
console=ttyS0,115200,8n1
on boot-up. If I don't, the boot-up grinds to a halt somewhere in PCI initialisation. Trying to grab some diagnostics with a serial console only leads to the system booting just fine :-)
I guess I can leave it with "console=ttyS0,115200,8n1" ...
software - openSUSE 13.2 64bit xen host.
I know very little about XEN, but a wild guess. Maybe the guest is trying to send something to the host, via serial port. I can't, and hangs. Makes any sense? :-?
Nope, this is the host booting up, not a guest. -- Per Jessen, Zürich (24.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-08-28 20:21, Per Jessen wrote:
Nope, this is the host booting up, not a guest.
Ah. Yes, didn't notice. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXgp/cACgkQja8UbcUWM1zu5wD/T24eqm7vA9QF1DkrC0c5P+pS oTI4M5Lqy3tac693ZRIA/i+Sl2aCRH1nzTI5PbaXSWvRXbDoEfVZ7xoEF7AoLrwI =8lNp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Did not notice this earlier: Am 28.08.2015 um 10:33 schrieb Per Jessen:
I guess I can leave it with "console=ttyS0,115200,8n1" ... software - openSUSE 13.2 64bit xen host.
In this case the console= should be different: xen.gz console=com1 com1=115200 vmlinuz-xen console=hvc0 console=tty1 That way the serial gets routed through Xen, and the video drivers have still a chance to do their work. Olaf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Aug 28, Per Jessen wrote:
I have a dual-Opteron box that refuses to boot unless I specify: console=ttyS0,115200,8n1
The default AFAIK is 'console=tty1', which means your system hangs due to graphics issues. Try to append also 'ignore_loglevel console=tty1'. That way the kernel output is mirrored to serial and graphical, and hopefully the actual issue will be logged to serial. Olaf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Olaf Hering wrote:
On Fri, Aug 28, Per Jessen wrote:
I have a dual-Opteron box that refuses to boot unless I specify: console=ttyS0,115200,8n1
The default AFAIK is 'console=tty1', which means your system hangs due to graphics issues.
Ah, I hadn't thought of that, thanks.
Try to append also 'ignore_loglevel console=tty1'. That way the kernel output is mirrored to serial and graphical, and hopefully the actual issue will be logged to serial.
Will try. -- Per Jessen, Zürich (19.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Olaf Hering wrote:
On Fri, Aug 28, Per Jessen wrote:
I have a dual-Opteron box that refuses to boot unless I specify: console=ttyS0,115200,8n1
The default AFAIK is 'console=tty1', which means your system hangs due to graphics issues.
Ah, I hadn't thought of that, thanks.
Try to append also 'ignore_loglevel console=tty1'. That way the kernel output is mirrored to serial and graphical, and hopefully the actual issue will be logged to serial.
Will try.
When I specify "device=tty1", I have a physical console up until a point in PCI initialisation: [ 0.227858] PCI host bridge to bus 0000:00 [ 0.227862] pci_bus 0000:00: root bus resource [bus 00-03] [ 0.227865] pci_bus 0000:00: root bus resource [io 0x0000-0x03af] [ 0.227867] pci_bus 0000:00: root bus resource [io 0x03b0-0x03bb] [ 0.227869] pci_bus 0000:00: root bus resource [io 0x03c0-0x03df] [ 0.227872] pci_bus 0000:00: root bus resource [io 0x03e0-0x0fff] [ 0.227874] pci_bus 0000:00: root bus resource [io 0x1000-0x5fff] [ 0.227877] pci_bus 0000:00: root bus resource [mem 0xf5f00000-0xf7ffffff] [ 0.227879] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff] [ 0.227906] pci 0000:00:03.0: [1022:7460] type 01 class 0x060400 The above is from 'dmesg' after a successful boot, I can't be 100% certain this is exactly where it would normally halt. I am not getting any serial console output though - initially during POST, the system recognises the serial port, but once the kernel and the initrd are loaded, no more output. I am booting a xen host, does that matter? The graphics device is: Advanced Micro Devices, Inc. [AMD/ATI] Rage XL PCI I seem to remember some issue with this type of graphics, but it's a long time ago and I can't find anyreferences. -- Per Jessen, Zürich (22.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-09-01 09:12, Per Jessen wrote:
When I specify "device=tty1",
It was supposed to be 'console=tty1' :-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXlZWEACgkQja8UbcUWM1wn6AEAgrUBt1lFWre0uSQuhgZTFLQp Tl+OzNbBondOZGggk7AA/0Xgsk56PWKM7ZlWJRak632otjRkqN4Nq5jd5H9VitGy =g2A8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-09-01 09:12, Per Jessen wrote:
When I specify "device=tty1",
It was supposed to be 'console=tty1' :-)
My typo, the rest I copied direfctly :-) -- Per Jessen, Zürich (22.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 01 Sep 2015 09:12:04 +0200 Per Jessen wrote:
I have a dual-Opteron box that refuses to boot unless I specify:
console=ttyS0,115200,8n1 ... The graphics device is: Advanced Micro Devices, Inc. [AMD/ATI] Rage XL PCI
Hi Per, Is this a production box? How did the problem manifest itself, i.e. 'out of the blue' or has other work been done on it? Are the graphics on-board or is this an add-on card? Thx! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carl Hartung wrote:
On Tue, 01 Sep 2015 09:12:04 +0200 Per Jessen wrote:
I have a dual-Opteron box that refuses to boot unless I specify:
console=ttyS0,115200,8n1 ... The graphics device is: Advanced Micro Devices, Inc. [AMD/ATI] Rage XL PCI
Hi Per,
Is this a production box? How did the problem manifest itself, i.e. 'out of the blue' or has other work been done on it? Are the graphics on-board or is this an add-on card?
Hi Carl it will become production, but for now it's in test. Using "console=ttyS0" to stop the boot-up from touching the graphics is sufficient as a work-arond. The problem was first seen during installation. It's an on-board graphics card. -- Per Jessen, Zürich (23.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 01 Sep 2015 12:52:57 +0200 Per Jessen wrote:
Carl Hartung wrote:
On Tue, 01 Sep 2015 09:12:04 +0200 Per Jessen wrote:
I have a dual-Opteron box that refuses to boot unless I specify:
console=ttyS0,115200,8n1 ... The graphics device is: Advanced Micro Devices, Inc. [AMD/ATI] Rage XL PCI
Hi Per,
Is this a production box? How did the problem manifest itself, i.e. 'out of the blue' or has other work been done on it? Are the graphics on-board or is this an add-on card?
Hi Carl
it will become production, but for now it's in test. Using "console=ttyS0" to stop the boot-up from touching the graphics is sufficient as a work-arond. The problem was first seen during installation. It's an on-board graphics card.
Is it a used board? Could someone have disabled the onboard graphics and installed an add-on card that's since been pulled? All the threads I've found discussing that device relate to problems with X, not during boot. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carl Hartung wrote:
On Tue, 01 Sep 2015 12:52:57 +0200 Per Jessen wrote:
Carl Hartung wrote:
On Tue, 01 Sep 2015 09:12:04 +0200 Per Jessen wrote:
I have a dual-Opteron box that refuses to boot unless I specify:
console=ttyS0,115200,8n1 ... The graphics device is: Advanced Micro Devices, Inc. [AMD/ATI] Rage XL PCI
Hi Per,
Is this a production box? How did the problem manifest itself, i.e. 'out of the blue' or has other work been done on it? Are the graphics on-board or is this an add-on card?
Hi Carl
it will become production, but for now it's in test. Using "console=ttyS0" to stop the boot-up from touching the graphics is sufficient as a work-arond. The problem was first seen during installation. It's an on-board graphics card.
Is it a used board? Could someone have disabled the onboard graphics and installed an add-on card that's since been pulled? All the threads I've found discussing that device relate to problems with X, not during boot.
It's a second hand server, the graphics can't be disabled :-) -- Per Jessen, Zürich (17.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 02 Sep 2015 08:46:33 +0200 Per Jessen wrote:
Carl Hartung wrote:
On Tue, 01 Sep 2015 12:52:57 +0200 Per Jessen wrote:
Carl Hartung wrote:
On Tue, 01 Sep 2015 09:12:04 +0200 Per Jessen wrote:
I have a dual-Opteron box that refuses to boot unless I specify:
console=ttyS0,115200,8n1 ... The graphics device is: Advanced Micro Devices, Inc. [AMD/ATI] Rage XL PCI
Hi Per,
Is this a production box? How did the problem manifest itself, i.e. 'out of the blue' or has other work been done on it? Are the graphics on-board or is this an add-on card?
Hi Carl
it will become production, but for now it's in test. Using "console=ttyS0" to stop the boot-up from touching the graphics is sufficient as a work-arond. The problem was first seen during installation. It's an on-board graphics card.
Is it a used board? Could someone have disabled the onboard graphics and installed an add-on card that's since been pulled? All the threads I've found discussing that device relate to problems with X, not during boot.
It's a second hand server, the graphics can't be disabled :-)
Does "during installation" mean at initial boot (installation kernel) or after first reboot (installed kernel?) Related: Have you booted any alternate OS's / Live CD's etc just to see if the graphics device can be somehow coaxed to behave? Are there any actual PCI cards installed that you can re-seat or relocate? :-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carl Hartung wrote:
Does "during installation" mean at initial boot (installation kernel) or after first reboot (installed kernel?)
Good question. I'm not sure - it obviously worked during installation, but whether that was with "console=ttyS0" or not, I don't remember.
Related: Have you booted any alternate OS's / Live CD's etc just to see if the graphics device can be somehow coaxed to behave?
Nope, but I might try that.
Are there any actual PCI cards installed that you can re-seat or relocate?
Hehe, nah, I've already removed the only one (a dual-port NIC). -- Per Jessen, Zürich (17.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 02 Sep 2015 10:11:04 +0200 Per Jessen wrote:
Carl Hartung wrote:
Does "during installation" mean at initial boot (installation kernel) or after first reboot (installed kernel?)
Good question. I'm not sure - it obviously worked during installation, but whether that was with "console=ttyS0" or not, I don't remember.
Related: Have you booted any alternate OS's / Live CD's etc just to see if the graphics device can be somehow coaxed to behave?
Nope, but I might try that.
Are there any actual PCI cards installed that you can re-seat or relocate?
Hehe, nah, I've already removed the only one (a dual-port NIC).
It'd be nice to know for a fact whether or not the graphics subsystem has failed -- either intrinsically, or after having been pulled down by some failed / incorrect / incorrectly attached display. If it has, I personally wouldn't put it into production, although there's a reasonable school of thought which says 'if the damage hasn't already propagated further, it's reached it's natural conclusion and is unlikely to spread.' :-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carl Hartung wrote:
On Wed, 02 Sep 2015 10:11:04 +0200 Per Jessen wrote:
Carl Hartung wrote:
Does "during installation" mean at initial boot (installation kernel) or after first reboot (installed kernel?)
Good question. I'm not sure - it obviously worked during installation, but whether that was with "console=ttyS0" or not, I don't remember.
Related: Have you booted any alternate OS's / Live CD's etc just to see if the graphics device can be somehow coaxed to behave?
Nope, but I might try that.
Are there any actual PCI cards installed that you can re-seat or relocate?
Hehe, nah, I've already removed the only one (a dual-port NIC).
It'd be nice to know for a fact whether or not the graphics subsystem has failed
It hasn't. I've just booted bith Knoppix 7.2, works all the way to X. None of the installer ISOs from 12.3 up to 13.2 work though. (without "console=ttyS0,..." I might try some of the older ones. -- Per Jessen, Zürich (19.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 02 Sep 2015 12:54:27 +0200 Per Jessen wrote:
Carl Hartung wrote:
On Wed, 02 Sep 2015 10:11:04 +0200 Per Jessen wrote:
Carl Hartung wrote:
Does "during installation" mean at initial boot (installation kernel) or after first reboot (installed kernel?)
Good question. I'm not sure - it obviously worked during installation, but whether that was with "console=ttyS0" or not, I don't remember.
Related: Have you booted any alternate OS's / Live CD's etc just to see if the graphics device can be somehow coaxed to behave?
Nope, but I might try that.
Are there any actual PCI cards installed that you can re-seat or relocate?
Hehe, nah, I've already removed the only one (a dual-port NIC).
It'd be nice to know for a fact whether or not the graphics subsystem has failed
It hasn't. I've just booted bith Knoppix 7.2, works all the way to X. None of the installer ISOs from 12.3 up to 13.2 work though. (without "console=ttyS0,..."
I might try some of the older ones.
You might want to try this package: # zypper se xf86-video-mach64 Loading repository data... Reading installed packages... Name Summary xf86-video-mach64 ATI Mach64 series video driver for the Xorg X server -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carl Hartung wrote:
On Wed, 02 Sep 2015 12:54:27 +0200 Per Jessen wrote:
Carl Hartung wrote:
On Wed, 02 Sep 2015 10:11:04 +0200 Per Jessen wrote:
Carl Hartung wrote:
Does "during installation" mean at initial boot (installation kernel) or after first reboot (installed kernel?)
Good question. I'm not sure - it obviously worked during installation, but whether that was with "console=ttyS0" or not, I don't remember.
Related: Have you booted any alternate OS's / Live CD's etc just to see if the graphics device can be somehow coaxed to behave?
Nope, but I might try that.
Are there any actual PCI cards installed that you can re-seat or relocate?
Hehe, nah, I've already removed the only one (a dual-port NIC).
It'd be nice to know for a fact whether or not the graphics subsystem has failed
It hasn't. I've just booted bith Knoppix 7.2, works all the way to X. None of the installer ISOs from 12.3 up to 13.2 work though. (without "console=ttyS0,..."
I might try some of the older ones.
You might want to try this package:
# zypper se xf86-video-mach64 Loading repository data... Reading installed packages...
Name Summary
xf86-video-mach64 ATI Mach64 series video driver for the Xorg X server
I have no need for X though. It seems unlikely that this package should affect what happens at boot time. /Per -- Per Jessen, Zürich (19.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 02 Sep 2015 19:08:02 +0200 Per Jessen wrote:
Carl Hartung wrote:
On Wed, 02 Sep 2015 12:54:27 +0200 Per Jessen wrote:
Carl Hartung wrote:
On Wed, 02 Sep 2015 10:11:04 +0200 Per Jessen wrote:
Carl Hartung wrote:
Does "during installation" mean at initial boot (installation kernel) or after first reboot (installed kernel?)
Good question. I'm not sure - it obviously worked during installation, but whether that was with "console=ttyS0" or not, I don't remember.
Related: Have you booted any alternate OS's / Live CD's etc just to see if the graphics device can be somehow coaxed to behave?
Nope, but I might try that.
Are there any actual PCI cards installed that you can re-seat or relocate?
Hehe, nah, I've already removed the only one (a dual-port NIC).
It'd be nice to know for a fact whether or not the graphics subsystem has failed
It hasn't. I've just booted bith Knoppix 7.2, works all the way to X. None of the installer ISOs from 12.3 up to 13.2 work though. (without "console=ttyS0,..."
I might try some of the older ones.
You might want to try this package:
# zypper se xf86-video-mach64 Loading repository data... Reading installed packages...
Name Summary
xf86-video-mach64 ATI Mach64 series video driver for the Xorg X server
I have no need for X though. It seems unlikely that this package should affect what happens at boot time.
That was my thinking, but I've seen enough 'solved' threads now that I'm beginning to suspect installing that package might pull in something else. It's just a thought... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carl Hartung -
Carlos E. R. -
Linda Walsh -
Olaf Hering -
Per Jessen