The technology exists, I've seen it demo'ed. Getting it to work
requires unusually high levels of expertise with both wpa_supplicant
and GNOME (or similar), and I think that lack of critical developer
mass has been the real hinderance.
John
--
John W. Linville
On Thu, 2014-06-26 at 07:14 -0400, Neal Becker wrote:
> John W. Linville wrote:
>
> > We are expecting to see a presentation of some work done on Miracast at
> > the Wireless Networking mini-conference that is part of the Linux
> > Plumber's Conference in Düsseldorf
>
> > >
> > > Seems like this project has the potential to open a big hole
> > > into a system's security and user's privacy :) :)
> > >
> >
> > Oh, of course! WiFi Alliance is all about making things EASY.
> >
> > Safe
m the kernel, do you know if it was added in terms of
> (a)kmod support? I've not yet seen anything about it.
As you intuit, cutting oneself off from future kernel updates is an
overreaction.
If your device has stopped working, then open a bug.
John
--
John W. LinvilleToday&
fferent issue.
The ath9k_htc firmware used to be in the linux-firmware tree, but
apparently they have stopped updating it there? Not sure...
Anyway, you can find the firmware and get it installed by starting
here:
http://wireless.kernel.org/en/users/Drivers/ath9k_htc#Firmware
Hth!
John
On Tue, Mar 01, 2011 at 12:57:57PM -0800, Guy, Wey-Yi wrote:
> On Tue, 2011-03-01 at 12:17 -0800, John W. Linville wrote:
> > Well, FWIW I offered to _merge_ a patch. :-)
> >
> > But, if I get some confirmation from a credible source at Intel that
> > simply hono
I can help with the patch, please
> advise.
>
>
>
> On Mon, Feb 28, 2011 at 1:42 PM, John W. Linville wrote:
>
> > On Mon, Feb 28, 2011 at 01:27:59PM -0300, Sebastian wrote:
> > > Thanks John for the message.
> > > Did Wey-yi respond to your mail John
f they say that your hardware will operate outside
of legal limits with your eeprom's values, then I can't enable it in
good conscience.
John
--
John W. LinvilleThe truth will set you free, but first it will
linvi...@redhat.com make you miserabl
#x27;m not sure what else to suggest.
The problem is that the EEPROM contains information related to
regulatory compliance, so using an unsupported data format could
allow your device to operate outside of legal parameters. :-(
Perhaps you could get your hardware supplier to swap-out the card
On Fri, Feb 25, 2011 at 11:23:34PM -0300, Sebastian wrote:
> On Fri, Feb 25, 2011 at 1:06 PM, John W. Linville wrote:
> > What seems most likely is that you have an older (possibly pre-release)
> > piece of hardware that has EEPROM data on the card that the driver
> >
cp iwlwifi-6000-4.ucode /lib/firmware
> 5. sync; sleep 1; sync; sleep 1; reboot
>
> During reboot, the driver will automatically look for iwlwifi-6000-4.ucode
> and load it into the wifi card.
Good grief...
Do this:
rpm -q iwl6000-firmware
If you see this:
iw
supposed to recognize it
is the only remaining question. Hopefully Wey-yi will chime-in.
John
--
John W. LinvilleThe truth will set you free, but first it will
linvi...@redhat.com make you miserable. -- James A. Garfield
--
users mailing list
users@lists.fedorap
ngineering sample that escaped out into the wild? That happens from
time to time...
Wey-yi, is it possible that you picked the wrong value for
EEPROM_6000_EEPROM_VERSION in commit 1f4b9665?
John
--
John W. LinvilleThe truth will set you free, but first it will
linvi...@redhat.com
On Mon, Feb 14, 2011 at 04:30:09PM +, mike cloaked wrote:
> On Mon, Feb 14, 2011 at 4:12 PM, John W. Linville wrote:
>
> > Neither -- the driver (like all mac80211-based drivers) simply does
> > not support that setting. mac80211-based drivers are simple, and
> >
c80211-based drivers are simple, and
they don't do roaming by themselves. Instead they rely on a userland
component (e.g. wpa_supplicant) to take care of roaming for them.
Unfortunately, I don't know of any roaming "knobs" to turn for
wpa_supplicant (or NetworkManager)
bnet.[1]
John
[1] There are other potential configurations for roaming, including
mobile IP and the like. If you (i.e. anyone reading) feels like
trying to explain them in an email then feel free. :-)
--
John W. LinvilleThe truth will set you free, but first it
support for these device. But now?
> >
> > Regards, Franta Hanzlik
>
> may be because the code is still experimental / broken ?
We have a winner...
--
John W. LinvilleThe truth will set you free, but first it will
linvi...@redhat.com
ts and hope someone finds the
time and desire to fix it. :-)
John
--
John W. LinvilleThe truth will set you free, but first it will
linvi...@redhat.com make you miserable. -- James A. Garfield
--
users mailing list
users@lists.fedoraproject.org
To unsu
atheros, etc..are those open source drivers or at least supported fairly
> good? Is there a website that can easily print/look at and see what
> works and what needs 3rd party support?
Stick to Intel and Atheros for best support at this time.
John
--
John W. LinvilleThe truth
; tg3 kernel module. I just booted up after the initial installation and it
> just
> worked. The kernel module must have been installed by default.
That, of course, is an ethernet device.
I still can't recommend a Broadcom wireless device at this time --
hopefully that i
On Mon, Aug 30, 2010 at 01:38:02PM -0700, Daniel B. Thurman wrote:
> On 08/30/2010 12:22 PM, John W. Linville wrote:
> > What kernel are you using?
> # uname -r
> 2.6.32.16-150.fc12.i686
mwl8k is enabled on that kernel. You can verify that it is present
by running 'modinfo
On Mon, Aug 30, 2010 at 01:35:31PM -0700, Daniel B. Thurman wrote:
> On 08/30/2010 12:22 PM, John W. Linville wrote:
> > lspci -n
> # lspci -n
> 00:00.0 0600: 8086:2770 (rev 02)
> 00:02.0 0300: 8086:2772 (rev 02)
> 00:1b.0 0403: 8086:27d8 (rev 01)
> 00:1c.0 0604: 8086:27d0
On Mon, Aug 30, 2010 at 12:04:20PM -0700, Daniel B. Thurman wrote:
> On 08/30/2010 11:31 AM, John W. Linville wrote:
> > On Mon, Aug 30, 2010 at 08:37:14AM -0700, Daniel B. Thurman wrote:
> >
> >> On 08/30/2010 07:49 AM, John W. Linville wrote:
> >>
> &g
On Mon, Aug 30, 2010 at 08:37:14AM -0700, Daniel B. Thurman wrote:
> On 08/30/2010 07:49 AM, John W. Linville wrote:
> > On Sun, Aug 29, 2010 at 10:55:43AM -0700, Daniel B. Thurman wrote:
> >
> >> I have a gateway M-6750 laptop which sports a
> >> Marvell TopDo
t first appears to be working... although there
> are crash data appearing in the log files but other
> than that, it continues on working.
I'm sorry, but I can't offer you any support for ndiswrapper. Did you
try the mwl8k driver?
John
--
John W. LinvilleThe tru
vers/net/wireless.
Unfortunately, they don't seem to be particularly interested in doing
that work themselves. Worse, they seem to be prefectly satisfied
with continuing to turn-out one crap...err..."staging" driver
after another...
John
--
John W. Linville
dhat
> distribution?
Open a bug at that distros bugzilla instance (or equivalent)?
> I am not running fedora atm.
Shame on you! :-)
John
--
John W. LinvilleThe truth will set you free, but first it will
linvi...@redhat.com make you miserable. --
On Sat, Jun 19, 2010 at 08:44:21AM -0500, Bruno Wolff III wrote:
> On Fri, Jun 18, 2010 at 11:35:58 -0400,
> "John W. Linville" wrote:
> >
> > yum install iwl6050-firmware
>
> Was this needed because iwl6050-firmware is such a new package? Would it
> be e
ard work in linux.
>
> http://ubuntuforums.org/showthread.php?t=1424177
yum install iwl6050-firmware
Hth!
John
--
John W. LinvilleThe truth will set you free, but first it will
linvi...@redhat.com make you miserable. -- James A. Garfield
--
users mailing
29 matches
Mail list logo
