Re: Changing efi system partition
EFI can boot from any FAT partition on the drive. You can put any bootloader you want on that partition (usually it is the first) and EFI will be able to boot from it. Check your mobo documentation, but for me the BIOS menu includes an «Boot from» option, to select the EFI file from which to boot. Not knowing the OpenBSD specifics, it should boot even if you move it. If you have doubts, try to recreate your setup on a virtual machine and try there. Thanks for the help, but unfortunately it doesn't seem to be this easy. I tried to copy the bootloader onto the other ESP and set my linux bootloader to chainload it. It seems to boot but it tries to load the kernel from the wrong partition and complains about a missing /etc/boot.conf. This is weird as I don't have this file on my real install. Even if I had, the bootloader wouldn't be able to read it as I use disk encryption. I figured that the bootloader was missing CLI arguments so I tried to find out how to read efi variables from OpenBSD. This led me to a reddit post from 9 months ago[0], which claims that OpenBSD doesn't use efi variables and always assumes that it controls BOOTX64.efi. This means that I'll probably need to change things on the linux side. Either way, thanks again. [0] https://www.reddit.com/r/openbsd/comments/haxyey/efibootmgr_openbsd/
Re: 6.9 Current amd64 xfce seems to freeze and not respond to mouse clicks or keystrokes
On 4/10/21 2:48 PM, gwes wrote: > > > On 4/10/21 5:22 PM, Tom Smyth wrote: >> Hello, >> >> 1) issue does not occur with fvwm or with chrome running in fvwm >> >> so the issue seems to be confined to xfce, and I was running just 1 >> xfce terminal session >> 2) (so the issue is not related to chromium) >> >> Thanks >> >> >> O >> -- >> Kindest regards, >> Tom Smyth. >> > Hi Tom, > Some application that you can't see is grabbing focus and not letting go. > > On another OS using xfce (XUbuntu) the screensaver sometimes causes something > extremely similar. Mouse cursor moves but nothing else responds. > The workaround is to use control-alt-F1 to get a > plain console and ps -ax | grep screen then doas kill . > > If it's not a screensaver it's almost always a second browser copy. > I just find likely greedy candidates in the ps and kill until the problem > goes away. > > If the X server won't let you use control-alt-Fx to change screens you'll > have to ssh in. > > Geoff Steckel > That xfce screen saver issue also seems to exists on OpenBSD 6.8, as I've triggered it a number of times on my desktop. I've found that even with the locked screen (mouse can move and nothing else as described) I can still enter my password to unlock the screen saver, and then things usually work as expected -- if not, switching terminals with ctrl+alt+f1 and back with ctrl+alt+f5 seems to do the trick once the screen saver has been unlocked with my users password, with no need to kill the screen saver process. Regards, Jordan
Re: 6.9 Current amd64 xfce seems to freeze and not respond to mouse clicks or keystrokes
Hi Ian, Thanks for that it seems to be the screensaver that was causing the issue. do you have the screensaver enabled also ? in hind sight it doesn't appear to be a hardware issue (or virtual hardware issue ) thanks for your reply and feedback On Sat, 10 Apr 2021 at 23:52, Ian Darwin wrote: > > On Sat, Apr 10, 2021 at 10:22:17PM +0100, Tom Smyth wrote: > > Hello, > > > > 1) issue does not occur with fvwm or with chrome running in fvwm > > > > so the issue seems to be confined to xfce, and I was running just 1 > > xfce terminal session > > 2) (so the issue is not related to chromium) > > > > > > I'm running OpenBSD on an Oracle Virtualbox VM > > I run xfce all the time on -current on amd64 on real hardware and do > not have any such issue. -- Kindest regards, Tom Smyth.
Re: 6.9 Current amd64 xfce seems to freeze and not respond to mouse clicks or keystrokes
On Sat, Apr 10, 2021 at 10:22:17PM +0100, Tom Smyth wrote: > Hello, > > 1) issue does not occur with fvwm or with chrome running in fvwm > > so the issue seems to be confined to xfce, and I was running just 1 > xfce terminal session > 2) (so the issue is not related to chromium) > > > > I'm running OpenBSD on an Oracle Virtualbox VM I run xfce all the time on -current on amd64 on real hardware and do not have any such issue.
Re: 6.9 Current amd64 xfce seems to freeze and not respond to mouse clicks or keystrokes
On 4/10/21 5:22 PM, Tom Smyth wrote: Hello, 1) issue does not occur with fvwm or with chrome running in fvwm so the issue seems to be confined to xfce, and I was running just 1 xfce terminal session 2) (so the issue is not related to chromium) Thanks O -- Kindest regards, Tom Smyth. Hi Tom, Some application that you can't see is grabbing focus and not letting go. On another OS using xfce (XUbuntu) the screensaver sometimes causes something extremely similar. Mouse cursor moves but nothing else responds. The workaround is to use control-alt-F1 to get a plain console and ps -ax | grep screen then doas kill . If it's not a screensaver it's almost always a second browser copy. I just find likely greedy candidates in the ps and kill until the problem goes away. If the X server won't let you use control-alt-Fx to change screens you'll have to ssh in. Geoff Steckel
Re: 6.9 Current amd64 xfce seems to freeze and not respond to mouse clicks or keystrokes
Geoff, The force is strong with you :) Thanks that worked xfce-screensaver was active but I was not seeing the screen-saver Appreciate your help Tom Smyth On Sat, 10 Apr 2021 at 22:48, gwes wrote: > > > > On 4/10/21 5:22 PM, Tom Smyth wrote: > > Hello, > > > > 1) issue does not occur with fvwm or with chrome running in fvwm > > > > so the issue seems to be confined to xfce, and I was running just 1 > > xfce terminal session > > 2) (so the issue is not related to chromium) > > > > Thanks > > > > > > O > > -- > > Kindest regards, > > Tom Smyth. > > > Hi Tom, > Some application that you can't see is grabbing focus and not letting go. > > On another OS using xfce (XUbuntu) the screensaver sometimes causes > something > extremely similar. Mouse cursor moves but nothing else responds. > The workaround is to use control-alt-F1 to get a > plain console and ps -ax | grep screen then doas kill . > > If it's not a screensaver it's almost always a second browser copy. > I just find likely greedy candidates in the ps and kill until the > problem goes away. > > If the X server won't let you use control-alt-Fx to change screens you'll > have to ssh in. > > Geoff Steckel -- Kindest regards, Tom Smyth.
Re: 6.9 Current amd64 xfce seems to freeze and not respond to mouse clicks or keystrokes
Hello, 1) issue does not occur with fvwm or with chrome running in fvwm so the issue seems to be confined to xfce, and I was running just 1 xfce terminal session 2) (so the issue is not related to chromium) Thanks On Fri, 9 Apr 2021 at 19:09, Tom Smyth wrote: > > just to update this thread, > > 1) the mouse pointer still moves around but It cant seem to select a > window or text or any icon in a menu > > 2) i did increase the resolution using xrandr -s 1920x1080 at the > start of the session without issue > > 3) crhomium is open when this happens > > Thanks > > On Fri, 9 Apr 2021 at 19:33, Tom Smyth wrote: > > > > Hello > > > > 6.9 Current amd64 xfce seems to freeze and not respond to mouse > > clicks or keystrokes. I cant seem to change windows or enter text on > > the X terminal > > > > > > im running OpenBSD on an Oracle Virtualbox VM > > > > however + does work and im able to restart the x > > session using the console > > > > rcctl restart xenodm > > > > Ill try FVWM to see is it an X11 issue or an issue with xfce > > > > just raising it incase someone else has noticed this issue > > > > dmesg below > > > > OpenBSD 6.9 (GENERIC.MP) #458: Fri Apr 9 01:05:30 MDT 2021 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 8573091840 (8175MB) > > avail mem = 8297865216 (7913MB) > > random: good seed from bootblocks > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe1000 (10 entries) > > bios0: vendor innotek GmbH version "VirtualBox" date 12/01/2006 > > bios0: innotek GmbH VirtualBox > > acpi0 at bios0: ACPI 4.0 > > acpi0: sleep states S0 S5 > > acpi0: tables DSDT FACP APIC HPET MCFG SSDT > > acpi0: wakeup devices > > acpitimer0 at acpi0: 3579545 Hz, 32 bits > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 2304.35 MHz, 06-8e-0c > > cpu0: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,CX16,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,RDRAND,NXE,RDTSCP,LONG,LAHF,ABM,3DNOWP,ITSC,FSGSBASE,AVX2,INVPCID,RDSEED,CLFLUSHOPT,MD_CLEAR,L1DF > > cpu0: 256KB 64b/line 8-way L2 cache > > cpu0: smt 0, core 0, package 0 > > mtrr: CPU supports MTRRs but not enabled by BIOS > > cpu0: apic clock running at 1000MHz > > cpu1 at mainbus0: apid 1 (application processor) > > cpu1: Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 2304.08 MHz, 06-8e-0c > > cpu1: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,CX16,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,RDRAND,NXE,RDTSCP,LONG,LAHF,ABM,3DNOWP,ITSC,FSGSBASE,AVX2,INVPCID,RDSEED,CLFLUSHOPT,MD_CLEAR,L1DF > > cpu1: 256KB 64b/line 8-way L2 cache > > cpu1: smt 0, core 1, package 0 > > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins, remapped > > acpihpet0 at acpi0: 14318179 Hz > > acpimcfg0 at acpi0 > > acpimcfg0: addr 0xdc00, bus 0-63 > > acpiprt0 at acpi0: bus 0 (PCI0) > > acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 > > acpicmos0 at acpi0 > > acpibat0 at acpi0: BAT0 model "1" serial 0 type VBOX oem "innotek" > > acpiac0 at acpi0: AC unit online > > acpicpu0 at acpi0: C1(@1 halt!) > > acpicpu1 at acpi0: C1(@1 halt!) > > acpivideo0 at acpi0: GFX0 > > pci0 at mainbus0 bus 0 > > vga1 at pci0 dev 2 function 0 "VMware SVGA II" rev 0x00 > > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > > wsdisplay0: screen 1-5 added (80x25, vt100 emulation) > > em0 at pci0 dev 3 function 0 "Intel 82540EM" rev 0x02: apic 2 int 19, > > address 08:00:27:bd:cb:77 > > "InnoTek VirtualBox Guest Service" rev 0x00 at pci0 dev 4 function 0 > > not configured > > auich0 at pci0 dev 5 function 0 "Intel 82801AA AC97" rev 0x01: apic 2 > > int 21, ICH > > ac97: codec id 0x83847600 (SigmaTel STAC9700) > > audio0 at auich0 > > piixpm0 at pci0 dev 7 function 0 "Intel 82371AB Power" rev 0x08: apic 2 int > > 23 > > iic0 at piixpm0 > > pcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02 > > pciide0 at pci0 dev 31 function 1 "Intel 82371AB IDE" rev 0x01: DMA, > > channel 0 configured to compatibility, channel 1 configured to > > compatibility > > wd0 at pciide0 channel 0 drive 0: > > wd0: 128-sector PIO, LBA48, 131072MB, 268435456 sectors > > wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 > > atapiscsi0 at pciide0 channel 1 drive 0 > > scsibus1 at atapiscsi0: 2 targets > > cd0 at scsibus1 targ 0 lun 0: removable > > cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 > > ohci0 at pci0 dev 31 function 4 "Apple Intrepid USB" rev 0x00: apic 2 > > int 23, version 1.0 > > isa0 at pcib0 > > isadma0 at isa0 > > pckbc0 at isa0 port 0x60/5 irq 1 irq 12 > > pckbd0 at pckbc0 (kbd slot) > > wskbd0 at pckbd0: console keyboard, using wsdisplay0 > > pms0 at pckbc0 (aux slot) > > wsmouse0 at pms0 mux 0 > >
Changing efi system partition
Hello folks, I recently installed OpenBSD as a dualboot next to a Linux install. However, I didn't pay much attention to partitioning and created a new ESP. This means that my Linux bootloader can't find the OpenBSD bootloader to chainload it. Now I want to fix this situation. If I don't reinstall (which I don' want to), I need to move one bootloader onto the other ESP. Moving the Linux bootloader seems easier, but I'd like to know if I can do the same with the OpenBSD one. I could just try to move the executable but I'm not sure how the bootloader finds the partition to boot from and how sysupgrade finds the bootloader to upgrade it (if it does it at all, the man page didn't mention it). Does anybody know whether it's safe to just move the bootloader to a different partition? If so, can I rename it as well? BOOTX64.efi conflicts with my linux bootloader. I already tried to find out via boot(8) and boot_amd64(8) but they only talk about legacy BIOS. At first glance, man -k efi doesn't point to any useful pages either. I might've overlooked something though, I'm fairly new to OpenBSD. Thanks in advance, David
Re: Changing efi system partition
O 10/04/21 ás 18:45, David Passens escribiu: Hello folks, I recently installed OpenBSD as a dualboot next to a Linux install. However, I didn't pay much attention to partitioning and created a new ESP. This means that my Linux bootloader can't find the OpenBSD bootloader to chainload it. Now I want to fix this situation. If I don't reinstall (which I don' want to), I need to move one bootloader onto the other ESP. Moving the Linux bootloader seems easier, but I'd like to know if I can do the same with the OpenBSD one. I could just try to move the executable but I'm not sure how the bootloader finds the partition to boot from and how sysupgrade finds the bootloader to upgrade it (if it does it at all, the man page didn't mention it). Does anybody know whether it's safe to just move the bootloader to a different partition? If so, can I rename it as well? BOOTX64.efi conflicts with my linux bootloader. I already tried to find out via boot(8) and boot_amd64(8) but they only talk about legacy BIOS. At first glance, man -k efi doesn't point to any useful pages either. I might've overlooked something though, I'm fairly new to OpenBSD. Thanks in advance, David EFI can boot from any FAT partition on the drive. You can put any bootloader you want on that partition (usually it is the first) and EFI will be able to boot from it. Check your mobo documentation, but for me the BIOS menu includes an «Boot from» option, to select the EFI file from which to boot. Not knowing the OpenBSD specifics, it should boot even if you move it. If you have doubts, try to recreate your setup on a virtual machine and try there.
Re: Toshiba Satellite A30 : panic
Hi,
No bother it might be a hardware fault,
Sry,
Jean-François
Le 10/04/2021 à 18:00, jeanfrancois a écrit :
Good afternoon,
After installing on an old Toshiba Satellite A30 with 1 Gb of Ram and
128 Mo of graphic shared memory, there is a panic on startup of
X-desktop, it sometimes goes up to showing fvwm but panics at starting
firefox.
It seems to me the issue comes from graphic card.
I tested with fw_update uninstall Radeon firmware, then the graphics
environment won't work at all.
Does this kernel error popup an idea where this comes from, what to do
about it ?
Appart from X environment it works well. Also started under fvwm but
unstable under XFCE4. Always crashes when starting starting firefox.
Probably Radeon driver issue as shown in attached kernel error message
(panic) and trace:
Attached jpeg
dmesg:
OpenBSD 6.8 (GENERIC) #5: Mon Feb 22 03:42:30 MST 2021
Welcome to OpenBSD: The proactively secure Unix-like operating system.
Please use the sendbug(1) utility to report bugs in the system.
Before reporting a bug, please try to reproduce it with the latest
version of the code. With bug reports, please try to ensure that
enough information to reproduce the problem is enclosed, and if a
known fix for it exists, include that as well.
portable$ dmesg
OpenBSD 6.8 (GENERIC) #5: Mon Feb 22 03:42:30 MST 2021
r...@syspatch-68-i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
real mem = 938360832 (894MB)
avail mem = 904957952 (863MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 01/16/04, BIOS32 rev. 0 @ 0xfd700, SMBIOS rev.
2.31 @ 0xd6010 (31 entries)
bios0: vendor TOSHIBA version "V1.30" date 01/16/2004
bios0: TOSHIBA Satellite A30
acpi0 at bios0: ACPI 1.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC SSDT SSDT SSDT
acpi0: wakeup devices ELAN(S3) OHC1(S3) OHC2(S3) EHCI(S3) MODM(S3)
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Mobile Intel(R) Pentium(R) 4 CPU 2.66GHz ("GenuineIntel"
686-class) 2.67 GHz, 0f-02-09
cpu0:
FPU,V86,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,CNXT-ID,xTPR,PERF,MELTDOWN
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 133MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (P2P_)
acpiprt2 at acpi0: bus 1 (AGP_)
acpiec0 at acpi0
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PWRB
"CMP0101" at acpi0 not configured
"PNP0A03" at acpi0 not configured
acpicmos0 at acpi0
"PNP0A05" at acpi0 not configured
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT1 model "PA3250U " serial 3658Q type Li-Ion oem
"TOSHIBA"
acpicpu0 at acpi0: !C2(500@1 io@0x8014), C1(1000@1 halt), FVS, 2660,
1596 MHz
acpivideo0 at acpi0: VGA_
bios0: ROM list: 0xc/0xf000 0xd/0x6000! 0xd6000/0x800!
0xd8000/0x1000
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "ATI RS300_133 Host" rev 0x02
agp at pchb0 not configured
ppb0 at pci0 dev 1 function 0 "ATI Radeon IGP 9100 AGP" rev 0x00
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 5 function 0 "ATI Radeon Mobility IGP 9100" rev
0x00
drm0 at radeondrm0
radeondrm0: apic 1 int 16
ohci0 at pci0 dev 19 function 0 "ATI SB200 USB" rev 0x01: apic 1 int
19, version 1.0, legacy support
ohci1 at pci0 dev 19 function 1 "ATI SB200 USB" rev 0x01: apic 1 int
19, version 1.0, legacy support
ehci0 at pci0 dev 19 function 2 "ATI SB200 USB2" rev 0x01: apic 1 int 19
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "ATI EHCI root hub" rev
2.00/1.00 addr 1
piixpm0 at pci0 dev 20 function 0 "ATI SB200 SMBus" rev 0x17: SMI
iic0 at piixpm0
spdmem0 at iic0 addr 0x50: 512MB DDR SDRAM non-parity PC2700CL2.5
spdmem1 at iic0 addr 0x51: 512MB DDR SDRAM non-parity PC2700CL2.5
pciide0 at pci0 dev 20 function 1 "ATI SB200 IDE" rev 0x00: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 38154MB, 78140160 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: removable
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 2
pcib0 at pci0 dev 20 function 3 "ATI SB200 ISA" rev 0x00
ppb1 at pci0 dev 20 function 4 "ATI SB200 PCI" rev 0x00
pci2 at ppb1 bus 2
"TI TSB43AB21 FireWire" rev 0x00 at pci2 dev 0 function 0 not configured
rl0 at pci2 dev 3 function 0 "Realtek 8139" rev 0x10: apic 1 int 19,
address 00:02:3f:d2:a4:f9
rlphy0 at rl0 phy 0: RTL internal PHY
cbb0 at pci2 dev 4 function 0 "ENE CB-1410 CardBus" rev 0x01: apic 1
int 16
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 3 device 0
Subscribe....
-- _ IMPORTANT: The information contained in this communication is confidential and/or legally privileged, and should be for the use only of the addressee(s). If you are not the intended recipient, please contact the sender and destroy all copies of this message and any attachments. Any disclosure, copying, distribution or taking any action in reliance on this information other than by the intended recipient is strictly prohibited and may be unlawful.
