Re: Keyboard won't work during OpenBSD 7.1 or 7.2 installation.

[Kevin Lo]

Hi Clint,

As mentioned in a private email, you need to disable acpimadt and mpbios
in the kernel to make it work.  Why don't you give it a try?

Also see: https://marc.info/?l=openbsd-bugs=165170229727676=2

On Wed, Nov 23, 2022 at 09:48:24AM +0800, Clint wrote:
> 
> Hi Fred,
> 
> I tried at specific point, but still not working. 
> Same problem remains when I use other keyboard.
> 
> On the other side, when I install OpenBSD on another Intel PC is working 
> fine. It seems there is compatible issue with DMP???s EBOX-336x mini PC, when 
> I tried OpenBSD direct installation.
> 
> Is there any BIOS setting (I mean in general) I should be aware of? Please 
> advise, thank you. 
> 
> Regards,
> Clint 
> 
> -Original Message-
> From: Fred Crowson  
> Sent: Tuesday, November 22, 2022 10:04 PM
> To: Clint 
> Cc: misc@openbsd.org
> Subject: Re: Keyboard won't work during OpenBSD 7.1 or 7.2 installation.
> 
> if you plug in a USB keyboard at that point it will probably be recognised so 
> that you can use it for the install.
> 
> hth
> 
> Fred
> 
> On Tue, 22 Nov 2022 at 06:19, Clint  wrote:
> >
> > Dear Sirs,
> >
> >
> >
> > My name is Clint Wu, I had been told the DMP???s EBOX-336x mini PC 
> > (product page  ) 
> > can run OpenBSD 7.1.
> >
> > I had downloaded install71.img & install72.img ad use rufus 3.20 to 
> > crate USB installer.
> >
> > When I boot up my mini PC till installation program show up as below 
> > picture.
> >
> > My keyboard stop working at this stage. Did any one report this 
> > problem before?
> >
> > Can you tell me how to solve this? what should I do nextPlease 
> > advise, thank you.
> >
> >
> >
> >
> >
> > Regards,
> > Clint
> >
> >
> >
> 

Re: sim7600 4g modem

[Kevin Lo]

On Fri, Sep 24, 2021 at 12:19:35PM +0800, Kevin Lo wrote:
> 
> On Fri, Sep 03, 2021 at 10:08:52PM +, Cord wrote:
> > 
> > 
> > 
> > >
> > > It looks like it is probably a Qualcomm-based device. It seems likely
> > >
> > > that as things are now, it will attach to umsm. I can't say for sure if
> > >
> > > it will work or not though I think there is a fairly good chance.
> > >
> > > But unless you are lucky and somebody already used the same device,
> > >
> > > you will need to buy one to find out for sure.
> > >
> > > If it does work, while attached to umsm there should be several com
> > >
> > > interfaces presented, one of which is likely to accept AT commands
> > >
> > > so you can find strength that way. For umsm, you will need to mess
> > >
> > > about with pppd to get it to connect to the internet.
> > >
> > > The device would probably support working with umb(4) but would need
> > >
> > > some extra work (maybe as simple as moving the vendor/product ID to 
> > > umb(4),
> > >
> > > but it may need more...so far I have a success rate of about 33% with umb
> > >
> > > devices, including some devices which are even listed in the manpage -
> > >
> > > the firmware on the device matters too, not just the chipset).
> > >
> > > There is no support for displaying signal strength directly via umb,
> > >
> > > and the other com ports are only available via umsm, so in that case you
> > >
> > > can't send AT commands to find it either..
> > >
> > > This device is cat4 only (no MIMO, no channel aggregation) so speed won't
> > >
> > > be amazing.
> > >
> > 
> > 
> > Hello, thank you very much for your help.
> > I bought the toy and it seems it works, but it stuck when I run fw_update 
> > at around 10% or 20%. In the log I found messages like:
> > ppp0: bad fcs 59f8
> > ppp0: bad protocol 728a
> > ppp0: packet too big
> > ppp0: bad fcs baf0
> > ppp0: bad protocol debc
> > ppp0: bad fcs and so on.
> > 
> > The strange thing is that when I press ctrl+c to break the ppp connection I 
> > lose all the connections I have with box. I mean lan and serial connections.
> > I don't know if the box is stucked or it's just the connection. But I find 
> > very strange that I lose the serial connection. Obviously the box is 
> > headless. It's just a simple
> > raspberry.
> > FCS stand for "Frame Check Sequence" and it seems a kind of ppp checksum.
> > Maybe I'm in a spot where the signal is weak. I'll try to move the dongle.
> 
> I got mine yesterday.  As sthen@ pointed out, this device would support 
> working with umb(4).  Using the following AT commands to switch into mbim 
> mode:
> 
> AT+CUSBPIDSWITCH=9003,1,1
> AT+CLANMODE=1
> 
> You also need to apply the following diff, thanks.

Index: sys/dev/usb/if_umb.c
===
RCS file: /cvs/src/sys/dev/usb/if_umb.c,v
retrieving revision 1.46
diff -u -p -u -p -r1.46 if_umb.c
--- sys/dev/usb/if_umb.c4 Jul 2021 19:22:31 -   1.46
+++ sys/dev/usb/if_umb.c24 Sep 2021 01:12:24 -
@@ -256,6 +256,12 @@ const struct umb_quirk umb_quirks[] = {
  0,
  0
},
+
+   { { USB_VENDOR_SIMCOM, USB_PRODUCT_SIMCOM_SIM7600 },
+ 0,
+ 1,
+ UMATCH_VENDOR_PRODUCT
+   },
 };
 
 #define umb_lookup(vid, pid)   \
Index: sys/dev/usb/usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.741
diff -u -p -u -p -r1.741 usbdevs
--- sys/dev/usb/usbdevs 31 Aug 2021 22:55:56 -  1.741
+++ sys/dev/usb/usbdevs 24 Sep 2021 01:12:24 -
@@ -4123,6 +4123,7 @@ product SILICONPORTALS YAPPHONE   0x0201  Y
 
 /* Simcom products */
 product SIMCOM SIM7600E0x9001  SIM7600E modem
+product SIMCOM SIM7600 0x9003  SIM7600 LTE
 
 /* Sirius Technologies products */
 product SIRIUS ROADSTER0x0001  NetComm Roadster II 56

Re: sim7600 4g modem

[Kevin Lo]

On Fri, Sep 03, 2021 at 10:08:52PM +, Cord wrote:
> 
> 
> 
> >
> > It looks like it is probably a Qualcomm-based device. It seems likely
> >
> > that as things are now, it will attach to umsm. I can't say for sure if
> >
> > it will work or not though I think there is a fairly good chance.
> >
> > But unless you are lucky and somebody already used the same device,
> >
> > you will need to buy one to find out for sure.
> >
> > If it does work, while attached to umsm there should be several com
> >
> > interfaces presented, one of which is likely to accept AT commands
> >
> > so you can find strength that way. For umsm, you will need to mess
> >
> > about with pppd to get it to connect to the internet.
> >
> > The device would probably support working with umb(4) but would need
> >
> > some extra work (maybe as simple as moving the vendor/product ID to umb(4),
> >
> > but it may need more...so far I have a success rate of about 33% with umb
> >
> > devices, including some devices which are even listed in the manpage -
> >
> > the firmware on the device matters too, not just the chipset).
> >
> > There is no support for displaying signal strength directly via umb,
> >
> > and the other com ports are only available via umsm, so in that case you
> >
> > can't send AT commands to find it either..
> >
> > This device is cat4 only (no MIMO, no channel aggregation) so speed won't
> >
> > be amazing.
> >
> 
> 
> Hello, thank you very much for your help.
> I bought the toy and it seems it works, but it stuck when I run fw_update at 
> around 10% or 20%. In the log I found messages like:
> ppp0: bad fcs 59f8
> ppp0: bad protocol 728a
> ppp0: packet too big
> ppp0: bad fcs baf0
> ppp0: bad protocol debc
> ppp0: bad fcs and so on.
> 
> The strange thing is that when I press ctrl+c to break the ppp connection I 
> lose all the connections I have with box. I mean lan and serial connections.
> I don't know if the box is stucked or it's just the connection. But I find 
> very strange that I lose the serial connection. Obviously the box is 
> headless. It's just a simple
> raspberry.
> FCS stand for "Frame Check Sequence" and it seems a kind of ppp checksum.
> Maybe I'm in a spot where the signal is weak. I'll try to move the dongle.

I got mine yesterday.  As sthen@ pointed out, this device would support working 
with umb(4).  Using the following AT commands to switch into mbim mode:

AT+CUSBPIDSWITCH=9003,1,1
AT+CLANMODE=1

You also need to apply the following diff, thanks.
> Cord

Re: OpenCV on 6.9 can't open camera

[Kevin Lo]

On Mon, Aug 09, 2021 at 11:56:36AM -0600, Jeff Ross wrote:
> 
> Hi,
> 
> I'm porting a python3 program I wrote for capturing jpegs from a USB based
> webcam, using OpenCV for capture and post-processing.?? I was running this
> on a RaspberryPi 3B+ under linux but I'm sick of battling crappy hardware
> and linux so I bought a Mini PC stick and installed 6.9.?? (dmesg follows)
> 
> OpenCV (installed from the package) doesn't seem to be able to open the
> camera. The camera (in this case for testing a Logitech C910) can be
> accessed no problem with ffplay, fswebcam and video(1).?? I also opened the
> kern sysctls for both audio and video and chowned /dev/video to my user.
> 
> jross@aurora-cam:/home/jross $ fswebcam?? -d v4l2:/dev/video0 -F3 --save
> test2.jpg
> --- Opening v4l2:/dev/video0...
> /dev/video0 opened.
> No input was specified, using the first.
> Adjusting resolution from 384x288 to 432x240.
> --- Capturing 3 frames...
> Captured 3 frames in 0.06 seconds. (46 fps)
> --- Processing captured image...
> Writing JPEG image to 'test2.jpg'.
> 
> OpenCV not so much though:
> 
> jross@aurora-cam:/home/jross $ cat open_test.py
> import cv2 as cv
> import subprocess
> 
> cap = cv.VideoCapture(0, cv.CAP_V4L2)
> print(cap)
> if not cap.isOpened():
> ?? print("Open Failed!")
> elif cap.isOpened():
> ?? print("Open Succeeded!")
> 
> height = cap.get(cv.CAP_PROP_FRAME_HEIGHT)
> width = cap.get(cv.CAP_PROP_FRAME_WIDTH)
> exposure = cap.get(cv.CAP_PROP_AUTO_EXPOSURE)
> 
> print(height,width,exposure)
> frame = []
> try:
> ?? ret, temp_frame = cap.read()
> ?? print(ret)
> except Exception as e:
> ?? print(e)
> ?? #kill anything else using the camera
> ?? pid = subprocess.check_output("fuser -k
> /dev/video0",stderr=subprocess.STDOUT, shell=True)[:-1].decode('utf-8')
> ?? print("Exception caught! %s" % (e))
> frame.append(temp_frame)
> print(frame)
> 
> jross@aurora-cam:/home/jross $ python3 open_test.py
> 
> Open Failed!
> 0.0 0.0 0.0
> False
> [None]
> 
> I'd appreciate anyone's thoughts on fixing this!

Hi, I encountered the same problem.  Just committed a fix:
https://marc.info/?l=openbsd-ports-cvs=162857744213080=2

> Jeff Ross

Kevin

Re: Issues with TP-Link UE300

[Kevin Lo]

On Tue, Sep 29, 2020 at 12:08:42AM +0200, Joel Carnat wrote:
> 
> Hi,

Hi Joel,

> This seems to work much better!
> Transferring files via NFS, I could sustain from 118 to 148Mbps.
> 
> Kernel says:
> ure0 at uhub0 port 15 configuration 1 interface 0 "TP-LINK USB 10/100/1000 
> LAN" rev 3.00/30.00 addr 5
> ure0: RTL8153 (0x5c20), address d0:37:45:xx:xx:xx
> rgephy0 at ure0 phy 0: RTL8251 PHY, rev. 0
> 
> ifconfig says:
> ure0: flags=808843 mtu 1500
> 
> usbdev says:
> addr 05: 2357:0601 TP-LINK, USB 10/100/1000 LAN
>  super speed, power 64 mA, config 1, rev 30.00, iSerial 0100
>  driver: ure0
> 
> iperf3 says:
> [  5]   0.00-10.00  sec   618 MBytes   518 Mbits/sec  sender
> [  5]   0.00-10.13  sec   618 MBytes   512 Mbits/sec  receiver
> 
> Thank you very much.

Thanks for testing.  I just committed this patch.

Re: Issues with TP-Link UE300

[Kevin Lo]

On Sun, Sep 27, 2020 at 11:43:13PM +0200, Joel Carnat wrote:
> 
> Hi,
> 
> I have plugged a TP-Link UE300 on my ThinkPad X260 running OpenBSD -snapshot
> and it seems I can't get more than 100Mbps.
> 
> The dongle attaches and get an IP address. But the speed seems limited.
> Same behaviour when attached to the USB3 port of my APU4D4 (running 6.7).
> When plugged in a MacBook Pro (running macos), it gets Gbps speed.
> 
> I have noticed that it gets attached to cdce0;
> I thought the RTL8153 chipset would give me an ure0 device.
> 
> Is this expected?
> Is there something I can do to get Gbps out of this device?

Please try this diff, thanks.

Index: sys/dev/usb/if_ure.c
===
RCS file: /cvs/src/sys/dev/usb/if_ure.c,v
retrieving revision 1.18
diff -u -p -u -p -r1.18 if_ure.c
--- sys/dev/usb/if_ure.c4 Aug 2020 14:45:46 -   1.18
+++ sys/dev/usb/if_ure.c28 Sep 2020 02:24:40 -
@@ -76,7 +76,8 @@ const struct usb_devno ure_devs[] = {
{ USB_VENDOR_LENOVO, USB_PRODUCT_LENOVO_DOCK_ETHERNET },
{ USB_VENDOR_REALTEK, USB_PRODUCT_REALTEK_RTL8152 },
{ USB_VENDOR_REALTEK, USB_PRODUCT_REALTEK_RTL8153 },
-   { USB_VENDOR_REALTEK, USB_PRODUCT_REALTEK_RTL8156 }
+   { USB_VENDOR_REALTEK, USB_PRODUCT_REALTEK_RTL8156 },
+   { USB_VENDOR_TPLINK, USB_PRODUCT_TPLINK_UE300 }
 };
 
 inture_match(struct device *, void *, void *);
Index: sys/dev/usb/usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.720
diff -u -p -u -p -r1.720 usbdevs
--- sys/dev/usb/usbdevs 3 Aug 2020 14:25:44 -   1.720
+++ sys/dev/usb/usbdevs 28 Sep 2020 02:24:40 -
@@ -4317,6 +4317,7 @@ product TPLINK RTL8192EU  0x0107  RTL8192E
 product TPLINK RTL8192EU_2 0x0108  RTL8192EU
 product TPLINK RTL8192EU_3 0x0109  RTL8192EU
 product TPLINK RTL8188EUS  0x010c  RTL8188EUS
+product TPLINK UE300   0x0601  UE300 Ethernet
 
 /* Trek Technology products */
 product TREK THUMBDRIVE0x  ThumbDrive
Index: sys/dev/usb/usbdevs.h
===
RCS file: /cvs/src/sys/dev/usb/usbdevs.h,v
retrieving revision 1.732
diff -u -p -u -p -r1.732 usbdevs.h
--- sys/dev/usb/usbdevs.h   3 Aug 2020 14:25:56 -   1.732
+++ sys/dev/usb/usbdevs.h   28 Sep 2020 02:24:40 -
@@ -1,4 +1,4 @@
-/* $OpenBSD: usbdevs.h,v 1.732 2020/08/03 14:25:56 deraadt Exp $   */
+/* $OpenBSD$   */
 
 /*
  * THIS FILE IS AUTOMATICALLY GENERATED.  DO NOT EDIT.
@@ -4324,6 +4324,7 @@
 #defineUSB_PRODUCT_TPLINK_RTL8192EU_2  0x0108  /* RTL8192EU */
 #defineUSB_PRODUCT_TPLINK_RTL8192EU_3  0x0109  /* RTL8192EU */
 #defineUSB_PRODUCT_TPLINK_RTL8188EUS   0x010c  /* RTL8188EUS */
+#defineUSB_PRODUCT_TPLINK_UE3000x0601  /* UE300 
Ethernet */
 
 /* Trek Technology products */
 #defineUSB_PRODUCT_TREK_THUMBDRIVE 0x  /* ThumbDrive */
Index: sys/dev/usb/usbdevs_data.h
===
RCS file: /cvs/src/sys/dev/usb/usbdevs_data.h,v
retrieving revision 1.726
diff -u -p -u -p -r1.726 usbdevs_data.h
--- sys/dev/usb/usbdevs_data.h  3 Aug 2020 14:25:56 -   1.726
+++ sys/dev/usb/usbdevs_data.h  28 Sep 2020 02:24:40 -
@@ -1,4 +1,4 @@
-/* $OpenBSD: usbdevs_data.h,v 1.726 2020/08/03 14:25:56 deraadt Exp $  
*/
+/* $OpenBSD$   */
 
 /*
  * THIS FILE IS AUTOMATICALLY GENERATED.  DO NOT EDIT.
@@ -11068,6 +11068,10 @@ const struct usb_known_product usb_known
{
USB_VENDOR_TPLINK, USB_PRODUCT_TPLINK_RTL8188EUS,
"RTL8188EUS",
+   },
+   {
+   USB_VENDOR_TPLINK, USB_PRODUCT_TPLINK_UE300,
+   "UE300 Ethernet",
},
{
USB_VENDOR_TREK, USB_PRODUCT_TREK_THUMBDRIVE,

Re: urtwn(4) gets wedged periodically

[Kevin Lo]

On Wed, Nov 13, 2019 at 01:41:28AM -0500, Brennan Vincent wrote:
> Hello,
> 
> I have a Wi-Fi USB adapter. urtwn(4) normally works fine, but it's a bit 
> flaky... 
> 
> The issue happens both on 6.6 and on -current.
> 
> When my adapter gets into the bad state, it appears (from dmesg output) that
> the driver is scanning for access points over and over, never
> finding any. When I get into this wedged state, I don't know any way
> to bring the card back up other than unplugging it and re-inserting.
> (`ifconfig urtwn0 down && sleep 10 && sh /etc/netstart urtwn0`
> is no help).
> 
> I am attaching the relevant snippets of the dmesg output
> (Kernel built with URTWN_DEBUG and urtwn_debug level set to 3).
> 
> Another interesting thing is these "RX status=6" error messages in the
> output. Apparently, "6" corresponds to "USBD_CANCELLED"
> in sys/dev/usb/usbdi.h .
> 
> I don't think this is a hardware issue because the device is
> working fine on Ubuntu.
> 
> Please let me know if there is anything more I can do to help debug this.
> I am a beginner with OpenBSD so I'm not sure exactly what is relevant.

Despite our USB issues, there are minor problems with the urtwn(4) for
RTL8188C/RTL8192C:

- we don't need to enable/disable efuse access protection; it may prevent
  incorrect mac address read from efuse.
- disable BB/RF is not needed.

Index: sys/dev/ic/rtwn.c
===
RCS file: /cvs/src/sys/dev/ic/rtwn.c,v
retrieving revision 1.46
diff -u -p -u -p -r1.46 rtwn.c
--- sys/dev/ic/rtwn.c   25 Apr 2019 01:52:13 -  1.46
+++ sys/dev/ic/rtwn.c   16 Nov 2019 09:23:07 -
@@ -529,7 +529,9 @@ rtwn_efuse_read(struct rtwn_softc *sc, u
uint32_t reg;
int i, len;
 
-   rtwn_write_1(sc, R92C_EFUSE_ACCESS, R92C_EFUSE_ACCESS_ON);
+   if (!(sc->chip & (RTWN_CHIP_92C | RTWN_CHIP_88C)))
+   rtwn_write_1(sc, R92C_EFUSE_ACCESS, R92C_EFUSE_ACCESS_ON);
+
rtwn_efuse_switch_power(sc);
 
memset(rom, 0xff, size);
@@ -571,7 +573,8 @@ rtwn_efuse_read(struct rtwn_softc *sc, u
printf("\n");
}
 #endif
-   rtwn_write_1(sc, R92C_EFUSE_ACCESS, R92C_EFUSE_ACCESS_OFF);
+   if (!(sc->chip & (RTWN_CHIP_92C | RTWN_CHIP_88C)))
+   rtwn_write_1(sc, R92C_EFUSE_ACCESS, R92C_EFUSE_ACCESS_OFF);
 }
 
 void
Index: sys/dev/usb/if_urtwn.c
===
RCS file: /cvs/src/sys/dev/usb/if_urtwn.c,v
retrieving revision 1.84
diff -u -p -u -p -r1.84 if_urtwn.c
--- sys/dev/usb/if_urtwn.c  12 Sep 2019 12:55:07 -  1.84
+++ sys/dev/usb/if_urtwn.c  16 Nov 2019 09:23:07 -
@@ -1704,21 +1704,6 @@ urtwn_r92c_power_on(struct urtwn_softc *
urtwn_write_2(sc, R92C_SYS_ISO_CTRL,
urtwn_read_2(sc, R92C_SYS_ISO_CTRL) & ~R92C_SYS_ISO_CTRL_DIOR);
 
-   /* Initialize MAC. */
-   urtwn_write_1(sc, R92C_APSD_CTRL,
-   urtwn_read_1(sc, R92C_APSD_CTRL) & ~R92C_APSD_CTRL_OFF);
-   for (ntries = 0; ntries < 200; ntries++) {
-   if (!(urtwn_read_1(sc, R92C_APSD_CTRL) &
-   R92C_APSD_CTRL_OFF_STATUS))
-   break;
-   DELAY(5);
-   }
-   if (ntries == 200) {
-   printf("%s: timeout waiting for MAC initialization\n",
-   sc->sc_dev.dv_xname);
-   return (ETIMEDOUT);
-   }
-
/* Enable MAC DMA/WMAC/SCHEDULE/SEC blocks. */
reg = urtwn_read_2(sc, R92C_CR);
reg |= R92C_CR_HCI_TXDMA_EN | R92C_CR_HCI_RXDMA_EN |

Re: alc0 watchdog timeout

[Kevin Lo]

On Fri, Jun 21, 2019 at 09:44:12PM +0200, Stephane HUC "PengouinBSD" wrote:
> 
> HI,

Hi,

> To communicate on Internet, with my laptop - a Dell Alienware 13 - I
> use an external LAN Adapter USB to RJ. This run correcty!
> 
> I did not notice / understood that the physical network card was managed
> .
> 
> $ grep alc0 dmesg.txt
> 
> alc0 at pci2 dev 0 function 0 "Attansic Technology E2200" rev 0x10:
> msi, address 34:e6:d7:1b:7f:14
> atphy0 at alc0 phy 0: AR8035 10/100/1000 PHY, rev. 9
> 
> But, if I configure inet and inet6 on hostname.alc0 file, either dhcp
> or static informations, dmesg filled with "alc0: watchdog timeout" and
> /var/log/messages grow up!
> 
> Into /var/log/messages, as:
> Jun 21 16:13:26 ptb-aw13zou /bsd: alc0: watchdog timeout
> Jun 21 16:14:00 ptb-aw13zou /bsd: alc0: watchdog timeout
> Jun 21 16:15:56 ptb-aw13zou last message repeated 5 times
> Jun 21 16:25:39 ptb-aw13zou last message repeated 20 times
> Jun 21 16:35:34 ptb-aw13zou last message repeated 21 times
> Jun 21 16:45:57 ptb-aw13zou last message repeated 22 times
> Jun 21 16:55:56 ptb-aw13zou last message repeated 19 times
> Jun 21 17:05:46 ptb-aw13zou last message repeated 22 times
> Jun 21 17:15:37 ptb-aw13zou last message repeated 22 times
> Jun 21 17:25:30 ptb-aw13zou last message repeated 22 times
> Jun 21 17:27:54 ptb-aw13zou last message repeated 4 times
> 
> With 'dhcp', the system reply: "no lease".
> 
> Someone can explain-me the reason (simply), please?!
> (and, perhaps, found a solution…)

I think this bug has been fixed in r1.48.  Please try -current, thanks.

Re: rtwn

[Kevin Lo]

On Tue, Dec 11, 2018 at 10:05:24AM +0800, Kevin Lo wrote:
> 
> On Tue, Dec 11, 2018 at 04:20:11AM +0300, gilmulin wrote:
> > 
> > Hello,
> > 
> > I have OpenBSD installed on my laptop (6.4 GENERIC.MP#1 amd64). I love 
> > it.
> > And I hope to fix Wi-Fi problem described below. Because staying on wire 
> > is not comfort way :)
> > 
> > My network device is Realtek RTL8723BE Wireless LAN 802.11 PCI-E NIC.
> > 
> > # dmesg | grep Realtek | grep pci2
> > "Realtek 8191SE" rev 0x00 at pci2 dev 0 function 0 not configured
> > 
> > # pcidump -v 2:0:0
> >   2:0:0: Realtek 8191SE
> >  0x: Vendor ID: 10ec Product ID: b723
> >  0x0004: Command: 0007 Status: 0010
> >  0x0008: Class: 02 Subclass: 80 Interface: 00 Revision: 00
> >  0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line 
> > Size: 10
> >  0x0010: BAR io addr: 0x2000/0x0100
> >  0x0014: BAR empty ()
> >  0x0018: BAR mem 64bit addr: 0x9050/0x4000
> >  0x0020: BAR empty ()
> >  0x0024: BAR empty ()
> >  0x0028: Cardbus CIS: 
> >  0x002c: Subsystem Vendor ID: 17aa Product ID: b736
> >  0x0030: Expansion ROM Base Address: 
> >  0x0038: 
> >  0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00
> >  0x0040: Capability 0x01: Power Management
> >  State: D0
> >  0x0050: Capability 0x05: Message Signalled Interrupts (MSI)
> >  0x0070: Capability 0x10: PCI Express
> >  Link Speed: 2.5 / 2.5 GT/s Link Width: x1 / x1
> >  0x0100: Enhanced Capability 0x01: Advanced Error Reporting
> >  0x0140: Enhanced Capability 0x03: Device Serial Number
> >  0x0150: Enhanced Capability 0x18: Latency Tolerance Reporting
> >  0x0158: Enhanced Capability 0x1e: L1 PM
> > 
> > By the way, rtwn driver has the firmware for my device:
> > # ls /etc/firmware | grep rtwn-rtl8723
> > rtwn-rtl8723befw_36
> > rtwn-rtl8723fw
> > rtwn-rtl8723fw_B
> > 
> > As one can see, the device is detected. Vendor's ID 10ec is Realtek, and 
> > 17aa is Lenovo. It's OK, as I see.
> > But card is not determined properly. However, "Product ID: b723" is 
> > close to reality.
> > What should I do to match correctly all these entities and to fix 
> > problem with this pci device?
> > As I see, there are few options to solve my problem.
> > Could you tell me the best option?
> 
> Yours is RTL8723DE, which is not supported yet.

Oops, typo.  RTL8723BE is currently not supported.

> > 
> > Current state of firmware packages:
> > $ fw_update -i
> > Installed: intel-firmware-20180807p0v0 uvideo-firmware-1.2p2
> > Installed, extra: rtwn-firmware-20180103 rsu-firmware-1.2p1
> > 
> > Thank you.
> > Stas
> 
>   Kevin
> 
> 

Re: rtwn

[Kevin Lo]

On Tue, Dec 11, 2018 at 04:20:11AM +0300, gilmulin wrote:
> 
> Hello,
> 
> I have OpenBSD installed on my laptop (6.4 GENERIC.MP#1 amd64). I love 
> it.
> And I hope to fix Wi-Fi problem described below. Because staying on wire 
> is not comfort way :)
> 
> My network device is Realtek RTL8723BE Wireless LAN 802.11 PCI-E NIC.
> 
> # dmesg | grep Realtek | grep pci2
> "Realtek 8191SE" rev 0x00 at pci2 dev 0 function 0 not configured
> 
> # pcidump -v 2:0:0
>   2:0:0: Realtek 8191SE
>  0x: Vendor ID: 10ec Product ID: b723
>  0x0004: Command: 0007 Status: 0010
>  0x0008: Class: 02 Subclass: 80 Interface: 00 Revision: 00
>  0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line 
> Size: 10
>  0x0010: BAR io addr: 0x2000/0x0100
>  0x0014: BAR empty ()
>  0x0018: BAR mem 64bit addr: 0x9050/0x4000
>  0x0020: BAR empty ()
>  0x0024: BAR empty ()
>  0x0028: Cardbus CIS: 
>  0x002c: Subsystem Vendor ID: 17aa Product ID: b736
>  0x0030: Expansion ROM Base Address: 
>  0x0038: 
>  0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00
>  0x0040: Capability 0x01: Power Management
>  State: D0
>  0x0050: Capability 0x05: Message Signalled Interrupts (MSI)
>  0x0070: Capability 0x10: PCI Express
>  Link Speed: 2.5 / 2.5 GT/s Link Width: x1 / x1
>  0x0100: Enhanced Capability 0x01: Advanced Error Reporting
>  0x0140: Enhanced Capability 0x03: Device Serial Number
>  0x0150: Enhanced Capability 0x18: Latency Tolerance Reporting
>  0x0158: Enhanced Capability 0x1e: L1 PM
> 
> By the way, rtwn driver has the firmware for my device:
> # ls /etc/firmware | grep rtwn-rtl8723
> rtwn-rtl8723befw_36
> rtwn-rtl8723fw
> rtwn-rtl8723fw_B
> 
> As one can see, the device is detected. Vendor's ID 10ec is Realtek, and 
> 17aa is Lenovo. It's OK, as I see.
> But card is not determined properly. However, "Product ID: b723" is 
> close to reality.
> What should I do to match correctly all these entities and to fix 
> problem with this pci device?
> As I see, there are few options to solve my problem.
> Could you tell me the best option?

Yours is RTL8723DE, which is not supported yet.
> 
> Current state of firmware packages:
> $ fw_update -i
> Installed: intel-firmware-20180807p0v0 uvideo-firmware-1.2p2
> Installed, extra: rtwn-firmware-20180103 rsu-firmware-1.2p1
> 
> Thank you.
> Stas

Kevin

Re: Open source RISC-V 64bit w ECC RAM & PCIe this summer

[Kevin Lo]

On Fri, May 18, 2018 at 08:00:14PM +0200, Peter J. Philipp wrote:
> 
> On Fri, May 18, 2018 at 03:31:51PM +0200, Karel Gardas wrote:
> > On Fri, 18 May 2018 02:30:13 -0400
> > Joseph Mayer  wrote:
> > 
> > > 4-core (5-core?) 1.5Ghz, 8GB DDR4 ECC RAM, two PCIe slots (one one-lane
> > > and one two-lane PCIe 2.0?), SATA, gigabit ethernet, microSD, HDMI,
> > > UART.
> > > 
> > > https://www.sifive.com/products/hifive-unleashed/
> > > 
> > > https://www.crowdsupply.com/microsemi/hifive-unleashed-expansion-board
> > > 
> > > 21 more available in lower link, to the lower right.
> > > 
> > > Great to see it happen finally.
> > 
> > Indeed! RISC-V is making progress. For plain programmers this is probably 
> > not yet the right set of hardware as (1) system spec of RISC-V is not 
> > finalized yet (IIRC!) and (2) speed of the board CPU is probably lower than 
> > speed of Qemu emulation on high-speed xeon CPU.
> > 
> > Also, w.r.t. price, it's a bit prohibitive indeed. IIRC promise was to have 
> > both boards on one board and for ~$1000 but I may be mistaken on this. 
> > Anyway, this is just first bird and I hope there will be more comming. 
> > Especially the promises of Esperanto Technologies look really promising. 
> > Future is open and interesting!
> 
> Hi!

Hi Peter,

> RISCV really interests me!  But the porting effort for this is probably
> above my head.  In the past in risc-v threads I posted a riscv-qemu build
> procedure.  I revisited this today and followed my own steps.  After a bit
> of trying I finally got it compiled.  I blogged about this experience:
> 
> http://www.centroid.eu/blog/c?article=1526665139

Our emulators/qemu port has already supported RISC-V and it runs quite well.
If you have time maybe you can test the riscv-elf port?

https://marc.info/?l=openbsd-ports=152775211718628=2

Thanks.

> Realistically if you want to run BSD on RISCV you can do it through this
> way.  You don't need to buy the hardware, unless you're seriously good with
> porting.  My emulation was on FreeBSD, thanks to those folks for makign a
> bbl available (so I don't have to install FreeBSD and crosscompile).
> 
> Best Regards,
> -peter
> 
> PS: I've been following Talos 2 as well, and really like it but again, that's
> the same as with the RISCV issue, I lack the clue to port this.  I'm going
> to learn about RISCV assembly first and then perhaps learn about POWER
> assembly, perhaps I can build a compiler.  (I have access to POWER hardware,
> but will need to ask permission).  Once that is done I'm ready to help
> with any porting effort *laugh*.  That's if I don't give up along the way.

Re: Chinese fonts on chrome

[Kevin Lo]

On Sun, Apr 01, 2018 at 08:00:16PM +0200, Pau wrote:
> 
> Hello:

Hi,

> I'm trying to get chrome or firefox display Chinese characters but I'm
> failing. I have installed zh-wqy-bitmapfont and zh-fonts-kc and then I
> run
> fc-cache but they do not show up. In the font menu of chrome I cannot
> find any option for those fonts to be used. Firefox is fine though.
> 
> I also followed this:
> 
> https://en.wikipedia.org/wiki/Help:Multilingual_support_%28East_Asian%29#Other_UNIX_Distributions
> 
> without success. Any idea of what I might be doing wrong? Thanks.

I've noticed a problem when viewing a page with Simplified Chinese characters
in Chrome, some Simplified Chinese characters can't be displayed properly.
Works for me after zh-wqy-zenhei-ttf is installed.

Kevin

Re: HP Mini 5102 with networking ?

[Kevin Lo]

On Mon, 2010-11-15 at 11:35 -0800, Frans Haarman wrote:
 Does anybody have a hp min 5102 with networking ?
 
 I managed to install 4.8 amd on a usbdisk (using qemu, on windows7, *sigh*).
  It boots, and works fine, just missing
 networking support.   I managed to boot i386 bsd.rd, and snapshots bsd.rd
 but both claim [vlan0] is the way to go.

It seems like the wired network is a SysKonnect Yukon2. 
Could you try this diff? Thanks.

Index: if_msk.c
===
RCS file: /cvs/src/sys/dev/pci/if_msk.c,v
retrieving revision 1.90
diff -u -p -r1.90 if_msk.c
--- if_msk.c20 Sep 2010 07:40:38 -  1.90
+++ if_msk.c16 Nov 2010 02:34:36 -
@@ -208,6 +208,7 @@ const struct pci_matchid mskc_devices[] 
{ PCI_VENDOR_MARVELL,   PCI_PRODUCT_MARVELL_YUKON_8056 },
{ PCI_VENDOR_MARVELL,   PCI_PRODUCT_MARVELL_YUKON_8057 },
{ PCI_VENDOR_MARVELL,   PCI_PRODUCT_MARVELL_YUKON_8058 },
+   { PCI_VENDOR_MARVELL,   PCI_PRODUCT_MARVELL_YUKON_8059 },
{ PCI_VENDOR_MARVELL,   PCI_PRODUCT_MARVELL_YUKON_8061CU },
{ PCI_VENDOR_MARVELL,   PCI_PRODUCT_MARVELL_YUKON_8061X },
{ PCI_VENDOR_MARVELL,   PCI_PRODUCT_MARVELL_YUKON_8062CU },

Re: ATutor

[Kevin Lo]

On Thu, 2009-12-17 at 10:08 -0500, Predrag Punosevac wrote:
 Kevin Lo ke...@kevlo.org wrote:
 
  On Wed, 2009-12-16 at 16:29 -0500, Predrag Punosevac wrote: 
   Fred Crowson fred.crow...@googlemail.com wrote:
   
On 12/16/09, Fred Crowson fred.crow...@googlemail.com wrote:
 On 12/16/09, Predrag Punosevac punoseva...@gmail.com wrote:
 Dear All,

 Is anybody using Learning Management System ATutor? The only LMS I
 noticed in ports is Moodle which is terribly outdate. I looked into
 installation of ATutor and it seems to me that it is just of bunch of
 xhtml, java-script, and php files which have to up unloaded in the 
 right
 directory and correctly linked with MySQL. Obviously ATutor also
 requires PHP module for Apache.

 Does anybody see the value of porting ATutor?

 Best,
 Predrag

 P.S. Do people have any experience with Drupal as LMS? Does it have a
 grade-book?

 What's wrong with Moodle?  I know that the packaged version is behind 
 the
 current release but you can upgrade quite easily.

 And it runs nicely in the httpd chroot.

 Fred
   
Sorry should have said have you asked on ports@ about bring moodle up
to the latest version?
   
Thanks
   
Fred
PS I would added to my own to-do list but I'm already behind on
getting netbeans uptodate
   
   No, I have not asked on ports about updating. I contacted privately the
   port maintainer who promised that he will update port pending on his 
   time. Fortunately, he happens to work on more interesting things than 
   updating Moodle. Since he is busy and I need the port I fell it is up
   to me to send the diff which people will test. 
 
  Okay, I have some free time. I just sent an updated diff for moodle 
  on po...@. Please test it, thanks! 
 
 Kev,

Hi Predrag,

 Thank you so much. I will test in the next day or so. On another note I
 have played for the past 10-12 hours with ATutor. The good news is that
 actually your Moodle port can be used as template for ATutor. If you 
 start with your Makefile for Moodle it would be enough just to replace
 port name with ATutor-1.6.3, edit the web-site and remove PostgreSQL 
 flavour since ATutor works only with MySQL. Here is the quick and 
 dirty Makefile I hope I will have some time this weekend to clean the 
 port and actually to send ATutor to ports. Obviously there would be no 
 flavors in the final version and php-mysql module has to be add as run 
 dependencies. The quick and dirty ATutor makefile is shown below. The 
 real difficulty with ATutor is to fire up MySQL, PHP module in proper
 order and create /var/www/tmp directory so that we can still use Apache
 in the chroot. 

Thanks for the info, but I'm not interested in ATutor.
Maybe you can make that port and post it on po...@.

 Best,
 Predrag

Kevin

Re: ATutor

[Kevin Lo]

On Wed, 2009-12-16 at 16:29 -0500, Predrag Punosevac wrote: 
 Fred Crowson fred.crow...@googlemail.com wrote:
 
  On 12/16/09, Fred Crowson fred.crow...@googlemail.com wrote:
   On 12/16/09, Predrag Punosevac punoseva...@gmail.com wrote:
   Dear All,
  
   Is anybody using Learning Management System ATutor? The only LMS I
   noticed in ports is Moodle which is terribly outdate. I looked into
   installation of ATutor and it seems to me that it is just of bunch of
   xhtml, java-script, and php files which have to up unloaded in the right
   directory and correctly linked with MySQL. Obviously ATutor also
   requires PHP module for Apache.
  
   Does anybody see the value of porting ATutor?
  
   Best,
   Predrag
  
   P.S. Do people have any experience with Drupal as LMS? Does it have a
   grade-book?
  
   What's wrong with Moodle?  I know that the packaged version is behind the
   current release but you can upgrade quite easily.
  
   And it runs nicely in the httpd chroot.
  
   Fred
 
  Sorry should have said have you asked on ports@ about bring moodle up
  to the latest version?
 
  Thanks
 
  Fred
  PS I would added to my own to-do list but I'm already behind on
  getting netbeans uptodate
 
 No, I have not asked on ports about updating. I contacted privately the
 port maintainer who promised that he will update port pending on his 
 time. Fortunately, he happens to work on more interesting things than 
 updating Moodle. Since he is busy and I need the port I fell it is up
 to me to send the diff which people will test. 

Okay, I have some free time. I just sent an updated diff for moodle 
on po...@. Please test it, thanks! 

 Well guess what? I did little bit of research and asking around so
 I prefer to spend my time on ATutor. That is just a personal preference.
 
 The Moodle in present state is useless as it doesn't contain the 
 grade-book module. The grade-book has been introduced in Moodle one or 
 two releases after the Kev's port. Some of more interesting features 
 of Moodle according to my source are closed source and needs to be 
 purchased. I am all ears and I would love to be contradicted and 
 provided with other testimonials. ATutor feels lot simpler than Moodle
 but I might be very wrong. 

 Most Kind Regards,
 Predrag Punosevac

Kevin

Re: Presentation tool

[Kevin Lo]

Mr Man wrote:
 Hi,
 
 I have a presentation coming up, and I would like to use my OpenBSD laptop 
 for it. What is the recommended application for a slides driven presentation?

misc/magicpoint

 Thanks

Kevin

Re: Create a bootable usb key?

[Kevin Lo]

On Sun, 2009-02-15 at 15:28 -0700, Theo de Raadt wrote:
   On 2009-01-10, Guillaume Thouvenin guillaume.thouve...@polymtl.ca wrote:
  
   Now next step is to have wired network working and so add support to my
   Attansic Technology L1E.
  
   This chip is not yet supported in OpenBSD. N.B. it is not the same
   as either Attansic L1 or L2.
  
  Yes right. I will have a look how driver are implemented in OpenBSD and
  I will try to add the support of Attansic L1E. Do you know if someone
  is working on it?
 
 it will happen as soon as kevlo has a board with it.

I just committed ale(4) driver:

http://marc.info/?l=openbsd-cvsm=123553127523101w=2

Please test it if you have time, thanks!

Kevin

Re: WordPress support

[Kevin Lo]

J Moore wrote:
 Wordpress ver 1.5 is in the package list for OpenBSD 3.9. The latest 
 version of Wordpress is 2.0.4.
 
 Is Wordpress being actively maintained on OpenBSD? 

Yes. I have diffs about www ports(including wordpress) I've maintained.
I've tested those diff about a week, I'll commit them, thanks.

 Thanks,
 Jay

Kevin