Tiny Core Base > CorePlus
Problem with rtl8188EUS wifi USB adapter
nick65go:
@patrikg: about " i like to make make a small Linux that fit on floppy".
IMHO I think there is no USEFUL "linux" on a floppy (max. 1.2 -1.4MB), smaller than:
https://en.wikipedia.org/wiki/KolibriOS
https://en.wikipedia.org/wiki/Tomsrtbt
I mean to have a kernel + a shell + few utilities + (eventually) a GUI.
FYI: Kolibri-OS has one GUI, because was written in FASM (Fast ASM, machine code).
ps: KolibriOS is NOT Russian OS
https://en.wikipedia.org/wiki/Talk:KolibriOS
The smaller it gets, then the less useful it becomes, we go in micro-controllers etc. (no human interface, just signals).
patrikg:
Yes I know that, but i think that cheating.
I have build just with the current kernel and current busybox and booting that with old lilo that not have lot of tons of that i don't need, like systemdboot and grub or syslinux.
Menuet and Kolibri, i think it's little easier to use fasm and it's inbuilt preprocess macro language, then nasm gas or another assembler.
I think this two OS is not very easy to accomplish.
I don't use the floppy at all, i doing it because, i learning more and more, what's behind some hidden curtains. And in this summer i take the LFS for a challenge, and getting it running in a vm in libvirt. Just for fun and learning.
Lua, why not python :) ??
For our children to not get tired to type in some characters and not getting some thing back(output)
Every language have it's own potential to shine.
It's not the program language that desire what it's want to be built.
Right now humans is pressing the keys.
Don't know how the future will be with the AI.
nick65go:
--- Quote from: patrikg on September 25, 2023, 02:54:25 PM ---Yes I know that, but i think that [is] cheating.
--- End quote ---
It says “all is fair in love and war.”.. and in linux! as long as the target is achieved in the affordable time frame. Time is the most scarce resource. So time has the maximum exchange value (is priceless). Why to invent the wheel again and again; maybe is better to "build"/cheat walking on the path the pioneers/experts already tried (K.I.S.S.).
aus9:
Hi notferrari
I have picked up my dummy....kernel module is built on qemu, tested by direct injection on TC32, package not yet built as I was not sure if everything would work. IT DOES proof
--- Code: ---tc@box:~$ inxi -Nxxx
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
Device-2: Realtek 802.11n NIC driver: rtl8188eu type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 1-3:2 chip-ID: 2357:010c class-ID: 0000
serial: 00E04C0001
tc@box:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:100 (100.0 B) TX bytes:100 (100.0 B)
wlan0 Link encap:Ethernet HWaddr 50:3E:AA:42:94:1D
inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:229 errors:0 dropped:4 overruns:0 frame:0
TX packets:182 errors:0 dropped:4 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:157644 (153.9 KiB) TX bytes:27738 (27.0 KiB)
--- End code ---
aus9:
The reason why I was failing in the past.....grrr....was I have only ever built one kernel module on TC
The error I was getting was unknown symbols in module.
This tricked me into thinking my kernel prep was somehow wrong. It was not.
The trick on TC32, which I did not do on TC64 was to load the run dependency module for 8188eu
Then build the module
--- Code: ---modinfo 8188eu | grep dep
depends: cfg80211
--- End code ---
I hope to build the package later today, test it and will give you a pm on how to get it early.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version