Re: Old 32bit PC 650kRam less VidMem 1024x768 will not run on Stretch ok on Jessie
GiaThnYgeia composed on 2017-04-10 10:18 (UTC):
Felix Miata:
GiaThnYgeia composed on 2017-04-09 15:16 (UTC):
Felix Miata composed:
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.
"kernel cmdline" is also known as "Kernel Command-Line". This is the
group of parameters that are provided to the kernel and init system by
the bootloader as a component of using its menu. See
‘GRUB_CMDLINE_LINUX’ and following on
https://www.gnu.org/software/grub/manual/html_node/Simple-configuration.html
for more detail as pertains to the bootloader Stretch normally installs.
Would this be IT?
sudo nano /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet iomem=relaxed"
sudo update-grub
It would be #1 below, the step to take after proving that iomem=relaxed is
necessary for your Prosavage8 S3 Graphics gfxchip to work with 4.8 or newer
kernels.
zcat /usr/share/doc/linux-image-amd64/NNEWS.Debian.gz:
- 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
The cmdline last applied can be view by 'cat /proc/cmdline'.
Alternatively, the cmdline last applied before Xorg was started can be
found by viewing the first several lines of Xorg.0.log.
What goes onto the cmdline can be configured either by
1-reconfiguring the bootloader after a successful boot (usually via
changes to /etc/default/grub, then having grub write a new
/boot/grub/grub.cfg file with grub-mkconfig), or
2-while the bootloader is showing its menu after POST has completed, to
make a change applicable to the boot about to be started only (usually
by hitting the "e" key while the menu is onscreen".
#2 is what I was suggesting you first try to see if iomem=relaxed can
solve the problem you have using your ProSavage8 S3 Graphics gfxchip. If
it works then you should apply method #1.
"If it works"
This is the key term here, unless you are an experienced
developer/programmer Debian or Linux is not for you! To the vast
majority of people using a) browser 60% b) wordprocessor/office 15% c)
multimedia software 20% d) some pluginnplay software 4% e) misc. 1%
linux is virtually useless/dangerous!
If 32bit systems are no longer supported it should be stated with bold
headlines. The fact that somewhere in the fine print there is an alert
that "some" hardware may cause the upgrade from 8 to 9 will break your
system, that actually takes "some knowledge" to interpret as such, is
unacceptable.
This is not so much about 32 bit as it is about old gfx hardware for which
drivers have not been adapted to the KMS model on which more modern gfxchips
depend and succeed.
--
"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/
Reply to: