Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Can the latest stable Debian be compelled to run in vesa mode, rather than the motherboard graphics card, if the said card doesn't have drivers available? How?

86 views
Skip to first unread message

Susmita/Rajib

unread,
Apr 18, 2021, 1:30:05 PM4/18/21
to
Namaste, my dear illustrious Team Leaders and Solution providers,

The questions was asked by Dr. Cater here:
https://lists.debian.org/debian-user/2021/04/msg00506.html
in relation to my post here:
https://lists.debian.org/debian-user/2021/04/msg00504.html

That post was on a different issue, of my asking for suggestion on
which Debian-authorised laptop to buy this time to avoid undue
complexity with the ones that I have already.

This one relates to my HCL-Me laptop. Presently, Debian Live isn't
able to run on it even in Vesa. GUI installation is possible, but not
using vesa post-installation.

Earlier when computers and drivers were 32bit, drivers from nvidia
downloaded directly would work. Download, chmod to exec and then run
the script from the init 3 mode with ./driver.run, and the driver
worked fine.

But as systems upgraded to 64bit, nvidia fails. nvidia has stopped
supporting, stopped upgrading the driver. The driver is last updated
way back. Nouveau doesn't support the card.

>>
>> Debian nvidia drivers, as ever, fails to install.
>
> How did you install them - what procedure did you follow?

This time, failed to use synaptic in Debian, as I don't bave a GUI
running there in init 5. In init 3, internet isn't accessible.
Information here:
http://forums.debian.net/viewtopic.php?f=17&t=149248

So used Knoppix persistent, a little altered Debian, with persistent.
Used vesa for knoppix grub and booted into GUI in init 5.

Updated synaptic.
Then
Searched for GeForce 8200M G [MCP79]

--------------------------------------------------------------------
Query:
BTW, what would be the equivalent command with apt like we have
"synaptic search"?
--------------------------------------------------------------------

Result:
nvidia-legacy-340xx-driver
nvidia-legacy-340xx-kernel-dkms
xserver-xorg-video-nvidia-legacy-340xx
nvidia-legacy-340xx-kernel-source


The first 3 of 4 packages chosen with apply. Source ignored.



Report:
----------------------------------------------------------------
E: nvidia-legacy-340xx-kernel-dkms: installed
nvidia-legacy-340xx-kernel-dkms package post-installation script
subprocess returned error exit status 10
E: nvidia-legacy-340xx-driver: dependency problems - leaving unconfigured
----------------------------------------------------------------

Installation Details:
----------------------------------------------------------------
Selecting previously unselected package update-glx.
(Reading database ... 416821 files and directories currently installed.)
Preparing to unpack .../update-glx_1.2.0_i386.deb ...
Unpacking update-glx (1.2.0) ...
Selecting previously unselected package glx-alternative-mesa.
Preparing to unpack .../glx-alternative-mesa_1.2.0_i386.deb ...
Unpacking glx-alternative-mesa (1.2.0) ...
Selecting previously unselected package nvidia-installer-cleanup.
Preparing to unpack .../nvidia-installer-cleanup_20151021+13_i386.deb ...
Unpacking nvidia-installer-cleanup (20151021+13) ...
Setting up nvidia-installer-cleanup (20151021+13) ...
Selecting previously unselected package glx-diversions.
(Reading database ... 416946 files and directories currently installed.)
Preparing to unpack .../00-glx-diversions_1.2.0_i386.deb ...
Unpacking glx-diversions (1.2.0) ...
Selecting previously unselected package glx-alternative-nvidia.
Preparing to unpack .../01-glx-alternative-nvidia_1.2.0_i386.deb ...
Unpacking glx-alternative-nvidia (1.2.0) ...
Selecting previously unselected package nvidia-legacy-340xx-alternative.
Preparing to unpack
.../02-nvidia-legacy-340xx-alternative_340.108-10_i386.deb ...
Unpacking nvidia-legacy-340xx-alternative (340.108-10) ...
Selecting previously unselected package libnvidia-legacy-340xx-glcore:i386.
Preparing to unpack .../03-libnvidia-legacy-340xx-glcore_340.108-10_i386.deb ...
Unpacking libnvidia-legacy-340xx-glcore:i386 (340.108-10) ...
Selecting previously unselected package nvidia-support.
Preparing to unpack .../04-nvidia-support_20151021+13_i386.deb ...
Unpacking nvidia-support (20151021+13) ...
Selecting previously unselected package libgl1-nvidia-legacy-340xx-glx:i386.
Preparing to unpack
.../05-libgl1-nvidia-legacy-340xx-glx_340.108-10_i386.deb ...
Unpacking libgl1-nvidia-legacy-340xx-glx:i386 (340.108-10) ...
Selecting previously unselected package libnvidia-legacy-340xx-eglcore:i386.
Preparing to unpack
.../06-libnvidia-legacy-340xx-eglcore_340.108-10_i386.deb ...
Unpacking libnvidia-legacy-340xx-eglcore:i386 (340.108-10) ...
Selecting previously unselected package libegl1-nvidia-legacy-340xx:i386.
Preparing to unpack .../07-libegl1-nvidia-legacy-340xx_340.108-10_i386.deb ...
Unpacking libegl1-nvidia-legacy-340xx:i386 (340.108-10) ...
Selecting previously unselected package nvidia-legacy-340xx-driver-libs:i386.
Preparing to unpack
.../08-nvidia-legacy-340xx-driver-libs_340.108-10_i386.deb ...
Unpacking nvidia-legacy-340xx-driver-libs:i386 (340.108-10) ...
Selecting previously unselected package libnvidia-legacy-340xx-ml1:i386.
Preparing to unpack .../09-libnvidia-legacy-340xx-ml1_340.108-10_i386.deb ...
Unpacking libnvidia-legacy-340xx-ml1:i386 (340.108-10) ...
Selecting previously unselected package nvidia-legacy-340xx-driver-bin.
Preparing to unpack
.../10-nvidia-legacy-340xx-driver-bin_340.108-10_i386.deb ...
Unpacking nvidia-legacy-340xx-driver-bin (340.108-10) ...
Selecting previously unselected package xserver-xorg-video-nvidia-legacy-340xx.
Preparing to unpack
.../11-xserver-xorg-video-nvidia-legacy-340xx_340.108-10_i386.deb ...
Unpacking xserver-xorg-video-nvidia-legacy-340xx (340.108-10) ...
Selecting previously unselected package nvidia-legacy-340xx-vdpau-driver:i386.
Preparing to unpack
.../12-nvidia-legacy-340xx-vdpau-driver_340.108-10_i386.deb ...
Unpacking nvidia-legacy-340xx-vdpau-driver:i386 (340.108-10) ...
Selecting previously unselected package nvidia-kernel-common.
Preparing to unpack .../13-nvidia-kernel-common_20151021+13_i386.deb ...
Unpacking nvidia-kernel-common (20151021+13) ...
Selecting previously unselected package nvidia-modprobe.
Preparing to unpack .../14-nvidia-modprobe_460.32.03-1_i386.deb ...
Unpacking nvidia-modprobe (460.32.03-1) ...
Selecting previously unselected package nvidia-legacy-340xx-kernel-support.
Preparing to unpack
.../15-nvidia-legacy-340xx-kernel-support_340.108-10_i386.deb ...
Unpacking nvidia-legacy-340xx-kernel-support (340.108-10) ...
Selecting previously unselected package nvidia-legacy-340xx-kernel-dkms.
Preparing to unpack
.../16-nvidia-legacy-340xx-kernel-dkms_340.108-10_i386.deb ...
Unpacking nvidia-legacy-340xx-kernel-dkms (340.108-10) ...
Selecting previously unselected package nvidia-legacy-340xx-driver.
Preparing to unpack .../17-nvidia-legacy-340xx-driver_340.108-10_i386.deb ...
Unpacking nvidia-legacy-340xx-driver (340.108-10) ...
Selecting previously unselected package libnvidia-legacy-340xx-cfg1:i386.
Preparing to unpack .../18-libnvidia-legacy-340xx-cfg1_340.108-10_i386.deb ...
Unpacking libnvidia-legacy-340xx-cfg1:i386 (340.108-10) ...
Selecting previously unselected package nvidia-persistenced.
Preparing to unpack .../19-nvidia-persistenced_460.32.03-1_i386.deb ...
Unpacking nvidia-persistenced (460.32.03-1) ...
Selecting previously unselected package nvidia-settings-legacy-340xx.
Preparing to unpack .../20-nvidia-settings-legacy-340xx_340.108-4_i386.deb ...
Unpacking nvidia-settings-legacy-340xx (340.108-4) ...
Selecting previously unselected package libgles1-nvidia-legacy-340xx:i386.
Preparing to unpack .../21-libgles1-nvidia-legacy-340xx_340.108-10_i386.deb ...
Unpacking libgles1-nvidia-legacy-340xx:i386 (340.108-10) ...
Selecting previously unselected package libgles2-nvidia-legacy-340xx:i386.
Preparing to unpack .../22-libgles2-nvidia-legacy-340xx_340.108-10_i386.deb ...
Unpacking libgles2-nvidia-legacy-340xx:i386 (340.108-10) ...
Setting up nvidia-support (20151021+13) ...
Setting up nvidia-kernel-common (20151021+13) ...
Setting up update-glx (1.2.0) ...
Setting up nvidia-modprobe (460.32.03-1) ...
Setting up libnvidia-legacy-340xx-glcore:i386 (340.108-10) ...
Setting up libnvidia-legacy-340xx-eglcore:i386 (340.108-10) ...
Setting up glx-alternative-mesa (1.2.0) ...
Setting up glx-diversions (1.2.0) ...
Removing diverted 'libGL.so' symlink with unexpected target 'libGL.so.1'.
Restoring diverted 'libGL.so' symlink.
Processing triggers for mailcap (3.68) ...
Warning: package evince listed in /etc/mailcap.order does not have
mailcap entries.
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for initramfs-tools (0.139) ...
Processing triggers for gnome-menus (3.36.0-1) ...
Processing triggers for libc-bin (2.31-9) ...
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for glx-alternative-mesa (1.2.0) ...
update-alternatives: using /usr/lib/mesa-diverted to provide
/usr/lib/glx (glx) in auto mode
update-alternatives: using /usr/lib/mesa-diverted to provide
/usr/lib/mesa-diverted/libGL.so-master (libGL.so-master) in auto mode
Setting up glx-alternative-nvidia (1.2.0) ...
Processing triggers for glx-alternative-nvidia (1.2.0) ...
Setting up nvidia-legacy-340xx-alternative (340.108-10) ...
Processing triggers for nvidia-legacy-340xx-alternative (340.108-10) ...
update-alternatives: using /usr/lib/nvidia/legacy-340xx to provide
/usr/lib/nvidia/nvidia (nvidia) in auto mode
Setting up libegl1-nvidia-legacy-340xx:i386 (340.108-10) ...
Setting up libgl1-nvidia-legacy-340xx-glx:i386 (340.108-10) ...
Setting up libnvidia-legacy-340xx-cfg1:i386 (340.108-10) ...
Setting up xserver-xorg-video-nvidia-legacy-340xx (340.108-10) ...
Setting up nvidia-legacy-340xx-vdpau-driver:i386 (340.108-10) ...
Setting up libgles2-nvidia-legacy-340xx:i386 (340.108-10) ...
Setting up libgles1-nvidia-legacy-340xx:i386 (340.108-10) ...
Setting up nvidia-legacy-340xx-kernel-support (340.108-10) ...
Setting up nvidia-settings-legacy-340xx (340.108-4) ...
Setting up nvidia-persistenced (460.32.03-1) ...
Warning: The home dir /var/run/nvpd/ you specified can't be accessed:
No such file or directory
Adding system user `nvpd' (UID 149) ...
Adding new group `nvpd' (GID 162) ...
Adding new user `nvpd' (UID 149) with group `nvpd' ...
Not creating home directory `/var/run/nvpd/'.
invoke-rc.d: could not determine current runlevel
Setting up nvidia-legacy-340xx-driver-libs:i386 (340.108-10) ...
Setting up libnvidia-legacy-340xx-ml1:i386 (340.108-10) ...
Setting up nvidia-legacy-340xx-driver-bin (340.108-10) ...
Processing triggers for nvidia-legacy-340xx-alternative (340.108-10) ...
update-alternatives: updating alternative /usr/lib/nvidia/legacy-340xx
because link group nvidia has changed slave links
Setting up nvidia-legacy-340xx-kernel-dkms (340.108-10) ...
Loading new nvidia-legacy-340xx-340.108 DKMS files...
Building for 5.10.10-64
Building initial module for 5.10.10-64
Error! Bad return status for module build on kernel: 5.10.10-64 (x86_64)
Consult /var/lib/dkms/nvidia-legacy-340xx/340.108/build/make.log for
more information.
dpkg: error processing package nvidia-legacy-340xx-kernel-dkms (--configure):
installed nvidia-legacy-340xx-kernel-dkms package post-installation
script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-legacy-340xx-driver:
nvidia-legacy-340xx-driver depends on nvidia-legacy-340xx-kernel-dkms
(= 340.108-10) | nvidia-legacy-340xx-kernel-340.108; however:
Package nvidia-legacy-340xx-kernel-dkms is not configured yet.
Package nvidia-legacy-340xx-kernel-340.108 is not installed.
Package nvidia-legacy-340xx-kernel-dkms which provides
nvidia-legacy-340xx-kernel-340.108 is not configured yet.

dpkg: error processing package nvidia-legacy-340xx-driver (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.31-9) ...
Processing triggers for initramfs-tools (0.139) ...
Processing triggers for update-glx (1.2.0) ...
Processing triggers for glx-alternative-nvidia (1.2.0) ...
update-alternatives: using /usr/lib/nvidia to provide /usr/lib/glx
(glx) in auto mode
Processing triggers for libc-bin (2.31-9) ...
Processing triggers for initramfs-tools (0.139) ...
Errors were encountered while processing:
nvidia-legacy-340xx-kernel-dkms
nvidia-legacy-340xx-driver
Running prelink, please wait...
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up nvidia-legacy-340xx-kernel-dkms (340.108-10) ...
Removing old nvidia-legacy-340xx-340.108 DKMS files...

------------------------------
Deleting module version: 340.108
completely from the DKMS tree.
------------------------------
Done.
Loading new nvidia-legacy-340xx-340.108 DKMS files...
Building for 5.10.10-64
Building initial module for 5.10.10-64
Error! Bad return status for module build on kernel: 5.10.10-64 (x86_64)
Consult /var/lib/dkms/nvidia-legacy-340xx/340.108/build/make.log for
more information.
dpkg: error processing package nvidia-legacy-340xx-kernel-dkms (--configure):
installed nvidia-legacy-340xx-kernel-dkms package post-installation
script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-legacy-340xx-driver:
nvidia-legacy-340xx-driver depends on nvidia-legacy-340xx-kernel-dkms
(= 340.108-10) | nvidia-legacy-340xx-kernel-340.108; however:
Package nvidia-legacy-340xx-kernel-dkms is not configured yet.
Package nvidia-legacy-340xx-kernel-340.108 is not installed.
Package nvidia-legacy-340xx-kernel-dkms which provides
nvidia-legacy-340xx-kernel-340.108 is not configured yet.

dpkg: error processing package nvidia-legacy-340xx-driver (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
nvidia-legacy-340xx-kernel-dkms
nvidia-legacy-340xx-driver

>
> If you use the proprietary drivers, then you will need to follow particular
> steps. The drivers you need are referenced here:
> https://packages.debian.org/buster/nvidia-legacy-340xx-driver
[...]
Please this following link be looked into:
http://bit.ly/HCL_Pen2Core

The /var/log/nvidia-installer.log is also uploaded to the above Driver folder.

For 11 years now, I have been dealing with repeated installation of
this card. Native Debian drivers failed always, but drivers downloaded
from nvidia website worked well. When 32bit was operational.

Didn't upgrade OS for a long time therefore, from 2013 to 2021.

Presently, I used the Debian grub to run knoppix, either as iso by
loopback loop, or with iso extracted and am presently using knoppix
for the HCL Me laptop.

Please tell me if there is a possibility of using Debian to use vesa
(or fbdev) from grub, although fbdev is deprecated, vesa runs fine.
But a little stressful for the motherboard and CPU. Heat up.

Best,
Rajib

Andrew M.A. Cater

unread,
Apr 18, 2021, 2:00:04 PM4/18/21
to
On Sun, Apr 18, 2021 at 10:36:07PM +0530, Susmita/Rajib wrote:
> Namaste, my dear illustrious Team Leaders and Solution providers,
>
> The questions was asked by Dr. Cater here:
> https://lists.debian.org/debian-user/2021/04/msg00506.html
> in relation to my post here:
> https://lists.debian.org/debian-user/2021/04/msg00504.html
>
> That post was on a different issue, of my asking for suggestion on
> which Debian-authorised laptop to buy this time to avoid undue
> complexity with the ones that I have already.
>
> This one relates to my HCL-Me laptop. Presently, Debian Live isn't
> able to run on it even in Vesa. GUI installation is possible, but not
> using vesa post-installation.
>

I followed through the screenshots you provided.

> Earlier when computers and drivers were 32bit, drivers from nvidia
> downloaded directly would work. Download, chmod to exec and then run
> the script from the init 3 mode with ./driver.run, and the driver
> worked fine.
>
> But as systems upgraded to 64bit, nvidia fails. nvidia has stopped
> supporting, stopped upgrading the driver. The driver is last updated
> way back. Nouveau doesn't support the card.
>
> >>
> >> Debian nvidia drivers, as ever, fails to install.
> >
> > How did you install them - what procedure did you follow?
>
> This time, failed to use synaptic in Debian, as I don't bave a GUI
> running there in init 5. In init 3, internet isn't accessible.
> Information here:
> http://forums.debian.net/viewtopic.php?f=17&t=149248
>
> So used Knoppix persistent, a little altered Debian, with persistent.
> Used vesa for knoppix grub and booted into GUI in init 5.
>
> Updated synaptic.
> Then
> Searched for GeForce 8200M G [MCP79]
>
> --------------------------------------------------------------------
> Query:
> BTW, what would be the equivalent command with apt like we have
> "synaptic search"?

apt-cache search first of all, apt-cache show to show more information
> --------------------------------------------------------------------
>
> Result:
> nvidia-legacy-340xx-driver
> nvidia-legacy-340xx-kernel-dkms
> xserver-xorg-video-nvidia-legacy-340xx
> nvidia-legacy-340xx-kernel-source
>
>
> The first 3 of 4 packages chosen with apply. Source ignored.
>
You can't ignore the source - you may have to apply it to a kernel.
YOu have dependency errors. That's a bad sign.
WHY, oh, why are you trying to use Bullseye and kernel 5.10 at this stage?

> > If you use the proprietary drivers, then you will need to follow particular
> > steps. The drivers you need are referenced here:
> > https://packages.debian.org/buster/nvidia-legacy-340xx-driver
> [...]
> Please this following link be looked into:
> http://bit.ly/HCL_Pen2Core
>
> The /var/log/nvidia-installer.log is also uploaded to the above Driver folder.
>
> For 11 years now, I have been dealing with repeated installation of
> this card. Native Debian drivers failed always, but drivers downloaded
> from nvidia website worked well. When 32bit was operational.
>
> Didn't upgrade OS for a long time therefore, from 2013 to 2021.
>

First things first: you have a laptop which is 64 bit capable, I think.
You also have a laptop which is capable of using UEFI. Use them.
Use those options.

Download a CD/DVD including firmware if that's what it takes -
First link is CD which may be enough, second is DVD

https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/firmware-10.9.0-amd64-netinst.iso
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-dvd/firmware-10.9.0-amd64-DVD-1.iso

> Presently, I used the Debian grub to run knoppix, either as iso by
> loopback loop, or with iso extracted and am presently using knoppix
> for the HCL Me laptop.
>
> Please tell me if there is a possibility of using Debian to use vesa
> (or fbdev) from grub, although fbdev is deprecated, vesa runs fine.
> But a little stressful for the motherboard and CPU. Heat up.
>
> Best,
> Rajib

Try the above with current Debian 10 and a text mode expert install _first_
Do NOT install a graphical environment until you can get the laptop working
in text mode. At that point, you may have to deal with installing nouveau
or, possibly, the Nvidia proprietary drivers.

You will almost certainly need the build-essential tools to build Nvidia
code if you use the proprietary drivers.

Please try taking this single step by single step and explaining what
errors you are getting as you go. For large amounts of logs, you might
need to use pastebin.

Hope this helps, all the best,

Andy C.
>

Susmita/Rajib

unread,
Apr 18, 2021, 11:10:04 PM4/18/21
to
On Sun, 18 Apr 2021 17:56:46 +0000, "Andrew M.A. Cater"
<amac...@einval.com> wrote:
[QUOTE]
[...]
I followed through the screenshots you provided.
[...]
You can't ignore the source - you may have to apply it to a kernel.
[/QUOTE]


Okay, learnt. Thank you.


[QUOTE]
[...]
You have dependency errors. That's a bad sign.

[...]
WHY, oh, why are you trying to use Bullseye and kernel 5.10 at this stage?
[/QUOTE]

I used the example of knoppix. Regarding Bullseye and kernel 5.10,
that was knoppix.



[QUOTE]
[...]
First things first: you have a laptop which is 64 bit capable, I think.
You also have a laptop which is capable of using UEFI. Use them.
Use those options.
[...]
[/QUOTE]

64bit yes. For the problematic laptop, UEFI, no.


[QUOTE]
Download a CD/DVD including firmware if that's what it takes -
First link is CD which may be enough, second is DVD

https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/firmware-10.9.0-amd64-netinst.iso
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-dvd/firmware-10.9.0-amd64-DVD-1.iso
[...]
[/QUOTE]

> Presently, I used the Debian grub to run knoppix, either as iso by
> loopback loop, or with iso extracted and am presently using knoppix
> for the HCL Me laptop.
>
> Please tell me if there is a possibility of using Debian to use vesa
> (or fbdev) from grub, although fbdev is deprecated, vesa runs fine.
> But a little stressful for the motherboard and CPU. Heat up.
>
> Best,
> Rajib


[QUOTE]
Try the above with current Debian 10 and a text mode expert install _first_
Do NOT install a graphical environment until you can get the laptop working
in text mode. At that point, you may have to deal with installing nouveau
or, possibly, the Nvidia proprietary drivers.

You will almost certainly need the build-essential tools to build Nvidia
code if you use the proprietary drivers.

Please try taking this single step by single step and explaining what
errors you are getting as you go. For large amounts of logs, you might
need to use pastebin.

Hope this helps, all the best,

Andy C.
[/QUOTE]

Thank you, Dr. Cater.

Until recently, Debian 10.8 was the most recent one. So I had used that one.

One question: After I have installed in the text mode, what codes do I
use for apt-get, or to be precise, like synaptic search in GUI, how do
I search for the specific nvidia drivers for "GeForce 8200M G
[MCP79]"? What would be equivalent apt-get lines?

Best.
Rajib

Susmita/Rajib

unread,
Apr 18, 2021, 11:30:05 PM4/18/21
to
On Sun, 18 Apr 2021 21:52:25 -0400, Felix Miata <mrm...@earthlink.net> wrote:
[...]
As above indicated, it works with Debian 10, using the FOSS default X driver
(Modesetting DIX), along with the Nouveau kernel driver it depends on. No
proprietary NVidia or other non-Debian software is required for competent Xorg
operation. I have other NVidia GPUs in other PCs, all newer than yours, and all
using the very same modesetting DIX driver.
[...]

Thank you, Dr./Mr Miata, for posting to my thread to inform me.

Much appreciated.

Could you please guide as to what lines should I use? What packages?

Please also oblige me and send a copy of your posts to my Gmailbox.

Best.
Rajib

Susmita/Rajib

unread,
Apr 19, 2021, 12:30:04 AM4/19/21
to
Would the setps as described in the following link be necessary?
http://www.linuxfromscratch.org/blfs/view/svn/x/xorg-server.html

-----------------------------------------------------------------------
Installation of Xorg Server

Install the server by running the following commands:

./configure $XORG_CONFIG \
--enable-glamor \
--enable-suid-wrapper \
--with-xkb-output=/var/lib/xkb &&
make

To test the results, issue: make check. You will need to run ldconfig
as the root user first or some tests may fail.

Now as the root user:

make install &&
mkdir -pv /etc/X11/xorg.conf.d &&
cat >> /etc/sysconfig/createfiles << "EOF"
/tmp/.ICE-unix dir 1777 root root
/tmp/.X11-unix dir 1777 root root
EOF

Command Explanations

--enable-glamor: Build the Glamor DIX (Device Independent X) module
which is currently used by: R600 or later radeon video chipsets, the
modesetting driver (which is part of this package) for hardware using
KMS which offers acceleration, and (optionally) the intel driver.

--enable-suid-wrapper: Builds the suid-root wrapper for legacy driver
support on rootless xserver systems.

--disable-systemd-logind: This switch disables elogind integration
allowing Xorg Server to work without having the PAM module configured.

--enable-install-setuid: This switch restores the setuid bit to the
Xorg executable allowing Xorg Server to work with a virtual terminal
designated on the startx command line.

cat >> /etc/sysconfig/createfiles...: This command creates the
/tmp/.ICE-unix and /tmp/.X11-unix directories at startup, and ensures
that the permissions and ownership are correct as required by the
server.

--enable-dmx: Builds the DMX (Distributed Multihead X) server.

--enable-kdrive: This option allows the configure script to enable
Xephyr if its dependencies are met.
-----------------------------------------------------------------------

Best,
Rajib

Susmita/Rajib

unread,
Apr 19, 2021, 12:50:04 AM4/19/21
to
On Mon, 19 Apr 2021 00:12:29 -0400, Felix Miata <mrm...@earthlink.net> wrote:
Ref: https://lists.debian.org/debian-user/2021/04/msg00530.html

"...
Unless and until all traces of NVidia's driver installation and associated
configuration changes have been purged from your machine, I can be no
help except
WRT eradicating them. Even in that regard others know better than me how to
proceed. AFAICT, whatever NVidia driver installation does eliminates
any chance to
make FOSS drivers work acceptably.
..."

Okay, in any case I am to reinstall fresh and latest stable Debian, as
advised by Dr./Mr. Cater.

So in nutshell, may please the steps be described? The idea involved?

It is requested that a copy of email be sent to my Gmailbox please.

Best.
Rajib

Felix Miata

unread,
Apr 19, 2021, 1:00:04 AM4/19/21
to
Susmita/Rajib composed on 2021-04-19 8:35 (UTC+05300):

> On Sun, 18 Apr 2021 21:52:25 -0400, Felix Miata wrote:
> [...]
> As above indicated, it works with Debian 10, using the FOSS default X driver
> (Modesetting DIX), along with the Nouveau kernel driver it depends on. No
> proprietary NVidia or other non-Debian software is required for competent Xorg
> operation. I have other NVidia GPUs in other PCs, all newer than yours, and all
> using the very same modesetting DIX driver.
> [...]

> Could you please guide as to what lines should I use? What packages?

In order to use the Modesetting DIX driver with GeForce 8200M G [MCP79] it should
be entirely sufficient as follows:

1-eradicate/purge/uninstall/delete all traces of NVidia's proprietary drivers
2-purge xserver-xorg-video-nouveau
3-reboot

Purging xserver-xorg-video-nouveau is not necessary, just simpler. It may be
necessary to configure specially in /etc/X11/ to not use the Nouveau DDX if it is
installed.

Note that #2 above may involve reinstalling one or more libraries required for
utilizing FOSS drivers with any model GeForce.

A visit to the following may prove fruitful moving forward:
<https://www.linuxquestions.org/questions/blog/mrmazda-1035595/amd-intel-and-nvidia-x-graphics-driver-primer-38306/>
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata *** http://fm.no-ip.com/

Felix Miata

unread,
Apr 19, 2021, 1:50:04 AM4/19/21
to
Susmita/Rajib composed on 2021-04-19 10:30 (UTC+0530):

> Okay, in any case I am to reinstall fresh and latest stable Debian, as
> advised by Dr./Mr. Cater.

> So in nutshell, may please the steps be described? The idea involved?

No specific steps should be necessary to enable use of your GeForce 8200M G
[MCP79]. However, a default installation will include xserver-xorg-video-nouveau,
to provide the nouveau DDX, which should work with all non-ancient NVidia GPUs,
such as GeForce 8200M G [MCP79]. To use the modesetting DIX instead of the nouveau
DDX on a fresh installation, it may be sufficient to do nothing specifically
regarding X drivers. If in fact xserver-xorg-video-nouveau is installed, and
utilized, it is sufficient to purge xserver-xorg-video-nouveau and restart X to
engage the modesetting DIX. The nouveau DDX should work similarly to the
modesetting DIX. Whether one or the other is better for your GeForce 8200M G
[MCP79] would require you do your own comparison testing.

Just a suggestion: a default Debian installation including X includes Gnome, which
seems to be quite demanding of the hardware compared to most other DEs. For users
of older hardware such as yours, I personally suggest just about any other DE be
selected for installation instead. The DE I use with older hardware is not
available directly from Debian repos, but from its developers:
<http://www.trinitydesktop.org/>
<https://wiki.trinitydesktop.org/Debian_Trinity_Repository_Installation_Instructions>

In order to exclude Debian DEs at installation I include the following on the
installation kernel's command line:

tasks=standard base-installer/install-recommends=false

Andrew M.A. Cater

unread,
Apr 19, 2021, 4:50:04 AM4/19/21
to
On Mon, Apr 19, 2021 at 08:15:45AM +0530, Susmita/Rajib wrote:
> On Sun, 18 Apr 2021 17:56:46 +0000, "Andrew M.A. Cater"
> <amac...@einval.com> wrote:
> [QUOTE]
> [...]
> I followed through the screenshots you provided.
> [...]
> You can't ignore the source - you may have to apply it to a kernel.
> [/QUOTE]
>
>
> Okay, learnt. Thank you.
>
Note: You _only_ need this if you are using the proprietary Nvidia driver.

>
> [QUOTE]
> [...]
> You have dependency errors. That's a bad sign.
>
> [...]
> WHY, oh, why are you trying to use Bullseye and kernel 5.10 at this stage?
> [/QUOTE]
>
> I used the example of knoppix. Regarding Bullseye and kernel 5.10,
> that was knoppix.
>
>
OK. Understood. If Knoppix is working, then Debian should too.

>
> [QUOTE]
> [...]
> First things first: you have a laptop which is 64 bit capable, I think.
> You also have a laptop which is capable of using UEFI. Use them.
> Use those options.
> [...]
> [/QUOTE]
>
> 64bit yes. For the problematic laptop, UEFI, no.

I was reading this from the screenshots you posted: that laptop is set to
Legacy [BIOS mode] which suggests that it might also be able to use UEFI.
>
>
> [QUOTE]
> Download a CD/DVD including firmware if that's what it takes -
> First link is CD which may be enough, second is DVD
>
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/firmware-10.9.0-amd64-netinst.iso
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-dvd/firmware-10.9.0-amd64-DVD-1.iso
> [...]
> [/QUOTE]
>
> > Presently, I used the Debian grub to run knoppix, either as iso by
> > loopback loop, or with iso extracted and am presently using knoppix
> > for the HCL Me laptop.

I'm assuming that the HCL Me laptop is the one you want to install on - and
was the one the screenshots relate to. To make it easier, I'm assuming that
you are prepared to wipe the disk, do a clean install and don't need to
retain previous data.

> >
> > Please tell me if there is a possibility of using Debian to use vesa
> > (or fbdev) from grub, although fbdev is deprecated, vesa runs fine.
> > But a little stressful for the motherboard and CPU. Heat up.
> >
> > Best,
> > Rajib
>
>
> [QUOTE]
> Try the above with current Debian 10 and a text mode expert install _first_
> Do NOT install a graphical environment until you can get the laptop working
> in text mode. At that point, you may have to deal with installing nouveau
> or, possibly, the Nvidia proprietary drivers.
>

To make sure that you _only_ have a text mode environment.

When the install gets to the task selection stage - uncheck / de-select
Debian desktop environment. Make sure that all other desktop environments
are not selected. Install only the standard utilities.

if you are using WiFi - before you finish the install drop to a shell
and apt-get install network-manager. This will allow you to use nmcli to
set up and access WiFi thereafter.

Once the install is complete, reboot. You should, at that stage, just have
text mode. At that point, you can do one of two things:

For the free drivers:

Run tasksel and select a desktop environment. I might suggest Mate as being
slightly less resource hungry than GNOME - your choice.

For Nvidia

Do NOT tasksel and install any desktop until you've got the essentials you
need and have built/installed the appropriate Nvidia binaries.

Andrew M.A. Cater

unread,
Apr 19, 2021, 4:50:04 AM4/19/21
to
Hi Rajib,

Under NO ACCOUNT do this. Mixing LFS instructions and Debian is a recipe
for a disaster. As Felix Miata has said elsewhere: either the Nouveau
drivers or, exceptionally, Nvidia drivers built the Debian way should
work for you.

All the best,

Andy C.

Andrew M.A. Cater

unread,
Apr 19, 2021, 5:30:05 AM4/19/21
to
On Mon, Apr 19, 2021 at 10:00:59AM +0530, Susmita/Rajib wrote:
> On Mon, 19 Apr 2021 00:12:29 -0400, Felix Miata <mrm...@earthlink.net> wrote:
> Ref: https://lists.debian.org/debian-user/2021/04/msg00530.html
>
> "...
> Unless and until all traces of NVidia's driver installation and associated
> configuration changes have been purged from your machine, I can be no
> help except
> WRT eradicating them. Even in that regard others know better than me how to
> proceed. AFAICT, whatever NVidia driver installation does eliminates
> any chance to
> make FOSS drivers work acceptably.
> ..."
>
> Okay, in any case I am to reinstall fresh and latest stable Debian, as
> advised by Dr./Mr. Cater.

Mr. Cater - but Andy / Andrew is more normal for me and I'm fine with
that :)

If you are doing a complete fresh install and want to use Nouveau - just
go through the install using the firmware CD/DVD image. The worst that
can happen is that it really doesn't work, at which point you need to try
a text install as outlined in an answer to your previous message.

If you can install using a wired Ethernet connection to start with, always
do so, in my opinion, as it makes it easier to know that you have a reliable
connection. If you can't -that's why using the firmware DVD is advised.

>
> So in nutshell, may please the steps be described? The idea involved?
>
> It is requested that a copy of email be sent to my Gmailbox please.
>
> Best.
> Rajib
>

On Debian lists, we would normally reply to the list first - so other people
get to see the answers - see the FAQ posted once a month here - but as
you've asked specifically, I'll do that for you.

All the very best, as ever,

Andy Cater
0 new messages