Home of the Squeezebox™ & Transporter® network music players.
Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 33
  1. #21
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    4,419
    This chipset does not use firmware, so that is of no consequence.

    I think at this point, we need to validate which driver you were actually using. Assuming your pCP7 image is still working. Can you post the output of

    lsmod

    and then run dmesg, and look towards the end, there should be a section that shows the detection of the wifi chipeset. Need to see the USB identifiers. xxxx:xxxx
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  2. #22
    Quote Originally Posted by paul- View Post
    lsmod

    and then run dmesg, and look towards the end, there should be a section that shows the detection of the wifi chipeset. Need to see the USB identifiers. xxxx:xxxx
    Thanks for the response, sorry for the delay. (My pCP is remote and not always accessible.)

    Digging into the driver install was my next plan, and yes the USB ID is key.

    I have been through this before on x86 Ubuntu and I am pretty sure the aircrack-ng 8812au driver is the one I need (88XX) but I am not sure why it isn't loading in my pCP 8 setup.

    I now have two separate SD images (a working 7 and 8), a debug display and USB keyboard, as well as pCP proximity. So I plan to dig into this later today or over the weekend.

    Will report back on what I find, thanks again.

  3. #23
    Here is the specific USB WiFi dongle model I use:

    https://www.edimax.com/edimax/mercha...and/ew-7811utc

    I fired up my pCP 7, the dongle works great. Here's some driver-related stuff:

    dmesg:
    [ 4.652782] usb 1-1.3: new high-speed USB device number 4 using dwc_otg
    [ 4.783956] usb 1-1.3: New USB device found, idVendor=7392, idProduct=a812, b
    cdDevice= 2.00
    [ 4.783987] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber
    =3
    [ 4.784006] usb 1-1.3: Product: Edimax AC600 USB
    [ 4.784024] usb 1-1.3: Manufacturer: Realtek
    [ 4.784041] usb 1-1.3: SerialNumber: 00e04c000001
    [ 145.892993] usbcore: registered new interface driver 8812au

    lsusb:
    Bus 001 Device 004: ID 7392:a812

    lsmod:
    8812au 1454080 0
    cfg80211 671744 1 8812au

    I expected to find a 8812au driver module in /lib/modules, but did not. Is 8812au built into the pCP kernel?

    tc@piCorePorch:/lib/modules$ find . -name "*88*" -print
    tc@piCorePorch:/lib/modules$

    Maybe that's a clue as to why pCP 8 is not loading the separate 88XX driver?

  4. #24
    Quote Originally Posted by Braklet View Post
    I expected to find a 8812au driver module in /lib/modules, but did not. Is 8812au built into the pCP kernel?
    Expanded my search, and found the associated driver module:

    /usr/local/lib/modules/5.4.83-pcpCore/kernel/drivers/net/wireless/realtek/rtl8812au
    /usr/local/lib/modules/5.4.83-pcpCore/kernel/drivers/net/wireless/realtek/rtl8812au/8812au.ko

  5. #25

    /lib/modules versus /usr/local/lib/modules ... ?

    I rebuilt my wireless driver extension on my pCP 7 system, installed and rebooted back into pCP 7. Here are the associated directories for both 7 and 8 kernels:

    Code:
    tc@piCorePorch:/$ sudo find / -name "*pcpCore*" -type d -print
    /lib/modules/5.10.42-pcpCore
    /lib/modules/5.4.83-pcpCore
    /tmp/tcloop/alsa-modules-5.4.83-pcpCore
    /tmp/tcloop/alsa-modules-5.4.83-pcpCore/usr/local/lib/modules/5.4.83-pcpCore
    /tmp/tcloop/wireless-5.4.83-pcpCore
    /tmp/tcloop/wireless-5.4.83-pcpCore/usr/local/lib/modules/5.4.83-pcpCore
    /tmp/tcloop/media-rc-5.4.83-pcpCore
    /tmp/tcloop/media-rc-5.4.83-pcpCore/usr/local/lib/modules/5.4.83-pcpCore
    /tmp/tcloop/88XXau-5.10.42-pcpCore
    /tmp/tcloop/88XXau-5.10.42-pcpCore/lib/modules/5.10.42-pcpCore
    find: /proc/8534: No such file or directory
    find: /proc/8536: No such file or directory
    /usr/local/lib/modules/5.4.83-pcpCore
    tc@piCorePorch:/$
    There is definitely a new driver in the tcloop location, obviously not loaded into the running 5.4 kernel:

    Code:
    tc@piCorePorch:/tmp/tcloop/88XXau-5.10.42-pcpCore/lib/modules/5.10.42-pcpCore/kernel/drivers/net/wireless$ ls -al
    total 2258
    drwxr-xr-x    2 tc       staff           32 Sep 24 10:23 ./
    drwxr-xr-x    3 tc       staff           31 Sep 24 10:23 ../
    -rw-r--r--    1 tc       staff      2311556 Sep 24 10:22 88XXau.ko
    I can't help but wonder if /lib/modules vs. /usr/local/lib/modules has an impact on future loading into the 5.10 kernel... I'll have to connect a monitor/KB before running the in-situ upgrade to pCP 8.

  6. #26
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    4,419
    That's just a piCore think as to why modules are in usr/local/..... there is a symlink that connects it back to /lib/modules/xxxx. You can put your driver anywhere in the tree under /lib/modules/5.10.42-pcpCore/....... depmod tells the kernel where to find it.

    Did you make this change to the driver source when you downloaded it?
    https://github.com/aircrack-ng/rtl88...-raspberry-rpi

    I can pm you a link to what I compiled to see if it helps. I have not been able to find my USB sticks that use this driver. Seems I put them all onto production machines,
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  7. #27
    Quote Originally Posted by paul- View Post
    Did you make this change to the driver source when you downloaded it?
    https://github.com/aircrack-ng/rtl88...-raspberry-rpi
    I followed your README here https://github.com/piCorePlayer/pCP-Kernels

    The result is the same: all Makefile CONFIG_PLATFORM* options are n except for

    CONFIG_PLATFORM_ARM_RPI = y

    I want to try loading my pCP 8 SD with a monitor/KB just to see what's going on before I try anything else.

  8. #28

    Attempting to run 8.0.0 with manual 88XX driver, monitor and KB

    Restarted with my 8.0.0 SD, monitor and KB.

    The extension loading phase was MUCH faster than with my 7.0.1 SD, leading me to believe something critical is not loading.

    Console output reflects my migrated 7.0.1 configuration in 8.0.0. The system thinks it enables WiFi and wlan0. Console keeps "waiting for network" and printing '.'.

    lsusb recognizes my Edimax WiFi USB dongle correctly.

    lsmod shows NO wireless drivers at all.

    modprobe -a restarted things, got rid of the constant '.', but still no wireless drivers.

    Will update this post as I learn more.

    later... FIXED MY PROBLEM, pCP 8.0.0 is now able to utilize my local-built 88XXau.ko driver!

    Problem: I fumble-fingered my onboot.lst entry, so it couldn't read my new WiFi driver extension. Chalk this up to pilot error, duh.
    Last edited by Braklet; 2021-09-24 at 13:46.

  9. #29
    Quote Originally Posted by Braklet View Post
    Problem: I fumble-fingered my onboot.lst entry, so it couldn't read my new WiFi driver extension. Chalk this up to pilot error, duh.
    Don't know how much of my own ignorance I want to put on display, but I have a related script change request and welcome further discussion.

    I ran into a couple issues with the driver build based on use of the "KERNEL" abstraction in instructions and script output.

    My problem is that I added "88XX-KERNEL.tcz" to my tce/onboot.lst, since that's what pcp_make_module_extension suggested.

    So, can you change this line:

    https://github.com/piCorePlayer/pCP-..._extension#L26

    from
    Code:
    ONBOOTNAM="$EXT-KERNEL.tcz"
    to
    Code:
    ONBOOTNAM="$EXTNAM.tcz"
    since "EXTNAM=$EXT-$KERNELVER" is exactly what's needed in onboot.lst?

    I just ran a quick little test on my pCP and that output looks right:

    Code:
    tc@piCorePorch:~/.local/bin$ ./pcp_make_module_extension -k 4.15.30-pcpRLR -e 88xxRR
    [ INFO ] The extension can be found at /tmp/88xxRR-4.15.30-pcpRLR.tcz
    [ INFO ] move 88xxRR-4.15.30-pcpRLR.tcz and 88xxRR-4.15.30-pcpRLR.tcz.md5.txt to /mnt/mmcblk0p2/tce/optional
    [ INFO ] Then edit /mnt/mmcblk0p2/tce/onboot.lst and add 88xxRR-4.15.30-pcpRLR.tcz to the list.
    In any case, I could never have gotten this working without your handy pCP-Kernels scripts, so once again THANK YOU!
    Last edited by Braklet; 2021-09-24 at 14:25.

  10. #30
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    4,419
    I’m not following, because -KERNEL is precisely what should be in onboot. The word KERNEL gets replaced in the extension loader by the running kernel name.

    Yes it means the new extension won’t mount under the old kernel…..but that’s of no consequence, since only matching kernel names will actually load.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •