Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #233354 > unrolled thread

Debian Stable Updates Announcement SUA 197-1

Started byKeith Wyatt <kilowattradio@att.net>
First post2021-03-23 01:10 +0100
Last post2021-03-23 18:00 +0100
Articles 14 — 7 participants

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Debian Stable Updates Announcement SUA 197-1 Keith Wyatt <kilowattradio@att.net> - 2021-03-23 01:10 +0100
    Re: Debian Stable Updates Announcement SUA 197-1 David Christensen <dpchrist@holgerdanske.com> - 2021-03-23 01:30 +0100
      Re: Debian Stable Updates Announcement SUA 197-1 David Wright <deblis@lionunicorn.co.uk> - 2021-03-23 04:40 +0100
        Re: Debian Stable Updates Announcement SUA 197-1 Greg Wooledge <greg@wooledge.org> - 2021-03-23 12:50 +0100
          Re: Debian Stable Updates Announcement SUA 197-1 The Wanderer <wanderer@fastmail.fm> - 2021-03-23 13:00 +0100
            Re: Debian Stable Updates Announcement SUA 197-1 Andrei POPESCU <andreimpopescu@gmail.com> - 2021-03-23 16:10 +0100
            Re: Debian Stable Updates Announcement SUA 197-1 David Wright <deblis@lionunicorn.co.uk> - 2021-03-23 17:50 +0100
              Re: Debian Stable Updates Announcement SUA 197-1 David Christensen <dpchrist@holgerdanske.com> - 2021-03-23 18:50 +0100
                Re: Debian Stable Updates Announcement SUA 197-1 "Andrew M.A. Cater" <amacater@einval.com> - 2021-03-23 20:40 +0100
                  Re: Debian Stable Updates Announcement SUA 197-1 David Christensen <dpchrist@holgerdanske.com> - 2021-03-24 00:10 +0100
                    Re: Debian Stable Updates Announcement SUA 197-1 "Andrew M.A. Cater" <amacater@einval.com> - 2021-03-24 15:10 +0100
          Re: Debian Stable Updates Announcement SUA 197-1 David Christensen <dpchrist@holgerdanske.com> - 2021-03-23 17:40 +0100
        Re: Debian Stable Updates Announcement SUA 197-1 David Christensen <dpchrist@holgerdanske.com> - 2021-03-23 17:40 +0100
          Re: Debian Stable Updates Announcement SUA 197-1 David Wright <deblis@lionunicorn.co.uk> - 2021-03-23 18:00 +0100

#233354 — Debian Stable Updates Announcement SUA 197-1

FromKeith Wyatt <kilowattradio@att.net>
Date2021-03-23 01:10 +0100
SubjectDebian Stable Updates Announcement SUA 197-1
Message-ID<BVCMp-1eu-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

----------------------------------------------------------------------------
Debian Stable Updates Announcement SUA 197-1         https://www.debian.org/
debian-release@lists.debian.org                              Adam D. Barratt
March 22nd, 2021
----------------------------------------------------------------------------

Upcoming Debian 10 Update (10.9)

An update to Debian 10 is scheduled for Saturday, March 27th, 2021. As o
now it will include the following bug fixes. They can be found in "buster-
proposed-updates", which is carried by all official mirrors.

Please note that packages published through security.debian.org are not
listed, but will be included if possible. Some of the updates below are also
already available through "buster-updates".

Testing and feedback would be appreciated. Bugs should be filed in the
Debian Bug Tracking System, but please make the Release Team aware of them
by copying "debian-release@lists.debian.org" on your mails.

The point release will also include a rebuild of debian-installer.


Miscellaneous Bugfixes
----------------------

This stable update adds a few important corrections to the following
packages:

  Package                    Reason
  -------                    ------

  avahi                      Remove avahi-daemon-check-dns mechanism, no
                             longer needed

  base-files                 Update /etc/debian_version for the 10.9 point
                             release

  cloud-init                 Avoid logging generated passwords to world-
                             readable log files [CVE-2021-3429]

  debian-archive-keyring     Add bullseye keys; retire jessie keys

  debian-installer           Use 4.19.0-16 Linux kernel ABI

  exim4                      Fix use of concurrent TLS connections under
                             GnuTLS; fix TLS certificate verification with
                             CNAMEs; README.Debian: document the
                             limitation/extent of server certificate
                             verification in the default configuration

  fetchmail                  No longer report "System error during
                             SSL_connect(): Success"; remove OpenSSL version
                             check

  fwupd                      Add SBAT support

  fwupdate                   Add SBAT support

  gdnsd                      Fix stack overflow with overly-large IPv6
                             addresses [CVE-2019-13952]

  groff                      Rebuild against ghostscript 9.27

  hwloc-contrib              Enable support for ppc64el

  intel-microcode            Update various microcode

  iputils                    Fix ping rounding errors; fix tracepath target
                             corruption

  jquery                     Fix untrusted code execution vulnerabilities
                             [CVE-2020-11022 CVE-2020-11023]

  libbsd                     Fix out-of-bounds read issue [CVE-2019-20367]

  libpano13                  Fix format string vulnerability

  libreoffice                Do not load encodings.py from current directoy

  linux                      New upstream stable release; bump ABI to -16;
                             rotate secure boot signing keys

  linux-latest               Update to -16 kernel ABI

  lirc                       Normalize embedded ${DEB_HOST_MULTIARCH} value
                             in /etc/lirc/lirc_options.conf to find
                             unmodified configuration files on all
                             architectures; recommend gir1.2-vte-2.91
                             instead of non-existant gir1.2-vte

  m2crypto                   Fix test failure with recent OpenSSL

  openafs                    Fix outgoing connections after unix epoch time
                             0x60000000 (14 January 2021)

  portaudio19                Handle EPIPE from
                             alsa_snd_pcm_poll_descriptors, fixing crash

  postgresql-11              New upstream stable release; fix information
                             leakage in constraint-violation error messages
                             [CVE-2021-3393]; fix CREATE INDEX CONCURRENTLY
                             to wait for concurrent prepared transactions

  privoxy                    Security issues [CVE-2020-35502 CVE-2021-20209
                             CVE-2021-20210 CVE-2021-20211 CVE-2021-20212
                             CVE-2021-20213 CVE-2021-20214 CVE-2021-20215
                             CVE-2021-20216 CVE-2021-20217 CVE-2021-20272
                             CVE-2021-20273 CVE-2021-20275 CVE-2021-20276]

  python3.7                  Fix CRLF injection in http.client
                             [CVE-2020-26116]; fix buffer overflow in
                             PyCArg_repr in _ctypes/callproc.c
                             [CVE-2021-3177]

  redis                      Fix a series of integer overflow issues on
                             32-bit systems [CVE-2021-21309]

  ruby-mechanize             Fix command injection issue [CVE-2021-21289]

  systemd                    core: make sure to restore the control command
                             id, too, fixing a segfault; seccomp: allow
                             turning off of seccomp filtering via an
                             environment variable

  uim                        libuim-data: Perform symlink_to_dir conversion
                             of /usr/share/doc/libuim-data in the
                             resurrected package for clean upgrades from
                             stretch

  xcftools                   Fix integer overflow vulnerability
                             [CVE-2019-5086 CVE-2019-5087]

  xterm                      Correct upper-limit for selection buffer,
                             accounting for combining characters
                             [CVE-2021-27135]


A complete list of all accepted and rejected packages together with
rationale is on the preparation page for this revision:

  <https://release.debian.org/proposed-updates/stable.html>


If you encounter any issues, please don't hesitate to get in touch with the
Debian Release Team at "debian-release@lists.debian.org".

[toc] | [next] | [standalone]

#233355

FromDavid Christensen <dpchrist@holgerdanske.com>
Date2021-03-23 01:30 +0100
Message-ID<BVD5L-1kJ-3@gated-at.bofh.it>
In reply to#233354
On 3/22/21 5:03 PM, Keith Wyatt wrote:

> As o
> now it will include the following bug fixes. They can be found in "buster-
> proposed-updates", which is carried by all official mirrors.


Please provide a URL.


David

[toc] | [prev] | [next] | [standalone]

#233362

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2021-03-23 04:40 +0100
Message-ID<BVG3E-38N-1@gated-at.bofh.it>
In reply to#233355
On Mon 22 Mar 2021 at 17:26:14 (-0700), David Christensen wrote:
> On 3/22/21 5:03 PM, Keith Wyatt wrote:
> 
> > As o[f]
> > now it will include the following bug fixes. They can be found in "buster-
> > proposed-updates", which is carried by all official mirrors.
> 
> Please provide a URL.

Do you mean for the .deb files themselves. AIUI they're in the
pool with all the rest. As for the changes files, they're in

http://XXXXXXXXXXXXXXXXXX/debian/dists/buster-proposed-updates/

where XXXXXXXXXXXXXXXXXX is whatever you put in /etc/apt/sources.list
as your local mirror.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#233380

FromGreg Wooledge <greg@wooledge.org>
Date2021-03-23 12:50 +0100
Message-ID<BVNHQ-7YQ-5@gated-at.bofh.it>
In reply to#233362
On Mon, Mar 22, 2021 at 10:34:12PM -0500, David Wright wrote:
> On Mon 22 Mar 2021 at 17:26:14 (-0700), David Christensen wrote:
> > On 3/22/21 5:03 PM, Keith Wyatt wrote:
> > 
> > > As o[f]
> > > now it will include the following bug fixes. They can be found in "buster-
> > > proposed-updates", which is carried by all official mirrors.
> > 
> > Please provide a URL.
> 
> Do you mean for the .deb files themselves. AIUI they're in the
> pool with all the rest. As for the changes files, they're in
> 
> http://XXXXXXXXXXXXXXXXXX/debian/dists/buster-proposed-updates/
> 
> where XXXXXXXXXXXXXXXXXX is whatever you put in /etc/apt/sources.list
> as your local mirror.

I think the request was really "Please tell us how to use this
buster-proposed-updates thing, which I've never heard of before."

Here's a wiki page: <https://wiki.debian.org/StableProposedUpdates>
However, I would not follow its advice literally.  You *never* want
to put the word "stable" in your sources.list.  You want to put the
actual name of a release instead.

So, wherever the wiki says to use stable-proposed-updates, please use
buster-proposed-updates instead.

[toc] | [prev] | [next] | [standalone]

#233381

FromThe Wanderer <wanderer@fastmail.fm>
Date2021-03-23 13:00 +0100
Message-ID<BVNRv-821-5@gated-at.bofh.it>
In reply to#233380

[Multipart message — attachments visible in raw view] — view raw

On 2021-03-23 at 07:43, Greg Wooledge wrote:

> I think the request was really "Please tell us how to use this
> buster-proposed-updates thing, which I've never heard of before."
> 
> Here's a wiki page: <https://wiki.debian.org/StableProposedUpdates>
> However, I would not follow its advice literally.  You *never* want
> to put the word "stable" in your sources.list.  You want to put the
> actual name of a release instead.

That depends on what your update patterns are. It's probably generally
good advice, but it's certainly not universal.

For myself, I have stable and testing in my sources.liist, and usually
update at least weekly if not daily. This is effectively updating
against testing, but keeps packages in stable which have been removed
from testing available to be installed if I want them.

When testing is released as stable and a new testing becomes available,
I lose access to the packages which were previously in stable (now
oldstable), which are old enough that it's probably not reasonable to
want to install them without specifically knowing that that's what
you're doing; I retain access to the packages previously in testing
(because they're now in stable, which is already in my sources.list); I
gain access to the new testing, to continue the pattern; and I do it all
without having to update sources.list for the purpose.

I don't see how that's unsafe or unreasonable; certainly I've been doing
it for years, I believe for over a decade, without encountering issues
which I think could even potentially be traced to it.

> So, wherever the wiki says to use stable-proposed-updates, please
> use buster-proposed-updates instead.

This is generally reasonable, however. My update pattern is unlikely to
be typical, and might be considered a special use-case.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#233385

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2021-03-23 16:10 +0100
Message-ID<BVQPo-1yl-1@gated-at.bofh.it>
In reply to#233381

[Multipart message — attachments visible in raw view] — view raw

On Ma, 23 mar 21, 07:52:52, The Wanderer wrote:
> On 2021-03-23 at 07:43, Greg Wooledge wrote:
> 
> > I think the request was really "Please tell us how to use this
> > buster-proposed-updates thing, which I've never heard of before."
> > 
> > Here's a wiki page: <https://wiki.debian.org/StableProposedUpdates>
> > However, I would not follow its advice literally.  You *never* want
> > to put the word "stable" in your sources.list.  You want to put the
> > actual name of a release instead.
> 
> That depends on what your update patterns are. It's probably generally
> good advice, but it's certainly not universal.

Agreed. I seem to remember some postings from users that had 'stable' on 
purpose in their sources.list.
 
> > So, wherever the wiki says to use stable-proposed-updates, please
> > use buster-proposed-updates instead.
> 
> This is generally reasonable, however. My update pattern is unlikely to
> be typical, and might be considered a special use-case.

Also, those who do have 'stable' in their APT package sources will know 
to use 'stable' for -updates and -proposed-updates as well, so the wiki 
should probably be changed.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#233391

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2021-03-23 17:50 +0100
Message-ID<BVSo9-2j3-1@gated-at.bofh.it>
In reply to#233381
On Tue 23 Mar 2021 at 07:52:52 (-0400), The Wanderer wrote:
> On 2021-03-23 at 07:43, Greg Wooledge wrote:
> 
> > I think the request was really "Please tell us how to use this
> > buster-proposed-updates thing, which I've never heard of before."

Actually I thought David wanted to do what I did, which is *not* to add
buster-proposed-updates to his sources.list, but just to poke around.
With good reason: ISTR that David runs his farm of machines on stretch.

I didn't think anyone would miss the pattern in sources.list's buster,
buster-updates, buster-proposed-updates.

However, I was unprepared for David's response today, of going back
to square one.

> > Here's a wiki page: <https://wiki.debian.org/StableProposedUpdates>
> > However, I would not follow its advice literally.  You *never* want
> > to put the word "stable" in your sources.list.  You want to put the
> > actual name of a release instead.
> 
> That depends on what your update patterns are. It's probably generally
> good advice, but it's certainly not universal.

Agreed, it's not universal practice, but it might be worth having
as a default for advice.

> For myself, I have stable and testing in my sources.liist, and usually
> update at least weekly if not daily. This is effectively updating
> against testing, but keeps packages in stable which have been removed
> from testing available to be installed if I want them.
> 
> When testing is released as stable and a new testing becomes available,
> I lose access to the packages which were previously in stable (now
> oldstable), which are old enough that it's probably not reasonable to
> want to install them without specifically knowing that that's what
> you're doing; I retain access to the packages previously in testing
> (because they're now in stable, which is already in my sources.list); I
> gain access to the new testing, to continue the pattern; and I do it all
> without having to update sources.list for the purpose.
> 
> I don't see how that's unsafe or unreasonable; certainly I've been doing
> it for years, I believe for over a decade, without encountering issues
> which I think could even potentially be traced to it.
> 
> > So, wherever the wiki says to use stable-proposed-updates, please
> > use buster-proposed-updates instead.
> 
> This is generally reasonable, however. My update pattern is unlikely to
> be typical, and might be considered a special use-case.

To be fair, once you've added testing, then you're in the category of
a rolling-update Debian distribution, which is not the same as the
target of that webpage, a rolling-update Debian Stable distribution.

The problem that putting "stable" into sources.list causes is, of
course, the shock of Release Day to people who might be quite
unprepared for it. It's difficult to envisage that you're unprepared
for the effect of that day on testing.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#233394

FromDavid Christensen <dpchrist@holgerdanske.com>
Date2021-03-23 18:50 +0100
Message-ID<BVTke-2YC-3@gated-at.bofh.it>
In reply to#233391
On 3/23/21 9:44 AM, David Wright wrote:
> On Tue 23 Mar 2021 at 07:52:52 (-0400), The Wanderer wrote:
>> On 2021-03-23 at 07:43, Greg Wooledge wrote:
>>
>>> I think the request was really "Please tell us how to use this
>>> buster-proposed-updates thing, which I've never heard of before."
> 
> Actually I thought David wanted to do what I did, which is *not* to add
> buster-proposed-updates to his sources.list, but just to poke around.

I was curious about the opportunity to evaluate point upgrades prior to 
release.


> With good reason: 
> ISTR that David runs his farm of machines on stretch.

I use Stretch for my daily driver laptop (Dell Latitude E6520) and UniFi 
Controller VPS.  I also have a Stretch USB flash drive instance for 
maintenance.  I use FreeBSD for my servers.  I need to migrate the daily 
driver to Buster, but Buster does not like the Optimus graphics in the 
E6520.  So, the plan is to sell the E6520, get a newer laptop with Intel 
graphics alone, put Buster on that, and migrate.  Migrating the VPS will 
likely involve backing up the existing instance, creating or leasing a 
new UniFi Controller instance, restoring onto the new instance, and then 
switching DNS.  Creating a Buster USB flash drive instance should be easy.


> I didn't think anyone would miss the pattern in sources.list's buster,
> buster-updates, buster-proposed-updates.

I have seen "buster" and "buster-updates" (and prior equivalents), but 
never "buster-proposed-updates".


> However, I was unprepared for David's response today, of going back
> to square one.

A fresh install of the current Stable point release would be the 
canonical starting point for testing proposed Stable point release 
updates.  This is an ideal use-case for virtualization.


David

[toc] | [prev] | [next] | [standalone]

#233397

From"Andrew M.A. Cater" <amacater@einval.com>
Date2021-03-23 20:40 +0100
Message-ID<BVV2G-468-7@gated-at.bofh.it>
In reply to#233394
On Tue, Mar 23, 2021 at 10:40:01AM -0700, David Christensen wrote:
> On 3/23/21 9:44 AM, David Wright wrote:
> > On Tue 23 Mar 2021 at 07:52:52 (-0400), The Wanderer wrote:
> > > On 2021-03-23 at 07:43, Greg Wooledge wrote:
> > > 
> > > > I think the request was really "Please tell us how to use this
> > > > buster-proposed-updates thing, which I've never heard of before."
> > 
> > Actually I thought David wanted to do what I did, which is *not* to add
> > buster-proposed-updates to his sources.list, but just to poke around.
> 
> I was curious about the opportunity to evaluate point upgrades prior to
> release.
> 
> 
> > With good reason: ISTR that David runs his farm of machines on stretch.
> 
> I use Stretch for my daily driver laptop (Dell Latitude E6520) and UniFi
> Controller VPS.  I also have a Stretch USB flash drive instance for
> maintenance.  I use FreeBSD for my servers.  I need to migrate the daily
> driver to Buster, but Buster does not like the Optimus graphics in the
> E6520.  So, the plan is to sell the E6520, get a newer laptop with Intel
> graphics alone, put Buster on that, and migrate.  Migrating the VPS will
> likely involve backing up the existing instance, creating or leasing a new
> UniFi Controller instance, restoring onto the new instance, and then
> switching DNS.  Creating a Buster USB flash drive instance should be easy.
> 
Have you tried installing the optimus under Buster - it's not as 
straightforward as the standard install but there's a couple of steps
that will make it work. The main trick is to make sure that nvidia drivers
are never loaded until the point at which you've got everythng else 
configured.


> 
> > I didn't think anyone would miss the pattern in sources.list's buster,
> > buster-updates, buster-proposed-updates.
> 
> I have seen "buster" and "buster-updates" (and prior equivalents), but never
> "buster-proposed-updates".
> 
> 
> > However, I was unprepared for David's response today, of going back
> > to square one.
> 
> A fresh install of the current Stable point release would be the canonical
> starting point for testing proposed Stable point release updates.  This is
> an ideal use-case for virtualization.
> 
> 
> David
>

[toc] | [prev] | [next] | [standalone]

#233403

FromDavid Christensen <dpchrist@holgerdanske.com>
Date2021-03-24 00:10 +0100
Message-ID<BVYjT-6d4-1@gated-at.bofh.it>
In reply to#233397
On 3/23/21 12:31 PM, Andrew M.A. Cater wrote:
> On Tue, Mar 23, 2021 at 10:40:01AM -0700, David Christensen wrote:

>> I use Stretch for my daily driver laptop (Dell Latitude E6520) and UniFi
>> Controller VPS.  ...
>> I need to migrate the daily
>> driver to Buster, but Buster does not like the Optimus graphics in the
>> E6520.

> Have you tried installing the optimus under Buster 

Looking in my notes, it looks like I tried installing 
nvidia-legacy-390xx-driver in January.  I do not see any URL for 
instructions.  The Debian wiki page for Optimus does not look familiar:

    https://wiki.debian.org/NVIDIA%20Optimus


In any case, my fumbling around only made things worse.  So, I wiped the 
SSD and did a fresh install KISS OOTB:

     Insert debian-10.8.0-amd64-xfce-CD-1 USB flash drive.

	Debian GNU/Linux installer boot menu (BIOS mode)
						Install
	Language				C
	Continent or Region			North America
	Country, territory or area		United States
	Keymap to use				American English

     Pop-up dialog:

	Detect network hardware

	Some of your hardware needs non-free firmware files to operate.
	The firwmare can be loaded from removable media, such as a USB
	stick or floppy.

	The missing firmware files are: iwlwifi-60000g2a-6.ucode
	iwlwifi-60000g2a-5.ucode

	If you have such media available now, insert it, and continue.

	Load missing fimrware from removable media?

     Insert USB flash drive "usb64a" with "firmware" subdirectory
     containing Debian 10.8.0 firmware.  Choose "Yes".

     Continue with install:

	Primary network interface		enp0s25
	Hostname				dipsy
	Domain name				tracy.holgerdanske.com
	Root password				*******
	Full name for the new user		debian
	Username for your account		debian
	Choose a password for the new user	********
	Select your time zone			Pacific
	Partitioning method			manual
	    Encrypted volume (sda2_crypt) - 1.0 GB Linux device-mapper (crypt)
		 #1             1.0 GB     f  swap          swap
	    Encrypted volume (sda3_crypt) - 13.0 GB Linux device-mapper (crypt)
		 #1            13.0 GB     f  ext4          /
	    SCSI5 (0,0,0) (sda) - 60.0 GB ATA INTEL SSDSC2CW06
		 #1  primary  999.3 MB  B  F  ext4          /boot
		 #2  primary    1.0 GB     K  crypto       (sda2_crypt)
		 #3  primary   13.0 GB     K  crypto       (sda3_crypt)
			       45.0 GB        FREESPACE
	Finish partitioning and write changes to disk
	Use a network mirror			Yes
	Mirror country				United States
	Archive mirror				deb.debian.org
	HTTP proxy				<blank>
	Participate in the package usage survey	No
	Choose software to install
	    Debian desktop environment
		Xfce
	    print server
	    SSH server
	    standard system utilities
	Install the GRUB boot loader to th emaster boot record
						Yes
	Device for boot loader installation	/dev/sda 
(ata-INTEL_SSDSC2SW060A3_***redacted***)
	Installation complete			Continue

	Power down at POST.

	Remove installation media and firmware USB flash drive.


The bug is back -- the desktop crashes within an hour when playing 
YouTube videos -- and the Dell Latitude E6520 laptop is on Craig's List. 
  So far, one scammer and two low-ballers.


> - it's not as
> straightforward as the standard install but there's a couple of steps
> that will make it work. The main trick is to make sure that nvidia drivers
> are never loaded until the point at which you've got everythng else
> configured.


If you have a URL with detailed instructions of how to install Buster on 
a laptop with Optimus, you have a laptop with Optimus, you followed the 
instructions, and the laptop can play YouTube videos for 24 hours 
without crashing, please post the URL.


David

[toc] | [prev] | [next] | [standalone]

#233421

From"Andrew M.A. Cater" <amacater@einval.com>
Date2021-03-24 15:10 +0100
Message-ID<BWcmR-6S8-1@gated-at.bofh.it>
In reply to#233403
On Tue, Mar 23, 2021 at 04:04:29PM -0700, David Christensen wrote:
> On 3/23/21 12:31 PM, Andrew M.A. Cater wrote:
> > On Tue, Mar 23, 2021 at 10:40:01AM -0700, David Christensen wrote:
> 
> > > I use Stretch for my daily driver laptop (Dell Latitude E6520) and UniFi
> > > Controller VPS.  ...
> > > I need to migrate the daily
> > > driver to Buster, but Buster does not like the Optimus graphics in the
> > > E6520.
> 
> > Have you tried installing the optimus under Buster
> 
> Looking in my notes, it looks like I tried installing
> nvidia-legacy-390xx-driver in January.  I do not see any URL for
> instructions.  The Debian wiki page for Optimus does not look familiar:
> 
>    https://wiki.debian.org/NVIDIA%20Optimus
> 
> 
> In any case, my fumbling around only made things worse.  So, I wiped the SSD
> and did a fresh install KISS OOTB:
> 
>     Insert debian-10.8.0-amd64-xfce-CD-1 USB flash drive.
> 
> 	Debian GNU/Linux installer boot menu (BIOS mode)
> 						Install
> 	Language				C
> 	Continent or Region			North America
> 	Country, territory or area		United States
> 	Keymap to use				American English
> 
>     Pop-up dialog:
> 
> 	Detect network hardware
> 
> 	Some of your hardware needs non-free firmware files to operate.
> 	The firwmare can be loaded from removable media, such as a USB
> 	stick or floppy.
> 
> 	The missing firmware files are: iwlwifi-60000g2a-6.ucode
> 	iwlwifi-60000g2a-5.ucode
> 
> 	If you have such media available now, insert it, and continue.
> 
> 	Load missing fimrware from removable media?
> 
>     Insert USB flash drive "usb64a" with "firmware" subdirectory
>     containing Debian 10.8.0 firmware.  Choose "Yes".
> 
>     Continue with install:
> 
> 	Primary network interface		enp0s25
> 	Hostname				dipsy
> 	Domain name				tracy.holgerdanske.com
> 	Root password				*******
> 	Full name for the new user		debian
> 	Username for your account		debian
> 	Choose a password for the new user	********
> 	Select your time zone			Pacific
> 	Partitioning method			manual
> 	    Encrypted volume (sda2_crypt) - 1.0 GB Linux device-mapper (crypt)
> 		 #1             1.0 GB     f  swap          swap
> 	    Encrypted volume (sda3_crypt) - 13.0 GB Linux device-mapper (crypt)
> 		 #1            13.0 GB     f  ext4          /
> 	    SCSI5 (0,0,0) (sda) - 60.0 GB ATA INTEL SSDSC2CW06
> 		 #1  primary  999.3 MB  B  F  ext4          /boot
> 		 #2  primary    1.0 GB     K  crypto       (sda2_crypt)
> 		 #3  primary   13.0 GB     K  crypto       (sda3_crypt)
> 			       45.0 GB        FREESPACE
> 	Finish partitioning and write changes to disk
> 	Use a network mirror			Yes
> 	Mirror country				United States
> 	Archive mirror				deb.debian.org
> 	HTTP proxy				<blank>
> 	Participate in the package usage survey	No
> 	Choose software to install
> 	    Debian desktop environment
> 		Xfce
> 	    print server
> 	    SSH server
> 	    standard system utilities
> 	Install the GRUB boot loader to th emaster boot record
> 						Yes
> 	Device for boot loader installation	/dev/sda
> (ata-INTEL_SSDSC2SW060A3_***redacted***)
> 	Installation complete			Continue
> 
> 	Power down at POST.
> 
> 	Remove installation media and firmware USB flash drive.
> 
> 
> The bug is back -- the desktop crashes within an hour when playing YouTube
> videos -- and the Dell Latitude E6520 laptop is on Craig's List.  So far,
> one scammer and two low-ballers.
> 
> 
> > - it's not as
> > straightforward as the standard install but there's a couple of steps
> > that will make it work. The main trick is to make sure that nvidia drivers
> > are never loaded until the point at which you've got everythng else
> > configured.
> 
> 
> If you have a URL with detailed instructions of how to install Buster on a
> laptop with Optimus, you have a laptop with Optimus, you followed the
> instructions, and the laptop can play YouTube videos for 24 hours without
> crashing, please post the URL.
> 
> 
> David
> 

OK - the trick is that for this to work out of the box, in my experience: 
you must NOT install any Nvidia drivers of any description or a desktop 
environment until after the prerequisites are in place - otherwise you end
up with instability. On the laptop I was using, the only way to get this
was to use bumblebee https://wiki.debian.org/Bumblebee. The strategy outlined
below will probably also work if you start with the Optimus page you listed
above.

1. Boot the CD/DVD - if you need WiFi firmware to continue with the 
installation, use the unofficial installer including firmware 
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
My wifi preference is to use network manager - nmcli works well enough.

2. Select expert install, text mode. Work through the installer until you
get to the task selection step. Uncheck any desktop environment.

3. Continue to reboot stage. Boot to the new, minimal, text-only install.

4. At that point, install the prerequisites for bumblebee using apt-get/
aptitude.

5. Reboot - you should still be in text only mode. At that point, use tasksel
to install a desktop environment - which will find the underlying drivers to
make best use of your Optimus.

6. In my (limited) experience: if you install the free nouveau driver from the 
start, or just install a desktop which will pull it in, you may get 
instability or things just not working. 

7. If you have once installed nouveau,it is then extremely hard to get the 
Nvidia proprietary drivers to install correctly - purging nouveau and then 
trying to install proprietary drivers at that point is almost impossible. 

The only winning strategy is not to play: at least not to install anything 
graphical until the prerequisites are in place hence the strict instructions
for text mode throughout.

Finding this out was incredibly frustrating and took me the best part of three 
days and several re-installs to track down. I promptly forgot it all and had 
to relearn a year or so later.

All the very best,

Andy Cater

[toc] | [prev] | [next] | [standalone]

#233388

FromDavid Christensen <dpchrist@holgerdanske.com>
Date2021-03-23 17:40 +0100
Message-ID<BVSet-2fO-3@gated-at.bofh.it>
In reply to#233380
On 3/23/21 4:43 AM, Greg Wooledge wrote:
> On Mon, Mar 22, 2021 at 10:34:12PM -0500, David Wright wrote:
>> On Mon 22 Mar 2021 at 17:26:14 (-0700), David Christensen wrote:
>>> On 3/22/21 5:03 PM, Keith Wyatt wrote:
>>>
>>>> As o[f]
>>>> now it will include the following bug fixes. They can be found in "buster-
>>>> proposed-updates", which is carried by all official mirrors.
>>>
>>> Please provide a URL.
>>
>> Do you mean for the .deb files themselves. AIUI they're in the
>> pool with all the rest. As for the changes files, they're in
>>
>> http://XXXXXXXXXXXXXXXXXX/debian/dists/buster-proposed-updates/
>>
>> where XXXXXXXXXXXXXXXXXX is whatever you put in /etc/apt/sources.list
>> as your local mirror.
> 
> I think the request was really "Please tell us how to use this
> buster-proposed-updates thing, which I've never heard of before."
> 
> Here's a wiki page: <https://wiki.debian.org/StableProposedUpdates>
> However, I would not follow its advice literally.  You *never* want
> to put the word "stable" in your sources.list.  You want to put the
> actual name of a release instead.
> 
> So, wherever the wiki says to use stable-proposed-updates, please use
> buster-proposed-updates instead.


Thank you for understanding practicality.  :-)


David

[toc] | [prev] | [next] | [standalone]

#233389

FromDavid Christensen <dpchrist@holgerdanske.com>
Date2021-03-23 17:40 +0100
Message-ID<BVSet-2fO-1@gated-at.bofh.it>
In reply to#233362
On 3/22/21 8:34 PM, David Wright wrote:
> On Mon 22 Mar 2021 at 17:26:14 (-0700), David Christensen wrote:
>> On 3/22/21 5:03 PM, Keith Wyatt wrote:
>>
>>> As o[f]
>>> now it will include the following bug fixes. They can be found in "buster-
>>> proposed-updates", which is carried by all official mirrors.
>>
>> Please provide a URL.
> 
> Do you mean for the .deb files themselves. AIUI they're in the
> pool with all the rest. As for the changes files, they're in
> 
> http://XXXXXXXXXXXXXXXXXX/debian/dists/buster-proposed-updates/
> 
> where XXXXXXXXXXXXXXXXXX is whatever you put in /etc/apt/sources.list
> as your local mirror.


Thank you for the response.


Browsing:

     http://ftp.us.debian.org/debian/dists/buster-proposed-updates/


Yes, I do see many *.changes files (one for each package and 
architecture combination).


But, that does not tell me how to *use* the information presented -- 
e.g. that proposed Debian Stable updates are available (for testing).


Assuming that I start with a fresh install of:

     debian-10.8.0-amd64-xfce-CD-1.iso


How do I download and/or install the proposed updates?


That is the URL I need.


David

[toc] | [prev] | [next] | [standalone]

#233392

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2021-03-23 18:00 +0100
Message-ID<BVSxP-2mi-1@gated-at.bofh.it>
In reply to#233389
On Tue 23 Mar 2021 at 09:31:52 (-0700), David Christensen wrote:
> On 3/22/21 8:34 PM, David Wright wrote:
> > On Mon 22 Mar 2021 at 17:26:14 (-0700), David Christensen wrote:
> > > On 3/22/21 5:03 PM, Keith Wyatt wrote:
> > > 
> > > > As o[f]
> > > > now it will include the following bug fixes. They can be found in "buster-
> > > > proposed-updates", which is carried by all official mirrors.
> > > 
> > > Please provide a URL.
> > 
> > Do you mean for the .deb files themselves. AIUI they're in the
> > pool with all the rest. As for the changes files, they're in
> > 
> > http://XXXXXXXXXXXXXXXXXX/debian/dists/buster-proposed-updates/
> > 
> > where XXXXXXXXXXXXXXXXXX is whatever you put in /etc/apt/sources.list
> > as your local mirror.
> 
> Thank you for the response.
> 
> Browsing:
> 
>     http://ftp.us.debian.org/debian/dists/buster-proposed-updates/
> 
> Yes, I do see many *.changes files (one for each package and
> architecture combination).
> 
> But, that does not tell me how to *use* the information presented --
> e.g. that proposed Debian Stable updates are available (for testing).

I would say "for trying out"; "testing" is rather ambiguous in this context.

> Assuming that I start with a fresh install of:
> 
>     debian-10.8.0-amd64-xfce-CD-1.iso
> 
> How do I download and/or install the proposed updates?
> 
> That is the URL I need.

It's not a URL, but just another line in sources.list.

But I myself prefer to just download .debs automatically with the
usual three lines:

deb http://deb.debian.org/debian/ buster main non-free contrib
deb http://security.debian.org/debian-security buster/updates main contrib non-free
deb http://deb.debian.org/debian/ buster-updates main contrib non-free

… and a cron job, then peruse and install them; and I treat
point releases in just the same way.

Cheers,
David.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web