Tiny Core Base > CorePlus
Problem with rtl8188EUS wifi USB adapter
notferrari:
--- Quote from: curaga on September 22, 2023, 12:29:01 PM ---Did you run out of space?
--- End quote ---
I think this might be the issue, didn't think of that... :-\
home folder stays in RAM, right?
If that's the case, it's probably that.
I'll format a pendrive with ext4 and try again.
aus9:
Hi
my 2 cents worth. Fixing partition file type to ext4 is good but does nor resolve an issue where you are loading into RAM drive very large files etc
so please make a very large swap partition
As you have not mentioned the size of pendrive.....I will let others decide whats best there
but.....if space on pendrive is still an issue....consider using firefox or whatever to change your downloads from
$HOME/Downloads to another usb stick
In firefox -> settings (General) -> Downloads -> click on browse and choose a new usb stick etc
2) and I suggest even with above.....consider booting with a boot code home=sdb1 or whereever your home dir is.
There are advantages and disadvantages of this....but it should free up some RAM
You should make a backup of your home independently on another stick first for any previous downloads you need to keep
or files you need to keep
That is because when you reboot with that bootcode you lose some home stuff and also you need to remove home from backup
such that my /opt/.filetool.sh has only entries
opt
etc/fstab
Then over reboot....you add back your missing files from your other usb stick
aus9:
Hi
At the risk of appearing to blog, when I am actually trying to resolve my 32 bit module build failure.....I have just looked at my TC64 kernel prep and re-did my TC64 kernel module. There are some things that might be useful for members and OP, depending on his level of knowledge, to know
1) I do not have a System.map anywhere, nor can I see one in an unpack of the 32 bit ISO
2) The realtek module compilation, if successful creates an empty file called Module.symvers such that
--- Code: ---ls -al Module.symvers
-rw-r--r-- 1 root root 0 Sep 23 06:24 Module.symvers
--- End code ---
and if I do a make clean....this file is deleted. I admit I should have read my Makefile before posting about trying renames and other gargage,
sorry about that.
Anyhow on TC64 the module build reports
--- Code: ---make all
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.1.2-tinycore64/build M=/tmp/rtl8188eu modules
SNIP
MODPOST /tmp/rtl8188eu/Module.symvers
# TEST direct injection
make install
install -p -m 644 8188eu.ko /lib/modules/6.1.2-tinycore64/kernel/drivers/net/wireless/
/sbin/depmod -a 6.1.2-tinycore64
# NOTE no errors for bad symbols so it looks good to me
--- End code ---
I might try to use a changed ARCH & cross compile on TC64 but with an unpack of 32 bit K source and modules in ram drive,
before I try qemu
and proof of net on TC64
--- Code: ---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:5 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:62 errors:0 dropped:0 overruns:0 frame:0
TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5212 (5.0 KiB) TX bytes:5212 (5.0 KiB)
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:492 errors:0 dropped:4266 overruns:0 frame:0
TX packets:241 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:258891 (252.8 KiB) TX bytes:29268 (28.5 KiB)
--- End code ---
If I was not on a tower, I would be tempted to suggest to OP to blacklist his ethernet module, mine shows up as r8169
aus9:
hI
My first attempt X compile has failed. Plus not sure I am doing it right but I modified or looked at these lines in the Makefile
--- Quote ---# SUBARCH := $(shell uname -m | sed -e s/i.86/i386/) -> x86
# ARCH ?= $(SUBARCH).....leave alone
# line 1355 CROSS_COMPILE ?= NOW left alone y fails
# KVER ?= $(shell uname -r) -> 6.1.2-tinycore
# KSRC := /lib/modules/$(KVER)/build....leave alone
# MODDESTDIR := /lib/modules/$(KVER)/kernel/drivers/net/wireless/.....leave alone
--- End quote ---
I linked the 64 bit kernel source which IMHO is the same as a 32 bit source to /lib/modules/6.1.2-tinycore/build
but cheated by copying my 64 bit modules....tricked because Module.symvers as discussed was a zero byte file in module source.
such that
--- Code: ---file 8188eu.ko
8188eu.ko: ELF 64-bit LSB relocatable
--- End code ---
Which is not was I expecting. I had error trying to put a y against X compile, I did not keep the error but claimed something like
it was looking for ygcc
I am vaguely aware that there might be a cross compiler setup that I have failed to setup. Need rest now. Unlikely to succeed in the next few days unless I can setup qemu.
thanks for reading
aus9:
Hi patrikg
Due to dumb luck I appear to have got some stuff now downloaded with a persistent tcedir in qemu.
altho its nobodies fault....I actually prefer not to use openssh to transfer files, altho its a bit easier with lxterminal
my current boot up for those interested is, after initial setup but avoiding bridge network for now
--- Code: ---tce-load -i qemu bridge-utils # I know I can leave out bridge
sudo modprobe kvm-amd # as my host is AMD
qemu-system-i386 -enable-kvm -hda vdisk.img -m 4G
--- End code ---
My guest, I can not find spice on TC32, which I was hoping to use with copy and paste between machines.
If I can not build it.....I might have to setup openssh....I am very reluctant to bridge. I attempted it once and lost the net ;D
Since you were kind enough to recommend qemu.....before I dig too many holes,
let me know your thoughts please?
Thanks....and sorry if I am hijacking OP thread....but I think the goal for me to build 32 bit module is looking closer
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version