Just installed 13.1 and even with the advanced failsafe second line in use, get to end of sequence, but with screen that scrambled – and there are no options for altering boot process like in earlier versions. What I noticed is that at beginning of install, and for the first time ever regarding the install screen itself, the screen was cut short, so had to go back and use less dense screen line option instead of the default. That put things right, but now I’m wondering if need to avoid the screen default also on the boot process – but there is no option to change it.
Any suggestions welcomed.
Ok where are you changing things you mean on the install or after the install in Yast?
In any case press e at the boot to edit the boot file. In is not clear but it sounds like there is a problem with the graphics card or chip. (what do you have??). So once in edit mode find the line starting with linux go to the ens of the line. Note it will be wrapped so it takes up several lines on screen. add a space and nomodeset. This should select a more generic driver that should work but will not have full sage of the card. Press F10 to continue the boot. If this works you will need to install the propritary driver for your video.
Changed line resolution on the install screen itself, since had lost bottom quarter and right quarter of the screen; new resolution completely returned it to full screen; possibly the e edit of boot will allow me to also change the resolution there also; will give both changes a try.
Thanks for the suggestion and advice.
Your instructions were very clear, and proceeded to insert nomodeset were specified [had to go down screen a ways to find it] and did so in initial regular boot option and in the “advanced” option [twice], but no difference was made to the scrambled screen at end of boot process. Anything else that I can try? [Is there some known problem with this 13.1 booting sequence – this total blocking is something never experienced with prior suse releases?].
Normally nomodeset works since the problems are mostly with video cards.
I have never heard of your problem before so you seem to be unique in that regrade
Did you choice a language at install (not English). Maybe it is a problem with the installed fonts not matching your language???
Sorry at a lose :shame:
Note that changes made to the boot screen are not permanent so only good for the current boot
Used English at install, and repeated the nomodeset at each new attempt.
Had hoped was some direct fix I could implement, but as seems not to be case can only assume the problem arises from my having an older laptop that suse no longer accommodates. Will likely have to reinstall an older suse release and look for different OS for future uses. Realized that more sophisticated releases might bring a slower performance, but never anticipated that suse wouldn’t always assure that its basics, like simple install, could always be counted upon.
Thanks again for those who took the trouble to respond; after over decade of suse use, is disappointing to have to switch.
On 2014-07-16 18:26 (GMT) wiliamvw composed:
> Had hoped was some direct fix I could implement, but as seems not to be
> case can only assume the problem arises from my having an older laptop
> that suse no longer accommodates. Will likely have to reinstall an older
> suse release and look for different OS for future uses. Realized that
> more sophisticated releases might bring a slower performance, but never
> anticipated that suse wouldn’t always assure that its basics, like
> simple install, could always be counted upon.
> Thanks again for those who took the trouble to respond; after over
> decade of suse use, is disappointing to have to switch.
My reader shows 7 posts in this thread. Among them, I found none in which you
provide any description whatsoever of your hardware or the model of your
laptop. How do you expect useful help when you tell us nothing about your
hardware?
I have hundreds of openSUSE installations on many kinds of hardware, none of
which is as new as 5 years old. I’ve been unable to find any older hardware
on which video cannot still be made usable, or on which openSUSE cannot still
be installed.
If you want useful help, start by telling us what video you have, preferably
via output from ‘lspci | grep VGA"’. Other hardware info might be useful too.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
This series uses vesa, so assume that is for this one also[Itronix IX250, Celeron 850MHz with .524 GB ram] and recall also used Savage with 256 k ram, chip set ATI, and had 600x800 display; as can’t get into yast, have to use memory for now [did lspci, and only got that VGA, will try adding the grep vga asap]; also tried lshw, but got command not found. Hadn’t put in this before since assumed wasn’t much more to be tried, but thanks for the attention and suggestions.
Tried the lspci | grep VGA and got that was improper syntax; tried all variations, with same result; one try gave that grep was unknown; tried lshw, whereis, which, init, startx, etc. and all gave that command-not-found.
On 2014-07-21 23:06 (GMT) wiliamvw composed:
>> This series uses vesa, so assume that is for this one also[Itronix
>> IX250, Celeron 850MHz with .524 GB ram] and recall also used Savage with
>> 256 k ram, chip set ATI, and had 600x800 display; as can’t get into
>> yast, have to use memory for now [did lspci, and only got that VGA, will
>> try adding the grep vga asap]; also tried lshw, but got command not
>> found. Hadn’t put in this before since assumed wasn’t much more to be
>> tried, but thanks for the attention and suggestions.
> Tried the lspci | grep VGA and got that was improper syntax; tried
> all variations, with same result; one try gave that grep was unknown;
> tried lshw, whereis, which, init, startx, etc. and all gave that
> command-not-found.
Try again logged in as root, or else prepend sudo to lspci.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
Finally got more specifics on my laptop [as couldn’t use control center].
VGA-compatible controller: S3 Savage IX/MV ; probably the only useful item, but others are:
CPU: Celeron CD-ROM: TEAC DV-28E-B Ethernet controller: Actiontec Electronics EtherExpress PRO/100B (TX) (MiniPCI)
HUB: Alcor Micro Hub also listed as hub: Linux 3.11.6-4-default uhci hcd UHCL Host Controller
IDE interface: Intel 82371AB/EB/MB P11x4 IDE Keyboard: AT Translated Set 2 keyboard
Modem: Actiontec Electronics LT WinModem 56k (MiniPCI Ethernet)
PS/2 mouse: SynPS/2 Synaptics Touch Pad
USB controller: Inter 82371AB/EB/MB P11x4 USB
I also tried reinstalling using a simpler desktop, LXDE instead of Gnome or KDE, but still got scrambled screen even using the alternative safe boot process.
If no one can think of something else for me to try, is it possible to “update” using an older suse version (12.3)? Not sure how that would work, but probably just go to a whole new install.
On 2014-08-13 23:36 (GMT) wiliamvw composed:
> VGA-compatible controller: S3 Savage IX/MV ; probably the only useful
> item, but others are:
> CPU: Celeron CD-ROM…
> If no one can think of something else for me to try, is it possible to
> “update” using an older suse version (12.3)? Not sure how that would
> work, but probably just go to a whole new install.
That S3 is seriously ancient hardware (like the rest of that laptop), rarely
seen any more. There is a good chance its savage driver got broken by
evolutionary changes to Xorg and/or kernel, and you’re the first to notice
and apprise others of the experience. If you were to try installing Factory
instead of something older, then filing a bug report if the video problem
remains, it might get fixed, or someone who knows might offer a solution.
Broken drivers for ancient hardware for released versions usually won’t get
fixed unless the developers know a problem exists, and can backport a fix
from the latest version into a fix for a released version.
If there is a driver bug, it might be old enough to exist back into versions
older than 12.3, so you might want to try the oldest live media you can find
just to get it working at all, then working your way forward with newer lives
until a date range can be narrowed down.
Last changelog entry for 13.1’s savage driver, August 2013, was only for
non-x86 hardware. Last before that was March 2013, near the time of 12.3
release. My guess would be that whatever is bad in 13.1 is bad in 12.3 too,
so trying something older might be less burden on your time.
The wise are known for their understanding, and pleasant
words are persuasive.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
you’ve tried nomodeset, and maybe splash=verbose as a boot option to troubleshoot more,
but yeah, just go to a whole new install is a next step imho . . .
You could try an older Fedora linux spin, lxde or other -
I have had success with Fedora 11 gnome and Fedora 12 KDE on an old Sharp laptop,
and currently have hard drive install of F19 as well as Centos 7.
I still have a Fedora 15 KDE installed all on a 4 GB USB - use it to boot up on university computers -
it is NOT a live version with persistence - but is made from from the older Live anaconda installer in use before Fedora 19.
Download the isos for live in the archive :
https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/12/Live/i686/
Good luck.
Correcting the link for fedora 15 archive . . .
Thank you all for your suggestions; I think mrmazda had it right about broken link to video card, but tried the new install to the most recent before 13.1 [12.3] and it did finally come up [after 10 minutes of slow manipulations], and since then has booted fairly rapidly [considering its age].
Installing Apache OO took some time [wish they had that as an install option], but finally have everything I need for my documents, which is all that really concerns me.