date:20210224


On Tue, 23 Feb 2021, Dan Ritter wrote:


Could be an option. What do you need pulseaudio for that
isn't handled by alsa, jack and/or apulse?


it's needed to have sound on youtube.
I tried your other suggestions a long time ago, and could not make them to work.
I'll try again today

best regards,
--
Pierre Frenkiel

Re: [BUG REPORT] luajit-2.1.0-beta3/jit/bcsave.lua:240: cannot convert 'nil' to 'unsigned short'

2021-02-24 Thread YunQiang Su

Ohh, this packages hasn't been update for so long.
If no objection, I will upload the current git snapshot.

Tiezhu Yang  于2021年2月24日周三 上午11:15写道：
>
> (1) Background
> Source: luajit
> Version: luajit_2.1.0~beta3+dfsg-5.3_mips64el.deb
> Severity: important
> Link: https://packages.debian.org/sid/luajit
>
> (2) Description of problem
> When I build bcc, there exists the following build error:
> [ 34%] Generating bcc.o
> /usr/bin/luajit: /usr/share/luajit-2.1.0-beta3/jit/bcsave.lua:240: cannot 
> convert 'nil' to 'unsigned short'
> [ 35%] Linking C executable bcc-lua
> cc: error: bcc.o: No such file or directory
>
> (3) Steps to Reproduce
> # According to https://packages.debian.org/source/sid/bpfcc,
> # BCC build dependencies:
> sudo apt-get install arping bison clang-format cmake dh-python \
>dpkg-dev pkg-kde-tools ethtool flex inetutils-ping iperf \
>libbpf-dev libclang-dev libclang-cpp-dev libedit-dev libelf-dev \
>libfl-dev libzip-dev linux-libc-dev llvm-dev libluajit-5.1-dev \
>luajit python3-netaddr python3-pyroute2 python3-distutils python3
> # In oreder to avoid "/bin/sh: 1: python: not found"
> sudo apt-get install python
>
> git clone https://github.com/iovisor/bcc.git
> mkdir bcc/build; cd bcc/build
> cmake ..
> make
>
> (4) Additional info
> I just replace the following old file [1] with the latest new file [2],
> then the error disappeared.
> [1] /usr/share/luajit-2.1.0-beta3/jit/bcsave.lua
> [2] https://github.com/LuaJIT/LuaJIT/blob/v2.1/src/jit/bcsave.lua
>
> It seems that this commit fixed it:
> https://github.com/LuaJIT/LuaJIT/commit/94d0b53004a5
>
> (5) Question and Suggestion
> Could you please update the luajit package used with the latest source code?
>
> Thanks,
> Tiezhu
>

Re: need to reinstall pulseaudio every day


On Tue, 23 Feb 2021, David Wright wrote:


Is this buster?


  yes


Are you running any applications, particularly those involving sound,
as root, particularly in response to some previous problem?


  no


Is it just that binary that goes missing, or does apt/dpkg actually
show that the entire package is uninstalled?


   I can't answer that now, because I run
   "ls -l /usr/bin/pulseaudio" every minute to find when it disappears,
   and curiously, it didn't disappear this night
   I'll see what happens after removing  the ls command in cron.

best regards,
--
Pierre Frenkiel

OT: Spicy stuff in sensitive areas (was Re: Got a machine name problem)

2021-02-24 Thread The Wanderer

On 2021-02-24 at 00:05, Gene Heskett wrote:

> On Tuesday 23 February 2021 23:54:03 Stefan Monnier wrote:
> 
 Then reboot and cross your fingers.
>>> 
>>> Arthritis at 86 is beginning to make that painful. :(
>> 
>> I don't believe in crossing fingers either  FWIW, I pick my nose 
>> instead, and I think it works just as well (but be careful not to
>> do that right after chopping some habanero),
> 
> And that rather sounds like the voice of experience :(

Puts me in mind of an anecdote one of my uncles told me, regarding himself.

We're all probably familiar with the little crusty bits that sometimes
have to be wiped out of the eyes after waking up in the morning. (From
what I can tell, these seem to happen more frequently after increased
consumption of sodium or the like.)

An uncle of mine once told me that he used to have to do that on a
regular basis, but then at some point in his life he put a drop of *hot
sauce* into each eye as one does with eyedrops (from what I gather,
apparently intentionally) - and although that was astoundingly painful,
he's never had those little crusty bits again.

I have never dared, nor even seriously had the impulse, to try that
experiment for myself. As to whether it has any basis in empirical fact,
your guess is as good as mine.

-- 
   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

signature.asc
Description: OpenPGP digital signature

Re: Got a machine name problem

2021-02-24 Thread Andrew M.A. Cater

On Tue, Feb 23, 2021 at 12:58:33PM -0500, Gene Heskett wrote:
> Greetings all;
> 
> I have been working on a lower priority project, replacing some atom 
> powered machines with i5 powered Dells. Installing buster but something 
> is overriding my efforts to rename the machine after the install because 
> I'd like to replace "lathe" with "TLM" for The Little Monster.
> 
> Nothing I do survives a reboot, so what do I do to actually rename the 
> machine and make it stick? Hopefully without losiing the networking 
> which I don't have after the last reboot, probably because of the 
> current volatility of interface names.
> 

hostnamectl should do it - and it will be permanent

hostnamectl set-hostname [whatever_you_want_goes_here]

All best, 

Andy C.

> Thanks.
> 
> Cheers, Gene Heskett
> -- 
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> If we desire respect for the law, we must first make the law respectable.
>  - Louis D. Brandeis
> Genes Web page 
>

Re: Got a machine name problem

2021-02-24 Thread Gene Heskett

On Wednesday 24 February 2021 03:32:04 to...@tuxteam.de wrote:

> On Tue, Feb 23, 2021 at 08:21:48PM -0500, Gene Heskett wrote:
> > On Tuesday 23 February 2021 19:22:19 James B wrote:
> > > With systemd-based Debian, the probably now best way to set a
> > > hostname is with:
> > >
> > > hostnamectl set-hostname NAME
> > >
> > > What Tom suggested is completely valid, but hostnamectl should I
> > > understand be the preferred route [...]
>
> ...if you restrict yourself to the systemd world [0], that is.
>
> > Does this also have a set-domainname option? This also is
> > disappearing on a reboot. Not ack the man page so I assume there is
> > a different method to handle that?
>
> Gene, please read the hostname(1) man page. It is short and sweet
> (120 - 240 lines, depending on your screen width). It's all in there.
>
> Choice quotes:
>
> - from the top
>   NAME
>hostname - show or set the system's host name
>domainname - show or set the system's NIS/YP domain name
>ypdomainname - show or set the system's NIS/YP domain name
>nisdomainname - show or set the system's NIS/YP domain name
>dnsdomainname - show the system's DNS domain name
>
I could spend the rest of my life changing it with variant 1, but when 
its been powered down overnight, the old name is restored in the morning 
boot. Now I've tried hostnamectl with its option set-hostname newname.
And I'm going to power it up right now, brb.

Ok hostname is good after reboot, but domainname has been reset to 
(none).

But wtf? I have edited "sudo nano" /etc/domainname, did not set the i 
bit, and the edit is still there, but asking for it is (none)

domainname domain.name changes it only for this boot, a reboot clears it 
to (none) again.

So I must have screwed something up with that edit, but how do I fix it?

Thanks Tomas.

> you can safely ignore all that NIS/YP [1] part, that rules out the
> variants 2-4; the last variant only shows the DNS domain name --
> you'd have to talk to Someone Else (TM) to change that. This leaves
> variant (1), i.e. hostname.
>
> Now:
>
>   DESCRIPTION
> [...]
> SET NAME
>   When called with one argument or with the --file option, the
>   commands set the host name or the NIS/YP domain name [...]
>
> So... it seems we're out of luck? Only changing your domain if it is
> with NIS/YP is supported? But, oh, lookee...
>
>THE FQDN
>  The FQDN (Fully Qualified Domain Name) of the system is the
>  name that the resolver(3) returns for the host name, such as,
>  ursula.example.com [...]
>
>  You cannot change the FQDN with hostname or dnsdomainname.
>
>  The recommended method of setting the FQDN is to make the
>  hostname be an alias for the fully qualified name using
>  /etc/hosts, DNS, or NIS [...]
>
> So if your domain isn't imposed on your host by DNS (you would
> know that, since that's your home network, and you'd have done
> some setup to enforce that or by NIS/YP (you most probably don't
> have that, your network admin, i.e. you, would know that), the
> result is... go look in your /etc/hosts [2] for the domain name
> your box thinks it has.
>
> This seemingly baroque thing is due that the domain name "in"
> which your box lives is a decision that not always can be
> taken by your box alone. Like when I'm in France, I can't say
> "I'm in Luxembourg" unless I am a rich person ;-)
>
> (Exchange perhaps France for U.S. and Luxembourg for Delaware
> for those west of the pond. For those elsewhere, please teach
> me: where are your favourite tax paradises?)
>
> Cheers
>
> [0] Me? I prefer to stay portable. Works consistently across
>systemd and non-systemd boxes.
> [1] https://en.wikipedia.org/wiki/Network_Information_Service
> [2] which kinda makes sense: if you squint a bit, /etc/hosts
>is sorta the "poor person's DNS". Read on the resolver, and
>/etc/resolv.conf for the next rabbit hole.

Rabbit hole is a misnomer, its worse than that. :(

Perhaps I should edit /etc/resolv.conf so it uses localhost, then the dns 
address, for resolving.  Its a real file here. And in looking around, 
none of my buster machines have a domainname. ???  That rabbit hole goes 
down to the iron core. At which point we have well overdone fried 
rabbit.

Thanks Tomas

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page

Re: Got a machine name problem

2021-02-24 Thread tomas

On Wed, Feb 24, 2021 at 06:14:00AM -0500, Gene Heskett wrote:
> On Wednesday 24 February 2021 03:32:04 to...@tuxteam.de wrote:
> 
> > On Tue, Feb 23, 2021 at 08:21:48PM -0500, Gene Heskett wrote:
> > > On Tuesday 23 February 2021 19:22:19 James B wrote:
> > > > With systemd-based Debian, the probably now best way to set a
> > > > hostname is with:
> > > >
> > > > hostnamectl set-hostname NAME
> > > >
> > > > What Tom suggested is completely valid, but hostnamectl should I
> > > > understand be the preferred route [...]
> >
> > ...if you restrict yourself to the systemd world [0], that is.
> >
> > > Does this also have a set-domainname option? This also is
> > > disappearing on a reboot. Not ack the man page so I assume there is
> > > a different method to handle that?
> >
> > Gene, please read the hostname(1) man page.

[...]

> I could spend the rest of my life changing it with variant 1, but when 
> its been powered down overnight, the old name is restored in the morning 
> boot. Now I've tried hostnamectl with its option set-hostname newname.
> And I'm going to power it up right now, brb.

Uh... sorry, you're right. You've got to change /etc/hostname for that.
By whatever means explained in this thread.

Tomas, please read posts more carefully :-)

Apologies
 - t


signature.asc
Description: Digital signature

Re: Got a machine name problem

2021-02-24 Thread Gene Heskett

On Wednesday 24 February 2021 06:13:16 Andrew M.A. Cater wrote:

> On Tue, Feb 23, 2021 at 12:58:33PM -0500, Gene Heskett wrote:
> > Greetings all;
> >
> > I have been working on a lower priority project, replacing some atom
> > powered machines with i5 powered Dells. Installing buster but
> > something is overriding my efforts to rename the machine after the
> > install because I'd like to replace "lathe" with "TLM" for The
> > Little Monster.
> >
> > Nothing I do survives a reboot, so what do I do to actually rename
> > the machine and make it stick? Hopefully without losiing the
> > networking which I don't have after the last reboot, probably
> > because of the current volatility of interface names.

> hostnamectl should do it - and it will be permanent
>
> hostnamectl set-hostname [whatever_you_want_goes_here]
>
But sudo that doesn't give it a domainname even if you rename it fqdn 
style, so I put it back.

> All best,

Thanks Andy C.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page

Re: need to reinstall pulseaudio every day

2021-02-24 Thread Nicholas Geovanis

On Wed, Feb 24, 2021, 3:18 AM Pierre Frenkiel 
wrote:

> 
> I can't answer that now, because I run
> "ls -l /usr/bin/pulseaudio" every minute to find when it disappears,
> and curiously, it didn't disappear this night
>

Quantum physics principles manifest in software, seen it before. The closer
you look, the more dice you have to roll ☺

I'll see what happens after removing  the ls command in cron.
>
> best regards,
> --
> Pierre Frenkiel
>
>

Re: need to reinstall pulseaudio every day

>
>
> I can't answer that now, because I run
> "ls -l /usr/bin/pulseaudio" every minute to find when it disappears,
> and curiously, it didn't disappear this night
> I'll see what happens after removing  the ls command in cron.
>

You could use ``inotify-tools``
https://packages.debian.org/en/buster/inotify-tools
They are based on kernel inotify api:
https://en.wikipedia.org/wiki/Inotify

Re: Got a machine name problem

2021-02-24 Thread Greg Wooledge

Gene Heskett (ghesk...@shentel.net) wrote:
> But wtf? I have edited "sudo nano" /etc/domainname, did not set the i 
> bit, and the edit is still there, but asking for it is (none)

There is no such file on my system.  What made you think that you should
create this file?  What program did you think would use it?

> domainname domain.name changes it only for this boot, a reboot clears it 
> to (none) again.

   domainname - show or set the system's NIS/YP domain name

Are you using NIS?  If you are, you should be configuring the NIS domain
name in the file /etc/defaultdomain (which is read by /etc/init.d/nis
which is what the systemd unit points to, because apparently Debian's NIS
packaging is not fully updated for systemd).

But I think you're actually just confused, and you aren't using NIS, but
somehow you've started poking around at various pieces of NIS without
realizing it.  And you've also mixed up command names and filenames.

> So I must have screwed something up with that edit, but how do I fix it?

What *exactly* are you trying to do?

Are you trying to set your default DNS domain name, which is used to
search for fully qualified hostnames when you only type partial hostnames?

E.g. let's pretend you work for a company named Neener and they use the
domain name neener.com for their internal hosts.  You're at your desk
in the Neener HQ, and you're using a Unix workstation that they've set
up for you.  It has the hostname "ws43", or "ws43.neener.com".

Now, you want to ssh into your coworker's workstation, which has the
hostname "ws31", or "ws31.neener.com".

Since it isn't the 1980s, your workplace has set up a DNS infrastructure
that lets you obtain the IP address of ws31.neener.com (and all the other
workstations, servers, and so on).  So, if you were to type
"ssh ws31.neener.com", that would work.  You'd get the IP address of
ws31.neener.com from DNS, and you'd connect to the correct workstation.

But that's a lot of typing.  So your workplace has also arranged things
so that you can simply type "ssh ws31", and that will also work.

How does that work?

In the file /etc/resolv.conf there are several different kinds of lines
that may be present.  One of them is the "search" line.

If the resolv.conf file contains the line "search neener.com", this means
any hostname that you try to resolve which doesn't contain a dot will
get ".neener.com" appended to it.  So, when you try to resolve "ws31",
the DNS resolver library will automatically try "ws31.neener.com" for
you.

So, the next question is, "How can I put the line search neener.com into
my /etc/resolv.conf file?"  In a sane, sensible universe, it would be
easy -- you would just edit the file with a text editor, and that would
be the end of it.

But we do not live in that universe.

The /etc/resolv.conf file is continually, automatically rewritten by a
plethora of programs that all think they know what you want.  They're
all wrong, of course, but you can't make the developers understand that.
Your changes to the /etc/resolv.conf file will be overwritten, probably
within an hour.

At this point, please read  to see
what your options are, for making permanent changes to resolv.conf.  It's
really stupidly complicated, and there's no point in my repeating it
all here.

THAT is how you set your default DNS domain name, and THAT is what it
means to have a default DNS domain name in the first place.  It's not
about your own hostname.  It's about shortening what you have to type
when you resolve *other* hostnames within your organization's namespace.

Re: need to reinstall pulseaudio every day

2021-02-24 Thread Dan Ritter

Pierre Frenkiel wrote: 
> On Tue, 23 Feb 2021, Dan Ritter wrote:
> 
> > Could be an option. What do you need pulseaudio for that
> > isn't handled by alsa, jack and/or apulse?
> 
> it's needed to have sound on youtube.
> I tried your other suggestions a long time ago, and could not make them to 
> work.
> I'll try again today

Your best bet there is alsa with apulse to pretend that it's
PulseAudio.

-dsr-

Re: Got a machine name problem

2021-02-24 Thread Tom Browder

On Wed, Feb 24, 2021 at 07:44 Greg Wooledge  wrote:

> Gene Heskett (ghesk...@shentel.net) wrote:
> > But wtf? I have edited "sudo nano" /etc/domainname, did not set the i
> > bit, and the edit is still there, but asking for it is (none)

...

For my LAN hosts as well as my WLAN hosts, I have always used the
/etc/hosts file and have never touched the default /etc/resolv.con file.

I have never had any problems with connecting to any of those hosts except
when  adding a new host snd needing to get ssh installed.

-Tom

Re: need to reinstall pulseaudio every day


On Wed, 24 Feb 2021, Nicholas Geovanis wrote:


Quantum physics principles manifest in software, seen it before. The closer
you look, the more dice you have to roll 


   but according Einstein, God doesn't play dice
   it seems he was wrong, this time

best regards,
--
Pierre Frenkiel

Re: Got a machine name problem

2021-02-24 Thread Greg Wooledge

Tom Browder (tom.brow...@gmail.com) wrote:
> For my LAN hosts as well as my WLAN hosts, I have always used the
> /etc/hosts file and have never touched the default /etc/resolv.con file.
> 
> I have never had any problems with connecting to any of those hosts except
> when  adding a new host snd needing to get ssh installed.

This is how things were configured in the early 1980s.  It works, as
long as you can maintain all of those copies of your hosts file, across
however many machines you have.

The disadvantages should be clear.  Every time you add a new host,
you have to go and edit the hosts file on *every other* host, so they
all know about the new guy.  Each time a host moves and gets a new IP
address, you have to edit *every* single hosts file.  And so on.

With a small number of hosts, with no changes occurring, you may be fine,
and you'll never need to change how you work.

For everyone else, there's DNS.

Re: Got a machine name problem

On Tue 23 Feb 2021 at 20:05:11 -0500, Gene Heskett wrote:

> On Tuesday 23 February 2021 14:29:01 Tom Browder wrote:
> 
> > Hey, Gene.  I usually have to fiddle around a little, but I've always
> > had success on Debian this way (as root):
> >
> > # hostname TLM
> >
> >edit /etc/hostname and set the desired name to TLM if it's not
> > already changed
> >
> > I also edit /etc/hosts and make the first couple of lines look like
> > this:
> >
> > 127.0.0.1 localhost.localdomain.com   localhost
> > 127.0.1.1 TLM.geneslinuxbox.netTLM
> 
> The first line is std here.

It may be your "standard", but it isn't what the installer gave you.
Is there a good reason for changing it?

> Why should it have the 2nd one?

Your machine hasn't any static external IP address. The system hostname
has to resolve to something and is assigned 127.0.1.1.

-- 
Brian.

Re: need to reinstall pulseaudio every day


On Wed, 24 Feb 2021, Dan Ritter wrote:


Your best bet there is alsa with apulse to pretend that it's
PulseAudio.


 the main difference is that it took 15 seconds to install pulseaudio and make 
it
 to work, and after 15 minutes of fight, I'm unable to make apulse to work
 I don't see why I should waste time to to replace a working solution by
 a non-working one.

PS: now, I don't need to re-install. I cross fingers.

best regards,
--
Pierre Frenkiel

Re: Got a machine name problem

2021-02-24 Thread Tom Browder

On Wed, Feb 24, 2021 at 08:11 Greg Wooledge  wrote:

> Tom Browder (tom.brow...@gmail.com) wrote:
> > For my LAN hosts as well as my WLAN hosts, I have always used the
> > /etc/hosts file and have never touched the default /etc/resolv.con file.
> >
> > I have never had any problems with connecting to any of those hosts
> except
> > when  adding a new host snd needing to get ssh installed.
>
> This is how things were configured in the early 1980s.  It works, as
> long as you can maintain all of those copies of your hosts file, across
> however many machines you have.
>
> The disadvantages should be clear.  Every time you add a new host,
> you have to go and edit the hosts file on *every other* host, so they
> all know about the new guy.  Each time a host moves and gets a new IP
> address, you have to edit *every* single hosts file.  And so on.

I'm not arguing with you, just saying it works for me and has for many
years (since I was with my former employer when we had our first LAN hookup
with coax cable in 1994ish with SGI hosts mixed with Windows PCs and Redhat
Linux PCs). The most hosts we ever had was about 30 and several of us
shared sysadmin duties.

I've continued that way on my own private network. Gene can probably do the
same.

The "real" way to do it is of course necessary for modern "real" networks
with dedicated sysadmin staff members.

Best regards,

-Tom

How to self-load non-freeware firmware on existing netinst ISO installer

I have another laptop which dual boot with Fedora and Windows10, it is not
my primary laptop since 9 months ago and I haven't used it since then. I
plan to fully install Debian testing on this machine because this laptop
has dual graphic cards (optimus) and theoretically, with Debian 11 (or
newer), special configuration shouldn't be needed and offloading should be
available as soon as you've installed the proprietary drivers[1]. This
machine has a faulty LAN port and only 1 of 3 USB ports are usable. So I
can only use 1 USB per time and only WIFI for the network connection.

Since Debian provides an unofficial netinst image for i386/amd64/powerpc
with the non-free firmware, I go and download the ISO[2] and make a
bootable USB installer.

But when I during the installation process (on "detect network hardware"
phase),   debian-installer dialog  asked me to load 2 firmware which is
iwIwifi-2030-6.ucode and  iwIwifi-2030-5.ucode  .. I feel perplexed about
this. So I checked the USB, it already have the firmware but with deb
package format:

/firmware/firmware-iwlwifi_20201218-3_all.deb
/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20201218-3_all.deb

Seems this firmware load on the next stage which is after network setup and
after do the partitioning stuff. I wonder why, since this is netinst I need
network working from the during installation process, not after that.

Question :
a) Is it possible to do self modification on the installation script so the
wifi chip will be available and working during the installation process so
I can pull the packages that I want during installation from Debian mirror.
If yes, how and if no, please suggest me some solutions that don't need me
to fix LAN port, buy cable and router (since I use wifi hotspot from my
phone)

The precompile firmware are available here[3] and here[4]

TLDR; I want  firmware-iwlwifi  already loaded and working during Debian
installation phase, not after install.

[1] https://wiki.debian.org/NVIDIA%20Optimus#PRIMEOffload
[2]
http://cdimage.debian.org/cdimage/unofficial/non-free/images-including-firmware/weekly-builds/amd64/iso-cd/firmware-testing-amd64-netinst.iso
[3]
https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-2030-ucode-18.168.6.1.tgz
[4] https://github.com/OpenELEC/iwlwifi-firmware/tree/master/firmware

Re: Got a machine name problem

2021-02-24 Thread Stefan Monnier

> Tomas, please read posts more carefully :-)

FWIW, `man hostname` also mentions /etc/hostname and /etc/hosts.


Stefan

Re: How to self-load non-freeware firmware on existing netinst ISO installer

2021-02-24 Thread Kenneth Parker

On Wed, Feb 24, 2021, 10:09 AM Robbi Nespu  wrote:

> I have another laptop which dual boot with Fedora and Windows10, it is not
> my primary laptop since 9 months ago and I haven't used it since then. I
> plan to fully install Debian testing on this machine because this laptop
> has dual graphic cards (optimus) and theoretically, with Debian 11 (or
> newer), special configuration shouldn't be needed and offloading should be
> available as soon as you've installed the proprietary drivers[1]. This
> machine has a faulty LAN port and only 1 of 3 USB ports are usable. So I
> can only use 1 USB per time and only WIFI for the network connection.
>
> Since Debian provides an unofficial netinst image for i386/amd64/powerpc
> with the non-free firmware, I go and download the ISO[2] and make a
> bootable USB installer.
>
> But when I during the installation process (on "detect network hardware"
> phase),   debian-installer dialog  asked me to load 2 firmware which is
> iwIwifi-2030-6.ucode and  iwIwifi-2030-5.ucode  .. I feel perplexed about
> this. So I checked the USB, it already have the firmware but with deb
> package format:
>
> /firmware/firmware-iwlwifi_20201218-3_all.deb
> /pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20201218-3_all.deb
>
> Seems this firmware load on the next stage which is after network setup
> and after do the partitioning stuff. I wonder why, since this is netinst I
> need network working from the during installation process, not after that.
>
> Question :
> a) Is it possible to do self modification on the installation script so
> the wifi chip will be available and working during the installation process
> so I can pull the packages that I want during installation from Debian
> mirror. If yes, how and if no, please suggest me some solutions that don't
> need me to fix LAN port, buy cable and router (since I use wifi hotspot
> from my phone)
>

When I had a situation like that, my workaround was to install without the
Network (but with the netinst CD), stopping at the "minimal system". It
actually gives you a bootable system.  And then, use the external media to
get WiFi working, and go from there.

>
> The precompile firmware are available here[3] and here[4]
>
> TLDR; I want  firmware-iwlwifi  already loaded and working during Debian
> installation phase, not after install.
>
> [1] https://wiki.debian.org/NVIDIA%20Optimus#PRIMEOffload
> [2]
> http://cdimage.debian.org/cdimage/unofficial/non-free/images-including-firmware/weekly-builds/amd64/iso-cd/firmware-testing-amd64-netinst.iso
> [3]
> https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-2030-ucode-18.168.6.1.tgz
> [4] https://github.com/OpenELEC/iwlwifi-firmware/tree/master/firmware
>

Kenneth Parker

>
>

Re: How to self-load non-freeware firmware on existing netinst ISO installer

On Wed 24 Feb 2021 at 22:51:05 +0800, Robbi Nespu wrote:

[...]

> TLDR; I want  firmware-iwlwifi  already loaded and working during Debian
> installation phase, not after install.

This is from memory; I haven't done it for some time.

1. The USB stick you boot from will have empty space or a secomd
   partition.

2. Extract the firmware files from the .deb and put them on the
   stick.

3. Boot and change to console 2: ALT-F2.

4. Mount the partition holding the firmware on /mnt.

5. Create /lib/firmware: mkdir /lib/firmware and transfer the
   firmware there.

6. ALT-F1 to go back to d-i. d-i should now find the firmware.

-- 
Brian.

Re: How to self-load non-freeware firmware on existing netinst ISO installer

2021-02-24 Thread John Boxall





On 2021-02-24 11:07 a.m., Brian wrote:

On Wed 24 Feb 2021 at 22:51:05 +0800, Robbi Nespu wrote:

[...]


TLDR; I want  firmware-iwlwifi  already loaded and working during Debian
installation phase, not after install.


This is from memory; I haven't done it for some time.

1. The USB stick you boot from will have empty space or a secomd
partition.

2. Extract the firmware files from the .deb and put them on the
stick.

3. Boot and change to console 2: ALT-F2.

4. Mount the partition holding the firmware on /mnt.

5. Create /lib/firmware: mkdir /lib/firmware and transfer the
firmware there.

6. ALT-F1 to go back to d-i. d-i should now find the firmware.



Alternatively, you can extract the firmware files to a different USB 
stick and put them in the root of that one, insert both and the 
installer will find the files when you boot the original USB stick.

--
Regards,

John Boxall

Re: need to reinstall pulseaudio every day

2021-02-24 Thread Nicholas Geovanis

On Wed, Feb 24, 2021, 7:57 AM Pierre Frenkiel 
wrote:

> On Wed, 24 Feb 2021, Nicholas Geovanis wrote:
>
> > Quantum physics principles manifest in software, seen it before. The
> closer
> > you look, the more dice you have to roll
> >
> but according Einstein, God doesn't play dice
> it seems he was wrong, this time
>

But of course Einstein said that in response to the work of Heisenberg and
Bohr. Which was also quite experimental as well as theoretical. Probability
is predictive at the sub-atomic level.

best regards,
> --
> Pierre Frenkiel
>
>

Re: shadowy, sort of fly by night debian mirrors? ...

2021-02-24 Thread Albretch Mueller

sorry, bad wording typing fast. what I meant is that I use the wget
setting "--server-response" and keep my logs, but all I could see in
the logs was:

WARNING: certificate common name `ftp.acc.umu.se' doesn't match
requested host name `chuangtzu.ftp.acc.umu.se'.
2021-02-17 11:14:47
URL:https://chuangtzu.ftp.acc.umu.se/debian-cd/current/amd64/iso-dvd/debian-10.8.0-amd64-DVD-2.iso
[4697370624/4697370624] -> "debian-10.8.0-amd64-DVD-2.iso" [1]

WARNING: certificate common name `ftp.acc.umu.se' doesn't match
requested host name `laotzu.ftp.acc.umu.se'.
2021-02-17 11:46:46
URL:https://laotzu.ftp.acc.umu.se/debian-cd/current/amd64/iso-dvd/debian-10.8.0-amd64-DVD-3.iso
[4679073792/4679073792] -> "debian-10.8.0-amd64-DVD-3.iso" [1]

I had never seen anything like that in my logs before, let alone from
debian mirrors. Why would they not protocol their server responses as
every server does?

Yes, I have plenty of reasons to believe "they are watching 'me' (and
'you' and every one and their pets)". That is why I effing never
connect my main work computer to the Internet and the greatest part of
my paranoia is that at the end of the day anyone can take that data
and check it (of course, offline), provided you are able to get a hold
of an uncorrupted data set somehow. It is as simple as that!

Also, I take pride at being from very prejudiced to cautiously racist
towards those not only "un-Amerikan", but, even "communist" Chinese
before they spread the Corona Virus and about the fact that Vladimir
Putin hasn't been able to take away my girlfriend, yet. I would have
been a bit less racist towards them (just a bit) if they had infected
Trump and his wife earlier to make him shut the eff up. I heard they
had been cooking some other virus to make people stop thumbing their
cell phones as teen agers touch their genitals. As John Lennon sang,
"Imagine!" what would have been of Trump without tweeting! If those
Chinese lowlifes would had managed that I would have stopped being
racist towards them for a weekend.

lbrtchx

Re: How to self-load non-freeware firmware on existing netinst ISO installer

On Wed 24 Feb 2021 at 11:14:59 -0500, John Boxall wrote:

> 
> 
> On 2021-02-24 11:07 a.m., Brian wrote:
> > On Wed 24 Feb 2021 at 22:51:05 +0800, Robbi Nespu wrote:
> > 
> > [...]
> > 
> > > TLDR; I want  firmware-iwlwifi  already loaded and working during Debian
> > > installation phase, not after install.
> > 
> > This is from memory; I haven't done it for some time.
> > 
> > 1. The USB stick you boot from will have empty space or a secomd
> > partition.
> > 
> > 2. Extract the firmware files from the .deb and put them on the
> > stick.
> > 
> > 3. Boot and change to console 2: ALT-F2.
> > 
> > 4. Mount the partition holding the firmware on /mnt.
> > 
> > 5. Create /lib/firmware: mkdir /lib/firmware and transfer the
> > firmware there.
> > 
> > 6. ALT-F1 to go back to d-i. d-i should now find the firmware.
> > 
> 
> Alternatively, you can extract the firmware files to a different USB stick
> and put them in the root of that one, insert both and the installer will
> find the files when you boot the original USB stick.

Indeed. However, the problem (unless I am misunderstanding) is that
the firmware is not even being found on the non-free netinstall,
which is the whole point of having that image available.

-- 
Brian.

Re: shadowy, sort of fly by night debian mirrors? ...

2021-02-24 Thread Andy Smith

Albrecht,

On Wed, Feb 24, 2021 at 11:27:31AM -0500, Albretch Mueller wrote:
> I take pride at being from very prejudiced to cautiously racist
> towards those not only "un-Amerikan", but,  even "communist"
> Chinese before they spread the Corona Virus…

Your racist conspiracy theories are not only abhorrent but also a
violation of Debian's Code of Conduct. Please do not post this kind
of thing to any part of Debian's infrastructure again (or
preferably, anywhere, ever, but it is specifically not tolerated
at Debian).

https://lists.debian.org/debian-user/2021/02/msg00010.html
https://www.debian.org/MailingLists/#codeofconduct
https://www.debian.org/code_of_conduct

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: need to reinstall pulseaudio every day

2021-02-24 Thread Nicholas Geovanis

On Wed, Feb 24, 2021, 10:16 AM Nicholas Geovanis 
wrote:

> On Wed, Feb 24, 2021, 7:57 AM Pierre Frenkiel 
> wrote:
>
>> On Wed, 24 Feb 2021, Nicholas Geovanis wrote:
>>
>> > Quantum physics principles manifest in software, seen it before. The
>> closer
>> > you look, the more dice you have to roll
>> >
>> but according Einstein, God doesn't play dice
>> it seems he was wrong, this time
>>
>
> But of course Einstein said that in response to the work of Heisenberg and
> Bohr. Which was also quite experimental as well as theoretical. Probability
> is predictive at the sub-atomic level.
>

In Schrödinger's Equation of quantum physics, "in practice, the square of
the absolute value of the wave function at each point is taken to define a
probability density function".

best regards,
>> --
>> Pierre Frenkiel
>>
>

Re: shadowy, sort of fly by night debian mirrors? ...

2021-02-24 Thread Reco

Hi.

On Wed, Feb 24, 2021 at 11:27:31AM -0500, Albretch Mueller wrote:
>  sorry, bad wording typing fast. what I meant is that I use the wget
> setting "--server-response" and keep my logs, but all I could see in
> the logs was:
> 
> WARNING: certificate common name `ftp.acc.umu.se' doesn't match
> requested host name `chuangtzu.ftp.acc.umu.se'.

And "openssl x509" helpfully shows that chuangtzu.ftp.acc.umu.se uses
the certificate issued to "CN = ftp.acc.umu.se" by LetsEncrypt, and has
chuangtzu.ftp.acc.umu.se in the "X509v3 Subject Alternative Name"
section.
I.e. the certificate is as valid as you consider LetsEncrypt to be.

Debian's wget uses GnuTLS for https, and GnuTLS can be quirky in this
regard.

>  I had never seen anything like that in my logs before, let alone from
> debian mirrors. Why would they not protocol their server responses as
> every server does?

Because less is more. As seen above, all you get is a false positive.
The less garbage fill your logs - the clearer the cause of the problem
is.

>  Yes, I have plenty of reasons to believe "they are watching 'me' (and
> 'you' and every one and their pets)".
...

Dear Albretch, you're in a in-between position here.

Either try to approach to the problem as an engineer. For instance,
judging a host by host name is not racist, it's highly inaccurate at
best (I'll refrain from stronger terms). According to RIPE, umu.se is a
perfectly valid Swedish domain, registered back in '87.

Or, try to approach a problem as complete lunatic. In this case, your
rant clearly lacks mentioning of nano-chips that are included in each
and every COVID vaccine shot, an ability to control said nano-chips via
5G, and last, but not least - the secret cabal which benefits from it.

To be serious, first approach is welcome here. Please try second
approach elsewhere.

Reco

Re: Got a machine name problem

2021-02-24 Thread Gene Heskett

On Wednesday 24 February 2021 08:44:06 Greg Wooledge wrote:

> Gene Heskett (ghesk...@shentel.net) wrote:
> > But wtf? I have edited "sudo nano" /etc/domainname, did not set the
> > i bit, and the edit is still there, but asking for it is (none)
>
> There is no such file on my system.  What made you think that you
> should create this file?  What program did you think would use it?
>
> > domainname domain.name changes it only for this boot, a reboot
> > clears it to (none) again.
>
>domainname - show or set the system's NIS/YP domain name
>
> Are you using NIS?  If you are, you should be configuring the NIS
> domain name in the file /etc/defaultdomain (which is read by
> /etc/init.d/nis which is what the systemd unit points to, because
> apparently Debian's NIS packaging is not fully updated for systemd).
>
> But I think you're actually just confused, and you aren't using NIS,
> but somehow you've started poking around at various pieces of NIS
> without realizing it.  And you've also mixed up command names and
> filenames.
>
> > So I must have screwed something up with that edit, but how do I fix
> > it?
>
> What *exactly* are you trying to do?
>
> Are you trying to set your default DNS domain name, which is used to
> search for fully qualified hostnames when you only type partial
> hostnames?
>
> E.g. let's pretend you work for a company named Neener and they use
> the domain name neener.com for their internal hosts.  You're at your
> desk in the Neener HQ, and you're using a Unix workstation that
> they've set up for you.  It has the hostname "ws43", or
> "ws43.neener.com".
>
> Now, you want to ssh into your coworker's workstation, which has the
> hostname "ws31", or "ws31.neener.com".
>
> Since it isn't the 1980s, your workplace has set up a DNS
> infrastructure that lets you obtain the IP address of ws31.neener.com
> (and all the other workstations, servers, and so on).  So, if you were
> to type
> "ssh ws31.neener.com", that would work.  You'd get the IP address of
> ws31.neener.com from DNS, and you'd connect to the correct
> workstation.
>
> But that's a lot of typing.  So your workplace has also arranged
> things so that you can simply type "ssh ws31", and that will also
> work.
>
> How does that work?

By looking its alias up in /etc/hosts.

> In the file /etc/resolv.conf there are several different kinds of
> lines that may be present.  One of them is the "search" line.
2 lines in that real file.

search coyote.den
dnsserver ipv4 address

which is the local domain name. And that does show up in the 
dnsdomainname report. That just started working but I've no clue why.

> If the resolv.conf file contains the line "search neener.com", this
> means any hostname that you try to resolve which doesn't contain a dot
> will get ".neener.com" appended to it.  So, when you try to resolve
> "ws31", the DNS resolver library will automatically try
> "ws31.neener.com" for you.
>
> So, the next question is, "How can I put the line search neener.com
> into my /etc/resolv.conf file?"  In a sane, sensible universe, it
> would be easy -- you would just edit the file with a text editor, and
> that would be the end of it.
>
> But we do not live in that universe.
>
It hasn't existed since Pottering came on the scene...
So its not a mystery link to something resolveconf might conjure up, and 
if it gets changed, NM is famous for that, so it gets restored and a +i 
applied.

> The /etc/resolv.conf file is continually, automatically rewritten by a
> plethora of programs that all think they know what you want.  They're
> all wrong, of course, but you can't make the developers understand
> that. Your changes to the /etc/resolv.conf file will be overwritten,
> probably within an hour.
>
> At this point, please read  to
> see what your options are, for making permanent changes to
> resolv.conf.  It's really stupidly complicated, and there's no point
> in my repeating it all here.
>
I just read it, Stupid is not an adequate description.

> THAT is how you set your default DNS domain name, and THAT is what it
> means to have a default DNS domain name in the first place.  It's not
> about your own hostname.  It's about shortening what you have to type
> when you resolve *other* hostnames within your organization's
> namespace.

Well, its now working. If I suddenly develop a bad case of the 
169.it.is.flu in my routing table, synaptic won't let me remove avahi or 
nm without totally destroying the system, but nothing complains if I 
nuke the binaries.

avahi and nm may be solutions a lappy user might need. Damned little is 
portable here without a multi-ton gantry crane. They are both just 
problems waiting to bite me, and to be emasculated by whatever means it 
takes.

My network was built by me, nothing portable about it, and I don't 
understand why a dirt simple, static, /etc/hosts based local network, is 
so damned hard to actually make work. It doesn't need a dns server other 
th

Debian install Question

2021-02-24 Thread M.R.P. zensky

Hello I am installing Debian on a amd processor computer. I connect to the net 
with wifi. I have tried the net install iso and it did not work. I think I need 
the unoficial stable non free firmware included. I select a mirror site but 
Here I am confused about what iso file I want. I am also assuming that I need 
an image for cd-rom. Any help would be apreciated.

Re: Debian install Question

Hello.
Try to download and install "debian-10.8.0-amd64-DVD-1.iso"
from here:
https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/



On Wed, Feb 24, 2021 at 8:48 PM M.R.P. zensky 
wrote:

> Hello I am installing Debian on a amd processor computer. I connect to the
> net with wifi. I have tried the net install iso and it did not work. I
> think I need the unoficial stable non free firmware included. I select a
> mirror site but Here I am confused about what iso file I want. I am also
> assuming that I need an image for cd-rom. Any help would be apreciated.
>

Re: Got a machine name problem

2021-02-24 Thread Greg Wooledge

Gene Heskett (ghesk...@shentel.net) wrote:
> > What *exactly* are you trying to do?

(crickets chirping)

> > How does that work?
> 
> By looking its alias up in /etc/hosts.

I was using rhetorical devices.  If you're truly using a pre-DNS
local network, then a lot of what I said simply does not apply to you.

> > In the file /etc/resolv.conf there are several different kinds of
> > lines that may be present.  One of them is the "search" line.
> 2 lines in that real file.
> 
> search coyote.den
> dnsserver ipv4 address

Your first line is valid.  Your second line is not.  There is no
keyword "dnsserver" in resolv.conf(5).  DNS resolvers are listed here
using the keyword "nameserver".

> It hasn't existed since Pottering came on the scene...

DHCP client daemons overwriting resolv.conf predate systemd by a lot.
This is not a thing that systemd can be blamed for.

> avahi and nm may be solutions a lappy user might need. Damned little is 
> portable here without a multi-ton gantry crane. They are both just 
> problems waiting to bite me, and to be emasculated by whatever means it 
> takes.

If you don't need them, delete them.

> My network was built by me, nothing portable about it, and I don't 
> understand why a dirt simple, static, /etc/hosts based local network, is 
> so damned hard to actually make work.

It's not!

Is that what you want?  A local network defined entirely by hosts files?
You can do that.  It's easy.  Just edit your /etc/hosts files to contain
the names and addresses of your machines.

In this scenario, your resolv.conf file will be used only to look up
hosts that live outside of your local network ("in the cloud").  You
won't CARE what the default DNS domain name is, because you aren't using
it.  Your local host lookups will be done by matching the strings that
you put in your hosts files.

Since you don't care what your resolv.conf file contains, you don't need
to jump through all the hoops involved in trying to prevent daemons from
overwriting it.  Let them.  Ignore them.  Your hostnames are defined in
your hosts files, and nothing will touch those.

Re: Got a machine name problem

2021-02-24 Thread Celejar

On Wed, 24 Feb 2021 12:25:34 -0500
Gene Heskett  wrote:

> On Wednesday 24 February 2021 08:44:06 Greg Wooledge wrote:
> 
> > Gene Heskett (ghesk...@shentel.net) wrote:

...

> > So, the next question is, "How can I put the line search neener.com
> > into my /etc/resolv.conf file?"  In a sane, sensible universe, it
> > would be easy -- you would just edit the file with a text editor, and
> > that would be the end of it.
> >
> > But we do not live in that universe.
> >
> It hasn't existed since Pottering came on the scene...

Not everything is systemd's fault - this craziness predates systemd, as
explained in https://wiki.debian.org/resolv.conf, mentioned by Greg
below.

> So its not a mystery link to something resolveconf might conjure up, and 
> if it gets changed, NM is famous for that, so it gets restored and a +i 
> applied.
> 
> > The /etc/resolv.conf file is continually, automatically rewritten by a
> > plethora of programs that all think they know what you want.  They're
> > all wrong, of course, but you can't make the developers understand
> > that. Your changes to the /etc/resolv.conf file will be overwritten,
> > probably within an hour.
> >
> > At this point, please read  to
> > see what your options are, for making permanent changes to
> > resolv.conf.  It's really stupidly complicated, and there's no point
> > in my repeating it all here.

Celejar

Re: need to reinstall pulseaudio every day


On Wed, 24 Feb 2021, Nicholas Geovanis wrote:


In Schrödinger's Equation of quantum physics, "in practice, the square of
the absolute value of the wave function at each point is taken to define a
probability density function".


 the situation is rather complex  now, after the experiments following
 the Bell's inequalities.
 For example, a lot of people think now that in the Schrodinger's cat
 experiment, the cat is actually alive or dead, before anybody open the door.

best regards,
--
Pierre Frenkiel

Re: Debian install Question

2021-02-24 Thread David Christensen


On 2021-02-24 09:47, M.R.P. zensky wrote:

Hello I am installing Debian on a amd processor computer. I connect to the net 
with wifi. I have tried the net install iso and it did not work. I think I need 
the unoficial stable non free firmware included. I select a mirror site but 
Here I am confused about what iso file I want. I am also assuming that I need 
an image for cd-rom. Any help would be apreciated.



I suggest that you try an "unofficial" installer that includes non-free 
firmware:


https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/


David

Re: Got a machine name problem

>
>
> Is that what you want?  A local network defined entirely by hosts files?
> You can do that.  It's easy.  Just edit your /etc/hosts files to contain
> the names and addresses of your machines.
>
> In this scenario, your resolv.conf file will be used only to look up
> hosts that live outside of your local network ("in the cloud").  You
> won't CARE what the default DNS domain name is, because you aren't using
> it.  Your local host lookups will be done by matching the strings that
> you put in your hosts files.
>


IMHO: "hosts" files could only be used in the network that uses static IP
addresses.
In this case neither DHCP client nor NetworkManager should be used, so
nothing should touch ``resolve.conf``.
And that means the DNS server could be used.

Sysadmin simply runs DNS server for the "younetwork.name" domain, adds "A"
record for each PC manually, and
then adds "nameserver" and "domain" to the "resolve.conf" on each station.
Latter is required to access "pc1.yournetwork.name" as "pc1".

To rename a machine one can simply change "A" record on DNS and "hostname"
on station.
All changes are persistent, because nothing overwrites resolve.conf

Changing name in two places (station and DNS) is easier than changing it on
all "hosts" files across your network.

Re: shadowy, sort of fly by night debian mirrors? ...

2021-02-24 Thread Steve McIntyre

lbrt...@gmail.com wrote:
>
> Also, I take pride at being from very prejudiced to cautiously racist
>towards those not only "un-Amerikan", but,  even "communist" Chinese
>before they spread the Corona Virus and about the fact that Vladimir

This kind of stuff has *no* place at all on Debian mailing lists, nor
anywhere else in our community. Please keep this kind of garbage to
yourself in future, or you will be blocked from posting to Debian
lists.

Steve, for the Community Team.

-- 
Steve McIntyre  93...@debian.org
Debian Community Team   commun...@debian.org

Re: Got a machine name problem

On Wed 24 Feb 2021 at 14:11:35 +, Brian wrote:

> On Tue 23 Feb 2021 at 20:05:11 -0500, Gene Heskett wrote:
> 
> > On Tuesday 23 February 2021 14:29:01 Tom Browder wrote:

[...]

> > > I also edit /etc/hosts and make the first couple of lines look like
> > > this:
> > >
> > > 127.0.0.1 localhost.localdomain.com   localhost
> > > 127.0.1.1 TLM.geneslinuxbox.netTLM
> > 
> > The first line is std here.
> 
> It may be your "standard", but it isn't what the installer gave you.
> Is there a good reason for changing it?

No good reason advanced.

For those users who read this far: ignore this advice; it is
something the OP is programmed to do without putting any
thought or investigation into the matter and isn't of any use.
Stick with what the installer gives you.

-- 
Brian.

Re: Debian install Question

2021-02-24 Thread Henning Follmann

On Wed, Feb 24, 2021 at 08:49:32PM +0300, IL Ka wrote:
> Hello.
> Try to download and install "debian-10.8.0-amd64-DVD-1.iso"
> from here:
> https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/
> 
>

Please do not do that.


You will find a iso here which includes most of the non-free firmware here:
https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/10.8.0+nonfree/amd64/iso-dvd/

Please take the time to read AND understand the information on that site.


-H




-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: Debian install Question

>
> Please do not do that.
>
>
> You will find a iso here which includes most of the non-free firmware here:
>
> https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/10.8.0+nonfree/amd64/iso-dvd/
>
> Please take the time to read AND understand the information on that site.
>

I am sorry for giving inadequate advice. Please forgive me as I am new to
Debian.
My idea was to install Debian, and then install non-free firmware.

This is the third question about "how to install Debian if I have nic that
needs non-free firmware" I see in this list on this week.

So, what is the best practice to do so? Use an unofficial installer that
contains non-free firmware?
If so, I believe this info is worth adding to the Debian installation guide
somewhere in the wiki, so we can give a link to this wiki to newbies.
It seems that a lot of people face this problem trying to install Debian on
their laptops.

Re: Debian install Question

On Thu 25 Feb 2021 at 01:36:58 +0300, IL Ka wrote:

> >
> > Please do not do that.
> >
> >
> > You will find a iso here which includes most of the non-free firmware here:
> >
> > https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/10.8.0+nonfree/amd64/iso-dvd/
> >
> > Please take the time to read AND understand the information on that site.
> >
> 
> I am sorry for giving inadequate advice. Please forgive me as I am new to
> Debian.
> My idea was to install Debian, and then install non-free firmware.

That was what I thought your intention was and I do not think it is
such bad idea, unless the user knows that she does not want Gnome.
 
> This is the third question about "how to install Debian if I have nic that
> needs non-free firmware" I see in this list on this week.
> 
> So, what is the best practice to do so? Use an unofficial installer that
> contains non-free firmware?

If the widest installation framework is required, that is probably best.

> If so, I believe this info is worth adding to the Debian installation guide
> somewhere in the wiki, so we can give a link to this wiki to newbies.
> It seems that a lot of people face this problem trying to install Debian on
> their laptops.

I've not looked at the wiki.

-- 
Brian.

Re: Debian install Question

2021-02-24 Thread Dan Ritter

IL Ka wrote: 
> 
> I am sorry for giving inadequate advice. Please forgive me as I am new to
> Debian.
> My idea was to install Debian, and then install non-free firmware.
> 
> This is the third question about "how to install Debian if I have nic that
> needs non-free firmware" I see in this list on this week.
> 
> So, what is the best practice to do so? Use an unofficial installer that
> contains non-free firmware?
> If so, I believe this info is worth adding to the Debian installation guide
> somewhere in the wiki, so we can give a link to this wiki to newbies.
> It seems that a lot of people face this problem trying to install Debian on
> their laptops.


Yes.

It's in the wiki, but it isn't at the front.

Most people with laptops are going to need it, or a similar
workaround.

Here's some recent discussion: https://lwn.net/Articles/843172/

-dsr-

Re: Debian install Question

2021-02-24 Thread Weaver

On 25-02-2021 09:32, Dan Ritter wrote:
> IL Ka wrote: 
>>
>> I am sorry for giving inadequate advice. Please forgive me as I am new to
>> Debian.
>> My idea was to install Debian, and then install non-free firmware.

This is quite possible.

>> This is the third question about "how to install Debian if I have nic that
>> needs non-free firmware" I see in this list on this week.
>>
>> So, what is the best practice to do so? Use an unofficial installer that
>> contains non-free firmware?

That's actually not required.
For a little while now, I've had a 2016 Acer TravelMate.
This requires three different blobs of non-free software to operate
efficiently.
As long as you opt for the nonfree and contrib lines to be included in
your sources.list file during installation, they're there when the
install process is over.
As soon as the netinst disc is spat out and reboot happens, there
appears to be a period when I can install aptitude, mc, menu, and a
couple of other niceties.
I then call up aptitude interface and go through the kernel nonfree
sector for the blobs I require, clearly delineated during the install
process.
Intel's iwlwifi being one of the packages required for this machine.

>> If so, I believe this info is worth adding to the Debian installation guide
>> somewhere in the wiki, so we can give a link to this wiki to newbies.

Definitely!

>> It seems that a lot of people face this problem trying to install Debian on
>> their laptops.

It's how I learnt to deal with it, two or three installs later.
Cheers!

Harry.

-- 
`The World is not dangerous because of those who do harm but
 because of those who look on without doing anything'.
 -- Albert Einstein

Re: How to self-load non-freeware firmware on existing netinst ISO installer

On Wed, 24 Feb 2021 10:39:16 -0500 Kenneth Parker  
wrote:
When I had a situation like that, my workaround was to install without the Network (but with the netinst CD), stopping at the "minimal system". It actually gives you a bootable system.  And then, use the external media to get WiFi working, and go from there. 


I also thinking to go this way but there could be another better 
solution to load the firmware at the beginning of installation (which is 
the most prefer solution) since I have ucode precompiled binary from 
Intel with me, let use it but I don't know how modify the installer or 
how to re-create the installer.


--
Email : Robbi Nespu 
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc

Re: How to self-load non-freeware firmware on existing netinst ISO installer


On Wed, 24 Feb 2021 16:07:09 +, Brian  wrote:

his is from memory; I haven't done it for some time.

1. The USB stick you boot from will have empty space or a secomd
   partition.


There only one partition but there is lot of empty space


2. Extract the firmware files from the .deb and put them on the
   stick.

It doesn't matter where I put right (on root location)? or need to have 
special directory?



3. Boot and change to console 2: ALT-F2.

4. Mount the partition holding the firmware on /mnt.

This is tricky part as I mentioned, I only have one partition. Where I 
can find my USB device location? try with `dh` command but that command 
not working/available



5. Create /lib/firmware: mkdir /lib/firmware and transfer the
   firmware there.

6. ALT-F1 to go back to d-i. d-i should now find the firmware.
You suggestion look like the most closest one, just need to find the 
perfect way how to accomplish it


--
Email : Robbi Nespu 
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc

Re: How to self-load non-freeware firmware on existing netinst ISO installer


On Wed, 24 Feb 2021 11:14:59 -0500, John Boxall  wrote:

Alternatively, you can extract the firmware files to a different USB stick and 
put them in the root of that one, insert both and the installer will find the 
files when you boot the original USB stick.


To bad, this machine only have 1 working USB port. Plan to fix the other 
2 USB port too but currently I can't cross district travel since 
"lock-down 2.0" in Malaysia. The USB port are faulty causes by USB fans..


--
Email : Robbi Nespu 
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc

Re: How to self-load non-freeware firmware on existing netinst ISO installer