Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #208940 > unrolled thread

got a new problem with heyu

Back to article view | Back to linux.debian.user

Contents

  got a new problem with heyu Gene Heskett <gheskett@shentel.net> - 2019-05-21 09:30 +0200
    Re: got a new problem with heyu Gene Heskett <gheskett@shentel.net> - 2019-05-21 10:20 +0200
      Re: got a new problem with heyu Jonas Smedegaard <jonas@jones.dk> - 2019-05-21 11:10 +0200
      Re: got a new problem with heyu Curt <curty@free.fr> - 2019-05-21 11:20 +0200
        Re: got a new problem with heyu Gene Heskett <gheskett@shentel.net> - 2019-05-21 20:00 +0200
          Re: got a new problem with heyu David Wright <deblis@lionunicorn.co.uk> - 2019-05-21 20:40 +0200
            Re: got a new problem with heyu Gene Heskett <gheskett@shentel.net> - 2019-05-21 23:10 +0200
      Re: got a new problem with heyu Gene Heskett <gheskett@shentel.net> - 2019-05-21 15:40 +0200
      Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's Gene Heskett <gheskett@shentel.net> - 2019-05-21 16:20 +0200
        Re: got a new problem with heyu, and it is a bug in bfltty that  kills all /dev/ttyUSBnumber's Curt <curty@free.fr> - 2019-05-21 17:50 +0200
          Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's Gene Heskett <gheskett@shentel.net> - 2019-05-21 20:10 +0200
            Re: got a new problem with heyu, and it is a bug in bfltty that  kills all /dev/ttyUSBnumber's David Wright <deblis@lionunicorn.co.uk> - 2019-05-21 20:30 +0200
            Re: got a new problem with heyu, and it is a bug in bfltty that  kills all /dev/ttyUSBnumber's Curt <curty@free.fr> - 2019-05-21 20:40 +0200
              Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's Gene Heskett <gheskett@shentel.net> - 2019-05-21 23:30 +0200
                Re: got a new problem with heyu, and it is a bug in bfltty that  kills all /dev/ttyUSBnumber's David Wright <deblis@lionunicorn.co.uk> - 2019-05-22 01:50 +0200
                  Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's Gene Heskett <gheskett@shentel.net> - 2019-05-22 02:10 +0200
                Re: got a new problem with heyu, and it is a bug in bfltty that  kills all /dev/ttyUSBnumber's Curt <curty@free.fr> - 2019-05-22 09:50 +0200
                  Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's Gene Heskett <gheskett@shentel.net> - 2019-05-22 11:50 +0200

#208940 — got a new problem with heyu

Greetings all;

I just got thru building and installing heyu. But it uses /dev/ttyUSB# 
which does not exist on stretch.  So where is it moved to?

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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [next] | [standalone]

#208942

On Tuesday 21 May 2019 03:27:14 am Gene Heskett wrote:

> Greetings all;
>
> I just got thru building and installing heyu. But it uses /dev/ttyUSB#
> which does not exist on stretch.  So where is it moved to?
>
> Cheers, Gene Heskett
continued, it seems that the usb-serial adapters I have, all ft232's, are 
no longer recognized.
I am logging essentially this for any usb to serial cable plugged in:

May 21 04:12:56 coyote kernel: [233588.749172] usb 2-5: new full-speed 
USB device number 24 using ohci-pci
May 21 04:12:56 coyote kernel: [233588.990150] usb 2-5: New USB device 
found, idVendor=0403, idProduct=6001
May 21 04:12:56 coyote kernel: [233588.990154] usb 2-5: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
May 21 04:12:56 coyote kernel: [233588.990156] usb 2-5: Product: USB FAST 
SERIAL ADAPTER
May 21 04:12:56 coyote kernel: [233588.990158] usb 2-5: Manufacturer: 
FTDI
May 21 04:12:56 coyote kernel: [233588.990159] usb 2-5: SerialNumber: 
FTOOS09N
May 21 04:12:56 coyote kernel: [233588.998182] ftdi_sio 2-5:1.0: FTDI USB 
Serial Device converter detected
May 21 04:12:56 coyote kernel: [233588.998224] usb 2-5: Detected FT232RL
May 21 04:12:56 coyote kernel: [233589.004209] usb 2-5: FTDI USB Serial 
Device converter now attached to ttyUSB0
May 21 04:12:56 coyote mtp-probe: checking bus 2, device 
24: "/sys/devices/pci0000:00/0000:00:02.0/usb2/2-5"
May 21 04:12:56 coyote mtp-probe: bus: 2, device: 24 was not an MTP 
device
May 21 04:12:57 coyote kernel: [233589.409147] usb 2-5: usbfs: interface 
0 claimed by ftdi_sio while 'brltty' sets config #1
May 21 04:12:57 coyote brltty[523]: USB configuration set error 16: 
Device or resource busy.
May 21 04:12:57 coyote brltty[523]: brltty: USB configuration set error 
16: Device or resource busy.
May 21 04:12:57 coyote brltty[523]: USB interface in use: 0 (ftdi_sio)
May 21 04:12:57 coyote brltty[523]: brltty: USB interface in use: 0 
(ftdi_sio)
May 21 04:12:57 coyote kernel: [233589.412361] ftdi_sio ttyUSB0: FTDI USB 
Serial Device converter now disconnected from ttyUSB0
May 21 04:12:57 coyote kernel: [233589.412385] ftdi_sio 2-5:1.0: device 
disconnected

I have no clue what brltty is, its new  to me.  Whats going on?

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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#208944

[Multipart message — attachments visible in raw view] — view raw

Quoting Gene Heskett (2019-05-21 10:17:28)
> On Tuesday 21 May 2019 03:27:14 am Gene Heskett wrote:
> I have no clue what brltty is, its new  to me.  Whats going on?

$ LANG=C apt-cache search brltty
brltty - Access software for a blind person using a braille display
brltty-espeak - Access software for a blind person - espeak driver
brltty-flite - Access software for a blind person - Flite speech driver
brltty-speechd - Access software for a blind person - Speech Dispatcher driver
brltty-x11 - Access software for a blind person using a braille display - X11 drivers
cl-brlapi - Common Lisp bindings for BrlAPI
libbrlapi-dev - Library for communication with BRLTTY - static libs and headers
libbrlapi-java - Java bindings for BrlAPI
libbrlapi-jni - Java bindings for BrlAPI (native library)
libbrlapi0.6 - braille display access via BRLTTY - shared library
python-brlapi - Braille display access via BRLTTY - Python bindings
python3-brlapi - Braille display access via BRLTTY - Python3 bindings
xbrlapi - Access software for a blind person using a braille display - xbrlapi
cicero - French and English Text-To-Speech for MBROLA

https://duckduckgo.com/?q=brltty provides additional clueful hits.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

[toc] | [prev] | [next] | [standalone]

#208945

On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
>
> I have no clue what brltty is, its new  to me.  Whats going on?

https://brltty.app/

There's some kind of conflict of interest between the kernel and
brltty, the latter of which is claiming the device.

If you're not visually impaired, uninstalling the brltty package
might be a fix.

All gleaned from the thread below (which looks analogous to your
problem):

https://forums.opensuse.org/showthread.php/520714-Bug-handling-USB-RS232-Serial-cable

> Cheers, Gene Heskett

[toc] | [prev] | [next] | [standalone]

#208960

On Tuesday 21 May 2019 05:13:45 am Curt wrote:

> On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
> > I have no clue what brltty is, its new  to me.  Whats going on?
>
> https://brltty.app/
>
> There's some kind of conflict of interest between the kernel and
> brltty, the latter of which is claiming the device.
>
> If you're not visually impaired, uninstalling the brltty package
> might be a fix.
>
> All gleaned from the thread below (which looks analogous to your
> problem):
>
> https://forums.opensuse.org/showthread.php/520714-Bug-handling-USB-RS2
>32-Serial-cable
>

yup, same nail, same hammer, same log output. Since this reduces the 
ability of a site impaired user to use these adapter devices, it could 
be construed as discriminatory in a court of law. The way I see it, this 
can be dumped in brltty's from yard with instructions to fix it, asap.

I'm not blind although I do have plastic eyes, so I don't have a clue why 
it was even being ran on my machine.  It would have saved me several 
hours, but then there would not be yet another confirmation that brltty 
is indeed broken.

There is also a machine killer bug in hplip, the module hpfax, which can 
kill the usb stuff if it doesn't have anything to do when cron awakens 
it to send a fax. renaming the binary to hpfox so cron can't find it is 
the first fix,  So thats another buglet to be fixed. Both of these need 
to be filed and fixed before an official buster respin. 

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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#208964

On Tue 21 May 2019 at 13:53:59 (-0400), Gene Heskett wrote:
> On Tuesday 21 May 2019 05:13:45 am Curt wrote:
> > On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
> > > I have no clue what brltty is, its new  to me.  Whats going on?
> >
> > https://brltty.app/
> >
> > There's some kind of conflict of interest between the kernel and
> > brltty, the latter of which is claiming the device.
> >
> > If you're not visually impaired, uninstalling the brltty package
> > might be a fix.
> >
> > All gleaned from the thread below (which looks analogous to your
> > problem):
> >
> > https://forums.opensuse.org/showthread.php/520714-Bug-handling-USB-RS2
> >32-Serial-cable
> >
> 
> yup, same nail, same hammer, same log output. Since this reduces the 
> ability of a site impaired user to use these adapter devices, it could 
> be construed as discriminatory in a court of law. The way I see it, this 
> can be dumped in brltty's from yard with instructions to fix it, asap.

If you want to take this breathless view of bug-fixing, perhaps you
should install sid; stretch was release virtually two years ago.

And since when were people hailed into court for misconfiguring
their software, particularly when it reminds you all the time of:

    "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."

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#208971

On Tuesday 21 May 2019 02:31:20 pm David Wright wrote:

> On Tue 21 May 2019 at 13:53:59 (-0400), Gene Heskett wrote:
> > On Tuesday 21 May 2019 05:13:45 am Curt wrote:
> > > On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
> > > > I have no clue what brltty is, its new  to me.  Whats going on?
> > >
> > > https://brltty.app/
> > >
> > > There's some kind of conflict of interest between the kernel and
> > > brltty, the latter of which is claiming the device.
> > >
> > > If you're not visually impaired, uninstalling the brltty package
> > > might be a fix.
> > >
> > > All gleaned from the thread below (which looks analogous to your
> > > problem):
> > >
> > > https://forums.opensuse.org/showthread.php/520714-Bug-handling-USB
> > >-RS2 32-Serial-cable
> >
> > yup, same nail, same hammer, same log output. Since this reduces the
> > ability of a site impaired user to use these adapter devices, it
> > could be construed as discriminatory in a court of law. The way I
> > see it, this can be dumped in brltty's from yard with instructions
> > to fix it, asap.
>
> If you want to take this breathless view of bug-fixing, perhaps you
> should install sid; stretch was release virtually two years ago.
>
> And since when were people hailed into court for misconfiguring
> their software, particularly when it reminds you all the time of:
>
In this day and time David, you never can tell when some libtard might 
take the A.D.A. seriously enough to hire a lawyer who never heard of the 
GPL. If he is worth his hourly, he will read up on it, then go shoping 
for a co-operative judge. One thing I've learned in my 84 years is to 
rarely say never.  Somewhere there's an idiot plotting how to make some 
money from a lawsuit.  He has the mistaken idea its better than working 
for his 3 hots and a cot under a roof. I'm 200% with you, but I'd hate 
to see what little income debian purports to have, wasted on legal 
beagles.

>     "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."
>
> Cheers,
> David.


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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#208950

On Tuesday 21 May 2019 04:17:28 am Gene Heskett wrote:

> On Tuesday 21 May 2019 03:27:14 am Gene Heskett wrote:
> > Greetings all;
> >
> > I just got thru building and installing heyu. But it uses
> > /dev/ttyUSB# which does not exist on stretch.  So where is it moved
> > to?
> >
> > Cheers, Gene Heskett
>
> continued, it seems that the usb-serial adapters I have, all ft232's,
> are no longer recognized.
> I am logging essentially this for any usb to serial cable plugged in:
>
> May 21 04:12:56 coyote kernel: [233588.749172] usb 2-5: new full-speed
> USB device number 24 using ohci-pci
> May 21 04:12:56 coyote kernel: [233588.990150] usb 2-5: New USB device
> found, idVendor=0403, idProduct=6001
> May 21 04:12:56 coyote kernel: [233588.990154] usb 2-5: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3
> May 21 04:12:56 coyote kernel: [233588.990156] usb 2-5: Product: USB
> FAST SERIAL ADAPTER
> May 21 04:12:56 coyote kernel: [233588.990158] usb 2-5: Manufacturer:
> FTDI
> May 21 04:12:56 coyote kernel: [233588.990159] usb 2-5: SerialNumber:
> FTOOS09N
> May 21 04:12:56 coyote kernel: [233588.998182] ftdi_sio 2-5:1.0: FTDI
> USB Serial Device converter detected
> May 21 04:12:56 coyote kernel: [233588.998224] usb 2-5: Detected
> FT232RL May 21 04:12:56 coyote kernel: [233589.004209] usb 2-5: FTDI
> USB Serial Device converter now attached to ttyUSB0
> May 21 04:12:56 coyote mtp-probe: checking bus 2, device
> 24: "/sys/devices/pci0000:00/0000:00:02.0/usb2/2-5"
> May 21 04:12:56 coyote mtp-probe: bus: 2, device: 24 was not an MTP
> device
> May 21 04:12:57 coyote kernel: [233589.409147] usb 2-5: usbfs:
> interface 0 claimed by ftdi_sio while 'brltty' sets config #1
> May 21 04:12:57 coyote brltty[523]: USB configuration set error 16:
> Device or resource busy.
> May 21 04:12:57 coyote brltty[523]: brltty: USB configuration set
> error 16: Device or resource busy.
> May 21 04:12:57 coyote brltty[523]: USB interface in use: 0 (ftdi_sio)
> May 21 04:12:57 coyote brltty[523]: brltty: USB interface in use: 0
> (ftdi_sio)
> May 21 04:12:57 coyote kernel: [233589.412361] ftdi_sio ttyUSB0: FTDI
> USB Serial Device converter now disconnected from ttyUSB0
> May 21 04:12:57 coyote kernel: [233589.412385] ftdi_sio 2-5:1.0:
> device disconnected
>
> I have no clue what brltty is, its new  to me.  Whats going on?

Its a braile utility.  I might have plastic eyes but I'm not blind so why 
is it running, and if I kill it, it comes back just by plugging in one 
of those cables.  What the hell sort of a virus is this thing called 
brltty?  Is it uninstallable?, yes, which now gives me a ttyUSB0 when 
one of these 232 adapter cables is plugged in. Now to find out why it 
really isn't working. Had to set perms to 0777 on the whole path to its 
log. ISTR I had to do something along those lines for wheezy too, years 
ago now. And now its working.
>
> 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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#208951 — Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

On Tuesday 21 May 2019 04:29:55 am you wrote:

> Gene Heskett composed on 2019-05-21 04:17 (UTC-0400):
> > I have no clue what brltty is, its new  to me.  Whats going on?
>
> Past bedtime. Google knew:
> https://github.com/brltty/brltty
> "BRLTTY is a background process (daemon) providing access to the
> Linux/Unix console (when in text mode) for a blind person using a
> refreshable braille display."

daytime again, and time to file a bug report, something I've not tried to 
negotiate since my last mind numbing encounter with the dumbest software 
out there, bugzilla.

It, brltty, should not disable /dev/ttyUSB# when its running. Thats what 
gave it away, when I couldn't make heyu run.  The CM-11a is a serial 
device, with a 4 pin telco plug on one end of its cable, and a db-9 for 
a simple serial port on the other, but since the serial port is already 
occupied, a usb to serial adapter is used and that creates 
a /dev/ttyUSBnumber according to how many there might be.

But between the CM-11a complaining that it needed serviced as it had 
stale data (about 2 weeks worth) to report, it hadn't had since wheezy, 
and brltty's erroring on the CM-11a data it sends once a second till it 
gets serviced when it has some status change to report, /dev/ttyUSB0 was 
being destroyed about 1 second after it was created, I assume by the 
CM-11a data being sent to udev as a string of errors instead of being 
given to heyu which has an automatic response to that sort of incoming 
data.

This to me is a bug that needs fixed.  No sense in denying someone using 
braile facilities being denied the use of such adapters.  Thats 
discriminatory.  And its a bug that could potentially generate a 
lawsuit. So I'm going to add the debian-user list to the CC: Maybe 
someone else with more experience at navigating their way thru bugzilla 
can do it based on what I've written here.

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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#208955 — Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
>
> This to me is a bug that needs fixed.  No sense in denying someone using 

There are already oldenbugs flurrying around the question, Gene.

Here's one from 2012:

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

tags 667616 + wontfix

 Arthur Magill, le Thu 05 Apr 2012 13:10:27 +0200, a écrit :

 > Can brltty be convinced not to grab this connection?

 It could, but we don't want to, as it would break brltty for people who
 use the braille devices with chips using that ID, making the computer
 completely unusable for them, really not a good thing.

writes Monsieur THIBAULT

> braile facilities being denied the use of such adapters.  Thats 
> discriminatory.  And its a bug that could potentially generate a 
> lawsuit. So I'm going to add the debian-user list to the CC: Maybe 
> someone else with more experience at navigating their way thru bugzilla 
> can do it based on what I've written here.

We are positively discriminating in favor of the blind.

> Cheers, Gene Heskett

[toc] | [prev] | [next] | [standalone]

#208962 — Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

On Tuesday 21 May 2019 11:41:00 am Curt wrote:

> On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
> > This to me is a bug that needs fixed.  No sense in denying someone
> > using
>
> There are already oldenbugs flurrying around the question, Gene.
>
> Here's one from 2012:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667616
>
> tags 667616 + wontfix
>
>  Arthur Magill, le Thu 05 Apr 2012 13:10:27 +0200, a écrit :
>  > Can brltty be convinced not to grab this connection?
>
>  It could, but we don't want to, as it would break brltty for people
> who use the braille devices with chips using that ID, making the
> computer completely unusable for them, really not a good thing.
>
> writes Monsieur THIBAULT
>
> > braile facilities being denied the use of such adapters.  Thats
> > discriminatory.  And its a bug that could potentially generate a
> > lawsuit. So I'm going to add the debian-user list to the CC: Maybe
> > someone else with more experience at navigating their way thru
> > bugzilla can do it based on what I've written here.
>
> We are positively discriminating in favor of the blind.
>
> > Cheers, Gene Heskett

Then perhaps the better question is why was it running on a new stretch 
install?   I think it probably could be fixed to keep both camps happy.

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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#208963 — Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

On Tue 21 May 2019 at 14:05:01 (-0400), Gene Heskett wrote:
> On Tuesday 21 May 2019 11:41:00 am Curt wrote:
> > On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
> > > This to me is a bug that needs fixed.  No sense in denying someone
> > > using
> >
> > There are already oldenbugs flurrying around the question, Gene.
> >
> > Here's one from 2012:
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667616
> >
> > tags 667616 + wontfix
> >
> >  Arthur Magill, le Thu 05 Apr 2012 13:10:27 +0200, a écrit :
> >  > Can brltty be convinced not to grab this connection?
> >
> >  It could, but we don't want to, as it would break brltty for people
> > who use the braille devices with chips using that ID, making the
> > computer completely unusable for them, really not a good thing.
> >
> > writes Monsieur THIBAULT
> >
> > > braile facilities being denied the use of such adapters.  Thats
> > > discriminatory.  And its a bug that could potentially generate a
> > > lawsuit. So I'm going to add the debian-user list to the CC: Maybe
> > > someone else with more experience at navigating their way thru
> > > bugzilla can do it based on what I've written here.
> >
> > We are positively discriminating in favor of the blind.
> >
> > > Cheers, Gene Heskett
> 
> Then perhaps the better question is why was it running on a new stretch 
> install?   I think it probably could be fixed to keep both camps happy.

Why not use   aptitude why   to find out. Are you running a DE?
Or are you installing Suggests perhaps?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#208965 — Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
>>
>> We are positively discriminating in favor of the blind.
>>
>> > Cheers, Gene Heskett
>
> Then perhaps the better question is why was it running on a new stretch 
> install?   I think it probably could be fixed to keep both camps happy.

That I don't know. I don't have it here on my Stretch. It would be
interesting to discover what dragged brltty into yours.

> Cheers, Gene Heskett

[toc] | [prev] | [next] | [standalone]

#208972 — Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

On Tuesday 21 May 2019 02:31:26 pm Curt wrote:

> On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
> >> We are positively discriminating in favor of the blind.
> >>
> >> > Cheers, Gene Heskett
> >
> > Then perhaps the better question is why was it running on a new
> > stretch install?   I think it probably could be fixed to keep both
> > camps happy.
>
> That I don't know. I don't have it here on my Stretch. It would be
> interesting to discover what dragged brltty into yours.
>
Good question. The install image is supposed to be the latest straight 
amd64 debian stretch, with a rt-preempt kernel and the latest stable 
2.7.4 linuxcnc.  Not much else is supposed to be changed.

> > 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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#208976 — Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

On Tue 21 May 2019 at 17:21:33 (-0400), Gene Heskett wrote:
> On Tuesday 21 May 2019 02:31:26 pm Curt wrote:
> > On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
> > >> We are positively discriminating in favor of the blind.
> > >>
> > > Then perhaps the better question is why was it running on a new
> > > stretch install?   I think it probably could be fixed to keep both
> > > camps happy.
> >
> > That I don't know. I don't have it here on my Stretch. It would be
> > interesting to discover what dragged brltty into yours.
> >
> Good question.

And do you expect Curt to tell you?

> The install image is supposed to be the latest straight 
> amd64 debian stretch, with a rt-preempt kernel and the latest stable 
> 2.7.4 linuxcnc.  Not much else is supposed to be changed.

Changed from what? Wasn't this a two week old installation from scratch?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#208978 — Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

On Tuesday 21 May 2019 07:44:51 pm David Wright wrote:

> On Tue 21 May 2019 at 17:21:33 (-0400), Gene Heskett wrote:
> > On Tuesday 21 May 2019 02:31:26 pm Curt wrote:
> > > On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
> > > >> We are positively discriminating in favor of the blind.
> > > >
> > > > Then perhaps the better question is why was it running on a new
> > > > stretch install?   I think it probably could be fixed to keep
> > > > both camps happy.
> > >
> > > That I don't know. I don't have it here on my Stretch. It would be
> > > interesting to discover what dragged brltty into yours.
> >
> > Good question.
>
> And do you expect Curt to tell you?
>
> > The install image is supposed to be the latest straight
> > amd64 debian stretch, with a rt-preempt kernel and the latest stable
> > 2.7.4 linuxcnc.  Not much else is supposed to be changed.
>
> Changed from what? Wasn't this a two week old installation from
> scratch?
>
> Cheers,
> David.

No clue what else, download the "testing" image from linuxcnc.org and 
look it over. Not trying to be a smartass about it, I really don't know.


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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#208988 — Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
>>
>> That I don't know. I don't have it here on my Stretch. It would be
>> interesting to discover what dragged brltty into yours.
>>
> Good question. The install image is supposed to be the latest straight 
> amd64 debian stretch, with a rt-preempt kernel and the latest stable 
> 2.7.4 linuxcnc.  Not much else is supposed to be changed.

If you had your ft232 connected at install time, and it was mistaken for
a refreshable braille display, I suppose that would've brought in brltty
as a consequence.


>> > Cheers, Gene Heskett
>
>
> Cheers, Gene Heskett

[toc] | [prev] | [next] | [standalone]

#208993 — Re: got a new problem with heyu, and it is a bug in bfltty that kills all /dev/ttyUSBnumber's

On Wednesday 22 May 2019 03:47:00 am Curt wrote:

> On 2019-05-21, Gene Heskett <gheskett@shentel.net> wrote:
> >> That I don't know. I don't have it here on my Stretch. It would be
> >> interesting to discover what dragged brltty into yours.
> >
> > Good question. The install image is supposed to be the latest
> > straight amd64 debian stretch, with a rt-preempt kernel and the
> > latest stable 2.7.4 linuxcnc.  Not much else is supposed to be
> > changed.
>
> If you had your ft232 connected at install time, and it was mistaken
> for a refreshable braille display, I suppose that would've brought in
> brltty as a consequence.
>
Humm, makes perfect sense since at the time there were 3 plugged in.  
I'll generally disconnect any drives I don't want a new install to 
touch, but it never occurred to me that I should unplug the usb stuffs.

But that I suspect explains it.  Call it mystery solved.

Thanks Curt.

> >> > Cheers, Gene Heskett
> >
> > 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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web