Porteus 5.0 Keeps Freezing

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Post Reply
JayMachine
Ronin
Ronin
Posts: 3
Joined: 15 Aug 2019, 16:37
Distribution: 5.0

Porteus 5.0 Keeps Freezing

Post#1 by JayMachine » 15 Aug 2019, 16:54

Hi,

I've just been evalulating Porteus 5.0, but it keeps freezing on me after a short time of use - it just locks up.

I have it installed on an 16gb SD card with a 2048mb .dat file. My PC is a Core-i5 with an Nvidia Card, 8 GB ram, wireless MS Mouse and wired keyboard, with good fibre - decent enough speck for any distro.

I had issues with earlier versions too, but I managed to at least run the OS for 5 minutes or more, but on version 5.0 I'm lucky to get 5 minutes before it freezes on me and I have to manually turn off the PC.

The only changes I've made apart from the .dat file, is to add wallpaper and update Firefox to the latest and add a few addons. This took ages as Porteus kept freezing while I customised, it must have frozen at least 10 times just adding a few addons. It feels totaly unusable, if it was stable, then it would be fantasic.

It doesn't seem to matter what I do, whether it's browser or system based, Porteus just freezes constantly.

I wondered if it was something to do with the defualt Nvidia driver? Otherwise I have no idea.

What can I do to fix?

Cheers for any help.

User avatar
Blaze
DEV Team
DEV Team
Posts: 2541
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus 5.0 Keeps Freezing

Post#2 by Blaze » 15 Aug 2019, 17:13

Hi JayMachine.
Welcome on the board!

1st - can you share this log

Code: Select all

su
toor
dmesg | egrep -i "nouveau|error|faile|warn|video|X11|issue|resolve|found|bug|ignore|ati|radeon|intel|amd"
cat /var/log/Xorg.0.log | egrep -i "nouveau|error|faile|warn|video|X11|issue|resolve|found|bug|ignore|ati|radeon|intel|amd"
2nd - do you tried another fs (for example ext2 or ext4)?

3rd - can you try another boot device instead SD card?

Thanks.
Linux 5.3.0-rc3-porteus #1 SMP Mon Aug 5 11:28:55 UTC 2019 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

User avatar
Ed_P
Contributor
Contributor
Posts: 5035
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Porteus 5.0 Keeps Freezing

Post#3 by Ed_P » 15 Aug 2019, 17:19

With your changes= cheatcode try adding the EXIT option to see if it helps. For example changes=EXIT:/porteussave.dat.
Ed

JayMachine
Ronin
Ronin
Posts: 3
Joined: 15 Aug 2019, 16:37
Distribution: 5.0

Porteus 5.0 Keeps Freezing

Post#4 by JayMachine » 15 Aug 2019, 19:52

Blaze,

Hi, this took some time as I couldn't copy the text quick enough before it froze up. I installed Porteus 5.0 on another different 8GB SD Card, and I just added Firefox into the Modules folder before boot to save time. But even without adding a .dat file I'm having the same issues of freezing up. I doubt I even get 4 minutes before it locks up on me.

I hope the logs can help shed some light on things.

The SD Cards were formatted to fat32 from Windows 10.

My graphics card is an Nvidia Geforce GTX 550 ti.

Code: Select all

[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.001975] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[    0.007398] found SMP MP-table at [mem 0x000fcd40-0x000fcd4f]
[    0.008315] RAMDISK: [mem 0x7ff36000-0x7fffefff]
[    0.008319] ACPI: Early table checksum verification disabled
[    0.011352] No NUMA configuration found
[    0.047908] Using ACPI (MADT) for SMP configuration information
[    0.047912] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
[    0.127629] Kernel/User page tables isolation: enabled
[    0.127676] rcu: Preemptible hierarchical RCU implementation.
[    0.140602] Calibrating delay loop (skipped), value calculated using timer frequency.. 5786.98 BogoMIPS (lpj=2893493)
[    0.142546] Spectre V2 : Mitigation: Full generic retpoline
[    0.142547] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.142547] Speculative Store Bypass: Vulnerable
[    0.142717] Freeing SMP alternatives memory: 20K
[    0.143593] smpboot: CPU0: Intel(R) Core(TM) i5-4460S CPU @ 2.90GHz (family: 0x6, model: 0x3c, stepping: 0x3)
[    0.148611] Performance Events: PEBS fmt2+, Haswell events, 16-deep LBR, full-width counters, Intel PMU driver.
[    0.150608] rcu: Hierarchical SRCU implementation.
[    0.162612] x86: Booting SMP configuration:
[    0.180844] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
[    0.180844] PCI: Using configuration type 1 for base access
[    0.180844] mtrr: corrected configuration.
[    0.182649] ACPI: Added _OSI(Linux-Dell-Video)
[    0.192423] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.194289] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.206662] videodev: Linux video capture interface: v2.00
[    0.211647] pnp: PnP ACPI: found 7 devices
[    0.249573] pci 0000:01:00.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[    0.323293] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[    0.325006] intel_idle: MWAIT substates: 0x42120
[    0.325007] intel_idle: v0.4.1 model 0x3C
[    0.325134] intel_idle: lapic_timer_reliable_states 0xffffffff
[    0.334837] Copyright (c) 1999-2008 LSI Corporation
[    0.334971] ehci-pci 0000:00:1a.0: debug port 2
[    0.345584] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01
[    0.345763] hub 1-0:1.0: USB hub found
[    0.345966] ehci-pci 0000:00:1d.0: debug port 2
[    0.356586] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01
[    0.356763] hub 2-0:1.0: USB hub found
[    0.358204] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01
[    0.358355] hub 3-0:1.0: USB hub found
[    0.359317] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.01
[    0.359468] hub 4-0:1.0: USB hub found
[    0.359745] i8042: PNP: No PS/2 controller found.
[    0.360361] intel_pstate: Intel P-state driver initializing
[    0.364689]   No soundcards found.
[    0.646985] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    0.654019] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    0.799929] usb 1-1: New USB device found, idVendor=8087, idProduct=8008, bcdDevice= 0.04
[    0.800646] hub 1-1:1.0: USB hub found
[    0.808201] usb 2-1: New USB device found, idVendor=8087, idProduct=8000, bcdDevice= 0.04
[    0.808631] hub 2-1:1.0: USB hub found
[    0.808883] usb 3-2: New USB device found, idVendor=08bb, idProduct=2902, bcdDevice= 1.00
[    1.113850] usb 3-3: New USB device found, idVendor=0bda, idProduct=0157, bcdDevice=57.13
[    1.319683] tsc: Refined TSC clocksource calibration: 2893.299 MHz
[    1.357798] usb 3-5: New USB device found, idVendor=045e, idProduct=07fd, bcdDevice= 3.15
[    1.716536] usb 3-9: New USB device found, idVendor=2a7a, idProduct=4103, bcdDevice= 0.01
[   15.362875] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20190215/utaddress-204)
[   15.362879] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   15.362882] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20190215/utaddress-204)
[   15.362884] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   15.362885] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20190215/utaddress-204)
[   15.362886] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20190215/utaddress-204)
[   15.362888] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   15.362889] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20190215/utaddress-204)
[   15.362890] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20190215/utaddress-204)
[   15.362892] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   15.362893] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   15.695491] snd_hda_intel 0000:01:00.1: Disabling MSI
[   15.695496] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[   15.794028] AES CTR mode by8 optimization enabled
[   15.804680] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[   15.804730] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[   15.804774] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
[   15.804826] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
[   15.804865] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
[   15.933988] nouveau 0000:01:00.0: NVIDIA GF116 (0cf200a1)
[   15.981211] intel_rapl: Found RAPL domain package
[   15.981212] intel_rapl: Found RAPL domain core
[   15.981213] intel_rapl: Found RAPL domain dram
[   15.981215] intel_rapl: RAPL package 0 domain package locked by BIOS
[   15.981218] intel_rapl: RAPL package 0 domain dram locked by BIOS
[   16.065170] nouveau 0000:01:00.0: bios: version 70.26.20.00.02
[   16.087581] nouveau 0000:01:00.0: fb: 1024 MiB GDDR5
[   16.148192] nouveau 0000:01:00.0: DRM: VRAM: 1024 MiB
[   16.148193] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[   16.148196] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[   16.148197] nouveau 0000:01:00.0: DRM: DCB version 4.0
[   16.148199] nouveau 0000:01:00.0: DRM: DCB outp 00: 01000312 00020030
[   16.148200] nouveau 0000:01:00.0: DRM: DCB outp 01: 04000310 00020030
[   16.148201] nouveau 0000:01:00.0: DRM: DCB outp 02: 08011382 00020030
[   16.148201] nouveau 0000:01:00.0: DRM: DCB outp 03: 02011380 00020030
[   16.148202] nouveau 0000:01:00.0: DRM: DCB outp 04: 02022362 00020010
[   16.148203] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001030
[   16.148204] nouveau 0000:01:00.0: DRM: DCB conn 01: 00010130
[   16.148205] nouveau 0000:01:00.0: DRM: DCB conn 02: 00002261
[   16.148885] nouveau 0000:01:00.0: DRM: MM: using COPY0 for buffer copies
[   16.224748] nouveau 0000:01:00.0: DRM: allocated 2560x1440 fb: 0x60000, bo 000000008937d243
[   16.225756] fbcon: nouveaufb (fb0) is primary device
[   16.354581] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[   16.361923] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
[   18.783934] Generic Realtek PHY r8169-300:00: attached PHY driver [Generic Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
[   28.494225] snd_hda_intel 0000:00:1b.0: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
[  112.062104] usb 3-6: New USB device found, idVendor=0781, idProduct=5575, bcdDevice= 1.27

>>>>>>>>>>>>>

[    18.474] Build Operating System: Slackware 15.0 Slackware Linux Project
[    18.474] Current Operating System: Linux porteus.example.net 5.1.5-porteus #1 SMP PREEMPT Sun May 26 17:25:39 Local time zone must be set-- x86_64
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    18.478] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
	Using a default monitor configuration.
[    18.481] (==) Automatically adding devices
[    18.481] (==) Automatically enabling devices
[    18.481] (==) Automatically adding GPU devices
[    18.481] (==) Automatically binding GPU devices
[    18.512] 	X.Org ANSI C Emulation: 0.4
[    18.512] 	X.Org Video Driver: 24.0
[    18.580] (II) Module glx: vendor="X.Org Foundation"
[    18.715] (II) Module modesetting: vendor="X.Org Foundation"
[    18.715] 	Module class: X.Org Video Driver
[    18.715] 	ABI class: X.Org Video Driver, version 24.0
[    18.727] (II) Module fbdev: vendor="X.Org Foundation"
[    18.727] 	Module class: X.Org Video Driver
[    18.727] 	ABI class: X.Org Video Driver, version 24.0
[    18.755] (II) Module vesa: vendor="X.Org Foundation"
[    18.755] 	Module class: X.Org Video Driver
[    18.755] 	ABI class: X.Org Video Driver, version 24.0
[    18.776] (II) Module fbdevhw: vendor="X.Org Foundation"
[    18.776] 	ABI class: X.Org Video Driver, version 24.0
[    18.776] (II) modeset(0): Creating default Display subsection in Screen section
[    18.833] (II) Module glamoregl: vendor="X.Org Foundation"
[    18.833] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    20.844] (II) modeset(0): glamor X acceleration enabled on NVCF
[    20.915] (II) modeset(0): Not using default mode "2048x1152" (bad mode clock/interlace/doublescan)
[    20.915] (II) modeset(0): Modeline "2048x1152"x60.0  302.50  2048 2072 2088 2128  1152 1153 1156 1185 doublescan +hsync -vsync (142.2 kHz d)
[    20.915] (II) modeset(0): Modeline "2048x1152"x59.9  197.00  2048 2184 2400 2752  1152 1155 1160 1195 -hsync +vsync (71.6 kHz d)
[    20.915] (II) modeset(0): Modeline "2048x1152"x59.9  156.75  2048 2096 2128 2208  1152 1155 1160 1185 +hsync -vsync (71.0 kHz d)
[    20.932] (II) Module fb: vendor="X.Org Foundation"
[    20.932] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    21.016] (II) modeset(0): [DRI2]   DRI driver: nouveau
[    21.016] (II) modeset(0): [DRI2]   VDPAU driver: nouveau
[    21.016] (II) Initializing extension XVideo
[    21.016] (II) Initializing extension XVideo-MotionCompensation
[    21.019] (II) AIGLX: Loaded and initialized nouveau
[    21.153] (II) Module evdev: vendor="X.Org Foundation"
[    21.153] (--) evdev: Power Button: Found keys
[    21.171] (--) evdev: Power Button: Found keys
[    21.173] (--) evdev: Burr-Brown from TI               USB Audio CODEC : Found keys
[    21.173] (--) evdev: Microsoft Microsoft Nano Transceiver 1.1: Found keys
[    21.173] (--) evdev: Microsoft Microsoft Nano Transceiver 1.1 Consumer Control: Found 1 mouse buttons
[    21.173] (--) evdev: Microsoft Microsoft Nano Transceiver 1.1 Consumer Control: Found scroll wheel(s)
[    21.173] (--) evdev: Microsoft Microsoft Nano Transceiver 1.1 Consumer Control: Found relative axes
[    21.173] (II) evdev: Microsoft Microsoft Nano Transceiver 1.1 Consumer Control: Forcing relative x/y axes to exist.
[    21.173] (--) evdev: Microsoft Microsoft Nano Transceiver 1.1 Consumer Control: Found absolute axes
[    21.173] (--) evdev: Microsoft Microsoft Nano Transceiver 1.1 Consumer Control: Found keys
[    21.174] (II) evdev: Microsoft Microsoft Nano Transceiver 1.1 Consumer Control: initialized for relative axes.
[    21.174] (**) Microsoft Microsoft Nano Transceiver 1.1 Consumer Control: (accel) keeping acceleration scheme 1
[    21.174] (**) Microsoft Microsoft Nano Transceiver 1.1 Consumer Control: (accel) acceleration profile 0
[    21.174] (**) Microsoft Microsoft Nano Transceiver 1.1 Consumer Control: (accel) acceleration factor: 2.000
[    21.174] (**) Microsoft Microsoft Nano Transceiver 1.1 Consumer Control: (accel) acceleration threshold: 4
[    21.174] (--) evdev: Microsoft Microsoft Nano Transceiver 1.1 System Control: Found keys
[    21.174] (--) evdev: Microsoft Microsoft Nano Transceiver 1.1: Found keys
[    21.175] (--) evdev: Microsoft Microsoft Nano Transceiver 1.1: Found 9 mouse buttons
[    21.175] (--) evdev: Microsoft Microsoft Nano Transceiver 1.1: Found scroll wheel(s)
[    21.175] (--) evdev: Microsoft Microsoft Nano Transceiver 1.1: Found relative axes
[    21.175] (--) evdev: Microsoft Microsoft Nano Transceiver 1.1: Found x and y relative axes
[    21.175] (II) evdev: Microsoft Microsoft Nano Transceiver 1.1: initialized for relative axes.
[    21.175] (**) Microsoft Microsoft Nano Transceiver 1.1: (accel) keeping acceleration scheme 1
[    21.175] (**) Microsoft Microsoft Nano Transceiver 1.1: (accel) acceleration profile 0
[    21.175] (**) Microsoft Microsoft Nano Transceiver 1.1: (accel) acceleration factor: 2.000
[    21.175] (**) Microsoft Microsoft Nano Transceiver 1.1: (accel) acceleration threshold: 4
[    21.175] (--) evdev: U: Found keys
[    21.176] (--) evdev: U System Control: Found keys
[    21.176] (--) evdev: U Consumer Control: Found keys
[    21.176] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event11)
[    21.176] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event12)
[    21.177] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event13)
[    21.177] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event14)
[    21.177] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event15)


Thanks for any help.

nanZor
Samurai
Samurai
Posts: 185
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.0 RC1 XFCE
Location: Los Angeles

Porteus 5.0 Keeps Freezing

Post#5 by nanZor » 15 Aug 2019, 21:57

Just for kicks to reduce variables, does it lockup with a corded-mouse instead of wireless?

And later on at some point, dmesg will complain that you should probably run an fsck-vfat on that drive that gets shut down cold. I boot Porteus to ram, unmount the boot drive, fsck it.

Here's where the EXIT: option comes in handy when hard poweroffs helps. :) In other words, I've been there when testing Porteus on cranky hardware too.
That's a UNIX book - cool. -Garth

JayMachine
Ronin
Ronin
Posts: 3
Joined: 15 Aug 2019, 16:37
Distribution: 5.0

Porteus 5.0 Keeps Freezing

Post#6 by JayMachine » 16 Aug 2019, 12:54

Well I managed to get hold of a wired mouse, I didn't have one spare so had to buy one, paid too much for a retractable cable one, all I could find in the shops - maybe it'll be useful one day for something - cable is really short. Anyway, no, same issue with freezing on Porteus - so that's removed from the list.

I tried an install on a new USB 32GB SandDisk Pendrive yesterday evening, but it wouldn't boot for some reason. Out of frustration today I installed Porteus on another USB Pendrive, this time a 16GB SandDisk, and it's working. I've done the various mods, like add the latest Firefox, added the .dat file and edited the config file, set the preferences. So far no locking up - I'll test further.

For me, looks like Porteus doesn't like SD Cards sadly, either that, or my system doesn't like Porteus on an SD Card.

Anyway, I'll see how I get on - thanks for the help!

nanZor
Samurai
Samurai
Posts: 185
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.0 RC1 XFCE
Location: Los Angeles

Porteus 5.0 Keeps Freezing

Post#7 by nanZor » 16 Aug 2019, 21:26

Jay - I apologize - I read the thread too fast to realize you are freezing with an SD card boot, not a usb.

Unfortunately, a lot of sd card hardware can be flaky. For instance, my Intel NUC has no problem whatsoever booting and using sd cards with Linux. However, a very cheep-n-cheerful little off brand mini-pc does exactly what yours does - crash after a small amount of time.

In some cases, merely inserting the sd card will bring the machine down, but not on the Intel NUC.

One thing you can do to prove this, is to get a quality SD <> USB adapter dongle, and try booting your sd card from that (it will show up as an sdX, and not an mmc device). I'll bet it works fine, pointing to the sd-card hardware in that particular unit.

If you suspect a funky sdcard format, you can also try the formatter (for mac or windows) right from the SDcard association itself:

https://www.sdcard.org/downloads/formatter/index.html

But no matter what, some sd-card hardware is just on the flaky side - no matter how hard linux tries to use it. If you try an adapter dongle to usb, I'll bet your card boots fine, although a usb dongle is probably not what you want to use anyway, but it will prove the point.
That's a UNIX book - cool. -Garth

nanZor
Samurai
Samurai
Posts: 185
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.0 RC1 XFCE
Location: Los Angeles

Porteus 5.0 Keeps Freezing

Post#8 by nanZor » 16 Aug 2019, 21:48

Options - because I've been there ...

You may try using optional kernel bootcodes to find the ones that *might* tame the sdcard hardware, like noapic, nolapic, noacpi, etc etc, but might have performance implications elsewhere. And in the meantime during all this testing, you are successively crashing the sdcard itself.

So much so that everytime you peek at dmesg, you see it recommending you fsck the drive because it wasn't dismounted properly. Over and over until it refuses to boot.

Option: if just the size of a thumbdrive is an issue, and you are willing to use an available usb port, you may want to consider the little "nub" sized usb sticks, like Sandisk UltraFits that barely peek out of the port.
That's a UNIX book - cool. -Garth

User avatar
Ed_P
Contributor
Contributor
Posts: 5035
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Porteus 5.0 Keeps Freezing

Post#9 by Ed_P » 17 Aug 2019, 20:04

Depending on how they are used some Ultrafits get very hot.
Ed

User avatar
Blaze
DEV Team
DEV Team
Posts: 2541
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Porteus 5.0 Keeps Freezing

Post#10 by Blaze » 17 Aug 2019, 20:40

JayMachine, not bad if you check BIOS updates for motherboard of your PC on the official website.
If it have a new BIOS, try to burn it and test Porteus 5.0 on freezing. Be careful!

But the better solution is use ext2 partition on your SD Card or USB Pendrive. For it:
  1. Boot up Porteus from your USB Pendrive where is no freezes and then connect your SD Card or USB Pendrive where you have freezing.
  2. Find and open in start menu GParted. Format this SD Card to ext2.
  3. Download iso file with Porteus 5.0 RC1 http://ftp.nluug.nl/os/Linux/distr/port ... teus-v5.0/
  4. Open terminal and run these commands:

    Code: Select all

    su
    toor
    # type here your path and name of porteus.iso file
    mloop /path/to/porteus.iso
    # define a section with a SD Card
    df -h
    # sdXN section of the SD Card on which you want to install Porteus
    cp -a /mnt/loop/* /mnt/sdXN/
    sync
    cd /mnt/sdXN/boot/
    ./Porteus-installer-for-Linux.com
    # enter ok in the English layout and press Enter
    uloop
  5. Boot up from this SD Card and test Porteus 5.0 on freezing.
Note! .dat file and cheat code for .dat file are not need.
Linux 5.3.0-rc3-porteus #1 SMP Mon Aug 5 11:28:55 UTC 2019 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

Post Reply