* Peter Joh. Brunner [03-07-17 13:10]:

when in jan 2017 support for 13.2 ceased, i downloaded 42.2 and installed it:

on my laptop: ok, with some minor difficulties.

on my wifes PC: ok, with some minor difficulties.

on my PC: installed OK, BUT: at first reboot after install and ever since ONLY a black display. no reaction to any input device, not even Ctrl+Alt+Del, also no reaction to hardware button on CDROM to eject medium but light indicating PC-On is lit.

when the grub boot screen appears, type "e" and when the edit screen comes up, add to the end of the "linux ... " line, 3 see if you get tty screens and can type there, then we can go farther -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Peter Joh. Brunner composed on 2017-03-07 19:07 (UTC+0100): ...

Sapphire Grafikkarte Atlantis Radeon 9250, 128MB DDR, DVI, TV-out, AGP, bulk/lite rtl (11046-65-20) On Board...

That's seriously ancient, unlikely to have been used on very many installations that got tested during the 42.2 development cycle, because Leap is 64 bit only, and AGP wasn't terribly widely supported on 64 bit hardware before it was replaced by the PCIe bus. This may be an obstacle currently unsolvable except by AGP card substitution or whole new machine. I just tried to get a Tumbleweed installation with a Radeon 9000 to work and also get a black screen. I noted it minutes ago here: https://bugzilla.opensuse.org/show_bug.cgi?id=1004453 You can try editing at Grub boot menu runtime to delete all kernel cmdline references to video configuration to see if it helps. In the bug, the cmdline VGA option must be removed so that framebuffers are not configured and used, leaving the vttys running in 80x25 text mode. If your 9250 in 42.2 is like my 9000 in TW, then X still may not work. Here, trying it locks up all console I/O, so I can only either use the reset button or proceed via remote login. If you can get it booted in text mode you can capture the journal for inspection and sharing: # journalctl -b > somefile.txt I get an oops during boot that contains the string "radeon". -- "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

* Dave Plater [03-08-17 09:45]:

On 07/03/2017 20:18, Patrick Shanahan wrote:

...

* Peter Joh. Brunner [03-07-17 13:10]:

...

when in jan 2017 support for 13.2 ceased, i downloaded 42.2 and installed it:

on my laptop: ok, with some minor difficulties.

on my wifes PC: ok, with some minor difficulties.

on my PC: installed OK, BUT: at first reboot after install and ever since ONLY a black display. no reaction to any input device, not even Ctrl+Alt+Del, also no reaction to hardware button on CDROM to eject medium but light indicating PC-On is lit.

when the grub boot screen appears, type "e" and when the edit screen comes up, add to the end of the "linux ... " line, 3

see if you get tty screens and can type there, then we can go farther

Bearing in mind that if graphical system was selected during installation then he can only get to runlevel 1 or 5. So replace 3 with 1 Dave P you may wish to rething this statement. and he probably is unable to achieve anything at "runlevel 1/S"

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Thank you Felix and Patrick and Carlos for your help But it's as i suspected - therefore i gave the detailed data of my PC - and the PCs Graphic card is too old. i tried his thing with 'e' in the boot select menue and altered the boot parameters in several ways without success in all cases when boot ended ok (protocol on ctrl-alt-f7): black display but on ctrl+alt+f1 there are messages: ... radeon 000:01:00.0: ring 0 stalled for more than >10 sec continuously. (this i didn't mention before i my question to this list) I can login as root on ctrl+alt+f1 and do as you proposed: journalctl -b > somefile.txt and cannot find an error there. So i will stay with 13.2 on my server PC, and replace it later on with new hardware. On 2017-03-08 04:07, Felix Miata wrote:

Peter Joh. Brunner composed on 2017-03-07 19:07 (UTC+0100): ...

...

Sapphire Grafikkarte Atlantis Radeon 9250, 128MB DDR, DVI, TV-out, AGP, bulk/lite rtl (11046-65-20) On Board...

That's seriously ancient, unlikely to have been used on very many installations that got tested during the 42.2 development cycle, because Leap is 64 bit only, and AGP wasn't terribly widely supported on 64 bit hardware before it was replaced by the PCIe bus.

If you can get it booted in text mode you can capture the journal for inspection and sharing:

# journalctl -b > somefile.txt

I get an oops during boot that contains the string "radeon".

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

Peter Joh. Brunner composed on 2017-03-10 17:16 (UTC+0100):

Thank you Felix and Patrick and Carlos for your help

But it's as i suspected - therefore i gave the detailed data of my PC - and the PCs Graphic card is too old.

i tried his thing with 'e' in the boot select menue and altered the boot parameters in several ways without success

in all cases when boot ended ok (protocol on ctrl-alt-f7): black display but on ctrl+alt+f1 there are messages: ... radeon 000:01:00.0: ring 0 stalled for more than >10 sec continuously. (this i didn't mention before i my question to this list)

If you were to report this on bugzilla.kernel.org I would amplify it with my own experience and maybe it would get fixed. If you do file a report, please include this reference: https://bugzilla.opensuse.org/show_bug.cgi?id=1004453#c13

I can login as root on ctrl+alt+f1 and do as you proposed: journalctl -b > somefile.txt and cannot find an error there.

So i will stay with 13.2 on my server PC, and replace it later on with new hardware.

As you can see in my recent comments in https://bugzilla.opensuse.org/show_bug.cgi?id=1004453 I had trouble much like yours with my Radeon 9000 AGP in Tumbleweed. However there is probably at least one more thing you can try. Add to the kernel cmdline after using e in Grub menu: radeon.agpmode=-1 Though it didn't work for me, it did for others in my Google search. What did work for me was removing my Radeon 9000 from the Pentium 4 PC it was in and put it in an older Athlon XP PC. I put an older Radeon 7500 AGP in the Pentium 4 PC and it works fine. And the 9000 works fine in the Athlon PC. Last I looked, Radeon 7500s were plentiful and very cheap on eBay. -- "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

Felix Miata writes:

That's seriously ancient, unlikely to have been used on very many installations that got tested during the 42.2 development cycle, because Leap is 64 bit only, and AGP wasn't terribly widely supported on 64 bit hardware before it was replaced by the PCIe bus.

Why is Tumbleweed 32 or 64, if Leap is 64 only? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org