There is an 8812 driver in my repository, however I do not have an 8812 chipset device so my kernel driver caused elevated cpu spikes and with a 32bit os and kernel that can only address 3072mb physical memory addressing (ram) I excluded it from being a default kernel driver, I will send a link to the driver download..
The driver download I listed is only for TinyPaw, will not work for tiny core. It was compiled kernel driver for TinyPaw linux, you could try to load it in tiny core, it was compiled for kernel 4.14.10 - copy the .tcz file into the /mnt/***/tce/optional folder and either open apps browser and select load extension locally or from the command line using tce-load -l extension_name
First off, yes I am still alive... *Evil laughter* Development has resumed on TinyPaw-Linux, many things are being changed and redone and cleaned up. Base so far is the same - TinyCore base, 6.1.x kernel, everything is being recompiled from source and updated, new libs, updated cryptography, updates to tools and all the junk completely gutted. After much consideration I am dumping the HackedBox window manager in favor of a customized version of JWM Tools, core packages & libs rebuilt and compiled from source so far against kernel 6.1.x Aircrack-ng 1.7 - built with extra (python3.9) scripts & compiled against libgcrypt 1.10.3 & libpcap 1.11 Bully 1.4 - kimocoder fork compiled against libpcap 1.11 Cowpatty 4.8 - compiled against libpcap 1.11 Hcxdumptool 6.3.2 Hcxtools 6.3.2 Hostapd-wpe 2.10 - patched Libcares 1.14.0 Libcap-ng 0.8.4 Libgcrypt 1.10.3 Libgpg-error 1.14 Libsmi 0.5.0 Macchanger 1.7.0 Mdk3 - v6-mod-musket-r1 fork Mdk4 4.2 Pixiewps 1.4.2 - compiled against libpcap 1.11 Pyrit 0.5.1 - compiled against libpcap 1.11 Reaver-wps 1.6.6 - t6x fork compiled against libpcap 1.11 Tcpdump 4.99.4 Tshark 4.2.1 - compiled against libpcap 1.11, libcares 1.14.0, libgcrypt 1.10.3 & libsmi 0.5.0 Wifite2 2.7.0 - kimocoder fork updated with python3.9 Zizzania 0.3.0 - compiled against libpcap 1.11
The next version of TinyPaw-Linux will soon have a release candidate, and official release. Some screenshots so far.. Plenty of attack and auditing tools - obviously geared mostly towards wifi/wireless security Tried to include a variety of tools across practical categories JWM menu entry for starting/stopping airmon functionality - ie wlan0 into wlan0mon, etc, etc Plenty of password auditing options New release builds of GUI tools and compiled against new libs and kernel
r1sen updated TinyPaw-Linux with a new update entry: New TinyPaw-Linux release build! Read the rest of this update entry...
as in it was compiled exclusively against the libgcrypt cryptography library instead of openSSL which is the default for aircrack
I have since pretty much the beginning compiled aircrack against libgcrypt exclusively for my project which is also the default library used for tshark and wireshark. Currently TinyPaw v2.0 uses the libgcrypt 1.11.pre-git version of the library or in other words the absolute newest source available of the crypto library.
sorry but not start for me I have tried with imagewriten, unebooting and from console like this: dd bs=4M if=TinyPaw_v2.0_hybrid.iso of=/dev/sde status=progress && sync no way
Just wrote an image using USB Image Writer in Debian using tinypaw_v2.0_hybrid iso... not entirely sure what issue you are having?
hmmm though I am not sure precisely what you are referring to I seemed to have caught a bug running from USB on another test machine involving the graphics driver TP is using with xorg, I am testing some alternate options. in a specific hardware configuration I am causing a waitforx error.. I may be re-releasing v2.0
After countless testing and evaluation I can say that there seems to be a bug in one of two places in the new TinyPaw build - which is built off of Tiny Core 14... certain display cards, potentially more affecting nvidia cause a "fail in waitforx" in the initialization of Xorg on boot. I have tried firmware, without firmware... with nvidia drivers, without... using nouveau, using generic vesa... nothing. I am writing this off as an issue in Xorg package itself or how it interacts with device drivers.. I say this because other display servers - such as xvesa & fbdev seem to have no issues with certain cards.. or any when booting from USB. Previous TinyPaw release also had no issue booting from USB.. at least with most display cards using Xorg and a generic xf86-video-vesa driver package. The previous version was tested booting off a test system with this card and no issues. Not sure if it is a kernel bug in 6.1.2 or an issue with device driver package or Xorg itself.. In the interim between my next release/update if anyone tries boot TinyPaw on physical hardware and encounters Xorg failure with a waitforx error please try installing and running from a virtual environment for best compatibility. Confirmed functionality in both VirtualBox and KVM. Now to answer the likely question of why have Xorg then and not one of the other display servers that are confirmed to work fine? Unfortunately many GUI applications and libraries in TinyPaw use Xorg and Xorg components as a dependency in both compiling and runtime. So you would on one hand gain very generic video compatibility but lose a large amount of packages and tools.
r1sen updated TinyPaw-Linux with a new update entry: New TinyPaw-Linux release build! Read the rest of this update entry...
aware when i can i comment xD --- Double Post Merged, 2 Apr 2024, Original Post Date: 1 Apr 2024 --- dont start no way is not a problem of xorg is a problem or syslinux or like this that is not here either finally i'll have to try it in VM i'm looking at it
makes no sense - the boot splash and kernel messages wouldn't scroll if it was syslinux or core - it's at the point of x-init, I installed on USB and got failed in WAITFORX messages - and Xorg fails to start and spits back (EE)no screens(EE) errors Definitely this kernel and Xorg seem to have several issues - there seems to be some issues with video working with certain version of VBox in windows.. not sure what exactly or where the issue lies :/
I can confirm that it boots and runs fine under KVM and VBox with a linux host, I also spun up a vanilla respin of tiny core linux 14 with kernel 6.1.2 with Xorg as display server and booting from USB on physical hardware Xorg crashes regardless of display drivers or firmware installed on the instance of tiny core - very frustrating lol previous tinypaw used Xorg and no special display firmware or device drivers and none of this issues - gotta be something on the kernel level or Xorg versioning for this kernel release
