Velocizzare avvio

Fedora Linux Configurazione
#1

Buongiorno a tutti.
Sarei curioso di apire se è possibile, sul mio sistema, velocizzare l’avvio.
Alcune info. Se ne servissero altre, chiedete pure.

[code][giacomob@Fodora ~]$ systemd-analyze blame --no-pager
34.636s dnf-makecache.service
19.953s plymouth-quit-wait.service
8.594s systemd-journal-flush.service
8.100s firewalld.service
7.437s NetworkManager-wait-online.service
6.357s systemd-udev-settle.service
6.327s vboxdrv.service
6.097s abrtd.service
5.866s dev-sda2.device
3.826s lm_sensors.service
3.792s chronyd.service
3.552s systemd-logind.service
3.437s rpcbind.service
3.436s netcf-transaction.service
2.763s libvirtd.service
2.691s accounts-daemon.service
2.444s packagekit.service
1.705s systemd-udevd.service
1.657s lvm2-monitor.service
1.370s systemd-binfmt.service
1.139s systemd-fsck@dev-disk-by\x2duuid-1cc86f97\x2dd6f0\x2d42b5\x2d8d16\x2d6cd91b8f2b44.service
1.027s dev-disk-by\x2duuid-17efda43\x2d329f\x2d4cbc\x2d9494\x2d1cf079d18bde.swap
1.020s plymouth-start.service
1.019s udisks2.service
996ms systemd-tmpfiles-setup-dev.service
961ms proc-sys-fs-binfmt_misc.mount
852ms polkit.service
756ms vboxautostart-service.service
754ms rsyslog.service
683ms kmod-static-nodes.service
653ms auditd.service
577ms systemd-journald.service
570ms systemd-remount-fs.service
563ms systemd-sysctl.service
541ms fedora-readonly.service
540ms dev-mqueue.mount
540ms tmp.mount
538ms dev-hugepages.mount
533ms NetworkManager.service
476ms gdm.service
445ms systemd-fsck@dev-disk-by\x2duuid-63c83c32\x2d3508\x2d4365\x2d8297\x2de9d5d245b4bb.service
413ms dmraid-activation.service
404ms abrt-ccpp.service
386ms rtkit-daemon.service
383ms console-kit-log-system-start.service
374ms systemd-random-seed.service
374ms mnt-server.mount
353ms [email protected]
256ms iio-sensor-proxy.service
220ms fedora-import-state.service
214ms wpa_supplicant.service
195ms systemd-tmpfiles-setup.service
170ms home.mount
158ms [email protected]
155ms systemd-udev-trigger.service
154ms plymouth-read-write.service
148ms colord.service
141ms sys-kernel-debug.mount
133ms systemd-user-sessions.service
119ms upower.service
111ms dracut-shutdown.service
104ms systemd-timesyncd.service
103ms console-kit-daemon.service
97ms systemd-fsck-root.service
73ms vboxweb-service.service
68ms vboxballoonctrl-service.service
38ms boot.mount
32ms systemd-update-utmp.service
13ms systemd-vconsole-setup.service
4ms systemd-update-utmp-runlevel.service
3ms sys-fs-fuse-connections.mount
3ms teamviewerd.service
1ms sys-kernel-config.mount
914us blk-availability.service
[giacomob@Fodora ~]$ systemd-analyze time
Startup finished in 1.546s (kernel) + 2.471s (initrd) + 53.660s (userspace) = 57.679s
[giacomob@Fodora ~]$ systemd-analyze critical-chain --no-pager
The time after the unit is active or started is printed after the “@” character.
The time the unit takes to start is printed after the “+” character.

graphical.target @53.644s
└─multi-user.target @53.644s
└─libvirtd.service @33.438s +2.763s
└─remote-fs.target @33.390s
└─mnt-server.mount @33.015s +374ms
└─network-online.target @32.986s
└─NetworkManager-wait-online.service @25.548s +7.437s
└─NetworkManager.service @25.004s +533ms
└─network-pre.target @24.988s
└─firewalld.service @16.887s +8.100s
└─polkit.service @18.726s +852ms
└─basic.target @13.517s
└─paths.target @13.517s
└─cups.path @13.517s
└─sysinit.target @13.497s
└─systemd-update-utmp.service @13.464s +32ms
└─auditd.service @12.797s +653ms
└─systemd-tmpfiles-setup.service @12.587s +195ms
└─fedora-import-state.service @12.356s +220ms
└─local-fs.target @12.235s
└─run-user-42.mount @35.009s
└─local-fs-pre.target @10.845s
└─systemd-tmpfiles-setup-dev.service @3.919s +996ms
└─kmod-static-nodes.service @3.212s +683ms
└─systemd-journald.socket
└─-.mount
└─system.slice
└─-.slice
[giacomob@Fodora ~]$ systemd-analyze critical-chain NetworkManager-wait-online.service --no-pager
The time after the unit is active or started is printed after the “@” character.
The time the unit takes to start is printed after the “+” character.

NetworkManager-wait-online.service +7.437s
└─NetworkManager.service @25.004s +533ms
└─network-pre.target @24.988s
└─firewalld.service @16.887s +8.100s
└─polkit.service @18.726s +852ms
└─basic.target @13.517s
└─paths.target @13.517s
└─cups.path @13.517s
└─sysinit.target @13.497s
└─systemd-update-utmp.service @13.464s +32ms
└─auditd.service @12.797s +653ms
└─systemd-tmpfiles-setup.service @12.587s +195ms
└─fedora-import-state.service @12.356s +220ms
└─local-fs.target @12.235s
└─run-user-42.mount @35.009s
└─local-fs-pre.target @10.845s
└─systemd-tmpfiles-setup-dev.service @3.919s +996ms
└─kmod-static-nodes.service @3.212s +683ms
└─systemd-journald.socket
└─-.mount
└─system.slice
└─-.slice
[giacomob@Fodora ~]$ journalctl -b 0 -u NetworkManager.service
Hint: You are currently not seeing messages from other users and the system.
Users in groups ‘adm’, ‘systemd-journal’, ‘wheel’ can see all messages.
Pass -q to turn off this notice.
– No entries –
[giacomob@Fodora ~]$ ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.77 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::b6b5:2fff:fecb:482f prefixlen 64 scopeid 0x20
ether b4:b5:2f:cb:48:2f txqueuelen 1000 (Ethernet)
RX packets 94920 bytes 127235671 (121.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 49819 bytes 4165618 (3.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf7100000-f7120000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1 (Local Loopback)
RX packets 180 bytes 14520 (14.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 180 bytes 14520 (14.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[giacomob@Fodora ~]$
[/code]
Il sistema monta in automatico una partizione ntfs che si trova su un server windows server R2 collegato in rete lan.

In particolar modo vorrei capire da cosa dipendono quei 53 secondi in userspace.
C’è da dire che la sola fase di boot probabilmente potrebbe essere accettabile ma la fase post inserimento pwd è veramente lunga (nonostante al momento stia usando lxdm e lxde)

Grazie.

#2

Ciao prova a dare il comando :

systemctl status lightdm.service

e poi dai

systemctl status gdm.service

perché gdm è attivo ma lightdm non mi pare altra domanda hai installato fedora gnome e poi hai aggiunto lxde come DE o hai preso la spin fedora lxde ? tanto per avere le idee più chiare :slight_smile:

#3

Ciao edmondo e grazie per la risposta.
Lightdm. service non era attivo anche perché lightdm non era nemmeno installato :reddy:
Installato, attivato e disabilitato gdm il tutto è migliorato

[giacomob@Fodora ~]$ systemd-analyze Startup finished in 1.547s (kernel) + 2.501s (initrd) + 37.459s (userspace) = 41.507s [giacomob@Fodora ~]$ systemd-analyze blame 9.893s firewalld.service 8.694s vboxdrv.service 8.389s NetworkManager-wait-online.service 7.648s systemd-journald.service 6.200s systemd-udev-settle.service 6.133s dev-sda2.device 5.410s abrtd.service 3.774s accounts-daemon.service 3.070s libvirtd.service 2.362s systemd-journal-flush.service 2.159s lvm2-monitor.service 1.781s systemd-udevd.service 1.632s polkit.service 1.626s rsyslog.service 1.617s systemd-binfmt.service 1.566s teamviewerd.service 1.515s systemd-tmpfiles-setup-dev.service 1.329s proc-sys-fs-binfmt_misc.mount 1.241s udisks2.service 1.201s console-kit-log-system-start.service 1.188s systemd-fsck@dev-disk-by\x2duuid-1cc86f97\x2dd6f0\x2d42b5\x2d8d 1.168s chronyd.service 1.165s netcf-transaction.service 1.072s plymouth-start.service 1.056s lm_sensors.service 942ms rpcbind.service 735ms fedora-readonly.service 724ms systemd-fsck@dev-disk-by\x2duuid-63c83c32\x2d3508\x2d4365\x2d82 647ms systemd-remount-fs.service 623ms auditd.service 607ms dev-hugepages.mount 607ms sys-kernel-debug.mount 598ms dev-mqueue.mount 581ms dev-disk-by\x2duuid-17efda43\x2d329f\x2d4cbc\x2d9494\x2d1cf079d 564ms abrt-ccpp.service 533ms dmraid-activation.service 531ms iio-sensor-proxy.service 509ms NetworkManager.service 456ms lightdm.service 423ms systemd-sysctl.service 392ms home.mount 387ms tmp.mount 372ms kmod-static-nodes.service 334ms rtkit-daemon.service 324ms systemd-udev-trigger.service 316ms plymouth-quit-wait.service 315ms plymouth-quit.service 289ms mnt-server.mount 254ms systemd-logind.service 248ms systemd-tmpfiles-setup.service 207ms fedora-import-state.service 187ms systemd-random-seed.service 164ms plymouth-read-write.service 155ms systemd-fsck-root.service 119ms systemd-user-sessions.service 117ms vboxautostart-service.service 109ms vboxweb-service.service 109ms vboxballoonctrl-service.service 104ms [email protected] 89ms systemd-timesyncd.service 86ms dracut-shutdown.service 63ms systemd-update-utmp.service 53ms console-kit-daemon.service 50ms boot.mount 12ms systemd-vconsole-setup.service 4ms systemd-update-utmp-runlevel.service 2ms sys-fs-fuse-connections.mount 1ms blk-availability.service 1ms sys-kernel-config.mount lines 47-69/69 (END)

Mi chiedo però, ancora, se 37 secondi non siano eccessivi per avviare un DE “leggero”.
Può dipendere dai file che ho ad esempio sul desktop (alcuni molto grandi)?

Ps: ho installato Fedora con gnome e poi aggiunto prima openbox, poi lxde.

#4

Ciao perfetto che cè un miglioramento una domanda , hai un pc con bios uefi o normale ? lancia

#dmidecode

e posta :slight_smile:

#5

Ciao edmondo.

Il PC credo sia con bios uefi anche se al momento dell’installazione disattivai il disattivabile per installare Fedora (17) in quanto ero alle prime armi (come tutti) con uefi e non fui in grado di fare un dual boot lasciando anche windows. Infatti ora ho solo fedora su questo pc.
A proposito. Riuscirei ora a reinstallare windows (10) su questo pc senza dover cancellare Fedora? (In caso si possa fare aprirei un altro topic ovviamente, in cui chiedere maggiori info su come operare).
Intanto l’output del tuo comando:

[code][root@Fodora ~]# dmidecode

dmidecode 3.0

Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
83 structures occupying 3203 bytes.
Table at 0x000E9010.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Hewlett-Packard
Version: K51 v01.02
Release Date: 05/03/2012
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 16384 kB
Characteristics:
PCI is supported
PNP 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
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.2

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Hewlett-Packard
Product Name: HP Z220 CMT Workstation
Version: Not Specified
Serial Number: CZC2412G9T
UUID: 055EE680-0AB5-11E2-BE24-B4B52FCB482F
Wake-up Type: Power Switch
SKU Number: A3J44AV
Family: 103C_53335X G=D

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Hewlett-Packard
Product Name: 1790
Version: Not Specified
Serial Number: CZC2412G9T
Asset Tag: CZC2412G9T
Features:
Board is a hosting board
Board is removable
Board is replaceable
Location In Chassis: Not Specified
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
Manufacturer: Hewlett-Packard
Type: Mini Tower
Lock: Not Present
Version: Not Specified
Serial Number: CZC2412G9T
Asset Tag: CZC2412G9T
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
SKU Number:

Handle 0x0004, DMI type 4, 42 bytes
Processor Information
Socket Designation: SOCKET 0
Type: Central Processor
Family: Core i5
Manufacturer: Intel
ID: A9 06 03 00 FF FB EB BF
Signature: Type 0, Family 6, Model 58, Stepping 9
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® Core™ i5-3470 CPU @ 3.20GHz
Voltage: 1.1 V
External Clock: 100 MHz
Max Speed: 3800 MHz
Current Speed: 3200 MHz
Status: Populated, Enabled
Upgrade: Socket BGA1155
L1 Cache Handle: 0x0005
L2 Cache Handle: 0x0006
L3 Cache Handle: 0x0007
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 4
Core Enabled: 4
Thread Count: 4
Characteristics:
64-bit capable
Multi-Core
Execute Protection
Enhanced Virtualization
Power/Performance Control

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

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

Handle 0x0007, 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:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: Other

Handle 0x0008, DMI type 9, 17 bytes
System Slot Information
Designation: SLOT 1
Type: x4 PCI Express 2 x8
Current Usage: Available
Length: Long
ID: 0
Characteristics:
3.3 V is provided
PME signal is supported
Bus Address: 0000:00:00.0

Handle 0x0009, DMI type 9, 17 bytes
System Slot Information
Designation: SLOT 2
Type: x16 PCI Express 3
Current Usage: In Use
Length: Long
ID: 1
Characteristics:
3.3 V is provided
PME signal is supported
Bus Address: 0000:01:00.0

Handle 0x000A, DMI type 9, 17 bytes
System Slot Information
Designation: SLOT 3
Type: x1 PCI Express 2
Current Usage: Available
Length: Short
ID: 2
Characteristics:
3.3 V is provided
PME signal is supported
Bus Address: 0000:00:00.0

Handle 0x000B, DMI type 9, 17 bytes
System Slot Information
Designation: SLOT 4
Type: x4 PCI Express 2 x16
Current Usage: Available
Length: Long
ID: 3
Characteristics:
3.3 V is provided
PME signal is supported
Bus Address: 0000:00:00.0

Handle 0x000C, DMI type 9, 17 bytes
System Slot Information
Designation: SLOT 5
Type: x1 PCI Express 2
Current Usage: Available
Length: Short
ID: 4
Characteristics:
3.3 V is provided
PME signal is supported
Bus Address: 0000:00:00.0

Handle 0x000D, DMI type 9, 17 bytes
System Slot Information
Designation: SLOT 6
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 5
Characteristics:
5.0 V is provided
3.3 V is provided
PME signal is supported
Bus Address: 0000:02:00.0

Handle 0x000E, DMI type 9, 17 bytes
System Slot Information
Designation: SLOT 7
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 6
Characteristics:
5.0 V is provided
3.3 V is provided
PME signal is supported
Bus Address: 0000:02:01.0

Handle 0x000F, DMI type 11, 5 bytes
OEM Strings
String 1: ABS 70/71 60 61 62 63;
String 2: FBYTE#3Q3X3Z3m47676J6S6b7N7Q7T7U7W7a8H8h.q3;
String 3: BUILDID#12WWSPBW602#SABZ#DABZ;

Handle 0x0010, DMI type 12, 5 bytes
System Configuration Options
Option 1: To Be Filled By O.E.M.

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

Handle 0x0012, DMI type 26, 22 bytes
Voltage Probe
Description: LM78A
Location: Power Unit
Status: OK
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000
Nominal Value: Unknown

Handle 0x0013, DMI type 28, 22 bytes
Temperature Probe
Description: LM78A
Location: Power Unit
Status: OK
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000
Nominal Value: Unknown

Handle 0x0014, DMI type 27, 15 bytes
Cooling Device
Temperature Probe Handle: 0x0013
Type: Power Supply Fan
Status: OK
Cooling Unit Group: 1
OEM-specific Information: 0x00000000
Nominal Speed: Unknown Or Non-rotating
Description: Cooling Dev 1

Handle 0x0015, DMI type 29, 22 bytes
Electrical Current Probe
Description: ABC
Location: Power Unit
Status: OK
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000
Nominal Value: Unknown

Handle 0x0016, DMI type 39, 22 bytes
System Power Supply
Power Unit Group: 1
Location: To Be Filled By O.E.M.
Name: To Be Filled By O.E.M.
Manufacturer: To Be Filled By O.E.M.
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Model Part Number: To Be Filled By O.E.M.
Revision: To Be Filled By O.E.M.
Max Power Capacity: Unknown
Status: Present, OK
Type: Switching
Input Voltage Range Switching: Auto-switch
Plugged: Yes
Hot Replaceable: No
Input Voltage Probe Handle: 0x0012
Cooling Device Handle: 0x0014
Input Current Probe Handle: 0x0015

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

Handle 0x0018, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard LAN
Type: Ethernet
Status: Enabled
Type Instance: 1
Bus Address: 0000:00:19.0

Handle 0x0019, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard 1394
Type: Other
Status: Enabled
Type Instance: 1
Bus Address: 0000:03:1c.2

Handle 0x001A, 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 0x001B, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x001A
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM4
Bank Locator:
Type: Unknown
Type Detail: None
Speed: Unknown
Manufacturer: [Empty]
Serial Number: [Empty]
Asset Tag: 9876543210
Part Number: [Empty]
Rank: Unknown
Configured Clock Speed: Unknown

Handle 0x001C, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x001A
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: DIMM
Set: None
Locator: DIMM3
Bank Locator:
Type: DDR3
Type Detail: Synchronous
Speed: 1600 MHz
Manufacturer: Micron
Serial Number: FB7A6045
Asset Tag: 9876543210
Part Number: 8JTF25664AZ-1G6M1
Rank: 1
Configured Clock Speed: 1600 MHz

Handle 0x001D, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x001C
Memory Array Mapped Address Handle: 0x0021
Partition Row Position: Unknown
Interleave Position: 1
Interleaved Data Depth: 2

Handle 0x001E, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x001A
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM2
Bank Locator:
Type: Unknown
Type Detail: None
Speed: Unknown
Manufacturer: [Empty]
Serial Number: [Empty]
Asset Tag: 9876543210
Part Number: [Empty]
Rank: Unknown
Configured Clock Speed: Unknown

Handle 0x001F, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x001A
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: DIMM
Set: None
Locator: DIMM1
Bank Locator:
Type: DDR3
Type Detail: Synchronous
Speed: 1600 MHz
Manufacturer: Micron
Serial Number: FB7A6044
Asset Tag: 9876543210
Part Number: 8JTF25664AZ-1G6M1
Rank: 1
Configured Clock Speed: 1600 MHz

Handle 0x0020, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FFFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x001F
Memory Array Mapped Address Handle: 0x0021
Partition Row Position: Unknown
Interleave Position: 2
Interleaved Data Depth: 2

Handle 0x0021, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FFFFFFFF
Range Size: 4 GB
Physical Array Handle: 0x001A
Partition Width: 4

Handle 0x002D, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 12
en|US|iso8859-1
fr|FR|iso8859-1
es|ES|iso8859-1
de|DE|iso8859-1
it|IT|iso8859-1
da|DK|iso8859-1
fi|FI|iso8859-1
nl|NL|iso8859-1
no|NO|iso8859-1
pt|PT|iso8859-1
sv|SE|iso8859-1
ja|JP|unicode
Currently Installed Language: it|IT|iso8859-1

Handle 0x002F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J68 PS2
Internal Connector Type: None
External Reference Designator: PS2Mouse
External Connector Type: PS/2
Port Type: Mouse Port

Handle 0x0030, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J68 PS2
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: PS/2
Port Type: Keyboard Port

Handle 0x0031, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J64 DP
Internal Connector Type: None
External Reference Designator: DisplayPort
External Connector Type: Other
Port Type: Video Port

Handle 0x0032, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J65
Internal Connector Type: None
External Reference Designator: DVI
External Connector Type: Other
Port Type: Video Port

Handle 0x0033, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9 RJ45
Internal Connector Type: None
External Reference Designator: LAN
External Connector Type: RJ-45
Port Type: Network Port

Handle 0x0034, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P52 COM
Internal Connector Type: Proprietary
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Serial Port 16550A Compatible

Handle 0x0035, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P126 PAR
Internal Connector Type: Proprietary
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Parallel Port ECP/EPP

Handle 0x0036, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J83
Internal Connector Type: None
External Reference Designator: Rear mic in
External Connector Type: Mini DIN
Port Type: Audio Port

Handle 0x0037, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J83
Internal Connector Type: None
External Reference Designator: Rear headphone/line out
External Connector Type: Mini DIN
Port Type: Audio Port

Handle 0x0038, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J83
Internal Connector Type: None
External Reference Designator: Rear line in
External Connector Type: Mini DIN
Port Type: Audio Port

Handle 0x0039, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P28 FRONT AUD
Internal Connector Type: None
External Reference Designator: Front mic in
External Connector Type: Mini DIN
Port Type: Audio Port

Handle 0x003A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P28 FRONT AUD
Internal Connector Type: None
External Reference Designator: Front headphone/line out
External Connector Type: Mini DIN
Port Type: Audio Port

Handle 0x003B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P27 Internal USB1 (0)
Internal Connector Type: Proprietary
External Reference Designator: Not Specified
External Connector Type: None
Port Type: USB

Handle 0x003C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P27 Internal USB1 (1)
Internal Connector Type: Proprietary
External Reference Designator: Not Specified
External Connector Type: None
Port Type: USB

Handle 0x003D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P25 Internal USB2 (2)
Internal Connector Type: Proprietary
External Reference Designator: Not Specified
External Connector Type: None
Port Type: USB

Handle 0x003E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P25 Internal USB2 (3)
Internal Connector Type: Proprietary
External Reference Designator: Not Specified
External Connector Type: None
Port Type: USB

Handle 0x003F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P24 FRONT USB
Internal Connector Type: Proprietary
External Reference Designator: Front USB (4)
External Connector Type: Access Bus (USB)
Port Type: USB

Handle 0x0040, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P24 FRONT USB
Internal Connector Type: Proprietary
External Reference Designator: Front USB (5)
External Connector Type: Access Bus (USB)
Port Type: USB

Handle 0x0041, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P24 FRONT USB
Internal Connector Type: Proprietary
External Reference Designator: Front USB (6)
External Connector Type: Access Bus (USB)
Port Type: USB

Handle 0x0042, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P26 Internal USB2 (7)
Internal Connector Type: Proprietary
External Reference Designator: Not Specified
External Connector Type: None
Port Type: USB

Handle 0x0043, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J10 USB
Internal Connector Type: None
External Reference Designator: Rear USB (8)
External Connector Type: Access Bus (USB)
Port Type: USB

Handle 0x0044, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J10 USB
Internal Connector Type: None
External Reference Designator: Rear USB (9)
External Connector Type: Access Bus (USB)
Port Type: USB

Handle 0x0045, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J10 USB
Internal Connector Type: None
External Reference Designator: Rear USB (10)
External Connector Type: Access Bus (USB)
Port Type: USB

Handle 0x0046, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J10 USB
Internal Connector Type: None
External Reference Designator: Rear USB (11)
External Connector Type: Access Bus (USB)
Port Type: USB

Handle 0x0047, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9 USB
Internal Connector Type: None
External Reference Designator: Rear USB (12)
External Connector Type: Access Bus (USB)
Port Type: USB

Handle 0x0048, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9 USB
Internal Connector Type: None
External Reference Designator: Rear USB (13)
External Connector Type: Access Bus (USB)
Port Type: USB

Handle 0x0049, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P60 SATA0
Internal Connector Type: SAS/SATA Plug Receptacle
External Reference Designator: Not Specified
External Connector Type: None
Port Type: SATA

Handle 0x004A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P61 SATA1
Internal Connector Type: SAS/SATA Plug Receptacle
External Reference Designator: Not Specified
External Connector Type: None
Port Type: SATA

Handle 0x004B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P62 SATA2
Internal Connector Type: SAS/SATA Plug Receptacle
External Reference Designator: Not Specified
External Connector Type: None
Port Type: SATA

Handle 0x004C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P63 SATA3
Internal Connector Type: SAS/SATA Plug Receptacle
External Reference Designator: Not Specified
External Connector Type: None
Port Type: SATA

Handle 0x004D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P64 SATA4
Internal Connector Type: SAS/SATA Plug Receptacle
External Reference Designator: Not Specified
External Connector Type: None
Port Type: SATA

Handle 0x004E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P65 SATA5
Internal Connector Type: SAS/SATA Plug Receptacle
External Reference Designator: Not Specified
External Connector Type: None
Port Type: SATA

Handle 0x004F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P1 (Main power)
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other

Handle 0x0050, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P3 CPU PWR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other

Handle 0x0051, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P5 FP (Front panel)
Internal Connector Type: Proprietary
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other

Handle 0x0052, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P6 SPKR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other

Handle 0x0053, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P8 CHFAN (Rear chassis fan)
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other

Handle 0x0054, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P9 (Front chassis fan)
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other

Handle 0x0055, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P71 CPU FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other

Handle 0x0056, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P124 HOOD_LOCK
Internal Connector Type: Proprietary
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other

Handle 0x0057, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: P125 HOOD_SENSE
Internal Connector Type: Proprietary
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other

Handle 0x0058, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: E49 (Password enable)
Internal Connector Type: Proprietary
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other

Handle 0x0059, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HLCK
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: Other
Port Type: Other

Handle 0x005A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HSNR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: Other
Port Type: Other

Handle 0x005B, DMI type 129, 8 bytes
OEM-specific Type
Header and Data:
81 08 5B 00 01 01 02 01
Strings:
Intel_ASF
Intel_ASF_001

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

Handle 0x005D, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 5D 00 37 00 00 00 08 00 00 00 00 00 3D 00
F8 00 53 1E FF FF FF FF 09 C0 00 00 00 00 08 00
A1 05 04 00 00 00 00 00 C8 00 02 15 00 00 00 00
00 00 00 00 F6 00 00 00 76 50 72 6F 00 00 00 00

Handle 0x005E, DMI type 127, 4 bytes
End Of Table[/code]

#6

Ciao io come consiglio direi di riabilitare uefi e di installare il tutto in uefi almeno io ho notato molti vantaggi con uefi in primo si possono fare più partizioni , la fase di boot in caso di più distro linux è perfettamente gestibile da efibootmgr per il discorso windows non so che dirti per il fatto che sono anni che lavoro solo con linux , bisogna vedere qualche utente che usa sia windows in dual boot con linux se ci sono problemi in caso di installazione ovvero se conviene mettere prima windows e poi Fedora o viceversa :slight_smile:
edit: si uefi è supoortato difatti :

UEFI is supported

tratto dalla lettura di dmidecode :slight_smile:

#7

Ciao edmondo.
Ti ringrazio per le info.
Ma dall’output di dmidecode cosa si doveva notare in merito al miglioramento della velocità di boot?
Il fatto di mettere in uefi migliorerebbe il tutto? E per la lentezza del caricamento del DE post inserimento pwd?

#8

Buongiorno.
Ravvivo questa discussione per lo stesso problema.
Uso con molta soddisfazione la F24 sul questo portatile in Dual-boot con Win7(anche se praticamente non lo uso mai) solo che ultimamente l’avvio si è dilungato in modo impressionante dopo aver selezionato il SO al grub. Dopo aver premuto Invio (evitando i 5s di attesa e non considerando il tempo per arrivare a questa finestra dall’accensione) F24 impiega 56s per arrivare alla finestra di richiesta pwd (mentre ad esempio Win7 si avvia dopo qualche secondo -srunt!- ); inserita pwd e confermato ci mette 18s per arrivare alla finestra del DE (Cinnamon).
Il tutto non è che siano tempi lunghissimi (tot 1.14m ca.), solo che dai primi giorni è spaventosamente aumentato. E con gli aggiornamenti vado mooolto piano.
Leggendo questa e altre vecchie discussioni ho voluto verificare con il comando sotto e mi sono ritrovato con alcune righe evidenziate in rosso oltre a qualche cosa di “strano”. Ho indicato le righe rosse con un * davanti

[code][massimo@localhost ~]$ systemd-analyze critical-chain --no-pager
The time after the unit is active or started is printed after the “@” character.
The time the unit takes to start is printed after the “+” character.

graphical.target @28.051s
*└─lightdm.service @27.605s +445ms
*└─systemd-user-sessions.service @26.987s +377ms
└─remote-fs.target @26.986s
└─remote-fs-pre.target @26.986s
└─iscsi-shutdown.service @26.985s
└─network.target @26.951s
*└─NetworkManager.service @26.382s +568ms
└─network-pre.target @26.374s
*└─firewalld.service @16.619s +9.755s
*└─polkit.service @17.015s +2.506s
└─basic.target @13.493s
└─paths.target @13.493s
└─cups.path @13.493s
└─sysinit.target @13.462s
*└─systemd-update-utmp.service @13.422s +39ms
*└─auditd.service @12.984s +432ms
*└─systemd-tmpfiles-setup.service @12.772s +182ms
*└─fedora-import-state.service @12.510s +255ms
└─local-fs.target @12.504s
*└─boot.mount @12.404s +99ms
*└─systemd-fsck@dev-disk-by\x2duuid-dcf30501\x2d8b9a\x2d458a\x2d96c0\x2d9a672e81890f.service @11.830s +542ms
└─local-fs-pre.target @11.792s
*└─lvm2-monitor.service @2.376s +2.072s
└─lvm2-lvmetad.service @3.232s
└─lvm2-lvmetad.socket @2.327s
└─-.mount
└─system.slice
└─-.slice

[/code]In particolare, nella mia ignoranza, le righe che mi sembrano “dubbie” sono queste: systemd-tmpfiles-setup.service e fedora-import-state.service. Che magari non c’entrano assolutamente nulla però mi hanno incuriosito.
Per completezza, aggiungo che il disco è meccanico e i vari test non rilevano nessun problema, e il sistema all’avvio monta una partizione per documenti e dati.
È possibile riportare i tempi di avvio ai precedenti o almeno accelerarlo un po’.
Grazie mille
Ciao

#9

In passato ho avuto anch’io questo problema (tempo molto lungo nell’avvio del DE gnome).
Ho risolto in questo modo:
dopo due o tre upgrade di sistema effettuavo in’installazione di fedora pulita mantenendo unicamente la home.
Lo so, è un lavoraccio risistemare tutto, ma non devi piu’ fare jogging nel frattempo.

#10

@MotoBruno, ti ringrazio, mi pare di aver capito che il tuo problema però nasceva da upgrade di sistema.
La mia situazione è invece una prima installazione di Fedora Cinnamon su un pc pulito con nessun aggiornamento di sistema, inteso come kernel o altre parti vitali. A dire il vero, ho aggiornato il DE ieri mattina sperando in qualche miglioramento ma poi l’ho subito rimosso perché ha generato diversi problemi, comunque il problema dell’avvio è ben antecedente a questo aggiornamento.

#11

Questo cosa dice?

# systemd-analyze critical-chain firewalld.service --no-pager
#12

Buongiorno.
@arkanoid questo il risultato:

[code][root@localhost massimo]# systemd-analyze critical-chain firewalld.service --no-pager
The time after the unit is active or started is printed after the “@” character.
The time the unit takes to start is printed after the “+” character.

firewalld.service +11.080s
└─polkit.service @17.356s +4.760s
└─basic.target @14.976s
└─dnf-makecache.timer @14.976s
└─sysinit.target @14.916s
└─systemd-update-utmp.service @14.874s +41ms
└─auditd.service @14.369s +497ms
└─systemd-tmpfiles-setup.service @14.164s +199ms
└─fedora-import-state.service @13.831s +326ms
└─local-fs.target @13.821s
└─boot.mount @13.528s +292ms
└─systemd-fsck@dev-disk-by\x2duuid-dcf30501\x2d8b9a\x2d458a\x2d96c0\x2d9a672e81890f.service @12.872s +625ms
└─local-fs-pre.target @12.866s
└─systemd-tmpfiles-setup-dev.service @3.070s +1.412s
└─kmod-static-nodes.service @2.657s +404ms
└─systemd-journald.socket
└─-.slice[/code]
Chiedo scusa, una curiosità: anche qui vedo delle righe evidenziate in rosso, hanno un significato particolare? (Mi piace sapere le cose :D)
Grazie mille

#13

Le righe evidenziate in rosso, sono quelle con il “+”, ossia quelle che aggiungono del tempo al boot del sistema.

La seguente, non è una soluzione, ma un tentativo di identificare la causa del problema.

  1. Prova temporaneamente a disabilitare il servizio firewalld:
# systemctl disable firewalld.service
  1. Riavvia e verifica il comportamento del sistema. Mostra quindi i seguenti output:
$ systemd-analyze time 
$ systemd-analyze critical-chain --no-pager
  1. Successivamente, riabilita comunque il servizio in questione, in attesa di ulteriori prove.
# systemctl enable firewalld.service
#14

Buongiorno.
@arkanoid, ecco i risultati:

questo con firewalld attivo (ho pensato di aggiungerlo per completezza d’informazioni):

[massimo@localhost ~]$ systemd-analyze time Startup finished in 1.655s (kernel) + 8.593s (initrd) + 30.839s (userspace) = 41.088s

questo disattivato:

[massimo@localhost ~]$ systemd-analyze time Startup finished in 2.642s (kernel) + 7.283s (initrd) + 22.728s (userspace) = 32.653s
e questo l’altro

[code][massimo@localhost ~]$ systemd-analyze critical-chain --no-pager
The time after the unit is active or started is printed after the “@” character.
The time the unit takes to start is printed after the “+” character.

graphical.target @22.717s
└─multi-user.target @22.717s
└─abrt-ccpp.service @21.486s +1.230s
└─abrtd.service @18.197s +3.259s
└─livesys.service @15.082s +3.062s
└─basic.target @15.049s
└─sockets.target @15.049s
└─dbus.socket @15.049s
└─sysinit.target @15.020s
└─systemd-update-utmp.service @14.984s +36ms
└─auditd.service @14.469s +506ms
└─systemd-tmpfiles-setup.service @14.281s +179ms
└─fedora-import-state.service @13.854s +420ms
└─local-fs.target @13.846s
└─boot.mount @13.604s +242ms
└─systemd-fsck@dev-disk-by\x2duuid-dcf30501\x2d8b9a\x2d458a\x2d96c0\x2d9a672e81890f.service @12.631s +949ms
└─local-fs-pre.target @12.624s
└─lvm2-monitor.service @2.762s +2.579s
└─lvm2-lvmetad.service @3.366s
└─lvm2-lvmetad.socket @2.679s
└─-.mount
└─system.slice
└─-.slice[/code]
Ti ringrazio molto per l’attenzione in questo problema e per la spiegazione che mi hai dato riguardo alle righe rosse, proprio non ci avevo fatto caso che queste erano contrassegnate anche dal segno “+”. Mi verrebbe da porre delle domande per soddisfare delle curiosità su questo segno, ma andiamo OT (magari cercando nella ricca Documentazione di questo Forum trovo già le risposte).
Grazie ancora.

#15

Puoi disabilitare il servizio livesys:

# systemctl disable livesys.service

Per il resto… Non credo che una quarantina di secondi siano tempi improponibili per un hard disk meccanico (non SSD). Disabilitando firewalld.service salvi qualche minuto, ma non è quello che influenza il processo, quanto appunto la lentezza del disco.

Piuttosto, 18 secondi tra login e desktop usabile sì, mi sembrano un’eternità. Hai provato a creare un utente di prova, per vedere se il problema persiste?

#16

Buongiorno.
@arkanoid, ti ringrazio molto, ho seguito le tue indicazioni ma il tempo non è variato di molto. Sicuramente i tempi per un hard disk meccanico sono onesti, ma come ho scritto all’inizio sono peggiorati dai primi tempi ed è per questo che volevo vedere se era possibile riportarlo a tale valore in modo semplice e veloce. Siccome già mi frulla l’idea di cambiare il disco con un ssd, è quindi meglio lasciar perdere per ora e di non lamentarmi :rolleyes: più per questa tempistica :smiley:
Piccolo OT. Certo che leggendo i post sulla migrazione ad un SSD mi sono un poco raffreddato per i problemi che potrebbero nascere. Fine OT

Scusami se ti ho fatto perdere del tempo, grazie ancora per la tua disponibilità e … Auguri di Buon Natale!