Legal conundrum. Media cartels want their profits back, crackdown ensues.
Piratebay ftw.
On Wed, Nov 22, 2017 at 1:09 PM, Michael wrote:
>
> I've been living where I didn't need kodi but moved a couple of days ago.
> Where did tvaddons go?
> --
> :-)~MIKE~(-:
>
> ---
well it is the same distro different version. Do you think upgrading the
desktop will do amything?
On Wed, Nov 22, 2017 at 9:42 PM, Michael wrote:
> well dang! I got the same card working in my tower though.
>
> On Wed, Nov 22, 2017 at 9:40 PM, James Mcphee wrote:
>
>> [ 15.881957] ieee80211
well dang! I got the same card working in my tower though.
On Wed, Nov 22, 2017 at 9:40 PM, James Mcphee wrote:
> [ 15.881957] ieee80211 phy0: rt2800_init_eeprom: Error - Invalid RF
> chipset 0x5362 detected
> says it hates your driver
>
> probably should check the forums of whatever distro y
[ 15.881957] ieee80211 phy0: rt2800_init_eeprom: Error - Invalid RF
chipset 0x5362 detected
says it hates your driver
probably should check the forums of whatever distro you're using for that
device to see if anyone else has problems. a google of the device name as
it shows in lspci shows lots
~ $ lsmod |grep 2800pci
rt2800pci 13606 0
rt2800mmio 20986 1 rt2800pci
rt2800lib 89076 2 rt2800pci,rt2800mmio
rt2x00pci 13287 1 rt2800pci
rt2x00mmio 13603 2 rt2800pci,rt2800mmio
rt2x00lib 55307 5
rt2x00pci,rt2800lib,
does lsmod show rt2800pci?
On Wed, Nov 22, 2017 at 7:06 PM, Michael wrote:
> ~ $ sudo lspci
> [sudo] password for kodi:
> 00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev
> 02)
> 00:01.0 PCI bridge: Intel Corporation 82Q35 Express PCI Express Root Port
> (rev 02)
> 00:03
~ $ sudo lspci
[sudo] password for kodi:
00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev
02)
00:01.0 PCI bridge: Intel Corporation 82Q35 Express PCI Express Root Port
(rev 02)
00:03.0 Communication controller: Intel Corporation 82Q35 Express MEI
Controller (rev 02)
00:03.2
response with lspci output for wireless device would help. maybe it's a
known funky chipset. it's probably in the wall of text somewhere, but
lspci is a good tool for grabbing your peripherals.
On Wed, Nov 22, 2017 at 5:05 PM, Michael wrote:
> My wireless card isn't working (never has). Could
My wireless card isn't working (never has). Could someone take a look and
tell me what I need to do to get it to work? Here is a link to dmesg and
and /var/log/syslog:
https://drive.google.com/drive/folders/1ZkeLVAytkRQW1q57YktgOh4lL8VbfDwa?usp=sharing
after inspecting the syslog I see that actua
Chrome runs each tab in a seperate process, and the same for plugins, etc,
though sometimes those are shared. If you run ps -ef instead of top and
get the parent processid, they'd likely share a common parent. You can
organize the output with H. ps -efH and it'll group it in a tree format
based
Why does ps -ef show four entries for chrome?
top - 15:39:19 up 117 days, 6:18, 3 users, load average: 0.52, 0.53, 0.40
Tasks: 254 total, 2 running, 252 sleeping, 0 stopped, 0 zombie
%Cpu(s): 4.5 us, 1.4 sy, 0.0 ni, 94.0 id, 0.1 wa, 0.0 hi, 0.0 si,
0.0 st
KiB Mem: 8056428 total,
I've been living where I didn't need kodi but moved a couple of days ago.
Where did tvaddons go?
--
:-)~MIKE~(-:
---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.
12 matches
Mail list logo