On Mon, 2013-05-13 at 02:44 -0400, Felix Miata wrote:

On 2013-05-13 07:31 (GMT+0200) Roger Oberholtzer composed:

...

I have a SuperMicro computer on which I seem unable to install openSUSE (11.2, 12.1 or 12.3). I can install Windows XP and CentOS 5.5. But not openSUSE. The machine has been back to the supplier, who claim they can find nothing wrong with it.

...

I can do the first part of the install up to and including when the system is copied to the hard disk. After that, the system is reboot to finish the install.

...

When the kernel is booting, it gets so far as to printing

...

Switching to clocksource tsc

...

and then nothing more can be done. No keyboard control is possible.

...

I have tried every kernel command line option I know to see if I can

Do you know them all? e.g. those listed on http://en.opensuse.org/Linuxrc

No one knows all the kernel command line options. The Failsafe boot does contain the ones known to usually cause issues. All those have been tried to no avail.

...

effect a change. Nope. It stops dead at this point.

Have you tried the other type of keyboard, PS/2 vs. USB? What USB support setting is in the BIOS?

We have changed RAM, hard disk, all connected devices (keyboard and mouse). The video card is an average NVIDIA of the type we use everywhere. My money is on the BIOS. SuperMicro have had the system returned and they claim this is not the case. Not sure I agree. But I an mot in a position to prove them wrong...

...

What could the issue be?

Lots of things. How about narrowing the possibilities by describing more, including sharing some hardware specifications, like age of PC, which video chip (& onboard?; PCIe vs AGP vs PCI), CPU, RAM, installation type (network vs DVD vs PXE, etc; minimal vs KDE vs Gnome or other), grub version installed (have you only tried the default Grub2?), storage system bus type (PATA/SATA/SCSI; controller chip), etc.?

I realize my report was a bit sketchy. Since the system freezes so early in the boot process, I never get a chance to see how Linux views the hardware. I know that the kernel and environment used during the install is not the same as that in the final installation. And the install kernel seems to work, as the install seems to complete. It is after booting in to the installed kernel that things go pear shaped.

You might wish to try another install using kexec_reboot=1 on installation cmdline. It might get you into a usable first boot from which you can more easily collect installation logs to share (e.g. attach to a bug report).

Should kexec_reboot=1 trigger a text-based installation? The openSUSE docs claim that =1 is the default. Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, 2013-05-13 at 12:15 +0200, Per Jessen wrote:

Roger Oberholtzer wrote:

...

I realize my report was a bit sketchy. Since the system freezes so early in the boot process, I never get a chance to see how Linux views the hardware.

Serial console. "console=ttyS0,19200,8n1"

This did not get me any further. However, I can see some messages from earlier in the boot process (installed kernel), like: [ 1.816720] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored Other than that, nothing looks suspicious. Just before failing, this is printed: [ 8.260768] ERST: Failed to get Error Log Address Range. [ 9.049084] Refined TSC clocksource calibration: 1999.999 MHz. [ 9.083950] Switching to clocksource tsc The serial port console is equally dead. Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2013-05-13 10:57 (GMT+0200) Roger Oberholtzer composed:

...

How about narrowing the possibilities by describing more, including sharing some hardware specifications, like age of PC, which video chip (& onboard?; PCIe vs AGP vs PCI), CPU, RAM, installation type (network vs DVD vs PXE, etc; minimal vs KDE vs Gnome or other), grub version installed (have you only tried the default Grub2?), storage system bus type (PATA/SATA/SCSI; controller chip), etc.?

I realize my report was a bit sketchy. Since the system freezes so early in the boot process, I never get a chance to see how Linux views the hardware.

Hardware info is all available if the system is multiboot and still boots another install, or if for the purpose you do some kind of live media boot that doesn't have the same problem.

...

You might wish to try another install using kexec_reboot=1 on installation cmdline. It might get you into a usable first boot from which you can more easily collect installation logs to share (e.g. attach to a bug report).

Should kexec_reboot=1 trigger a text-based installation? The openSUSE docs claim that =1 is the default.

AFAIK, kexec_reboot never triggered text-based installation. And we all know all web docs are always up to date, right? :-p When I wrote that I should have mentioned I believe that particular doc item is wrong. Take a look at: http://lists.opensuse.org/opensuse-factory/2012-07/msg00072.html I was unable to locate a bug report that confirms that thread's assertion. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2013-05-13 13:19 (GMT+0200) Roger Oberholtzer composed:

...

Hardware info is all available if the system is multiboot and still boots another install, or if for the purpose you do some kind of live media boot that doesn't have the same problem.

The system is not multiboot. It did not come with any Microsoft stuff. The test of other OS installs was by the equipment supplier.

Multiboot isn't about Windows. I have more than 30 functional systems, the vast majority of which are multiboot, and few of which have Windows installed. If you have three / filesystems for Linux, then you have one for operating normally (ver x.x), one for trying out the next release before committing to operating normally with it (ver x.y), and another for contributing to the (community) development of the next release (ver x.z) and ensuring it will actually function on your hardware, and/or test driving (an)other distribution(s). Once you're committed to x.y, x.x becomes a fallback/rescue system, until it's time for the trying out the next next prior to committing it to normal. IOW, you're virtually guaranteed _something_ will boot and give you access to logs and repair tools without having to hunt down something slow to shove in a hole to get booted and operate slowly from. With the size of modern HDs, there's ample space for at least three /s without materially cutting into available user data space. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Roger Oberholtzer wrote:

I am doing a 12.1 install via the serial console in the hopes that I can get further there than on the video console.

If it is a video issue, you try adding "vga=normal" to the command line when you boot, but you've probably tried that already. -- Per Jessen, Zürich (14.9°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, 2013-05-13 at 15:08 +0200, Per Jessen wrote:

Roger Oberholtzer wrote:

...

I am doing a 12.1 install via the serial console in the hopes that I can get further there than on the video console.

If it is a video issue, you try adding "vga=normal" to the command line when you boot, but you've probably tried that already.

Yes. And nomodeset, edd, and others. I do now see an interesting thing on the serial port that I did not see on the video console. I let the system sit in failure mode (I have productive work to accomplish as well...), and I see this printed every once in a while: [ 9.083950] Switching to clocksource tsc tick tock... [ 966.240728] INFO: task swapper:1 blocked for more than 480 seconds. [ 966.278177] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 966.324989] swapper D 7dff2173 0 1 0 0x00000000 [ 966.363133] dc4ade2c 00000046 c046518d 7dff2173 80000000 c0a8afa0 c0b51e00 c0b51e00 [ 966.409841] e1aa165e 00000001 e5006e00 dc4aacf0 c0a8afa0 00000002 00000000 00000000 [ 966.456544] ffffffff dc4adee5 dc4ade16 c046bb56 0007dff2 00000001 00000000 00000000 [ 966.503208] Call Trace: [ 966.517852] [<c0707645>] schedule_timeout+0x255/0x2d0 [ 966.548571] [<c070680e>] wait_for_common+0x7e/0x110 [ 966.578257] [<c02b13d7>] synchronize_rcu+0x37/0x40 [ 966.607425] [<c04b5656>] acpi_post_unmap_gar.part.0+0x70/0x89 [ 966.642301] [<c04deb45>] post_unmap_gar_callback+0x15/0x20 [ 966.675618] [<c04de25c>] apei_exec_for_each_entry+0x5c/0x90 [ 966.709455] [<c04de2c6>] apei_exec_post_unmap_gars+0x16/0x20 [ 966.743811] [<c0b04d30>] erst_init+0x257/0x2b2 [ 966.770903] [<c0201123>] do_one_initcall+0x33/0x170 [ 966.800589] [<c0ad9823>] kernel_init+0xb0/0x13c [ 966.828198] [<c070f966>] kernel_thread_helper+0x6/0xd [ 966.858921] INFO: task rcub1:11 blocked for more than 480 seconds. [ 966.895864] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 966.942675] rcub1 D 00000013 0 11 2 0x00000000 [ 966.980716] dc4cbf08 00000046 dc4c8f90 00000013 00000013 c0a8afa0 c0b51e00 c0b51e00 [ 967.027373] 0c04f784 00000002 e5006e00 dc4c8e30 c0a8afa0 e5006e44 00000000 dc4cbed0 [ 967.074031] c0231fac dc4aacf0 dc4aacf0 dc4cbef4 c02433a8 00000078 e5006e00 00000062 [ 967.120740] Call Trace: [ 967.135335] [<c07083f1>] __rt_mutex_slowlock+0x31/0xa0 [ 967.166576] [<c07084e9>] rt_mutex_slowlock+0x89/0x140 [ 967.197300] [<c0708612>] rt_mutex_lock+0x32/0x40 [ 967.225426] [<c02b020a>] rcu_boost+0x5a/0xd0 [ 967.251481] [<c02b02f7>] rcu_boost_kthread+0x77/0xa0 [ 967.281684] [<c0266c99>] kthread+0x69/0x70 [ 967.306702] [<c070f966>] kernel_thread_helper+0x6/0xd tick tock... [ 1446.392980] INFO: task swapper:1 blocked for more than 480 seconds. [ 1446.430422] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. The function traces do not tell me what may have been going on. But the system is not dead. Only deadlocked... Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

El 13/05/13 11:29, Cristian Rodríguez escribió:

El 13/05/13 10:00, Roger Oberholtzer escribió:

...

[ 966.517852] [<c0707645>] schedule_timeout+0x255/0x2d0 [ 966.548571] [<c070680e>] wait_for_common+0x7e/0x110 [ 966.578257] [<c02b13d7>] synchronize_rcu+0x37/0x40 [ 966.607425] [<c04b5656>] acpi_post_unmap_gar.part.0+0x70/0x89 [ 966.642301] [<c04deb45>] post_unmap_gar_callback+0x15/0x20 [ 966.675618] [<c04de25c>] apei_exec_for_each_entry+0x5c/0x90 [ 966.709455] [<c04de2c6>] apei_exec_post_unmap_gars+0x16/0x20 [ 966.743811] [<c0b04d30>] erst_init+0x257/0x2b2 [ 966.770903] [<c0201123>] do_one_initcall+0x33/0x170 [ 966.800589] [<c0ad9823>] kernel_init+0xb0/0x13c [ 966.828198] [<c070f966>] kernel_thread_helper+0x6/0xd

OK, try booting with ghes.disable=1 and upgrade your BIOS...too.

if that does not help, try booting with erst_disable -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

El 13/05/13 11:42, Roger Oberholtzer escribió:

On Mon, 2013-05-13 at 11:29 -0400, Cristian Rodríguez wrote:

...

El 13/05/13 10:00, Roger Oberholtzer escribió:

...

[ 966.517852] [<c0707645>] schedule_timeout+0x255/0x2d0 [ 966.548571] [<c070680e>] wait_for_common+0x7e/0x110 [ 966.578257] [<c02b13d7>] synchronize_rcu+0x37/0x40 [ 966.607425] [<c04b5656>] acpi_post_unmap_gar.part.0+0x70/0x89 [ 966.642301] [<c04deb45>] post_unmap_gar_callback+0x15/0x20 [ 966.675618] [<c04de25c>] apei_exec_for_each_entry+0x5c/0x90 [ 966.709455] [<c04de2c6>] apei_exec_post_unmap_gars+0x16/0x20 [ 966.743811] [<c0b04d30>] erst_init+0x257/0x2b2 [ 966.770903] [<c0201123>] do_one_initcall+0x33/0x170 [ 966.800589] [<c0ad9823>] kernel_init+0xb0/0x13c [ 966.828198] [<c070f966>] kernel_thread_helper+0x6/0xd

OK, try booting with ghes.disable=1 and upgrade your BIOS...too.

No joy. That option had no effect.

neither erst_disable ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, 2013-05-13 at 18:01 +0200, Roger Oberholtzer wrote:

On Mon, 2013-05-13 at 11:47 -0400, Cristian Rodríguez wrote:

...

El 13/05/13 11:42, Roger Oberholtzer escribió:

...

On Mon, 2013-05-13 at 11:29 -0400, Cristian Rodríguez wrote:

...

El 13/05/13 10:00, Roger Oberholtzer escribió:

...

[ 966.517852] [<c0707645>] schedule_timeout+0x255/0x2d0 [ 966.548571] [<c070680e>] wait_for_common+0x7e/0x110 [ 966.578257] [<c02b13d7>] synchronize_rcu+0x37/0x40 [ 966.607425] [<c04b5656>] acpi_post_unmap_gar.part.0+0x70/0x89 [ 966.642301] [<c04deb45>] post_unmap_gar_callback+0x15/0x20 [ 966.675618] [<c04de25c>] apei_exec_for_each_entry+0x5c/0x90 [ 966.709455] [<c04de2c6>] apei_exec_post_unmap_gars+0x16/0x20 [ 966.743811] [<c0b04d30>] erst_init+0x257/0x2b2 [ 966.770903] [<c0201123>] do_one_initcall+0x33/0x170 [ 966.800589] [<c0ad9823>] kernel_init+0xb0/0x13c [ 966.828198] [<c070f966>] kernel_thread_helper+0x6/0xd

OK, try booting with ghes.disable=1 and upgrade your BIOS...too.

No joy. That option had no effect.

neither erst_disable ?

That one did get further. The system booted. It then started the second part of the install, and then waited while checking for DSL devices (don't have 'em).

But as I had been playing with things, I decided to do a clean install and see what it does. That is in progress.

I did a clean install. With erst_disable, it now reboots and gets to Automatic Configuration. At that point it fails. In GUI mode, I can only see that it stops at 19%. I did a text-based trial, and, as reported earlier, that one stopped when it was looking for DSL stuff in the Automatic Configuration step. I see that there is occasional activity on the disk. Not sure what is happening. So, I will leave this for a bit. Maybe the Auto Config will time out and then move on... Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, 2013-05-13 at 16:11 -0400, Cristian Rodríguez wrote:

El 13/05/13 12:47, Roger Oberholtzer escribió:

...

I did a clean install. With erst_disable, it now reboots and gets to Automatic Configuration.

OK, does it keep the erst_disable in the boot line after reboot ?

At that point it fails. In GUI mode, I can only

...

see that it stops at 19%. I did a text-based trial, and, as reported earlier, that one stopped when it was looking for DSL stuff in the Automatic Configuration step.

Did you tried massive axe acpi=off and see if the installation finishes ?

That did the trick! So, it seems that during install I need: erst_disable acpi=off and during later use: acpi=off The only thing that remains is that when the system is shut down, the power to the PC does not go off. Maybe this is because of the acpi=off option. Otherwise, all our other SuperMicro units power off completely.

Also do you have any sort of custom BIOS configuration ? try using "setup defaults" or "optimized setup defaults".

The BIOS is pretty much in the default state. Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, 2013-05-14 at 11:06 -0400, Cristian Rodríguez wrote:

HOw to continue:

1. update your kernel to the one available on the Kernel:HEAD repository.

2. see if it can boot now without acpi=off

3. post any error, hang, backtrace in bugzilla, component kernel.

I have had to return the machine to our support guys, who will probably have to return it to the customer before I will get a chance to explore further. What I saw was that erst_disable got the kernel to finish starting and the system come up. What later failed was when the openSUSE install was doing Automatic Configuration. When that was failing (without acpi=off) I tried looking at a vt to see if there was any useful message. I did not see anything. Then the system hung. I am not sure what I could do to see more. Presumably try other kernel options less severe than acpi=off. Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/15/2013 08:35 AM, Roger Oberholtzer wrote:

On Wed, 2013-05-15 at 07:35 +0200, Roger Oberholtzer wrote:

As I mentioned earlier, when I added acpi=off, powering off the PC on shutdown stopped working. I tried setting HALT="poweroff" in /etc/sysconfig/shutdown, but that also had no effect.

The issue is that, when the system is shutdown, a green splash is shown, so you do not see the shutdown progress. So you never know when the shutdown is complete. If you hit ESC in time the splash goes away. But these systems are powered off/on many times per day, making the ESC awkward.

Is there some way to disable the shutdown splash so that the shutdown progress can be seen?

Yes but without acpi the shutdown will never finish anyway. that's expected, as acpi manages all power management related functions. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hi, On Thu, May 16, 2013 at 8:10 AM, Roger Oberholtzer wrote: ...

...

...

Is there some way to disable the shutdown splash so that the shutdown progress can be seen? ... If I could disable the splash screen so that the text written during shutdown is seen, they would see when the system prints "System halted" and then know it is OK to power off. With the splash screen hiding this information, the user needs to trust faith that the system is ok to shut down. There is a very narrow window where pressing ESC removes the splash screen. If you miss that, then you will never be able to see that the system has halted.

I usually remove splash=silent and quiet options from kernel options (using Yast system->bootloader or directly editing menu.lst or grub.cfg) and then I see the power up and shut down messages on screen. -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2013-05-16 10:19 (GMT+0200) Roger Oberholtzer composed:

We have splash=silent, but the green screen with the Geeko is still shown at boot and shutdown. This is on 12.1

All my grub stanzas have no quiet, but do have either splash=verbose or splash=0. I see messages instead of nothing at both boot and shutdown. IIUC, no splash anything on cmdline also equates to not silent, or at least, it used to or does without Plymouth. On 12.2, the only green I see during boot or shutdown is on the right side used to spell "done". -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, 2013-05-16 at 11:07 +0200, Per Jessen wrote:

Felix Miata wrote:

...

On 2013-05-16 10:19 (GMT+0200) Roger Oberholtzer composed:

...

We have splash=silent, but the green screen with the Geeko is still shown at boot and shutdown. This is on 12.1

All my grub stanzas have no quiet, but do have either splash=verbose or splash=0.

I will try splash=0. OTOH, the faithful docs at http://en.opensuse.org/Linuxrc claim the allowed values are silent and verbose. Also, seems splash=silent is what YaST sets up in the grub menus (12.1 at least)... I am growing to distrust the information on that page. Is there a better source that is perhaps a bit more correct/up-to-date? Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/16/2013 10:10 AM, Roger Oberholtzer wrote:

On Thu, 2013-05-16 at 11:07 +0200, Per Jessen wrote:

...

Felix Miata wrote:

...

On 2013-05-16 10:19 (GMT+0200) Roger Oberholtzer composed:

...

We have splash=silent, but the green screen with the Geeko is still shown at boot and shutdown. This is on 12.1

All my grub stanzas have no quiet, but do have either splash=verbose or splash=0.

I will try splash=0. OTOH, the faithful docs at http://en.opensuse.org/Linuxrc claim the allowed values are silent and verbose. Also, seems splash=silent is what YaST sets up in the grub menus (12.1 at least)...

linuxrc will not be running on an installed system, I thought that went without saying.. to get the progress of startup/shutdown set plymouth theme to "details", rebuid initrd , and remove quiet from the kernel command line. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

El 16/05/13 17:05, Roger Oberholtzer escribió:

On Thu, 2013-05-16 at 11:42 -0400, Cristian Rodríguez wrote:

...

linuxrc will not be running on an installed system, I thought that went without saying..

So there is a different place where all the supported options ate listed?

yes. read kernel-command-line(7) and the man pages/documents referenced there. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

El 16/05/13 17:35, Felix Miata escribió:

On 2013-05-16 17:23 (GMT-0400) Cristian Rodríguez composed:

...

...

So there is a different place where all the supported options ate listed?

...

yes. read kernel-command-line(7) and the man pages/documents referenced there.

Closest thing I can find to kernel-command-line(7) is https://www.kernel.org/doc/Documentation/kernel-parameters.txt. Where is kernel-command-line(7) to be found? Is kernel-command-line(7) an openSUSE-specific document?

http://www.freedesktop.org/software/systemd/man/kernel-command-line.html it may not be shipped with your version of systemd. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2013-05-16 23:37 (GMT+0200) Martin Helm composed:

Felix Miata composed:

...

Where is kernel-command-line(7) to be found?

open terminal:

Is it OK to use the one already open and ready?

man 7 kernel-command-line

No manual entry for kernel-command-line in section 7 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, 2013-05-16 at 17:48 -0400, Felix Miata wrote:

On 2013-05-16 23:37 (GMT+0200) Martin Helm composed:

...

Felix Miata composed:

...

...

Where is kernel-command-line(7) to be found?

...

open terminal:

Is it OK to use the one already open and ready?

:):) Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, 2013-05-16 at 17:23 -0400, Cristian Rodríguez wrote:

El 16/05/13 17:05, Roger Oberholtzer escribió:

...

On Thu, 2013-05-16 at 11:42 -0400, Cristian Rodríguez wrote:

...

linuxrc will not be running on an installed system, I thought that went without saying..

So there is a different place where all the supported options ate listed?

yes. read kernel-command-line(7) and the man pages/documents referenced there.

Thanks for that. I have found a new source of information. Still, the options I have been playing with and that were mentioned in the linuxrc web page (and that do exist on openSUSE 12.x) don't seem to be mentioned in any of the pages I checked. Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2013-05-16 11:26 (GMT-0400) Ken Schneider composed:

Roger Oberholtzer wrote:

...

We have splash=silent, but the green screen with the Geeko is still shown at boot and shutdown. This is on 12.1

Change it to splash=verbose

I know splash=verbose is equivalent to splash=0, which gains 6 precious characters for those bumping into cmdline length limitation. I believe both are equivalent to simply removing splash=silent, but would have to install splashy and/or bootsplash and/or Plymouth on something to unequivocally confirm. On 12.3 with none of the three installed, removal, at least in conjunction with silent removal, is equivalent. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, 2013-05-17 at 12:04 +0300, ellanios82 wrote:

however the boot process still is shown in same small characters regardless of the vga mode selected

. . . How to increase character size please ?

OTOH, when I added the splash=0, the text for the activity is oddly very big. It is not an issue, but since the topic is up, how to make the text smaller? Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2013-05-17 11:40 (GMT+0200) Roger Oberholtzer composed:

On Fri, 2013-05-17 at 12:04 +0300, ellanios82 wrote:

...

however the boot process still is shown in same small characters regardless of the vga mode selected

...

. . . How to increase character size please ?

OTOH, when I added the splash=0, the text for the activity is oddly very big. It is not an issue, but since the topic is up, how to make the text smaller?

AFAIK, there are two basic ways to control boot process (and virtual console) font size: 1-CONSOLE_FONT= in /etc/sysconfig/console 2-kernel cmdline A-with KMS active: video= B-without KMS active: 1-with Grub Legacy and Lilo: vga= 2-with Grub2: see man page (actually vga= still works) Whether Plymouth configuration may be another method I don't know, as I have Plymouth in none of my openSUSE and Fedora installations. Kernel cmdline is the method I usually use, as it's changeable on the fly at boot time. It works via screen resolution setting, which controls font size indirectly. Lower resolution means larger fonts. If you get big fonts, it's probably because something about KMS isn't working as it should on your hardware, often bad EDID. If you're getting tiny fonts, it's probably WAD based upon designers who like mousetype and filling the screen with an incomprehensibly huge amount of text at once. To get biggest text try both vga=normal or vga=788 and video=640x480 or video=800x600 on cmdline. To get smaller text depends on your screen's native or preferred resolution. The framebuffer HOWTO lists vga= modes available by both color depth and resolution. Temporarily using vga=ask will list those specifically applicable to your hardware and allow you to pick one of many. To get smaller text, choose vga=794 or vga=0x31a as a starting point for no KMS, and video=1280x1024, video=1400x1050 or video=1600x1200 for KMS on regular screens, and whatever are your display's supported modes for wide screens, such as video=1920x1080, video=1680x1050 or video=1440x900. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* ellanios82 [05-17-13 14:17]: [...]

__________________

using grub legacy ______________ - for me, vga=788 made no change at all

but, using :

video=640x480 worked great : nice large readable characters

Probably because grub(1) doesn't recognize "video=" on kernel command line and you get the monitor/system default which most likely is 640x480. fwiw, "yast bootloader" provides you the opportunity to set the video parameters. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, May 13 02:44:52 AM Felix Miata wrote:

On 2013-05-13 07:31 (GMT+0200) Roger Oberholtzer composed:

...

I have tried every kernel command line option I know to see if I can

Do you know them all? e.g. those listed on http://en.opensuse.org/Linuxrc

Felix, are you sure those parameters still work? About 5 year ago or so I was doing installations on various hardware and sometimes having difficulties with loading modules. Earlier I had used the text gui version of linuxrc which you could break out of the installation to access, and from there select modules and parameters, etc. But I could not get that to work any longer. Nor would the linuxrc parms BrokenModules and Insmod work if invoked on the kernel boot line. At that time I asked about this on the mailing list but got no response. Can anyone confirm whether or not this feature is supposed to still work? TIA --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2013-05-13 10:58 (GMT-0400) Dennis Gallien composed:

...

http://en.opensuse.org/Linuxrc

are you sure those parameters still work?

It would surprise me if they did. I imagine the voluntary patch write, review, commit process disinclines patch writers to conform wiki pages to the changes they have made. Wiki pages really need (a) front and center link(s) to corresponding official docs so as to lead Googlers to them, if not update the Wiki. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, 2013-05-13 at 08:34 -0400, Anton Aylward wrote:

Roger Oberholtzer said the following on 05/13/2013 01:31 AM:

...

I have a SuperMicro computer on which I seem unable to install openSUSE (11.2, 12.1 or 12.3). I can install Windows XP and CentOS 5.5. But not openSUSE. The machine has been back to the supplier, who claim they can find nothing wrong with it.

In the 'Same but different" category, I have seen machines where the CD/DVD drive works perfectly for everything except doing an install.

Of Linux that is. All versions. Its as if there's something that knows the difference between Linux and Windows ...

We have tried USB and DVD installs. We even installed an OEM image on the hard disk (we make those via KIWI) that contains a fully installed system, with only localization questions to be answered. All stop at the same place... Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org