Interesting observation.
With the latest uboot (2018.09) and Fedora 29-beta-Xfce
No wifi. Nothing shows when I do 'ip a'
BUT...
Same uboot, but the Centos7 image:
CentOS-Userland-7-armv7hl-generic-GNOME-1804-sda
There is the wifi interface. The Gnome install asks me if I want to connect to any of the visible SSIDs.
How did the Centos arm team get this to work and not Fedora? :)
Really not so important RIGHT now, as my CT is for a Centos server. I am only planning on running Fedora on Cubieboard2 which do not have their own embedded wifi.
Just a data point for now.
On 9/27/18 7:34 PM, Robert Moskowitz wrote:
Interesting observation.
With the latest uboot (2018.09) and Fedora 29-beta-Xfce
No wifi. Nothing shows when I do 'ip a'
BUT...
Same uboot, but the Centos7 image:
CentOS-Userland-7-armv7hl-generic-GNOME-1804-sda
There is the wifi interface. The Gnome install asks me if I want to connect to any of the visible SSIDs.
How did the Centos arm team get this to work and not Fedora? :)
Really not so important RIGHT now, as my CT is for a Centos server. I am only planning on running Fedora on Cubieboard2 which do not have their own embedded wifi.
Just a data point for now.
Another datapoint:
Centos is running the WPA Supplicant daemon. Fedora is not. But is there a WPA Supplicant daemon in Fedora, or is this function merged into NetworkManager?
Did you take a look at dmesg?, perhaps you can dmesg > boot.out and attach it.
Nige
On Thu, Sep 27, 2018 at 8:23 PM Robert Moskowitz rgm@htt-consult.com wrote:
On 9/27/18 7:34 PM, Robert Moskowitz wrote:
Interesting observation.
With the latest uboot (2018.09) and Fedora 29-beta-Xfce
No wifi. Nothing shows when I do 'ip a'
BUT...
Same uboot, but the Centos7 image:
CentOS-Userland-7-armv7hl-generic-GNOME-1804-sda
There is the wifi interface. The Gnome install asks me if I want to connect to any of the visible SSIDs.
How did the Centos arm team get this to work and not Fedora? :)
Really not so important RIGHT now, as my CT is for a Centos server. I am only planning on running Fedora on Cubieboard2 which do not have their own embedded wifi.
Just a data point for now.
Another datapoint:
Centos is running the WPA Supplicant daemon. Fedora is not. But is there a WPA Supplicant daemon in Fedora, or is this function merged into NetworkManager?
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
On 9/27/18 8:30 PM, Nigel Sollars wrote:
Did you take a look at dmesg?, perhaps you can dmesg > boot.out and attach it.
System is powered down, probably for the night. I finished up what I was going to do with it. Tomorrow. And do you mean the Centos on CT or Fedora on CT image?
Nige
On Thu, Sep 27, 2018 at 8:23 PM Robert Moskowitz <rgm@htt-consult.com mailto:rgm@htt-consult.com> wrote:
On 9/27/18 7:34 PM, Robert Moskowitz wrote: > Interesting observation. > > With the latest uboot (2018.09) and Fedora 29-beta-Xfce > > No wifi. Nothing shows when I do 'ip a' > > BUT... > > Same uboot, but the Centos7 image: > > CentOS-Userland-7-armv7hl-generic-GNOME-1804-sda > > There is the wifi interface. The Gnome install asks me if I want to > connect to any of the visible SSIDs. > > How did the Centos arm team get this to work and not Fedora? :) > > Really not so important RIGHT now, as my CT is for a Centos server. I > am only planning on running Fedora on Cubieboard2 which do not have > their own embedded wifi. > > Just a data point for now. > Another datapoint: Centos is running the WPA Supplicant daemon. Fedora is not. But is there a WPA Supplicant daemon in Fedora, or is this function merged into NetworkManager? _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org <mailto:arm@lists.fedoraproject.org> To unsubscribe send an email to arm-leave@lists.fedoraproject.org <mailto:arm-leave@lists.fedoraproject.org> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org-- “Science is a differential equation. Religion is a boundary condition.” Alan Turing
I think from both would be helpful, also would be a good idea to look at the boot args from both and as much info you can get out of uboot on both.
( I know im not asking for much : ) ) ..
I am interested to see what the difference is.
Nige
On Thu, Sep 27, 2018 at 8:35 PM Robert Moskowitz rgm@htt-consult.com wrote:
On 9/27/18 8:30 PM, Nigel Sollars wrote:
Did you take a look at dmesg?, perhaps you can dmesg > boot.out and attach it.
System is powered down, probably for the night. I finished up what I was going to do with it. Tomorrow. And do you mean the Centos on CT or Fedora on CT image?
Nige
On Thu, Sep 27, 2018 at 8:23 PM Robert Moskowitz rgm@htt-consult.com wrote:
On 9/27/18 7:34 PM, Robert Moskowitz wrote:
Interesting observation.
With the latest uboot (2018.09) and Fedora 29-beta-Xfce
No wifi. Nothing shows when I do 'ip a'
BUT...
Same uboot, but the Centos7 image:
CentOS-Userland-7-armv7hl-generic-GNOME-1804-sda
There is the wifi interface. The Gnome install asks me if I want to connect to any of the visible SSIDs.
How did the Centos arm team get this to work and not Fedora? :)
Really not so important RIGHT now, as my CT is for a Centos server. I am only planning on running Fedora on Cubieboard2 which do not have their own embedded wifi.
Just a data point for now.
Another datapoint:
Centos is running the WPA Supplicant daemon. Fedora is not. But is there a WPA Supplicant daemon in Fedora, or is this function merged into NetworkManager?
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
-- “Science is a differential equation. Religion is a boundary condition.”
Alan Turing
Interesting observation.
With the latest uboot (2018.09) and Fedora 29-beta-Xfce
No wifi. Nothing shows when I do 'ip a'
BUT...
Same uboot, but the Centos7 image:
CentOS-Userland-7-armv7hl-generic-GNOME-1804-sda
There is the wifi interface. The Gnome install asks me if I want to connect to any of the visible SSIDs.
How did the Centos arm team get this to work and not Fedora? :)
Really not so important RIGHT now, as my CT is for a Centos server. I am only planning on running Fedora on Cubieboard2 which do not have their own embedded wifi.
Just a data point for now.
Another datapoint:
Centos is running the WPA Supplicant daemon. Fedora is not. But is there a WPA Supplicant daemon in Fedora, or is this function merged into NetworkManager?
Fedora runs it, in some cases, but it's started by NM on demand when it needs it, there's also a iwd that replaces it in some situations.
On Fri, Sep 28, 2018 at 12:34 AM Robert Moskowitz rgm@htt-consult.com wrote:
Interesting observation.
With the latest uboot (2018.09) and Fedora 29-beta-Xfce
No wifi. Nothing shows when I do 'ip a'
BUT...
Same uboot, but the Centos7 image:
CentOS-Userland-7-armv7hl-generic-GNOME-1804-sda
There is the wifi interface. The Gnome install asks me if I want to connect to any of the visible SSIDs.
How did the Centos arm team get this to work and not Fedora? :)
Really not so important RIGHT now, as my CT is for a Centos server. I am only planning on running Fedora on Cubieboard2 which do not have their own embedded wifi.
Just a data point for now.
We don't ship it because 1) it's not upstream in the Linux kernel or linux-firmware 2) the information currently can't be redistributed legally, for a couple of reasons. This is the same issue on the Raspberry Pi and a number of other devices with broadcom chips. The file that CentOS has now doubt chosen to ship is device specific but linux currently deals with it generically so if another device has the same wifi model with things like clocks/crystals and other settings that are device or regional specific. This could cause random things like actual wifi that shows up but doesn't work, it could actually break the user's device or get the user in trouble for using power/frequencies that are out of range. So the general stance of Fedora is not do things like that and I'd much sooner a user not having working wifi than cooking their device or getting them in trouble with authorities.
All of the above being said I am working with a number of individuals both within Red Hat and other organisations (this has literally taken 3+ years) to get this problem resolved and we're nearing the end game. I don't have a specific timeframe but "Real Soon Now" is what I'm hoping, the Raspberry Pi will be fist in the list to be resolved and the rest should follow on not far behind, people's time pending.
Peter
On 9/28/18 6:55 AM, Peter Robinson wrote:
On Fri, Sep 28, 2018 at 12:34 AM Robert Moskowitz rgm@htt-consult.com wrote:
Interesting observation.
With the latest uboot (2018.09) and Fedora 29-beta-Xfce
No wifi. Nothing shows when I do 'ip a'
BUT...
Same uboot, but the Centos7 image:
CentOS-Userland-7-armv7hl-generic-GNOME-1804-sda
There is the wifi interface. The Gnome install asks me if I want to connect to any of the visible SSIDs.
How did the Centos arm team get this to work and not Fedora? :)
Really not so important RIGHT now, as my CT is for a Centos server. I am only planning on running Fedora on Cubieboard2 which do not have their own embedded wifi.
Just a data point for now.
We don't ship it because 1) it's not upstream in the Linux kernel or linux-firmware 2) the information currently can't be redistributed legally, for a couple of reasons. This is the same issue on the Raspberry Pi and a number of other devices with broadcom chips. The file that CentOS has now doubt chosen to ship is device specific but linux currently deals with it generically so if another device has the same wifi model with things like clocks/crystals and other settings that are device or regional specific. This could cause random things like actual wifi that shows up but doesn't work, it could actually break the user's device or get the user in trouble for using power/frequencies that are out of range. So the general stance of Fedora is not do things like that and I'd much sooner a user not having working wifi than cooking their device or getting them in trouble with authorities.
All of the above being said I am working with a number of individuals both within Red Hat and other organisations (this has literally taken 3+ years) to get this problem resolved and we're nearing the end game. I don't have a specific timeframe but "Real Soon Now" is what I'm hoping, the Raspberry Pi will be fist in the list to be resolved and the rest should follow on not far behind, people's time pending.
Peter,
I am always very appreciative of what you and others there do for us. Given this information, I will not dig more into it. I am looking into the Nethserver community's Centos-arm work, so what Centos is doing on my Cubietruck is of immediate value. Maybe. :)
I can wait for your Fedora-arm wifi general solution.
thanks
Peter,
I am always very appreciative of what you and others there do for us. Given this information, I will not dig more into it. I am looking into the Nethserver community's Centos-arm work, so what Centos is doing on my Cubietruck is of immediate value. Maybe. :)
I can wait for your Fedora-arm wifi general solution.
This will land into Fedora first but the solution is a generic upstream so will benefit the entire linux ecosystem not just Fedora.
-
Nigel Sollars -
Peter Robinson -
Robert Moskowitz