Re: [DNG] Tried Debian Stretch with systemd out of constrainsts
On Sat, 11 Jan 2020 20:18:09 + Edward Bartolo via Dng wrote: > Hi, > > First of all thanks for replying. It seems the driver is installed > according to usb-devices. The interesting stanza is the following: > > T: Bus=07 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 6 Spd=480 MxCh= 0 > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=04b5 ProdID=6cde Rev=00.00 > S: Manufacturer=ODM > S: Product=DSO Device > C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA > I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) > > Running both the manufacturer's graphical frontend for the > oscilloscope under wine and openhantek fail to detect the > oscilloscope. For both of them the oscilloscope does not exist. > > The firmware and its loader have been extracted from the Windows > drivers. > > Knowing the vendor ID and the Product ID I should be able to > communicate with the oscilloscope. Any ideas how this can be done? Just my 2c. The easiest is to adapt some existing(past?) piece of software that drives something similar. As far as using the V-ID & P-ID, this might be similar to some of the (recent) hacking to get various flatbed paper scanners working where it was necessary to add an entry to udev(?) As to software, it as to be about two decades ago when I saw a presentation at a LUG of a PC driven Oscilloscope that was primarily to run under Linux, It has since been released, but i do not know if the software is FOSS. Last suggestion is to trawl Github or similar repository for software you could adapt, ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Tried Debian Stretch with systemd out of constrainsts
On 11/01/2020 21:15, Florian Zieboll wrote: > On January 11, 2020 9:18:09 PM GMT+01:00, Edward Bartolo via Dng > wrote: > >> Knowing the vendor ID and the Product ID I should be able to >> communicate with the oscilloscope. Any ideas how this can be done? > > > Out of couriosity, I just websearched for openhantek, and found this fork: > > https://github.com/OpenHantek/OpenHantek6022/blob/master/readme.md > > There is some udev rule mentioned (which is the first thing I had thought of > when readong your message) and probably a lot more useful information. And eevblog seems to be the place to go to find others attempts to use Linux. Note the suggestion NOT to upload the firmware :) https://www.eevblog.com/forum/testgear/hantek-6254bd-250mhz-1gsas-pcusb-dso/ > > libre Grüße, > Florian > > > > [message sent otg] > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Tried Debian Stretch with systemd out of constrainsts
On January 11, 2020 9:18:09 PM GMT+01:00, Edward Bartolo via Dng wrote: > Knowing the vendor ID and the Product ID I should be able to > communicate with the oscilloscope. Any ideas how this can be done? Out of couriosity, I just websearched for openhantek, and found this fork: https://github.com/OpenHantek/OpenHantek6022/blob/master/readme.md There is some udev rule mentioned (which is the first thing I had thought of when readong your message) and probably a lot more useful information. libre Grüße, Florian [message sent otg] ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Tried Debian Stretch with systemd out of constrainsts
Hi, First of all thanks for replying. It seems the driver is installed according to usb-devices. The interesting stanza is the following: T: Bus=07 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 6 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=04b5 ProdID=6cde Rev=00.00 S: Manufacturer=ODM S: Product=DSO Device C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) Running both the manufacturer's graphical frontend for the oscilloscope under wine and openhantek fail to detect the oscilloscope. For both of them the oscilloscope does not exist. The firmware and its loader have been extracted from the Windows drivers. Knowing the vendor ID and the Product ID I should be able to communicate with the oscilloscope. Any ideas how this can be done? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Alternatives to synaptic?
On Fri, Jan 10, 2020 at 03:35:39PM -0800, Rick Moen wrote: > > (My own notion of a 'GUI package manager' is apt-get in an xterm. My > own notion of how to make sure an application has superuser privilege > is to do 'su -' to get it. policykit? I don't need no steenin > policykit.) So do I. Except I oftern forget to type the "-". Policykit is for when there are specific actions you'd like users to be able to do that would normally require root privileges, but you can't trust them with all the power that su provided. You are clearly not one of those users. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Fri, 2020-01-10 at 18:15 -0700, 'smee via Dng wrote: > > On Fri, 2020-01-10 at 11:25 +0100, Svante Signell via Dng wrote: > > > > I just installed a fresh ascii install, ran update-initramfs -u and had > no errors (I did see the same last line that's mentioned). So I tried > apt remover *nonfree, let that run, and tried again and it produces > that set of errors when the nonfree firmware is not there. Good! > So, as you mentioned the errors happened after the upgrade to Beowulf. > I'm going to assume that it was just because firmware-misc-nonfree was > in a bad state after the upgrade and that a reinstall of both firmware- > misc-nonfree and firmware-linux-nonfree would fix the issue there. I > can test that if you'd like, by doing the reinstall and running update- > initramfs -u again. Yes, please do. Then we know if we can close this issue or not. Note that you can choose how to update and backup by editing: /etc/initramfs-tools/update- initramfs.conf. You also have a lot of options for updating, see the manpage for update-initramfs. If possible, do also try to find out if your new (beowulf) kernel initrd(.img- 4.19.0-6-amd64, or whatever) has firmware-*-nonfree or not. (Don't know how yet). Thanks! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Spam filtering on this list.
My prior 3 posts to this list, on the "Alternatives to synaptic?" thread, ended in my spam folder, because the listserver's headers included: X-IronPort-SPAM: SPAM But further down, SpamAssassin disagrees, giving no false positive. I guess that IronPort is not useful here. I'll try using only the SpamAssassin header, instead. Erik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Alternatives to synaptic?
Le 10/01/2020 à 18:15, Andreas Messer a écrit : On Thu, Jan 09, 2020 at 07:16:38PM +0100, Alessandro Vesely via Dng wrote: # apt install libelogind0 libpam-elogind synaptic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: elogind libept1.5.0 policykit-1 Suggested packages: dwww software-properties-gtk The following packages will be REMOVED: libpam-ck-connector The following NEW packages will be installed: elogind libelogind0 libept1.5.0 libpam-elogind policykit-1 synaptic 0 upgraded, 6 newly installed, 1 to remove and 3 not upgraded. Need to get 876 kB/3,047 kB of archives. After this operation, 11.4 MB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. if I just try synaptic, I get additional packages libept1.5.0 and policykit-1, so adding elogind doesn't seem to help. This is fine and just as expected. Policykit is not related with systemd. policykit is a framework which allows "normal" users to run commands which usually need "root" permissions like removable drive mounting, installing packages, shutting down the system. Its main purpose is to provide a "smooth" feel to GUI desktop users: E.g. Plug in USB-Stick and just click in the file manager on it without the need to enter a password or invoke sudo. For that purpose policykit uses a rule set. E.g. a typical rule to allow mounting a removable drive could be "User must be logged in locally and the session should be still active ( Not switched to another terminal/screen)". In order to determine the state of a user session and if the corresponding program is part of this session policykit can use either: - consolekit (deprectaed and not working well anymore) - systemd (...) - elogind (Just the session management part of systemd extracted) Besides that session management, elogind/systemd provide some additional functions like commands to shutdown/reboot the system as user. You might be able to run without them on a headless machine or with simple desktop environments but virtually all the "big" desktop environments nowadays depend on availability of either "systemd" or "elogind". Even such applications like "apt" or "apt-*" are now linked to libsystemd0. So if you're going to have a package manager, you'll have either libsystemd0 or libelogind0 installed. Back to topic: I personally stick with apt or aptitude but since the the family sticks more or less to GUI, I have also installed "muon". It is Qt/KDE based and is quite similar to aptitude. I didn't like synaptic since it performs too much "background" magic as I'd tolerate. I invoke synaptic as 'gksu synaptic', bypassing policykit. I dislike policykit, nevertheless it is installed, forced in by dependant packages. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
