Attempt to use the chipset NVIDIA Corp MCP79 [GeForce 8200M G] (rev b1) (prog-if 00 [VGA controller]) with Dix. Teacher-Guide, Mr. Felix Miata

[Susmita/Rajib]

Changing the subject Line:
From:
Can the latest stable Debian be compelled to run in vesa mode, rather
than the motherboard graphics card, if the said card doesn't have
drivers available? How?
Last thread:  https://lists.debian.org/debian-user/2021/04/msg00534.html

To the present one, to maintain relevance and for other support
seekers subsequently.


On 19/04/2021, Felix Miata  wrote:
[...]
>   
> In order to use the Modesetting DIX driver with GeForce 8200M G [MCP79] it
> should
> be entirely sufficient as follows:
>
> 1-eradicate/purge/uninstall/delete all traces of NVidia's proprietary
> drivers
> 2-purge xserver-xorg-video-nouveau
> 3-reboot
>
> Purging xserver-xorg-video-nouveau is not necessary, just simpler. It may
> be
> necessary to configure specially in /etc/X11/ to not use the Nouveau DDX if
> it is
> installed.
>
> Note that #2 above may involve reinstalling one or more libraries required
> for
> utilizing FOSS drivers with any model GeForce.
[...]

I have already downloaded the ISO, firmware-10.9.0-amd64-netinst.iso,
from the link:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/firmware-10.9.0-amd64-netinst.iso

I will dd the ISO to a flash drive and clean reinstall the OS. Have
saved the grub lines for Knoppix too.

Shall proceed with your later steps, whenever required.


> A visit to the following may prove fruitful moving forward:
> 
[...]

But the website requires creation of an account in order for me to
read the post. I wouldn't like to create an account just for this
purpose, unless required. Could the essential steps be posted to this
thread please?

Best.
Rajib

Re: GRUB no inicia sistema antiguo (era: debian 11 kde primer arranque)

[Camaleón]

El 2021-04-18 a las 15:12 -0300, Marcelo Giordano escribió:

> > > > Ejecuta como súperusuario «fstab -l» y manda la salida a la lista.
> 
> root@Marcelo:/home/marcelo# fstab -l
> bash: fstab: orden no encontrada
> 
> Que raro esto, no anda nada.

No, es un error de transcripción mío :-) 
La orden no era esa, sino «fdisk -l».

> Antes de intentar reinstalar el paquete, dinos qué te devuelve estas
> > órdenes (la primera como súperusuario):
> > 
> > apt-get -f install
> > dpkg -l | grep util-linux
> > 
> 
> root@Marcelo:/home/marcelo# apt-get -f install
> Leyendo lista de paquetes... Hecho
> Creando árbol de dependencias... Hecho
> Leyendo la información de estado... Hecho
> El paquete indicado a continuación se instaló de forma automática y ya no es
> necesario.
>   linux-image-5.9.0-4-amd64

No te saca ningún error en los paquetes.
 
> root@Marcelo:/home/marcelo# dpkg -l | grep util-linux
> ii  util-linux2.36.1-7
>  amd64miscellaneous system utilities
> ii  util-linux-locales2.36.1-7
>  all  locales files for util-linux

Y «util-linux», que contiene binario blkid está instalado. Pues eso sí 
es extraño... búscalo con «whereis blkid» a ver qué te dice y si te lo 
localiza.

Saludos, 

-- 
Camaleón 

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

[Felix Miata]

Susmita/Rajib composed on 2021-04-19 10:30 (UTC+0530):

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

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

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

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



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

tasks=standard base-installer/install-recommends=false
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

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

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

[Felix Miata]

Susmita/Rajib composed on 2021-04-19 8:35 (UTC+05300):

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

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

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

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

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

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

A visit to the following may prove fruitful moving forward:

-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

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

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

[Susmita/Rajib]

On Mon, 19 Apr 2021 00:12:29 -0400, Felix Miata  wrote:
Ref: https://lists.debian.org/debian-user/2021/04/msg00530.html

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

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

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

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

Best.
Rajib

HP zBook G5 issues

[Tom Dial]

I have a Hewlett Packard zBook G5, with a generally successful Debian
with Gnome install, initially 10.x (as current in January 2020) and
recently upgraded to bullseye.

The installation is vanilla except that:

a. It is installed on ZFS (including /)
b. It has the nVidia proprietary driver and xorg (Nouveau was very sluggish)
c. It is dual boot, with Windows on one NVMe device and Debian on
another. Grub is installed on the Debian device and handles both Linux
and Windows well.
d. Several not-debian programs are installed on /opt and probably not
relevant to any of the issues described below.

There were several relatively low-impact but annoying issues, most of
which evaporated with no effort beyond regular software maintenance. The
one that remains is:

Keyboard: the keyboard function keys to control screen brightness that
(usually) do not work correctly but, instead, operate identically to the
microphone on/off function key, including producing the same scan and
key codes (as reported by showkey -s or showkey -k, on either a gnome or
console terminal). Output from showkey -s 0x5a 0xda, and scancode -k
reports keycode 190 press keycode 190 release. Irritatingly, on occasion
they work correctly to control brightness. When this happens it may
persist over several reboots.

The brightness control in the Gnome settings power tab works as
expected, and the buttons work normally when Windows is in control.

2. From time to time, while running, the screen freezes: keyboard input
and mouse buttons do not work, although the pointer moves appropriately.
Switching to a virtual console and back almost always corrects the problem.

Suggestions on any of these defects will be gratefully received. The
zBook is a very nice machine in most respects. I'm posting to both
debian-laptop and debian-users since it is not whether this is
exclusively a laptop type problem and apologize if that is inappropriate.

Regards,

Tom Dial

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

[Susmita/Rajib]

Would the setps as described in the following link be necessary?
http://www.linuxfromscratch.org/blfs/view/svn/x/xorg-server.html

---
Installation of Xorg Server

Install the server by running the following commands:

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

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

Now as the root user:

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

Command Explanations

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

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

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

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

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

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

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

Best,
Rajib

Re: [?]List of Best Debian-approved laptops in India

[Felix Miata]

Susmita/Rajib composed on 2021-04-19 08:34 (UTC+0530):

> On Sun, 18 Apr 2021 21:52:25 -0400, Felix Miata wrote:

> Can I make a request please? Could I send you a reply from the other thread 
> at:
> https://lists.debian.org/debian-user/2021/04/msg00512.html

Unless and until all traces of NVidia's driver installation and associated
configuration changes have been purged from your machine, I can be no help 
except
WRT eradicating them. Even in that regard others know better than me how to
proceed. AFAICT, whatever NVidia driver installation does eliminates any chance 
to
make FOSS drivers work acceptably.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

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

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

[Susmita/Rajib]

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

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

Much appreciated.

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

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

Best.
Rajib

Re: [?]List of Best Debian-approved laptops in India

[Susmita/Rajib]

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

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

Much appreciated.

Can I make a request please? Could I send you a reply from the other thread at:
https://lists.debian.org/debian-user/2021/04/msg00512.html
Subject:
Can the latest stable Debian be compelled to run in vesa mode, rather
than the motherboard graphics card, if the said card doesn't have
drivers available? How?

...as to address some specific questions of Dr./Mr. Cater, I created
that thread.

I am really interested as I find my problems getting solved.

Best.
Rajib

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

[Susmita/Rajib]

On Sun, 18 Apr 2021 17:56:46 +, "Andrew M.A. Cater"
 wrote:
[QUOTE]
[...]
I followed through the screenshots you provided.
[...]
You can't ignore the source - you may have to apply it to a kernel.
[/QUOTE]


Okay, learnt. Thank you.


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

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

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



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

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


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

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

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


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

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

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

Hope this helps, all the best,

Andy C.
[/QUOTE]

Thank you, Dr. Cater.

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

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

Best.
Rajib

Re: [?]List of Best Debian-approved laptops in India

[Susmita/Rajib]

On Sun, 18 Apr 2021 17:56:46 +, "Andrew M.A. Cater"
 wrote:
[QUOTE]
[...]
I followed through the screenshots you provided.
[...]
You can't ignore the source - you may have to apply it to a kernel.
[/QUOTE]


Okay, learnt. Thank you.


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

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

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



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

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


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

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

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


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

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

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

Hope this helps, all the best,

Andy C.
[/QUOTE]

Thank you, Dr. Cater.

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

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

Best.
Rajib

Re: scanner recommendation

[Gregory Seidman]

https://www.usa.canon.com/internet/portal/us/home/products/details/scanners/photo-scanner/canoscan-lide-110

It's a cheap workhorse. I haven't tried it with Linux but it doesn't
require any special software or drivers on macOS, which makes me think it
is entirely open standard.

--Gregory

On Sun, Apr 18, 2021 at 03:57:30PM -0400, Default User wrote:
> Hi!
> 
> It may be time for a new scanner.
> 
> For years I have used a Visioneer OneTouch 7100 usb flatbed scanner on
> various x86 computers running various versions of Debian and
> simple-scan.
> 
> Currently:
> Debian Unstable (updated, of course)
> Linux 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 (2021-04-09) x86_64 GNU/Linux
> Cinnamon 4.8.6-2
> Dell Inspiron 3542 (laptop, circa 2015), 64-bit
> Scanner software: simple-scan, from Debian Unstable repositories
> Use case: light duty home use.
> 
> For years it worked "okay".  But it suddenly started producing scans
> with a narrow pink stripe down the left side of the scan image
> produced.
> 
> I tried installing xsane (too complicated for me), which I did not
> configure at all.  And if I just clicked the scan button in xsane it
> would "dim out" and then do nothing.  As a bonus, simple-scan then no
> longer worked; upon clicking scan in simple-scan it would just do
> nothing, with a rotating "activity busy" circle displaying
> indefinitely.
> 
> So I uninstalled (purged) both xsane and simple-scan, re-installed
> simple-scan, then rebooted.
> Simple-scan now "works", but still produces the pink stripe down the
> image left side, just as before.
> 
> : (
> 
> Note: the scanner is (about) 20 years, so no parts or service
> available from Visioneer.
> 
> : (
> 
> So . . .
> Can anyone recommend a good replacement scanner?
> 
> I am really hoping to get something that works "out of the box", with
> little or no configuration, etc.
> 
> 

Re: which mixer can show sound volume as colorful bar

[Dan Ritter]

Long Wind wrote: 
> it  changes as sound volume change
> i use alsa, not pulseaudioThanks!

alsamixer

-dsr-

Re: [?]List of Best Debian-approved laptops in India

[Susmita/Rajib]

Perhaps these lines in the post:
http://forums.debian.net/viewtopic.php?f=10=149280 were missed.

[quote="bkpsusmitaa"]Have been referring to the page:
https://wiki.debian.org/InstallingDebianOn#OfficialDocumentation
[...]
Indian vendors have been contacted by email/SMS or called over phone.
Remain Incommunicado.
https://www.debian.org/distrib/pre-installed#in
[/quote]

Best,
Rajib

Re: [?]List of Best Debian-approved laptops in India

[Felix Miata]

Susmita/Rajib composed on 2021-04-18 20:01 (UTC+0530):

> Vesa doesn't work in Debian Buster 10.8, by my blocking Nouveau
> through grub.cfg that halts the nvidia graphics chip. The string
> 'xmodule=vesa' doesn't work either.

> Debian nvidia drivers, as ever, fails to install.

> The nvidia drivers 64bit downloaded from nvidia website don't work.
> The problematic Hardware:
> (1) VGA compatible controller : NVIDIA Corporation MCP79 [GeForce
> 8200M G] (rev b1) (prog-if 00 [VGA controller])   
> 
I have a slightly older version of what you have:
# inxi -GISay
System:
  Host: mcp61 Kernel: 4.19.0-16-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
...
  Desktop: Trinity R14.0.9 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 vt: 7
  dm: TDM Distro: Debian GNU/Linux 10 (buster)
Graphics:
  Device-1: NVIDIA C61 [GeForce 6150SE nForce 430] vendor: Micro-Star MSI
  driver: nouveau v: kernel bus-ID: 00:0d.0 chip-ID: 10de:03d0 class-ID: 0300
  Display: x11 server: X.Org 1.20.4 driver: loaded: modesetting
  unloaded: fbdev,vesa alternate: nouveau,nv display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1680x1050 s-dpi: 108 s-size: 395x246mm (15.6x9.7")
  s-diag: 465mm (18.3")
  Monitor-1: VGA-1 res: 1680x1050 hz: 60 dpi: 90 size: 474x296mm (18.7x11.7")
  diag: 559mm (22")
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
  compat-v: 3.1 direct render: Yes
Info:...Shell: Bash v: 5.0.3 running-in: konsole inxi: 3.3.04

As above indicated, it works with Debian 10, using the FOSS default X driver
(Modesetting DIX), along with the Nouveau kernel driver it depends on. No
proprietary NVidia or other non-Debian software is required for competent Xorg
operation. I have other NVidia GPUs in other PCs, all newer than yours, and all
using the very same modesetting DIX driver.

No one wants the dismal performance of the VESA driver except for 
troubleshooting
purposes.

The Nouveau DDX driver is an old technology alternative to the Modesetting DIX
that may or may not do any better on old NVidia IGPs like ours, which I find
unnecessary.

For GUI mode installation purposes, it's possible you might need a kernel 
command
line option "nomodeset", intended mainly for troubleshooting, but scant few need
it once Debian is installed.
-- 
Evolution as taught in public schools, like religion,
is based on faith, not on science.

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

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

looks like I need an hid interface

[Gene Heskett]

Greetings all;

I am trying to install a BLTouch kit in an Ender-3 3d printer.

The BLTouch is a gismo that touches the printers bed and records for 
later correction, any errors in the bed leveling, a very important 
item in a 3d printer.

This kit has a very sparsely described installation proceedure which 
includes a usb to hid/spi interface that plugs into a 6 pin interface 
socket on the printers control board. With only a 2 foot cable. :(

Its also written assuming a windows computer is available. Which there 
is not at this linux only location.


dmesg reports it like this on a stretch machine.

[1543461.117873] snd_hda_codec_hdmi hdaudioC0D2: HDMI: pin nid 7 not registered
[1543491.958435] usb 1-12.4.1.3: new low-speed USB device number 81 using 
xhci_hcd
[1543492.184129] usb 1-12.4.1.3: New USB device found, idVendor=03eb, 
idProduct=c8b4, bcdDevice= 1.00
[1543492.184136] usb 1-12.4.1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[1543492.184140] usb 1-12.4.1.3: Product: USBHID
[1543492.184143] usb 1-12.4.1.3: Manufacturer: zhifengsoft

And duplicates this on a buster machine except for the obvious changes 
in the usb bus address.  

The windows .exe program used to run this thing which is called a 
burner, is "progisp.exe".

It looks as if dfu-programmer might work, but I just went to a buster 
machine and installed dfu-* but the --targets listing output does not 
include this particular ATmega1284p chip.

Is there a newer version of dfu-programmer that does work with this
programmer and chip?  Or do I have to round up a windoze box and hope
it comes with a recent copy of progisp.exe?

Thanks all.

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: Wi-fi imbutido não encontra nenhuma rede

[Leonardo de Araújo Augusto]

Para registro, também tentei instalar um driver alternativo que encontrei
no github: https://github.com/FreedomBen/rtl8188ce-linux-driver

Nenhuma diferença aparente.


On Sun, 18 Apr 2021 at 17:52, Leonardo de Araújo Augusto <
leonardodearaujoaugu...@gmail.com> wrote:

> Gente, no link do hw-probe do email original (e no resultado do inxi) é
> possível notar que o driver relevante está instalado e carregado.
>
> cynthia@cy:~$ inxi -n
>>
>> Network:
>>
>>   Device-1: Realtek RTL8188CE 802.11b/g/n WiFi *Adapter driver:
>> rtl8192ce *
>>
>>   IF: wlp1s0 state: down mac: 9a:53:9b:7a:84:35
>>
>>   Device-2: JMicron JMC250 PCI Express Gigabit Ethernet driver: jme
>>
>>   IF: enp2s0f5 state: down mac: 80:ee:73:79:ec:99
>>
>>   IF-ID-1: usb0 state: unknown speed: N/A duplex: N/A mac:
>> ae:27:3e:fe:26:72
>>
>>
> Já tentei inclusive utilizar o ndiswrapper para usar o driver windows que
> sei que funciona (uma vez que a máquina rodava windows e o wifi era
> funcional) e não deu certo.
>
> Essa placa é, em tese, suportada pelo kernel upstream sem a necessidade de
> firmware não-livre, e de fato desde a instalação o Debian a reconhece, só
> não consegue fazer nada com ela.
>
> Obrigado,
>
>
>
>

Re: Wi-fi imbutido não encontra nenhuma rede

[Leonardo de Araújo Augusto]

Gente, no link do hw-probe do email original (e no resultado do inxi) é
possível notar que o driver relevante está instalado e carregado.

cynthia@cy:~$ inxi -n
>
> Network:
>
>   Device-1: Realtek RTL8188CE 802.11b/g/n WiFi *Adapter driver: rtl8192ce
> *
>
>   IF: wlp1s0 state: down mac: 9a:53:9b:7a:84:35
>
>   Device-2: JMicron JMC250 PCI Express Gigabit Ethernet driver: jme
>
>   IF: enp2s0f5 state: down mac: 80:ee:73:79:ec:99
>
>   IF-ID-1: usb0 state: unknown speed: N/A duplex: N/A mac:
> ae:27:3e:fe:26:72
>
>
Já tentei inclusive utilizar o ndiswrapper para usar o driver windows que
sei que funciona (uma vez que a máquina rodava windows e o wifi era
funcional) e não deu certo.

Essa placa é, em tese, suportada pelo kernel upstream sem a necessidade de
firmware não-livre, e de fato desde a instalação o Debian a reconhece, só
não consegue fazer nada com ela.

Obrigado,

scanner recommendation

[Default User]

Hi!

It may be time for a new scanner.

For years I have used a Visioneer OneTouch 7100 usb flatbed scanner on
various x86 computers running various versions of Debian and
simple-scan.

Currently:
Debian Unstable (updated, of course)
Linux 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 (2021-04-09) x86_64 GNU/Linux
Cinnamon 4.8.6-2
Dell Inspiron 3542 (laptop, circa 2015), 64-bit
Scanner software: simple-scan, from Debian Unstable repositories
Use case: light duty home use.

For years it worked "okay".  But it suddenly started producing scans
with a narrow pink stripe down the left side of the scan image
produced.

I tried installing xsane (too complicated for me), which I did not
configure at all.  And if I just clicked the scan button in xsane it
would "dim out" and then do nothing.  As a bonus, simple-scan then no
longer worked; upon clicking scan in simple-scan it would just do
nothing, with a rotating "activity busy" circle displaying
indefinitely.

So I uninstalled (purged) both xsane and simple-scan, re-installed
simple-scan, then rebooted.
Simple-scan now "works", but still produces the pink stripe down the
image left side, just as before.

: (

Note: the scanner is (about) 20 years, so no parts or service
available from Visioneer.

: (

So . . .
Can anyone recommend a good replacement scanner?

I am really hoping to get something that works "out of the box", with
little or no configuration, etc.

Re: new user MacBook

[David Christensen]

On 4/18/21 1:25 AM, Thanos Katsiolis wrote:

Thank you for your responses, you have been very helpful.


YW.  :-)



My intention was to have both OSs installed and choose which one to boot.
From your answers I understand that it may not be safe for both OSs, so the
best solution is to have a machine dedicated to Debian.


That sounds like a good solution for trying Debian.


I suggest that you create a macOS bootable installer USB flash drive 
before installing Debian, so that you can reinstall macOS on your 
MacBook if you so choose:


https://support.apple.com/en-us/HT201372


David

Re: [?]List of Best Debian-approved laptops in India

[Stefan Monnier]

> I'd recommend to find a vendor that is shipping hardware with a linux
> distribution pre-installed,

Seconded.  Not only it minimizes the problems you'll have when
installing Debian on it but it additionally helps promote those vendors
who do provide GNU/Linux support: vote with your wallet.


Stefan "writing this on a Librem mini"

Re: GRUB no inicia sistema antiguo (era: debian 11 kde primer arranque)

[Marcelo Giordano]

Ejecuta como súperusuario «fstab -l» y manda la salida a la lista.


root@Marcelo:/home/marcelo# fstab -l
bash: fstab: orden no encontrada

Que raro esto, no anda nada.

Antes de intentar reinstalar el paquete, dinos qué te devuelve estas

órdenes (la primera como súperusuario):

apt-get -f install
dpkg -l | grep util-linux

Saludos,


root@Marcelo:/home/marcelo# apt-get -f install
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias... Hecho
Leyendo la información de estado... Hecho
El paquete indicado a continuación se instaló de forma automática y ya 
no es necesario.

  linux-image-5.9.0-4-amd64


root@Marcelo:/home/marcelo# dpkg -l | grep util-linux
ii  util-linux2.36.1-7  
   amd64miscellaneous system utilities
ii  util-linux-locales2.36.1-7  
   all  locales files for util-linux

Re: [?]List of Best Debian-approved laptops in India

[deloptes]

Susmita/Rajib wrote:

> But in the end. may the two laptops, HP and HCL, be please ignored.

It is not about the make, but about the model. In general I recommend
choosing the business line if possible (perhaps buy used one), but still
only experience with the hardware can be the right. For example Dell
Latitude 5440 excellent, 3440 poor. HP ProBook is also not bad

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

[Andrew M.A. Cater]

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

I followed through the screenshots you provided. 

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

apt-cache search first of all,  apt-cache show to show more information
> 
> 
> Result:
> nvidia-legacy-340xx-driver
> nvidia-legacy-340xx-kernel-dkms
> xserver-xorg-video-nvidia-legacy-340xx
> nvidia-legacy-340xx-kernel-source
> 
> 
> The first 3 of 4 packages chosen with apply. Source ignored.
> 
You can't ignore the source - you may have to apply it to a kernel. 

> 
> 
> Report:
> 
> E: nvidia-legacy-340xx-kernel-dkms: installed
> nvidia-legacy-340xx-kernel-dkms package post-installation script
> subprocess returned error exit status 10
> E: nvidia-legacy-340xx-driver: dependency problems - leaving unconfigured
> 
> 
> Installation Details:
> 
> Selecting previously unselected package update-glx.
> (Reading database ... 416821 files and directories currently installed.)
> Preparing to unpack .../update-glx_1.2.0_i386.deb ...
> Unpacking update-glx (1.2.0) ...
> Selecting previously unselected package glx-alternative-mesa.
> Preparing to unpack .../glx-alternative-mesa_1.2.0_i386.deb ...
> Unpacking glx-alternative-mesa (1.2.0) ...
> Selecting previously unselected package nvidia-installer-cleanup.
> Preparing to unpack .../nvidia-installer-cleanup_20151021+13_i386.deb ...
> Unpacking nvidia-installer-cleanup (20151021+13) ...
> Setting up nvidia-installer-cleanup (20151021+13) ...
> Selecting previously unselected package glx-diversions.
> (Reading database ... 416946 files and directories currently installed.)
> Preparing to unpack .../00-glx-diversions_1.2.0_i386.deb ...
> Unpacking glx-diversions (1.2.0) ...
> Selecting previously unselected package glx-alternative-nvidia.
> Preparing to unpack .../01-glx-alternative-nvidia_1.2.0_i386.deb ...
> Unpacking glx-alternative-nvidia (1.2.0) ...
> Selecting previously unselected package nvidia-legacy-340xx-alternative.
> Preparing to unpack
> .../02-nvidia-legacy-340xx-alternative_340.108-10_i386.deb ...
> Unpacking nvidia-legacy-340xx-alternative (340.108-10) ...
> Selecting previously unselected package libnvidia-legacy-340xx-glcore:i386.
> Preparing to unpack .../03-libnvidia-legacy-340xx-glcore_340.108-10_i386.deb 
> ...
> Unpacking libnvidia-legacy-340xx-glcore:i386 (340.108-10) ...
> Selecting previously unselected package nvidia-support.
> Preparing to unpack .../04-nvidia-support_20151021+13_i386.deb ...
> Unpacking nvidia-support (20151021+13) ...
> Selecting previously unselected package libgl1-nvidia-legacy-340xx-glx:i386.
> Preparing to unpack
> .../05-libgl1-nvidia-legacy-340xx-glx_340.108-10_i386.deb ...
> Unpacking libgl1-nvidia-legacy-340xx-glx:i386 (340.108-10) ...
> Selecting previously unselected package libnvidia-legacy-340xx-eglcore:i386.
> Preparing to unpack
> .../06-libnvidia-legacy-340xx-eglcore_340.108-10_i386.deb ...
> Unpacking libnvidia-legacy-340xx-eglcore:i386 (340.108-10) ...
> Selecting previously unselected package 

Re: [?]List of Best Debian-approved laptops in India

[Susmita/Rajib]

On Sun, 18 Apr 2021 15:19:36 +, "Andrew M.A. Cater"
 wrote:
> To: debian-user@lists.debian.org
> Subject: Re: [?]List of Best Debian-approved laptops in India
> From: "Andrew M.A. Cater" 
> Date: Sun, 18 Apr 2021 15:19:36 +
> Message-id: <[] 20210418151936.ga12...@einval.com>
> In-reply-to: <[]
> caeg4czu0mqrkfzbjypl_wzutdouojmmrw509tw82hp0gcyu...@mail.gmail.com>

[...]
>
> Please do not do this. Please do not refer across to the forums as that
> means chasing away from the mailing lists. Please do ask questions here.

Thank you for replying to my post, Mr. Cater. I consider such
reportage my honesty and empathy. I won't have my support-providers
waste man-hours doubly, both there and here. I shall share the links
there and here.

> [...]
> The forum post you have made is not very clear. Most laptops require some
> firmware. Most laptops require non-free WiFi firmware. An increasing number
> also require non-free video drivers. This is, unfortunately, to be
> expected:
> the market share for Linux is small - even where manufacturers pre-install
> Linux - like Lenovo - we may have to install non-free drivers.
>
[...]

Yes, I am pained to find GNU FSF failing.

> [...]
> _Which_ model of HP laptop?
> What does the output of lspci show?
> If you use grep to search the output of dmesg, what does it show for
> firmware / video chipset and so on?

HP laptop issue was partially solved by these two posts:
https://lists.debian.org/debian-user/2019/10/msg00493.html
https://lists.debian.org/debian-user/2019/10/msg00497.html

Debian wifi icon gauges the wireless signal through the card alright,
but fails to use internet through it. However, Knoppix is able to use
the wifi card for internet.

May the issue be _ignored_ therefore.

>> Vesa doesn't work in Debian Buster 10.8, by my blocking Nouveau
>> through grub.cfg that halts the nvidia graphics chip. The string
>> 'xmodule=vesa' doesn't work either.
>
> Don't do that, then. If you install the main Debian installer [using text
> mode
>  only if necessary) - an expert install does the laptop display anything?
> The text mode installer and the graphical installer both use basic drivers
> that should work with most chipsets.

I created a separate thread on this issue, posting the problem in
details and then asking for a HowTo:
Can the latest stable Debian be compelled to run in vesa mode, rather
than the motherboard graphics card, if the said card doesn't have
drivers available? How?

So please bear with me until then.

But in the end. may the two laptops, HP and HCL, be please ignored.

Please peruse the links that have been provided and suggest a good
laptop to buy.

Mr.  Kushal Kumaran  has mentioned two laptops
from India. I shall talk to him

Thank you,

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

[Susmita/Rajib]

Namaste, my dear illustrious Team Leaders and Solution providers,

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

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

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

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

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

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

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

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

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


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


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


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



Report:

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


Installation Details:

Selecting previously unselected package update-glx.
(Reading database ... 416821 files and directories currently installed.)
Preparing to unpack .../update-glx_1.2.0_i386.deb ...
Unpacking update-glx (1.2.0) ...
Selecting previously unselected package glx-alternative-mesa.
Preparing to unpack .../glx-alternative-mesa_1.2.0_i386.deb ...
Unpacking glx-alternative-mesa (1.2.0) ...
Selecting previously unselected package nvidia-installer-cleanup.
Preparing to unpack .../nvidia-installer-cleanup_20151021+13_i386.deb ...
Unpacking nvidia-installer-cleanup (20151021+13) ...
Setting up nvidia-installer-cleanup (20151021+13) ...
Selecting previously unselected package glx-diversions.
(Reading database ... 416946 files and directories currently installed.)
Preparing to unpack .../00-glx-diversions_1.2.0_i386.deb ...
Unpacking glx-diversions (1.2.0) ...
Selecting previously unselected package glx-alternative-nvidia.
Preparing to unpack .../01-glx-alternative-nvidia_1.2.0_i386.deb ...
Unpacking glx-alternative-nvidia (1.2.0) ...
Selecting previously unselected package nvidia-legacy-340xx-alternative.
Preparing to unpack
.../02-nvidia-legacy-340xx-alternative_340.108-10_i386.deb ...
Unpacking nvidia-legacy-340xx-alternative (340.108-10) ...
Selecting previously unselected package libnvidia-legacy-340xx-glcore:i386.
Preparing to unpack .../03-libnvidia-legacy-340xx-glcore_340.108-10_i386.deb ...
Unpacking libnvidia-legacy-340xx-glcore:i386 (340.108-10) ...
Selecting previously unselected package nvidia-support.
Preparing to unpack .../04-nvidia-support_20151021+13_i386.deb ...
Unpacking nvidia-support (20151021+13) ...
Selecting previously unselected package libgl1-nvidia-legacy-340xx-glx:i386.
Preparing to unpack
.../05-libgl1-nvidia-legacy-340xx-glx_340.108-10_i386.deb ...
Unpacking libgl1-nvidia-legacy-340xx-glx:i386 (340.108-10) ...
Selecting previously unselected package libnvidia-legacy-340xx-eglcore:i386.
Preparing to unpack
.../06-libnvidia-legacy-340xx-eglcore_340.108-10_i386.deb ...
Unpacking libnvidia-legacy-340xx-eglcore:i386 (340.108-10) ...
Selecting previously unselected package libegl1-nvidia-legacy-340xx:i386.
Preparing to unpack .../07-libegl1-nvidia-legacy-340xx_340.108-10_i386.deb ...
Unpacking libegl1-nvidia-legacy-340xx:i386 (340.108-10) ...
Selecting previously unselected package nvidia-legacy-340xx-driver-libs:i386.
Preparing to unpack
.../08-nvidia-legacy-340xx-driver-libs_340.108-10_i386.deb ...
Unpacking nvidia-legacy-340xx-driver-libs:i386 (340.108-10) ...
Selecting previously unselected package libnvidia-legacy-340xx-ml1:i386.
Preparing to 

Re: command to start sshfs at bootup?

[Andy Smith]

Hi Gene,

On Sun, Apr 18, 2021 at 12:41:05PM -0400, Gene Heskett wrote:
> My best guess, and admittedly a WAG, certainly not a SWAG, is that ssh 
> and its ilk have been around for yonks. It has not been updated to allow 
> what the lastest rfc now does. Based on that, perhaps a low priority bug 
> should be entered?

It's trivial to test this without wasting anyone's time:

$ getent hosts specialbrew
2001:8b0:ca07:c57a::5 specialbrew.localnet
$ ssh specialbrew hostname
specialbrew.localnet
$ echo "2001:8b0:ca07:c57a::5 specialbrew.localnet 3gene" | sudo tee -a 
/etc/hosts
2001:8b0:ca07:c57a::5 specialbrew.localnet 3gene
$ ssh 3gene hostname
The authenticity of host '[3gene]: ([2001:8b0:ca07:c57a::5]:)' can't be 
established.
ECDSA key fingerprint is SHA256:fdRpfj3HfBaY3K3lCyrBIU2+/bUPX1e5EtC2/bInB5w.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[3gene]:' (ECDSA) to the list of known hosts.
specialbrew.localnet

So no, you are not correct. If you somehow still think you are
please work out a reproducible test that confirms your theory,
before reporting a bug that forces someone else to spend time
debunking it.

Since you have a habit of not issuing commands people ask you to,
and issuing other commands without reporting that you have done so nor
recording what the effect was, my best guess is that you simply
changed something else that you have no recollection of. Another
string possibility is that you made a human error in the first
place. Now it works but you don't know what changed.

The "it starts with a number" theory is not it.

Regards,
Andy

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

Re: command to start sshfs at bootup?

[Greg Wooledge]

On Sun, Apr 18, 2021 at 12:41:05PM -0400, Gene Heskett wrote:
> On Sunday 18 April 2021 10:05:36 Greg Wooledge wrote:
> > I'm not saying that *all* programs will handle this hostname
> > correctly, but bullseye's version of getent(1) does.  Assuming of
> > course that you have corrected your broken configuration, which had
> > "3d" instead of "3dprint" in the hosts file.
> 
> That was in the alias position of the hosts files. And while is now been 
> removed, it did work as an alias to dddprint.

You are allowed to have MANY aliases in that "position".

10.0.0.3   3dprint.local 3dprint 3d threed ddd

At the BARE minimum, you are expected to have the one "canonical" name
(which includes your LAN's domain name or pseudo-domain name), and then
the short form hostname.  Everything AFTER that are your optional aliases.

> My best guess, and admittedly a WAG, certainly not a SWAG, is that ssh 
> and its ilk have been around for yonks. It has not been updated to allow 
> what the lastest rfc now does. Based on that, perhaps a low priority bug 
> should be entered?

Stop guessing.  Start testing.

unicorn:~$ grep 3d /etc/hosts
127.0.0.1   localhost 3dprint
unicorn:~$ ssh 3dprint
The authenticity of host '3dprint (127.0.0.1)' can't be established.
ECDSA key fingerprint is SHA256:Qja12gT16BfC+LPi5Cix3/yCE0pnMKhxTnnifdJbIAE.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '3dprint' (ECDSA) to the list of known hosts.
greg@3dprint's password: 
Linux unicorn 5.10.0-5-amd64 #1 SMP Debian 5.10.24-1 (2021-03-19) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Apr  2 09:17:25 2021 from 139.137.128.43

Re: command to start sshfs at bootup?

[Tixy]

On Sun, 2021-04-18 at 12:41 -0400, Gene Heskett wrote:
> On Sunday 18 April 2021 10:05:36 Greg Wooledge wrote:
> 
> > On Sat, Apr 17, 2021 at 11:31:20PM -0400, Gene Heskett wrote:
> > > On Saturday 17 April 2021 21:47:20 Greg Wooledge wrote:
> > > > getent hosts 3dprint
> > > 
> > > nothing is returned.
> > 
> > For the record, I cannot reproduce this on bullseye.
> > 
> > unicorn:~$ grep hosts /etc/nsswitch.conf
> > hosts:  files mdns4_minimal [NOTFOUND=return] dns
> > unicorn:~$ grep 3d /etc/hosts
> > 10.0.69.3   3dprint.local 3dprint
> > unicorn:~$ getent hosts 3dprint
> > 10.0.69.3   3dprint.local 3dprint
> > 
> > I'm not saying that *all* programs will handle this hostname
> > correctly, but bullseye's version of getent(1) does.  Assuming of
> > course that you have corrected your broken configuration, which had
> > "3d" instead of "3dprint" in the hosts file.
> 
> That was in the alias position of the hosts files. And while is now been 
> removed, it did work as an alias to dddprint.
> 
> My best guess, and admittedly a WAG, certainly not a SWAG, is that ssh 
> and its ilk have been around for yonks. It has not been updated to allow 
> what the lastest rfc now does.

That 'latest' RFC [1] mentioned in another mail is dated October 1989.

[1] https://tools.ietf.org/html/rfc1123

-- 
Tixy

Re: command to start sshfs at bootup?

[Gene Heskett]

On Sunday 18 April 2021 10:05:36 Greg Wooledge wrote:

> On Sat, Apr 17, 2021 at 11:31:20PM -0400, Gene Heskett wrote:
> > On Saturday 17 April 2021 21:47:20 Greg Wooledge wrote:
> > > getent hosts 3dprint
> >
> > nothing is returned.
>
> For the record, I cannot reproduce this on bullseye.
>
> unicorn:~$ grep hosts /etc/nsswitch.conf
> hosts:  files mdns4_minimal [NOTFOUND=return] dns
> unicorn:~$ grep 3d /etc/hosts
> 10.0.69.3 3dprint.local 3dprint
> unicorn:~$ getent hosts 3dprint
> 10.0.69.3   3dprint.local 3dprint
>
> I'm not saying that *all* programs will handle this hostname
> correctly, but bullseye's version of getent(1) does.  Assuming of
> course that you have corrected your broken configuration, which had
> "3d" instead of "3dprint" in the hosts file.

That was in the alias position of the hosts files. And while is now been 
removed, it did work as an alias to dddprint.

My best guess, and admittedly a WAG, certainly not a SWAG, is that ssh 
and its ilk have been around for yonks. It has not been updated to allow 
what the lastest rfc now does. Based on that, perhaps a low priority bug 
should be entered? If ones memory is working, and at 86, that's iffy at 
best, but having been bit 2x by it now, I'll remember it a little 
better.

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: Wi-fi imbutido não encontra nenhuma rede

[riesdra]

Além do firmware da realtek veja se tem o firmware-linux-nonfreeE veja se não 
tem outro módulo carregado que possa estar conflitando com este 
realtek.--Ricardo Libanio  On Dom, 18 abr 2021 07:28:33 -0300  
leonardodearaujoaugu...@gmail.com  wrote Já está instalado e na última 
versão. O driver está carregado, ele só não faz nada com ele.Já tentei até usar 
ndiswrapper pra tentar um driver windows que sei que funciona com a placa, 
nada.Obrigado!Em sáb, 17 de abr de 2021 18:36, riesdra  
escreveu:Se tiver acesso a internet pelo cabo instale o pacote firmware-realtek 
* Precisa do non-free no sources.Talvez isto resolva.--Ricardo Libanio  On 
Sáb, 17 abr 2021 16:33:46 -0300  leonardodearaujoaugu...@gmail.com  wrote 
Estou com dificuldades para fazer com que a minha placa Realtek 8188CE 
(imbutida, notebook Positivo C14CR21 (não tenho informação sobre o modelo 
específico de notebook, mas segue a ficha pelo hw-probe. 
https://linux-hardware.org/?probe=2829ea9d87))Resultado de inxi 
-n:cynthia@cy:~$ inxi -nNetwork:  Device-1: Realtek RTL8188CE 802.11b/g/n WiFi 
Adapter driver: rtl8192ce   IF: wlp1s0 state: down mac: 9a:53:9b:7a:84:35   
Device-2: JMicron JMC250 PCI Express Gigabit Ethernet driver: jme   IF: 
enp2s0f5 state: down mac: 80:ee:73:79:ec:99   IF-ID-1: usb0 state: unknown 
speed: N/A duplex: N/A mac: ae:27:3e:fe:26:72 Ao erro: em tese a placa é 
reconhecida e aparentemente funciona, mas não localiza nenhum SSID. Tentei 
conectar diretamente à rede existente, sem sucesso.O driver que o sistema 
utiliza é o rtl8192ce. Encontrei também um driver alternativo no github, pra 
nenhum efeito. Tentei utilizar o ndiswrapper para tentar carregar um driver 
windows (sei que a placa funciona, ela é funcional no windows 10) e igualmente 
não obtive sucesso.Alguém com experiência nesse dispositivo poderia auxiliar? 
Posso prover logs se necessário.Obrigado!

Re: command to start sshfs at bootup?

[David Wright]

On Sat 17 Apr 2021 at 21:28:34 (-0400), Gene Heskett wrote:
> On Saturday 17 April 2021 20:26:19 Greg Wooledge wrote:
> > On Sat, Apr 17, 2021 at 08:11:37PM -0400, Gene Heskett wrote:
> > > I just checked this machine and 4 others, all of whom are mounted to
> > > their own named directory as subdirs of /sshnet, which work
> > > perfectly without a mention of it in any machines /etc/fstab. Adding
> > > the new machine as the last line in this $HOME/bin/mount-machines
> > > bash script: 
> > > #!/bin/bash
> > > sshfs g...@sixty40.coyote.den:/ /sshnet/sixty40
> > > sshfs gene@lathe:/  /sshnet/lathe
> > > sshfs gene@GO704:/  /sshnet/GO704
> > > sshfs pi@rpi4:/   /sshnet/rpi4
> > > sshfs gene@TLM:/  /sshnet/TLM
> > > sshfs gene@3dprint:/  /sshnet/3dprint
> > > --

> Humm, I just recalled that I had to rename another machine to sixty40 as 
> 6040 was apparently not a valid hostname. I now wonder if I should 
> rename that machine to threedeeprint.domain.name.
> 
> That has to be it, I'll change that and try it tomorrow

So twice in less than two months, you seem to be having a
self-inflicted problem with machine names, and I guess these
quotations give hints why. Back in 1990, RFC1178/FYI5 listed
some recommendations, a selection of which is:

  . Don't choose a name after a project unique to that machine.
  . Don't use long names.
  . Don't use digits at the beginning of the name.
  . Don't expect case to be preserved.

Here, they forgot to add "don't mix O0, Il1, S5 etc". A later
paragraph is amusing:

  . There is always room for an exception.

   I don't think any explanation is needed here.  However, let me
   add that if you later decide to change a name (to something
   sensible like you should have chosen in the first place), you
   are going to be amazed at the amount of pain awaiting you.
   matter how easy the manuals suggest it is to change a name, you
   will find that lots of obscure software has rapidly accumulated
   which refers to that computer using that now-ugly name.  It all
   has to be found and changed.  People mailing to you from other
   sites have to be told.  And you will have to remember that
   names on old backup media labels correspond to different names.

   I could go on but it would be easier just to forget this
   guideline exists.

It's obvious that numerical hostnames are allowed (there are many in
my /etc/hosts, resolving to 127.0.0.1), and they'll work with blue
chip software on the Internet, but it's always going to be a risk
if you use software that hasn't been stress tested like that.

Cheers,
David.

Re: Wi-fi imbutido não encontra nenhuma rede

[Wesley Davi]

Acho bem válido tentar a solução que o Ricardo apresentou.

#apt-cache search realtek
Verifica qual vai atender sua placa e instala, lembrando do non-free no
sources.


Em sáb., 17 de abr. de 2021 às 18:36, riesdra  escreveu:

> Se tiver acesso a internet pelo cabo instale o pacote firmware-realtek
> * Precisa do non-free no sources.
>
> Talvez isto resolva.
>
> --
>
>
>
> *Ricardo Libanio*
>
>  On Sáb, 17 abr 2021 16:33:46 -0300 *
> leonardodearaujoaugu...@gmail.com  *
> wrote 
>
> Estou com dificuldades para fazer com que a minha placa Realtek
> 8188CE (imbutida, notebook Positivo C14CR21 (não tenho informação sobre o
> modelo específico de notebook, mas segue a ficha pelo hw-probe.
> https://linux-hardware.org/?probe=2829ea9d87))
>
> Resultado de inxi -n:
>
> cynthia@cy:~$ inxi -n
>
> Network:
>
>   Device-1: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce
>
>   IF: wlp1s0 state: down mac: 9a:53:9b:7a:84:35
>
>   Device-2: JMicron JMC250 PCI Express Gigabit Ethernet driver: jme
>
>   IF: enp2s0f5 state: down mac: 80:ee:73:79:ec:99
>
>   IF-ID-1: usb0 state: unknown speed: N/A duplex: N/A mac:
> ae:27:3e:fe:26:72
>
>
> Ao erro: em tese a placa é reconhecida e aparentemente funciona, mas não
> localiza nenhum SSID. Tentei conectar diretamente à rede existente, sem
> sucesso.
>
> O driver que o sistema utiliza é o rtl8192ce. Encontrei também um driver
> alternativo no github, pra nenhum efeito. Tentei utilizar o ndiswrapper
> para tentar carregar um driver windows (sei que a placa funciona, ela é
> funcional no windows 10) e igualmente não obtive sucesso.
>
> Alguém com experiência nesse dispositivo poderia auxiliar? Posso prover
> logs se necessário.
>
> Obrigado!
>
>
>

-- 
Att., Wesley Davi da Silva

Problème impression HP Photosmart C4400 avec buster sur armel

[Guilhem Bonnefille]

Bonjour,

Voici quelques jours que je me bataille avec un soucis d'impression.
Ne trouvant pas la solution, je me résoud à demander votre aide.

Depuis des années, j'ai une imprimante HP PhotoSmart C4400 connecté
sur un petit B3 (armel). Mais suite à une montée de version en Buster
(10.9) voilà que l'impression ne fonctionne plus. J'ai pu constater
deux soucis :
- lorsque je tente l'impression d'une page de test avec hp-setup,
j'obtient une page blanche (il charge une page et la recrache)
- lorsque je tente l'impression d'un doc, il imprime un immense triangle noir.

J'ai pu vérifier que l'imprimante fonctionne toujours :
- la page de d'auto-test est nickel
- j'arrive à imprimer depuis un vieux PC sous jessie (il me semble)

Suivant https://wiki.debian.org/CUPSDebugging j'ai tenté de comprendre
ce qui pouvait coincer. J'ai déposé tous les fichiers dans un dossier
partagé :
https://cloud.bonnefille.net/s/ZN5e3CP7pRFYNs4

La seule inquiétude en lisant le log tourne autour de message d'alerte
sur les profils de couleur. Mais je pense que c'est un faux problème
vu les autres tests.
J'ai donc décomposé avec cupsfilter.
1. le fichier original (d1-001) est un PS
2. en sortie de gstopdf, le PDF semble correct (hp.pdf)
3. en sortie de pdftopdf, le PDF est altéré : la page est pivotée de
270° (hp.cups-pdf)
4. en sortie de gstoraster le document est blanc sur une page
5. en sortie de hpcups le document est étrangement léger et semble
contenir deux pages

Le PPD est généré par hp-setup. Son NickName : "HP Photosmart c4400
Series, hpcups 3.16.11"
Il me semble ressembler beaucoup à celui qui fonctionnait.

Bref, je ne sais pas trop dans quelle direction chercher. Si vous avez
une piste, je suis vivement intéressé.

Merci par avance.

-- 
Guilhem BONNEFILLE
-=- mailto:guilhem.bonnefi...@gmail.com
-=- http://nathguil.free.fr/

Re: [?]List of Best Debian-approved laptops in India

[Andrew M.A. Cater]

On Sun, Apr 18, 2021 at 08:01:46PM +0530, Susmita/Rajib wrote:
> My illustrious List Leaders and solution providers,
> 
> My references are here:
> http://forums.debian.net/viewtopic.php?f=10=149280
> {to avoid repetition)

Rajib,

Please do not do this. Please do not refer across to the forums as that 
means chasing away from the mailing lists. Please do ask questions here.

The forum post you have made is not very clear. Most laptops require some
firmware. Most laptops require non-free WiFi firmware. An increasing number
also require non-free video drivers. This is, unfortunately, to be expected:
the market share for Linux is small - even where manufacturers pre-install
Linux - like Lenovo - we may have to install non-free drivers.

> 
> Need your advice and suggestion on the issue. The laptops that I have
> are problematic under Debian. Some modified Debian installation like
> Knoppix have sorted out some problems that exist with Pure Debian,
> like wifi in HP and vesa in HCL Me.
> 

_Which_ model of HP laptop? 
What does the output of lspci show?
If you use grep to search the output of dmesg, what does it show for
firmware / video chipset and so on?

> Vesa doesn't work in Debian Buster 10.8, by my blocking Nouveau
> through grub.cfg that halts the nvidia graphics chip. The string
> 'xmodule=vesa' doesn't work either.

Don't do that, then. If you install the main Debian installer [using text mode
 only if necessary) - an expert install does the laptop display anything?
The text mode installer and the graphical installer both use basic drivers
that should work with most chipsets.

> 
> Debian nvidia drivers, as ever, fails to install.

How did you install them - what procedure did you follow?
> 
> The nvidia drivers 64bit downloaded from nvidia website don't work.
> The problematic Hardware:
> (1) VGA compatible controller : NVIDIA Corporation MCP79 [GeForce
> 8200M G] (rev b1) (prog-if 00 [VGA controller])
> (2) Audio device : NVIDIA Corporation MCP79 High Definition Audio (rev b1)
> 

If you use the proprietary drivers, then you will need to follow particular
steps. The drivers you need are referenced here: 
https://packages.debian.org/buster/nvidia-legacy-340xx-driver

> So information would be welcome. This time I wish to buy a laptop that
> shall not be DND, but Debian approved.
> 
> Regards,
> Rajib
> Etc.
> 

All best, as ever,

Andy Cater

Re: [?]List of Best Debian-approved laptops in India

[Kushal Kumaran]

On Sun, Apr 18 2021 at 08:01:46 PM, "Susmita/Rajib"  
wrote:
> My illustrious List Leaders and solution providers,
>
> My references are here:
> http://forums.debian.net/viewtopic.php?f=10=149280
> {to avoid repetition)
>
> Need your advice and suggestion on the issue. The laptops that I have
> are problematic under Debian. Some modified Debian installation like
> Knoppix have sorted out some problems that exist with Pure Debian,
> like wifi in HP and vesa in HCL Me.
>
> Vesa doesn't work in Debian Buster 10.8, by my blocking Nouveau
> through grub.cfg that halts the nvidia graphics chip. The string
> 'xmodule=vesa' doesn't work either.
>
> Debian nvidia drivers, as ever, fails to install.
>
> The nvidia drivers 64bit downloaded from nvidia website don't work.
> The problematic Hardware:
> (1) VGA compatible controller : NVIDIA Corporation MCP79 [GeForce
> 8200M G] (rev b1) (prog-if 00 [VGA controller])
> (2) Audio device : NVIDIA Corporation MCP79 High Definition Audio (rev b1)
>
> So information would be welcome. This time I wish to buy a laptop that
> shall not be DND, but Debian approved.
>

I'd recommend to find a vendor that is shipping hardware with a linux
distribution pre-installed, and pick a device that does not have nvidia
hardware, assuming you don't need any specific nvidia feature.  When I
last bought a laptop in India (~2016), it was a Dell Vostro 3458 with
Ubuntu preinstalled.  My current hardware is a Dell Precision 7520,
again with Ubuntu preinstalled.  Both run debian with no difficulty.  I
have no recent experience with running nvidia hardware.  The Vostro has
Intel and the Precision has Intel/AMD.

-- 
regards,
kushal

[?]List of Best Debian-approved laptops in India

[Susmita/Rajib]

My illustrious List Leaders and solution providers,

My references are here:
http://forums.debian.net/viewtopic.php?f=10=149280
{to avoid repetition)

Need your advice and suggestion on the issue. The laptops that I have
are problematic under Debian. Some modified Debian installation like
Knoppix have sorted out some problems that exist with Pure Debian,
like wifi in HP and vesa in HCL Me.

Vesa doesn't work in Debian Buster 10.8, by my blocking Nouveau
through grub.cfg that halts the nvidia graphics chip. The string
'xmodule=vesa' doesn't work either.

Debian nvidia drivers, as ever, fails to install.

The nvidia drivers 64bit downloaded from nvidia website don't work.
The problematic Hardware:
(1) VGA compatible controller : NVIDIA Corporation MCP79 [GeForce
8200M G] (rev b1) (prog-if 00 [VGA controller])
(2) Audio device : NVIDIA Corporation MCP79 High Definition Audio (rev b1)

So information would be welcome. This time I wish to buy a laptop that
shall not be DND, but Debian approved.

Regards,
Rajib
Etc.

Re: command to start sshfs at bootup?

[Greg Wooledge]

On Sat, Apr 17, 2021 at 11:31:20PM -0400, Gene Heskett wrote:
> On Saturday 17 April 2021 21:47:20 Greg Wooledge wrote:
> 
> > getent hosts 3dprint
> nothing is returned.

For the record, I cannot reproduce this on bullseye.

unicorn:~$ grep hosts /etc/nsswitch.conf 
hosts:  files mdns4_minimal [NOTFOUND=return] dns
unicorn:~$ grep 3d /etc/hosts
10.0.69.3   3dprint.local 3dprint
unicorn:~$ getent hosts 3dprint
10.0.69.3   3dprint.local 3dprint

I'm not saying that *all* programs will handle this hostname correctly,
but bullseye's version of getent(1) does.  Assuming of course that
you have corrected your broken configuration, which had "3d" instead
of "3dprint" in the hosts file.

Re: SOLVED:command to start sshfs at bootup?

[Reco]

Hi.

On Sun, Apr 18, 2021 at 03:49:12PM +0200, to...@tuxteam.de wrote:
> > Hence "3dprint" is a perfectly valid hostname, compliant with RFC1123.
> > As shown (to me) by a quick experiment, both dnsmasq and bind accept
> > "3dprint" for both A and  record, and it resolves successfully.
> > 
> > The original problem is more likely a local configuration problem, or an
> > operator error.
> 
> Would be interesting to find out why...

Our resident telepath is on vacation, and my crystal ball is receiving
monthly maintenance. OP e-mails, as you surely know, usually lack all
those technical details which us could use to solve the problem. And
this particular problem is not an exception.

All I can say - all known aspects of OP setup indicate that it should
work, and if I ever need it to work for me (I prefer NFS to "persistent"
SSHFS mounts) - it will.

Reco

Re: SOLVED:command to start sshfs at bootup?

[tomas]

On Sun, Apr 18, 2021 at 04:44:05PM +0300, Reco wrote:
>   Hi.
> 
> On Sun, Apr 18, 2021 at 03:36:45PM +0200, to...@tuxteam.de wrote:
> > On Sun, Apr 18, 2021 at 09:21:55AM -0400, Gene Heskett wrote:
> > > On Saturday 17 April 2021 23:31:20 Gene Heskett wrote:
> > > 
> > > It boiled down to something, someplace, not liking a hostname starting 
> > > with a number, I recalled I had to rename another machine a couple 
> > > months ago because it didn't work either.
> > > 
> > > But I changed its hostname to dddprint, based on the previous 3dprint, 
> > > and it now works as requested. So my problem is solved.
> > > 
> > > Is that just a head scratcher, or is there a valid reason to not allow a 
> > > hostname such as 6040 or 3dprint? Something starting with a numeral IOW.
> > 
> > Well, it's in rfc1035 [1]:
> 
> That RFC is obsolete. RFC1123 says on this:

Oh, thanks for that update.

> [...]  Host software MUST support this more liberal syntax.
> 
> Host software MUST handle host names of up to 63 characters and SHOULD
> handle host names of up to 255 characters.
> 
> 
> Hence "3dprint" is a perfectly valid hostname, compliant with RFC1123.
> As shown (to me) by a quick experiment, both dnsmasq and bind accept
> "3dprint" for both A and  record, and it resolves successfully.
> 
> The original problem is more likely a local configuration problem, or an
> operator error.

Would be interesting to find out why...

Cheers
 - t


signature.asc
Description: Digital signature

Re: SOLVED:command to start sshfs at bootup?

[Greg Wooledge]

On Sun, Apr 18, 2021 at 09:21:55AM -0400, Gene Heskett wrote:
> It boiled down to something, someplace, not liking a hostname starting 
> with a number, I recalled I had to rename another machine a couple 
> months ago because it didn't work either.
> 
> But I changed its hostname to dddprint, based on the previous 3dprint, 
> and it now works as requested. So my problem is solved.
> 
> Is that just a head scratcher, or is there a valid reason to not allow a 
> hostname such as 6040 or 3dprint? Something starting with a numeral IOW.

It was one of the thoughts that I had last night when I was suggesting
debugging steps.

As for why it happens -- well, it's something a programmer will understand
intuitively.  I can't say whether it's a bug, a lazy implementation,
or a feature.

Let's say you're writing a program that can accept either an IP address
or a hostname.  You'd like to make it as easy as possible for the user,
so you don't require the user to say "the following is a hostname" or
"the following is an IP address".  Instead, you write code that will
automatically detect which one it is.

Now, how much effort do you actually put into the piece of the program
that performs the automatic detection?  That's the tricky question.  Do
you want the code to be super efficient?  Do you want to handle all kinds
of bizarre cases?  That's up to the individual programmer, or the designer
of the application.

Someone who leans toward the "bizarre cases" side might decide to write
a regular expression that matches an IPv4 address, another regular
expression that matches an IPv6 address, and then apply both of those
(in one order or the other order) against the user's input, and the first
one that matches wins.  If neither one matches, then treat it as a
hostname.

The cost of this solution is quite high.  You have to link in a regular
expression library, and you have to write two nontrivial regular
expressions, and you have to actually compile them and perform the
matching, which is a fairly expensive (in terms of CPU time) operation.
On top of all that, now you're locked in to the current design notions
of IPv4 and IPv6 addresses.  If someone comes up with IPv7 in the future,
your code won't handle it.

On the other end of the spectrum, there's the quick and dirty way.  You
look at the first byte of the user's input, and see whether it's a digit.
If it's a digit, you assume it's an IPv4 address.  Otherwise, you assume
it's a hostname.  You don't handle IPv6 because you probably wrote this
code before IPv6 even existed.

This solution is extremely cheap.  No libraries are needed, and no
regular expressions have to be written or compiled or matched.  Grabbing
one byte of memory through a pointer you've already got is about as fast
a test as you can possibly have.

So, based on what you're telling us, you've got some program that went
with the quick and dirty solution.

Since your statements are so incredibly vague, we can't even guess *which*
program it is, but if you want to pursue it with the developers, that's
your choice.

For the record, this kind of quick-and-dirty detection is common in
other namespaces besides just hostnames.  It also happens with user names
and group names, for example.  "chown 1000 foobar" will change the
owner of the file foobar to UID 1000.  If you try to create a user whose
*name* is 1000, you will have problems.  Lots of problems, very serious
ones.  Even a username that starts with a digit is probably an extremely
bad idea, for the reasons given above.

Re: SOLVED:command to start sshfs at bootup?

[Reco]

Hi.

On Sun, Apr 18, 2021 at 03:36:45PM +0200, to...@tuxteam.de wrote:
> On Sun, Apr 18, 2021 at 09:21:55AM -0400, Gene Heskett wrote:
> > On Saturday 17 April 2021 23:31:20 Gene Heskett wrote:
> > 
> > It boiled down to something, someplace, not liking a hostname starting 
> > with a number, I recalled I had to rename another machine a couple 
> > months ago because it didn't work either.
> > 
> > But I changed its hostname to dddprint, based on the previous 3dprint, 
> > and it now works as requested. So my problem is solved.
> > 
> > Is that just a head scratcher, or is there a valid reason to not allow a 
> > hostname such as 6040 or 3dprint? Something starting with a numeral IOW.
> 
> Well, it's in rfc1035 [1]:

That RFC is obsolete. RFC1123 says on this:

The syntax of a legal Internet host name was specified in RFC-952
[DNS:4].  One aspect of host name syntax is hereby changed: the
restriction on the first character is relaxed to allow either a letter
or a digit.  Host software MUST support this more liberal syntax.

Host software MUST handle host names of up to 63 characters and SHOULD
handle host names of up to 255 characters.


Hence "3dprint" is a perfectly valid hostname, compliant with RFC1123.
As shown (to me) by a quick experiment, both dnsmasq and bind accept
"3dprint" for both A and  record, and it resolves successfully.

The original problem is more likely a local configuration problem, or an
operator error.

Reco

Re: SOLVED:command to start sshfs at bootup?

[tomas]

On Sun, Apr 18, 2021 at 09:21:55AM -0400, Gene Heskett wrote:
> On Saturday 17 April 2021 23:31:20 Gene Heskett wrote:
> 
> It boiled down to something, someplace, not liking a hostname starting 
> with a number, I recalled I had to rename another machine a couple 
> months ago because it didn't work either.
> 
> But I changed its hostname to dddprint, based on the previous 3dprint, 
> and it now works as requested. So my problem is solved.
> 
> Is that just a head scratcher, or is there a valid reason to not allow a 
> hostname such as 6040 or 3dprint? Something starting with a numeral IOW.

Well, it's in rfc1035 [1]:

"The labels must follow the rules for ARPANET host names.  They must
 start with a letter, end with a letter or digit, and have as interior
 characters only letters, digits, and hyphen.  There are also some
 restrictions on the length.  Labels must be 63 characters or less."

("label" is the rfc's parlance for a FQDN component, i.e. "what goes
between the dots [2]).

I guess what happens is that whatever program is trying to resolve
the host name relies on that and assumes an IP address was given
whenever the thing starts with a digit. Fair enough, I'd say.

> Is that a bug?  Or is there a specific reason for the silent failure?

I don't think so.

Cheers

[1] https://tools.ietf.org/html/rfc1035
[2] Yes, I'm imagining dots at the beginning and the end of the
   FQDN, you nitpickers ;-)

 - t


signature.asc
Description: Digital signature

Re: SOLVED:command to start sshfs at bootup?

[Gene Heskett]

On Saturday 17 April 2021 23:31:20 Gene Heskett wrote:

It boiled down to something, someplace, not liking a hostname starting 
with a number, I recalled I had to rename another machine a couple 
months ago because it didn't work either.

But I changed its hostname to dddprint, based on the previous 3dprint, 
and it now works as requested. So my problem is solved.

Is that just a head scratcher, or is there a valid reason to not allow a 
hostname such as 6040 or 3dprint? Something starting with a numeral IOW.

Is that a bug?  Or is there a specific reason for the silent failure?

In which case, it really ought to be a little mouthier about the failure.

> On Saturday 17 April 2021 21:47:20 Greg Wooledge wrote:
> > getent hosts 3dprint
>
> nothing is returned.
>
> I think I might be on the trail though, I just recalled I had to
> rename another machine several months back, from 6040 to sixty40,
> someplace it doesn't like a hostname starting with a number. So I'll
> investigate that tomorrow. I just shut that one down for the night
> since I've not yet added it to amanda's nightly backups.
>
> Thanks Greg.
>
> Cheers, Gene Heskett


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 

Backuppc : can't write 4 bytes to socket

[Migrec]

  
  
Bonjour,

Depuis quelques mois, j'ai un des clients sauvegardé par backuppc
qui ne veut plus rien savoir...
Voici la fin du log
michel/.mozilla/firefox/mns532kb.default/storage/default/moz-extension+++546c6e1d-ebfd-4ee5-9374-506b2a42fbc7^userContextId=4294967295/.metadata-v2 got digests 381bbe9a2b00734669982984121eb0ea vs 381bbe9a2b00734669982984121eb0ea
[ 3 lignes sautées ]
Read EOF: 
Tried again: got 0 bytes
Can't write 4 bytes to socket
finish: removing in-process file michel/.mozilla/firefox/mns532kb.default/storage/default/moz-extension+++546c6e1d-ebfd-4ee5-9374-506b2a42fbc7^userContextId=4294967295/idb/3647222921wleabcEoxlt-eengsairo.files/20363
Child is aborting


J'ai tenté de rajouter -o ServerAliveInterval=1200
  dans les options de RsyncClientCmd mais sans succès. À noter que
  ce n'est pas toujours le même fichier qui coince : ça arrive au
  bout de 10 à 15 minutes environ. Le pc sauvegardé ne se met pas en
  veille.
  Je ne sais plus trop quoi faire...
  
  Une idée ?
  --
  Migrec

  

Re: Debian chromium package enable_hangout_services_extension=false by default. How to turn it on during run time?

[Curt]

On 2021-04-18, Sven Joachim  wrote:
>>
>> How I can turn it on during runtime? without need to patch manually
>> and built the package locally?
>
> I don't think you can, this is a build time feature IIUC.  There is a
> bug report requesting it to be enabled: https://bugs.debian.org/886358.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881701

I believe the upshot is (if you're unwilling to wait for alpine skiing
to be a thing in the netherworld) that the OP will have to rebuild the
package from source after removing the 
'enable_hangout_services_extension=false' 
line from the debian/rules file.

> Cheers,
>Sven

Re: new user MacBook

[Thanos Katsiolis]

Thank you for your responses, you have been very helpful.

My intention was to have both OSs installed and choose which one to boot.
>From your answers I understand that it may not be safe for both OSs, so the
best solution is to have a machine dedicated to Debian.

On Sun, Apr 18, 2021 at 8:28 AM riveravaldez 
wrote:

> On 4/17/21, David Christensen  wrote:
> > On 4/17/21 8:39 AM, Thanos Katsiolis wrote:
> >> Hello,
> >>
> >> I am a new user who would like to try Debian.
> >>
> >> I have a MacBook Pro (Early 11) which runs Mac OS, to which I want to
> >> also
> >> install Debian. Will I have any issues installing Debian regarding
> >> hardware?
> >> I would also appreciate it if you have any tips before the installation
> >> as
> >> well as if there is any source that helps for the installation.
> >>
> >> Forgive me if this is not the right place to ask this question, and feel
> >> free directing me to the right place.
> >
> >
> > That is called "dual-boot'.  Setting it up correctly is non-trivial; the
> > details vary by computer make and model.  Even when I have succeeded at
> > dual-boot, I found that, no matter which OS I was running, I always
> > needed to do something on the other OS.
> >
> >
> > The obvious answer today is virtualization.  I suggest installing
> > VirtualBox, creating a virtual machine, and installing Debian into the
> > virtual machine.  That will allow you to "try Debian" (or any other x86
> > operating system) with far less risk of making your MacBook unbootable,
> > corrupting the native OS, or destroying data.  And, you can use both
> > macOS and Debian at the same time.
>
> Hi,
>
> another option (not sure why not mentioned, sorry if this is not
> convenient)
> could be to try with a LiveCD/DVD/USB, you can check:
>
> https://wiki.debian.org/LiveCD
> https://wiki.debian.org/DebianLive
> https://www.debian.org/CD/live/
> https://wiki.debian.org/USBBoot
> https://wiki.debian.org/DebianLive/MultibootISO
>
> (Maybe in that order.)
>
> Hope this helps. :)
>
> Best regards!
>
>

Re: command to start sshfs at bootup?

[Tom Dial]

On 4/17/21 21:31, Gene Heskett wrote:
> On Saturday 17 April 2021 21:47:20 Greg Wooledge wrote:
> 
>> getent hosts 3dprint
> nothing is returned.
> 
> I think I might be on the trail though, I just recalled I had to rename 
> another machine several months back, from 6040 to sixty40, someplace it 
> doesn't like a hostname starting with a number. So I'll investigate that 
> tomorrow. I just shut that one down for the night since I've not yet 
> added it to amanda's nightly backups.
> 
> Thanks Greg.
> 
> Cheers, Gene Heskett
> 
Hi Gene,

Post the output of

sftp -vvv gene@3dprint

for all to see. It may well contain some useful information.
The symptoms - Connection reset by peer - look to me like nothing is
listening at the far end, or maybe something went south with the
authentication. It might be worth looking at /var/log/messages and
/var/log/auth.log for events that correlate with the connection attempt.

Regards,

Tom Dial

Re: command to start sshfs at bootup?

[Tom Dial]

On 4/17/21 21:31, Gene Heskett wrote:
> On Saturday 17 April 2021 21:47:20 Greg Wooledge wrote:
> 
>> getent hosts 3dprint
> nothing is returned.
> 
> I think I might be on the trail though, I just recalled I had to rename 
> another machine several months back, from 6040 to sixty40, someplace it 
> doesn't like a hostname starting with a number. So I'll investigate that 
> tomorrow. I just shut that one down for the night since I've not yet 
> added it to amanda's nightly backups.
> 
> Thanks Greg.
> 
> Cheers, Gene Heskett
> 
Hi Gene,

Post the output of

sftp -vvv gene@3dprint

for all to see. It may well contain some useful information.
The symptoms - Connection reset by peer - look to me like nothing is
listening at the far end, or maybe something went south with the
authentication. It might be worth looking at /var/log/messages and
/var/log/auth.log for events that correlate with the connection attempt.

>>> That would be /var/log/messages and /var/log/auth.log on the 3dprint
machine.

Regards,

Tom Dial

Re: Debian chromium package enable_hangout_services_extension=false by default. How to turn it on during run time?

[Sven Joachim]

On 2021-04-18 07:56 +0800, Robbi Nespu wrote:

> Hello! I not able to use "screen share" on google meet using chromium
> browser.
>
> Each time I clicked on it, I get "your browser can't share your
> screen" and dev tool > console don't complaint anything about it.
>
> I did a google-fu and found out it related with a feature that been
> disabled by debian (rule) during built.
>
> $ apt-cache policy chromium
> chromium:
>   Installed: 89.0.4389.114-1
>   Candidate: 89.0.4389.114-1
>   Version table:
>  *** 89.0.4389.114-1 500
> 500 http://ftp.jp.debian.org/debian bullseye/main amd64 Packages
> 100 /var/lib/dpkg/status
>
> So I checked here
> https://sources.debian.org/src/chromium/89.0.4389.114-1/debian/rules/
> # disabled features
> defines+=is_debug=false \
>  use_goma=false \
>  use_ozone=false \
>  use_sysroot=false \
>  use_allocator=\"none\" \
>  use_libjpeg_turbo=true \
>  use_custom_libcxx=false \
>  use_gnome_keyring=false \
>  use_unofficial_version_number=false \
>  enable_vr=false \
>  enable_nacl=false \
>  enable_nacl_nonsfi=false \
>  enable_swiftshader=false \
>  enable_reading_list=false \
>  enable_one_click_signin=false \
>  enable_iterator_debugging=false \
>  enable_hangout_services_extension=false \ # <--- HERE
>  optimize_webui=false \
>  angle_has_histograms=false \
>  enable_js_type_check=false \
>  treat_warnings_as_errors=false \
>
> How I can turn it on during runtime? without need to patch manually
> and built the package locally?

I don't think you can, this is a build time feature IIUC.  There is a
bug report requesting it to be enabled: https://bugs.debian.org/886358.

Cheers,
   Sven

Re: Need help finding the right package under which to report a bug

[Sven Joachim]

On 2021-04-18 12:31 +0800, Robbi Nespu wrote:

> A quick or temporary solution are to git clone
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> and copy thus selection (warning line) of missing modules to
> /lib/firmware/amdgpu/
>
> (Don't try my solution if you are novice).

I would rather live with the warnings unless I actually had a GPU which
needs this firmware.  Don't know if you can actually buy these yet.

> Look like the bug are the 5.10.0-6-amd64 kernel.

No, it is in the firmware-amd-graphics package.  A bug report against
this package could help to remind the maintainers that they should
include the arcturus firmware in future uploads.

Cheers,
   Sven