Re: Sierra Wireless MC7750 attaches as ugen(4) on OpenBSD 7.3 #1125 2023-March-25
On Wed, Apr 05, 2023 at 11:22:34PM +, Mikolaj Kucharski wrote: > On Wed, Apr 05, 2023 at 11:16:55PM +, miko...@kucharski.name wrote: > > >Synopsis: Sierra Wireless MC7750 attaches as ugen(4) > > >Category: kernel > > >Environment: > > System : OpenBSD 7.3 > > Details : OpenBSD 7.3 (GENERIC.MP) #1125: Sat Mar 25 10:36:29 MDT > > 2023 > > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > Sierra Wireless MC7750 attaches as ugen(4) on PC Engines APU3, > > running OpenBSD. Modem is mini-PCIe device. > > >How-To-Repeat: > > No specific steps. Plug in the device, boot up OpenBSD. > > >Fix: > > Unknown. > > > > Forgot to also add lsusb output. > > # lsusb -vvv -d 1199:68a2 > > Bus 002 Device 003: ID 1199:68a2 Sierra Wireless, Inc. > Device Descriptor: > bLength18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize064 > idVendor 0x1199 Sierra Wireless, Inc. > idProduct 0x68a2 > bcdDevice0.06 > iManufacturer 3 Sierra Wireless, Incorporated > iProduct2 MC7750 > iSerial 4 00102700999 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 115 > bNumInterfaces 4 > bConfigurationValue 1 > iConfiguration 1 Sierra Configuration > bmAttributes 0xe0 > Self Powered > Remote Wakeup > MaxPower0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber0 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass255 Vendor Specific Subclass > bInterfaceProtocol255 Vendor Specific Protocol > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 32 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x01 EP 1 OUT > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 32 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber2 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass255 Vendor Specific Subclass > bInterfaceProtocol255 Vendor Specific Protocol > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 32 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 EP 2 OUT > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 32 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber3 > bAlternateSetting 0 > bNumEndpoints 3 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass255 Vendor Specific Subclass > bInterfaceProtocol255 Vendor Specific Protocol > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes3 > Transfer TypeInterrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval
Re: Sierra Wireless MC7750 attaches as ugen(4) on OpenBSD 7.3 #1125 2023-March-25
On Thu, 2023-04-06 at 18:49 +1000, David Gwynne wrote: > On Wed, Apr 05, 2023 at 11:22:34PM +, Mikolaj Kucharski wrote: > > On Wed, Apr 05, 2023 at 11:16:55PM +, miko...@kucharski.name wrote: > > > > Synopsis: Sierra Wireless MC7750 attaches as ugen(4) > > > > Category: kernel > > > > Environment: > > > System : OpenBSD 7.3 > > > Details : OpenBSD 7.3 (GENERIC.MP) #1125: Sat Mar 25 10:36:29 > > > MDT 2023 > > > > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > Architecture: OpenBSD.amd64 > > > Machine : amd64 > > > > Description: > > > Sierra Wireless MC7750 attaches as ugen(4) on PC Engines APU3, > > > running OpenBSD. Modem is mini-PCIe device. > > > > How-To-Repeat: > > > No specific steps. Plug in the device, boot up OpenBSD. > > > > Fix: > > > Unknown. > > > > > > > Forgot to also add lsusb output. > > > > # lsusb -vvv -d 1199:68a2 > > > > Bus 002 Device 003: ID 1199:68a2 Sierra Wireless, Inc. > > Device Descriptor: > > bLength 18 > > bDescriptorType 1 > > bcdUSB 2.00 > > bDeviceClass 0 (Defined at Interface level) > > bDeviceSubClass 0 > > bDeviceProtocol 0 > > bMaxPacketSize0 64 > > idVendor 0x1199 Sierra Wireless, Inc. > > idProduct 0x68a2 > > bcdDevice 0.06 > > iManufacturer 3 Sierra Wireless, Incorporated > > iProduct 2 MC7750 > > iSerial 4 00102700999 > > bNumConfigurations 1 > > Configuration Descriptor: > > bLength 9 > > bDescriptorType 2 > > wTotalLength 115 > > bNumInterfaces 4 > > bConfigurationValue 1 > > iConfiguration 1 Sierra Configuration > > bmAttributes 0xe0 > > Self Powered > > Remote Wakeup > > MaxPower 0mA > > Interface Descriptor: > > bLength 9 > > bDescriptorType 4 > > bInterfaceNumber 0 > > bAlternateSetting 0 > > bNumEndpoints 2 > > bInterfaceClass 255 Vendor Specific Class > > bInterfaceSubClass 255 Vendor Specific Subclass > > bInterfaceProtocol 255 Vendor Specific Protocol > > iInterface 0 > > Endpoint Descriptor: > > bLength 7 > > bDescriptorType 5 > > bEndpointAddress 0x81 EP 1 IN > > bmAttributes 2 > > Transfer Type Bulk > > Synch Type None > > Usage Type Data > > wMaxPacketSize 0x0200 1x 512 bytes > > bInterval 32 > > Endpoint Descriptor: > > bLength 7 > > bDescriptorType 5 > > bEndpointAddress 0x01 EP 1 OUT > > bmAttributes 2 > > Transfer Type Bulk > > Synch Type None > > Usage Type Data > > wMaxPacketSize 0x0200 1x 512 bytes > > bInterval 32 > > Interface Descriptor: > > bLength 9 > > bDescriptorType 4 > > bInterfaceNumber 2 > > bAlternateSetting 0 > > bNumEndpoints 2 > > bInterfaceClass 255 Vendor Specific Class > > bInterfaceSubClass 255 Vendor Specific Subclass > > bInterfaceProtocol 255 Vendor Specific Protocol > > iInterface 0 > > Endpoint Descriptor: > > bLength 7 > > bDescriptorType 5 > > bEndpointAddress 0x82 EP 2 IN > > bmAttributes 2 > > Transfer Type Bulk > > Synch Type None > > Usage Type Data > > wMaxPacketSize 0x0200 1x 512 bytes > > bInterval 32 > > Endpoint Descriptor: > > bLength 7 > > bDescriptorType 5 > > bEndpointAddress 0x02 EP 2 OUT > > bmAttributes 2 > > Transfer Type Bulk > > Synch Type None > > Usage Type Data > > wMaxPacketSize 0x0200 1x 512 bytes > > bInterval 32 > > Interface Descriptor: > > bLength 9 > > bDescriptorType 4 > > bInterfaceNumber 3 > > bAlternateSetting 0 > > bNumEndpoints 3 > > bInterfaceClass 255 Vendor Specific Class > > bInterfaceSubClass 255 Vendor Specific Subclass > > bInterfaceProtocol 255 Vendor Specific Protocol > > iInterface 0 > > Endpoint Descriptor: > > b
Re: Sierra Wireless MC7750 attaches as ugen(4) on OpenBSD 7.3 #1125 2023-March-25
On Thu, Apr 06, 2023 at 09:13:27AM +, Gerhard Roth wrote:
> On Thu, 2023-04-06 at 18:49 +1000, David Gwynne wrote:
> > On Wed, Apr 05, 2023 at 11:22:34PM +, Mikolaj Kucharski wrote:
> >
> > this is almost certainly a qualcomm msm interface (qmi) device.
> > making umsm(4) attach to it is a good first start.
> >
> > hopefully you'll be able to talk AT commands to one of the interfaces.
> >
> > qmi devices are notoriously inconsistent and complicated, so what to do
> > next isnt clear. i would be trying to tell the modem to switch to mbim
> > mode and then figure out how to get umb(4) to attach. this is similar to
> > the changes i made to umsm and umb for quectel devices, but they
> > actually provided a decent manual.
>
> The Sierra Wireless documentation is available. Alas, switching the
> mode seems far too complex and error prone to perform this inside
> a driver.
agreed. i just want the kernel to attach the right things to what is
presented.
> When the AT (modem) interface is available, you would have to:
>
> 1) enter password protected command mode with "AT!ENTERCND=passwd"
>
> 2) query the list of modes with "AT!UDUSBCOMP=?". Example result:
>
> 0 - reserved NOT SUPPORTED
> 1 - DM AT SUPPORTED
> 2 - reserved NOT SUPPORTED
> 3 - reserved NOT SUPPORTED
> 4 - reserved NOT SUPPORTED
> 5 - reserved NOT SUPPORTED
> 6 - DM NMEA ATQMI SUPPORTED
> 7 - DM NMEA ATRMNET1 RMNET2 RMNET3SUPPORTED
> 8 - DM NMEA ATMBIMSUPPORTED
> 9 - MBIM SUPPORTED
> 10 - NMEA MBIMSUPPORTED
> 11 - DM MBIMSUPPORTED
> 12 - DM NMEA MBIM SUPPORTED
> 13 - Config1: comp6Config2: comp8 NOT SUPPORTED
> 14 - Config1: comp6Config2: comp9 SUPPORTED
> 15 - Config1: comp6Config2: comp10NOT SUPPORTED
> 16 - Config1: comp6Config2: comp11NOT SUPPORTED
> 17 - Config1: comp6Config2: comp12NOT SUPPORTED
> 18 - Config1: comp7Config2: comp8 NOT SUPPORTED
> 19 - Config1: comp7Config2: comp9 SUPPORTED
> 20 - Config1: comp7Config2: comp10NOT SUPPORTED
> 21 - Config1: comp7Config2: comp11NOT SUPPORTED
> 22 - Config1: comp7Config2: comp12NOT SUPPORTED
>
> There is no guarantee that the table doesn't change. And every
> device has a differnt set of supported modes.
>
> 3) select the desired mode with "AT!UDUSBCOMP=X"
> 4) wait for the device to reset itself
yep.
the linux driver has some clues, so the following should let umb attach
once you've reconfigured the modem.
Index: umsm.c
===
RCS file: /cvs/src/sys/dev/usb/umsm.c,v
retrieving revision 1.125
diff -u -p -r1.125 umsm.c
--- umsm.c 2 Apr 2023 23:57:57 - 1.125
+++ umsm.c 6 Apr 2023 09:21:35 -
@@ -101,6 +101,7 @@ struct umsm_type {
#defineDEV_NORMAL 0x
#defineDEV_HUAWEI 0x0001
#defineDEV_TRUINSTALL 0x0002
+#defineDEV_SIERRA 0x0004
#defineDEV_UMASS1 0x0010
#defineDEV_UMASS2 0x0020
#defineDEV_UMASS3 0x0040
@@ -271,6 +272,7 @@ static const struct umsm_type umsm_devs[
{{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_AIRCARD_340U}, 0},
{{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_AIRCARD_770S}, 0},
{{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_MC7455}, 0},
+ {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_MC7700}, DEV_SIERRA},
{{ USB_VENDOR_SIMCOM, USB_PRODUCT_SIMCOM_SIM5320}, 0},
{{ USB_VENDOR_SIMCOM, USB_PRODUCT_SIMCOM_SIM7600E}, 0},
@@ -363,6 +365,17 @@ umsm_match(struct device *parent, void *
/* Interface 4 can be used as a network device */
if (uaa->ifaceno >= 4)
return UMATCH_NONE;
+ } else if (flag & DEV_SIERRA) {
+ /* Sierra Wireless layout */
+ switch (uaa->ifaceno) {
+ case 0:
+ case 2:
+ case 3:
+ /* Only umsm on specific interfaces */
+ break;
+ default:
+ return UMATCH_NONE;
+ }
}
return UMATCH_VENDOR_IFACESUBCLASS;
Re: Sierra Wireless MC7750 attaches as ugen(4) on OpenBSD 7.3 #1125 2023-March-25
On 2023/04/06 09:13, Gerhard Roth wrote:
> 2) query the list of modes with "AT!UDUSBCOMP=?". Example result:
>
> 0 - reserved NOT SUPPORTED
> 1 - DM AT SUPPORTED
> 2 - reserved NOT SUPPORTED
> 3 - reserved NOT SUPPORTED
> 4 - reserved NOT SUPPORTED
> 5 - reserved NOT SUPPORTED
> 6 - DM NMEA ATQMI SUPPORTED
> 7 - DM NMEA ATRMNET1 RMNET2 RMNET3SUPPORTED
> 8 - DM NMEA ATMBIMSUPPORTED
> 9 - MBIM SUPPORTED
> 10 - NMEA MBIMSUPPORTED
> 11 - DM MBIMSUPPORTED
> 12 - DM NMEA MBIM SUPPORTED
> 13 - Config1: comp6Config2: comp8 NOT SUPPORTED
> 14 - Config1: comp6Config2: comp9 SUPPORTED
> 15 - Config1: comp6Config2: comp10NOT SUPPORTED
> 16 - Config1: comp6Config2: comp11NOT SUPPORTED
> 17 - Config1: comp6Config2: comp12NOT SUPPORTED
> 18 - Config1: comp7Config2: comp8 NOT SUPPORTED
> 19 - Config1: comp7Config2: comp9 SUPPORTED
> 20 - Config1: comp7Config2: comp10NOT SUPPORTED
> 21 - Config1: comp7Config2: comp11NOT SUPPORTED
> 22 - Config1: comp7Config2: comp12NOT SUPPORTED
>
> There is no guarantee that the table doesn't change. And every
> device has a differnt set of supported modes.
>
> 3) select the desired mode with "AT!UDUSBCOMP=X"
Take care with this. You can put the modem in a mode where you no
longer have an AT interface to be able to reset it (there maybe
a different way to reset it via USB commands rather than AT commands,
but that won't be straightforward from OpenBSD).
> 4) wait for the device to reset itself
>
> >
> > Index: umsm.c
> > ===
> > RCS file: /cvs/src/sys/dev/usb/umsm.c,v
> > retrieving revision 1.125
> > diff -u -p -r1.125 umsm.c
> > --- umsm.c 2 Apr 2023 23:57:57 - 1.125
> > +++ umsm.c 6 Apr 2023 08:40:30 -
> > @@ -271,6 +271,7 @@ static const struct umsm_type umsm_devs[
> > {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_AIRCARD_340U}, 0},
> > {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_AIRCARD_770S}, 0},
> > {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_MC7455}, 0},
> > + {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_MC7700}, 0},
> >
> > {{ USB_VENDOR_SIMCOM, USB_PRODUCT_SIMCOM_SIM5320}, 0},
> > {{ USB_VENDOR_SIMCOM, USB_PRODUCT_SIMCOM_SIM7600E}, 0},
> >
>
Re: Sierra Wireless MC7750 attaches as ugen(4) on OpenBSD 7.3 #1125 2023-March-25
On Thu, 2023-04-06 at 11:15 +, Mikolaj Kucharski wrote:
> On Thu, Apr 06, 2023 at 09:13:27AM +, Gerhard Roth wrote:
> >
> > The Sierra Wireless documentation is available. Alas, switching the
> > mode seems far too complex and error prone to perform this inside
> > a driver.
> >
> > When the AT (modem) interface is available, you would have to:
> >
> > 1) enter password protected command mode with "AT!ENTERCND=passwd"
> >
> > 2) query the list of modes with "AT!UDUSBCOMP=?". Example result:
> >
> > 0 - reserved NOT SUPPORTED
> > 1 - DM AT SUPPORTED
> > 2 - reserved NOT SUPPORTED
> > 3 - reserved NOT SUPPORTED
> > 4 - reserved NOT SUPPORTED
> > 5 - reserved NOT SUPPORTED
> > 6 - DM NMEA AT QMI SUPPORTED
> > 7 - DM NMEA AT RMNET1 RMNET2 RMNET3 SUPPORTED
> > 8 - DM NMEA AT MBIM SUPPORTED
> > 9 - MBIM SUPPORTED
> > 10 - NMEA MBIM SUPPORTED
> > 11 - DM MBIM SUPPORTED
> > 12 - DM NMEA MBIM SUPPORTED
> > 13 - Config1: comp6 Config2: comp8 NOT SUPPORTED
> > 14 - Config1: comp6 Config2: comp9 SUPPORTED
> > 15 - Config1: comp6 Config2: comp10 NOT SUPPORTED
> > 16 - Config1: comp6 Config2: comp11 NOT SUPPORTED
> > 17 - Config1: comp6 Config2: comp12 NOT SUPPORTED
> > 18 - Config1: comp7 Config2: comp8 NOT SUPPORTED
> > 19 - Config1: comp7 Config2: comp9 SUPPORTED
> > 20 - Config1: comp7 Config2: comp10 NOT SUPPORTED
> > 21 - Config1: comp7 Config2: comp11 NOT SUPPORTED
> > 22 - Config1: comp7 Config2: comp12 NOT SUPPORTED
> >
> > There is no guarantee that the table doesn't change. And every
> > device has a differnt set of supported modes.
> >
> > 3) select the desired mode with "AT!UDUSBCOMP=X"
> > 4) wait for the device to reset itself
>
> So, I am not sure do I understand the output right, but is this modem
> already in correct mode?
Well "correct" depends on what you want ;)
Mode 6 offers AT mode (meaning you have a modem to control with AT-
commands) and QMI. Sadly, none of the supported modes includes
an MBIM (umb) interface. So mode 6 is probably the best one you can pick.
>
>
> AT!ENTERCND="A710"
> OK
> AT!UDUSBCOMP=?
> 0 - HIP DM NMEA AT MDM1 MDM2 MDM3 MS NOT SUPPORTED
> 1 - HIP DM NMEA AT MDM1 MS NOT SUPPORTED
> 2 - HIP DM NMEA AT NIC1 MS NOT SUPPORTED
> 3 - HIP DM NMEA AT MDM1 NIC1 MS NOT SUPPORTED
> 4 - HIP DM NMEA AT NIC1 NIC2 NIC3 MS NOT SUPPORTED
> 5 - HIP DM NMEA AT ECM1 MS NOT SUPPORTED
> 6 - DM NMEA AT QMI SUPPORTED
> 7 - DM NMEA AT RMNET1 RMNET2 RMNET3 SUPPORTED
> 8 - Win8 Std Net SUPPORTED
>
>
> OK
> AT!UDUSBCOMP?
> !UDUSBCOMP: 6
>
> OK
>
>
> That is on kernel with the below diff applied - on line change to umsm.c
>
> # dmesg
> ...
> umsm0 at uhub4 port 3 configuration 1 interface 0 "Sierra Wireless,
> Incorporated MC7750" rev 2.00/0.06 addr 3
> ucom0 at umsm0
> umsm1 at uhub4 port 3 configuration 1 interface 2 "Sierra Wireless,
> Incorporated MC7750" rev 2.00/0.06 addr 3
> ucom1 at umsm1
> umsm2 at uhub4 port 3 configuration 1 interface 3 "Sierra Wireless,
> Incorporated MC7750" rev 2.00/0.06 addr 3
> ucom2 at umsm2
> umsm3 at uhub4 port 3 configuration 1 interface 8 "Sierra Wireless,
> Incorporated MC7750" rev 2.00/0.06 addr 3
> ucom3 at umsm3
>
>
> > >
> > > Index: umsm.c
> > > ===
> > > RCS file: /cvs/src/sys/dev/usb/umsm.c,v
> > > retrieving revision 1.125
> > > diff -u -p -r1.125 umsm.c
> > > --- umsm.c 2 Apr 2023 23:57:57 - 1.125
> > > +++ umsm.c 6 Apr 2023 08:40:30 -
> > > @@ -271,6 +271,7 @@ static const struct umsm_type umsm_devs[
> > > {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_AIRCARD_340U}, 0},
> > > {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_AIRCARD_770S}, 0},
> > > {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_MC7455}, 0},
> > > + {{ USB_VENDOR_SIERRA, USB_PRODUCT_SIERRA_MC7700}, 0},
> > >
> > > {{ USB_VENDOR_SIMCOM, USB_PRODUCT_SIMCOM_SIM5320}, 0},
> > > {{ USB_VENDOR_SIMCOM, USB_PRODUCT_SIMCOM_SIM7600E}, 0},
> > >
> >
>
smime.p7s
Description: S/MIME cryptographic signature
Re: Sierra Wireless MC7750 attaches as ugen(4) on OpenBSD 7.3 #1125 2023-March-25
On Thu, 2023-04-06 at 11:51 +, Mikolaj Kucharski wrote: > On Thu, Apr 06, 2023 at 11:40:06AM +, Gerhard Roth wrote: > > On Thu, 2023-04-06 at 11:15 +, Mikolaj Kucharski wrote: > > > > > > So, I am not sure do I understand the output right, but is this modem > > > already in correct mode? > > > > Well "correct" depends on what you want ;) > > > > Mode 6 offers AT mode (meaning you have a modem to control with AT- > > commands) and QMI. Sadly, none of the supported modes includes > > an MBIM (umb) interface. So mode 6 is probably the best one you can pick. > > Ah, sorry. I got confused by all those abbreviations. The device umb(4) > is MBIM and not QMI. Yeah, I see what you mean. > > Basically there is nothing more to do here? Then my option to have an > internet via that modem is pppd(8) on /dev/cueU2 ? I don't know what kind of mode is supplied by "Win8 Std Net". But from the others listed, I'm afraid that is correct. pppd(8)/chat(8) is what you need. > > > > > > > > > > AT!ENTERCND="A710" > > > OK > > > AT!UDUSBCOMP=? > > > 0 - HIP DM NMEA AT MDM1 MDM2 MDM3 MS NOT SUPPORTED > > > 1 - HIP DM NMEA AT MDM1 MS NOT SUPPORTED > > > 2 - HIP DM NMEA AT NIC1 MS NOT SUPPORTED > > > 3 - HIP DM NMEA AT MDM1 NIC1 MS NOT SUPPORTED > > > 4 - HIP DM NMEA AT NIC1 NIC2 NIC3 MS NOT SUPPORTED > > > 5 - HIP DM NMEA AT ECM1 MS NOT SUPPORTED > > > 6 - DM NMEA AT QMI SUPPORTED > > > 7 - DM NMEA AT RMNET1 RMNET2 RMNET3 SUPPORTED > > > 8 - Win8 Std Net SUPPORTED > > > > > > > > > OK > > > AT!UDUSBCOMP? > > > !UDUSBCOMP: 6 > > > > > > OK > > > > smime.p7s Description: S/MIME cryptographic signature
Re: Sierra Wireless MC7750 attaches as ugen(4) on OpenBSD 7.3 #1125 2023-March-25
On Thu, 2023-04-06 at 11:59 +, Gerhard Roth wrote: > On Thu, 2023-04-06 at 11:51 +, Mikolaj Kucharski wrote: > > On Thu, Apr 06, 2023 at 11:40:06AM +, Gerhard Roth wrote: > > > On Thu, 2023-04-06 at 11:15 +, Mikolaj Kucharski wrote: > > > > > > > > So, I am not sure do I understand the output right, but is this modem > > > > already in correct mode? > > > > > > Well "correct" depends on what you want ;) > > > > > > Mode 6 offers AT mode (meaning you have a modem to control with AT- > > > commands) and QMI. Sadly, none of the supported modes includes > > > an MBIM (umb) interface. So mode 6 is probably the best one you can pick. > > > > Ah, sorry. I got confused by all those abbreviations. The device umb(4) > > is MBIM and not QMI. Yeah, I see what you mean. > > > > Basically there is nothing more to do here? Then my option to have an > > internet via that modem is pppd(8) on /dev/cueU2 ? > > I don't know what kind of mode is supplied by "Win8 Std Net". But from > the others listed, I'm afraid that is correct. pppd(8)/chat(8) is what > you need. But I might stand corrected after googling a little bit: https://techship.com/faq/how-to-change-usb-interface-using-atusbcomp-on-sierra-wireless-modules/ says that MC7750 uses "AT!USBCOMP" instead of "AT!UDUSBCOMP" to switch modes. Maybe that'll help. > > > > > > > > > > > > > > > > AT!ENTERCND="A710" > > > > OK > > > > AT!UDUSBCOMP=? > > > > 0 - HIP DM NMEA AT MDM1 MDM2 MDM3 MS NOT SUPPORTED > > > > 1 - HIP DM NMEA AT MDM1 MS NOT SUPPORTED > > > > 2 - HIP DM NMEA AT NIC1 MS NOT SUPPORTED > > > > 3 - HIP DM NMEA AT MDM1 NIC1 MS NOT SUPPORTED > > > > 4 - HIP DM NMEA AT NIC1 NIC2 NIC3 MS NOT SUPPORTED > > > > 5 - HIP DM NMEA AT ECM1 MS NOT SUPPORTED > > > > 6 - DM NMEA AT QMI SUPPORTED > > > > 7 - DM NMEA AT RMNET1 RMNET2 RMNET3 SUPPORTED > > > > 8 - Win8 Std Net SUPPORTED > > > > > > > > > > > > OK > > > > AT!UDUSBCOMP? > > > > !UDUSBCOMP: 6 > > > > > > > > OK > > > > > > > smime.p7s Description: S/MIME cryptographic signature
Can't record audio from USB microphone
>Synopsis:Can't record audio from USB microphone >Category:system >Environment: System : OpenBSD 7.2 Details : OpenBSD 7.2 (GENERIC.MP) #7: Sat Feb 25 14:07:58 MST 2023 r...@syspatch-72-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture: OpenBSD.amd64 Machine : amd64 >Description: On a Lenovo ThinkPad T440P, can't start recording any audio from a guitar amp (that "acts" like a regular USB microphone for the sake of audio recording) via aucat or any other software with errors "can't set interface" and "audio device gone, stopping" >How-To-Repeat: 1. Connect USB microphone (USB guitar amp in this case) to the computer via a USB 2.0 port and power it up. Everything pops up as expected in dmesg, the device is uaudio0 (audio1, "Mustang LT 40S"). 2. Start a test recording with aucat (it's under snd/1 in this case): $ aucat -f snd/1 -o recording.wav 3. Immediately see two errors spewed out to dmesg: uaudio0: can't set interface audio1: failed to start recording and another one thrown by aucat itself: snd/1: audio device gone, stopping after which aucat closes. >Fix: Not known, though I don't own an _actual_ USB microphone to re-test with. The internal laptop microphone at snd/0 works well. dmesg: OpenBSD 7.2 (GENERIC.MP) #7: Sat Feb 25 14:07:58 MST 2023 r...@syspatch-72-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8445980672 (8054MB) avail mem = 8172601344 (7794MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbcc0d000 (67 entries) bios0: vendor LENOVO version "GLETA2WW (2.56 )" date 07/16/2021 bios0: LENOVO 20AWS1BL1C acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC DBGP ECDT HPET APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT TCPA UEFI MSDM ASF! BATB FPDT UEFI acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) EXP3(S4) XHCI(S3) EHC1(S3) EHC2(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2394.49 MHz, 06-3c-03 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 6MB 64b/line 12-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2394.46 MHz, 06-3c-03 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 6MB 64b/line 12-way L3 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2394.46 MHz, 06-3c-03 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 6MB 64b/line 12-way L3 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2394.46 MHz, 06-3c-03 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SRBD
Re: Can't record audio from USB microphone
On Thu, Apr 6, 2023, at 4:32 PM, Bruno wrote: >>Synopsis:Can't record audio from USB microphone >>Category:system >>Environment: > System : OpenBSD 7.2 > Details : OpenBSD 7.2 (GENERIC.MP) #7: Sat Feb 25 14:07:58 MST > 2023 > > r...@syspatch-72-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > Architecture: OpenBSD.amd64 > Machine : amd64 >>Description: > On a Lenovo ThinkPad T440P, can't start recording any audio from a > guitar amp (that "acts" like a regular USB microphone for the sake of > audio recording) via aucat or any other software with errors "can't > set interface" and "audio device gone, stopping" >>How-To-Repeat: > 1. Connect USB microphone (USB guitar amp in this case) to the > computer via a USB 2.0 port and power it up. Everything pops up as > expected in dmesg, the device is uaudio0 (audio1, "Mustang LT 40S"). > 2. Start a test recording with aucat (it's under snd/1 in this case): > $ aucat -f snd/1 -o recording.wav > 3. Immediately see two errors spewed out to dmesg: > uaudio0: can't set interface > audio1: failed to start recording > and another one thrown by aucat itself: > snd/1: audio device gone, stopping > after which aucat closes. Did you enable the recording sysctl? https://www.openbsd.org/faq/faq13.html#enablerec Brian Conway
Re: Can't record audio from USB microphone
Hi, thanks for the quick response. I did, and added it to sysctl.conf On Thu, 6 Apr 2023 at 23:54, Bruno wrote: > > Hi, thanks for the quick response. > I did, and added it to sysctl.conf > > On Thu, 6 Apr 2023 at 23:43, Brian Conway wrote: > > > > On Thu, Apr 6, 2023, at 4:32 PM, Bruno wrote: > > >>Synopsis:Can't record audio from USB microphone > > >>Category:system > > >>Environment: > > > System : OpenBSD 7.2 > > > Details : OpenBSD 7.2 (GENERIC.MP) #7: Sat Feb 25 14:07:58 MST > > > 2023 > > > > > > r...@syspatch-72-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > > > Architecture: OpenBSD.amd64 > > > Machine : amd64 > > >>Description: > > > On a Lenovo ThinkPad T440P, can't start recording any audio from a > > > guitar amp (that "acts" like a regular USB microphone for the sake of > > > audio recording) via aucat or any other software with errors "can't > > > set interface" and "audio device gone, stopping" > > >>How-To-Repeat: > > > 1. Connect USB microphone (USB guitar amp in this case) to the > > > computer via a USB 2.0 port and power it up. Everything pops up as > > > expected in dmesg, the device is uaudio0 (audio1, "Mustang LT 40S"). > > > 2. Start a test recording with aucat (it's under snd/1 in this case): > > > $ aucat -f snd/1 -o recording.wav > > > 3. Immediately see two errors spewed out to dmesg: > > > uaudio0: can't set interface > > > audio1: failed to start recording > > > and another one thrown by aucat itself: > > > snd/1: audio device gone, stopping > > > after which aucat closes. > > > > Did you enable the recording sysctl? > > > > https://www.openbsd.org/faq/faq13.html#enablerec > > > > Brian Conway
