t-bob
-
Posts
45 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by t-bob
-
-
Best of luck with this one as I've never had any success with a 5.x dev image.
If you install a 4.x image then use armbian-config to switch to the nightly stream you can get a 5.x kernel booting.
-
those details were just things i've read about on this and other forums.
some people had luck with using devmem2 and doing echo's to the gpio device.
that module doesnt exist for me.
hciattach seems to load everything but i'm unable to bring the network up
[ 63.874269] Bluetooth: hci0: command 0x1003 tx timeout
[ 65.890379] Bluetooth: hci0: command 0x1001 tx timeout
[ 67.906448] Bluetooth: hci0: command 0x1009 tx timeout -
in /boot/armbianEnv.txt add these lines.
overlays=uart1
param_uart1_rtscts=1 -
did you 'decompile' the dts using dtc and then compile it again ?
-
[ 231.171784] r8723bs: module is from the staging directory, the quality is unknown, you have been warned.
[ 231.226752] RTL8723BS: module init start
[ 231.226761] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
[ 231.226766] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40
[ 231.226840] RTL8723BS: module init ret =0
[ 231.308168] Bluetooth: Core ver 2.22
[ 231.308277] NET: Registered protocol family 31
[ 231.308281] Bluetooth: HCI device and connection manager initialized
[ 231.308300] Bluetooth: HCI socket layer initialized
[ 231.308309] Bluetooth: L2CAP socket layer initialized
[ 231.308339] Bluetooth: SCO socket layer initialized
[ 231.342572] Bluetooth: HCI UART driver ver 2.3
[ 231.342584] Bluetooth: HCI UART protocol H4 registered
[ 231.342588] Bluetooth: HCI UART protocol BCSP registered
[ 231.342675] Bluetooth: HCI UART protocol LL registered
[ 231.342680] Bluetooth: HCI UART protocol ATH3K registered
[ 231.342739] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 231.342989] Bluetooth: HCI UART protocol Intel registered
[ 231.343157] Bluetooth: HCI UART protocol Broadcom registered
[ 231.343207] Bluetooth: HCI UART protocol QCA registered
[ 231.343212] Bluetooth: HCI UART protocol AG6XX registered
[ 231.343216] Bluetooth: HCI UART protocol Marvell registered
[ 231.371480] Bluetooth: RFCOMM TTY layer initialized
[ 231.371501] Bluetooth: RFCOMM socket layer initialized
[ 231.371527] Bluetooth: RFCOMM ver 1.11
[ 231.530453] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 231.530461] Bluetooth: BNEP filters: protocol multicast
[ 231.530476] Bluetooth: BNEP socket layer initialized
[ 233.543018] Bluetooth: hci0: command 0x1003 tx timeout
[ 235.559107] Bluetooth: hci0: command 0x1001 tx timeout
[ 237.575212] Bluetooth: hci0: command 0x1009 tx timeout -
looks like it almost wants to work with 4.x and that firmware.
modprobe r8723bs; modprobe hci_uart; modprobe bluetooth; modprobe rfcomm
systemctl restart bluetooth
hciattach -s 1500000 /dev/ttyS1 any bdaddr 43:29:B1:55:01:01hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN INIT RUNNING
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:12 acl:0 sco:0 commands:3 errors:0
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DH1 HV1
Link policy:
Link mode: SLAVE ACCEPThciconfig hci0 up
Can't init device hci0: Connection timed out (110) -
check some of the other questions raised further down the list.
it's coming in kernel 5.4 but does work using a legacy kernel
-
Yes, I've had a play with this too but without any luck.
I built a dev image but that kernel panics as it boots up.
If you want BT you'll need to use the legacy kernel (3.x) otherwise you can't see the hci device
-
here's the patched devmem2 if anyone needs it
-
excellent. many thanks for that. now i get this which seems like an impressive SID
6400462092C000BA:541500CE50368518
-
i get bus errors on memory access for 0x01c14204 & 0x01c1420c.
is this expected ?
92C000BA 50368518
-
easy ... just use the armbian build process to generate a new image and select "stable"
but i did find that in 5.5x that the wifi wouldn't automatically connect and doing an ifdown/ifup would work 50% of the time.
-
I've built the latest armbian (5.48 & 5.46) for all the different versions (default, next & dev) and they all have issues starting the wifi !
If i manually do an ifdown/ifup it usually comes up (say 80% of the time)
I was just wondering if anyone else had seen this issue or is it just me .....
Thanks, TB
-
I built a 18.04 for opiwin+ ... mostly works but for some reason wifi needs to be manually started
-
you'll need to stick with 3.10 for the moment. 4.xx has several issues which will be fixed but not yet.
not much you can do
-
Hi,
I was wondering if anyone was having issues with the ethernet port using the legacy kernel ?
It does seem to kind of work ... it will get DHCP from the router and configure the routing tables etc but after that it goes wonky.
When I do a ping test from the router I get "50/50 transmitted, 15/50 received, 70% loss". A ping test from the opi-win to the router gets a similar result.
If I try a ping/ssh from a PC connected to the router I get a 95% packet loss
Everything else seems to work fine ... HDMI, USB, WiFi (AP/STA modes) which is really, really nice.
Thanks
TB
-
Can you tell me how you go with network speeds. I tried it yesterday and ethernet/wifi worked but was really, really slow. Just not sure if it was me or the O/S ....
-
The only odd thing so far is the that USB ports dont seem to work
The hubs appear but when you insert a usb key nothing appears in /dev or the syslog/kernel log etc etc. Will keep looking.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -
I just built the latest OPi Win image and WOW ... just about everything seems to be working. I'll test it over the coming days but AWESOME work guys.
Wifi is back, eth0 is back and HDMI works !!!!!
I've not tried any kind of GUI yet but I can get a console prompt on the TV & see the kernel boot messages
Now for more testing, testing & testing ....
TB
-
You have to build it using the various toolsets to do that. Quite easy. Their system is well put together
-
And I also found that it was missing from /boot/armbianEnv.txt as it wasnt loading the fixup scripts
overlay_prefix=sun50i-a64
-
Hi,
I've been playing around with the latest build (Armbian_5.37_Orangepiwin_Debian_stretch_next_4.14.5.img.gz) just to see how things are going and I've noticed that the wifi has gone ?
I saw that it doesnt talk about patching the ap6212 firmware anymore. Had a look around but couldnt see anything.
I know it's a dev build but I hope that it's just a missing config file from that build branch or something.
Thanks
TB
-
Yes, we'd never get complete agreement on a config ... but even if we could get an agreement on say the wifi chipset(s) and always include usb3 on anything that's not a 'zero' clone. Stuff like that would be good.
The Wemos stuff looks interesting and not too pricey like some other ones.
Well, the whole trickle down economy thing worked so well for everyone didnt it
The master mode would only need OK performance and not excellent ... just web traffic (5+ users)
-
Many thanks for the comments & info.
Yes, the only guarantee in life is death & taxes
All these SBC's have compromises that have to be made. Even the RPi which has awesome s/w support but no external wifi antenna, bad microSD slot (why didnt they pay an extra 5 cents and get the one that clicks in) & only 1G of ram.
It's a pity we couldnt get someone to make a SBC with all the stuff that we want but I doubt that would ever happen
rtl88xx wifi driver - current repo deprecated
in Beginners
Posted
Hi,
I was building a new image for my win and noticed this:
https://github.com/cilynx/rtl88x2BU_WiFi_linux_v5.3.1_27678.20180430_COEX20180427-5959
Deprecation notice. This repo is deprecated and a newer version of the driver is available at https://github.com/cilynx/rtl88x2bu
Not sure if it's worth switching over.
Thanks
TB