3:42 p.m.
I have a Toshiba Satellite L850 Laptop for which the WiFi card appears
to be incompatible
with any drivers available for Linux. To try to get around this problem
I recently purchased
a USB WiFi device: An ASUS USB-N110. They (ASUS) provide drivers which
one must
install. After a great deal of travail and fumbling around (the
instructions were both unclear
--- apparently written by someone for whom English was at best a *third*
language ---
and slightly misleading) I managed to get the device *partially* working.
The device appears to work immediately after boot-up but if I close the
lid of my laptop,
(which causes it to go into hibernation (???) mode) or if I log out and
log back in,
the WiFi connection gets lost. When I try to restore the connection it
seems to keep
trying to use the WiFi card that is built into the laptop rather than
the USB WiFi device.
(And the built-in device doesn't work; as I said, its drivers are
incompatible with Linux OSes.
Which is why I bought the USN-N10 in the first place.) The only way to
get the laptop to
make use of the USB WiFi device seems to be to shut down and restart.
This is unsatisfactory.
Is there any way to "disable" the (non-functional) built-in WiFi card so
that the laptop will
*not* try to use it but will rather go straight to the (functional) USB
device? I Googled around
a bit and found some instructions for disabling the built-in WiFi card
under Ubuntu, but
these instruction did not (as far as I could tell) mesh with the Fedora
system that I am
running. Can anyone tell me how to do what I want under Fedora?
If you reply, ***PLEASE*** be as clear and explicit as you possibly
can. I am not terribly
swift with OS matters. I know and understand ***some*** things, but
there are huge
lacunae in my knowledge.
I am running Fedora 17; output of "uname -a" is:
Linux localhost.localdomain 3.3.4-5.fc17.x86_64 #1 SMP Mon May 7
17:29:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Thanks for any help that anyone can give me.
cheers,
Rolf Turner
7:01 p.m.
New subject: Disable built-in WiFi card so that USB WiFi device gets used --- systemctl?
So far I have received no useful responses to my question (given
below). However I have
recently seen in another thread a considerable amount of discussion of
something called
"systemctl". This sounds like it *might* do what I want. However
looking at the man page
for systemctl leaves just as ignorant as when I started. It's way over
my head. Can someone
tell me:
(a) Would systemctl do what I want, i.e. serve to disable (mask?)
the internal WiFi card?
(b) Would it be possible to disable/mask the internal WiFi card but
leave the USB WiFi device
available, so that I can actually get a WiFi connection?
(c) If the answers to (a) and (b) are "Yes", then could some kind
soul please guide me as
to the syntax to use in calling upon systemctl? In particular, how
do I specify what it is that
I want disabled/masked in such a way that systemctl will understand
what I'm talking about?
cheers,
Rolf Turner
On 28/07/13 08:42, Rolf Turner wrote:
I have a Toshiba Satellite L850 Laptop for which the WiFi card appears
to be incompatible
with any drivers available for Linux. To try to get around this
problem I recently purchased
a USB WiFi device: An ASUS USB-N110. They (ASUS) provide drivers
which one must
install. After a great deal of travail and fumbling around (the
instructions were both unclear
--- apparently written by someone for whom English was at best a
*third* language ---
and slightly misleading) I managed to get the device *partially* working.
The device appears to work immediately after boot-up but if I close
the lid of my laptop,
(which causes it to go into hibernation (???) mode) or if I log out
and log back in,
the WiFi connection gets lost. When I try to restore the connection
it seems to keep
trying to use the WiFi card that is built into the laptop rather than
the USB WiFi device.
(And the built-in device doesn't work; as I said, its drivers are
incompatible with Linux OSes.
Which is why I bought the USN-N10 in the first place.) The only way
to get the laptop to
make use of the USB WiFi device seems to be to shut down and restart.
This is unsatisfactory.
Is there any way to "disable" the (non-functional) built-in WiFi card
so that the laptop will
*not* try to use it but will rather go straight to the (functional)
USB device? I Googled around
a bit and found some instructions for disabling the built-in WiFi card
under Ubuntu, but
these instruction did not (as far as I could tell) mesh with the
Fedora system that I am
running. Can anyone tell me how to do what I want under Fedora?
If you reply, ***PLEASE*** be as clear and explicit as you possibly
can. I am not terribly
swift with OS matters. I know and understand ***some*** things, but
there are huge
lacunae in my knowledge.
I am running Fedora 17; output of "uname -a" is:
> Linux localhost.localdomain 3.3.4-5.fc17.x86_64 #1 SMP Mon May 7
> 17:29:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Thanks for any help that anyone can give me.
5:17 p.m.
On 30/07/13 19:07, poma wrote:
On 30.07.2013 06:51, Rolf Turner wrote:
> On 30/07/13 14:45, poma wrote:
>> On 30.07.2013 00:03, Rolf Turner wrote:
>>> Thanks "poma" (???) and Harald. It sounds like you may have solved
my
>>> problem .... but I'm afraid that your advice is too cryptic for my poor
>>> feeble
>>> brain. Can either of you (or someone else) spell out in tedious detail
>>> just
>>> what I need to do? I cannot figure out whether things written in your
>>> messages
>>> are commands that I issue at the command line or lines that I need to
>>> insert
>>> into certain files. And if so, which files? I'm sure it's all
obvious
>>> to you guys,
>>> but it leaves me floundering.
>>>
>>> Some specific questions:
>>>
>>> (1) "poma's" original posting referred to the directory
/boot/extlinux
>>> and a file therein called extlinux.conf. On my system there is no
>>> directory
>>> "extlinux" in /boot. The only subdirectories of /boot are
"efi", "grub"
>>> and
>>> "grub2".
>>>
>>> Should I create the directory /boot/extlinux and the file
>>> /boot/extlinux/extlinux.conf?
>>> Or is there some other incantation that I should invoke?
>>>
>>> (2) Likewise the original posting refers to <drivername>. How do I
>>> find/figure out
>>> the *name* of the driver associated with the internal WiFi card? This
>>> may sound
>>> clueless, but I guess I am clueless.
>>>
>>> (3) I did "man 7 dracut.cmdline" and found the reference to
>>> "rd.driver.blacklist"
>>> but I could not fathom what it was saying.
>>>
>>> (4) The original posting contains:
>>>> e.g.
>>>> /boot/extlinux/extlinux.conf
>>>> append … rd.driver.blacklist=<drivername>
>>> Is the line "append … rd.driver.blacklist=<drivername>" to be
placed
>>> in the file /boot/extlinux/extlinux.conf? (After I figure out what to
>>> substitute
>>> for "<drivername>" of course.) Are the three dots
"..." literal? Or
>>> are are they a filler for something that I need to insert? If so, what
>>> do I need to insert? I haven't a clue!
>>>
>>> (5) I have found the file /boot/grub2/grub.cfg alright. But it has a
>>> header
>>> saying "DO NOT EDIT THIS FILE". It goes on to say:
>>>> # It is automatically generated by grub2-mkconfig using templates
>>>> # from /etc/grub.d and settings from /etc/default/grub
>>> So do I need to edit /etc/default/grub? Or what?
>>>
>>> (6) In respect of "poma's" follow-up posting: Do I create a
file
>>> /etc/modprobe.d/blacklist.<modulename>.conf (after having figured
>>> out what "<modulename>" should be) and place in it the line:
>>>
>>> blacklist <modulename>
>>>
>>> (again after having figured out what "<modulename>" should
be) ?
>>>
>>> (7) In /etc/modprobe.d there is already a file called
>>> "blacklist.conf" in
>>> which there are many many lines such as:
>>>
>>>> # watchdog drivers
>>>> blacklist i8xx_tco
>>>>
>>>> # framebuffer drivers
>>>> blacklist aty128fb
>>>> blacklist atyfb
>>>> blacklist radeonfb
>>>> blacklist i810fb
>>>> blacklist cirrusfb
>>> .........
>>>
>>> Could I just put "blacklist <modulename>" into that file?
>>>
>>> (8) "poma" says " However OP should upgrade, anyway."
I'm sure that
>>> I should. But the thought terrifies me. After all that I have read on
>>> this
>>> list recently about problems with Fedora 19, with fedup, with "yum
>>> upgrade".
>>> I have understood almost none of the discourse but it seems to indicate
>>> that upgrading is essentially impossible unless you *really* know
>>> what you
>>> are doing. And I don't.
>>>
>>> Is there a simple (hah!) recipe by means of which I could upgrade? E.g.
>>> could I just type
>>>
>>> sudo fedup
>>>
>>> at the command line? Or perhaps
>>>
>>> sudo yum upgrade
>>>
>>> ??? If either would work, what are the implications of using the one
>>> rather
>>> than the other?
>>>
>>> Thanks for any insight.
>>>
>>> cheers,
>>>
>>> Rolf Turner
>>>
>>>
>> Step by step. ;)
>>
>> This is the hyperlink:
>> https://support.mozillamessaging.com/en-US/kb/reply-above-or-below-quoted...
>>
>> Below quoted text, s'il vous plaît.
>>
>> This is the command - c/p into reply s'il vous plaît:
>> $ lspci -knn
>>
>>
>> poma
>>
>
> Here we go. (It is all Greek to me! :-) )
>
>> 00:00.0 Host bridge [0600]: Intel Corporation Ivy Bridge DRAM
>> Controller [8086:0154] (rev 09)
>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>> 00:01.0 PCI bridge [0604]: Intel Corporation Ivy Bridge PCI Express
>> Root Port [8086:0151] (rev 09)
>> Kernel driver in use: pcieport
>> 00:14.0 USB Controller [0c03]: Intel Corporation Panther Point USB
>> xHCI Host Controller [8086:1e31] (rev 04)
>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>> Kernel driver in use: xhci_hcd
>> 00:16.0 Communication controller [0780]: Intel Corporation Panther
>> Point MEI Controller #1 [8086:1e3a] (rev 04)
>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>> 00:1a.0 USB Controller [0c03]: Intel Corporation Panther Point USB
>> Enhanced Host Controller #2 [8086:1e2d] (rev 04)
>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>> Kernel driver in use: ehci_hcd
>> 00:1b.0 Audio device [0403]: Intel Corporation Panther Point High
>> Definition Audio Controller [8086:1e20] (rev 04)
>> Subsystem: Toshiba America Info Systems Device [1179:fb30]
>> Kernel driver in use: snd_hda_intel
>> 00:1c.0 PCI bridge [0604]: Intel Corporation Panther Point PCI Express
>> Root Port 1 [8086:1e10] (rev c4)
>> Kernel driver in use: pcieport
>> 00:1c.1 PCI bridge [0604]: Intel Corporation Panther Point PCI Express
>> Root Port 2 [8086:1e12] (rev c4)
>> Kernel driver in use: pcieport
>> 00:1c.2 PCI bridge [0604]: Intel Corporation Panther Point PCI Express
>> Root Port 3 [8086:1e14] (rev c4)
>> Kernel driver in use: pcieport
>> 00:1d.0 USB Controller [0c03]: Intel Corporation Panther Point USB
>> Enhanced Host Controller #1 [8086:1e26] (rev 04)
>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>> Kernel driver in use: ehci_hcd
>> 00:1f.0 ISA bridge [0601]: Intel Corporation Panther Point LPC
>> Controller [8086:1e59] (rev 04)
>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>> 00:1f.2 SATA controller [0106]: Intel Corporation Panther Point 6 port
>> SATA AHCI Controller [8086:1e03] (rev 04)
>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>> Kernel driver in use: ahci
>> 00:1f.3 SMBus [0c05]: Intel Corporation Panther Point SMBus Controller
>> [8086:1e22] (rev 04)
>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>> 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Device
>> [1002:6840]
>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>> Kernel driver in use: radeon
>> 01:00.1 Audio device [0403]: ATI Technologies Inc Device [1002:aa90]
>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>> Kernel driver in use: snd_hda_intel
>> 08:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd.
>> RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
>> Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:8212]
>> Kernel driver in use: rtl8192ce
>> 09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
>> RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev
>> 07)
>> Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
>> Kernel driver in use: r8169
>
> Hope it enables you to give me some insight.
>
> cheers,
>
> Rolf
>
>
This is the file - create it with your favorite text editor, as root:
/etc/modprobe.d/blacklist-rtl8192ce.conf
This is the command:
$ su -c "<TEXT EDITOR> /etc/modprobe.d/blacklist-rtl8192ce.conf"
e.g.
$ su -c "gedit /etc/modprobe.d/blacklist-rtl8192ce.conf"
Password: <ENTER HERE THE ROOT PASSWORD>
Then type the following line into the file:
blacklist rtl8192ce
Save and close.
$ su -c "init 6"
Finito.
That ***ALMOST*** works. Thanks very much. The only WiFi device that
the machine now sees is the USB device. The remaining flaw in the
ointment is that when I close the lid on the laptop, it seems to stop
seeing any available networks. When I clicking on the networking icon
it indicates "Wireless disconnected" and does not list any available
network. (Previously it indicated that the USB device was disconnected
and listed available networks under the internal device.)
I thought I might try "sudo ifup wlan0" --- no idea if that really makes
sense, but it seemed like something I could try. However it just
complains that it can't find the network "UoA-Guest-WiFi" which is
a network available when I am at the Uni. Whereas I was doing this at
home and wanted it to use my home network (called "belkin.aaa"). Dunno
if it would've worked anyway, but.
It finds the available networks OK upon boot-up. It's just after
closing and re-opening the lid that they all disappear. Can anyone give
me a recipe to tell it to find the available networks? Seems to me that
this should be do-able.
cheers,
Rolf
P. S. I can't actually work around the problem, in a shaganappi way,
without rebooting. If I unplug the WiFi dongle, plug it back in, and
then click on the network icon --> Connect to Hidden Wireless Network ->
Connection (downarrow) then I'm given a list of networks. I can then
click on belkin.aaa. It spins the wheel of death for a while, then pops
up a window saying that a password is required (although the password is
stored in the connection information). I just click on "Connect".
It usually pops up that window again, I click on "Connect" again.
Sometimes that gives me a connection, sometimes a third or forth try is
required. Eventually (so far) I get through. Not impossible to live
with, but not really satisfactory.
R.
2:06 a.m.
On 08/02/2013 12:06 AM, poma wrote:
Cut 'n' loose :)
This is an embedded device,
lspci:
Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter
[10ec:8176] (rev 01)
Kernel driver in use: rtl8192ce
- filename:
/lib/modules/$(uname-r)/kernel/drivers/net/wireless/rtlwifi/
rtl8192ce/rtl8192ce.ko
- rpm: kernel
- firmware: /usr/lib/firmware/rtlwifi/rtl8192cfw.bin
- rpm: linux-firmware
And this one is blacklisted in
/etc/modprobe.d/blacklist-rtl8192ce.conf:
blacklist rtl8192ce
And it isn't used.
Is it useful or not I leave you to consider.
Period.
This is an external usb device,
http://www.asus.com/Networking/USBN10
lsusb:
ID 0b05:1786 ASUSTek Computer, Inc. USB-N10 Wireless N dongle [Realtek
RTL8712U]
Driver=r8712u
- filename:
/usr/lib/modules/$(uname-r)/kernel/drivers/staging/rtl8712/r8712u.ko
- rpm: kernel
- firmware: /usr/lib/firmware/rtlwifi/rtl8712u.bin
- rpm: linux-firmware
OK.
You wrote that the device works under the following conditions:
- Installed kernel is 3.3.4-5.fc17.x86_64, i.e.
"kernel-3.3.4-5.fc17.x86_64.rpm" and
"kernel-devel-3.3.4-5.fc17.x86_64.rpm"
- You do not use a module that is already provided by
the kernel install itself - "r8712u.ko"
- You use the original Realtek rtl871x wireless lan driver - "8712u.ko"
downloaded[1] and compiled against the 3.3.4-5.fc17.x86_64 kernel.
In order to achieve this again, the following should be done:
- download kernel packages:
https://dl.fedoraproject.org/pub/fedora/linux/releases/17/Fedora/x86_64/o...
https://dl.fedoraproject.org/pub/fedora/linux/releases/17/Fedora/x86_64/o...
- install kernel packages as root:
# rpm -ivh kernel-3.3.4-5.fc17.x86_64.rpm --force
# rpm -ivh kernel-devel-3.3.4-5.fc17.x86_64.rpm --force
- reboot into 3.3.4-5.fc17.x86_64 kernel
- compile downloaded[1] original Realtek rtl871x wireless lan driver
against 3.3.4-5.fc17.x86_64 kernel
- install produced moudule - "8712u.ko"
To download, compile and install original Realtek module you already
know, right.
After that, the following should be done.
Because kernel already provides the appropriate module(and firmware) for
the same device - "r8712u.ko", and you intend to use compiled original
one - "8712u.ko", the first one should be blacklisted so they don't
collide.
i.e.
/etc/modprobe.d/blacklist-r8712u.conf:
blacklist r8712u
Regarding a power management to check what's engaged, kernel ring buffer
should be parsed:
$ dmesg | grep 'ACPI\|PM'
e.g. Suspend/Resume output:
PM: Preparing system for mem sleep
PM: Entering mem sleep
PM: suspend of devices complete after 1672.538 msecs
ACPI: Preparing to enter system sleep state S3
==================system suspension=================
ACPI: Low-level resume complete
ACPI: Waking up from system sleep state S3
PM: resume of devices complete after 10629.433 msecs
PM: Finishing wakeup.
e.g. Hibernate/Thaw output:
PM: Hibernation mode set to 'platform'
PM: freeze of devices complete after 1478.525 msecs
ACPI: Preparing to enter system sleep state S4
PM: Creating hibernation image:
================system hibernation==================
ACPI: Waking up from system sleep state S4
PM: restore of devices complete after 1363.236 msecs
PM: Image restored successfully.
I can only assume that you use this mechanism to achieve the system
suspend or the system hibernate,
$ dconf read /org/gnome/settings-daemon/plugins/power/lid-close-ac-action
'suspend/hibernate'
$ dconf read
/org/gnome/settings-daemon/plugins/power/lid-close-battery-action
'suspend/hibernate'
And finally, the idea that I mentioned.
Regarding losing the WiFi device after the system resume/thaw,
# yum install pm-utils
and create as root,
/etc/pm/config.d/modunload_modreload
with the following line:
SUSPEND_MODULES="8712u"
Now if you engage the system suspend as root with the following command:
# pm-suspend
kernel module "8712u" will be unloaded before system hit suspension, and
later during system resuming, kernel module "8712u" will be re-loaded.
In this way, the device should be reusable.
Will it work or not, manually or with lid-close/open, that is the question.
This method is rather obsolete, and in an ideal world it should not be
necessary at all.
One day, all kernel modules will be properly designed.
Until then.
OK I think it was really enough. :)
Godspeed.
poma
[1] Original Realtek rtl871x wireless lan driver
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=48&...
RTL819xSU_usb_linux_v2.6.6.0.20120405.zip
- rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405.tar.gz
- filename: 8712u.ko
Ref. apps.
- rpm: NetworkManager*, wpa_supplicant, network-manager-applet
"r8712u is a USB driver for RTL8712U/RTL8192SU devices, it's going to be
replaced by r92su." [1]
$ modinfo r92su
filename:
/lib/modules/3.10.4-300.fc19.x86_64/updates/wip/r92su/r92su.ko
license: GPL
author: Christian Lamparter <chunkeey(a)googlemail.com>
firmware: rtlwifi/rtl8712u.bin
alias: usb:v5A57p0291d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0E0Bp9063d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0009p21E7d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p0061d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0409p02B6d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v7392p7622d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v07AAp0051d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v050Dp845Ad*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp8174d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3325d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3310d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3341d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3340d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3339d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v04F2pAFF6d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v04F2pAFF5d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v04F2pAFF2d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0CDEp0030d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v14B2p3302d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v14B2p3301d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v14B2p3300d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p0064d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p004Cd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p0049d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p0058d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2019p4901d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2019pED18d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3306d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0E66p0015d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v06F8pE031d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1740p9605d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v7392p7612d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v07D1p3303d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v07D1p3300d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v07D1p3302d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v050Dp815Fd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3309d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3336d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3335d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3334d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3333d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3342d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3311d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v13D3p3323d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0EB0p9061d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1B75p8172d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp8192d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp8172d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp8175d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v25D4p4CABd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v25D4p4CA1d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v20F4p646Bd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1690p0752d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp5077d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v177Fp0154d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p0063d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p005Dd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p005Bd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p004Bd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p0059d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p0045d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p0057d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2019pED16d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2019pAB28d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0789p0167d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v06F8pE032d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v06F8pE034d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0E66p0016d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1740p9603d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v7392p7611d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v07D1p3306d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2001p3306d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v07AAp0047d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v050Dp11F1d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v050Dp945Ad*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0B05p1791d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0B05p1786d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1B75p8171d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v083ApC512d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v07B8p8188d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDApC512d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDApC047d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp8713d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp8712d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp8173d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp8171d*dc*dsc*dp*ic*isc*ip*in*
depends: cfg80211
vermagic: 3.10.4-300.fc19.x86_64 SMP mod_unload
parm: noht:Disable MPDU aggregation. (bool)
# modprobe -v r92su
insmod /lib/modules/3.10.4-300.fc19.x86_64/kernel/net/rfkill/rfkill.ko
insmod /lib/modules/3.10.4-300.fc19.x86_64/kernel/net/wireless/cfg80211.ko
insmod /lib/modules/3.10.4-300.fc19.x86_64/updates/wip/r92su/r92su.ko
$ dmesg -t
cfg80211: Calling CRDA to update world regulatory domain
usbcore: registered new interface driver r92su
cfg80211: World regulatory domain updated:
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain,
max_eirp)
cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
poma
[1] http://wireless.kernel.org/en/users/Drivers/rtl819x#staging_drivers
Ref.
http://www.spinics.net/lists/linux-wireless/msg105622.html
https://github.com/chunkeey/rtl8192su
https://github.com/chunkeey/rtl8192su/archive/master.zip
http://vger.kernel.org/vger-lists.html#linux-wireless
5:06 p.m.
Cut 'n' loose :)
This is an embedded device,
lspci:
Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter
[10ec:8176] (rev 01)
Kernel driver in use: rtl8192ce
- filename:
/lib/modules/$(uname-r)/kernel/drivers/net/wireless/rtlwifi/
rtl8192ce/rtl8192ce.ko
- rpm: kernel
- firmware: /usr/lib/firmware/rtlwifi/rtl8192cfw.bin
- rpm: linux-firmware
And this one is blacklisted in
/etc/modprobe.d/blacklist-rtl8192ce.conf:
blacklist rtl8192ce
And it isn't used.
Is it useful or not I leave you to consider.
Period.
This is an external usb device,
http://www.asus.com/Networking/USBN10
lsusb:
ID 0b05:1786 ASUSTek Computer, Inc. USB-N10 Wireless N dongle [Realtek
RTL8712U]
Driver=r8712u
- filename:
/usr/lib/modules/$(uname-r)/kernel/drivers/staging/rtl8712/r8712u.ko
- rpm: kernel
- firmware: /usr/lib/firmware/rtlwifi/rtl8712u.bin
- rpm: linux-firmware
OK.
You wrote that the device works under the following conditions:
- Installed kernel is 3.3.4-5.fc17.x86_64, i.e.
"kernel-3.3.4-5.fc17.x86_64.rpm" and
"kernel-devel-3.3.4-5.fc17.x86_64.rpm"
- You do not use a module that is already provided by
the kernel install itself - "r8712u.ko"
- You use the original Realtek rtl871x wireless lan driver - "8712u.ko"
downloaded[1] and compiled against the 3.3.4-5.fc17.x86_64 kernel.
In order to achieve this again, the following should be done:
- download kernel packages:
https://dl.fedoraproject.org/pub/fedora/linux/releases/17/Fedora/x86_64/o...
https://dl.fedoraproject.org/pub/fedora/linux/releases/17/Fedora/x86_64/o...
- install kernel packages as root:
# rpm -ivh kernel-3.3.4-5.fc17.x86_64.rpm --force
# rpm -ivh kernel-devel-3.3.4-5.fc17.x86_64.rpm --force
- reboot into 3.3.4-5.fc17.x86_64 kernel
- compile downloaded[1] original Realtek rtl871x wireless lan driver
against 3.3.4-5.fc17.x86_64 kernel
- install produced moudule - "8712u.ko"
To download, compile and install original Realtek module you already
know, right.
After that, the following should be done.
Because kernel already provides the appropriate module(and firmware) for
the same device - "r8712u.ko", and you intend to use compiled original
one - "8712u.ko", the first one should be blacklisted so they don't
collide.
i.e.
/etc/modprobe.d/blacklist-r8712u.conf:
blacklist r8712u
Regarding a power management to check what's engaged, kernel ring buffer
should be parsed:
$ dmesg | grep 'ACPI\|PM'
e.g. Suspend/Resume output:
PM: Preparing system for mem sleep
PM: Entering mem sleep
PM: suspend of devices complete after 1672.538 msecs
ACPI: Preparing to enter system sleep state S3
==================system suspension=================
ACPI: Low-level resume complete
ACPI: Waking up from system sleep state S3
PM: resume of devices complete after 10629.433 msecs
PM: Finishing wakeup.
e.g. Hibernate/Thaw output:
PM: Hibernation mode set to 'platform'
PM: freeze of devices complete after 1478.525 msecs
ACPI: Preparing to enter system sleep state S4
PM: Creating hibernation image:
================system hibernation==================
ACPI: Waking up from system sleep state S4
PM: restore of devices complete after 1363.236 msecs
PM: Image restored successfully.
I can only assume that you use this mechanism to achieve the system
suspend or the system hibernate,
$ dconf read /org/gnome/settings-daemon/plugins/power/lid-close-ac-action
'suspend/hibernate'
$ dconf read
/org/gnome/settings-daemon/plugins/power/lid-close-battery-action
'suspend/hibernate'
And finally, the idea that I mentioned.
Regarding losing the WiFi device after the system resume/thaw,
# yum install pm-utils
and create as root,
/etc/pm/config.d/modunload_modreload
with the following line:
SUSPEND_MODULES="8712u"
Now if you engage the system suspend as root with the following command:
# pm-suspend
kernel module "8712u" will be unloaded before system hit suspension, and
later during system resuming, kernel module "8712u" will be re-loaded.
In this way, the device should be reusable.
Will it work or not, manually or with lid-close/open, that is the question.
This method is rather obsolete, and in an ideal world it should not be
necessary at all.
One day, all kernel modules will be properly designed.
Until then.
OK I think it was really enough. :)
Godspeed.
poma
[1] Original Realtek rtl871x wireless lan driver
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=48&...
RTL819xSU_usb_linux_v2.6.6.0.20120405.zip
- rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20120405.tar.gz
- filename: 8712u.ko
Ref. apps.
- rpm: NetworkManager*, wpa_supplicant, network-manager-applet
12:25 a.m.
On 31/07/13 20:54, poma wrote:
<SNIP>
>
> [RT] That ***ALMOST*** works. Thanks very much. The only WiFi device that
> the machine now sees is the USB device. The remaining flaw in the
> ointment is that when I close the lid on the laptop, it seems to stop
> seeing any available networks. When I clicking on the networking icon
> it indicates "Wireless disconnected" and does not list any available
> network. (Previously it indicated that the USB device was disconnected
> and listed available networks under the internal device.)
>
> I thought I might try "sudo ifup wlan0" --- no idea if that really makes
> sense, but it seemed like something I could try. However it just
> complains that it can't find the network "UoA-Guest-WiFi" which is
> a network available when I am at the Uni. Whereas I was doing this at
> home and wanted it to use my home network (called "belkin.aaa"). Dunno
> if it would've worked anyway, but.
>
> It finds the available networks OK upon boot-up. It's just after
> closing and re-opening the lid that they all disappear. Can anyone give
> me a recipe to tell it to find the available networks? Seems to me that
> this should be do-able.
>
> cheers,
>
> Rolf
>
> P. S. I can't actually work around the problem, in a shaganappi way,
> without rebooting. If I unplug the WiFi dongle, plug it back in, and
> then click on the network icon --> Connect to Hidden Wireless Network ->
> Connection (downarrow) then I'm given a list of networks. I can then
> click on belkin.aaa. It spins the wheel of death for a while, then pops
> up a window saying that a password is required (although the password is
> stored in the connection information). I just click on "Connect".
> It usually pops up that window again, I click on "Connect" again.
> Sometimes that gives me a connection, sometimes a third or forth try is
> required. Eventually (so far) I get through. Not impossible to live
> with, but not really satisfactory.
>
> R.
>
[poma]
Kernel mentioned at the beginning of the thread:
3.3.4-5.fc17.x86_64
and
Probably the last official kernel for Fedora 17/EOL:
…/fedora/linux/updates/17/x86_64/kernel-3.9.10-100.fc17.x86_64.rpm
Do you notice the obvious?
At least update the existing version.
I'm pretty sure that this is a red herring. I had the device *working*
under the 3.3.4 kernel, so the aged kernel wasn't the problem. The
problem was the the device would "see" available networks on boot-up but
would no longer "see" them after going into hibernation (I *think* it's
hibernation that it goes into!).
Be that as it may: I have recently (due to a disaster that I
instigated, the details of which I will not go into) had to reinstall
the Fedora system. It now has kernel 3.9.10-etc. And thereby has
arisen a new disaster. I can no longer get the driver for the ASUS
USB-N10 to build. The "make" fails with an error (a whole mess of
output which is incomprehensible to me). With the 3.3.4 kernel the make
ran seamlessly. And yes, in case you ask, I *did* put the source of the
3.9.10 kernel into /usr/src/kernels (using yum install kernel-devel).
The name of the directory corresponds exactly to the output of uname -r.
So I kind of followed your advice --- to update to the "existing"
version --- before I received that advice. And disaster resulted. My
USB WiFi device is no longer usable at all.
[poma]
Device - built-in WiFi card, supposedly unsupported:
"08:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd.
RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)"
Is it really so:
$ modinfo
./kernel-3.9.10-100.fc17.x86_64/lib/modules/3.9.10-100.fc17.x86_64/kernel/drivers/net/wireless/rtlwifi/rtl8192ce/rtl8192ce.ko
| grep -iP '(?=.*10ec)(?=.*8176)'
alias: pci:v000010ECd00008176sv*sd*bc*sc*i*
Firmware:
./linux-firmware-20121218-0.1.gitbda53ca.fc17.noarch/lib/firmware/rtlwifi/rtl8192cfw.bin
I have no idea what you are on about in the forgoing. It is all Greek to
me. Sorry to be such a thicko, but I am one.
[poma] Once more recommendation:
# yum update
I have, as I said, just re-installed Fedora 17, and in the process was
prompted to update a brazillion packages. Which I did. Now "yum
update" produces the message "No Packages marked for Update".
[poma] I have an idea what you could try, but I need information
about the
module USB WiFi device uses, therefore c/p s'il vous plaît:
[RT] lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 0b05:1786 ASUSTek Computer, Inc. USB-N10 Wireless N dongle
[Realtek RTL8712U]
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
[RT] lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
|__ Port 1: Dev 2, If 0, Class=vend., Driver=r8712u, 480M
|__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 1, Class=HID, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 2, Class=HID, Driver=usbhid, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
For what it's worth. But as I said, I cannot get the USB WiFi device
to work ***at all*** now, so this is probably all irrelevant.
[poma] Can you confirm whether this is indeed a problem with the system
hibernation(suspend to disk) or is it actually a system
suspension(suspend to RAM).
Sorry, I have no idea. I close the lid, and the screen goes black.
Open the lid, the screen stays black. Press a key, and the lights
come back on (but wireless connections are lost. Or at least they
***were*** lost when I had wireless connections! I no longer have any
such.)
Thanks for giving this some thought. I really do appreciate your
effort. But I'm afraid that my only recourse will be to sell this
<expletive deleted> Toshiba and buy another brand which has a WiFi
device compatible with Linux. I gather that they ***do*** exist.
I will take a financial bath by so doing, but I guess that's what I have
to pay for being stupid.
cheers,
Rolf Turner
2:07 a.m.
New subject: Disable built-in WiFi card so that USB WiFi device gets used --- systemctl?
On 30.07.2013 06:51, Rolf Turner wrote:
On 30/07/13 14:45, poma wrote:
> On 30.07.2013 00:03, Rolf Turner wrote:
>> Thanks "poma" (???) and Harald. It sounds like you may have solved my
>> problem .... but I'm afraid that your advice is too cryptic for my poor
>> feeble
>> brain. Can either of you (or someone else) spell out in tedious detail
>> just
>> what I need to do? I cannot figure out whether things written in your
>> messages
>> are commands that I issue at the command line or lines that I need to
>> insert
>> into certain files. And if so, which files? I'm sure it's all obvious
>> to you guys,
>> but it leaves me floundering.
>>
>> Some specific questions:
>>
>> (1) "poma's" original posting referred to the directory
/boot/extlinux
>> and a file therein called extlinux.conf. On my system there is no
>> directory
>> "extlinux" in /boot. The only subdirectories of /boot are
"efi", "grub"
>> and
>> "grub2".
>>
>> Should I create the directory /boot/extlinux and the file
>> /boot/extlinux/extlinux.conf?
>> Or is there some other incantation that I should invoke?
>>
>> (2) Likewise the original posting refers to <drivername>. How do I
>> find/figure out
>> the *name* of the driver associated with the internal WiFi card? This
>> may sound
>> clueless, but I guess I am clueless.
>>
>> (3) I did "man 7 dracut.cmdline" and found the reference to
>> "rd.driver.blacklist"
>> but I could not fathom what it was saying.
>>
>> (4) The original posting contains:
>>> e.g.
>>> /boot/extlinux/extlinux.conf
>>> append … rd.driver.blacklist=<drivername>
>> Is the line "append … rd.driver.blacklist=<drivername>" to be
placed
>> in the file /boot/extlinux/extlinux.conf? (After I figure out what to
>> substitute
>> for "<drivername>" of course.) Are the three dots "..."
literal? Or
>> are are they a filler for something that I need to insert? If so, what
>> do I need to insert? I haven't a clue!
>>
>> (5) I have found the file /boot/grub2/grub.cfg alright. But it has a
>> header
>> saying "DO NOT EDIT THIS FILE". It goes on to say:
>>> # It is automatically generated by grub2-mkconfig using templates
>>> # from /etc/grub.d and settings from /etc/default/grub
>> So do I need to edit /etc/default/grub? Or what?
>>
>> (6) In respect of "poma's" follow-up posting: Do I create a file
>> /etc/modprobe.d/blacklist.<modulename>.conf (after having figured
>> out what "<modulename>" should be) and place in it the line:
>>
>> blacklist <modulename>
>>
>> (again after having figured out what "<modulename>" should be) ?
>>
>> (7) In /etc/modprobe.d there is already a file called
>> "blacklist.conf" in
>> which there are many many lines such as:
>>
>>> # watchdog drivers
>>> blacklist i8xx_tco
>>>
>>> # framebuffer drivers
>>> blacklist aty128fb
>>> blacklist atyfb
>>> blacklist radeonfb
>>> blacklist i810fb
>>> blacklist cirrusfb
>> .........
>>
>> Could I just put "blacklist <modulename>" into that file?
>>
>> (8) "poma" says " However OP should upgrade, anyway."
I'm sure that
>> I should. But the thought terrifies me. After all that I have read on
>> this
>> list recently about problems with Fedora 19, with fedup, with "yum
>> upgrade".
>> I have understood almost none of the discourse but it seems to indicate
>> that upgrading is essentially impossible unless you *really* know
>> what you
>> are doing. And I don't.
>>
>> Is there a simple (hah!) recipe by means of which I could upgrade? E.g.
>> could I just type
>>
>> sudo fedup
>>
>> at the command line? Or perhaps
>>
>> sudo yum upgrade
>>
>> ??? If either would work, what are the implications of using the one
>> rather
>> than the other?
>>
>> Thanks for any insight.
>>
>> cheers,
>>
>> Rolf Turner
>>
>>
> Step by step. ;)
>
> This is the hyperlink:
> https://support.mozillamessaging.com/en-US/kb/reply-above-or-below-quoted...
>
> Below quoted text, s'il vous plaît.
>
> This is the command - c/p into reply s'il vous plaît:
> $ lspci -knn
>
>
> poma
>
Here we go. (It is all Greek to me! :-) )
> 00:00.0 Host bridge [0600]: Intel Corporation Ivy Bridge DRAM
> Controller [8086:0154] (rev 09)
> Subsystem: Toshiba America Info Systems Device [1179:fb31]
> 00:01.0 PCI bridge [0604]: Intel Corporation Ivy Bridge PCI Express
> Root Port [8086:0151] (rev 09)
> Kernel driver in use: pcieport
> 00:14.0 USB Controller [0c03]: Intel Corporation Panther Point USB
> xHCI Host Controller [8086:1e31] (rev 04)
> Subsystem: Toshiba America Info Systems Device [1179:fb31]
> Kernel driver in use: xhci_hcd
> 00:16.0 Communication controller [0780]: Intel Corporation Panther
> Point MEI Controller #1 [8086:1e3a] (rev 04)
> Subsystem: Toshiba America Info Systems Device [1179:fb31]
> 00:1a.0 USB Controller [0c03]: Intel Corporation Panther Point USB
> Enhanced Host Controller #2 [8086:1e2d] (rev 04)
> Subsystem: Toshiba America Info Systems Device [1179:fb31]
> Kernel driver in use: ehci_hcd
> 00:1b.0 Audio device [0403]: Intel Corporation Panther Point High
> Definition Audio Controller [8086:1e20] (rev 04)
> Subsystem: Toshiba America Info Systems Device [1179:fb30]
> Kernel driver in use: snd_hda_intel
> 00:1c.0 PCI bridge [0604]: Intel Corporation Panther Point PCI Express
> Root Port 1 [8086:1e10] (rev c4)
> Kernel driver in use: pcieport
> 00:1c.1 PCI bridge [0604]: Intel Corporation Panther Point PCI Express
> Root Port 2 [8086:1e12] (rev c4)
> Kernel driver in use: pcieport
> 00:1c.2 PCI bridge [0604]: Intel Corporation Panther Point PCI Express
> Root Port 3 [8086:1e14] (rev c4)
> Kernel driver in use: pcieport
> 00:1d.0 USB Controller [0c03]: Intel Corporation Panther Point USB
> Enhanced Host Controller #1 [8086:1e26] (rev 04)
> Subsystem: Toshiba America Info Systems Device [1179:fb31]
> Kernel driver in use: ehci_hcd
> 00:1f.0 ISA bridge [0601]: Intel Corporation Panther Point LPC
> Controller [8086:1e59] (rev 04)
> Subsystem: Toshiba America Info Systems Device [1179:fb31]
> 00:1f.2 SATA controller [0106]: Intel Corporation Panther Point 6 port
> SATA AHCI Controller [8086:1e03] (rev 04)
> Subsystem: Toshiba America Info Systems Device [1179:fb31]
> Kernel driver in use: ahci
> 00:1f.3 SMBus [0c05]: Intel Corporation Panther Point SMBus Controller
> [8086:1e22] (rev 04)
> Subsystem: Toshiba America Info Systems Device [1179:fb31]
> 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Device
> [1002:6840]
> Subsystem: Toshiba America Info Systems Device [1179:fb31]
> Kernel driver in use: radeon
> 01:00.1 Audio device [0403]: ATI Technologies Inc Device [1002:aa90]
> Subsystem: Toshiba America Info Systems Device [1179:fb31]
> Kernel driver in use: snd_hda_intel
> 08:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd.
> RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
> Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:8212]
> Kernel driver in use: rtl8192ce
> 09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
> RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev
> 07)
> Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
> Kernel driver in use: r8169
Hope it enables you to give me some insight.
cheers,
Rolf
This is the file - create it with your favorite text editor, as root:
/etc/modprobe.d/blacklist-rtl8192ce.conf
This is the command:
$ su -c "<TEXT EDITOR> /etc/modprobe.d/blacklist-rtl8192ce.conf"
e.g.
$ su -c "gedit /etc/modprobe.d/blacklist-rtl8192ce.conf"
Password: <ENTER HERE THE ROOT PASSWORD>
Then type the following line into the file:
blacklist rtl8192ce
Save and close.
$ su -c "init 6"
Finito.
poma
11:51 p.m.
New subject: Disable built-in WiFi card so that USB WiFi device gets used --- systemctl?
On 30/07/13 14:45, poma wrote:
On 30.07.2013 00:03, Rolf Turner wrote:
> Thanks "poma" (???) and Harald. It sounds like you may have solved my
> problem .... but I'm afraid that your advice is too cryptic for my poor
> feeble
> brain. Can either of you (or someone else) spell out in tedious detail
> just
> what I need to do? I cannot figure out whether things written in your
> messages
> are commands that I issue at the command line or lines that I need to
> insert
> into certain files. And if so, which files? I'm sure it's all obvious
> to you guys,
> but it leaves me floundering.
>
> Some specific questions:
>
> (1) "poma's" original posting referred to the directory /boot/extlinux
> and a file therein called extlinux.conf. On my system there is no
> directory
> "extlinux" in /boot. The only subdirectories of /boot are "efi",
"grub"
> and
> "grub2".
>
> Should I create the directory /boot/extlinux and the file
> /boot/extlinux/extlinux.conf?
> Or is there some other incantation that I should invoke?
>
> (2) Likewise the original posting refers to <drivername>. How do I
> find/figure out
> the *name* of the driver associated with the internal WiFi card? This
> may sound
> clueless, but I guess I am clueless.
>
> (3) I did "man 7 dracut.cmdline" and found the reference to
> "rd.driver.blacklist"
> but I could not fathom what it was saying.
>
> (4) The original posting contains:
>> e.g.
>> /boot/extlinux/extlinux.conf
>> append … rd.driver.blacklist=<drivername>
> Is the line "append … rd.driver.blacklist=<drivername>" to be placed
> in the file /boot/extlinux/extlinux.conf? (After I figure out what to
> substitute
> for "<drivername>" of course.) Are the three dots "..."
literal? Or
> are are they a filler for something that I need to insert? If so, what
> do I need to insert? I haven't a clue!
>
> (5) I have found the file /boot/grub2/grub.cfg alright. But it has a
> header
> saying "DO NOT EDIT THIS FILE". It goes on to say:
>> # It is automatically generated by grub2-mkconfig using templates
>> # from /etc/grub.d and settings from /etc/default/grub
> So do I need to edit /etc/default/grub? Or what?
>
> (6) In respect of "poma's" follow-up posting: Do I create a file
> /etc/modprobe.d/blacklist.<modulename>.conf (after having figured
> out what "<modulename>" should be) and place in it the line:
>
> blacklist <modulename>
>
> (again after having figured out what "<modulename>" should be) ?
>
> (7) In /etc/modprobe.d there is already a file called "blacklist.conf" in
> which there are many many lines such as:
>
>> # watchdog drivers
>> blacklist i8xx_tco
>>
>> # framebuffer drivers
>> blacklist aty128fb
>> blacklist atyfb
>> blacklist radeonfb
>> blacklist i810fb
>> blacklist cirrusfb
> .........
>
> Could I just put "blacklist <modulename>" into that file?
>
> (8) "poma" says " However OP should upgrade, anyway." I'm
sure that
> I should. But the thought terrifies me. After all that I have read on
> this
> list recently about problems with Fedora 19, with fedup, with "yum
> upgrade".
> I have understood almost none of the discourse but it seems to indicate
> that upgrading is essentially impossible unless you *really* know what you
> are doing. And I don't.
>
> Is there a simple (hah!) recipe by means of which I could upgrade? E.g.
> could I just type
>
> sudo fedup
>
> at the command line? Or perhaps
>
> sudo yum upgrade
>
> ??? If either would work, what are the implications of using the one
> rather
> than the other?
>
> Thanks for any insight.
>
> cheers,
>
> Rolf Turner
>
>
Step by step. ;)
This is the hyperlink:
https://support.mozillamessaging.com/en-US/kb/reply-above-or-below-quoted...
Below quoted text, s'il vous plaît.
This is the command - c/p into reply s'il vous plaît:
$ lspci -knn
poma
Here we go. (It is all Greek to me! :-) )
00:00.0 Host bridge [0600]: Intel Corporation Ivy Bridge DRAM
Controller [8086:0154] (rev 09)
Subsystem: Toshiba America Info Systems Device [1179:fb31]
00:01.0 PCI bridge [0604]: Intel Corporation Ivy Bridge PCI Express
Root Port [8086:0151] (rev 09)
Kernel driver in use: pcieport
00:14.0 USB Controller [0c03]: Intel Corporation Panther Point USB
xHCI Host Controller [8086:1e31] (rev 04)
Subsystem: Toshiba America Info Systems Device [1179:fb31]
Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation Panther
Point MEI Controller #1 [8086:1e3a] (rev 04)
Subsystem: Toshiba America Info Systems Device [1179:fb31]
00:1a.0 USB Controller [0c03]: Intel Corporation Panther Point USB
Enhanced Host Controller #2 [8086:1e2d] (rev 04)
Subsystem: Toshiba America Info Systems Device [1179:fb31]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation Panther Point High
Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Toshiba America Info Systems Device [1179:fb30]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation Panther Point PCI Express
Root Port 1 [8086:1e10] (rev c4)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation Panther Point PCI Express
Root Port 2 [8086:1e12] (rev c4)
Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation Panther Point PCI Express
Root Port 3 [8086:1e14] (rev c4)
Kernel driver in use: pcieport
00:1d.0 USB Controller [0c03]: Intel Corporation Panther Point USB
Enhanced Host Controller #1 [8086:1e26] (rev 04)
Subsystem: Toshiba America Info Systems Device [1179:fb31]
Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation Panther Point LPC
Controller [8086:1e59] (rev 04)
Subsystem: Toshiba America Info Systems Device [1179:fb31]
00:1f.2 SATA controller [0106]: Intel Corporation Panther Point 6 port
SATA AHCI Controller [8086:1e03] (rev 04)
Subsystem: Toshiba America Info Systems Device [1179:fb31]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation Panther Point SMBus Controller
[8086:1e22] (rev 04)
Subsystem: Toshiba America Info Systems Device [1179:fb31]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Device
[1002:6840]
Subsystem: Toshiba America Info Systems Device [1179:fb31]
Kernel driver in use: radeon
01:00.1 Audio device [0403]: ATI Technologies Inc Device [1002:aa90]
Subsystem: Toshiba America Info Systems Device [1179:fb31]
Kernel driver in use: snd_hda_intel
08:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd.
RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:8212]
Kernel driver in use: rtl8192ce
09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 07)
Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
Kernel driver in use: r8169
Hope it enables you to give me some insight.
cheers,
Rolf
9:45 p.m.
New subject: Disable built-in WiFi card so that USB WiFi device gets used --- systemctl?
On 30.07.2013 00:03, Rolf Turner wrote:
Thanks "poma" (???) and Harald. It sounds like you may have solved my
problem .... but I'm afraid that your advice is too cryptic for my poor
feeble
brain. Can either of you (or someone else) spell out in tedious detail
just
what I need to do? I cannot figure out whether things written in your
messages
are commands that I issue at the command line or lines that I need to
insert
into certain files. And if so, which files? I'm sure it's all obvious
to you guys,
but it leaves me floundering.
Some specific questions:
(1) "poma's" original posting referred to the directory /boot/extlinux
and a file therein called extlinux.conf. On my system there is no
directory
"extlinux" in /boot. The only subdirectories of /boot are "efi",
"grub"
and
"grub2".
Should I create the directory /boot/extlinux and the file
/boot/extlinux/extlinux.conf?
Or is there some other incantation that I should invoke?
(2) Likewise the original posting refers to <drivername>. How do I
find/figure out
the *name* of the driver associated with the internal WiFi card? This
may sound
clueless, but I guess I am clueless.
(3) I did "man 7 dracut.cmdline" and found the reference to
"rd.driver.blacklist"
but I could not fathom what it was saying.
(4) The original posting contains:
> e.g.
> /boot/extlinux/extlinux.conf
> append … rd.driver.blacklist=<drivername>
Is the line "append … rd.driver.blacklist=<drivername>" to be placed
in the file /boot/extlinux/extlinux.conf? (After I figure out what to
substitute
for "<drivername>" of course.) Are the three dots "..."
literal? Or
are are they a filler for something that I need to insert? If so, what
do I need to insert? I haven't a clue!
(5) I have found the file /boot/grub2/grub.cfg alright. But it has a
header
saying "DO NOT EDIT THIS FILE". It goes on to say:
> # It is automatically generated by grub2-mkconfig using templates
> # from /etc/grub.d and settings from /etc/default/grub
So do I need to edit /etc/default/grub? Or what?
(6) In respect of "poma's" follow-up posting: Do I create a file
/etc/modprobe.d/blacklist.<modulename>.conf (after having figured
out what "<modulename>" should be) and place in it the line:
blacklist <modulename>
(again after having figured out what "<modulename>" should be) ?
(7) In /etc/modprobe.d there is already a file called "blacklist.conf" in
which there are many many lines such as:
> # watchdog drivers
> blacklist i8xx_tco
>
> # framebuffer drivers
> blacklist aty128fb
> blacklist atyfb
> blacklist radeonfb
> blacklist i810fb
> blacklist cirrusfb
.........
Could I just put "blacklist <modulename>" into that file?
(8) "poma" says " However OP should upgrade, anyway." I'm sure
that
I should. But the thought terrifies me. After all that I have read on
this
list recently about problems with Fedora 19, with fedup, with "yum
upgrade".
I have understood almost none of the discourse but it seems to indicate
that upgrading is essentially impossible unless you *really* know what you
are doing. And I don't.
Is there a simple (hah!) recipe by means of which I could upgrade? E.g.
could I just type
sudo fedup
at the command line? Or perhaps
sudo yum upgrade
??? If either would work, what are the implications of using the one
rather
than the other?
Thanks for any insight.
cheers,
Rolf Turner
Step by step. ;)
This is the hyperlink:
https://support.mozillamessaging.com/en-US/kb/reply-above-or-below-quoted...
Below quoted text, s'il vous plaît.
This is the command - c/p into reply s'il vous plaît:
$ lspci -knn
poma
10:52 a.m.
New subject: Disable built-in WiFi card so that USB WiFi device gets used --- systemctl?
On 29.07.2013 09:47, Harald Hoyer wrote:
On 07/29/2013 02:28 AM, poma wrote:
> On 29.07.2013 02:01, Rolf Turner wrote:
> …
>> (b) Would it be possible to disable/mask the internal WiFi card but
>> leave the USB WiFi device
>> available, so that I can actually get a WiFi connection?
> …
>>> I am running Fedora 17; output of "uname -a" is:
>>>
>>>> Linux localhost.localdomain 3.3.4-5.fc17.x86_64 #1 SMP Mon May 7
>>>> 17:29:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> Thanks for any help that anyone can give me.
>>
>
> https://lists.fedoraproject.org/pipermail/announce/2013-July/003169.html
>
> BIOS settings, NetworkManager?
>
> on Fedora 19,
> man 7 dracut.cmdline - rd.driver.blacklist
>
> e.g.
> /boot/extlinux/extlinux.conf
> append … rd.driver.blacklist=<drivername>
>
> /boot/grub2/grub.cfg
> linux … rd.driver.blacklist=<drivername>
>
>
> poma
>
That would disable it only in the initramfs.
True, thank you master Yoda.
Therefore abovementioned is for e.g. 'nouveau',
plus
/etc/modprobe.d/blacklist-<modulename>.conf
blacklist <modulename>
which should be sufficient for OP's case.
man 5 modprobe.conf
man 5 modprobe.d
And there is a potential problem - one/module-to-many/devices.
However OP should upgrade, anyway.
Regarding terminology, there is a discrepancy in naming scheme -
(kernel) module vs driver.
Where from come this le chauffeur?
poma
2:47 a.m.
New subject: Disable built-in WiFi card so that USB WiFi device gets used --- systemctl?
On 07/29/2013 02:28 AM, poma wrote:
On 29.07.2013 02:01, Rolf Turner wrote:
…
> (b) Would it be possible to disable/mask the internal WiFi card but
> leave the USB WiFi device
> available, so that I can actually get a WiFi connection?
…
>> I am running Fedora 17; output of "uname -a" is:
>>
>>> Linux localhost.localdomain 3.3.4-5.fc17.x86_64 #1 SMP Mon May 7
>>> 17:29:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>>
>> Thanks for any help that anyone can give me.
>
https://lists.fedoraproject.org/pipermail/announce/2013-July/003169.html
BIOS settings, NetworkManager?
on Fedora 19,
man 7 dracut.cmdline - rd.driver.blacklist
e.g.
/boot/extlinux/extlinux.conf
append … rd.driver.blacklist=<drivername>
/boot/grub2/grub.cfg
linux … rd.driver.blacklist=<drivername>
poma
That would disable it only in the initramfs.
11:15 p.m.
On 07/27/2013 01:42 PM, Rolf Turner wrote:
Is there any way to "disable" the (non-functional) built-in WiFi card so
that the laptop will
*not* try to use it but will rather go straight to the (functional) USB
device? I Googled around
a bit and found some instructions for disabling the built-in WiFi card
under Ubuntu, but
these instruction did not (as far as I could tell) mesh with the Fedora
system that I am
running. Can anyone tell me how to do what I want under Fedora?
I have an earlier model, the L350. There's a switch on the front that
turns the WiFi card on and off. Have you checked to see if there's one
on yours?
7:28 p.m.
New subject: Disable built-in WiFi card so that USB WiFi device gets used --- systemctl?
On 29.07.2013 02:01, Rolf Turner wrote:
…
(b) Would it be possible to disable/mask the internal WiFi card
but
leave the USB WiFi device
available, so that I can actually get a WiFi connection?
…
> I am running Fedora 17; output of "uname -a" is:
>
>> Linux localhost.localdomain 3.3.4-5.fc17.x86_64 #1 SMP Mon May 7
>> 17:29:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>
> Thanks for any help that anyone can give me.
https://lists.fedoraproject.org/pipermail/announce/2013-July/003169.html
BIOS settings, NetworkManager?
on Fedora 19,
man 7 dracut.cmdline - rd.driver.blacklist
e.g.
/boot/extlinux/extlinux.conf
append … rd.driver.blacklist=<drivername>
/boot/grub2/grub.cfg
linux … rd.driver.blacklist=<drivername>
poma
11:25 p.m.
On 28/07/13 16:15, Joe Zeff wrote:
On 07/27/2013 01:42 PM, Rolf Turner wrote:
>
> Is there any way to "disable" the (non-functional) built-in WiFi card so
> that the laptop will
> *not* try to use it but will rather go straight to the (functional) USB
> device? I Googled around
> a bit and found some instructions for disabling the built-in WiFi card
> under Ubuntu, but
> these instruction did not (as far as I could tell) mesh with the Fedora
> system that I am
> running. Can anyone tell me how to do what I want under Fedora?
I have an earlier model, the L350. There's a switch on the front that
turns the WiFi card on and off. Have you checked to see if there's
one on yours?
Just checked; as far as I can see, the answer is no; there is no such
switch.
cheers,
Rolf Turner
3:54 a.m.
On 31.07.2013 00:17, Rolf Turner wrote:
On 30/07/13 19:07, poma wrote:
> On 30.07.2013 06:51, Rolf Turner wrote:
>> On 30/07/13 14:45, poma wrote:
>>> On 30.07.2013 00:03, Rolf Turner wrote:
>>>> Thanks "poma" (???) and Harald. It sounds like you may have
solved my
>>>> problem .... but I'm afraid that your advice is too cryptic for my
>>>> poor
>>>> feeble
>>>> brain. Can either of you (or someone else) spell out in tedious
>>>> detail
>>>> just
>>>> what I need to do? I cannot figure out whether things written in your
>>>> messages
>>>> are commands that I issue at the command line or lines that I need to
>>>> insert
>>>> into certain files. And if so, which files? I'm sure it's all
>>>> obvious
>>>> to you guys,
>>>> but it leaves me floundering.
>>>>
>>>> Some specific questions:
>>>>
>>>> (1) "poma's" original posting referred to the directory
/boot/extlinux
>>>> and a file therein called extlinux.conf. On my system there is no
>>>> directory
>>>> "extlinux" in /boot. The only subdirectories of /boot are
"efi",
>>>> "grub"
>>>> and
>>>> "grub2".
>>>>
>>>> Should I create the directory /boot/extlinux and the file
>>>> /boot/extlinux/extlinux.conf?
>>>> Or is there some other incantation that I should invoke?
>>>>
>>>> (2) Likewise the original posting refers to <drivername>. How do I
>>>> find/figure out
>>>> the *name* of the driver associated with the internal WiFi card? This
>>>> may sound
>>>> clueless, but I guess I am clueless.
>>>>
>>>> (3) I did "man 7 dracut.cmdline" and found the reference to
>>>> "rd.driver.blacklist"
>>>> but I could not fathom what it was saying.
>>>>
>>>> (4) The original posting contains:
>>>>> e.g.
>>>>> /boot/extlinux/extlinux.conf
>>>>> append … rd.driver.blacklist=<drivername>
>>>> Is the line "append … rd.driver.blacklist=<drivername>"
to be placed
>>>> in the file /boot/extlinux/extlinux.conf? (After I figure out what to
>>>> substitute
>>>> for "<drivername>" of course.) Are the three dots
"..." literal? Or
>>>> are are they a filler for something that I need to insert? If so,
>>>> what
>>>> do I need to insert? I haven't a clue!
>>>>
>>>> (5) I have found the file /boot/grub2/grub.cfg alright. But it has a
>>>> header
>>>> saying "DO NOT EDIT THIS FILE". It goes on to say:
>>>>> # It is automatically generated by grub2-mkconfig using templates
>>>>> # from /etc/grub.d and settings from /etc/default/grub
>>>> So do I need to edit /etc/default/grub? Or what?
>>>>
>>>> (6) In respect of "poma's" follow-up posting: Do I create
a file
>>>> /etc/modprobe.d/blacklist.<modulename>.conf (after having figured
>>>> out what "<modulename>" should be) and place in it the
line:
>>>>
>>>> blacklist <modulename>
>>>>
>>>> (again after having figured out what "<modulename>"
should be) ?
>>>>
>>>> (7) In /etc/modprobe.d there is already a file called
>>>> "blacklist.conf" in
>>>> which there are many many lines such as:
>>>>
>>>>> # watchdog drivers
>>>>> blacklist i8xx_tco
>>>>>
>>>>> # framebuffer drivers
>>>>> blacklist aty128fb
>>>>> blacklist atyfb
>>>>> blacklist radeonfb
>>>>> blacklist i810fb
>>>>> blacklist cirrusfb
>>>> .........
>>>>
>>>> Could I just put "blacklist <modulename>" into that
file?
>>>>
>>>> (8) "poma" says " However OP should upgrade, anyway."
I'm sure that
>>>> I should. But the thought terrifies me. After all that I have
>>>> read on
>>>> this
>>>> list recently about problems with Fedora 19, with fedup, with "yum
>>>> upgrade".
>>>> I have understood almost none of the discourse but it seems to
>>>> indicate
>>>> that upgrading is essentially impossible unless you *really* know
>>>> what you
>>>> are doing. And I don't.
>>>>
>>>> Is there a simple (hah!) recipe by means of which I could upgrade?
>>>> E.g.
>>>> could I just type
>>>>
>>>> sudo fedup
>>>>
>>>> at the command line? Or perhaps
>>>>
>>>> sudo yum upgrade
>>>>
>>>> ??? If either would work, what are the implications of using the one
>>>> rather
>>>> than the other?
>>>>
>>>> Thanks for any insight.
>>>>
>>>> cheers,
>>>>
>>>> Rolf Turner
>>>>
>>>>
>>> Step by step. ;)
>>>
>>> This is the hyperlink:
>>>
https://support.mozillamessaging.com/en-US/kb/reply-above-or-below-quoted...
>>>
>>>
>>> Below quoted text, s'il vous plaît.
>>>
>>> This is the command - c/p into reply s'il vous plaît:
>>> $ lspci -knn
>>>
>>>
>>> poma
>>>
>>
>> Here we go. (It is all Greek to me! :-) )
>>
>>> 00:00.0 Host bridge [0600]: Intel Corporation Ivy Bridge DRAM
>>> Controller [8086:0154] (rev 09)
>>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>>> 00:01.0 PCI bridge [0604]: Intel Corporation Ivy Bridge PCI Express
>>> Root Port [8086:0151] (rev 09)
>>> Kernel driver in use: pcieport
>>> 00:14.0 USB Controller [0c03]: Intel Corporation Panther Point USB
>>> xHCI Host Controller [8086:1e31] (rev 04)
>>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>>> Kernel driver in use: xhci_hcd
>>> 00:16.0 Communication controller [0780]: Intel Corporation Panther
>>> Point MEI Controller #1 [8086:1e3a] (rev 04)
>>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>>> 00:1a.0 USB Controller [0c03]: Intel Corporation Panther Point USB
>>> Enhanced Host Controller #2 [8086:1e2d] (rev 04)
>>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>>> Kernel driver in use: ehci_hcd
>>> 00:1b.0 Audio device [0403]: Intel Corporation Panther Point High
>>> Definition Audio Controller [8086:1e20] (rev 04)
>>> Subsystem: Toshiba America Info Systems Device [1179:fb30]
>>> Kernel driver in use: snd_hda_intel
>>> 00:1c.0 PCI bridge [0604]: Intel Corporation Panther Point PCI Express
>>> Root Port 1 [8086:1e10] (rev c4)
>>> Kernel driver in use: pcieport
>>> 00:1c.1 PCI bridge [0604]: Intel Corporation Panther Point PCI Express
>>> Root Port 2 [8086:1e12] (rev c4)
>>> Kernel driver in use: pcieport
>>> 00:1c.2 PCI bridge [0604]: Intel Corporation Panther Point PCI Express
>>> Root Port 3 [8086:1e14] (rev c4)
>>> Kernel driver in use: pcieport
>>> 00:1d.0 USB Controller [0c03]: Intel Corporation Panther Point USB
>>> Enhanced Host Controller #1 [8086:1e26] (rev 04)
>>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>>> Kernel driver in use: ehci_hcd
>>> 00:1f.0 ISA bridge [0601]: Intel Corporation Panther Point LPC
>>> Controller [8086:1e59] (rev 04)
>>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>>> 00:1f.2 SATA controller [0106]: Intel Corporation Panther Point 6 port
>>> SATA AHCI Controller [8086:1e03] (rev 04)
>>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>>> Kernel driver in use: ahci
>>> 00:1f.3 SMBus [0c05]: Intel Corporation Panther Point SMBus Controller
>>> [8086:1e22] (rev 04)
>>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>>> 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Device
>>> [1002:6840]
>>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>>> Kernel driver in use: radeon
>>> 01:00.1 Audio device [0403]: ATI Technologies Inc Device [1002:aa90]
>>> Subsystem: Toshiba America Info Systems Device [1179:fb31]
>>> Kernel driver in use: snd_hda_intel
>>> 08:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd.
>>> RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
>>> Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:8212]
>>> Kernel driver in use: rtl8192ce
>>> 09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
>>> RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev
>>> 07)
>>> Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
>>> Kernel driver in use: r8169
>>
>> Hope it enables you to give me some insight.
>>
>> cheers,
>>
>> Rolf
>>
>>
>
> This is the file - create it with your favorite text editor, as root:
> /etc/modprobe.d/blacklist-rtl8192ce.conf
>
> This is the command:
> $ su -c "<TEXT EDITOR> /etc/modprobe.d/blacklist-rtl8192ce.conf"
>
> e.g.
> $ su -c "gedit /etc/modprobe.d/blacklist-rtl8192ce.conf"
> Password: <ENTER HERE THE ROOT PASSWORD>
>
> Then type the following line into the file:
> blacklist rtl8192ce
>
> Save and close.
> $ su -c "init 6"
>
> Finito.
That ***ALMOST*** works. Thanks very much. The only WiFi device that
the machine now sees is the USB device. The remaining flaw in the
ointment is that when I close the lid on the laptop, it seems to stop
seeing any available networks. When I clicking on the networking icon
it indicates "Wireless disconnected" and does not list any available
network. (Previously it indicated that the USB device was disconnected
and listed available networks under the internal device.)
I thought I might try "sudo ifup wlan0" --- no idea if that really makes
sense, but it seemed like something I could try. However it just
complains that it can't find the network "UoA-Guest-WiFi" which is
a network available when I am at the Uni. Whereas I was doing this at
home and wanted it to use my home network (called "belkin.aaa"). Dunno
if it would've worked anyway, but.
It finds the available networks OK upon boot-up. It's just after
closing and re-opening the lid that they all disappear. Can anyone give
me a recipe to tell it to find the available networks? Seems to me that
this should be do-able.
cheers,
Rolf
P. S. I can't actually work around the problem, in a shaganappi way,
without rebooting. If I unplug the WiFi dongle, plug it back in, and
then click on the network icon --> Connect to Hidden Wireless Network ->
Connection (downarrow) then I'm given a list of networks. I can then
click on belkin.aaa. It spins the wheel of death for a while, then pops
up a window saying that a password is required (although the password is
stored in the connection information). I just click on "Connect".
It usually pops up that window again, I click on "Connect" again.
Sometimes that gives me a connection, sometimes a third or forth try is
required. Eventually (so far) I get through. Not impossible to live
with, but not really satisfactory.
R.
Kernel mentioned at the beginning of the thread:
3.3.4-5.fc17.x86_64
and
Probably the last official kernel for Fedora 17/EOL:
…/fedora/linux/updates/17/x86_64/kernel-3.9.10-100.fc17.x86_64.rpm
Do you notice the obvious?
At least update the existing version.
Device - built-in WiFi card, supposedly unsupported:
"08:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd.
RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)"
Is it really so:
$ modinfo
./kernel-3.9.10-100.fc17.x86_64/lib/modules/3.9.10-100.fc17.x86_64/kernel/drivers/net/wireless/rtlwifi/rtl8192ce/rtl8192ce.ko
| grep -iP '(?=.*10ec)(?=.*8176)'
alias: pci:v000010ECd00008176sv*sd*bc*sc*i*
Firmware:
./linux-firmware-20121218-0.1.gitbda53ca.fc17.noarch/lib/firmware/rtlwifi/rtl8192cfw.bin
Once more recommendation:
# yum update
I have an idea what you could try, but I need information about the
module USB WiFi device uses, therefore c/p s'il vous plaît:
$ lsusb
$ lsusb -t
Can you confirm whether this is indeed a problem with the system
hibernation(suspend to disk) or is it actually a system
suspension(suspend to RAM).
poma
5:03 p.m.
New subject: Disable built-in WiFi card so that USB WiFi device gets used --- systemctl?
Thanks "poma" (???) and Harald. It sounds like you may have solved my
problem .... but I'm afraid that your advice is too cryptic for my poor
feeble
brain. Can either of you (or someone else) spell out in tedious detail just
what I need to do? I cannot figure out whether things written in your
messages
are commands that I issue at the command line or lines that I need to insert
into certain files. And if so, which files? I'm sure it's all obvious
to you guys,
but it leaves me floundering.
Some specific questions:
(1) "poma's" original posting referred to the directory /boot/extlinux
and a file therein called extlinux.conf. On my system there is no directory
"extlinux" in /boot. The only subdirectories of /boot are "efi",
"grub" and
"grub2".
Should I create the directory /boot/extlinux and the file
/boot/extlinux/extlinux.conf?
Or is there some other incantation that I should invoke?
(2) Likewise the original posting refers to <drivername>. How do I
find/figure out
the *name* of the driver associated with the internal WiFi card? This
may sound
clueless, but I guess I am clueless.
(3) I did "man 7 dracut.cmdline" and found the reference to
"rd.driver.blacklist"
but I could not fathom what it was saying.
(4) The original posting contains:
e.g.
/boot/extlinux/extlinux.conf
append … rd.driver.blacklist=<drivername>
Is the line "append …
rd.driver.blacklist=<drivername>" to be placed
in the file /boot/extlinux/extlinux.conf? (After I figure out what to
substitute
for "<drivername>" of course.) Are the three dots "..." literal?
Or
are are they a filler for something that I need to insert? If so, what
do I need to insert? I haven't a clue!
(5) I have found the file /boot/grub2/grub.cfg alright. But it has a header
saying "DO NOT EDIT THIS FILE". It goes on to say:
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
So do I need to edit /etc/default/grub? Or what?
(6) In respect of "poma's" follow-up posting: Do I create a file
/etc/modprobe.d/blacklist.<modulename>.conf (after having figured
out what "<modulename>" should be) and place in it the line:
blacklist <modulename>
(again after having figured out what "<modulename>" should be) ?
(7) In /etc/modprobe.d there is already a file called "blacklist.conf" in
which there are many many lines such as:
# watchdog drivers
blacklist i8xx_tco
# framebuffer drivers
blacklist aty128fb
blacklist atyfb
blacklist radeonfb
blacklist i810fb
blacklist cirrusfb
.........
Could I just put "blacklist <modulename>" into that file?
(8) "poma" says " However OP should upgrade, anyway." I'm sure
that
I should. But the thought terrifies me. After all that I have read on this
list recently about problems with Fedora 19, with fedup, with "yum upgrade".
I have understood almost none of the discourse but it seems to indicate
that upgrading is essentially impossible unless you *really* know what you
are doing. And I don't.
Is there a simple (hah!) recipe by means of which I could upgrade? E.g.
could I just type
sudo fedup
at the command line? Or perhaps
sudo yum upgrade
??? If either would work, what are the implications of using the one rather
than the other?
Thanks for any insight.
cheers,
Rolf Turner
On 30/07/13 03:52, poma wrote:
On 29.07.2013 09:47, Harald Hoyer wrote:
> On 07/29/2013 02:28 AM, poma wrote:
>> On 29.07.2013 02:01, Rolf Turner wrote:
>> …
>>> (b) Would it be possible to disable/mask the internal WiFi card but
>>> leave the USB WiFi device
>>> available, so that I can actually get a WiFi connection?
>> …
>>>> I am running Fedora 17; output of "uname -a" is:
>>>>
>>>>> Linux localhost.localdomain 3.3.4-5.fc17.x86_64 #1 SMP Mon May 7
>>>>> 17:29:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>>>> Thanks for any help that anyone can give me.
>> https://lists.fedoraproject.org/pipermail/announce/2013-July/003169.html
>>
>> BIOS settings, NetworkManager?
>>
>> on Fedora 19,
>> man 7 dracut.cmdline - rd.driver.blacklist
>>
>> e.g.
>> /boot/extlinux/extlinux.conf
>> append … rd.driver.blacklist=<drivername>
>>
>> /boot/grub2/grub.cfg
>> linux … rd.driver.blacklist=<drivername>
>>
>>
>> poma
>>
> That would disable it only in the initramfs.
>
True, thank you master Yoda.
Therefore abovementioned is for e.g. 'nouveau',
plus
/etc/modprobe.d/blacklist-<modulename>.conf
blacklist <modulename>
which should be sufficient for OP's case.
man 5 modprobe.conf
man 5 modprobe.d
And there is a potential problem - one/module-to-many/devices.
However OP should upgrade, anyway.
Regarding terminology, there is a discrepancy in naming scheme -
(kernel) module vs driver.
Where from come this le chauffeur?
poma
3925
days inactive
3932
days old
15 comments
4 participants
participants (4)
-
Harald Hoyer -
Joe Zeff -
poma -
Rolf Turner