wired/wireless

Thu Nov 23 12:06:51 MST 2017

unless it is part of the video card.

On Thu, Nov 23, 2017 at 2:05 PM, Michael <bmike1 at gmail.com> wrote:

> I took the wireless card out but that didn't do a thing so I put back in
> so I would have internet. As for the firewire I never put that in. If it is
> in there it is on the motherboard
>
> On Thu, Nov 23, 2017 at 2:01 PM, Brien Dieterle <briend at gmail.com> wrote:
>
>> 03:06.0 Network controller: Ralink corp. RT5362 PCI 802.11n Wireless
>> Network Adapter
>> 03:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000
>> Controller (PHY/Link)
>>
>> Do you still have the wireless in there?  I would remove that firewire
>> card too.
>> When you plug the computer into the modem, do you mean you are plugging
>> it directly into the single port on a "cable modem", or do you mean you're
>> plugging it into one of several ports on the wifi "router"?  If the former,
>> you need to make sure to power cycle the "modem" in order for it to accept
>> a new device (mac address)
>>
>> On Thu, Nov 23, 2017 at 11:50 AM, Michael <bmike1 at gmail.com> wrote:
>>
>>> My computer seems to reboot when I run darktable with a wireless card. I
>>> connect the modem to the computer and the network manager says that the
>>> wired connection is 'unmanaged'. I tried taking the wireless card out in
>>> case it caused a conflict but it still said 'unmanaged'. How do I get the
>>> network port working?
>>>
>>>  $ lspci
>>> 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge
>>> 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI
>>> bridge (ext gfx port 0)
>>> 00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI
>>> to PCI bridge (PCIE port 5)
>>> 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI]
>>> SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode]
>>> 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI]
>>> SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
>>> 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB
>>> OHCI1 Controller
>>> 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI]
>>> SB7x0/SB8x0/SB9x0 USB EHCI Controller
>>> 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI]
>>> SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
>>> 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB
>>> OHCI1 Controller
>>> 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI]
>>> SB7x0/SB8x0/SB9x0 USB EHCI Controller
>>> 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus
>>> Controller (rev 3c)
>>> 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI]
>>> SB7x0/SB8x0/SB9x0 IDE Controller
>>> 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00
>>> Azalia (Intel HDA)
>>> 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI]
>>> SB7x0/SB8x0/SB9x0 LPC host controller
>>> 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to
>>> PCI Bridge
>>> 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI]
>>> SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
>>> 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h
>>> Processor HyperTransport Configuration
>>> 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h
>>> Processor Address Map
>>> 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h
>>> Processor DRAM Controller
>>> 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h
>>> Processor Miscellaneous Control
>>> 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h
>>> Processor Link Control
>>> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
>>> [AMD/ATI] RV770 [Radeon HD 4850]
>>> 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV770 HDMI
>>> Audio [Radeon HD 4850/4870]
>>> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>>> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
>>> 03:06.0 Network controller: Ralink corp. RT5362 PCI 802.11n Wireless
>>> Network Adapter
>>> 03:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23
>>> IEEE-1394a-2000 Controller (PHY/Link)
>>>
>>> I assume RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller  is
>>> the card I want to work.
>>>
>>> That made me think....
>>>
>>>  more /var/log/syslog|grep Ethernet
>>> Nov 23 11:07:06 MikesBeast kernel: [    2.111079] r8169 Gigabit Ethernet
>>> driver 2.3LK-NAPI loaded
>>> Nov 23 11:07:11 MikesBeast NetworkManager[1165]: <info>
>>> [1511453231.3365] Loaded device plugin: NMEthernetFactory (internal)
>>> Nov 23 11:07:11 MikesBeast NetworkManager[1165]: <info>
>>> [1511453231.5231] manager: (enp2s0): new Ethernet device
>>> (/org/freedesktop/NetworkManager/Devices/1)
>>> Nov 23 11:36:29 MikesBeast kernel: [    2.125630] r8169 Gigabit Ethernet
>>> driver 2.3LK-NAPI loaded
>>> Nov 23 11:36:32 MikesBeast NetworkManager[1185]: <info>
>>> [1511454992.9499] Loaded device plugin: NMEthernetFactory (internal)
>>> Nov 23 11:36:33 MikesBeast NetworkManager[1185]: <info>
>>> [1511454993.2939] manager: (enp2s0): new Ethernet device
>>> (/org/freedesktop/NetworkManager/Devices/1)
>>> Nov 23 11:50:42 MikesBeast kernel: [    2.115241] r8169 Gigabit Ethernet
>>> driver 2.3LK-NAPI loaded
>>> Nov 23 11:50:46 MikesBeast NetworkManager[1189]: <info>
>>> [1511455846.1309] Loaded device plugin: NMEthernetFactory (internal)
>>> Nov 23 11:50:46 MikesBeast NetworkManager[1189]: <info>
>>> [1511455846.5400] manager: (enp2s0): new Ethernet device
>>> (/org/freedesktop/NetworkManager/Devices/1)
>>>
>>> $ less /var/log/syslog|grep network
>>> Nov 23 11:07:06 MikesBeast systemd[1]: Starting Raise network
>>> interfaces...
>>> Nov 23 11:07:06 MikesBeast systemd[1]: Started Raise network interfaces.
>>> Nov 23 11:07:10 MikesBeast NetworkManager[1165]: <info>
>>> [1511453229.9995] monitoring ifupdown state file '/run/network/ifstate'.
>>> Nov 23 11:07:14 MikesBeast NetworkManager[1165]: <info>
>>> [1511453234.2537] device (wlp3s6): Activation: (wifi) Stage 2 of 5 (Device
>>> Configure) successful.  Connected to wireless network 'SBG6700AC-AA593'.
>>> Nov 23 11:07:59 MikesBeast pulseaudio[2192]: [pulseaudio] bluez5-util.c:
>>> GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not
>>> receive a reply. Possible causes include: the remote application did not
>>> send a reply, the message bus security policy blocked the reply, the reply
>>> timeout expired, or the network connection was broken.
>>> Nov 23 11:24:21 MikesBeast NetworkManager[1165]: <info>
>>> [1511454261.5171] device (wlp3s6): Activation: (wifi) Stage 2 of 5 (Device
>>> Configure) successful.  Connected to wireless network 'SBG6700AC-AA593'.
>>> Nov 23 11:36:29 MikesBeast systemd[1]: Starting Raise network
>>> interfaces...
>>> Nov 23 11:36:29 MikesBeast systemd[1]: Started Raise network interfaces.
>>> Nov 23 11:36:31 MikesBeast NetworkManager[1185]: <info>
>>> [1511454991.3216] monitoring ifupdown state file '/run/network/ifstate'.
>>> Nov 23 11:37:20 MikesBeast pulseaudio[1987]: [pulseaudio] bluez5-util.c:
>>> GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not
>>> receive a reply. Possible causes include: the remote application did not
>>> send a reply, the message bus security policy blocked the reply, the reply
>>> timeout expired, or the network connection was broken.
>>> Nov 23 11:50:42 MikesBeast systemd[1]: Starting Raise network
>>> interfaces...
>>> Nov 23 11:50:42 MikesBeast systemd[1]: Started Raise network interfaces.
>>> Nov 23 11:50:44 MikesBeast NetworkManager[1189]: <info>
>>> [1511455844.4680] monitoring ifupdown state file '/run/network/ifstate'.
>>> Nov 23 11:50:50 MikesBeast NetworkManager[1189]: <info>
>>> [1511455850.0822] device (wlp3s6): Activation: (wifi) Stage 2 of 5 (Device
>>> Configure) successful.  Connected to wireless network 'SBG6700AC-AA593'.
>>> Nov 23 11:51:34 MikesBeast pulseaudio[2195]: [pulseaudio] bluez5-util.c:
>>> GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not
>>> receive a reply. Possible causes include: the remote application did not
>>> send a reply, the message bus security policy blocked the reply, the reply
>>> timeout expired, or the network connection was broken.
>>> bmike1 at MikesBeast ~/Pictures/2017 $
>>>
>>> That was my lame attempt to isolate network errors in the syslog.
>>> --
>>> :-)~MIKE~(-:
>>>
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>
>>
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>
>
>
>
> --
> :-)~MIKE~(-:
>

-- 
:-)~MIKE~(-:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20171123/46330c56/attachment.html>