Tiny Core Linux
Tiny Core Base => Raspberry Pi => piCore Test Releases => Topic started by: bmarkus on December 06, 2014, 11:55:27 AM
-
Team Tiny Core is pleased to announce that piCore 6.0 Beta2 is available for public testing:
http://repo.tinycorelinux.net/6.x/armv6/release_candidates/
This is a beta level cut. If you decide to help test, then please test carefully. We don't want anyone to lose data.
Since this is an beta cut, although the team has worked through several preview cuts, we ask that only experienced users test. This cut is not for production use. The features in any beta may change before a public release candidate is available.
Note that the fltk library has been updated to 1.3.3 to enable unicode. fltk-1.1 and 1.3 can be installed at the same time, and old apps using 1.1 will continue to work.
We appreciate testing and feedback.
Changelog for 6.0 Beta2:
* kernel updated to 3.17.4
* RPi firmware updated to December 3 release
* serial terminal now started by default
* preinstalled components updated
Changelog for 6.0 Beta1:
* kernel updated to 3.17.3
* glibc updated to 2.20
* gcc updated to 4.9.2
* e2fsprogs base libs/apps updated to 1.42.12
* util-linux base libs/apps updated to 2.25.2
-
Hi bmarkus!
Took the second beta for a little spin today and it seems just OK! Good work!
Have fun making TC for RPi 'shine',
meo
-
Thanks Meo
-
SSH, X version working so far.
Was just wondering if the I/O stuff should be included as standard.
I can access the GPIO pins through /sys/class...
But for i2c sensors I use i2c-tools, so it is the 1st thing I install.
Have not done SPI in PiCore yet so not sure what is needed.
-
Thanks for the feedback.
Regarding I/O I2C and SPI kernel modules part of base.
-
Yep, Also must remember to turn off serial console now.
Was trying new version SSH it boots then does nothing.
Commenting out #/sbin/getty in bootlocal.sh got keyboard back.
-
Yep, Also must remember to turn off serial console now.
Was trying new version SSH it boots then does nothing.
Commenting out #/sbin/getty in bootlocal.sh got keyboard back.
Tested with SSH image downloaded from the server. Keyboard, serial terminal and SSH works out of box as expected.
-
Tested X version with installed wifi.tcz. Still need to be installed additional rtlwifi firmware to work with RTL8188CUS dongle.
After the reboot there are still module loading issues at variety hardware around USB hub. The 5 sec delay is not enough.
The LAN network need some time to start working and WiFi is even more delayed and not stable. The LED on the dongle is still ON independently on the state. I've tried to copy the older 5.3 driver module to work without need of additional firmware and be more stable but it's not working at all. Probably the kernel compatibility issue.
-
Hi Y'all!
Just wanted to say that I can confirm what jgrulich says about the lan network. Yesterday I was just going to check if a program I like was available for the 6.0 beta 2 cut. Apps wouldn't load and I had an error message about the network. Tried again with the same result. Then I opened a terminal and issued: $ifconfig wich confirmed that I finally had a network connection. So it seems that it can take a while before the network actually is up even with cable.
Have fun,
meo
-
Meo
which version you tried, Base, SSH or X? Where is your DHCP server in the network?
Béla
-
The LAN network need some time to start working
Please be more specific what 'some time' means and how are you measuring.
In my environment I do not see issues with networking, including wireless. Referring to wireless, there can be many issues including the wireless stick, kernel module (is it supported), firmware (is it the proper version?), power (is stick connected to RPi or a HUB), if to a HUB is it powered or, not, you can get issues with your Access Point as well as DHCP server and so on.
-
Hi bmarkus!
Sorry that I wasn't specific in my post. I'm running the X version of the second beta of piCore 6.0 and I have three Raspberry Pies connected to a switch (two are running 24/7) the third I use with various distributions available for RPi. The switch is connected to a router and normally in my experience when I start the third RPi it connects directly to the internet but that wasn't the case as I told. Starting Apps I got an error message about checking the network something. It happened a couple of times but, like I said, when I tried ifconfig I had connection to the internet and after that I checked for the program I was interested in (e.g. omxplayer) but couldn't find it in the repo. It would be a good program to add to the repository. Hope this post clarified the previous post. ;)
Keep up the good work,
meo
PS Posting this as I'm trying out the TC rc1 DS
-
Hi again!
Will try it out again tomorrow to see if it was just a glitch in my setup or it is persistant. Right now my screen (e.g. TV) occupied by my girls looking at the Nobel dinner.
Will get back tomorrow,
meo
-
Hi bmarkus,
as I've wrote, it is the same story for me. I'm using the X version. Everything is working well for the 5.x build, but not for the 6.0 beta1, or beta2. ifconfig says that everything is fine and that the IP is obtained, but when I use ping on the router, there is no response for several seconds and that is starts to work with some lost packets and long responses. The wifi is working well for the 5.x build, nothing is different with the HW setup for 6.0 testing, even the SD card is the same. There need to be some difference in the driver structure. In the 5.x build is works out-of-the-box, means only the core driver module, without any binary firmware loaded and it works. But for 6.0 there are errors during the startup which indicates that there is something wrong with the bcm2807 chipset setup and that modules for USB hub and other loading fails. Don't know how to copy the error messages from the main screen via the SSH.
-
Hi
thanks. Please post dmesg output for 5.x and 6.0. You can save it to file with
dmesg > dmesg.txt
and transfer with mc, copy with scp, etc. Another way is just pront dmesg to screen and copy it to clipbord in your terminal. There are no related change from 5.x to 6.0 in the base, but we have a different kernel which can make a difference.
Let's see dmesg files first. You can post them here or email to picoresubmit@gmail.com
-
Hi bmarkus!
The network problem I experienced doesn't seem to be related to the piCore. Started from a poweroff state three times in a row and I was connected to the internet as soon as X was up all three times. It must have been somekind of glitch with my network that caused the former problem. :)
Keep up your good work,
meo
-
The network issue is related to the 6.0 distro, at least in my case. It is related to the wifi - LAN interaction.
I've did exactly these steps:
1) downloaded the piCore-6.0beta2-X.zip file, extracted and uploaded it to SD card
2) booted the Rpi and expanded the mmcblk0p2 partition via fdisk + resize2fs
3) tested the network with the LAN connection and it works well.
4) installed wifi.tcz, mc.tcz and firmware-rtlwifi.tcz via the apps manager
5) disconnected the LAN cable and rebooted
6) After startup, inserted the wifi dongle and USB Flash to store the test results
7) connected to the AP via the wifi utility
dmesg as follows:
[ 522.186600] usb 1-1.3.1: new high-speed USB device number 7 using dwc_otg
[ 522.288289] usb 1-1.3.1: New USB device found, idVendor=0bda, idProduct=8176
[ 522.288319] usb 1-1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 522.288336] usb 1-1.3.1: Product: 802.11n WLAN Adapter
[ 522.288354] usb 1-1.3.1: Manufacturer: Realtek
[ 522.288369] usb 1-1.3.1: SerialNumber: 00e04c000001
[ 522.404370] cfg80211: Calling CRDA to update world regulatory domain
[ 522.640605] rtl8192cu: Chip version 0x10
[ 522.782527] rtl8192cu: MAC address: 00:e0:4c:0b:6f:67
[ 522.782577] rtl8192cu: Board Type 0
[ 522.782838] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 522.783012] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[ 522.791978] usbcore: registered new interface driver rtl8192cu
[ 522.811741] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 522.816587] rtlwifi: wireless switch is on
[ 531.406625] usb 1-1.3.3: new high-speed USB device number 8 using dwc_otg
[ 531.512058] usb 1-1.3.3: New USB device found, idVendor=125f, idProduct=dc1a
[ 531.512087] usb 1-1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 531.512107] usb 1-1.3.3: Product: ADATA USB Flash Drive
[ 531.512123] usb 1-1.3.3: Manufacturer: ADATA
[ 531.512137] usb 1-1.3.3: SerialNumber: 149032124213001B
[ 531.517930] usb-storage 1-1.3.3:1.0: USB Mass Storage device detected
[ 531.522418] scsi host0: usb-storage 1-1.3.3:1.0
[ 532.691300] scsi 0:0:0:0: Direct-Access ADATA USB Flash Drive 1100 PQ: 0 ANSI: 6
[ 532.695228] sd 0:0:0:0: [sda] 15155200 512-byte logical blocks: (7.75 GB/7.22 GiB)
[ 532.696163] sd 0:0:0:0: [sda] Write Protect is off
[ 532.696199] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 532.697201] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 532.705144] sda: sda1
[ 532.709683] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 652.653963] rtl8192cu: MAC auto ON okay!
[ 652.703302] rtl8192cu: Tx queue select: 0x05
[ 659.219728] wlan0: authenticate with 74:ea:3a:c3:46:a6
[ 659.256422] wlan0: send auth to 74:ea:3a:c3:46:a6 (try 1/3)
[ 659.262886] wlan0: authenticated
[ 659.266550] wlan0: associate with 74:ea:3a:c3:46:a6 (try 1/3)
[ 659.274806] wlan0: RX AssocResp from 74:ea:3a:c3:46:a6 (capab=0x431 status=0 aid=4)
[ 659.275435] wlan0: associated
Seems to be everything fine, the wifi works well:
wlan0 IEEE 802.11bgn ESSID:"DomaciLAN"
Mode:Managed Frequency:2.422 GHz Access Point: 74:EA:3A:C3:46:A6
Bit Rate=150 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr=2347 B Fragment thr:off
Power Management:off
Link Quality=36/70 Signal level=-74 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:1 Missed beacon:0
and IP is obtained:
wlan0 Link encap:Ethernet HWaddr 00:E0:4C:0B:6F:67
inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:97 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18973 (18.5 KiB) TX bytes:5845 (5.7 KiB)
But when tested the ping, it is not working well:
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: seq=7 ttl=64 time=46.916 ms
64 bytes from 192.168.1.1: seq=8 ttl=64 time=5.185 ms
--- 192.168.1.1 ping statistics ---
15 packets transmitted, 2 packets received, 86% packet loss
round-trip min/avg/max = 5.185/26.050/46.916 ms
After several minutes it starts to work better:
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: seq=0 ttl=64 time=9.228 ms
64 bytes from 192.168.1.1: seq=1 ttl=64 time=43.432 ms
64 bytes from 192.168.1.1: seq=2 ttl=64 time=2.895 ms
64 bytes from 192.168.1.1: seq=3 ttl=64 time=2.284 ms
64 bytes from 192.168.1.1: seq=4 ttl=64 time=4.195 ms
64 bytes from 192.168.1.1: seq=5 ttl=64 time=10.648 ms
64 bytes from 192.168.1.1: seq=6 ttl=64 time=4.711 ms
64 bytes from 192.168.1.1: seq=7 ttl=64 time=10.544 ms
64 bytes from 192.168.1.1: seq=8 ttl=64 time=6.388 ms
64 bytes from 192.168.1.1: seq=9 ttl=64 time=4.570 ms
64 bytes from 192.168.1.1: seq=10 ttl=64 time=4.977 ms
64 bytes from 192.168.1.1: seq=11 ttl=64 time=3.464 ms
64 bytes from 192.168.1.1: seq=12 ttl=64 time=2.253 ms
64 bytes from 192.168.1.1: seq=13 ttl=64 time=2.150 ms
64 bytes from 192.168.1.1: seq=14 ttl=64 time=2.216 ms
64 bytes from 192.168.1.1: seq=15 ttl=64 time=2.146 ms
64 bytes from 192.168.1.1: seq=16 ttl=64 time=3.216 ms
64 bytes from 192.168.1.1: seq=17 ttl=64 time=1.811 ms
64 bytes from 192.168.1.1: seq=18 ttl=64 time=7.035 ms
64 bytes from 192.168.1.1: seq=19 ttl=64 time=1.304 ms
64 bytes from 192.168.1.1: seq=20 ttl=64 time=1.324 ms
64 bytes from 192.168.1.1: seq=21 ttl=64 time=2.657 ms
64 bytes from 192.168.1.1: seq=22 ttl=64 time=4.982 ms
64 bytes from 192.168.1.1: seq=23 ttl=64 time=1.638 ms
64 bytes from 192.168.1.1: seq=24 ttl=64 time=1.259 ms
64 bytes from 192.168.1.1: seq=25 ttl=64 time=3.403 ms
64 bytes from 192.168.1.1: seq=26 ttl=64 time=1.330 ms
64 bytes from 192.168.1.1: seq=27 ttl=64 time=1.261 ms
64 bytes from 192.168.1.1: seq=28 ttl=64 time=1.286 ms
64 bytes from 192.168.1.1: seq=29 ttl=64 time=2.818 ms
64 bytes from 192.168.1.1: seq=30 ttl=64 time=1.350 ms
64 bytes from 192.168.1.1: seq=31 ttl=64 time=2.155 ms
64 bytes from 192.168.1.1: seq=32 ttl=64 time=1.692 ms
64 bytes from 192.168.1.1: seq=33 ttl=64 time=7.612 ms
64 bytes from 192.168.1.1: seq=34 ttl=64 time=3.419 ms
64 bytes from 192.168.1.1: seq=35 ttl=64 time=1.603 ms
64 bytes from 192.168.1.1: seq=36 ttl=64 time=2.825 ms
64 bytes from 192.168.1.1: seq=37 ttl=64 time=1.279 ms
64 bytes from 192.168.1.1: seq=38 ttl=64 time=5.130 ms
64 bytes from 192.168.1.1: seq=39 ttl=64 time=1.451 ms
64 bytes from 192.168.1.1: seq=40 ttl=64 time=2.396 ms
64 bytes from 192.168.1.1: seq=41 ttl=64 time=2.086 ms
64 bytes from 192.168.1.1: seq=42 ttl=64 time=1.705 ms
64 bytes from 192.168.1.1: seq=43 ttl=64 time=6.720 ms
64 bytes from 192.168.1.1: seq=44 ttl=64 time=1.840 ms
64 bytes from 192.168.1.1: seq=45 ttl=64 time=3.819 ms
64 bytes from 192.168.1.1: seq=46 ttl=64 time=11.977 ms
64 bytes from 192.168.1.1: seq=47 ttl=64 time=1.874 ms
64 bytes from 192.168.1.1: seq=48 ttl=64 time=5.273 ms
64 bytes from 192.168.1.1: seq=49 ttl=64 time=3.110 ms
64 bytes from 192.168.1.1: seq=50 ttl=64 time=3.833 ms
64 bytes from 192.168.1.1: seq=51 ttl=64 time=2.351 ms
64 bytes from 192.168.1.1: seq=52 ttl=64 time=1.772 ms
--- 192.168.1.1 ping statistics ---
53 packets transmitted, 53 packets received, 0% packet loss
round-trip min/avg/max = 1.259/4.315/43.432 ms
As you may see, there are great differences in the time, means that the connection is not stable and therefor it is slow when transferring some larger files.
-
Post lsmod output and above files with 5.3
-
jgrulich@
Please try Beta100 which comes with the latest 3.18.0 kernel.
-
The same test results from the 5.3 distro:
dmesg:
[ 34.812632] bcm2708-i2s bcm2708-i2s.0: Failed to create debugfs directory
[ 34.850776] pcm512x 1-004c: Failed to reset device: -5
[ 34.850931] pcm512x: probe of 1-004c failed with error -5
[ 35.342850] usbcore: registered new interface driver snd-usb-audio
[ 36.739457] usbcore: registered new interface driver rtl8192cu
[ 37.805915] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 42.908098] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 98.026913] usb 1-1.3.3: new high-speed USB device number 8 using dwc_otg
[ 98.132362] usb 1-1.3.3: New USB device found, idVendor=125f, idProduct=dc1a
[ 98.132388] usb 1-1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 98.132401] usb 1-1.3.3: Product: ADATA USB Flash Drive
[ 98.132411] usb 1-1.3.3: Manufacturer: ADATA
[ 98.132422] usb 1-1.3.3: SerialNumber: 149032124213001B
[ 98.138071] usb-storage 1-1.3.3:1.0: USB Mass Storage device detected
[ 98.141111] scsi0 : usb-storage 1-1.3.3:1.0
[ 99.325237] scsi 0:0:0:0: Direct-Access ADATA USB Flash Drive 1100 PQ: 0 ANSI: 6
[ 99.329660] sd 0:0:0:0: [sda] 15155200 512-byte logical blocks: (7.75 GB/7.22 GiB)
[ 99.330553] sd 0:0:0:0: [sda] Write Protect is off
[ 99.330583] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 99.331458] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 99.339827] sda: sda1
[ 99.343759] sd 0:0:0:0: [sda] Attached SCSI removable disk
ifconfig:
wlan0 Link encap:Ethernet HWaddr 00:E0:4C:0B:6F:67
inet addr:192.168.1.108 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:75 errors:0 dropped:1 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20720 (20.2 KiB) TX bytes:1406 (1.3 KiB)
iwconfig:
wlan0 IEEE 802.11bgn ESSID:"DomaciLAN" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency:2.422 GHz Access Point: 74:EA:3A:C3:46:A6
Bit Rate:150 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=100/100 Signal level=49/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
ping 56 data:
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: seq=0 ttl=64 time=11.155 ms
64 bytes from 192.168.1.1: seq=1 ttl=64 time=14.959 ms
64 bytes from 192.168.1.1: seq=2 ttl=64 time=16.438 ms
64 bytes from 192.168.1.1: seq=3 ttl=64 time=13.518 ms
64 bytes from 192.168.1.1: seq=4 ttl=64 time=5.551 ms
64 bytes from 192.168.1.1: seq=5 ttl=64 time=6.986 ms
64 bytes from 192.168.1.1: seq=6 ttl=64 time=6.301 ms
64 bytes from 192.168.1.1: seq=7 ttl=64 time=5.617 ms
64 bytes from 192.168.1.1: seq=8 ttl=64 time=6.165 ms
64 bytes from 192.168.1.1: seq=9 ttl=64 time=5.578 ms
64 bytes from 192.168.1.1: seq=10 ttl=64 time=9.747 ms
64 bytes from 192.168.1.1: seq=11 ttl=64 time=14.154 ms
64 bytes from 192.168.1.1: seq=12 ttl=64 time=6.602 ms
64 bytes from 192.168.1.1: seq=13 ttl=64 time=8.820 ms
64 bytes from 192.168.1.1: seq=14 ttl=64 time=18.360 ms
64 bytes from 192.168.1.1: seq=15 ttl=64 time=11.387 ms
64 bytes from 192.168.1.1: seq=16 ttl=64 time=6.282 ms
64 bytes from 192.168.1.1: seq=17 ttl=64 time=8.355 ms
--- 192.168.1.1 ping statistics ---
18 packets transmitted, 18 packets received, 0% packet loss
round-trip min/avg/max = 5.551/9.776/18.360 ms
ping 1024 data:
PING 192.168.1.1 (192.168.1.1): 1024 data bytes
1032 bytes from 192.168.1.1: seq=0 ttl=64 time=16.306 ms
1032 bytes from 192.168.1.1: seq=1 ttl=64 time=6.752 ms
1032 bytes from 192.168.1.1: seq=2 ttl=64 time=6.592 ms
1032 bytes from 192.168.1.1: seq=3 ttl=64 time=7.132 ms
1032 bytes from 192.168.1.1: seq=4 ttl=64 time=5.928 ms
1032 bytes from 192.168.1.1: seq=5 ttl=64 time=7.946 ms
1032 bytes from 192.168.1.1: seq=6 ttl=64 time=6.384 ms
1032 bytes from 192.168.1.1: seq=7 ttl=64 time=6.822 ms
1032 bytes from 192.168.1.1: seq=8 ttl=64 time=5.870 ms
1032 bytes from 192.168.1.1: seq=9 ttl=64 time=5.877 ms
1032 bytes from 192.168.1.1: seq=10 ttl=64 time=10.373 ms
1032 bytes from 192.168.1.1: seq=11 ttl=64 time=10.252 ms
1032 bytes from 192.168.1.1: seq=12 ttl=64 time=6.096 ms
1032 bytes from 192.168.1.1: seq=13 ttl=64 time=6.702 ms
1032 bytes from 192.168.1.1: seq=14 ttl=64 time=2.255 ms
1032 bytes from 192.168.1.1: seq=15 ttl=64 time=7.142 ms
1032 bytes from 192.168.1.1: seq=16 ttl=64 time=5.918 ms
1032 bytes from 192.168.1.1: seq=17 ttl=64 time=6.641 ms
--- 192.168.1.1 ping statistics ---
18 packets transmitted, 18 packets received, 0% packet loss
round-trip min/avg/max = 2.255/7.277/16.306 ms
ping 10240 data:
PING 192.168.1.1 (192.168.1.1): 10240 data bytes
10248 bytes from 192.168.1.1: seq=0 ttl=64 time=13.773 ms
10248 bytes from 192.168.1.1: seq=1 ttl=64 time=9.004 ms
10248 bytes from 192.168.1.1: seq=2 ttl=64 time=7.563 ms
10248 bytes from 192.168.1.1: seq=3 ttl=64 time=5.909 ms
10248 bytes from 192.168.1.1: seq=4 ttl=64 time=5.923 ms
10248 bytes from 192.168.1.1: seq=5 ttl=64 time=7.640 ms
10248 bytes from 192.168.1.1: seq=6 ttl=64 time=8.846 ms
10248 bytes from 192.168.1.1: seq=7 ttl=64 time=8.018 ms
10248 bytes from 192.168.1.1: seq=8 ttl=64 time=5.877 ms
10248 bytes from 192.168.1.1: seq=9 ttl=64 time=8.249 ms
10248 bytes from 192.168.1.1: seq=10 ttl=64 time=5.897 ms
10248 bytes from 192.168.1.1: seq=11 ttl=64 time=10.433 ms
10248 bytes from 192.168.1.1: seq=12 ttl=64 time=5.973 ms
10248 bytes from 192.168.1.1: seq=13 ttl=64 time=13.109 ms
10248 bytes from 192.168.1.1: seq=14 ttl=64 time=11.885 ms
10248 bytes from 192.168.1.1: seq=15 ttl=64 time=5.927 ms
10248 bytes from 192.168.1.1: seq=16 ttl=64 time=8.904 ms
10248 bytes from 192.168.1.1: seq=17 ttl=64 time=7.966 ms
10248 bytes from 192.168.1.1: seq=18 ttl=64 time=5.969 ms
10248 bytes from 192.168.1.1: seq=19 ttl=64 time=7.519 ms
10248 bytes from 192.168.1.1: seq=20 ttl=64 time=6.818 ms
--- 192.168.1.1 ping statistics ---
21 packets transmitted, 21 packets received, 0% packet loss
round-trip min/avg/max = 5.877/8.152/13.773 ms
Everything is working well, eve with the large packets.
-
Do not see wireless related messages in dmesg
-
There is only one line in the 5.3 distro:
[ 36.739457] usbcore: registered new interface driver rtl8192cu