PiotrO
-
Posts
46 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by PiotrO
-
-
1 hour ago, Pic55 said:
@PiotrOI tried on my TX6-A (4G / 32G). The lcd doesn't work. Attanched the output of dmesg. I also tried on a TX6-P but the booting process not even finish (so I can not connect with Telnet).
Pic55: many many thx!
May you spent more 2..3 minutes on this?
If yes - pls make sure that file minimyth.conf on partition BOOT has uncommented entry MM_LCDPROC_ENABLED='openvfd'
(probably you download SD card image variant in which this var is not set by default. i corrected this approx 12:45 CET)
Re: TX6-P: did box get IP addr at all or rather i.e. hang on DHCP stage?
If it is failing on Eth - you can try with WiFi.
1. leave Eth unconnected
2. set in minimyth.conf MM_WLAN_SSID='your net' and MM_WLAN_PASS='your pass'
sorry dragging you with all this!
-
12 hours ago, awawa said:
@awawa
thx for keeping eye on this!
i opened my box and look with oscilloscope on sda/scl pins on fd650.
-with factory android: led display works; 3.3v + every 0.5sec series of to low polarity pulses
-with yours armbian: led display black; constant 3.3v without any pulses
-with mine distro: led display black; constant 3.3v without any pulses
So for me it looks like:
-issue is not due missed pull-ups
-issue is because my board uses different gpio
i don't believe issue is i.e.due miss-working gpio controller as i have working i.e. wifi which uses near gpio pin228.
Now i see: you have tanix-tx6-p while i have tanix-tx6. This may explain: in fact we have different devices.
I dumped boot/system/vendor/dtbo partitions from factory Android - and i want to extract android dtb to see what gpio are used to drive fd650 on my box.
Has anybody any hint what is easiest way to do this? (playing mkdtboimg.py or...?)
In the meantime i want to see how population of various tanix-tx6 variants looks like.
Are users of tanix-tx6 may give me favour please and:
-download my distro (https://github.com/warpme/minimyth2/releases/download/v11.28.3-master-Pre-122-g6a79086179/MiniMyth2-armv8-master-11.28.3.r122-board-h6.tanix_tx6-board-s912-SD-Image.img.xz)
-burn to SD card
-if lcd display not works: telnet to box (user is root; no password) and provide me pls dmesg + possible box details
thx in advance!
-
1 hour ago, awawa said:
What's in the dmesg when you activate openvfd in my fork? The dmesg output is different than on 5.17? Just to be sure: did you enabled that service before running it? 5.17 introduces some breaking changes in DT for our board and as jernej noted still could have some bugs.
Settings for Tanix TX6 are generic and taken from vfd homepage https://github.com/arthur-liberman/vfd-configurations/blob/master/tanix-tx6-allwinner-h6-vfd.conf
I didn't open my box so don't know its board revision.
Pls find dmesg from armbian running on my tanix-tx6:
[ 3723.481800] OpenVFD: Version: V1.4.1 [ 3723.481839] OpenVFD: vfd_gpio_clk: #0 = 0x01; #1 = 0xE5; #2 = 0x00; [ 3723.481857] OpenVFD: vfd_gpio_dat: #0 = 0x01; #1 = 0xE6; #2 = 0x00; [ 3723.481873] OpenVFD: vfd_gpio_stb: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 3723.481889] OpenVFD: vfd_gpio0: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 3723.481905] OpenVFD: vfd_gpio1: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 3723.481921] OpenVFD: vfd_gpio2: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 3723.481936] OpenVFD: vfd_gpio3: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 3723.481950] OpenVFD: vfd_gpio_protocol: #0 = 0x00; #1 = 0x00; [ 3723.481969] OpenVFD: vfd_chars: #0 = 0x02; #1 = 0x04; #2 = 0x03; #3 = 0x02; #4 = 0x01; [ 3723.481992] OpenVFD: vfd_dot_bits: #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x05; #6 = 0x06; [ 3723.482011] OpenVFD: vfd_display_type: #0 = 0x01; #1 = 0x00; #2 = 0x00; #3 = 0x03; [ 3723.482026] OpenVFD: Detected gpio chips: 300b000.pinctrl, 7022000.pinctrl. [ 3723.482037] OpenVFD: "300b000.pinctrl" chip found. base = 0, pin count = 256, pin = 229, offset = 229 [ 3723.482055] OpenVFD: "300b000.pinctrl" chip found. base = 0, pin count = 256, pin = 230, offset = 230 [ 3723.482071] OpenVFD: Skipping vfd_gpio_stb evaluation (0xFF) [ 3723.482080] OpenVFD: Skipping vfd_gpio0 evaluation (0xFF) [ 3723.482088] OpenVFD: Skipping vfd_gpio1 evaluation (0xFF) [ 3723.482096] OpenVFD: Skipping vfd_gpio2 evaluation (0xFF) [ 3723.482104] OpenVFD: Skipping vfd_gpio3 evaluation (0xFF) [ 3723.482662] OpenVFD: Select FD650 controller [ 3723.482777] OpenVFD: SW I2C interface intialized (address = 0x0000 (N/A), MSB mode, pull-ups off)On my box with my distro i tried multiple ways:
1. by providing all data in DT
2. by inserting openvfd.ko with params taken from https://github.com/arthur-liberman/vfd-configurations/blob/master/tanix-tx6-allwinner-h6-vfd.conf
3. by adding in /etc/modprobe.d file openvfd.conf with content like this:
# This file must be renamed to vfd.conf and placed in the /storage/.config/ folder. # # Tanix TX6 - Allwinner H6 configuration #-------------------- #gpio_xxx: # [0] 0 = &gpiochip0, 1 = &gpiochip1. # [1] pin number # [0] Reserved - must be 0. options openvfd vfd_gpio_clk=1,229,0 options openvfd vfd_gpio_dat=1,230,0 options openvfd vfd_gpio_stb=0,0,0xFF options openvfd vfd_gpio_chip_name="300b000.pinctrl" #chars: # < DHHMM > Order of display chars (D=dots, represented by a single char) options openvfd vfd_chars=2,4,3,2,1 #dot_bits: # Order of dot bits. Typical configurations: # Display Type 0, 1 usually has Alarm, USB, Play, Pause, Col, Ethernet, Wifi dots # Alarm = 0, USB = 1, Play = 2, Pause = 3, Col = 4, Eth = 5, Wifi = 6 # Display Type 2 usually has APPS, USB, SETUP, CARD, Col, HDMI, CVBS dots # APPS = 0, USB = 1, SETUP = 2, CARD = 3, Col = 4, HDMI = 5, CVBS = 6 # Display Type 3 Power, LAN, Col, Low Wifi, High Wifi # N/A = 0, N/A = 1, Power = 2, LAN = 3, Col = 4, Low Wifi = 5, High Wifi = 6 options openvfd vfd_dot_bits=0,1,2,3,4,5,6 #display_type: # [0] - Display type. # [1] - Reserved - must be 0.. # [2] - Flags. (bit 0 = '1' - Common Anode display) # [3] - Controller. options openvfd vfd_display_type=0x01,0x00,0x00,0x03on every case i examined dmesg to make sure module loads ok.
no matter what - display is black
for me most probable issue is in bus from SOC to fd650: gpio wrong lines or logic state voltages are out of working levels.
i don't believe tanix changed gpio between board versions....
but it is highly probable i.e. some Chinese manager decided to save 0.01$ by not soldering 2 pull-up resistors. or soldered resistors with way too high resistance...
thats why i'm curious what board you have?
(mine is H6-06_V1.0 2019-07-10)
-
On 2/16/2022 at 11:29 PM, awawa said:
Had better luck using OpenVfd. The watch is working. But currently really have no idea how to include it in the build scripts.
@awawa
Since few days i'm trying to get openvfd working on tanix-tx6 in my project.
i'm on 5.17 kernel and dmesg's openvfd entires are looking like expected - but display is black.
Hw is ok as under factory android led disp. works ok.
I installed latest armbian from your git, kick systemctl start openvfd and...display is also black.
I verified LED IC on my tanix-tx6: it is fd650.
As you have it working + my box failing on sources build 5.17+openvfd1.4.1 nor on your armbian not with jernej's i2c with py code - i see 2 possible reasons:
-my box is using different gpio's
-my box has missing pull-ups on SDA/SCL (so wire OR not works)
What board version you have in your box?
-
2 hours ago, balbes150 said:
I checked these options, they correspond to the specified values. Means the reason in availability of options from other platforms (RK and AML), which can hinder work AW.
@balbes150: fyi: I take special care with these options to have single kernel config working for AML/RK/ALW/BCM.
Tested on 7 hw platforms I have and those seems to work ok...
-
1 hour ago, balbes150 said:
Added these settings and got the message from the TV about an unsupported mode. Pulled out HDMI and plugged again and the image appeared. Means u-boot, kernel and DTB working. But there is no wired network yet. But this is already a big progress, there is something to work on that would make this TV box work, and not fall on the shelf. By the way, the sound and USB WiFi\LAN and stuff works.
Added these parameters to (extlinux.conf) for the Le image and everything automatically started with default u-boot and dtb for TX6. There is a network, a sound and other on Eachlink H6.
@balbes150
Regarding Eth: for sure You have AC200 2& H6 and PWM patches + proper kernel config?
IIRC kernel config should have:
CONFIG_COMMON_CLK_PWM=y
CONFIG_PWM_SUN4I=y
CONFIG_DWMAC_SUN8I=m
CONFIG_AC200_PHY=y
CONFIG_MFD_AC200=y
CONFIG_I2C_MV64XXX=y
note that all mentioned drivers have to be =y and only DWMAC_SUN8I=m
-
53 minutes ago, balbes150 said:
Took "clean" config from LE and built Armbian with It (version 20191222). Now the wired network works. Perhaps when using the universal kernel config, some options are not in the state that would ensure the operation of a wired network.
@hexdump @PiotrO Can you drop me a copy of the u-boot and dtb you use for Eachlink H6 ? For u-boot, you can simply make a copy of the DD - 4M from your working SD card.
@balbes150
pls find below:
On 5.5 kernel - for eachlink H6 i'm using this patch to get dtb:
For u-boot I'm using custodian repo:
https://gitlab.denx.de/u-boot/custodians/u-boot-sunxi
with patch adding H6 support:
Pls let me know do You still need 4M from SD card.
(of corse I'm sure You remember to add PWM & AC200 support in kernel)
br
-
5 hours ago, hexdump said:
@PiotrO - btw. has the hdmi problem been fixed meanwhile or is there still the video=HDMI-A-1:e kernel cmdline option required on the eachlink h6 mini? if it is fixed, which patch or commit fixed it in case you know it?
a lot of thanks in advance and best wishes - hexdump
Just done test on mainline 5.4.1 with removed video=HDMI-A-1:e and it looks like without it hdmi display is not detected :-(
-
10 hours ago, hexdump said:
attached is my eachlink dtb,
Thx. t720 works perfectly now!
Still shame because overlooking all this :-p
-
17 hours ago, Redferne said:
Huge thanks for this! I have one of these boxes just collecting dust. Will it boot an Armbian minted SD or do you need Pheonixcard tricks?
You need to apply list of patches I mentioned in my original post atop of mainline 5.4 kernel and compile. Patches in my Makefile are grouped per functionality so it should be easy to pick those interested for you I think.
PS: I'm not using armbian. I'm doing my own distro.
I put this H6 eachlink related post because armbian community seems to be most resonating & willing to discuss about various ARM SoC aspects :-)
-
4 hours ago, hexdump said:
i doubt that there is really a power problem with the t720 gpu, as i am able to use it with the mali fbdev blob successfully on an eachlink h6 - using gl4es and LIBGL_FB=3 mode as described here: https://github.com/ptitSeb/gl4es/issues/119
best wishes - hexdump
aha!
This is important!
My approach for H6 t720 enablement is following:
in sun50i-h6.dtsi I'm adding gpu node:
<------><------>gpu: gpu@1800000 { <------><------><------>compatible = "allwinner,sun50i-h6-mali", <------><------><------><------> "arm,mali-t720"; <------><------><------>reg = <0x01800000 0x4000>; <------><------><------>interrupts = <GIC_SPI 84 IRQ_TYPE_LEVEL_HIGH>, <------><------><------><------> <GIC_SPI 85 IRQ_TYPE_LEVEL_HIGH>, <------><------><------><------> <GIC_SPI 83 IRQ_TYPE_LEVEL_HIGH>; <------><------><------>interrupt-names = "job", "mmu", "gpu"; <------><------><------>clocks = <&ccu CLK_GPU>, <&ccu CLK_BUS_GPU>; <------><------><------>clock-names = "core", "bus"; <------><------><------>resets = <&ccu RST_BUS_GPU>; <------><------><------>status = "disabled"; <------><------>};
and in i.e working ok beelink gs1 tvbox dts - I'm enabling gpu in board dtb:
&gpu { mali-supply = <®_dcdcc>; status = "okay"; };So far I don't have enabling gpu dtb fragments for eachlink tvbox - because all the time I was thinking PMIC needs to be touched!
What You enlighten me that thing is closer to get than I think :-)
May You pls hint me about Yous DTS entries related to gpu?
I mean:
gpu node entries in sun50i-h6.dtsi
gpu enabling fragment in eachlink H6 dts file (including power regulator entries it uses)
thx in advance!
-
9 hours ago, Belgrado said:
Hi @PiotrO,
I am very happy and enthusiasmatic with your post. I was so sad and disappointed to have Orange Pi 3 but can't use as a hand computer. So, I already have a doubt about the hdmi sound (in my case doesn't work): How could I use your patches or when is it available for all users in Armbian versions?
Best regards.
Belgrado.Well - this is relatively simple: You need to apply list of patches I mentioned in my original post atop of mainline 5.4 kernel and compile. I'm not sure about Orange Pi3 dts - but HDMI sound related device tree fragments are in all H6 platforms include (sun50i-h6.dtsi) so it should work for You I think...
Good luck!
BTW: all kudos for H6 sound should go to codekipper!
He done fantastic work on allwinner ASoC!
-
I'm creating this topic to track progress with support for EachLink H6 support.
So far with patches in lines 127..202 in List of patches with patch files I was able to get:
working:
-boot with mainline 5.4 kernel
-HDMI video (with correct DDC)
-HDMI audio
-Ethernet
-GPU mali t720
-USB2/USB3 ports
-CPU temp reading
-DVFS (CPU freq scalling)
-internal IR sensor (MCE remote works nicely)
not tested:
WiFi
Blutooth
This box might be cheap H6 box to become nice mediaplayer as current panfrost started to support really well t720 (I've got fully working GLES UI, playback with OpenG & yv12 renderers + GLSL based shader deinterlacers: OneFileld. LinearBlend & Kernel on mythtv).
Only issue I had at this moment is insufficient cooling with stock cooler - so if You launch compute intensive tasks and Yours OPP has 1.8GHz cpu clock entries - after some time bow is self-reseting due overheated CPU.
Solution seems to be:
-lower max CPU clock in OPP tables to 1.4GHz or
-add better cooler...
-
3 hours ago, jcaron said:
I'm using it since the 19/10/08 kernel release, no problem with glxgear nor compositing, glxinfo tell me direct rendering is enable, the driver support
@jcaron
Are You using mesa on t720 or mali blob?
-
10 hours ago, hexdump said:
@PiotrO - with megous 5.2 tree i have a normal /sys/devices/cpu/cpu0/cpufreq and i can see all the frequencies (up to 1.8ghz is possible) i have hacked the voltage for into the h6 dtsi and thermal throttling is working perfectly well too as long as there is enough airflow so that just reducing the frequency can cool the cpu enough down (as there is no voltage scaling, which usually reduces heat the most)
Hmm - interesting: in my case on 5.3-rc8 it looks I need to look in: /sys/devices/system/cpu/cpufreq/policy0
And indeed i.e.:
cat /sys/devices/system/cpu/cpufreq/policy0/stats/trans_table From : To : 480000 720000 816000 888000 1080000 1320000 1488000 1800000 480000: 0 0 0 0 0 0 0 0 720000: 0 0 0 0 0 0 0 0 816000: 0 0 0 0 0 0 0 0 888000: 0 0 0 0 0 0 0 0 1080000: 0 0 0 0 0 0 0 1 1320000: 0 0 0 0 0 0 0 0 1488000: 0 0 0 0 0 0 0 0 1800000: 0 0 0 0 0 0 0 0but
cat /sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed <unsupported> echo 1080000 > /sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed ash: write error: Invalid argument
is it setspeed working for You on 5.2?
-
1 hour ago, hexdump said:
@PiotrO - did you add a supply to your cpu too? - like https://github.com/megous/linux/blob/orange-pi-5.1/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi-3.dts#L122
on the h6 tv boxes this is getting a bit tricky as they do not have a real regulator for the cpu voltage - you might have a look at my hack in the patch in the link below: see vcccpu (as some kind of dummy regulator) in the dts and the hacked opp tables in the h6 dtsi to allow this single voltage for all frequencies - but this is just a hack for now ... on the megous 5.2 kernel both the temp sensor and cpufreq are working well this way.
@hexdump,
Yes. I added these entries as indeed adding cpu supply is a must to get my GS1 and eachlink working. I understand You have working DVFS on Yours H6 hw.
Do You have any entries in /sys/class/cpufreq ?
Also - what is best way to see what is current cpu freq/voltage & also to see how system walks on dvfs trips?
-
12 hours ago, jernej said:
@PiotrO 5.3-rc8 contains fixes needed for this workaround to work. Can you try again?
@jernej,
thx for hint!
for sure i'll test it.
rc7+patches You mention gives me working screen on eachlink h6 mini.
Last days I'm playing a bit with DVFS on h6 (beelink gs1).
I'm using 5.3-rc7 mainline + and megous patches (also verified with Yours libreelec patches for h6).
I got ths working (as I see entries in /sys/class/thermal)
So next I tried to play with cpufreq.
I added clk to cpu cores (like in https://github.com/megous/linux/commit/19a1b4942b8f040f2b8f2d322368518c5776025b), OPP tables (like in https://github.com/megous/linux/commit/b4aca20e5ce774f6f91bc79317d232ead36e8ede) and trip points/cooling maps (like in https://github.com/megous/linux/commit/b1a1c764c50b6d2d86d1c9124d01ca1726836e9b ). Next I enabled cpu0 power from dcdca reg and my gs1 boots.
but here is no any entries in /sys/class/cpufreq
What intriguing me: in megous & Yours patches there is no any touch in cpufreq-dt-platdev for H6 ( https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/cpufreq/cpufreq-dt-platdev.c?id=089cf7f6ecb266b6a4164919a2e69bd2f938374a#n28
so cpufreq-dt will not load for h6.
By curiosity I added 'sun50i-h6' entry in cpufreq-dt-platdev.c and now kernel tries to load cpufreq-dt module but fails with error -2 (cant get cpu0 clock).
interesting.
maybe clock framework not provides required method clock_get to cpufreq?
-
Guys,
Just quick Q: on 5.3-rc7 I still have blackscreen on Eachlink H6 (even with video=HDMI-A-1:e).
Is this 5.3 kernel issue or rather something else?
btw: I switch to beelink Gs1 and got almost fully working with mainline 5.3-rc7 (so far except: thermal, cpu freq. scaling and t720 gpu - but this is different story...)
-
On 8/2/2019 at 5:32 PM, jernej said:
My patches which you took use old method of enabling DDC (https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-5.3/files/0807-add-orange-pi-3.patch#L370-L586) but DTs which you added later use newer method (https://github.com/megous/linux/commit/4d10f540fe1635c684c5d0e985c5fe6686d412a7).
Well - thx for pointing this!
Unfortunately this probably not explains why I still don't have anything on hdmi output with 5.3 kernel while exactly the same patch set + kernel config gives screen with 5.2 kernel.
I change H6 related patch set from Your git to https://github.com/megous/linux/commits/opi3-5.3 but this not helps.
It looks like 5.3 needs some more work to get hdmi working in each link h6.
boot log for 5.3-rc2 with megous patches attached.
-
13 hours ago, jernej said:
Let me rephrase - can you give me the link to the source code and DT source you're using? Not all patches needed to make this (kinda) work are merged and different, incompatible versions exist.
Oh- sorry. I miss Your request :-p
Here are list of patches I'm using to get 5.3 mainline working ok (with gfx & sound) on my hw test set: x86 intel/amd, s905, s912, rk3328, rpi3 and very initially h6 (forget some of h6 patches. this is for pure experiments):
https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-5.3/Makefile
Patches are here: https://github.com/warpme/minimyth2/tree/master/script/kernel/linux-5.3/files
DT for eachlink H6 i'm using is here: https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-5.3/files/0812-arm64-dts-allwinner-add-h6-eachlink-h6mini.patch
-
23 hours ago, jernej said:
Which kernel sources are you using?
I'm using mainline 5.3-rc2.
Sill can't get HDMI screen working on 5.3.
Exactly the same build but with 5.2 mainline gives HDMI - so it looks 5.3 has something hanged...
(5.3-rc2 boot log attached)
-
On 7/29/2019 at 6:48 PM, hexdump said:
@PiotrO - dd you btw. check if hdmi out works on your eachlink without the "video=HDMI-A-1:e"? is your eachlink board revision 1.1 or 1.2?
best wishes and good luck - hexdump
sorry for late replay.
With 5.2 kernel adding video=HDMI-A-1:e is required to get anything on screen.
With 5.3-rc3 screen not works.
Regarding board ver. - it is v1.1.
Did You see anywhere on Internet android DT for this board?
-
19 hours ago, jernej said:
why not? According to Android DT voltage regulator node, it's fixed voltage regulator, so it's supplying voltage, you just can't change it or disable it. GPU support does not depend if you can or can't adjust voltage. It only means that it will produce more heat than necessary.
Oh - I just was extrapolating from other H6 designs :-p.
Is anybody looking on GPU support in eachlink h6?
If not - may You pls provide me (or point to) Android DT for this device for experimenting?
I can play with this hw for gpu support - but probably will need some assistance.....
BTW: regarding audio support: I already experimenting with 5.2 mainline + Your's LibreELEC H6 patches from https://github.com/jernejsk/LibreELEC.tv/tree/tanix-tx6/projects/Allwinner/devices/H6/patches/linux
As I mentioned in my post:
sound modules seems to be loaded - but no any audio reported by alsa.
May You hint me where to further investigate why there is no any sound card?
-
13 hours ago, hexdump said:
@PiotrO - for the frequency scaling there two things needed:
- the hardware on tv boxes (or maybe their current support) does not support a changable voltage for the cpu - you only have one fixed voltage and you'll have to change the ranges of all opp speeds you want to support to include this one voltage (opp-table in sun50i-h6.dtsi)
- i think you need to create (vcccpu) and attach a cpu-supply voltage regulator (&cpu0 section) to make it work
have a look at my qplus and eachlink-h6mini dtbs in the patch i attached above. this should get you forward i guess.
on my eachlink h6 mini (board revision v1.2) i have to add video=HDMI-A-1:e to get hdmi output at all. if you have an eachlink too, it might be interesting if you get something on hdmi without it.
what gpu node in the dtb are you using for panfrost?
best wishes and good luck - hexdump
Thx for replay!
It looks eachlink mini box isn't god investment for anybody who wants to play with H6....
This box is not using AXP 805 PMIC (typically bundled with the H6) but unknown IC which cryptic label "A8038 8099330k".
Unless we will have support for this PMIC - no GPU support nor any other HW parts supplied by this PMIC :-(
Allwinner H6
in Allwinner CPU Boxes
Posted
@Pic55
great you find time to play with this.
many thx!
i'm really surprised about hang of tx6-p model.
ideally will be to see what logging on UART says.
Is armbian working ok on this box?
btw: I suspect hang is at wifi driver.
Interesting will be to
-mount sd card ROOTFS partition under Linux
-delete /rootfs-ro/lib/modules/5.17.0-rc6/kernel/drivers/net/wireless/*
-see is it booting