Re: Debian 9 cron = sounds are ok : Debian 11 cron no sound [Solved]

[Roger Price]

On Sun, 17 Jul 2022, 16 Jul 2022, Lee wrote:

Nope.  Audio has always just worked; I never had to do anything
special or extra to get it working


Following https://wiki.archlinux.org/title/PulseAudio/Examples ,
I installed file ~/.config/pulse/default.pa

   .include /etc/pulse/default.pa
   set-default-sink alsa_output.pci-_00_1b.0.analog-stereo

rebooted the machine and it works correctly! I hear historic dog Biff still 
barking.


As Lee reported, it just worked, with no need to specify XDG_RUNTIME_DIR. I 
suspect that my ~/.config/pulse/default.pa is not really needed, but by 
installing it I cleaned up the default pulse mess left over by previous 
operating system installations (My user space ~rprice has been running since 
Sept 1994).


To my surprise, when cron calls the Bash script bark.sh, command "pactl list 
short sinks" reports


  Connection failure: Connection refused

and command "pacmd list-sinks" also reports:

  No PulseAudio daemon running, or not running as session daemon.

but if Biff barks, I won't worry.   Roger

Re: failure trying to install bullseye on Cubox-i

[Vagrant Cascadian]

On 2022-07-17, Rick Thomas wrote:
> I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep around for 
> testing purposes.
>
> I followed the instructions at:
> 
> http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images


> Then I dd'ed the resulting complete image onto an 8GB microSD card,
> which I then inserted into the microSD slot in the Cubox-I.  When I
> applied power, I got the attached log on the serial console.

Those sound like reasonable steps...

What's confusing is your screen logs shows a u-boot from bookworm/sid:

  U-Boot SPL 2022.04+dfsg-2+b1 (May 14 2022 - 21:25:25 +)

So either the images you downloaded were not the images you thought you
downloaded... or you saved the wrong screenlog file... or the bullseye
images contain u-boot from the wrong release... or somehow you're
loading u-boot from some other media, such as eMMC?

I actually need to reinstall a cuboxi4pro maybe by the end of the week,
so I will test it myself then.


live well,
  vagrant


signature.asc
Description: PGP signature

Re: failure trying to install bullseye on Cubox-i

[tomas]

On Sun, Jul 17, 2022 at 06:37:55PM -0700, Rick Thomas wrote:
> I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep around for 
> testing purposes.
> 
> I followed the instructions at:
> 
> http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images
> 
> Then I dd'ed the resulting complete image onto an 8GB microSD card, which I 
> then inserted into the microSD slot in the Cubox-I.  When I applied power, I 
> got the attached log on the serial console.

Disclaimer: I have no idea what a Cubox-i4Pro is, so take the
following with one or two fists of salt.

Going through the attached log, this calls my attention:

> MMC:   FSL_SDHC: 1, FSL_SDHC: 2^M
> Loading Environment from MMC... *** Warning - bad CRC, using default 
> environment^M

which seems to mean that the bootloader isn't finding what it
expects. This could be due to a bad MMC card, or to something
going wrong with the dd, or to the Cubox needing something
different than what you have got. Unless you are quite sure
about the third, I'd try to eliminate the first two ones.

Typically such an installer is a partitioned disk: if you insert
the card into your Linux box: can you see the partitions? Can
you mount them?

Then this:

> mmc1 is current device^M
> Card did not respond to voltage select! : -110^M
> CACHE: Misaligned operation at range [e59ff01c, e59ff91c]^M
> timeout exit!^M
> CACHE: Misaligned operation at range [e59ff01c, e59ff91c]^M
> timeout exit!^M

Are you sure your MMC card is working as it should? They are known
to be of... varying quality.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: failure trying to install bullseye on Cubox-i

[Rick Thomas]

On Sun, Jul 17, 2022, at 6:37 PM, Rick Thomas wrote:
> I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep 
> around for testing purposes.
>
> I followed the instructions at:
> 
> 
> http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images
>
> Then I dd'ed the resulting complete image onto an 8GB microSD card, 
> which I then inserted into the microSD slot in the Cubox-I.  When I 
> applied power, I got the attached log on the serial console.
>
> Does anyone know what I'm doing wrong?  Is this a bug in the installer? 
>  If so, what's the best way for me to volunteer to help as a tester in 
> debugging it.
>
> Rick
> Attachments:
> * screenlog

In case it helps, the two components I used in this experiment are:


http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/20210731+deb11u4/images/netboot/SD-card-images/firmware.MX6_Cubox-i.img.gz

and


http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/20210731+deb11u4/images/netboot/SD-card-images/partition.img.gz

On the web page, these files are dated 2022-07-05 15:57 .

Any clues are appreciated!
Rick

failure trying to install bullseye on Cubox-i

[Rick Thomas]

I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep around for 
testing purposes.

I followed the instructions at:

http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images

Then I dd'ed the resulting complete image onto an 8GB microSD card, which I 
then inserted into the microSD slot in the Cubox-I.  When I applied power, I 
got the attached log on the serial console.

Does anyone know what I'm doing wrong?  Is this a bug in the installer?  If so, 
what's the best way for me to volunteer to help as a tester in debugging it.

Rick

screenlog
Description: Binary data

Re: OT, Recommendation for low cost laptop

[Rick Thomas]

On Sun, Jul 17, 2022, at 1:59 PM, Charlie Gibbs wrote:
> On Sun Jul 17 09:16:57 2022 Dekks Herton  wrote:
>
>  > john doe  writes:
>  >
>  >> I'm comtemplating buying a Pinebook pro but I'm not sure if this is
>  >> better then buying a Windows laptop and putting linux on it.
>  >>
>  >> I'm looking for something cheap (max would be around 300 bucks),
>  >> do you have any suggestions/ideas?
>  >
>  > 2nd hand Thinkpad off ebay, craigslist etc, likely easy to upgrade and
>  > certainly straightforward to install linux.
>
> Another place to look is your local laptop store.  My current laptop,
> as well as its predecessor, are refurbished ThinkPads I bought there
> for about $300.  They run Linux just fine.

Or ask your neighbors.  Due to Covid, a lot of people are replacing their 
Windows or Mac machines so they can run Zoom and other "community building 
while isolated" apps.  Most of them don't bother with looking for a good 
trade-in deal, and have the old computer lying around doing nothing.  If you 
let it be known that you will take it of their hands, upgrade it to run modern 
software (like Linux) and make it available to charities in the area, often 
they will donate it to you for free.  

Anyway, that's how I do it...
Rick

Re: OT, Recommendation for low cost laptop

[Charlie Gibbs]

On Sun Jul 17 09:16:57 2022 Dekks Herton  wrote:

> john doe  writes:
>
>> I'm comtemplating buying a Pinebook pro but I'm not sure if this is
>> better then buying a Windows laptop and putting linux on it.
>>
>> I'm looking for something cheap (max would be around 300 bucks),
>> do you have any suggestions/ideas?
>
> 2nd hand Thinkpad off ebay, craigslist etc, likely easy to upgrade and
> certainly straightforward to install linux.

Another place to look is your local laptop store.  My current laptop,
as well as its predecessor, are refurbished ThinkPads I bought there
for about $300.  They run Linux just fine.

--
/~\  Charlie Gibbs  |  They don't understand Microsoft
\ /|  has stolen their car and parked
 X   I'm really at ac.dekanfrus |  a taxi in their driveway.
/ \  if you read it the right way.  |-- Mayayana

Re: Getting rid of backuppc password protection.

[Gary L. Roach]

On 7/17/22 2:07 AM, Nicolas George wrote:

Gary L. Roach (12022-07-16):

Some time ago I installed backuppc and then decided to not use it. Even
though I purged the program and made sure that I deleted all directories, I
still get a backuppc password request when starting any of my programs.
Anyone had this problem and if so, do you know how to get rid of it.

Does it happen when you run your programs from the command line?

If yes, then use strace to see how your command is redirected.

If no, then you need to investigate whatever you use to run the
programs.

Thanks for the reply. No the problem doesn't occur when starting a 
program from the command line. This finally lead me to two fixes. If you 
dig down deep enough on the desktop icon properties (application -> 
Advanced Options -> User) you can set the user to root. When this is 
done a request for a password is presented on startup. Apparently this 
was set by backuppc. I just unchecked the box and the problem is gone. I 
also found a way to bypass the security lock on Dolphin so that I can 
now use it on root files. Yes I know that is not safe but my system is 
single user, in my home office and really doesn't include files that 
would be a disaster to loose. Because of the work I do I am constantly 
working with files that are owned by root and the inability to use 
Dolphin has been a great pain.


Thanks again

Gary R

Re: Processors older than Intel Pentium 4

[Tim Woodall]

On Sat, 16 Jul 2022, Tim Woodall wrote:


On Sat, 16 Jul 2022, Timothy M Butterworth wrote:


Is anyone running Debian 11 on a processor older than Pentium 4? I ask
because I would like to bump 32 bit OS support from i386 (1985) to i686
Pentium 4 and newer.

Thanks



I think I'm running it on an eeepc. I don't know what processor that
corresponds to but I can check tomorrow (and whether I actually upgraded
it from buster yet)


Yes, it is running bullseye.

tim@eeepc:~$ cat /proc/cpuinfo 
processor   : 0

vendor_id   : GenuineIntel
cpu family  : 6
model   : 13
model name  : Intel(R) Celeron(R) M processor  900MHz
stepping: 8
microcode   : 0x20
cpu MHz : 630.059
cache size  : 512 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx bts cpuid pti
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit
bogomips: 1260.11
clflush size: 64
cache_alignment : 64
address sizes   : 32 bits physical, 32 bits virtual

Re: Processors older than Intel Pentium 4

[gene heskett]

On 7/17/22 10:41, Stefan Monnier wrote:

Greg Wooledge [2022-07-17 08:25:24] wrote:

On Sun, Jul 17, 2022 at 08:35:33AM +, Marco wrote:

But why the packages are still named i386 instead of i686?

Because changing the name of the architecture would be such a massive
pain in the ass, and would probably break *so* many things, that it's
simply not worthwhile.

The 80386 processor was the processor that introduced that new
instruction set, quite different from its predecessors (like 80286), so
much so that it needed a different mode, just like the amd64 is
different enough that it requires a different mode.

Subsequent processors introduced various extensions (addition of CMOVE,
MMX, SSE, ...) which are incremental changes which don't break
compatibility with previously existing code, so I think it makes a lot
of sense to still call it the "i386 instruction set".

Also, as seen here, there is no such thing as "the i686".  For some
people (like me), this is a "name" that was given to the Pentium Pro
(because after 286, 386, 486, when Intel decided to switch gear and
call the next one "Pentium" people couldn't resist thinking about it as
"586" and hence "686" for the next one), but after that the "number
name" faded into history (the "786" name was never really used to refer
to one of the subsequent CPUs).

According to
https://lists.debian.org/debian-devel-announce/2016/05/msg1.html it
seems that Debian uses "i686" to refer to the ISA supported by the
Pentium Pro.

Another thing that should not be forgotten is that the family of processors
vs the ability to make use of firmware patches to fix bugs took a hit since
family ID's of $0F and below could not be fixed with microcode. And many
of them had a halt bug that if encountered, had no recovery except a full
power down restart.  The use of microcode to fix such was only in family $10
and higher. I think most of those have been thrown in the dumpster by now,
but be aware they could still exist.


 Stefan

.



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, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Debian 9 cron = sounds are ok : Debian 11 cron no sound

[Roger Price]

On Sun, 17 Jul 2022, Lee wrote:

On 7/17/22, The Wanderer  wrote:

I don't use cron to play sounds, so I can't speak to this directly,
but...

While this may turn out in the end to be pure FUD, when I hear about
things which work properly when run by hand but not when run
automatically on a modern Debian system, my first suspicion is always
that the culprit is the systemd / logind / whatever-it-is "user session"
concept.


I don't know about systemd, but cron sets just a very few environment
vars (interestingly enough, you _do_ get /etc/environment processed).
I'd guess the problem with "works when run interactively but fails
when run from cron" is because most all of the sh setup is skipped for
things started by cron.


I added some debugging commands to the bark.sh script which produces the sounds 
to try to see more clearly what is happening.


When bark.sh is called from the command line I hear the barking and command
 pactl list short sinks   reports:

 1  alsa_output.pci-_00_1b.0.analog-stereo  module-alsa-card.c  
s16le 2ch 44100Hz   RUNNING
 2  alsa_output.pci-_23_00.0.analog-stereo  module-alsa-card.c  
s16le 2ch 44100Hz   SUSPENDED
 48 alsa_output.pci-_03_00.1.hdmi-stereomodule-alsa-card.c  
s16le 2ch 44100Hz   SUSPENDED

but when bark.sh is called by a crontab entry, the same command reports:
 Connection failure: Connection refused

When bark.sh is called from cron, the command pacmd list-sinks also reports:
 No PulseAudio daemon running, or not running as session daemon.

Following https://wiki.archlinux.org/title/PulseAudio/Examples ,
I am currently looking at installing a file ~/.config/pulse/default.pa

 .include /etc/pulse/default.pa
 set-default-sink alsa_output.pci-_00_1b.0.analog-stereo

but its getting hotter in my place and I work slowly.  Roger

Re: Debian 9 cron = sounds are ok : Debian 11 cron no sound

[Dan Ritter]

Roger Price wrote: 
> On Sat, 16 Jul 2022, Lee wrote:
> 
> > I don't have play, so I tried aplay .. and it works, even if I'm
> > logged out, even if someone else is logged in.
> > 
> > ## run the script every minute
> > 
> > $ crontab -l | tail -3
> > # m h  dom mon dow   command
> >  * *   *   *   */home/lee/bin/neener.sh
> > 
> > ## which plays a .wav and an .au file
> > 
> > $ cat ~/bin/neener.sh
> > #!/bin/sh
> > /usr/bin/aplay -q $HOME/Sounds/Old/NEENER.WAV
> > sleep 0.25
> > /usr/bin/aplay -q $HOME/Sounds/SunOS/busy.au
> 
> I get the following error message from aplay:
> 
>  ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave
>  aplay: main:830: audio open error: Device or resource busy
> 
> and a different message from play:
> 
>  ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave
>  /usr/bin/play FAIL sox: Sorry, there is no default audio device configured

I'm going to guess that:

- you normally have pulseaudio running
- the commands work when systemd has set up a pulseaudio daemon
  for you
- the commands don't work when pulseaudio has control of the
  audio system but the cron job does not know how to reach it via
  a pulseaudio socket

Perhaps putting pulseaudio --start at the beginning of your
script and pulseaudio --kill at the end will fix this.

-dsr-

Re: Debian 9 cron = sounds are ok : Debian 11 cron no sound

[Lee]

On 7/17/22, The Wanderer  wrote:
> On 2022-07-16 at 04:47, Roger Price wrote:
>
>> People occasionally have a cron job emit some sound each hour.  On my
>> Debian 9
>> machine I hear Biff [1] barking. In /etc/crontab I have an entry to call a
>>
>> script bark.sh which does the barking. Typically
>>
>>   0,1 0,12 * * * rprice full-path-to/bark.sh 12 2>>&1
>>
>> where bark.sh is a Bash script which calls /usr/bin/play to play a .au
>> file.
>>
>> This ran for years with Debian 9. I upgrade to Debian 11 and hear nothing.
>>  The
>> usual advice is
>>   (a) in /etc/crontab export XDG_RUNTIME_DIR=/run/user/1000
>>   (b) play the sound from a script.
>>
>> But that doesn't work with Debian 11. Does any reader of this list have
>> sound
>> coming from a Debian 11 cron job?  If so, how is it done?
>
> I don't use cron to play sounds, so I can't speak to this directly,
> but...
>
> While this may turn out in the end to be pure FUD, when I hear about
> things which work properly when run by hand but not when run
> automatically on a modern Debian system, my first suspicion is always
> that the culprit is the systemd / logind / whatever-it-is "user session"
> concept.

I don't know about systemd, but cron sets just a very few environment
vars (interestingly enough, you _do_ get /etc/environment processed).
I'd guess the problem with "works when run interactively but fails
when run from cron" is because most all of the sh setup is skipped for
things started by cron.

Lee

Re: Debian 9 cron = sounds are ok : Debian 11 cron no sound

[The Wanderer]

On 2022-07-16 at 04:47, Roger Price wrote:

> People occasionally have a cron job emit some sound each hour.  On my Debian 
> 9 
> machine I hear Biff [1] barking. In /etc/crontab I have an entry to call a 
> script bark.sh which does the barking. Typically
> 
>   0,1 0,12 * * * rprice full-path-to/bark.sh 12 2>>&1
> 
> where bark.sh is a Bash script which calls /usr/bin/play to play a .au file.
> 
> This ran for years with Debian 9. I upgrade to Debian 11 and hear nothing.  
> The 
> usual advice is
>   (a) in /etc/crontab export XDG_RUNTIME_DIR=/run/user/1000
>   (b) play the sound from a script.
> 
> But that doesn't work with Debian 11. Does any reader of this list have sound 
> coming from a Debian 11 cron job?  If so, how is it done?

I don't use cron to play sounds, so I can't speak to this directly,
but...

While this may turn out in the end to be pure FUD, when I hear about
things which work properly when run by hand but not when run
automatically on a modern Debian system, my first suspicion is always
that the culprit is the systemd / logind / whatever-it-is "user session"
concept.

In this case, my guess would be that there's a session being set up when
you log in which puts in place the necessary configuration, access
permissions, or the like to make it possible for play to do what you
need it to do - but for a command invoked from the crontab, no such
session has been set up (or whatever session is set up doesn't supply
the same configuration), so play can't produce any audible output.

Another thing I don't do is run systemd, so I'm not in a position to
even figure out what you'd do to verify that, never mind test
possibilities for myself. Again, this might be a complete false trail
and nothing but unfounded FUD, but it *might* be worth checking out.

-- 
   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: Debian 9 cron = sounds are ok : Debian 11 cron no sound

[Lee]

On 7/16/22, Roger Price wrote:
> On Sat, 16 Jul 2022, Lee wrote:
>
>> I don't have play, so I tried aplay .. and it works, even if I'm
>> logged out, even if someone else is logged in.
>>
>> ## run the script every minute
>>
>> $ crontab -l | tail -3
>> # m h  dom mon dow   command
>>  * *   *   *   */home/lee/bin/neener.sh
>>
>> ## which plays a .wav and an .au file
>>
>> $ cat ~/bin/neener.sh
>> #!/bin/sh
>> /usr/bin/aplay -q $HOME/Sounds/Old/NEENER.WAV
>> sleep 0.25
>> /usr/bin/aplay -q $HOME/Sounds/SunOS/busy.au
>
> I get the following error message from aplay:
>
>   ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave
>   aplay: main:830: audio open error: Device or resource busy
>
> and a different message from play:
>
>   ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave
>   /usr/bin/play FAIL sox: Sorry, there is no default audio device
> configured
>
> I'm wondering what causes this. Do you have any specific environment
> variable
> set which defines a default audio device?

Nope.  Audio has always just worked; I never had to do anything
special or extra to get it working

Lee

Re: Processors older than Intel Pentium 4

[Greg Wooledge]

On Sun, Jul 17, 2022 at 08:35:33AM +, Marco wrote:
> But why the packages are still named i386 instead of i686?

Because changing the name of the architecture would be such a massive
pain in the ass, and would probably break *so* many things, that it's
simply not worthwhile.

how to check compatibility of (any party) package file? (and more)

[Patrice Duroux]

Hi,

My purpose is multiple here.

First, I am trying to build a tool[1] to check a given package file (ie a
.deb, whatever its origin) for the compatibility with Debian distribution
versions, including if it may be required to have more sections (contrib,
non-free) or a backports pool.
I am able to extract some field values (package, version, architecture,
depends) and check the compatibility of some of the values with my current
host system (using . deb-dpkg and dpkg).
I am currently stuck to check the depends value.
Is there any facility for this: 1. on my local system (using some
commands)? 2. on all the Debian systems (using rmadison or some ad-hock UDD
queries)?
Check the value as a whole or iterate all its elements, deal with the
version constraint, etc..

Second, would it be useful to maintain a website (database + webui) where
to identify those package files not part of a known (Debian or famous 3rd)
repository.
I am thinking of this for a better / improved deb-get[2] project and a
robot to maintain the database content.

Third, expose the first tool as a webservice where to post a .deb file and
get all the Debian distribution versions it is compatible with? Or maybe
get the corresponding apt source configuration required (ie. the context)
required to be able to install the package?
Is piuparts able to determine or setup an adequate Debian container such to
install a given package?

Thanks,
Patrice

[1] as simple as a shell script if possible
[2] https://github.com/wimpysworld/deb-get

Re: OT, Recommendation for low cost laptop

[Dekks Herton]

john doe  writes:


> I'm comtemplating buying a Pinebook pro but I'm not sure if this is
> better then buying a Windows laptop and putting linux on it.
>
> I'm looking for something cheap (max would be around 300 bucks), do you
> have any suggestions/ideas?

2nd hand Thinkpad off ebay, craigslist etc, likely easy to upgrade and
certainly straightforward to install linux.

Regards.

Re: Getting rid of backuppc password protection.

[Nicolas George]

Gary L. Roach (12022-07-16):
> Some time ago I installed backuppc and then decided to not use it. Even
> though I purged the program and made sure that I deleted all directories, I
> still get a backuppc password request when starting any of my programs.
> Anyone had this problem and if so, do you know how to get rid of it.

Does it happen when you run your programs from the command line?

If yes, then use strace to see how your command is redirected.

If no, then you need to investigate whatever you use to run the
programs.

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: Getting rid of backuppc password protection.

[Cindy Sue Causey]

On 7/17/22, David Wright  wrote:
> On Sat 16 Jul 2022 at 19:13:25 (-0700), Gary L. Roach wrote:
>> I used apt install to install the standard debian package and used apt
>> purge to uninstall. Further, I used rm -r to clean up the directories
>> that were left. If it helps:
>>
>
> Were I to install backuppc, 21 other packages would arrive with it
> (including Recommends). Did you purge all those too?


Another route I might try if I'd been purging some and "rm -r" others
is to maybe reinstall then "apt get autoremove backuppc". That very
nicely picks out everything that came along with and is no longer
needed if backuppc is removed. I check autoremove's proposed list
carefully each time because some packages will try to remove the
desktop environment, for example.

Using autoremove comes from actually reading my terminal's entire
output when apt-get shows off a list of packages that are no longer
needed after upgrades make them obsolete. :)

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: 32 bit thin client

[Marco]

Am Sun, 17 Jul 2022 07:07:28 +0100
schrieb David :

> I am running Debian 11 on a 32 bit thin client. This thin client is
> running headless.
> 
> I am trying to add either ssmtp or msmtp, but these appear not to be
> in the repositories.
> 
> I've tried adding ssmtp, downloaded from the Debian web site, and
> installing it with dpkg. This fails due to missing dependences, which
> I don't appear to resolve.

Please show the content of /etc/apt/sources.list and the output of apt
update.
Additionally, you can use sendmail, I can confirm that this works fine.
:-)

Re: Processors older than Intel Pentium 4

[didier gaumet]

Le dimanche 17 juillet 2022 à 07:40:05 UTC+2, Timothy M Butterworth a écrit :
> On Sun, Jul 17, 2022 at 12:30 AM Marco  wrote:
> Am Sat, 16 Jul 2022 11:26:44 -0400
> schrieb Timothy M Butterworth :
> 
> > Is anyone running Debian 11 on a processor older than Pentium 4? I ask
> > because I would like to bump 32 bit OS support from i386 (1985) to
> > i686 Pentium 4 and newer.
> 
> It would be interesting what the benefit of that is. You may compile
> amd64 packages with support for SSE, SSE2, etc., this won't break
> something, but for i386 (only a small amount of computers really needs
> that) this will make many of the current usages of i386 impossible.
> All thanks for the responses but the situation is mute. Debian already 
> migrated to i686 as the minimum supported version a few years ago. i686 
> supports Pentium 3 which is the oldest processor in use on this thread. Some 
> internet sites say that i686 is Pentium 4 and later others say that it is 
> Pentium 2 or later. Others say that i686 is Pentium Pro version 2 and later. 
> If it is indeed Pentium Pro and later then a lot of older processors are 
> still supported: Pentium 2, Pentium 3, Pentium M, Celeron, Pentium 4 etc.
> -- 
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
> ⠈⠳⣄⠀⠀

Hello,

Wikipedia states that the P6 (aka i686) line starts with the Pentium Pro:
https://en.wikipedia.org/wiki/List_of_Intel_CPU_microarchitectures#32-bit_(IA-32)
https://en.wikipedia.org/wiki/P6_(microarchitecture)

That is confirmed by Intel own doc (Intel® 64 and IA-32 Architectures
Software Developer’s Manual):
https://d2pgu9s4sfmw1s.cloudfront.net/UAM/Prod/Done/a062E1UMCFmQAP/6d880c8b-2e3a-44ff-9915-0eb627584855?Expires=1658045234&Key-Pair-Id=APKAJKRNIMMSNYXST6UA&Signature=Nk6FAwzRAhgXWfEkT7PHxHckS4alDVsDYd5i7kUPdkiRAyVCiPBycIPgnYYPoWXEgVaT3oURcGyVj-j1mDT8TcfschC1Hsj9S6sxCQ0U~juM1Qr3g5KqedfMSkZCvps2nI5xu4PupAU83d6HrWXq4cXVAQIO79o3IROj7YeWYZjV6EwhtajcM55xoFUN3Rh8rYuGBr59wxm13J~FZLhoZHzt23Gis5oEMDUDGIPyh240tFUI9uVsc2y7mD9mhL4mEk5e2X00lYemgrDyJmhCzebVinNSwByCs09qQflEqlRIVAzmQVE57POL3opkYvQQEWHYsUzflX9yXKNV5J9~Mw__

Re: Processors older than Intel Pentium 4

[Marco]

Am Sun, 17 Jul 2022 01:34:07 -0400
schrieb Timothy M Butterworth :

> All thanks for the responses but the situation is mute. Debian
> already migrated to i686 as the minimum supported version a few years
> ago. i686 supports Pentium 3 which is the oldest processor in use on
> this thread. Some internet sites say that i686 is Pentium 4 and later
> others say that it is Pentium 2 or later. Others say that i686 is
> Pentium Pro version 2 and later. If it is indeed Pentium Pro and
> later then a lot of older processors are still supported: Pentium 2,
> Pentium 3, Pentium M, Celeron, Pentium 4 etc.

But why the packages are still named i386 instead of i686?
Pentium Pro makes sense. The follower of the 485 was the Pentium (Penta
for 5 in Greek) internally named 586. The successor of that was the
Pentium Pro (686).
https://www.pcmag.com/encyclopedia/term/686

The change of newer processors is that additional instructions like
MMX, SSE (Pentium 3/Athlon XP), SSE2 (Pentium 4 Willamette/Northwood)
and SSE3 (P4 Prescott) are supported.
Enforcing SSE could be an option (only Pentium 2 and Athlon (K7, without
XP) couldn't be used anymore. Although, both can still be used today
(if somebody has a Pentium 2 I might test it :-)).

Re: Sid installation fails - No kernel modules found

[Piscium]

On Sat, 16 Jul 2022 at 23:41, Brian  wrote:

> But you did not download and try the one I suggested? Therefore, you
> are working blindfolded. It is dated 2022-0 7-05. The archive modules
> may match the d-i kernel.

I successfully installed Sid using the Bullseye mini.iso that I
downloaded from the UK mirror. It has the same timestamp  as the file
you suggested from the Netherlands mirror.

I filed a bug report, hopefully someone will fix it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015172

Thanks for your help.

Re: 32 bit thin client

[David]

On Sun, 17 Jul 2022 at 16:25, David  wrote:

> I am running Debian 11 on a 32 bit thin client. This thin client is
> running headless.

Hello. I'm unsure exactly what the above means in practice.
Are you attempting to install onto the client or onto the server?

> I am trying to add either ssmtp or msmtp, but these appear not to be in
> the repositories.

This is what I see on a standard 32bit installation here.

root@kapop:~# cat /etc/debian_version
11.4

root@kapop:~# uname -a
Linux kapop 5.10.0-16-686 #1 SMP Debian 5.10.127-1 (2022-06-30) i686 GNU/Linux

root@kapop:~# apt update

root@kapop:~# apt list msmtp ssmtp
Listing... Done
msmtp/stable 1.8.11-2.1 i386
ssmtp/stable 2.64-10 i386

So 32bit versions of msmtp and ssmtp are definitely available
in the repository.

Can you show the output you get for this command?
  cat /etc/apt/sources.list

> I've tried adding ssmtp, downloaded from the Debian web site, and
> installing it with dpkg. This fails due to missing dependences, which I
> don't appear to resolve.

I suggest getting apt working will be a better approach.
Anyway, that's all the advice I can give you and hopefully someone
more familiar with your situation will assist you.