Windows 10 & GhostBSD

Post your general questions or comments about GhostBSD here!
NevilleGoddard
Developer
Posts: 421
Joined: Thu Dec 22, 2016 10:30 pm
Location: Japan
Has thanked: 6 times
Been thanked: 4 times

Re: Windows 10 & GhostBSD

Post by NevilleGoddard » Sat Dec 09, 2017 9:41 am

:lol:

hank2000
Posts: 253
Joined: Mon Sep 16, 2013 9:42 am
Has thanked: 2 times
Been thanked: 1 time

Re: Windows 10 & GhostBSD

Post by hank2000 » Sun Dec 10, 2017 8:15 am

OK,

tried a little bit further and stumbled across some very weired things or behaviour:

1) since major update (well, about 40+ packages yesterday) every 5th or 6th reboot, the system starts until maybe the network interfaces are loaded/configured, then black screen and it starts again from the beginning: "acer" logo, boot loader etcetc.
From shutdown and the rest of reboots the boot process is normal and gets me to the login screen.
I still wonder why there are two 'slim_enable="YES" ' entries in 'rc.conf'?
2) main problem: unstable wlan still UNsolved! :(
I now know the exact chipset and the 'rsu' driver configuration should work with it, but I only have about 5 minutes wlan then it s deactivated again...nameserver entries and 'loader.conf' as well as wpa_supplicant.conf- entries fit,too!!
3) strangely, I found my "root"-password in 'wpa_supplicant.conf' after installation and the steps from the GhostBSD FAQ instead of my router-password when network manager did this on its own,corrected that manually, so these entries fit now, too!
4) it needed 4 attempts to even get the installation process goin, three times it said "failed" but I couldn t find any 'pcsysinstall' or whatever file to find the reason; then with exact the SAME procedure it suddenly worked, installation tog. with ntfs partitions maybe a bit buggy?
5) what happend to 'Gimp'? can t find the program in the repositories anymore, only the help-files!?
at least with OctoPkg there s no gimp, could try the ports of course!

So far, very mixed feelings with GhostBSD 11.1 on my Acer Aspire, at least Win 10 and openSuSe 42 Leap had no problems at all with my Qualcomm/Atheros wlan chipset, a pity BSD does!
hope, I ll get a stable wlan soon, otherwise I can t work with the BSD-side seriously.
Then - Plan B would be, cont. with the netbook-version of Ghost 10.3, wait til I may get the Lenovo T430 from my wife, and start a new attempt!!
Guess, experiencing with drivers has "dried out" but maybe there s another idea I haven t taken into consideration yet!

best
Achim

NevilleGoddard
Developer
Posts: 421
Joined: Thu Dec 22, 2016 10:30 pm
Location: Japan
Has thanked: 6 times
Been thanked: 4 times

Re: Windows 10 & GhostBSD

Post by NevilleGoddard » Sun Dec 10, 2017 8:59 am

Are you dual-booting? I looked on some forums and they said that even ubuntu users can have network problems while dual-booting.
The solution that worked for them was to disable "boot from LAN" in the BIOS.

So the network was working before but since the update it has become unreliable again? I'd remove the other slim_enable entry in rc.conf. And check the other lines in rc.conf concerning the wlan settings to make sure they weren't changed.

I don't know if you have already done this but maybe you can try the Atheros again.
Try these steps.

To configure the network , edit your /etc/rc.conf by adding the following line ( to configure the network on startup):

wlans_ath0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"

Create a wlan interface:

ifconfig wlan0 create wlandev ath0

Scan for access points:

ifconfig wlan0 up scan

Create a /etc/wpa_supplicant.conf configuration file with the following contents:

network={
ssid="your_ssid"
psk="your_password"
}

Connect:

To connect you need to restart the network service:

service netif restart

After restarting the network service, the wifi should work.

Or you ca do:

wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf


If that doesn't work, try the other driver:

boot/loader.conf:

if_urtwn_load="YES"

/etc/rc.conf

wlans_urtwn0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"

Best of luck.
I also have mixed feelings about GhostBSD 11.1. My thumbnails aren't working properly. In FreeBSD they work fine.

hank2000
Posts: 253
Joined: Mon Sep 16, 2013 9:42 am
Has thanked: 2 times
Been thanked: 1 time

Re: Windows 10 & GhostBSD

Post by hank2000 » Sun Dec 10, 2017 10:10 am

Hi Neville,

thanks a lot for all Your efforts man!
You def. prevented me from getting back to openSuse so far. ;)
1) well, I checked the rc.conf entries and deleted the 2nd "slim" entry, everything else seems fine so far.
2) yes, it s a dual boot system with Win 10/GhostBSD but never had problems with that concerning "wlan" but will check that bios hint from You, too!
3) great, if that Qualcomm/Atheros chip could work, too; will try that tom. evening as I have to prepare for work tomorrow this evening.
but strange is, that wlan works very different concerning stability, now running for more than 1/4 hour, sometimes just two minutes..... strange!
let s have a break and see what runs best tomorrow evening.
BTW: donnow who gave me the hint, but ordered a ASUS stick with the Realtek xxxxCU chipset as well, so 3 ways to try out, ONE should work out, shouldn t it-F.G.`s SAKE! :?

cheers
Achim

NevilleGoddard
Developer
Posts: 421
Joined: Thu Dec 22, 2016 10:30 pm
Location: Japan
Has thanked: 6 times
Been thanked: 4 times

Re: Windows 10 & GhostBSD

Post by NevilleGoddard » Sun Dec 10, 2017 10:14 am

OK. Good luck tomorrow.

All the best

hank2000
Posts: 253
Joined: Mon Sep 16, 2013 9:42 am
Has thanked: 2 times
Been thanked: 1 time

Re: Windows 10 & GhostBSD

Post by hank2000 » Sun Dec 10, 2017 3:03 pm

NevilleGoddard wrote:OK. Good luck tomorrow.

All the best
well, I tried already tonight as I couldn t get it out of my head!

1) Atheros attempts completely failed, wasn t even able to create the wlan0 interface with "ifconfig wlan0 create wlandev ath0... "(always said: "bad value" when I entered that command), no wlan0 was detected afterwards, so no scan possible and no 'wpa_supplicant' file as well! :(
2) back to the 'rsu' driver for now with valid entries in 'wpa_supplicant.conf and waiting for the Asus nano stick ordered today.
3) next attempt with that Asus stick, if no improvements with that I ll stay with the netbook GhostBSD and put openSuse Linux on here.
4) no network boot in Bios or any stuff BTW and I guess, with re0=DHCP for 'Ethernet' in the network management, that shouldn t be a problem should it??

best
Achim

hank2000
Posts: 253
Joined: Mon Sep 16, 2013 9:42 am
Has thanked: 2 times
Been thanked: 1 time

Re: Windows 10 & GhostBSD

Post by hank2000 » Sat Dec 16, 2017 2:31 pm

Hi Folks,

well, with the ASUS N10 wlan stick I was able to get a "stable" connection, but with awful speed and I found another obstacle I need a solution for.
My Acer Aspire has a cinch-connect for the headset but it does not work, there s always the speaker on with vlc as well as Exaile!
does anyone know where to configure the use of headset except for the mixer?
and what happend to Gimp??

best
Achim

NevilleGoddard
Developer
Posts: 421
Joined: Thu Dec 22, 2016 10:30 pm
Location: Japan
Has thanked: 6 times
Been thanked: 4 times

Re: Windows 10 & GhostBSD

Post by NevilleGoddard » Sun Dec 17, 2017 8:10 am

Hi, Achim.

How far away from the router in the usb device?
About the slow network some users have found an improvement when they use the -ht flag when creating the wlan device.

So maybe try this:

in /boot/loader.conf

if_urtwn_load="YES"
legal.realtek.license_ack=1

in /etc/rc.conf

wlans_urtwn0="wlan0"
ifconfig_urtwn0="SYNCDHCP"

create urtwn0 device

ifconfig -ht wlan0 create wlandev urtwn0

restart network

service netif restart
service routing restart

if this is no improvement try in rc.conf

wlans_urtwn0="wlan0"
ifconfig_urtwn0="DHCP"

About the headset issue, it probably means GhostBSD hasn't or can't configure the audio pins properly. The good news is I had the same problem on FreeBSD 10 and fixed it.
Also on my old laptop the headset works properly out of the box.

if you run dmesg -a or look in /var/run/dmesg.boot you may find something like this:

hdaa0: nid 0x as seq device conn jack loc color misc
hdaa0: 20 01014020 2 0 Line-out Jack 1/8 Rear Green 0
hdaa0: 21 99130110 1 0 Speaker Fixed ATAPI Onboard Unknown 1
hdaa0: 22 411111f0 15 0 Speaker None 1/8 Rear Black 1 DISA
hdaa0: 23 411111f0 15 0 Speaker None 1/8 Rear Black 1 DISA
hdaa0: 24 01a19830 3 0 Mic Jack 1/8 Rear Pink 8
hdaa0: 25 02a1983f 3 15 Mic Jack 1/8 Front Pink 8
hdaa0: 26 01813031 3 1 Line-in Jack 1/8 Rear Blue 0
hdaa0: 27 0221401f 1 15 Headphones Jack 1/8 Front Green 0
hdaa0: 28 411111f0 15 0 Speaker None 1/8 Rear Black 1 DISA
hdaa0: 30 411111f0 15 0 Speaker None 1/8 Rear Black 1 DISA
hdaa0: 31 411111f0 15 0 Speaker None 1/8 Rear Black 1 DISA

The columns as means association, seg is sequence nid is node ID.

Notice 2 lines:
nid as seq device conn jack location color misc
hdaa0: 27 0221401f 1 15 Headphones Jack 1/8 Front Green 0
your headphone jack
nid as seq device conn jack location color misc
hdaa0: 20 01014020 2 0 Line-out Jack 1/8 Rear Green 0
Line out
nid as seq device conn location color misc
hdaa0: 21 99130110 1 0 Speaker Fixed ATAPI Onboard Unknown 1
onboard speaker


There is a file /boot/device.hints which you can edit to change the behaviour of these pins and you can configure the speakers to mute when connecting headphones.

In this case putting these lines in /boot/device.hints will do the trick:

hint.hdac.0.cad0.nid20.config="as=1"
hint.hdac.0.cad0.nid21.config="as=2"

You have to change the nidXX numbers and the "as" numbers according to your Acer machine.

It was so long ago when I did it but I remember it worked perfeclty.

Some help here https://forums.freebsd.org/threads/10451/ and here https://www.freebsd.org/cgi/man.cgi?que ... ease-ports

By the way, what audio chip is the Acer using?

wb7odyfred
Posts: 22
Joined: Sat Nov 12, 2016 5:44 pm
Has thanked: 0
Been thanked: 0

Re: Windows 10 & GhostBSD

Post by wb7odyfred » Mon Dec 18, 2017 6:44 am

hank2000 wrote:
NevilleGoddard wrote:OK. Good luck tomorrow.

All the best
well, I tried already tonight as I couldn t get it out of my head!

1) Atheros attempts completely failed, wasn t even able to create the wlan0 interface with "ifconfig wlan0 create wlandev ath0... "(always said: "bad value" when I entered that command), no wlan0 was detected afterwards, so no scan possible and no 'wpa_supplicant' file as well! :(


best
Achim
Achim what are the outputs of these two commands: Do they show a wlan device on the PCI bus or wlan device plugged into a USB bus? Maybe you don't have an atheros wlan device on this computer? see forum post for detailed explanations viewtopic.php?f=64&t=570

Code: Select all

pciconf -lv
usbconfig list 
usbconfig dump_device_desc
For my Dell Inspiron 11 3000 series computer:
ath0@pci0:1:0:0: class=0x028000 card=0x020e1028 chip=0x0036168c rev=0x01 hdr=0x00
vendor = 'Qualcomm Atheros'
device = 'QCA9565 / AR9565 Wireless Network Adapter'
class = network


http://www.exton.se/?p=1472 Arne Exton has a fantastic write up with lots of pictures for Dual booting Win10 and Linux using GRUB2. I placed this here because GhostBSD 11.1 uses (what method) for booting up from hard drive?. I am still researching.
Older boot BSD using grub post from Google Web Cache'
http://webcache.googleusercontent.com/s ... refox-b-ab
Refers to wonkity.com disksetup website
http://wonkity.com/~wblock/docs/html/disksetup.html


Achim, would like to see what configuration works for you on Dual booting GhostBSD and Windows 10 or Windows 8,

I have an Atheros AR9565 PCI Wifi chip working here in GHOSTBSD11.1 booting from USB flash drive as wlan0.

What version of Atheros Wifi chip is in your hardware, Achim?

Notes:
/etc/rc.conf file last two lines

Code: Select all

wlans_ath0="wlan0"
ifconfig_wlan0="WPA DHCP"
/etc/wpa_supplicant.conf file contents
root@ghostbsd:~ # cat /etc/wpa_supplicant.conf

Code: Select all

network={
  	ssid="ES_32439"
  	psk="42600000"
}

Debug wpa_supplicant command: Open a separate root terminal from MENU --> Applications --> Root Terminal

Code: Select all

wpa_supplicant -d -K -iwlan0 -c/etc/wpa_supplicant.conf
Open a second Root Terminal and issue the command to test internet connectivity:

Code: Select all

ping -c 3 he.net
or

Code: Select all

ping -c 3 ghostbsd.org
"he.net" is just quicker to type

root@ghostbsd:~ # ping -c 3 ghostbsd.org
PING ghostbsd.org (192.99.188.34): 56 data bytes
64 bytes from 192.99.188.34: icmp_seq=0 ttl=47 time=116.668 ms
64 bytes from 192.99.188.34: icmp_seq=1 ttl=47 time=134.310 ms
64 bytes from 192.99.188.34: icmp_seq=2 ttl=47 time=134.188 ms

--- ghostbsd.org ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 116.668/128.389/134.310/8.288 ms
root@ghostbsd:~ # ping -c 3 he.net
PING he.net (216.218.186.2): 56 data bytes
64 bytes from 216.218.186.2: icmp_seq=0 ttl=50 time=70.920 ms
64 bytes from 216.218.186.2: icmp_seq=1 ttl=50 time=108.351 ms
64 bytes from 216.218.186.2: icmp_seq=2 ttl=50 time=120.227 ms

Code: Select all

netstat -4r
root@ghostbsd:~ # netstat -4r
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 192.168.43.1 UGS wlan0
localhost link#1 UH lo0
192.168.43.0/24 link#2 U wlan0
ghostbsd link#2 UHS lo0
root@ghostbsd:~ #
root@ghostbsd:~ # ifconfig wlan0
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether ec:0e:c4:1f:ea:73
hwaddr ec:0e:c4:1f:ea:73
inet 192.168.43.114 netmask 0xffffff00 broadcast 192.168.43.255
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
ssid ES_32439 channel 8 (2447 MHz 11g ht/20) bssid 5c:af:06:4f:bc:83
regdomain 108 indoor ecm authmode WPA privacy ON deftxkey UNDEF
TKIP 2:128-bit TKIP 3:128-bit txpower 20 bmiss 7 scanvalid 60
protmode CTS ampdulimit 64k shortgi -stbctx stbcrx wme burst
roaming MANUAL
groups: wlan
if network problems then:

Code: Select all

killall dhclient
dhclient wlan0
or use these commands that Neville suggested

Code: Select all

service netif restart
service routing restart
Neville thanks for your detailed messages. I have learned from the information you have provided to others.
Do you have other suggestions for debugging the Atheros wlan wifi problems Achim is having. I provided links to the manual entries and the dmesg output below.

wlandebug (8) manual entry
http://polarhome.com/service/man/?qf=wl ... stBSD&sf=8

wlan (4) manual entry
http://polarhome.com/service/man/?qf=wl ... stBSD&sf=4

ifconfig (8) manual entry
http://polarhome.com/service/man/?qf=if ... stBSD&sf=8
To disable all use of 802.11n use -ht. from Neville's suggestion in previous post
about creating urtwn0 device and disable all use of 802.11n Read the ifconfig (8) manual entry above.

Code: Select all

ifconfig -ht wlan0 create wlandev urtwn0
I used the log viewer application from MENU --> Applications --> System tools --> Log File Viewer to see the "dmesg" messages quoted below. What do you see listed about your Atheros device, Achim
Dec 18 02:11:09 ghostbsd kernel: ath0: <Qualcomm Atheros AR9565> mem 0x90400000-0x9047ffff irq 16 at device 0.0 on pci1
Dec 18 02:11:09 ghostbsd kernel: ath0: WB335 2-ANT card detected
Dec 18 02:11:09 ghostbsd kernel: ath0: Bluetooth Antenna Diversity card detected
Dec 18 02:11:09 ghostbsd kernel: ar9300_attach: calling ar9300_hw_attach
Dec 18 02:11:09 ghostbsd kernel: ar9300_hw_attach: calling ar9300_eeprom_attach
Dec 18 02:11:09 ghostbsd kernel: ar9300_flash_map: unimplemented for now
Dec 18 02:11:09 ghostbsd kernel: Restoring Cal data from DRAM
Dec 18 02:11:09 ghostbsd kernel: Restoring Cal data from EEPROM
Dec 18 02:11:09 ghostbsd kernel: Restoring Cal data from Flash
Dec 18 02:11:09 ghostbsd kernel: Restoring Cal data from Flash
Dec 18 02:11:09 ghostbsd kernel: Restoring Cal data from OTP
Dec 18 02:11:09 ghostbsd kernel: ar9300_hw_attach: ar9300_eeprom_attach returned 0
Dec 18 02:11:09 ghostbsd kernel: ath0: [HT] enabling HT modes
Dec 18 02:11:09 ghostbsd kernel: ath0: [HT] enabling short-GI in 20MHz mode
Dec 18 02:11:09 ghostbsd kernel: ath0: [HT] 1 stream STBC receive enabled
Dec 18 02:11:09 ghostbsd kernel: ath0: [HT] 1 RX streams; 1 TX streams
Dec 18 02:11:09 ghostbsd kernel: ath0: QCA9565 mac 704.1 RF5110 phy 2630.0
Dec 18 02:11:09 ghostbsd kernel: ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000
Dec 18 02:11:09 ghostbsd kernel: isab0: <PCI-ISA bridge> at device 31.0 on pci0

much later in message file

Dec 18 02:11:34 ghostbsd kernel: wlan0: Ethernet address: ec:0e:c4:1f:ea:73
Dec 18 02:11:35 ghostbsd ghostbsd: /etc/rc.d/wpa_supplicant: WARNING: /etc/wpa_supplicant.conf is not readable.
Dec 18 02:11:35 ghostbsd ghostbsd: /etc/rc.d/wpa_supplicant: WARNING: failed precmd routine for wpa_supplicant
Dec 18 02:11:35 ghostbsd root: /etc/rc.d/wpa_supplicant: WARNING: /etc/wpa_supplicant.conf is not readable.
Dec 18 02:11:35 ghostbsd root: /etc/rc.d/wpa_supplicant: WARNING: failed precmd routine for wpa_supplicant
Dec 18 02:12:13 ghostbsd su: ghostbsd to root on /dev/pts/0
Dec 18 02:12:52 ghostbsd kernel: ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping
Dec 18 02:13:51 ghostbsd kernel: ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping
Dec 18 02:14:38 ghostbsd kernel: ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping
Dec 18 02:17:44 ghostbsd last message repeated 2 times
Dec 18 02:17:46 ghostbsd kernel: wlan0: link state changed to UP
Dec 18 02:17:48 ghostbsd dhclient: New IP Address (wlan0): 192.168.43.114
Dec 18 02:17:48 ghostbsd dhclient: New Subnet Mask (wlan0): 255.255.255.0
Dec 18 02:17:48 ghostbsd dhclient: New Broadcast Address (wlan0): 192.168.43.255
Dec 18 02:17:48 ghostbsd dhclient: New Routers (wlan0): 192.168.43.1
Achim, Here is the Audio interface information also from Log Viewer with the nid information for my Dell Inspiron 11 3000 series
Dec 18 02:11:09 ghostbsd kernel: hdacc0: <Realtek ALC255 HDA CODEC> at cad 0 on hdac0
Dec 18 02:11:09 ghostbsd kernel: hdaa0: <Realtek ALC255 Audio Function Group> at nid 1 on hdacc0
Dec 18 02:11:09 ghostbsd kernel: pcm0: <Realtek ALC255 (Internal Analog)> at nid 20 and 18 on hdaa0
Dec 18 02:11:09 ghostbsd kernel: pcm1: <Realtek ALC255 (Front Analog Headphones)> at nid 33 on hdaa0
Dec 18 02:11:09 ghostbsd kernel: hdacc1: <Intel (0x2882) HDA CODEC> at cad 2 on hdac0
Dec 18 02:11:09 ghostbsd kernel: hdaa1: <Intel (0x2882) Audio Function Group> at nid 1 on hdacc1
Dec 18 02:11:09 ghostbsd kernel: pcm2: <Intel (0x2882) (HDMI/DP 8ch)> at nid 4 on hdaa1

hank2000
Posts: 253
Joined: Mon Sep 16, 2013 9:42 am
Has thanked: 2 times
Been thanked: 1 time

Re: Windows 10 & GhostBSD

Post by hank2000 » Mon Dec 18, 2017 2:10 pm

Hi,

well, my wlan chipset is: the new Qualcomm/Atheros QCA9377ac!
I tried every hint from GhostBSD´s FAQs as well as freeBSD forums and man pages, so stopped with "playing around" with the Atheros chipset!

The best results are with the Asus N10 and "urtwn" drivers so far, will try the Lenovo t430 with the live version of GhostBSD 11.1 this week and see what wifi support THIS has...
But thx for the infos on my headset problems Neville, but I m tired of adjusting and configuring stuff on my new laptop, I now want to work with it.
And when GhostBSD is NOT that user friendly with new hardware I m afraid I have to find something that IS....
I still have my Asus eeePC 1005 that works with either wlan and streaming radio via headset, so I guess I ll leave it to that for the moment tog. with 10.3 and see what happens to that Lenovo laptop and GhostBSD 11.1.
It s frustrating that my 10 yr old wlan PCI card is much faster from my room than any modern USB stick I tried!
I m about 5 meters away from my router with a wooden door seperating my room from the living room, that shouldn t be a problem of stability anymore these days...

best
Achim

Post Reply