Closed dancat closed 1 year ago
I have a little problem here. I am trying to use and usb dongle that behaves kind of strange. It is based on 8188EUS (Bus 004 Device 002: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter) and it is working well as soon as also the wired network is connected. If I unplug the wired network, also the wifi starts to get disconnections. I am trying to build another module from here: https://github.com/aircrack-ng/rtl8188eus but I need the linux-headers for 6.1.10-rockchip64, but I cannot find them anywhere. Any idea where can I find the package?
@dancat , thank you for the update. I will put MKS SKIPR remark to the latest release page.
IRQ#57
issue is present for MKS PI boar too. I am not sure it's critical. At leas my printer runs without any issues.
About sources... I am not sure how it works for already build kernel. Release 0.1.9-23.02.2
uses v5.15.92 (current) and v6.1.10 (edge).. I would say you have a 2 options to get a sources:
In first case you would have sources with all Armbian patches applied. In the second option fresh sources without any custom patches.
Which feature would you like to have?
Hi, first thank you very much for this! I have just tried the Jammy image and it works just fine on MKS SKIPR also.
The only problem I can see is a crash dump in dmesg: 53.555017] Call trace: [ 53.555026] dump_backtrace+0x140/0x150 [ 53.555052] show_stack+0x18/0x28 [ 53.555068] dump_stack_lvl+0x68/0x84 [ 53.555095] dump_stack+0x18/0x34 [ 53.555118] report_bad_irq+0x4c/0xdc [ 53.555138] note_interrupt+0x164/0x378 [ 53.555161] handle_irq_event_percpu+0x4c/0x60 [ 53.555180] handle_irq_event+0x48/0x98 [ 53.555199] handle_level_irq+0xd0/0x160 [ 53.555221] generic_handle_domain_irq+0x2c/0x48 [ 53.555240] rockchip_irq_demux+0x9c/0x220 [ 53.555265] generic_handle_domain_irq+0x2c/0x48 [ 53.555283] gic_handle_irq+0x98/0xd0 [ 53.555301] call_on_irq_stack+0x2c/0x54 [ 53.555321] do_interrupt_handler+0xd8/0xf0 [ 53.555343] el1_interrupt+0x38/0x70 [ 53.555360] el1h_64_irq_handler+0x18/0x28 [ 53.555377] el1h_64_irq+0x64/0x68 [ 53.555393] arch_cpu_idle+0x18/0x28 [ 53.555410] default_idle_call+0x40/0x168 [ 53.555434] do_idle+0x1ec/0x250 [ 53.555457] cpu_startup_entry+0x28/0x30 [ 53.555479] kernel_init+0x0/0x130 [ 53.555497] arch_post_acpi_subsys_init+0x0/0x18 [ 53.555523] start_kernel+0x99c/0x9d4 [ 53.555546] primary_switched+0xb4/0xbc [ 53.555570] handlers: [ 53.555577] [<00000000dbfee410>] irq_default_primary_handler threaded [<00000000a8b57b68>] regmap_irq_thread [ 53.555621] Disabling IRQ #37
I am not sure that is caused by you as a similar one can be seen also on the 'official' MKS image for MKS SKIPR, just that there the IRQ#57 is disabled.
Thanks for this again and have a nice day!
Funding