mister-devel/linux-kernel_mister

linux-kernel_mister's Issues

bluetooth key blinking very fast

Hello
I have my Bluetooth key which behaves strangely, the led flashes excessively
I put the log for you for your information

MiSTer V210906 OS 210906

[bluetooth]# show 00:1A:7D:DA:71:13
Controller 00:1A:7D:DA:71:13 (public)
Name: MiSTer
Alias: MiSTer-0
Class: 0x00000000
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x000000b4
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d053D
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x05 (5)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedCapabilities Key: MaxAdvLen
SupportedCapabilities Value: 0x1f (31)
SupportedCapabilities Key: MaxScnRspLen
SupportedCapabilities Value: 0x1f (31)
Advertisement Monitor Features:
SupportedMonitorTypes: or_patterns

Version Key : CSR 4.0

Merci

https://imgur.com/aKOFc83

LFTP disappeared with Linux Update v210829

Hi,

At first, thank you very much for your incredible and hard work.

It's a pity that you removed LFTP from the Linux Update v210829. It's very useful for me.

Best regards.

Default config results in a kernel where some peripherals don't work

If the kernel compilation instructions at https://github.com/MiSTer-devel/Main_MiSTer/wiki/Compiling-the-Linux-kernel-for-MiSTer are followed exactly on a clean Ubuntu installation, the resulting zImage_dtb file mostly works, but some peripherals no longer function. Examples of nonworking peripherals include CIFS mounts, the Edimax EW-7811Un, and the Xbox Elite Controller. However, most peripherals work fine.

This appears to be due to some discrepancies between the default settings in this repo (particularly Kconfig and Makefile?) and the settings used to compile release builds of the kernel:

• The build process needs to include the EXTRAVERSION=-MiSTer flag so that the resulting kernel name, 5.15.1-MiSTer, matches the name of the official release. Right now, the compiled kernel gets the version "5.15.1+".
• For the Edimax EW-7811Un wi-fi adapter to work, I had to flip CONFIG_RTL8188EU from "m" to "y". I'm not sure what the general solution for other wi-fi adapters here is; a quick try at flipping multiple wi-fi driver flags from "m" to "y" failed due to multiple conflicting definitions.

Request: assign rmem_max

Hi,
I can't resolve that rmem_max is assigned to 2097152 for MiSTer at boot. I need that because i have received buffer errors without it.

1. Tried SO_RCVBUFFORCE inside MiSTer main
2. Tried user-start.sh with "sysctl -w net.core.rmem_max 2097152" or "sysctl -p" with /etc/sysctl.conf

If i kill MiSTer main and re-run, rmem_max is working properly. It's possible to do that by default on kernel?

Thank you

Wifi RTL8812BU does not work

I've got this Comfast CF-812AC (RTL8812BU) wifi dongle and it works fine under windows.
O mister it cant connect. Sometimes it lists the ssids, sometimes not. But even when it lists, I cant connect to the network.
Tested with latest update from today and with the previous one.
Adapter is listed on the wiki as working and it's on the changelog since Aug 25.
Driver problem?

Add Namco GunCon 2 driver

Hello,

This request pairs with MiSTer-devel/Main_MiSTer#516 (just merged) to provide support in MiSTer for the Namco GunCon 2 lightgun.

Could you please include the GunCon 2 driver at https://github.com/beardypig/guncon2 in the kernel?

Sorry this isn't a PR; my only working copy uses an externally compiled module, since I'm not experienced at building new modules into the kernel itself.

Thank you!

Linux merges dual HID joysticks over Bluetooth (BLE).

I suspect this is related to how the Linux kernel and/or Bluez handle HID over GATT:

bootsector/ControllaBLE#2

The kernel quirks for the VID/PID used by ControllaBLE seem to be ignored when used through HoG/BLE and are not applied - basically we get two virtual pads merged as one, wth second player buttons getting stripped off.

If possible, I would love to see ControllaBLE fully supported on MiSTer (currently player 2 doesn't work).

Building the rtl8188eu driver against current kernel

Hi there,

First things first, thanks a lot for the continuing work on the MiSTer platform, and the recent developments that brought us the 5.13 kernel!

I have been able to build the rtl8188eu WiFi driver against the old kernel for a long time, but I am unable to do so with the new kernel.

I am configuring the kernel sources like this:
make ARCH=arm mrproper && make ARCH=arm MiSTer_defconfig && make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- EXTRAVERSION=-MiSTer modules_prepare
And then I try to build the driver from these repos:
https://github.com/ulli-kroll/rtl8188eu
https://github.com/lwfinger/rtl8188eu
https://github.com/quickreflex/rtl8188eus

Like this:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- clean && make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- KSRC=/home/manuel/src/mister/Linux-Kernel_MiSTer modules

But I always end up getting this:

/home/manuel/src/mister/rtl8188eus/os_dep/linux/os_intfs.c:1240:22: error: initialization of ‘u16 (*)(struct net_device *, struct sk_buff *, struct net_device *)’ {aka ‘short unsigned int (*)(struct net_device *, struct sk_buff *, struct net_device *)’} from incompatible pointer type ‘u16 (*)(struct net_device *, struct sk_buff *, struct net_device *, u16 (*)(struct net_device *, struct sk_buff *, struct net_device *))’ {aka ‘short unsigned int (*)(struct net_device *, struct sk_buff *, struct net_device *, short unsigned int (*)(struct net_device *, struct sk_buff *, struct net_device *))’} [-Werror=incompatible-pointer-types]
 1240 |  .ndo_select_queue = rtw_select_queue,
      |                      ^~~~~~~~~~~~~~~~
/home/manuel/src/mister/rtl8188eus/os_dep/linux/os_intfs.c:1240:22: note: (near initialization for ‘rtw_netdev_ops.ndo_select_queue’)

So, maybe I am doing something wrong?

Thanks!

Latest MiSTer/Linux (?) update breaks SNES Switch Online controller USB compatibility

Hi, I've been using the SNES Switch pad plugged into my MiSTer with a USB cable as my go-to and never had issues, but the latest update seems to have broken compatibility (now the controller just charges.) I do recall reading that there's been a change to how Linux polls inputs/how Bluetooth works and I assume they're related somehow, so I thought I'd bring it to everybody's attention here.

Extra disk operations in a new OS

Hello.

I moved from OS 210314 to the recent one (210825) and now I see Disk LED blinking even if the system is idle (1-4 blinks once in 4-7 seconds). Are there new apps added to OS that read/write the disk in the background? (I understand that there's a huge gap between 210314 and 210825)
Old system works fine...

wifi Realtek 8821AU/8812AU/8821CU broken drivers please sync with upstream

as per https://misterfpga.org/viewtopic.php?t=407&start=30
8821au based dongles seems to have trouble with associate even with open network
there is a better than upstream , maintainted by aircrack-ng project , driver for realtek 8821au/8812au/8821cu cards

https://github.com/morrownr/8821au-20210708
https://github.com/morrownr/8821cu-20210118
https://github.com/morrownr/8812au-20210629

which being updated and maintained by aircrack-ng community

ath9k_htc support

Hi, would it be possible to add this USB wifi driver to that standard kernel modules? It's a stock driver and does work on rpi arm. Thanks

Yan

https://wiki.debian.org/ath9k_htc

oled screen stops working after update / all linux.img kernel has one less file in a specific path

hello I hope I can explain myself well. After doing update / all, the initial oled screen that put a different logo on each core has stopped working. I think it is because the kernel of linux.img has changed along with some things and in the path etc / init.d / the file s60i2c2oled related to boot is missing at the boot of the mister.
any ideas on this?

Regression with PS5 controller behaviour since v5.13.12 release (erroneous inputs?)

Hi there,

Firstly, thanks for your hard work with the new kernel and all of the other major changes. It must have taken a lot of time and effort - like I said when responding to your update post on FB, these kind of 'under the hood' updates make a massive difference to MiSTer.

However, I believe I have discovered an issue with PS5 controller behaviour since the new kernel was released. I can replicate the issue easily and solve it by reverting back to the last release of the socfpga-4.19 kernel (210711) and MiSTer binary (210803).

Here are the details / process to replicate/solve:

1. PS5 controller is working well on previous kernel release (210711) and MiSTer binary (210803).

2. Update MiSTer to latest release (210825) and latest v5.13.12 kernel (210805).

3. As soon as the update is complete, the problems start - as follows:

• PS5 controller behaviour is erratic when using the analog sticks, a good example is Arkanoid. There is no smooth movement of the bat when moving the analog stick left and right, it jerks around and stops, etc. This is the same on any other game/core where you can use the analog stick (eg. Atari 5200).
• If you redefine the buttons using the global option on the MiSTer UI, since the update it will quickly skip past letting you define the 'right' dpad (it will flash up quickly and then go straight to defining 'left' - unless, you skip the 'stick 2 test: down' procedure (which precedes defining dpad 'right'). This then allows you to map the right dpad button.
• If you successfully define all your buttons, if you shake the controller on the menu screen it will move up and down. Same applies if you shake the controller when defining any buttons or directions, it will define a movement (I assume) to the action and move to the next button.

I'm not sure what's up but it looks like perhaps motion control is enabled, or something related to this is causing a ton of erroneous inputs perhaps?
Not sure if there is more to it, but perhaps something related is responsible for causing all of the above issues. Maybe a previous fix was not ported across during the move to v5.13.12?

4. To solve the problem, simply downgrade MiSTer and the kernel back to the previous version - I used the MiSTer SD utility to reflash the '210711' kernel (latest 4.19) and MiSTer binary file '210803' on the same SD card.

5. Once complete, everything worked perfectly well again with the PS5 controller. No issues or random inputs, analog behaviour is good.

6. I update again to the latest kernel and MiSTer binary, and the problems start again. Exactly as step '3'.

7. Revert one more time back to 4.19, the problem is solved once again.

NOTE 1: This behaviour affects both USB and Bluetooth.
NOTE 2: Unfortunately, I do not know if this issue also affects PS4 controllers, as I do not have one to test with.

I hope the above detail helps you to track the issue. If you require any testing I have 2xPS5 controllers and happy to assist if I can. I have a second SD card which I can test a different kernel with if you know what the problem might be.

Thanks!

Request: build Python with sqlite3 module

Please include the sqlite3 module for Python.

It will allow us to create faster, safer, and more elegant solutions for working with persistent data.

Such is the case with update/downloader scripts. The current downloader script from theypsilon uses large JSON encoded files to store relational data. [I've also experimented with using the available dbm and CSV modules; but they introduce their own issues.]

Note: The sqlite3 module has been part of the Python standard library since 2.5. There are currently random Python files [cruft?] on the file system that expect it.

WiFi region always "world" even when specified otherwise in wpa_supplicant.conf

The WiFi region on MiSTer seems to always be "world", even if it's set to TW or US or anything else in wpa_supplicant.conf.

As a result, I can't see my 5 GHz access point when it's set to certain US-specific channels, even when wpa_supplicant.conf is set to US. Being set to world may also limit the transmit power of the USB dongle, but this is a less critical issue.

Talking with @birdybro in the channel, we think that we need CRDA to be able to set the WiFi region correctly. Can we add it?

My adapter is a Asus AC-53 Nano (RTL8812BU), but from what I understand this doesn't matter.

Symptoms:

• Run iw reg get on any MiSTer and you get this:

# iw reg get
global
country 00: DFS-UNSET

• As a result the region being set to world, MiSTer won't ever see or connect to APs on certain region-specific channels even if wpa_supplicant.conf is configured correctly.

Request: enable rumble on Pantherlord USB to PS1 controller adapter

Hi,

If possible, please add CONFIG_PANTHERLORD_FF=y to kernel config file to enable rumble on Pantherlord USB to PS1 Dual adapter.

Best regards,

Wifi randomly pulls a second 169 IP, causing all internet connections to fail post-boot

Over the last week a few of us have been hammering at what is causing these weird wifi-related failures on boot at random. When they occur, the MiSTer gets an IP, even gets the time when you don't have an RTC board, and SAMBA/SSH connections work, but anything attempting to get an internet connection after that fails. Even nslookup google.com 8.8.8.8 fails with a timeout to the DNS.

What we have found are the following:

• The issue seems to stem from the commits around April 2022. This commit may be the underlying culprit, but it is unsure how.
• The issue will occur if the wlan0 interface exists when dhcpcd and ifup start up. Normally the interface does not exist until further in the boot process, but for mine it is there early (within a few seconds), so dhcpcd pulls an initial IP when its process is started.
• On my MiSTer, a second udev fires, causing a second lease to be called, and it obtains a 169 IP address, while the previous lease still has a correct local IP that is reachable. This does not fire automatically for most other people, but forcefully firing it does reproduce the issue: udevadm trigger /sys/class/net/wlan0 --action add
• Wifi seems to initiate for me very early, before the filesystem is mounted as r/w. This is not the case for most others. I am using a TP-Link Archer T3U Plus adapter (Amazon link). It is uncertain that this plays a factor in the issue at all. The random loss of internet occurs with the adapter from Porkchop as well, but it is uncertain that it is the same exact issue.
• Resetting the router does often fix the issue, but only shortly. Otherwise, you'll find the issue fixed after cold rebooting the MiSTer 6-10 times, and then it returns a number of days later again, requiring another count of excessive reboots to fix.
• dhcpcd fails to write the lease file to /var/lib/dhcpcd/interface-ssid.lease because the dhcpcd directory does not exist and it states the filesystem is read-only, which is the truth because it fires before the remount to r/w occurs. Considering I do not have an RTC addon (and the system time defaults to 1/1/1979), this means that the lease is about 40 years old once the time is pulled from NTP servers, which is most likely expired. It is uncertain if this causes it to pull a second lease.
• dhcpcd will also fail to write the duid to /var/lib/dhcpcd/duid, since it is a read-only filesystem at the time it runs.
• dhcpcd is outdated on the MiSTer. It is uncertain if updating it can be the fix. Possibly BusyBox needs work.
• The issue occurs with multiple of my own routers/modems, so the issue shouldn't be related to the router. The udev command is reproducible even on reputable routers.
• The DUID problem appears to cause some routers(mine) to give a new/different lease on every boot. Additionally it appears the r/o filesystem lease problem causes the system to trigger the IPV4LL behavior because if I move the lease directory to /media/fat/something with a symlink I can use the udevadm command multiple times and it just uses the existing lease.
• This second lease seems to load under udhcpd and not dhcpcd. It is probably best to only use one and not both. This may be causing issues.
• Depending on timing, the DUID can be static, but with my MiSTer it pulls it too early, and fails to keep it.
• The wifi initiating early is most likely caused by the wlan0 interface loading within the first few seconds of booting. On working MiSTers, it seems to not load the wlan0 interface for a while longer, which allows the system to work normally.
• Running rm /sbin/udhcpc causes ifup to use dhcpcd, and then the rc script starts another copy. It seems the priority for the startup script is to load udhcpc before dhcpcd. It would probably be best to only use dhcpcd. If udhcpd is wanted instead, eth0 does not load since it is not in the interfaces config file, so it would need to be added there.

Possible methods to fix (doing multiple is not a bad idea):

• Seemingly the beest way to fix could be to use wpa_supplicant hook scripts (/usr/share/dhcpcd/hooks/10-wpa_supplicant), but it is broken with the MiSTer's wpa_supplicant implementation. wpa_supplicant would need to be fixed. This would allow using dhcpcd.conf to address anything related to network issues. And have ifupdown just do loopback.
• Find what's causing the interface to exist on boot. This alone should fix the issue, but it is a bit of a dirty fix.
• Fixing write-permissions on boot, so dhcpcd can write the lease/duid files properly. Another dirty fix, but should address the issue.
• Fix it so only dhcpcd or udhcpd run, and not have a possibility of both. I recommend doing this regardless of other methods.

Any thoughts as to what may be directly causing this is welcome. I'd like to get to the bottom of this, as various users besides me have reported this happening at random with their MiSTer. We are using the latest Mr. Fusion images as far as I know.

I have attached my syslog for review.

/var/log/messages

https missing in latest python version

urllib.error.URLError:

Most likely caused by SSL missing

"HTTPS support is only available if the socket module was compiled with SSL support."

Is it possible openssl was missing from the compile?

How to know if a wheel device is supported?

See bottom of the screen.

Looks like my old "Guillemot Thrustmaster force feedback racing wheel" is getting detected by linux drivers. But I don't know how to later configure in PSX to make it work.

Is there any utility in the linux side to make sure it is getting well detected?

Request: Mouse Wheel as Spinner for 2 mouse objects

Moved here from this request MiSTer-devel/NeoGeo_MiSTer#161

https://www.amazon.co.jp/dp/B096FL5VXC/ - This is seen as a mouse device apparently, the trackball is the x and y for the mouse and the spinner is mouse wheel. vid:pid is 0ae4:0701 according to the user. Tested in the input core. Clockwise turn = increase mwhl number, counter-clockwise turn = decrease mwhl number.

https://www.amazon.com/gp/product/B002OOWB3O/ - This is a popular option for trackball users, seen as a mouse, trackball is x and y for the mouse, and the dial around the trackball is a mouse wheel. vid:pid is 047d:2048. When tested in the input core there is the same result as the first one, cw turn = increase and ccw turn = decrease. Below is the debug console output from this one:

clockwise

047d:2048:00 P0 Input event: type=EV_REL, Axis=8, Offset=-1
/dev/input/mouse0: dx=0, dy=0, scroll=1
PS2 MOUSE: 8 0 0 1

counter-clockwise

047d:2048:00 P0 Input event: type=EV_REL, Axis=8, Offset=1
/dev/input/mouse0: dx=0, dy=0, scroll=-1
PS2 MOUSE: 8 0 0 -1

Request: NFS support

The MiSTer having Linux under the hood, I was surprised to find out that kernel support for NFS isn't compiled in. While CIFS works, it's a very round about way to work for a Linux system. I'd rather not deal with Samba on my server system if it can be avoided. Compiling in support is no more than a single line in the kernel config.

If this gets an OK, I can start working on scripts that make it work in similar ways to the current CIFS implementation.

WiFi no longer connects on startup for Realtek chipset adapters

At some point in the past month, the Linux MiSTer distribution stopped connecting to WiFi with the MiSTer Addons WiFi + Bluetooth Adapter. This is a common Realtek Chipset rebrand.

After witnessing this on one system, I performed the same udpate on another outdated system with the same model WiFi dongle. It also is no longer working upon reboot, so I feel confident I could downgrade and that would fix the issue.

Here are the listings for both adapters

# ls usb | grep 802
Bus 001 Device 008: ID 0bda:818b Realtek Semiconductor Corp. RTL8192EU 802.11b/g/n WLAN Adapter
Bus 001 Device 006: ID 0bda:c820 Realtek Semiconductor Corp. 802.11ac NIC

Kuro Houou pointed out that upon starting from the system completely powered off, WiFi will connect if the Ethernet is plugged in first (confirmed using ip addr, showing both adapters getting IP addresses). I have confirmed this for both adapters.

I/O boards tested and confirmed:
Jammix
MiSTer Ironclad+
Retro Castle dual-ram

Here are various versions I have today, after updating:
MiSTer v240110
OS v231108
Linux MiSTer 5.15.1-MiSTer 1 SMP Wed Nov 8 16:41:16 CSG 2023 armv71 GNU/Linux

update_all.log

Sony DualSense (Wired) doesn't connect on official usb hub, but works on makerspot otg usb hub

Here's the log on my Makerspot OTG USB Hub, the Sony DualSense (DualShock 5) connected via USB-C.

log.txt

When I attempt to connect it on the other MiSTer I have which has a USB Hub 2.1 from misteraddons, here is the log:

log2.1.txt

Another user experienced the same kind of thing with their usb hub 2.1 in the discord, so I looked into it, and here are the results.

Segmentation fault in exFAT

A segmentation fault occurs when writing to a file in /media/fat using mmap. This is in code that worked before the recent kernel upgrade and which still works elsewhere on the filesystem. Since exFAT was ported in, I'm hoping you could review the issue.

Below is a sample application which forces the segmentation fault. The specific line it crashes on is memset.

#include <stdio.h>
#include <string.h>
#include <sys/mman.h>
#include <stdlib.h>
#include <fcntl.h>
#include <unistd.h>

int main(int argc, char *argv[])
{
    if(argc < 2)
    {
        printf("File path not mentioned\n");
        exit(0);
    }
   
    const char *filepath = argv[1];
    int fd = open(filepath, O_RDWR | O_CREAT);
    if (fd < 0)
    {
        printf("Could not open file\n");
        exit(1);
    }

    if (ftruncate(fd, 8192) != 0)
    {
        printf("Could not resize file\n");
        exit(1);
    }

    char *ptr = mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0);
    if (ptr == MAP_FAILED)
    {
        printf("Mapping Failed\n");
        return 1;
    }

    memset(ptr, 0, 1);

    if (munmap(ptr, 8192) != 0)
    {
        printf("UnMapping Failed\n");
        return 1;
    }

    close(fd);

    return 0;
}

Works: ./sample /test.txt
Works: ./sample /tmp/test.txt
Crashes: ./sample /media/fat/test.txt

Logitech controllers stops working after update script

Logitech controllers stops working after update script

Gamepads:
Logitech Cordless RumblePad 2
Logitech Wireless Gamepad F710

dmesg:

previous kernel - mr-fusion-v2.2:
input: Logitech Logitech Cordless RumblePad 2 as /devices/platform/soc/ffb40000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:046D:C219.0003/input/input4
logitech 0003:046D:C219.0003: input,hidraw2: USB HID v1.10 Gamepad [Logitech Logitech Cordless RumblePad 2] on usb-ffb40000.usb-1.3/input0
hid_logitech: Force feedback for Logitech force feedback devices by Johann Deneux [email protected]

after update script:
input: Logitech Logitech Cordless RumblePad 2 as /devices/platform/soc/ffb40000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:046D:C219.0004/input/input5
logitech 0003:046D:C219.0004: input,hidraw2: USB HID v1.10 Gamepad [Logitech Logitech Cordless RumblePad 2] on usb-ffb40000.usb-1.3/input0
logitech: probe of 0003:046D:C219.0004 failed with error -1

Thanks.

RTL8821AU with 5ghz support (TPLINK Archer T2U Nano and others)

hi,
i've tried the TPLink Archer T2U Nano with Mister (latest update) and it works flawlessy under 2.4ghz. With 5ghz networks, it doesn't work at all (can't find the network).
after a bit of search around, seems to be a common problem and i managed to compile an updated version of the driver, with specific Makefile tweaks for the Mister.

this is the original repo and here is the specific MiSTer build info on my fork.

it works flawlessy then with both 2.4 and 5ghz networks.

should be included in the main kernel replacing the old driver, imho ....

regards!

Auto fire 32ms Lag with Neogeo Core

With the latest kernel, the neogeo core has an issue with auto fire at default 32ms. It's a lot slower, feels likes it auto fires every 1 second.