[DNG] Tried Debian Stretch with systemd out of constrainsts
Hi, Thanks for the links. The https://github.com/Ho-Ro/Hantek6022API is a promising resource. My USB oscilloscope is the version succeeding Hantek6022. ___ 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 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] Tried Debian Stretch with systemd out of constrainsts
On 10/01/2020 17:28, Andreas Messer wrote: > On Thu, Jan 09, 2020 at 10:04:28PM +0100, Edward Bartolo via Dng wrote: >> [...] >> >> I still have yet not figured out how to avoid having to use snapd and >> install the firmware for the oscilloscope, Hantek 6000B (USB). I have >> successfully extracted .hex files from the MS Windows drivers but have >> no idea what to do with these hex files which are supposed to contain >> the oscilloscope's firmware. The openhantek package has a .rules udev >> file to enable detection of the oscilloscope. However, the kernel >> still wants to know where to look for the oscilloscope's firmware, and >> that particular information is missing. > > Firmware file for the linux kernel usually reside in /lib/firmware. You > could try to copy your hex files there. Make sure to use proper name as > expected by kernel. > > What do you need snapd for? > > cheers, > Andreas > 'modinfo ' should show you the firmware name and path (under /lib/firmware) that the module expects. ___ 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 Thu, Jan 09, 2020 at 10:04:28PM +0100, Edward Bartolo via Dng wrote: > [...] > > I still have yet not figured out how to avoid having to use snapd and > install the firmware for the oscilloscope, Hantek 6000B (USB). I have > successfully extracted .hex files from the MS Windows drivers but have > no idea what to do with these hex files which are supposed to contain > the oscilloscope's firmware. The openhantek package has a .rules udev > file to enable detection of the oscilloscope. However, the kernel > still wants to know where to look for the oscilloscope's firmware, and > that particular information is missing. Firmware file for the linux kernel usually reside in /lib/firmware. You could try to copy your hex files there. Make sure to use proper name as expected by kernel. What do you need snapd for? cheers, Andreas -- gnuPG keyid: 8C2BAF51 fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51 signature.asc Description: PGP signature ___ 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
These last few days I tried Debian Stretch with systemd on a piece of 'old' hardware. I used Stretch to allow snapd and then openhantek to be installed. The following is my experience: I do not intend to negatively criticise systemd just for the sake of it. I would like to recount my experience, which is the experience of someone, who had to try systemd out of constraints, but was set back for various reasons. During boot Stretch faltered several times. The first falter was, trying to resume from swap. This wasted about one minute of boot time. The second was udev complaining pcspkr was already detected or something like that. Then udev faltered at least twice wasting more than 90 seconds. The reason was Broadcomm wifi driver not being successfully loaded. As if these grave hiccups were not enough, there was yet another delay when the boot 'MTA' line was displayed. After this long unnecessary wait and rising exaspiration, the login manager screen appeared. When the desktop, xfce4, was displayed I was yet another time dismayed to notice the time lag graphics were being rendered and I remembered someone on this mailing list discussed Debian's decision to use the main CPU as a graphics renderer when a proper powerful GPU is apsent. Needless to state this was a blow under the belt for me: I could not use a computer with so much sluggishness. This made me think about those who cannot afford to frequently replace their computers and yet they are being constrained to replace their old hardware, because newer software expects to use a proper GPU, and this under Linux! So, I decided to remove systemd and point to Devuan's ASCII repository. I did the usual dist-upgrade command with Debian's repository still included in /etc/apt/sources.list. Then, I installed sysvinit and removed systemd. At the end, I removed the link to Debian's repository and only used Devuan's. When I booted the system, there was an initial delay caused by the swap partition's UUID being mismatched. Udev continued to misbehave and waste boot time, pcspkr also caused another delay, dhclient yet another delay and finally, the MTA line, whatever that may be. These problems were corrected by making sure to reinstall the kernel, udev and the Broadcomm firmware. I also made sure the right UUID for swap is used. Now, the OS boots nicely without systemd which is supposed to surpass sysvinit regarding boot speed. I still have yet not figured out how to avoid having to use snapd and install the firmware for the oscilloscope, Hantek 6000B (USB). I have successfully extracted .hex files from the MS Windows drivers but have no idea what to do with these hex files which are supposed to contain the oscilloscope's firmware. The openhantek package has a .rules udev file to enable detection of the oscilloscope. However, the kernel still wants to know where to look for the oscilloscope's firmware, and that particular information is missing. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
