1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • Re: Orca install repeating - can't reproduce [WAS Re: Installerandassis

    From gene heskett@21:1/5 to Max Nikulin on Sun Dec 15 18:10:01 2024
    On 12/15/24 09:48, Max Nikulin wrote:
    On 15/12/2024 20:27, gene heskett wrote:
    On 12/14/24 23:00, Max Nikulin wrote:
         /var/log/installer/hardware-summary

    that is quite lengthy, 75+ kilobytes, what would I be looking for?

    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    I am interested in some equivalent of

       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


         lsusb -vt

    - Option 1. <http://paste.debian.net/>
    - Option 2.

          grep usb-list: /var/log/installer/hardware-summary
    usb-list:
    usb-list: Bus 01 Device 01: xHCI Host Controller [1d6b:0002]
    usb-list:    Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
    usb-list:    Manufacturer: Linux 6.1.0-9-amd64 xhci-hcd
    usb-list:    Interface 00: Class 09(hub  ) Subclass 00 Protocol 00
    Driver hub
    usb-list:
    usb-list: Bus 01 Device 04: USB Receiver [046d:c52b]
    usb-list:    Level 01 Parent 01 Port 12  Class 00(>ifc ) Subclass 00 Protocol 00
    usb-list:    Manufacturer: Logitech
    usb-list:    Interface 00: Class 03(HID  ) Subclass 01 Protocol 01
    Driver usbhid
    usb-list:    Interface 01: Class 03(HID  ) Subclass 01 Protocol 02
    Driver usbhid
    usb-list:    Interface 02: Class 03(HID  ) Subclass 00 Protocol 00
    Driver usbhid
    usb-list:
    usb-list: Bus 01 Device 05: USB Receiver [046d:c52f]
    usb-list:    Level 01 Parent 01 Port 13  Class 00(>ifc ) Subclass 00 Protocol 00
    usb-list:    Manufacturer: Logitech
    usb-list:    Interface 00: Class 03(HID  ) Subclass 01 Protocol 02
    Driver usbhid
    usb-list:    Interface 01: Class 03(HID  ) Subclass 00 Protocol 00
    Driver usbhid
    usb-list:
    usb-list: Bus 01 Device 03: USB2.0 Hub              [2109:2817] usb-list:    Level 01 Parent 01 Port 05  Class 09(hub  ) Subclass 00 Protocol 02
    usb-list:    Manufacturer: VIA Labs, Inc.
    usb-list:    Interface 00: Class 09(hub  ) Subclass 00 Protocol 02
    Driver hub
    usb-list:
    usb-list: Bus 01 Device 06: MFC-J6920DW [04f9:02f5]
    usb-list:    Level 02 Parent 03 Port 03  Class 00(>ifc ) Subclass 00 Protocol 00
    usb-list:    Manufacturer: Brother
    usb-list:    Interface 00: Class 07(print) Subclass 01 Protocol 02
    Driver <none>
    usb-list:    Interface 01: Class ff(vend.) Subclass ff Protocol ff
    Driver <none>
    usb-list:    Interface 02: Class ff(vend.) Subclass ff Protocol ff
    Driver <none>
    usb-list:    Interface 03: Class 08(mstor) Subclass 06 Protocol 50
    Driver usb-storage
    This above should not have been there unless it was read thru its ipv4
    address, the usb usb cable was unplugged. only the rx button for the
    wireless keyboard and mouse was plugged in.
    usb-list:
    usb-list: Bus 02 Device 01: xHCI Host Controller [1d6b:0003]
    usb-list:    Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 03
    usb-list:    Manufacturer: Linux 6.1.0-9-amd64 xhci-hcd
    usb-list:    Interface 00: Class 09(hub  ) Subclass 00 Protocol 00
    Driver hub
    usb-list:
    usb-list: Bus 02 Device 02: USB3.0 Hub              [2109:0817] usb-list:    Level 01 Parent 01 Port 05  Class 09(hub  ) Subclass 00 Protocol 03
    usb-list:    Manufacturer: VIA Labs, Inc.
    usb-list:    Interface 00: Class 09(hub  ) Subclass 00 Protocol 00
    Driver hub
    usb-list:
    usb-list: Bus 03 Device 01: xHCI Host Controller [1d6b:0002]
    usb-list:    Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
    usb-list:    Manufacturer: Linux 6.1.0-9-amd64 xhci-hcd
    usb-list:    Interface 00: Class 09(hub  ) Subclass 00 Protocol 00
    Driver hub
    usb-list:
    usb-list: Bus 04 Device 01: xHCI Host Controller [1d6b:0003]
    usb-list:    Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 03
    usb-list:    Manufacturer: Linux 6.1.0-9-amd64 xhci-hcd
    usb-list:    Interface 00: Class 09(hub  ) Subclass 00 Protocol 00
    Driver hub

    quite lengthy today, nearly 2 screens full and has 2 serial convertors,

    The hypothesis you agreed with (several times) is that the *installer* enables assistive technologies when it sees ftdi or a similar device.
    So the subject of my interest is state of hardware namely during
    install, not today. I suspect you forgot to disconnect some cable that
    time.

    Which I have consistently denied.
    ls /dev/tty*
    ditto

    Do you see anything related to ttyUSB or ftdi in
    /var/log/installer/syslog?

    Was screen reader active during install or it revealed itself later?

    I don't recall, the was 18 months ago.

    Cheers, Gene Heskett, CET.

    --
    "There are four boxes to be used in defense of liberty:
    soap, ballot, jury, and ammo. Please use in that order."
    -Ed Howdershelt (Author, 1940)
    If we desire respect for the law, we must first make the law respectable.
    - Louis D. Brandeis

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrew M.A. Cater@21:1/5 to gene heskett on Sun Dec 15 18:40:01 2024
    On Sun, Dec 15, 2024 at 12:08:36PM -0500, gene heskett wrote:

    On 12/15/24 09:48, Max Nikulin wrote:
    On 15/12/2024 20:27, gene heskett wrote:
    On 12/14/24 23:00, Max Nikulin wrote:
    áááá /var/log/installer/hardware-summary

    usb-list:
    usb-list: Bus 02 Device 01: xHCI Host Controller [1d6b:0003]
    usb-list:ááá Level 00 Parent 00 Port 00á Class 09(hubá ) Subclass 00 Protocol 03
    usb-list:ááá Manufacturer: Linux 6.1.0-9-amd64 xhci-hcd
    usb-list:ááá Interface 00: Class 09(hubá ) Subclass 00 Protocol 00
    Driver hub

    I don't know if this is a kernel that you built for yourself: current version should be somewhere closer to 6.1.0-28-amd64


    The hypothesis you agreed with (several times) is that the *installer* enables assistive technologies when it sees ftdi or a similar device. So the subject of my interest is state of hardware namely during install,
    not today. I suspect you forgot to disconnect some cable that time.


    As mentioned elsewhere in the thread, I think this was first mentioned
    some five years ago - https://lists.debian.org/debian-user/2019/05/msg01001.htmlat which point you are agreeing that this is a possibility and telling Curt
    as much

    Which I have consistently denied.

    I don't recall, the was 18 months ago.

    Cheers, Gene Heskett, CET.


    In the absence of a reinstall at any point, I might suggest that we
    kill this topic once and for all and leave it as not able to be solved?

    All the very best, as ever,

    Andy Cater
    (amacater@debian.org)
    --
    "There are four boxes to be used in defense of liberty:
    soap, ballot, jury, and ammo. Please use in that order."
    -Ed Howdershelt (Author, 1940)
    If we desire respect for the law, we must first make the law respectable.
    - Louis D. Brandeis


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From gene heskett@21:1/5 to Andrew M.A. Cater on Sun Dec 15 19:00:01 2024
    On 12/15/24 12:31, Andrew M.A. Cater wrote:
    On Sun, Dec 15, 2024 at 12:08:36PM -0500, gene heskett wrote:
    On 12/15/24 09:48, Max Nikulin wrote:
    On 15/12/2024 20:27, gene heskett wrote:
    On 12/14/24 23:00, Max Nikulin wrote:
         /var/log/installer/hardware-summary
    usb-list:
    usb-list: Bus 02 Device 01: xHCI Host Controller [1d6b:0003]
    usb-list:    Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 >>> Protocol 03
    usb-list:    Manufacturer: Linux 6.1.0-9-amd64 xhci-hcd
    usb-list:    Interface 00: Class 09(hub  ) Subclass 00 Protocol 00
    Driver hub
    I don't know if this is a kernel that you built for yourself: current version should be somewhere closer to 6.1.0-28-amd64

    The hypothesis you agreed with (several times) is that the *installer*
    enables assistive technologies when it sees ftdi or a similar device. So >>> the subject of my interest is state of hardware namely during install,
    not today. I suspect you forgot to disconnect some cable that time.

    As mentioned elsewhere in the thread, I think this was first mentioned
    some five years ago - https://lists.debian.org/debian-user/2019/05/msg01001.htmlat which point you are agreeing that this is a possibility and telling Curt
    as much

    Which I have consistently denied.

    I don't recall, the was 18 months ago.

    Cheers, Gene Heskett, CET.

    In the absence of a reinstall at any point, I might suggest that we
    kill this topic once and for all and leave it as not able to be solved?
    See the subject line Andy, I believe nuking suricata was the magic
    twanger. Hurray!!!!
    All the very best, as ever,

    Andy Cater
    (amacater@debian.org)
    --
    "There are four boxes to be used in defense of liberty:
    soap, ballot, jury, and ammo. Please use in that order."
    -Ed Howdershelt (Author, 1940)
    If we desire respect for the law, we must first make the law respectable.
    - Louis D. Brandeis

    .

    Cheers, Gene Heskett, CET.
    --
    "There are four boxes to be used in defense of liberty:
    soap, ballot, jury, and ammo. Please use in that order."
    -Ed Howdershelt (Author, 1940)
    If we desire respect for the law, we must first make the law respectable.
    - Louis D. Brandeis

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)