Re: Installing Debian Bullseye on Cubox-i4 with eSATA drive... No ethernet detected

2021-02-06 Thread Vagrant Cascadian
On 2021-02-06, Rick Thomas wrote:
> On Fri, Jan 29, 2021, at 7:18 PM, Rick Thomas wrote:
>> Hi!
>> 
>> On Fri, Jan 29, 2021, at 1:03 AM, Holger Wansing wrote:
>> > On https://www.debian.org/devel/debian-installer/
>> > you should look under the daily snapshots.
>> > For armhf that would be
>> > https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
>> 
>> I downloaded the two-part image from [1] dated 2021-01-30 and tried to 
>> install it on my Cubox-i4.
>> 
>> It booted fine but when it got to the "Detect network hardware" phase, 
>> it failed and said:
>> 
>> No Ethernet card was detected. If you know the name of the driver 
>> needed by your Ethernet card, you can select it from the list. 
>> Driver needed by your Ethernet card:  
>> and gave a long list of available ethernet drivers.
>> 
>> I couldn't find anything that looked like an Atheros 8035 driver, which 
>> seems to be the one in use when I boot with a working system.
>> 
>> Any suggestions?
>> Thanks!
>> Rick
>> 
>> [1] https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
>>  dated 2021-01-30
>
> I tried it again, this time with the components dated 2021-02-06 (today).
> I was hoping that the problem was transient and might have been fixed in the 
> intervening week, but I still got the same result: "No Ethernet card was 
> detected."
>
> Do I need to file a bug report?  If so, to which package?  If I do, is there 
> any chance it will be fixed before Bullseye is released into the wild?
> Is there a known workaround that I can apply?

Pretty sure it is a kernel bug, since I can make it go away on a similar
system by downgrading to linux 5.9.x. Please CC me on the report and
I'll try to contribute what I can!


live well,
  vagrant


signature.asc
Description: PGP signature


Re: Installing Debian Bullseye on Cubox-i4 with eSATA drive... No ethernet detected

2021-02-06 Thread Rick Thomas
On Fri, Jan 29, 2021, at 7:18 PM, Rick Thomas wrote:
> Hi!
> 
> On Fri, Jan 29, 2021, at 1:03 AM, Holger Wansing wrote:
> > On https://www.debian.org/devel/debian-installer/
> > you should look under the daily snapshots.
> > For armhf that would be
> > https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
> 
> I downloaded the two-part image from [1] dated 2021-01-30 and tried to 
> install it on my Cubox-i4.
> 
> It booted fine but when it got to the "Detect network hardware" phase, 
> it failed and said:
> 
> No Ethernet card was detected. If you know the name of the driver 
> needed by your Ethernet card, you can select it from the list. 
> Driver needed by your Ethernet card:  
> and gave a long list of available ethernet drivers.
> 
> I couldn't find anything that looked like an Atheros 8035 driver, which 
> seems to be the one in use when I boot with a working system.
> 
> Any suggestions?
> Thanks!
> Rick
> 
> [1] https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
>  dated 2021-01-30

I tried it again, this time with the components dated 2021-02-06 (today).
I was hoping that the problem was transient and might have been fixed in the 
intervening week, but I still got the same result: "No Ethernet card was 
detected."

Do I need to file a bug report?  If so, to which package?  If I do, is there 
any chance it will be fixed before Bullseye is released into the wild?
Is there a known workaround that I can apply?

Thanks for any help!
Rick



Sound Issue

2021-02-06 Thread Rainer Dorsch
Hi,

sound was working for years on my Debian System w/o any issue with pulseaudio. 
Since a few weeks I have problems with the on-board Intel sound, listed as

Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel 

whereas the Logitech USB headset always works

Device-2: Logitech Headset H390 type: USB driver: hid-generic,snd-usb-
audio,usbhid 

Full inxi -F output is here: 

http://paste.debian.net/1184310/

Out of the blue I noticed today that it worked again, but after I rebooted 
into Debian 10.8 it disappeared again.

In dmesg I find

[...]
[   13.567175] snd_hda_intel :00:1f.3: enabling device ( -> 0002) 
[   13.567306] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915]) 
[   13.609251] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC887-VD: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line 
[   13.609252] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 (0x1a/
0x0/0x0/0x0/0x0) 
[   13.609253] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x1b/
0x0/0x0/0x0/0x0) 
[   13.609253] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 
[   13.609254] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x11/0x0 
[   13.609254] snd_hda_codec_realtek hdaudioC0D0:inputs: 
[   13.609255] snd_hda_codec_realtek hdaudioC0D0:  Rear Mic=0x18 
[   13.609256] snd_hda_codec_realtek hdaudioC0D0:  Front Mic=0x19 
[   13.609256] snd_hda_codec_realtek hdaudioC0D0:  Line=0x15
[...]


http://paste.debian.net/1184308/


In $ pactl list I get

Card #0
Name: alsa_card.usb-Logitech_Logitech_USB_Headset-00
Driver: module-alsa-card.c
Owner Module: 6
Properties:
alsa.card = "1"
alsa.card_name = "Logitech USB Headset"
alsa.long_card_name = "Logitech Logitech USB Headset at 
usb-:00:14.0-13.1, full speed"
alsa.driver_name = "snd_usb_audio"
device.bus_path = "pci-:00:14.0-usb-0:13.1:1.0"
sysfs.path = "/devices/pci:00/:00:14.0/
usb1/1-13/1-13.1/1-13.1:1.0/sound/card1"
udev.id = "usb-Logitech_Logitech_USB_Headset-00"
device.bus = "usb"
device.vendor.id = "046d"
device.vendor.name = "Logitech, Inc."
device.product.id = "0a44"
device.product.name = "Headset H390"
device.serial = "Logitech_Logitech_USB_Headset"
device.form_factor = "headset"
device.string = "1"
device.description = "Headset H390"
module-udev-detect.discovered = "1"
device.icon_name = "audio-headset-usb"
device.intended_roles = "phone"
Profiles:
input:analog-mono: Analog Mono-Eingabe (sinks: 0, sources: 1, 
priority: 7, available: yes)
output:analog-stereo: Analog Stereo-Ausgabe (sinks: 1, 
sources: 0, priority: 6500, available: yes)
output:analog-stereo+input:analog-mono: Analog Stereo-Ausgabe 
+ Analog Mono-Eingabe (sinks: 1, sources: 1, priority: 6507, available: yes)
off: Aus (sinks: 0, sources: 0, priority: 0, available: yes)
Active Profile: output:analog-stereo+input:analog-mono
Ports:
analog-input-mic: Mikrofon (priority: 8700, latency offset: 0 
usec)
Properties:
device.icon_name = "audio-input-microphone"
Part of profile(s): input:analog-mono, output:analog-
stereo+input:analog-mono
analog-output-headphones: Kopfhörer (priority: 9000, latency 
offset: 0 usec)
Properties:
device.icon_name = "audio-headphones"
Part of profile(s): output:analog-stereo, 
output:analog-stereo+input:analog-mono

http://paste.debian.net/1184312/

but there is no other sound card listed.

I tried from the Debian pulseaudio wiki the part under "Missing playback 
devices or audio capture":

rd@h370:~$ rm -r ~/.config/pulse /tmp/pulse-*
rm: cannot remove '/home/rd/.config/pulse': No such file or directory
rm: descend into write-protected directory '/tmp/pulse-PKdhtXMmr18n'? y
rm: remove write-protected directory '/tmp/pulse-PKdhtXMmr18n'? y
rm: cannot remove '/tmp/pulse-PKdhtXMmr18n': Operation not permitted
rd@h370:~$ ls -ld /tmp/pulse-PKdhtXMmr18n
drwx-- 2 root root 4096 Feb  6 20:19 /tmp/pulse-PKdhtXMmr18n
rd@h370:~$ systemctl --user restart pulseaudio.service
rd@h370:~$ 

Not sure if it is expected that there is a pulse file for root in /tmp

What is also strange for me, is that the intel card is listed by-path by not 
by-id:

rd@h370:~$ ls -l /dev/snd/by-id/ 
total 0
lrwxrwxrwx 1 root root 12 Feb  6 20:42 usb-Logitech_Logitech_USB_Headset-00 -> 
../controlC1
rd@h370:~$ ls -l /dev/snd/by-path/
total 0
lrwxrwxrwx 1 root root 12 Feb  6 20:42 pci-:00:14.

Re: Sound Issue

2021-02-06 Thread Andrea Borgia

Il 06/02/21 20:53, Rainer Dorsch ha scritto:



sound was working for years on my Debian System w/o any issue with pulseaudio.
Since a few weeks I have problems with the on-board Intel sound, listed as


I'm having a similar issue and it might be because of this bug: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980836



With this command I get the audio back, at least until the next reboot 
or plug/unplug cycle:


pacmd unload-module module-udev-detect && pacmd load-module 
module-udev-detect



Regards,

Andrea.




Re: timedatectl DHCP NTP Server

2021-02-06 Thread Charles Curley
On Fri, 5 Feb 2021 12:13:43 -0700
Charles Curley  wrote:

> > For lack of time, I resorted to use systemd-timesyncd but apparently
> > you need to configure NM to handle NTP server by way of a hook or
> > tweaking the profile for the desired connection.  
> 
> So I conjecture. I am working on a script to update systemd-timesyncd,
> based on one I found in one of the two bug reports I mentioned
> earlier.

The attached script should do it. Note that it only handles IPV4. See
other notes in the comments.

Note that it creates and logs to its own log file. Once you are
satisfied that it works, you can comment out the rest of the debug
statements.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/


60ntp
Description: Binary data


Re: FVWM title bar information......

2021-02-06 Thread Charlie
On Fri, 5 Feb 2021 08:00:03 -0500
Greg Wooledge  wrote:

> On Fri, Feb 05, 2021 at 09:46:15AM +0100, to...@tuxteam.de wrote:
> > > > I think this is called "shading" [...]  
> > 
> > Glad it helped. Actually, I was unsure myself, because, although
> > I do use fvwm, I somehow managed to make shading inaccessible to
> > me (I don't use it). Not having the time to research properly, I
> > still decided to take the risk.  
> 
> It has to be enabled in your configuration.  The default config for
> the current version of fvwm has it, but if you're using a config
> that you created for an older version (like I am), you may not even
> know it's a possibility.
> 

Thanks Greg,

When I right click on the title bar it does say "shade". But as
with many other things, I must have clicked on it by accident
at times and not knowing what was done or what it was called.
Didn't know how to undo it.

Now am a little wiser thanks to Tomas for giving the result a name.

I too use an old, carry over to various laptops of: /.fvwm/fvwm2rc or
config. The latter, based on the former now.

Thanks for the reply.
 
-- 
Registered Linux User:- 329524

***

We are all in the gutter, but some of us are looking at the
stars. ---Oscar Wilde

***
Debian GNU/Linux - Magic indeed.

-



Re: Linux router AP with reserved IPs on wlan0?

2021-02-06 Thread John Conover
Stefan Monnier writes:
> > A wireless router made with hostapd/dnsmasq/dhcpcd is fairly easy, and
> > works well with iptables, with one shortcoming.
> >
> > After antagonizing the Google for hours, I can not find any way to add
> > reserved IPs based on the the MAC address of devices connected on
> > wlan0, (presumably in dhcpcd.conf.) Seems kind of a simple oversight
> > for a wireless AP.
> 
> I'm not familiar with dhcpd, but dnsmasq's built-in DHCP server has been
> perfectly sufficient so far and it lets you specify fixed IPs based on
> MACs by simply putting those in the `/etc/ethers` file.
>

Thank you, Stefan.

Works like a charm. The syntax of /etc/ethers is ':' delimited MAC
address, followed by a space delimiter, followed by the IPv4 IP
address, per IP reservation. That IP address must also be in
/etc/hosts.

John

-- 

John Conover, cono...@rahul.net, http://www.johncon.com/



Re: AMD GPU + HDMI + vlc = lockup

2021-02-06 Thread Charles Curley
On Sat, 06 Feb 2021 12:38:30 +0100
Kamil Jońca  wrote:

> >
> > Is your HD 5450 passively cooled? If yes, you might try placing a
> > case fan  
> 
> Yes. I try to avoid fans, but I think I have no choice.

If noise is your objection to fans, have some reviews of quiet
equipment: https://silentpcreview.com

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/



Re: Linux router AP with reserved IPs on wlan0?

2021-02-06 Thread Stefan Monnier
> A wireless router made with hostapd/dnsmasq/dhcpcd is fairly easy, and
> works well with iptables, with one shortcoming.
>
> After antagonizing the Google for hours, I can not find any way to add
> reserved IPs based on the the MAC address of devices connected on
> wlan0, (presumably in dhcpcd.conf.) Seems kind of a simple oversight
> for a wireless AP.

I'm not familiar with dhcpd, but dnsmasq's built-in DHCP server has been
perfectly sufficient so far and it lets you specify fixed IPs based on
MACs by simply putting those in the `/etc/ethers` file.


Stefan



Re: Problems installing from flash drive.

2021-02-06 Thread Richard Owlett

On 02/05/2021 01:05 PM, songbird wrote:

Richard Owlett wrote:
...

One can purchase a flash drive containing ISO images of all installation
DVDs of the desired architecture. It is straight forward to do a default
install after copying dvd1.iso to a flash drive.

...

Are the instructions to create a "local repository" composed of
appropriate ISO files?


   yes, i'm sure there are, but also in the past i was able to
just copy the files to the right place on a hard drive or
partition and use that without using any other tool other
than a straight copy.



As I just replied to Jeremy, that works.
I don't recall a previous so can't say why things didn't work.
I suspect I've been using Debian enough since that my unstated 
assumptions more closely match yours ?


Thanks for your time.





Re: Problems installing from flash drive.

2021-02-06 Thread Richard Owlett

That works.
Your choice of directory names in the path to the files extracted from 
each ISO broke my current mental logjam.


Thanks


On 02/05/2021 10:21 AM, Jeremy Andrews wrote:

Hi Richard,

Here's what I would probably do:

- create directories on your USB or partition for each of the DVDs
- extract each ISO, and place the contents in the directories
- if using a separate partition, mount it in your fstab at a location 
such as /mnt/deb, or if using a USB, just make sure to always mount it 
at the same location when you want to install something


Then you can add a line such as this to your APT sources:
deb [trusted=yes] file:///mnt/deb/DVD1/ buster main
deb [trusted=yes] file:///mnt/deb/DVD2/ buster main
deb [trusted=yes] file:///mnt/deb/DVD3/ buster main

Now whenever you want to install something, you shouldn't have to worry 
about which DVD it was on, APT should just automatically find it.



Jeremy

On Fri, 5 Feb 2021 at 09:55, Richard Owlett > wrote:


I wish to do custom Debian install on a machine *WITHOUT*:
    1. functional mechanical CD/DVD drive.
    2. without internet access.

One can purchase a flash drive containing ISO images of all
installation
DVDs of the desired architecture. It is straight forward to do a
default
install after copying dvd1.iso to a flash drive.

Resulting problems include:
    1. undesired programs clutter machine (e.g. LibreOffice).
    2. project critical software cannot be installed as Synaptic
       asks for a non-existent DVD be inserted in a non-existent drive.

One vendor has a shell program which loop mounts the ISO files in
such a
way that *IF* you have the purchased flash drive installed you can use
Synaptic.

The Debian documentation does not appear to describe how apt &/or
Synaptic can access ISO files on dedicated partition.

Are the instructions to create a "local repository" composed of
appropriate ISO files?

TIA








Re: Linux router AP with reserved IPs on wlan0?

2021-02-06 Thread Dan Ritter
John Conover wrote: 
> 
> A wireless router made with hostapd/dnsmasq/dhcpcd is fairly easy, and
> works well with iptables, with one shortcoming.
> 
> After antagonizing the Google for hours, I can not find any way to add
> reserved IPs based on the the MAC address of devices connected on
> wlan0, (presumably in dhcpcd.conf.) Seems kind of a simple oversight
> for a wireless AP.


host conoverlaptop {
 hardware ethernet 00:14:d3:11:22:32;
 fixed-address 192.168.0.20;
}




Re: AMD GPU + HDMI + vlc = lockup

2021-02-06 Thread Kamil Jońca
Felix Miata  writes:

> Kamil Jońca composed on 2021-02-06 09:41 (UTC+0100):
>
>> Yesterday this lockup happens with monitor connected by DVI. So my
>> theory that these lockups are related to DVI/HDMI connection became untrue.
>> I will try to investigate further. Again thanks to Felix for his
>> efforts so far.
>
> You never answered one of my last questions:
> "Have you tried watching top as you start VLC?"

Sorry. I did it now. It is about 90-110 % regardless lockup or not.


>
> Is your HD 5450 passively cooled? If yes, you might try placing a case fan

Yes. I try to avoid fans, but I think I have no choice.
KJ

-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html



Re: AMD GPU + HDMI + vlc = lockup

2021-02-06 Thread Kamil Jońca
Kamil Jońca  writes:

> Felix Miata  writes:
>
>> Kamil Jońca composed on 2021-02-06 09:41 (UTC+0100):
>>
>>> Yesterday this lockup happens with monitor connected by DVI. So my
>>> theory that these lockups are related to DVI/HDMI connection became untrue.
>>> I will try to investigate further. Again thanks to Felix for his
>>> efforts so far.
>>
>> You never answered one of my last questions:
>> "Have you tried watching top as you start VLC?"
>
> Sorry. I did it now. It is about 90-110 % regardless lockup or not.


I mean vlc takes ~90-110% CPU.

KJ


-- 
http://wolnelektury.pl/wesprzyj/teraz/



Re: AMD GPU + HDMI + vlc = lockup

2021-02-06 Thread Felix Miata
Kamil Jońca composed on 2021-02-06 09:41 (UTC+0100):

> Yesterday this lockup happens with monitor connected by DVI. So my
> theory that these lockups are related to DVI/HDMI connection became untrue.
> I will try to investigate further. Again thanks to Felix for his
> efforts so far.

You never answered one of my last questions:
"Have you tried watching top as you start VLC?"

Is your HD 5450 passively cooled? If yes, you might try placing a case fan
somewhere where it can blow on the GPU's heat sink.
-- 
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/



Re: Linux router AP with reserved IPs on wlan0?

2021-02-06 Thread tomas
On Sat, Feb 06, 2021 at 02:29:08AM -0800, John Conover wrote:
> 
> A wireless router made with hostapd/dnsmasq/dhcpcd is fairly easy, and
> works well with iptables, with one shortcoming.
> 
> After antagonizing the Google for hours, I can not find any way to add
> reserved IPs based on the the MAC address of devices connected on
> wlan0, (presumably in dhcpcd.conf.) Seems kind of a simple oversight
> for a wireless AP.
> 
> Am I correct in my assumption?

I think the jargon is "DHCP reservation" or thereabouts. Do these ([1],
[2]) fit your quest?

And oh, BTW. Don't antagonize Google. They don't love you (besides, they
don't make for good neighbours, but I disgress). My search provider just
gave me those results in exchange for a moderate amount of effort (~15
min).

Cheers :)

[1] 
https://servercomputing.blogspot.com/2012/02/reserve-ip-address-in-dhcp-server-linux.html
[2] 
https://askubuntu.com/questions/392599/how-to-reserve-ip-address-in-dhcp-server

 - t


signature.asc
Description: Digital signature


Linux router AP with reserved IPs on wlan0?

2021-02-06 Thread John Conover


A wireless router made with hostapd/dnsmasq/dhcpcd is fairly easy, and
works well with iptables, with one shortcoming.

After antagonizing the Google for hours, I can not find any way to add
reserved IPs based on the the MAC address of devices connected on
wlan0, (presumably in dhcpcd.conf.) Seems kind of a simple oversight
for a wireless AP.

Am I correct in my assumption?

Thanks,

John

-- 

John Conover, cono...@rahul.net, http://www.johncon.com/



Re: AMD GPU + HDMI + vlc = lockup

2021-02-06 Thread Kamil Jońca
Kamil Jońca  writes:

> There is desktop box with sid.
>
> sudo lspci|grep -i vga
> 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
> Cedar [Radeon HD 5000/6000/7350/8350 Series]
>
> So far I have monitor connected via DVI
>
> Recently I connected monitor via hdmi output (instead old one)
> And strange things starts happend.
> When I tried to play movie with vlc there were hand for few seconds and
> then monitor "resets", and there were only black rectanle - have to
> reopen movie.
>

Yesterday this lockup happens with monitor connected by DVI. So my
theory that these lockups are related to DVI/HDMI connection became
untrue.
I will try to investigate further. Again thanks to Felix for his
efforts so far.

KJ

-- 
http://wolnelektury.pl/wesprzyj/teraz/