Re: Old 32bit PC 650kRam less VidMem 1024x768 will not run on Stretch ok on Jessie
- Date: Sun, 9 Apr 2017 10:23:10 -0400
- From: Felix Miata <mrmazda@xxxxxxxxxxxxx>
- Subject: Re: Old 32bit PC 650kRam less VidMem 1024x768 will not run on Stretch ok on Jessie
GiaThnYgeia composed on 2017-04-09 13:45 (UTC):
GiaThnYgeia composed on 2017-04-09 10:22 (UTC):
See attached file for complete lshw of the failed stretch upgrade
You need to do it again but without lshw outputting in xml format. With
no switches lshw outputs in plain text, exactly the right format for an
'inxi -c0 -Gx' should be all we need to address this thread subject, as
would the lscpi or inxi commands suggested in a previous thread response.
> I am not physically there anymore, this is what they sent me.
> Power Management bus mastering PCI capabilities listing VGA compatible
> controller VT8375 [ProSavage8 KM266/KL266] [5333:8D04] S3 Graphics Ltd.
>  0 pci@0000:01:00.0 00 32 66000000
The ProSavage8 S3 Graphics gfxchip described there, which has no KMS support and
thus requires a user-space driver, fits into the following description from Stretch:
linux-latest (76) unstable; urgency=medium
* From Linux 4.8, several changes have been made in the kernel
configuration to 'harden' the system, i.e. to mitigate security bugs.
Some changes may cause legitimate applications to fail, and can be
reverted by run-time configuration:
- On most architectures, the /dev/mem device can no longer be used to
access devices that also have a kernel driver. This breaks dosemu
and some old user-space graphics drivers. To allow this, set the
kernel parameter: iomem=relaxed
IOW, it is suggested that iomem=relaxed may need to be included on kernel
cmdline for the old user-space xserver-xorg-video-savage driver to work with
your gfxchip in Stretch.
"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/