potentiallynotfelix @ potentiallynotfelix @lemmy.fish

Posts

43

Comments

438

Joined

10 mo. ago

hi, a bios version revert solved the issue. thank you for the help!

a bios update revert fixed this. you were correct that it was mobo related.

exif is stripped when uploading to lemmy, I believe

Thank you!

Flashing an older bios seemed to succeed! I gave it 14 hours or so before attempting a reboot, and if seemed to reboot without stalling. I'll give it a few more days now and try another, but that seemed to have fixed it.

halt -p did nothing different. still hung on shutdown.

average suv should have racks on top to strap it and depending on the model space in the back.

buy used. you aren't giving them anything more then.

Why not a graphene phone?

Only happened to me once

sudo systemctl reboot did the same. I'm starting to think this is bios related.

Agreed, lsmod | grep nouveau returns nothing, so I'm not concerned about nouveau or nvidia being the issue here.

sudo dmsetup info returns:

    
Name:              raven--vg-root
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        1
Event number:      0
Major, minor:      254, 0
Number of targets: 1
UUID: LVM-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Name:              raven--vg-swap_1
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        2
Event number:      0
Major, minor:      254, 1
Number of targets: 1
UUID: LVM-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

  

Yes, I've always made sure to use update-grub and checked cmdline to make sure it has the correct parameters. Regardless of acpi=force or acpi=off, it would still hang.

I retract my statement, this looks perfectly safe and effective.

Good luck transporting a couch on a motorbike.

I click the reboot button on cockpit, which issues a shutdown --reboot command as root. I agree that sleep state S5 is powered off. From the acpi docs:

A computer state where the computer consumes a minimal amount of power. No user mode or system mode code is run. This state requires a large latency in order to return to the Working state. The system’s context will not be preserved by the hardware. The system must be restarted to return to the Working state. It is not safe to disassemble the machine in this state.

This likely means my system is failing to reach that s5/g2 state.

can you elaborate on why you suspect this? The cockpit reboot or shutdown button uses the shutdown command directly along with a --reboot or --poweroff flag.

    
    onSubmit(event) {
        const Dialogs = this.context;
        const arg = this.props.shutdown ? "--poweroff" : "--reboot";
        if (!this.props.shutdown)
            cockpit.hint("restart");

        cockpit.spawn(["shutdown", arg, this.state.when, this.state.message], { superuser: "require", err: "message" })
                .then(this.props.onClose || Dialogs.close)
                .catch(e => this.setState({ error: e.toString() }));

        event.preventDefault();
        return false;
    }


  

(source)

thanks for the suggestion, could you elaborate on what this would do differently from the regular shutdown command that systemctl uses? thanks again