search

BlissOS / bug_reports

0 stars 0 forks source link

WiFi APs Blank on Trial #24

Open datashuttle opened 6 months ago

datashuttle commented 6 months ago

On trial boot, no WiFi APs are shown available when there are many available.

electrikjesus commented 6 months ago

Please reply with the Bliss OS build you are testing and detailed information on your system hardware including Wi-Fi chipset included on the device.

datashuttle commented 6 months ago

Okay, sure. I didn't know that this bug GitHub was for all versions. I'm testing 16.x in beta, and using 15.9.x, and using an Intel NUC with 16 GB memory, and multiple TB of storage. The WiFi chipset is an Intel Dual Band Wireless-AC-9560, which is standard for that series of NUC . Note: The WiFi works fine on 15.9.x and prior versions.

electrikjesus commented 6 months ago

This repo handles issues for Bliss OS 16, 17, ++. Since we've released the v17 alpha, we have to get in the habit of asking version here too.

Are you also able to attach the results of lsmod > lsmod txt from ADB root or Termux after granting it Superuser access from KernelSU?

datashuttle commented 6 months ago

Okay, I see on the version reference. Are you asking for the kernel modules loaded for when I've loaded the live version of 16, If so, I'll have to load it because I'm currently in the throws of working with big mapping downloads in 15.9.x. So it may take me a few minutes to finish up that task, and load 16. Is there anything else you would like to know while I'm in 16?

electrikjesus commented 6 months ago

That is all I am thinking so far. If we need anything else we will reply

datashuttle commented 6 months ago

Okay, in 16 and with appropriate permissions granted to the shell. Command lsmod is not available in the live run. Which package is it in and I'll load it?

electrikjesus commented 6 months ago

It'll need root, or if you boot into debug mode DEBUG=2 androidboot.enable_console=1, you can use the alt-f1 root console to write it to a mounted USB drive or temp data folder for retrieval

datashuttle commented 6 months ago

Ok, booted to the first debug option in GRUB, and ran. Upon reaching the shell prompt, and shortly thereafter, it begins iterating USB devices without command, and it looks like an endless loop output as it doesn't stop. Am I booting the correct debug mode in GRUB?