Re: mpv won't play video : "Consider fixing your graphic drivers"
Le 2023-12-20 20:42, Mihai Popescu a écrit : Please post your dmesg. If you don't know what it is or how to get it please search the internet. Tell the list how the /home/media is mounted. Again , if you don't know how ... search the internet. If you are using some configuration options inside a file for mpv please list them here. I don't think someone on this list is an expert in paranormal nor telepathy guessing and even there is someone it won't be for free :) . You didn't forward your response email to my address ! Hence my late reply. The /home/media is a regular mountpoint, I don't think it is the cause for the problem/bug since it also happens when reading file stored in my home folder or from the internet. I don't use specific configuration options for mpv, the bug has been happening ever since I installed and used both openbsd and mpv. Here's my dmesg: OpenBSD 7.4-current (GENERIC.MP) #1607: Thu Jan 18 00:25:09 MST 2024 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8449818624 (8058MB) avail mem = 8172941312 (7794MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xda571018 (40 entries) bios0: vendor American Megatrends Inc. version "4.6.5" date 11/11/2013 bios0: CLEVO CO. W240EU/W250EUQ/W270EUQ efi0 at bios0: UEFI 2.3.1 efi0: American Megatrends rev 0x4028d acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG SSDT HPET SSDT SSDT SSDT DMAR BGRT acpi0: wakeup devices P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, 2693.99 MHz, 06-2a-07, patch 002f cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, 2694.08 MHz, 06-2a-07, patch 002f cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, 2694.13 MHz, 06-2a-07, patch 002f cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, 2694.12 MHz, 06-2a-07, patch 002f cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus -1 (RP02) acpiprt3 at acpi0: bus 2 (RP03) acpiprt4 at acpi0: bus 3 (RP04) acpiec0 at acpi0 acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x acpicmos0 at acpi0 acpibtn0 at acpi0: PWRB(wakeup) acpibtn1 at acpi0: SLPB(wakeup)
Re: disk not found after first reboot
On Jan 20 17:48:01, i...@lyberth.dk wrote: > Installation goes just fine. I sellect the disk (whole disk) auto > partition, create user, install the files. At the end it asks to reboot > halt or go to shell. No error messages, i just reboot, and get the no > bootable device found message You are rebooting with the usb install media out, right? If are using GPT, have you tried MBR? Boot the install media again, but don't reinstall; go to shell and get the output of fdisk and disklabel on the _target_ disk, i.e. the one you installed on.
Re: disk not found after first reboot
On Jan 20 16:43:54, i...@lyberth.dk wrote: > I had the disk in my windows pc, had diskmgr make a gpt drive of it and > then i could use the disk in OoenBsd. As I said: don't complicate it with other OSes. You don't need to massage your disk with win diskmgr prior to an openbsd installation; the installer will take care of the paritioning. So, reinstall anew; what do the last lines of the successfull install say?
Re: any terminal emulator will default to root folder instead of $HOME
On 2024-01-18 21:33, Sylvain Saboua wrote: I have been using KDE/Plasma on openbsd since last week-end. Amongst other bugs, mostly minor, which I should also report, there is this one : when opening an new instance of konsole, Plasma's terminal emulator program, the fallback folder location will be in / instead of $HOME (in my case /home/sylvain). How to reproduce to bug : open a new konsole instance and type : $pwd / $ This also happens when using (suckless') st or (default) xterm. I did not have this problem with st and (openbsd's) cwm on the same openbsd installation (before upgrading to kde packages) Thank you Your ~/.profile should have a line that cd to /
Re: any terminal emulator will default to root folder instead of $HOME
Le 2024-01-20 11:53, Rafael Sadowski a écrit : On Thu Jan 18, 2024 at 03:33:48PM +0100, Sylvain Saboua wrote: I have been using KDE/Plasma on openbsd since last week-end. Amongst other bugs, mostly minor, which I should also report, there is this one : when opening an new instance of konsole, Plasma's terminal emulator program, the fallback folder location will be in / instead of $HOME (in my case /home/sylvain). How to reproduce to bug : open a new konsole instance and type : $pwd / $ This also happens when using (suckless') st or (default) xterm. I did not have this problem with st and (openbsd's) cwm on the same openbsd installation (before upgrading to kde packages) Thank you -- Sylvain Saboua linktr.ee/Sylvain How do you start kde plasma? Have you read: /usr/local/share/doc/pkg-readmes/kde-plasma ? I have read the readme and simply copy-pasted the indicated lines in my .xsession (this is an extract from the files, last lines) : export XDG_RUNTIME_DIR=/tmp/run/$(id -u) if [ ! -d $XDG_RUNTIME_DIR ]; then mkdir -m 700 -p $XDG_RUNTIME_DIR fi export QT_FORCE_STDERR_LOGGING=1 export XDG_CURRENT_DESKTOP=KDE export DESKTOP_SESSION=plasma export QT_FORCE_STDERR_LOGGING=1 /usr/local/bin/startplasma-x11 > ~/.startplasma-x11.log 2>&1 -- Sylvain Saboua linktr.ee/Sylvain
Re: any terminal emulator will default to root folder instead of $HOME
Le 2024-01-20 11:59, hahahahacker2...@airmail.cc a écrit : On 2024-01-18 21:33, Sylvain Saboua wrote: I have been using KDE/Plasma on openbsd since last week-end. Amongst other bugs, mostly minor, which I should also report, there is this one : when opening an new instance of konsole, Plasma's terminal emulator program, the fallback folder location will be in / instead of $HOME (in my case /home/sylvain). How to reproduce to bug : open a new konsole instance and type : $pwd / $ This also happens when using (suckless') st or (default) xterm. I did not have this problem with st and (openbsd's) cwm on the same openbsd installation (before upgrading to kde packages) Thank you Your ~/.profile should have a line that cd to / you mean that cd to $HOME or /home/sylvain ? There is no such cd / in my .profile. This file on my installation is very basic : $more .profile # $OpenBSD: dot.profile,v 1.7 2020/01/24 02:09:51 okan Exp $ # # sh/ksh initialization PATH=$HOME/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/games export PATH HOME TERM export ENV=$HOME/.kshrc export LC_CTYPE=en_US.UTF-8 $more .kshrc . /etc/ksh.kshrc export PS1=\$ export HISTCONTROL=ignoredups export HISTFILE=$HOME/.history export HISTSIZE=5000 export CLICOLOR=1 ... (stripped out aliases definitions) $ Note that the problem/bug is absent with yakuake : opening the terminal panel with F12 and typing pwd accurately displays /home/sylvain -- Sylvain Saboua linktr.ee/Sylvain
Re: any terminal emulator will default to root folder instead of $HOME
On Thu Jan 18, 2024 at 03:33:48PM +0100, Sylvain Saboua wrote: > I have been using KDE/Plasma on openbsd since last week-end. > > Amongst other bugs, mostly minor, which I should also report, > there is this one : when opening an new instance of konsole, > Plasma's terminal emulator program, the fallback folder location > will be in / instead of $HOME (in my case /home/sylvain). > > How to reproduce to bug : open a new konsole instance and type : > > $pwd > / > $ > > This also happens when using (suckless') st or (default) xterm. > > I did not have this problem with st and (openbsd's) cwm on the > same openbsd installation (before upgrading to kde packages) > > Thank you > -- > Sylvain Saboua > linktr.ee/Sylvain > How do you start kde plasma? Have you read: /usr/local/share/doc/pkg-readmes/kde-plasma ?
Re: disk not found after first reboot
On Sat, Jan 20, 2024 at 10:34:25AM +0100, Jan Stary wrote: > You should need to dd anything as a part of installation, I think you meant 'should NOT'. > and zeroing out a disk will surely not fix you booting problem. Agreed, in this case it's very unlikely to be necessary or useful to zero out the disk. Occasionally it's possible to encounter a BIOS which doesn't like particular things in the MBR or whatever, and hangs at boot time when it accesses a disk that has such an MBR. In those cases, zeroing out the MBR on another machine is a useful procedure. In almost all other install problem cases it is not. Additionally, for the benefit of the list archvies, we should clarify that we're talking about dd'ing zeros across the disk here. There are other valid reasons that you might want to write _random_ data across the whole disk as part of a new installation. So this is _not_ a case of, 'any install instructions that involve using dd are automatically wrong'. > No. If you're having beginner problems, start with > a dedicated machine where nothing matters and practice there. The OP said that he uses his 'favorite OS', (which I am assuming is OpenBSD), on a firewall, so presumably he is not a complete beginner. If possible, I would do a full install of OpenBSD to a USB drive on another machine, then try to boot that on the laptop. If it works, then we can easily get dmesg output, etc, and start to diagnose the real problem. > In particular, don't bring other OSes into it. Agreed.
Re: disk not found after first reboot
> > /dev/sd0c represents the whole drive, so dd should be pointed at it. > > You should need to dd anything "Shouldn't", obviously.
Re: disk not found after first reboot
On Jan 20 05:12:40, nothingn...@citycable.ch wrote: > > On 19/01/2024 01:38, Isak Lyberth wrote: > > Hello guys, I am sorry to bother you with such a basic question. > > After many years of only using my favorite OS on my firewall, I have > > decided to install OpenBSD 7.4 on my Dell Latitude 7490 laptop, fitted with > > a 500 GB Samsung 980 (non pro) nvme disk i use the entire disk with auto > > partitioning). > > it had Windows on it when iÍ got it, I removed it and used Linux Mint for > > about a week and now i have installed OpenBSD 7.4. i have tried it a lot of > > times, clearing the disk with the dd if=/dev/zero of=/dev/sd0 command and > > also dd'd to sd0a, rsd0 and anything i could think of, i also tried exiting > > to shell and done some fdisk -iy sd0 (suggested on reddit) > > I have tested that I can get FreeBSD and Dragonfly bsd installed on the > > laptop. > > > > I will gladly supply more info if needed. > > But how do I get my laptop to boot OpenBSD? > > > > Kind regards Isak > > Hi, > > /dev/sd0c represents the whole drive, so dd should be pointed at it. You should need to dd anything as a part of installation, and zeroing out a disk will surely not fix you booting problem. > If you're having beginner > problems, try using gpartdisk from a Linux flash drive to create an A6 > partition and then installing OpenBSD. No. If you're having beginner problems, start with a dedicated machine where nothing matters and practice there. In particular, don't bring other OSes into it. Jan
