Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Post
  • Reply
sb hermit
Dec 13, 2016





FlapYoJacks posted:

Nah, it’s because running j1 makes the logs easier to parse as everything is sequential.

:hmmyes:

Adbot
ADBOT LOVES YOU

ryanrs
Jul 12, 2011

FlapYoJacks posted:

huh, I’m pretty sure I submitted a patch for that and it was merged upstream on the master branch.

I'm building OpenWrt 23.05.3, not current? I think I just need to turn on IGNORE_ERRORS=1.

FlapYoJacks
Feb 12, 2009

ryanrs posted:

I'm building OpenWrt 23.05.3, not current? I think I just need to turn on IGNORE_ERRORS=1.

ah yeah. All of my PRs are for the master branch.

Captain Foo
May 11, 2004

we vibin'
we slidin'
we breathin'
we dyin'

make -jo

ryanrs
Jul 12, 2011

Building Linux: The Quest for USB

ryanrs posted:

I can't unfuck this SoC's USB phy in python.

code:
[   64.599866] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[   64.782404] usb-storage 1-1:1.0: USB Mass Storage device detected
[   64.783418] scsi host0: usb-storage 1-1:1.0
[   66.110317] scsi 0:0:0:0: Direct-Access     Samsung  Flash Drive      1100 PQ: 0 ANSI: 6
[   66.112488] sd 0:0:0:0: [sda] 62656641 512-byte logical blocks: (32.1 GB/29.9 GiB)
[   66.196124] sd 0:0:0:0: [sda] Write Protect is off
[   66.284708] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   67.944804]  sda: sda1 sda2
[   67.945549] sd 0:0:0:0: [sda] Attached SCSI removable disk


BusyBox v1.36.1 (2024-04-24 12:12:15 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt SNAPSHOT, r0+26009-6ca8305598
 -----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt:/# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 6.1.86 xhci-hcd xHCI Host Controller
Bus 001 Device 002: ID 090c:1000 Samsung Flash Drive
Bus 002 Device 001: ID 1d6b:0003 Linux 6.1.86 xhci-hcd xHCI Host Controller
root@OpenWrt:/# mkdir /mnt/fart
root@OpenWrt:/# mount -t f2fs /dev/sda2 /mnt/fart
[  188.702867] F2FS-fs (sda2): Found nat_bits in checkpoint
[  189.284809] F2FS-fs (sda2): Mounted with checkpoint version = 57fdb94e
root@OpenWrt:/# cat /mnt/fart/test 
yospos
:cool:

The Aruba AP-303H is based on a Qualcomm IPQ4029 SoC. This chip has a USB 2.0 controller AND a USB 3.0 controller. Different boards use 0/1/both of these USB controllers. The AP-303H has a single USB 2.0 port, so the current device tree only describes the SoC's USB 2.0 controller.

But the physical port is wired to the USB 3.0 controller's phy, lol. If you change the device tree definitions to enable the USB 3 controller usb3@8af8800, the port will start working. The superspeed lines are not connected, so you only get USB 2.0 speed.

I'll do some more testing today and prepare a PR.

e: https://github.com/openwrt/openwrt/pull/15264

ryanrs fucked around with this message at 06:18 on Apr 25, 2024

sb hermit
Dec 13, 2016





ryanrs posted:

Building Linux: The Quest for USB

code:
[   64.599866] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[   64.782404] usb-storage 1-1:1.0: USB Mass Storage device detected
[   64.783418] scsi host0: usb-storage 1-1:1.0
[   66.110317] scsi 0:0:0:0: Direct-Access     Samsung  Flash Drive      1100 PQ: 0 ANSI: 6
[   66.112488] sd 0:0:0:0: [sda] 62656641 512-byte logical blocks: (32.1 GB/29.9 GiB)
[   66.196124] sd 0:0:0:0: [sda] Write Protect is off
[   66.284708] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   67.944804]  sda: sda1 sda2
[   67.945549] sd 0:0:0:0: [sda] Attached SCSI removable disk


BusyBox v1.36.1 (2024-04-24 12:12:15 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt SNAPSHOT, r0+26009-6ca8305598
 -----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt:/# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 6.1.86 xhci-hcd xHCI Host Controller
Bus 001 Device 002: ID 090c:1000 Samsung Flash Drive
Bus 002 Device 001: ID 1d6b:0003 Linux 6.1.86 xhci-hcd xHCI Host Controller
root@OpenWrt:/# mkdir /mnt/fart
root@OpenWrt:/# mount -t f2fs /dev/sda2 /mnt/fart
[  188.702867] F2FS-fs (sda2): Found nat_bits in checkpoint
[  189.284809] F2FS-fs (sda2): Mounted with checkpoint version = 57fdb94e
root@OpenWrt:/# cat /mnt/fart/test 
yospos
:cool:

The Aruba AP-303H is based on a Qualcomm IPQ4029 SoC. This chip has a USB 2.0 controller AND a USB 3.0 controller. Different boards use 0/1/both of these USB controllers. The AP-303H has a single USB 2.0 port, so the current device tree only describes the SoC's USB 2.0 controller.

But the physical port is wired to the USB 3.0 controller's phy, lol. If you change the device tree definitions to enable the USB 3 controller usb3@8af8800, the port will start working. The superspeed lines are not connected, so you only get USB 2.0 speed.

I'll do some more testing today and prepare a PR.

:nice:

outhole surfer
Mar 18, 2003

gnome wayland is really starting to get under my skin.

any time i have high disk io, the ui will start stuttering. launching steam after updates have been collecting a while is a sure fire way to trigger it.

FlapYoJacks
Feb 12, 2009

outhole surfer posted:

gnome wayland is really starting to get under my skin.

any time i have high disk io, the ui will start stuttering. launching steam after updates have been collecting a while is a sure fire way to trigger it.

Use Plasma. It's made by competent people OP.

shackleford
Sep 4, 2006

outhole surfer posted:

gnome wayland is really starting to get under my skin.

any time i have high disk io, the ui will start stuttering. launching steam after updates have been collecting a while is a sure fire way to trigger it.

does the GNOME compositor not do this trick

https://github.com/swaywm/sway/blob/646019cad9e8a075911e960fc7645471d9c26bf6/sway/realtime.c#L20-L37

code:
	int prio = sched_get_priority_min(SCHED_RR);
	int old_policy;
	int ret;
	struct sched_param param;

	ret = pthread_getschedparam(pthread_self(), &old_policy, &param);
	if (ret != 0) {
		sway_log(SWAY_DEBUG, "Failed to get old scheduling priority");
		return;
	}

	param.sched_priority = prio;

	ret = pthread_setschedparam(pthread_self(), SCHED_RR, &param);
	if (ret != 0) {
		sway_log(SWAY_INFO, "Failed to set scheduling priority to %d", prio);
		return;
	}

Tankakern
Jul 25, 2007

i think chromium 125 fixed my make-chromium-crash-by-trying-random-mouse-gestures-in-wayland issue

Silver Alicorn
Mar 30, 2008

𝓪 𝓻𝓮𝓭 𝓹𝓪𝓷𝓭𝓪 𝓲𝓼 𝓪 𝓬𝓾𝓻𝓲𝓸𝓾𝓼 𝓼𝓸𝓻𝓽 𝓸𝓯 𝓬𝓻𝓮𝓪𝓽𝓾𝓻𝓮
chome

ryanrs
Jul 12, 2011

This new USB 2 port is amazing, btw. I'm getting 35 MB/s read and 11 MB/s write.

Compare those numbers to the built-in SPI NAND which runs at 1 MB/s read and write. I think it's using classic 1-bit SPI running at 24 MHz.

Adbot
ADBOT LOVES YOU

Beeftweeter
Jun 28, 2005

a medium-format picture of beeftweeter staring silently at the camera, a quizzical expression on his face

FlapYoJacks posted:

Nah, it’s because running j1 makes the logs easier to parse as everything is sequential.

that and running -j7 would probably start/continue building something unrelated too. i've always found openwrt's -j1 V=s thing needs suiting, they haven't changed that message much in like 20 years for a reason lol

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply