New network manager is exist bug.

You have a problem with Salix? Post here and we'll do what we can to help.
zw963
Posts: 82
Joined: 13. Mar 2014, 18:36

Re: New network manager is exist bug.

Post by zw963 »

My laptop is HP Zbook 15 G2.

Following is my device out with

Code: Select all

# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
37 structures occupying 1888 bytes.
Table at 0x7BE3F000.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: Hewlett-Packard
	Version: M70 Ver. 01.12
	Release Date: 09/23/2015
	Address: 0xF0000
	Runtime Size: 64 kB
	ROM Size: 10240 kB
	Characteristics:
		PCI is supported
		PC Card (PCMCIA) is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		EDD is supported
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		ACPI is supported
		USB legacy is supported
		Smart battery is supported
		BIOS boot specification is supported
		Function key-initiated network boot is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 1.12
	Firmware Revision: 3.16

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: Hewlett-Packard
	Product Name: HP ZBook 15 G2
	Version: A3009CD10002
	Serial Number: CND5283R58
	UUID: 5047AA7F-EF9F-11E4-9501-6079730000FF
	Wake-up Type: Power Switch
	SKU Number: J4M39EP
	Family: 103C_5336AN G=N L=BUS B=HP S=ELI

Handle 0x0002, DMI type 2, 16 bytes
Base Board Information
	Manufacturer: Hewlett-Packard
	Product Name: 2253
	Version: KBC Version 03.10
	Serial Number: PENNRG2WV9HFMD
	Asset Tag: Not Specified
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis:  
	Chassis Handle: 0x0003
	Type: Unknown
	Contained Object Handles: 0

Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
	Manufacturer: Hewlett-Packard
	Type: Notebook
	Lock: Not Present
	Version: Not Specified
	Serial Number: CND5283R58
	Asset Tag: CND5283R58
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Other
	Security Status: Other
	OEM Information: 0x00000000

Handle 0x001E, DMI type 4, 42 bytes
Processor Information
	Socket Designation: U3E1
	Type: Central Processor
	Family: Core i7
	Manufacturer: Intel(R) Corporation
	ID: C3 06 03 00 FF FB EB BF
	Signature: Type 0, Family 6, Model 60, Stepping 3
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		PAE (Physical address extension)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		APIC (On-chip APIC hardware supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		PSE-36 (36-bit page size extension)
		CLFSH (CLFLUSH instruction supported)
		DS (Debug store)
		ACPI (ACPI supported)
		MMX (MMX technology supported)
		FXSR (FXSAVE and FXSTOR instructions supported)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		SS (Self-snoop)
		HTT (Multi-threading)
		TM (Thermal monitor supported)
		PBE (Pending break enabled)
	Version: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz
	Voltage: 0.8 V
	External Clock: 100 MHz
	Max Speed: 4200 MHz
	Current Speed: 2800 MHz
	Status: Populated, Enabled
	Upgrade: Socket BGA1364
	L1 Cache Handle: 0x001F
	L2 Cache Handle: 0x0020
	L3 Cache Handle: 0x0021
	Serial Number: To Be Filled By O.E.M.
	Asset Tag: To Be Filled By O.E.M.
	Part Number: Not Specified
	Core Count: 4
	Core Enabled: 4
	Thread Count: 8
	Characteristics:
		64-bit capable
		Multi-Core
		Hardware Thread
		Execute Protection
		Enhanced Virtualization
		Power/Performance Control

Handle 0x001D, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 32 kB
	Maximum Size: 32 kB
	Supported SRAM Types:
		Asynchronous
	Installed SRAM Type: Asynchronous
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Data
	Associativity: 8-way Set-associative

Handle 0x001F, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 32 kB
	Maximum Size: 32 kB
	Supported SRAM Types:
		Asynchronous
	Installed SRAM Type: Asynchronous
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Instruction
	Associativity: 8-way Set-associative

Handle 0x0020, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L2 Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 256 kB
	Maximum Size: 256 kB
	Supported SRAM Types:
		Asynchronous
	Installed SRAM Type: Asynchronous
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Unified
	Associativity: 8-way Set-associative

Handle 0x0021, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L3 Cache
	Configuration: Enabled, Not Socketed, Level 3
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 6144 kB
	Maximum Size: 6144 kB
	Supported SRAM Types:
		Asynchronous
	Installed SRAM Type: Asynchronous
	Speed: Unknown
	Error Correction Type: Multi-bit ECC
	System Type: Unified
	Associativity: 12-way Set-associative

Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Ctrl0Port0
	Internal Connector Type: SAS/SATA Plug Receptacle
	External Reference Designator: Primary HDD Bay
	External Connector Type: SAS/SATA Plug Receptacle
	Port Type: SATA

Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Ctrl0Port5
	Internal Connector Type: SAS/SATA Plug Receptacle
	External Reference Designator: Docking Station Upgrade Bay
	External Connector Type: SAS/SATA Plug Receptacle
	Port Type: SATA

Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Ctrl0Port4
	Internal Connector Type: SAS/SATA Plug Receptacle
	External Reference Designator: eSATA
	External Connector Type: SAS/SATA Plug Receptacle
	Port Type: SATA

Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Ctrl0Port3
	Internal Connector Type: SAS/SATA Plug Receptacle
	External Reference Designator: Docking Station eSATA
	External Connector Type: SAS/SATA Plug Receptacle
	Port Type: SATA

Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Ctrl0Port2
	Internal Connector Type: SAS/SATA Plug Receptacle
	External Reference Designator: mSATA
	External Connector Type: SAS/SATA Plug Receptacle
	Port Type: SATA

Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Ctrl0Port1
	Internal Connector Type: SAS/SATA Plug Receptacle
	External Reference Designator: Upgrade Bay
	External Connector Type: SAS/SATA Plug Receptacle
	Port Type: SATA

Handle 0x000F, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI SLOT1
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 1
	Characteristics:
		3.3 V is provided
		PME signal is supported
		SMBus signal is supported

Handle 0x0005, DMI type 10, 6 bytes
On Board Device Information
	Type: Video
	Status: Enabled
	Description: 256

Handle 0x000E, DMI type 11, 5 bytes
OEM Strings
	String 1: ABS 70/71 79 7A 7B 7C
	String 2: CSM v0x.xx
	String 3: HP_Mute_LED_0_0
	String 4: www.hp.com

Handle 0x0012, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Abbreviated
	Installable Languages: 14
		en-US
		da-DK
		nl-NL
		fi-FI
		fr-FR
		de-DE
		it-IT
		ja-JP
		no-NO
		pt-PT
		es-ES
		sv-SE
		zh-CN
		zh-TW
	Currently Installed Language: zh-CN

Handle 0x0013, DMI type 16, 23 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 32 GB
	Error Information Handle: Not Provided
	Number Of Devices: 4

Handle 0x0014, DMI type 17, 34 bytes
Memory Device
	Array Handle: 0x0013
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8192 MB
	Form Factor: SODIMM
	Set: None
	Locator: Top - Slot 2 (under)
	Bank Locator: BANK 0
	Type: DDR3
	Type Detail: Synchronous
	Speed: 1600 MHz
	Manufacturer: Samsung
	Serial Number: 32596930
	Asset Tag: 9876543210
	Part Number: M471B1G73QH0-YK0  
	Rank: Unknown
	Configured Clock Speed: Unknown

Handle 0x0016, DMI type 17, 34 bytes
Memory Device
	Array Handle: 0x0013
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8192 MB
	Form Factor: SODIMM
	Set: None
	Locator: Bottom-Slot 2(right)
	Bank Locator: BANK 1
	Type: DDR3
	Type Detail: Synchronous
	Speed: 1600 MHz
	Manufacturer: Samsung
	Serial Number: 57122121
	Asset Tag: 9876543210
	Part Number: M471B1G73DB0-YK0  
	Rank: Unknown
	Configured Clock Speed: Unknown

Handle 0x0018, DMI type 17, 34 bytes
Memory Device
	Array Handle: 0x0013
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8192 MB
	Form Factor: SODIMM
	Set: None
	Locator: Top - Slot 1 (top)
	Bank Locator: BANK 2
	Type: DDR3
	Type Detail: Synchronous
	Speed: 1600 MHz
	Manufacturer: Samsung
	Serial Number: 32596823
	Asset Tag: 9876543210
	Part Number: M471B1G73QH0-YK0  
	Rank: Unknown
	Configured Clock Speed: Unknown

Handle 0x001A, DMI type 17, 34 bytes
Memory Device
	Array Handle: 0x0013
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8192 MB
	Form Factor: SODIMM
	Set: None
	Locator: Bottom-Slot 1(left)
	Bank Locator: BANK 3
	Type: DDR3
	Type Detail: Synchronous
	Speed: 1600 MHz
	Manufacturer: Samsung
	Serial Number: 15147391
	Asset Tag: 9876543210
	Part Number: M471B1G73DB0-YK0  
	Rank: Unknown
	Configured Clock Speed: Unknown

Handle 0x001C, DMI type 19, 31 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x007FFFFFFFF
	Range Size: 32 GB
	Physical Array Handle: 0x0013
	Partition Width: 4

Handle 0x0015, DMI type 20, 35 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x001FFFFFFFF
	Range Size: 8 GB
	Physical Device Handle: 0x0014
	Memory Array Mapped Address Handle: 0x001C
	Partition Row Position: 1
	Interleave Position: 1
	Interleaved Data Depth: 2

Handle 0x0017, DMI type 20, 35 bytes
Memory Device Mapped Address
	Starting Address: 0x00200000000
	Ending Address: 0x003FFFFFFFF
	Range Size: 8 GB
	Physical Device Handle: 0x0016
	Memory Array Mapped Address Handle: 0x001C
	Partition Row Position: 1
	Interleave Position: 1
	Interleaved Data Depth: 2

Handle 0x0019, DMI type 20, 35 bytes
Memory Device Mapped Address
	Starting Address: 0x00400000000
	Ending Address: 0x005FFFFFFFF
	Range Size: 8 GB
	Physical Device Handle: 0x0018
	Memory Array Mapped Address Handle: 0x001C
	Partition Row Position: 1
	Interleave Position: 2
	Interleaved Data Depth: 2

Handle 0x001B, DMI type 20, 35 bytes
Memory Device Mapped Address
	Starting Address: 0x00600000000
	Ending Address: 0x007FFFFFFFF
	Range Size: 8 GB
	Physical Device Handle: 0x001A
	Memory Array Mapped Address Handle: 0x001C
	Partition Row Position: 1
	Interleave Position: 2
	Interleaved Data Depth: 2

Handle 0x0010, DMI type 22, 26 bytes
Portable Battery
	Location: Primary
	Manufacturer: 33-12
	Name: AR08075XL
	Design Capacity: 74880 mWh
	Design Voltage: 14400 mV
	SBDS Version: 1.1
	Maximum Error: Unknown
	SBDS Serial Number: 0B8B
	SBDS Manufacture Date: 2015-01-06
	SBDS Chemistry: LION
	OEM-specific Information: 0x00000000

Handle 0x0004, DMI type 32, 20 bytes
System Boot Information
	Status: No errors detected

Handle 0x0006, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: 256
	Type: Video
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:00:02.0

Handle 0x0007, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: WLAN
	Type: Ethernet
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:3c:00.0

Handle 0x0022, DMI type 130, 20 bytes
OEM-specific Type
	Header and Data:
		82 14 22 00 24 41 4D 54 01 01 01 01 00 A5 9F 02
		00 00 01 00

Handle 0x0023, DMI type 131, 64 bytes
OEM-specific Type
	Header and Data:
		83 40 23 00 35 00 00 00 0A 00 00 00 00 00 06 00
		F8 00 4F 8C 00 00 00 00 09 C0 00 00 01 00 09 00
		60 04 00 00 00 00 00 00 C8 00 3A 15 00 00 00 00
		04 0C 00 00 32 00 00 00 76 50 72 6F 00 00 00 00

Handle 0x0011, DMI type 137, 12 bytes
OEM-specific Type
	Header and Data:
		89 0C 11 00 01 00 F0 03 F0 FF 00 00

Handle 0xFFFD, DMI type 127, 4 bytes
End Of Table



User avatar
mimosa
Salix Warrior
Posts: 3311
Joined: 25. May 2010, 17:02
Contact:

Re: New network manager is exist bug.

Post by mimosa »

The use of the default dhcp client on your notebook already works, so the linked-to discussion about troubleshooting with another dhcp client than the default does not apply to you.
You seem very sure of this. But I think it is worth a try. Who knows how all these components are interacting? It is in any case easy enough to do and (if needed) reverse, with no harm done.

In the scenario addressed in that thread, it is not the case that dhcp doesn't work - it just isn't stable under certain conditions. However, see laprjns's latest post there. There seem to be a lot of problems with NM.

Would wicd be an option in this case? Again, this is easy to try, and reverse, even if it is a theoretical impossibility that it might help.
zw963
Posts: 82
Joined: 13. Mar 2014, 18:36

Re: New network manager is exist bug.

Post by zw963 »

mimosa wrote:
The use of the default dhcp client on your notebook already works, so the linked-to discussion about troubleshooting with another dhcp client than the default does not apply to you.

In the scenario addressed in that thread, it is not the case that dhcp doesn't work - it just isn't stable under certain conditions. However, see laprjns's latest post there. There seem to be a lot of problems with NM.

Would wicd be an option in this case? Again, this is easy to try, and reverse, even if it is a theoretical impossibility that it might help.
You seem very sure of this. But I think it is worth a try. Who knows how all these components are interacting? It is in any case easy enough to do and (if needed) reverse, with no harm done.
Oh, I understood now wicd is a network manager ... i will try later. but I think I found some issue about my config:

1. I found /etc/rc.d/rc.inet1 is executable, i don't remember when to change this ... it is a unexpected behavior, anywhy, we use NM.
I think my issue caused by this?? I make this not executable again, try some days, maybe it resolved ?
2. last night I suspend system (I always to like this, not poweroff), this moning, same issue happen again.
But, I found restart /etc/rc.d/rc.network is worked, so i think some other issue cause this ...

I will report after servel days, Thanks.
westms
Posts: 298
Joined: 17. Mar 2013, 18:51

Re: New network manager is exist bug.

Post by westms »

This page left intentionally blank
Last edited by westms on 23. Sep 2017, 13:54, edited 1 time in total.
DidierSpaier
Posts: 518
Joined: 20. Jun 2016, 20:15

Re: New network manager is exist bug.

Post by DidierSpaier »

Well, having the same /home partition for several distro is not a good idea, as many files stored in hidden directories should probably differ between distros. You are probably not eager to re-partition the mass storage device that host it now, but what you can easily do is create a user with a different name from each distro, e.g. zwsalix, zwslackel, zwslint and so (do not create the same user in several distros, of course).

Then for instance /home/zwsalix would automatically host hidden directories (like .config, .cache, .local, etc.) specific to Salix.

You could still share all not hidden directories and files under your current username. Lets assume it is zw963: all you have to do, I think, is set the permissions to 664 (instead of 644) for all regular files in /home/zw963 (assuming that you are the sole actual user of your machine). This way all users members of the users group will have read and write accesses to these files, so they will be available under all your user names, i.e. from all your distros. To do that you could log in using your current user name then type:

Code: Select all

cd ~
find . -user $(id -u) -perm 644 -group $(id -g) -exec chmod 664 '{}' ';'
Now to clean the house I would do this from Salix in a terminal:
First, to reset all network settings:

Code: Select all

sudo netsetup
and set the connection method as loopback, then confirm.
Then, to properly set NetworkManager

Code: Select all

sudo netsetup
again and set the connection method as NetworkManager, then confirm.
westms
Posts: 298
Joined: 17. Mar 2013, 18:51

Re: New network manager is exist bug.

Post by westms »

This page left intentionally blank
Last edited by westms on 23. Sep 2017, 13:54, edited 1 time in total.
zw963
Posts: 82
Joined: 13. Mar 2014, 18:36

Re: New network manager is exist bug.

Post by zw963 »

This connection still existed and could be used after you could not use the NetworkManager GUI. Did I understand you correctly?
Connection is missing when I come back, the icon is with a red X.
I have to right click `Enable network` close it and reclick it again.
the icon is still with a red X, seem like not connnect to.
But, current, it could not wo internet.
zw963
Posts: 82
Joined: 13. Mar 2014, 18:36

Re: New network manager is exist bug.

Post by zw963 »

DidierSpaier wrote:Well, having the same /home partition for several distro is not a good idea, as many files stored in hidden directories should probably differ between distros. You are probably not eager to re-partition the mass storage device that host it now, but what you can easily do is create a user with a different name from each distro, e.g. zwsalix, zwslackel, zwslint and so (do not create the same user in several distros, of course).

Then for instance /home/zwsalix would automatically host hidden directories (like .config, .cache, .local, etc.) specific to Salix.

You could still share all not hidden directories and files under your current username. Lets assume it is zw963: all you have to do, I think, is set the permissions to 664 (instead of 644) for all regular files in /home/zw963 (assuming that you are the sole actual user of your machine). This way all users members of the users group will have read and write accesses to these files, so they will be available under all your user names, i.e. from all your distros. To do that you could log in using your current user name then type:

Code: Select all

cd ~
find . -user $(id -u) -perm 644 -group $(id -g) -exec chmod 664 '{}' ';'
Now to clean the house I would do this from Salix in a terminal:
First, to reset all network settings:

Code: Select all

sudo netsetup
and set the connection method as loopback, then confirm.
Then, to properly set NetworkManager

Code: Select all

sudo netsetup
again and set the connection method as NetworkManager, then confirm.
Cool thinking, thanks.

Current, what I doing is: create some symbol links to some home special directory with a bash install scripts when switch to a new distros
I think that not well enough, but, basically, if some special situation happen, I could delete all my hidden files+directory in my $HOME,
and use that scripts to create symlink again.

Though, some weried things still happen .... I think I will try to use your's method when I have some time to do this.
zw963
Posts: 82
Joined: 13. Mar 2014, 18:36

Re: New network manager is exist bug.

Post by zw963 »

My attempt to find the external influence on the NetworkManager:

1. You open the screensaver and choose "Disable screensaver" (possibly not literal). Then boot and wait for the error to reappear.

2. If the error occurs, you can also ban the X server from turning off the screen and others. You create a file named 50-serverflags.conf

The content is:
CODE: SELECT ALL
Section "ServerFlags"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
EndSection

Copy this file to /etc/X11/xorg.conf.d :
CODE: SELECT ALL
sudo cp 50-serverflags.conf /etc/X11/xorg.conf.d

Set ownership and file permissions:
CODE: SELECT ALL
sudo chown root:root /etc/X11/xorg.conf.d/50-serverflags.conf
sudo chmod 0644 /etc/X11/xorg.conf.d/50-serverflags.conf
I not found the correct why to disable XScreenServer daemon, so i do exact the way as you suggest.

It maybe need several days to confirom this still happen or not.

I will give feedback after serveral days.

Thanks.
zw963
Posts: 82
Joined: 13. Mar 2014, 18:36

Re: New network manager is exist bug.

Post by zw963 »

Now in the distribution Salix approximately seven of 1449 members are affected and NetworkManager is to be responsible. I will not believe it so easily.
Thank you for another ones have same issue with me ....
It is seem like probably not caused by my personal stupid `common use $HOME directrory` issues or similar things.

I read english very slowly bacause pool english, I need more time to following those reply ....
Post Reply