Re: 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?
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.
>
>
> 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...
>
YOu have dependency errors. That's a bad sign.
> ------------------------------
> 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
>
> >
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.
>
Reply to: