paul- wrote:
> You cannot do this.
>
> >
Code:
> >
> pcp_make_module_extension -k 5.10-42-pcpTEST -e 88XXauTEST
>
> >
>
> The kernel name that you use in the build scripts, must match the name
> of the kernel shown when you run `uname -r`
You cannot do this.
Code:
pcp_make_module_extension -k 5.10-42-pcpTEST -e 88XXauTEST
The kernel name that you use in the build scripts, must match the name
of the kernel shown when you run `uname -r` in pcp8. WEhich for a
pizero is
paul- wrote:
> Im 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.
I'm missing something here, because my 8.0.0 system did not load the
extension until after I changed onboot from
Im 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 wont mount under the old kernel
..but
thats of no consequence, since only matching kernel names will
Braklet wrote:
>
> 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
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
paul- wrote:
>
> Did you make this change to the driver source when you downloaded it?
> https://github.com/aircrack-ng/rtl8812au#for-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
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/. 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
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
Braklet wrote:
>
> 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
Here is the specific USB WiFi dongle model I use:
https://www.edimax.com/edimax/merchandise/merchandise_detail/data/edimax/au/wireless_adapters_ac600_dual-band/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
paul- wrote:
>
> 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. :
Thanks for the response, sorry for the delay. (My pCP is remote and not
always accessible.)
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
I believe you need to load wifi firmware extensions first before
wireless_tools.tcz.
Note: The order was important originally, I am only assuming it still
is!
Greg Erskine's Profile:
Extension name does not matter. Really need a keyboard and monitor to
connect and see what is going on. Ive not been able to test the driver
I built. All of my sticks I that use this driver are at work.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage:
Braklet wrote:
>
> Do you think it's worth rebuilding my extension using "-e 88XXau" ?
I tried it, no change. No LED activity from the WiFi USB dongle.
Have to ponder my next course of action.
Braklet's Profile:
paul-1, is the extension name critical in loading? I used "88XX" as my
extension name, and got these extensions as a result:
88XX-5.10.42-pcpCore.tcz
88XX-5.10.42-pcpCore.tcz.md5.txt
But the actual driver name is "88XXau.ko" in the contents:
D:\Devices\Raspberry
Sadly, my wireless drivers didn't work after the 8.0.0 upgrade. The
LEDs on my pCP Pi B+ showed CPU activity, but the WiFi dongle never
recovered any LED activity, indicating no drivers.
I'm pulling an SD image now, in case I want to debug further. I will
restore the 7.0.1 image I took a
paul- wrote:
>
> Then obviously move it to the proper location.
Hi paul-1, your instructions worked a treat. Here's what I now have in
/mnt/mmcblk0p2/tce/optional:
Code:
tc@piCorePorch:/mnt/mmcblk0p2/tce/optional$ ls -al 88*
-rw-r--r--1 tc staff
paul- wrote:
> The wifi driver does indeed take forever to compile on a piZero. Anyway
> I found the problem
>
I will give this a go tomorrow. Thanks very much, paul! I do
appreciate your help with this, pCP allows me to maintain my now
decades-old LMS ecosystem.
The wifi driver does indeed take forever to compile on a piZero. Anyway
I found the problem
Download new copies of the build scripts from the github. To avoid
recompiling do this.
sudo mkdir -p /lib/modules/5.10.42-pcpCore
sudo ln -s /lib/modules/5.10.42-pcpCore/build
touch /tmp/mark
cd to
Give me a chance to run through it.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=U7JHY5WYHCNRU=GB_code=USD=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted)
if you
And if it isn't obvious, THANK YOU for all the work you have put into
pCP, and dealing with all this stuff. Probably time for another project
contribution...
Braklet's Profile:
paul- wrote:
> I'm concerned about the error. It seems part of the install script from
> the source package did not pickup the new kernel name, and used the
> running kernel name. The extension may have no contents. However the
> compiled driver should still be sitting on the persistent
paul- wrote:
> Rebooting is fine, since you are on 7.0.1. The new kernel drivers
> would not be used anyway. I'm concerned about the error. It seems part
> of the install script from the source package did not pickup the new
> kernel name, and used the running kernel name. The extension
Braklet wrote:
> I have set up cross-compile environments for OpenWrt and work with Yocto
> and buildroot occasionally, so I'm not completely clueless there. But I
> have never worked with TinyCoreLinux or tried to build PiCorePlayer.
> What's involved in your driver build environment?
RPI
Rebooting is fine, since you are on 7.0.1. The new kernel drivers
would not be used anyway. I'm concerned about the error. It seems part
of the install script from the source package did not pickup the new
kernel name, and used the running kernel name. The extension may have
no contents.
I rebooted back into 7.0.1 with my new driver in onboot.lst, and
wireless came back up. (This is a headless system, wifi only.)
I will probably shut it down, take a SD card image, and then attempt a
8.0.0 in-situ upgrade.
But I am still very interested in swapping to in-tree USB WLAN
paul- wrote:
> If you have an x86_64 ubuntu system, you could also cross compile the
> driver. I use a x86_64 system to compile all of the pCP kernels.
I have set up cross-compile environments for OpenWrt and work with Yocto
and buildroot occasionally, so I'm not completely clueless there.
Editing the quote...
paul- wrote:
> there is a chance you are running low of ram.
> You can look at the drivers in the extension wireless-KERNEL.tcz and see
> the list of drivers.
> What are your wifi specs? I don't have a good feel of the AC and AX
> chipsets that work. (Since I use the
If you have an x86_64 ubuntu system, you could also cross compile the
driver. I use a x86_64 system to compile all of the pCP kernels.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Single core chips also have limited memory available, there is a chance
you are running low of ram. Swap files are disabled by default.
Perhaps remove nozswap from the command line. As for what's in the
kernel, lists of drivers to chipsets to commercial products are not well
maintained.
32 matches
Mail list logo
