Re: help debug NFS
Hi Maxim, I cannot help you fix this as I don't have a similar set-up but I can tell you this isn't normal behaviour for NFS. You should not need to tweak anything to get a stable mount at least in my experience. It sounds like a bug somewhere to me. You could try using the gnu watch command or similar while loop to run an ls of the share from the client to confirm if it hangs after non use or after five minutes regardless of use or non-use. You could also try testing the network connection between the two machines to make sure there is no connectivity or cable problem. You could use the same while loop to run rpcinfo or showmount commands from the client and server to see if it stops working after the same delay. Someone with more knowledge of NFS might suggest some better debugging steps... Regards Ed Gray On Sun, 11 Apr 2021, 10:07 am Родин Максим, wrote: > Hello > I have an NFS server on OpenBSD 6.8 stable > which exports a folder with default settings. > I have a linux mint client which mounts a share from this NFS server > with these settings: > sudo mount -o wsize=8192,rsize=8192 192.168.1.65:/big > /home/user/store > which gives a decent speed at about 50-60MB/s both sides which seem ok > for me. > The problem is: when the mount point is not used for a while (5 minutes > and more) the share becomes unresponsive and the only way to unmount the > share is to do > sudo umount -lf /home/user/store > After that I can mount the share once again. > When I imitate using the share on client using > while :; do ls /home/user/store/ && echo "OK" && sleep 3 ; done; > the share remains responsive all the time and shows no problems. > > What tweaks(settings) on the client(server) am I missing in my setup > to keep the mount point responsive? > -- > Best regards > Maksim Rodin > >
Re: 6.8 with gnome boots to xterm after upgrade
Sivan, On the boot problem I would suggest you check your BIOS settings for legacy boot and UEFI options in the boot or disk settings. The manual for your system / motherboard should explain. These can have several names like compatibility mode or CSM. I would expect to either use legacy BIOS / CSM boot or UEFI not both but I don't know how well it is supported on OpenBSD. Regards Ed Gray On Wed, 10 Mar 2021, 1:53 am Sivan !, wrote: > Thank you. Please see inline: > > On Tue, 9 Mar 2021 at 13:03, Stuart Henderson wrote: > > > > On 2021-03-08, Sivan ! wrote: > > > Thank you. One unresolved issue. While running fetch, there was an > > > error pop up that said /usr directory is out of space, though an > > > entire 250 GB nvme is for OpenBSD, almost with no user files, except > > > for the ports tree that was being downloaded b the fetch command. > > > When installing OpenBSD in a 250 GB nvme, I chose GPT and let the > > > installer decide on partitions. But something went wrong. > > > > The disk is split into partitions. Run df -h to see what's free. > > This is what I see: > > bash-5.0$ df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/sd2a 986M128M809M14%/ > /dev/sd2l 168G5.2G155G 3%/home > /dev/sd2d 3.9G324M3.4G 9%/tmp > /dev/sd2f 5.8G5.1G432M92%/usr > /dev/sd2g 986M239M697M26%/usr/X11R6 > /dev/sd2h 19.4G4.9G 13.5G26%/usr/local > /dev/sd2k 5.8G116M5.4G 2%/usr/obj > /dev/sd2j 1.9G2.0K1.8G 0%/usr/src > /dev/sd2e 15.3G 36.5M 14.5G 0%/var > > > > > > To convert "marketing capacity" for a drive (given in "decimal GB") into > > usable capacity in binary GB (some people call this GiB), use this > > calculation: > > > > (97696368+(1953504*(capacity-50)))/2048 > > > > (The formula is from IDEMA LBA1-03 plus a conversion from 512-byte LBA > > blocks to GB) > > > > So for 250GB > > > > (97696368+(1953504*(250-50)))/2048 = 238475.1796875 > > Thank you. The issue is that in the bios I see two entries, the entry > that is listed as > "Samsung SSD 970 EVO Plus 250 GB (238476 MB)" is sometimes > automatically selected to boot, the boot process halts with a one line > "No active partition error. Then I have to get into bios to choose the line > that says "line No 1: UEFI OS (samsung SSD EVO 970 Plus 250 GB)" This > is why I raised the 30 blocks / GB-MB issue. > > > > > Then there's a little extra used for filesystem structures. > > > > > > > It started with the warning: Not all of the space available to > > > /dev/nvme0n1 appears to be used, you can fix the GPT to use all the > > > space (an extra 30 blocks) or > > > continue with the current setting? > > > > 30 blocks is nothing. Leave this alone. > > Yes, I will leave the 30 blocks alone. > > > > > Does this imply that the 232.89 GiB is OpenBSD area, but somehow with > > > "no active partition" which is perhaps the reason why there was an > > > error message during fetch that said /usr directory is low on disk > > > space ? > > > > You filled the partition holding /usr when you ran "make" in > > /usr/ports/x11/gnome. Remove the build files with "rm -r /usr/ports/pobj" > > (or remove /usr/ports completely if you don't need it). > > Before removing I looked for "pobj" under /usr/ports but did not find it: > > bash-5.0$ cd /usr/ports/ > bash-5.0$ ls > CVS cad games mathprint > Makefilechinese geo meta > productivity > README comms graphicsmiscsecurity > archivers converters infrastructure multimedia shells > astro databases inputmethodsnet sysutils > audio devel japanesenewstelephony > benchmarks editors javaplan9 tests > biology education korean plist textproc > books emulators langports.pub www > bulkfonts mailports.sec x11 > > Is there a way of expanding the space in the /usr directory? > > > > > The default auto-partitioning sizes do not give enough space to place > > ports under /usr and build anything other than the smallest ports. > > > > > >
Re: 6.8 with gnome boots to xterm after upgrade
Hi Sivan, If you have a separate issue it's best to write a new email to the list with an appropriate subject, then it will make more sense to those reading or following. It does sound like you have a few different issues here and I'm not sure I understand your configuration. I also think you might benefit from reading the documentation particularly the INSTALL file, the FAQs and afterboot man page. It seems like you don't understand some of the fundamental differences between Openbsd and other systems. Particularly the disk layout. Regards Ed Gray On Mon, 8 Mar 2021, 7:27 pm Sivan !, wrote: > Thank you. One unresolved issue. While running fetch, there was an > error pop up that said /usr directory is out of space, though an > entire 250 GB nvme is for OpenBSD, almost with no user files, except > for the ports tree that was being downloaded b the fetch command. > When installing OpenBSD in a 250 GB nvme, I chose GPT and let the > installer decide on partitions. But something went wrong. > > My bios shows this in the hard disk list: > > line No 1: UEFI OS (samsung SSD EVO 970 Plus 250 GB) > line No 2: Samsung SSD 970 EVO Plus 250 GB (238476 MB) > (line No 3 : SATA ... # this is Ubunu > line No 4: SATA # this is CentOS) > > In BIOS if I choose item 1, it boots to OpenBSD > If I choose item 2, it shows a blank boot screen shows a one line > error message that says "no active partition" that is it. > > I ran gparted after booting the UEFI OS > > It started with the warning: Not all of the space available to > /dev/nvme0n1 appears to be used, you can fix the GPT to use all the > space (an extra 30 blocks) or > continue with the current setting? > > I chose "ignore", because I suspected that gparted probably saw the > UEFI boot content of (250 GB - 238476 MB) as 30 blocks of "unused" > space. > > Gparted shows: > > EFI System Area fat 16 > /dev/nvme0n1p2 480 KiB > Efi Sstem Aea Used 292 KiB > /dev/ nvme0n1p4 OpenBSD Area 232.89 GiB > > Does this imply that the 232.89 GiB is OpenBSD area, but somehow with > "no active partition" which is perhaps the reason why there was an > error message during fetch that said /usr directory is low on disk > space ? > > Thank you. > > > On Sun, 7 Mar 2021 at 15:54, Ed Gray wrote: > > > > Glad you solved it. > > > > I would recommend running sysupgrade with the -n switch if you are using > the system. > > > > E.g. sysupgrade -s -n > > > > This delays the reboot but still prepares the upgrade. > > > > Upgrades are now completely automated but you still have to update > packages and your ports tree as well as the base system to keep everything > working properly. > > > > Regards > > Ed Gray > > > > On Sat, 6 Mar 2021, 6:19 pm Sivan !, wrote: > >> > >> Solved. > >> sysupgrade -s > >> (after reboot, gnome loaded) > >> bash-5.0# uname -r > >> 6.9 > >> > >> On Sat, 6 Mar 2021 at 22:53, Sivan ! wrote: > >> > > >> > /use/x11/ports/gnome make install didn't work. Images attached. > >> > > >> > On Sat, Mar 6, 2021, 22:12 Sivan ! wrote: > >> >> > >> >> > >> >> dear Ed, > >> >> > >> >> It wasn't complicated at all in till the unintended upgrade, and I > wish to try and resolve this, even though I a person with copy skills > in command line. OpenBSD 6.8 was booting fine with gnome, but now stuck in > xterm. > >> >> > >> >> Now in xsession cd/use/pets/gnome, typed make, it is making, will > report what happens. > >> >> > >> >> Thank you. > >> >> > >> >> > >> >> On Fri, 5 Mar 2021 at 23:23, Ed Gray wrote: > >> >> > > >> >> > Hi Sivan, > >> >> > > >> >> > Sorry I've not had chance to look at everything you sent. > >> >> > > >> >> > Firstly the message about SSH keys sounds normal as this is part > of a normal X session startup. I suspect you have a key that has changed or > needs a passphrase entered and it's just picking it up when you try to > start X. > >> >> > > >> >> > The command history looks strange, you're running shutdown and > reboot and then other commands, unless these are from another session? > >> >> > > >> >> > Openbsd needs the -h option to both shutdown and power off the > machine or -r for reboot. > >> >> > > >> >> > Where is your startx pr
Re: 6.8 with gnome boots to xterm after upgrade
Hi Sivan, Sorry I've not had chance to look at everything you sent. Firstly the message about SSH keys sounds normal as this is part of a normal X session startup. I suspect you have a key that has changed or needs a passphrase entered and it's just picking it up when you try to start X. The command history looks strange, you're running shutdown and reboot and then other commands, unless these are from another session? Openbsd needs the -h option to both shutdown and power off the machine or -r for reboot. Where is your startx program and is it a custom program? If you have done unintended upgrades and your /usr is also full it's going to cause all sorts of problems. I would recommend reinstalling a release from scratch if you can. Alternatively when the boot program runs you can choose bad.rd to get the installer ramdisk and manually repair from there but it's a rather complex process. On my system I had to boot bad.rd, type s for shell, run the MAKEDEV script in /dev to create device nodes and then run disklabel manually to rearrange volumes to make space. You would also need to grow or shrink the volumes. Regarding further troubleshooting of X sessions I would recommend moving .xsession to .xsession.bak and starting with a fresh configuration. I would need to understand more about how you are starting gnome like more details of any changes you made to the standard installation. Regards Ed Gray On Fri, 5 Mar 2021, 12:03 am Sivan !, wrote: > Dear Stuart Henderson. > > I ran sysmerge. > > I posted, earlier in this thread, 11 images in response to Ed Gray's > comment that I had not shared sufficient details. In addition there > are four more images attached here that I think are important. > > One of these four images show the output of sysmerge and startx commands. > Another is a screenshot of a strange prompt that appears before boot, > it asks for the ssh password - not an encryption password, which > might be understandable, if I had an encrypted disk, I haven't > encrypted -- so why does it ask for the ssh password, before asking > for a login password in X Term? > Two more pictures show the reboot sequence that is some sort of a loop > when shutdown now command is issued as user or root, from x Term, then > the main screen command line is seen flashing the status, and > invariably reboots the system in X Term. This happened in gnome (or > gde) before the accidental upgrade to 6.9 beta and happens in x Term > in 6.9 beta. > > Thank you. > > On Thu, 4 Mar 2021 at 14:10, Stuart Henderson wrote: > > > > On 2021-03-03, Sivan ! wrote: > > > After sysupgrade -s, during which there were two or more automatic > > > reboots, freebsd, upgraded to 6.9 booted after asking password for ssh > key, > > > and started with xvterm console. Startx attempted to switch to gui, but > > > returned errors. > > > > > > Please advise. > > > > > > Thank you > > > > > > > Make sure you have run sysmerge. > > > > If that doesn't help then we need more than just "returned errors" - > *what* errors? > > >
Re: 6.8 with gnome boots to xterm after upgrade
Hi Sivan, I think you need to provide more details on your problem if you want some help at least a log from X and what is in your .xsession file. You also mentioned errors but don't say what they are. Did you upgrade the packages each time you upgraded the system? Regards Ed Gray On Wed, 3 Mar 2021, 5:12 pm Sivan !, wrote: > After sysupgrade -s, during which there were two or more automatic > reboots, freebsd, upgraded to 6.9 booted after asking password for ssh key, > and started with xvterm console. Startx attempted to switch to gui, but > returned errors. > > Please advise. > > Thank you >
Re: Window Manager performance impact on applications
Hi Mihai, What do you mean by slow moving? Are window operations like moving the window, maximizing, iconify slow or is Firefox slow performing? If it's Firefox, I have not had any issues on 6.8 but perhaps check the pkg-readme file if you haven't already for Cwm and Firefox. I don't know any security reason not to run fvwm 2 although it's older than others. Maybe worth confirming if this just an issue with the last snapshot and providing more details. Different window managers can certainly provide better general performance especially with low memory or older hardware but I'm not aware of any technical reasons why Firefox should be significantly faster with one rather than another. You'd still be using gtk either way I imagine. Regards Ed Gray On Wed, 3 Mar 2021, 3:48 pm Mihai Popescu, wrote: > Hello, > > Technically speaking, is it possible for a window manager to have a > performance impact on running applications in the GUI area? > > Real case: i had to run firefox very fast on a fresh snapshot install, so i > used the default fvwm instead of cwm. The graphical response is instant, > much much better than cwm. I tried twm, firefox was slow moving too. The > configuration for firefox is the same on all WM. > Is it possible, or is it my imagination? > > If that's the case, is it advisable to run fvwm from base? Is it too old > and should be avoided? > > Thank you/ >
Re: OpenBSD NTFS experience
unt /dev/sd0a on / type ffs (local) /dev/sd0k on /home type ffs (local, nodev, nosuid) /dev/sd0d on /tmp type ffs (local, nodev, nosuid) /dev/sd0f on /usr type ffs (local, nodev) /dev/sd0g on /usr/X11R6 type ffs (local, nodev) /dev/sd0h on /usr/local type ffs (local, nodev, wxallowed) /dev/sd0j on /usr/obj type ffs (local, nodev, nosuid) /dev/sd0i on /usr/src type ffs (local, nodev, nosuid) /dev/sd0e on /var type ffs (local, nodev, nosuid) fusefs on /mnt/local/hdd type fuse (local) myname# disklabel -p m /dev/sd2c # /dev/sd2c: type: SCSI disk: SCSI disk label: M3 Portable duid: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 121601 total sectors: 1953525168 # total bytes: 953869.7M boundstart: 0 boundend: 1953525168 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c:953869.7M0 unused i:720201.0M 64NTFS j:233667.0M 1474971648 MSDOS atactl reports: myname# atactl sd2 Model: ST1000LM025 HN-M101ABB, Rev: 2BA30003, Serial #: E7663G94AA5CEY Device type: ATA, fixed Cylinders: 16383, heads: 16, sec/track: 63, total sectors: 1953525168 Device capabilities: ATA standby timer values IORDY operation IORDY disabling Device supports the following standards: ATA-1 ATA-2 ATA-3 ATA-4 ATA-5 ATA-6 ATA-7 ATA-8 Master password revision code 0xfffe Device supports the following command sets: NOP command READ BUFFER command WRITE BUFFER command Host Protected Area feature set Read look-ahead Write cache Power Management feature set Security Mode feature set SMART feature set Flush Cache Ext command Flush Cache command Device Configuration Overlay feature set 48bit address feature set Automatic Acoustic Management feature set Set Max security extension commands Set Features subcommand required Power-up in standby feature set Advanced Power Management feature set DOWNLOAD MICROCODE command IDLE IMMEDIATE with UNLOAD FEATURE SMART self-test SMART error logging Device has enabled the following command sets/features: NOP command READ BUFFER command WRITE BUFFER command Host Protected Area feature set Read look-ahead Write cache Power Management feature set SMART feature set Flush Cache Ext command Flush Cache command Device Configuration Overlay feature set 48bit address feature set Set Features subcommand required DOWNLOAD MICROCODE command Regards Ed Gray https://www.linkedin.com/in/ed-gray-55079422 On Mon, 22 Feb 2021 at 17:26, Ed Gray wrote: > > My latest issue with NTFS was that my external drive stopped > responding and caused Thunar to hang. After this my entire session > hung until I killed it with Ctrl + Alt+ backspace. > > It seems the rsync data copy I did completely properly but the mount > stopped responding after some time of the PC being unused. Any > attempts to access the mounted directory caused a hang of the terminal > or process. > > I can now see with atactl that my USB hard drive supports power > management and looks to be in standby mode when not in use. I am > wondering if maybe the drive goes into standby or powers down and that > causes the mount to stop working or if it is a bug in NTFS-3G support > or something else. > > This time I am going to run ntfs-3g with the debug mode enabled in > no_detach to determine if there are any errors when the drive is left > connected but unused. > > It outputs the following on successful mount: > > Version 2017.3.23 external FUSE 26 > Mounted /dev/sd2i (Read-Write, label "SAMSUNG", NTFS 3.1) > Cmdline options: no_detach > Mount options: > allow_other,nonempty,relatime,fsname=/dev/sd2i,blkdev,blksize=4096 > Ownership and permissions disabled, configuration type 1 > > Regards > Ed Gray > https://www.linkedin.com/in/ed-gray-55079422 > > On Sun, 21 Feb 2021 at 19:15, Ed Gray wrote: > > > > Thanks for your reply Maurice, > > > > I tried the read-only driver on an earlier version maybe 6.6 and it > > crashed. I wasn't able to debug it myself but I suppose it could have been > > my external hard drive, the NTFS version or a particular file that caused > > that issue as it happened with a large data copy and a particularly large > > file (multiple GB). > > > > I'm finding poor performance with USB drives on 6.8 with a hard disk and a > > card reader. It could be ntfs-3g with the hard drive but the card is FAT32. > > I am wondering if it's to do with the default shm kernel variables or > > maxfiles and such. It causes various hangs in thunar file manager. > > > > I previously had increased shm variables because of a KDE application > > recommending it for lots of file accesses. > > > > I know ntfs-3g is using FUSE rather than a native driver. > > > > Regards > > Ed Gray > > > > On Sun, 21 Feb 2021, 6:51 pm Maurice McCarthy, wrote: > >> > >> Native read-only support is excellent. > >> I find writing with ntfs-3g quite a lot slower than native Windows > >> Best
Re: OpenBSD NTFS experience
My latest issue with NTFS was that my external drive stopped responding and caused Thunar to hang. After this my entire session hung until I killed it with Ctrl + Alt+ backspace. It seems the rsync data copy I did completely properly but the mount stopped responding after some time of the PC being unused. Any attempts to access the mounted directory caused a hang of the terminal or process. I can now see with atactl that my USB hard drive supports power management and looks to be in standby mode when not in use. I am wondering if maybe the drive goes into standby or powers down and that causes the mount to stop working or if it is a bug in NTFS-3G support or something else. This time I am going to run ntfs-3g with the debug mode enabled in no_detach to determine if there are any errors when the drive is left connected but unused. It outputs the following on successful mount: Version 2017.3.23 external FUSE 26 Mounted /dev/sd2i (Read-Write, label "SAMSUNG", NTFS 3.1) Cmdline options: no_detach Mount options: allow_other,nonempty,relatime,fsname=/dev/sd2i,blkdev,blksize=4096 Ownership and permissions disabled, configuration type 1 Regards Ed Gray https://www.linkedin.com/in/ed-gray-55079422 On Sun, 21 Feb 2021 at 19:15, Ed Gray wrote: > > Thanks for your reply Maurice, > > I tried the read-only driver on an earlier version maybe 6.6 and it crashed. > I wasn't able to debug it myself but I suppose it could have been my external > hard drive, the NTFS version or a particular file that caused that issue as > it happened with a large data copy and a particularly large file (multiple > GB). > > I'm finding poor performance with USB drives on 6.8 with a hard disk and a > card reader. It could be ntfs-3g with the hard drive but the card is FAT32. I > am wondering if it's to do with the default shm kernel variables or maxfiles > and such. It causes various hangs in thunar file manager. > > I previously had increased shm variables because of a KDE application > recommending it for lots of file accesses. > > I know ntfs-3g is using FUSE rather than a native driver. > > Regards > Ed Gray > > On Sun, 21 Feb 2021, 6:51 pm Maurice McCarthy, wrote: >> >> Native read-only support is excellent. >> I find writing with ntfs-3g quite a lot slower than native Windows >> Best
Re: OpenBSD NTFS experience
Thanks for your reply Maurice, I tried the read-only driver on an earlier version maybe 6.6 and it crashed. I wasn't able to debug it myself but I suppose it could have been my external hard drive, the NTFS version or a particular file that caused that issue as it happened with a large data copy and a particularly large file (multiple GB). I'm finding poor performance with USB drives on 6.8 with a hard disk and a card reader. It could be ntfs-3g with the hard drive but the card is FAT32. I am wondering if it's to do with the default shm kernel variables or maxfiles and such. It causes various hangs in thunar file manager. I previously had increased shm variables because of a KDE application recommending it for lots of file accesses. I know ntfs-3g is using FUSE rather than a native driver. Regards Ed Gray On Sun, 21 Feb 2021, 6:51 pm Maurice McCarthy, wrote: > Native read-only support is excellent. > I find writing with ntfs-3g quite a lot slower than native Windows > Best >
OpenBSD NTFS experience
Hi, Has anyone had experience using NTFS with OpenBSD and if so any pointers particularly around performance and any problems encountered? I realise NTFS is probably not used by many people but I have an external drive which is formatted with it. It would be useful to know if anyone is using the read-only NTFS driver or ntfs-3g port successfully and if there are any known bugs with these. Regards Ed Gray https://www.linkedin.com/in/ed-gray-55079422
Re: Zotac 880GITX-A-E amd64 Onboard NEC USB3 does not work.
ess: 0x0038: 0x003c: Interrupt Pin: 01 Line: 07 Min Gnt: 00 Max Lat: 00 0x0050: Capability 0x01: Power Management State: D0 0x0070: Capability 0x05: Message Signalled Interrupts (MSI) Enabled: yes 0x0090: Capability 0x11: Extended Message Signalled Interrupts (MSI-X) Enabled: no; table size 8 (BAR 0:4096) 0x00a0: Capability 0x10: PCI Express Link Speed: 5.0 / 5.0 GT/s, Link Width: x1 / x1 0x0100: Enhanced Capability 0x01: Advanced Error Reporting 0x0140: Enhanced Capability 0x03: Device Serial Number Serial Number: 0x0150: Enhanced Capability 0x18: Latency Tolerance Reporting If anyone is able to help me try to find a solution to this issue please contact me directly and I will copy the list. I have a current system that I can test with as well but it needs upgrading to the latest snapshot. In the meantime I think I will try connecting other USB devices to confirm if anything at all is detected as I have so far only used the USB 3.0 ports with this drive. If the firmware is the issue I would be interested in any suggestions as to where I might search for an official firmware download as I cannot find one from renasas or NEC. Regards Ed Gray https://www.linkedin.com/in/ed-gray-55079422 On Wed, 10 Feb 2021 at 21:43, Ed Gray wrote: > > Hi, > > My main OpenBSD system is a Mini-ITX PC that I built myself using the > Zotac 880GITX-A-E amd64 AM3 motherboard. It is running an AMD Phenom > II X2 555 processor and AMD RS880 / RS780 chipset. > > The onboard NEC USB3 PCI-E chip does not work. I have tested it with a > Samsung M3 1TB external USB3 HDD. I have been unable to use this hard > drive with any version of OpenBSD from 6.1 to 6.8 on USB3. The drive > works fine plugged into a USB2 port. The drive powers up but is > undetected by usbdevs or dmesg. USB3 is enabled in the system BIOS / > UEFI. > > dmesg, pcidump and usbdevs below: > > OpenBSD 6.8 (GENERIC.MP) #4: Mon Jan 11 10:35:56 MST 2021 > > r...@syspatch-68-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8304394240 (7919MB) > avail mem = 8037658624 (7665MB) > random: good seed from bootblocks > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.5 @ 0x9f800 (49 entries) > bios0: vendor American Megatrends Inc. version "080015" date 04/13/2011 > bios0: ZOTAC RS880P > acpi0 at bios0: ACPI 4.0 > acpi0: sleep states S0 S1 S3 S4 S5 > acpi0: tables DSDT FACP APIC MCFG SLIC OEMB SRAT HPET SSDT > acpi0: wakeup devices PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE7(S4) > PCE9(S4) PCEA(S4) SBAZ(S4) P0PC(S4) UHC1(S4) UHC2(S4) USB3(S4) > UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD Phenom(tm) II X2 555 Processor, 3200.42 MHz, 10-04-03 > 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,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC > cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache > cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative > cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative > cpu0: AMD erratum 721 detected and fixed > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 199MHz > cpu0: mwait min=64, max=64, IBE > cpu1 at mainbus0: apid 1 (application processor) > cpu1: AMD Phenom(tm) II X2 555 Processor, 3200.00 MHz, 10-04-03 > 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,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC > cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache > cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative > cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative > cpu1: AMD erratum 721 detected and fixed > cpu1: smt 0, core 1, package 0 > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins > acpimcfg0 at acpi0 > acpimcfg0: addr 0xe000, bus 0-255 > acpihpet0 at acpi0: 14318180 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 1 (P0P1) > acpiprt2 at acpi0: bus -1 (PCE2) > acpiprt3 at acpi0: bus -1 (PCE3) > acpiprt4 at acpi0: bus 2 (PCE4) > acpi
Zotac 880GITX-A-E amd64 Onboard NEC USB3 does not work.
TI SB700 USB 0:22:2: ATI SB700 USB2 0:24:0: AMD 10h HyperTransport 0:24:1: AMD 10h Address Map 0:24:2: AMD 10h DRAM Cfg 0:24:3: AMD 10h Misc Cfg 0:24:4: AMD 10h Link Cfg 1:5:0: ATI Radeon HD 4250 1:5:1: ATI Radeon HD 4200 HD Audio 2:0:0: Atheros AR9285 3:0:0: Realtek 8168 4:0:0: NEC xHCI pcidump -v Error after 3:0:0: Realtek 8168: pcidump: PCIOCGETVPD: Input/output error 00 00 00 00 00 00 00 00 00\^@\^@\^@\^C 00 00 00 00\^@\^@\M^@ 00 00 00 00 2c: [|vpd] 4:0:0: NEC xHCI 0x: Vendor ID: 1033, Product ID: 0194 0x0004: Command: 0106, Status: 0010 0x0008:Class: 0c Serial Bus, Subclass: 03 USB, Interface: 30, Revision: 03 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, Cache Line Size: 10 0x0010: BAR mem 64bit addr: 0xfe9fe000/0x2000 0x0018: BAR empty () 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: Product ID: 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 01 Line: 07 Min Gnt: 00 Max Lat: 00 0x0050: Capability 0x01: Power Management State: D0 0x0070: Capability 0x05: Message Signalled Interrupts (MSI) Enabled: yes 0x0090: Capability 0x11: Extended Message Signalled Interrupts (MSI-X) Enabled: no; table size 8 (BAR 0:4096) 0x00a0: Capability 0x10: PCI Express Link Speed: 5.0 / 5.0 GT/s, Link Width: x1 / x1 0x0100: Enhanced Capability 0x01: Advanced Error Reporting 0x0140: Enhanced Capability 0x03: Device Serial Number Serial Number: 0x0150: Enhanced Capability 0x18: Latency Tolerance Reporting Controller /dev/usb0: addr 01: 1033: NEC, xHCI root hub Controller /dev/usb1: addr 01: 1002: ATI, EHCI root hub Controller /dev/usb2: addr 01: 1002: ATI, EHCI root hub addr 02: 1a40:0101 Terminus Technology, USB 2.0 Hub addr 03: 05e3:0608 Genesys Logic, USB2.0 Hub addr 04: 1bcf:0005 Sunplus, USB Optical Mouse addr 05: 046d:c31b Logitech, Logitech USB Keyboard Controller /dev/usb3: addr 01: 1002:0000 ATI, EHCI root hub Controller /dev/usb4: addr 01: 1002: ATI, OHCI root hub Controller /dev/usb5: addr 01: 1002: ATI, OHCI root hub Controller /dev/usb6: addr 01: 1002: ATI, OHCI root hub Controller /dev/usb7: addr 01: 1002: ATI, OHCI root hub usbdevs -v Controller /dev/usb0: addr 01: 1033: NEC, xHCI root hub super speed, self powered, config 1, rev 1.00 driver: uhub0 Regards Ed Gray https://www.linkedin.com/in/ed-gray-55079422
Re: Installation overwritten... Accidental disklabel and newfs
Thanks for the answers. I will make a note of this command. I have now installed 6.8 and am gradually getting my settings and software back. Regards Ed Gray https://www.linkedin.com/in/ed-gray-55079422 On Wed, 10 Feb 2021 at 19:25, Ian Darwin wrote: > > The device nodes don't exist until the install or upgrade program detects > > the disk and creates them. > > > > Likewise for wd0 as although outdated for ahci disks. > > > > Dmesg identifies the disk as: > > sd0 at scsibus0 targ0 lun0 ATA ST1000DM003... > > sd0 953869mb > > > > This is why I had to run the install program and accidentally went too > far. > > > > It would be helpful to be able to use disklabel and other tools such as > > newfs, growfs without running through the installer. > > > When booted into the installer, just do CTRL/C to kill the install script > Then do: > cd /dev; sh MAKEDEV sd0 wd0 sd1 # or whatever devices you need > Porblem solved: you can now do "disklabel and other tools" without > risk of destroying your filesystesms. At least, not having the installer > do it. With these tools most people are quite capable of destroying > filesystems. >
Re: Installation overwritten... Accidental disklabel and newfs
Hi Otto, Thanks for your reply. This is what I see on a shell from bad.rd when I try to access the first SATA HDD. # disklabel sd0 disklabel: /dev/rsd0: no such file or directory # disklabel sd0c disklabel: /dev/rsd0c: no such file or directory Same for rsd0 and rsd0c. The device nodes don't exist until the install or upgrade program detects the disk and creates them. Likewise for wd0 as although outdated for ahci disks. Dmesg identifies the disk as: sd0 at scsibus0 targ0 lun0 ATA ST1000DM003... sd0 953869mb This is why I had to run the install program and accidentally went too far. It would be helpful to be able to use disklabel and other tools such as newfs, growfs without running through the installer. In my case I forgot that the installer continues automatically with the next command and also used the wrong switch to disklabel. It's a good thing I take backups seriously nowadays. Regards Ed Gray On Wed, 10 Feb 2021, 3:52 pm Otto Moerbeek, wrote: > On Wed, Feb 10, 2021 at 03:35:06PM +0000, Ed Gray wrote: > > > Okay, thanks Stuart. > > > > I have left testdisk running a deep scan and will see if it finds my > /var. > > I know I'll still have to mount the partitions and I don't know if an > fsck > > would be able to fix any damage done by newfs. > > > > I think at this point I'm better off starting again as like others I've > > done many upgrades. It's probably not worth trying to fix for the sake of > > getting a few configuration files and settings back and maybe some files > I > > have elsewhere. > > > > I would be interested in finding out a way to access my SATA HDD (sd0) > with > > disklabel and other tools on the ramdisk without first running the > install > > or upgrade programs. > > If you starft a shell on the initial prompt of a bsd.rd boot you get a > shell and a fine selection of commands that are useful for recovery. > > -Otto > > > > > Regards > > Ed Gray > > > > On Wed, 10 Feb 2021, 8:33 am Stuart Henderson, > wrote: > > > > > On 2021-02-09, Ed Gray wrote: > > > > I have backups and will probably not have lost anything important > but I > > > > just wondered if anyone had any suggestions as to whether this is > fixable > > > > and what steps to take before I give up and re-install? I followed a > > > how-to > > > > I found which suggested using scan_ffs to rebuild my disklabel but > it's > > > > finding some of the volumes and not all of them. > > > > > > If you were able to recover /var, check in /var/backups where you will > > > hopefully find some disklabel.* files. > > > > > > scan_ffs does not support FFS2, previously used only for large > > > filesystems but on newer installations now used for all filesystems. > > > > > > > > > >
Re: Installation overwritten... Accidental disklabel and newfs
Okay, thanks Stuart. I have left testdisk running a deep scan and will see if it finds my /var. I know I'll still have to mount the partitions and I don't know if an fsck would be able to fix any damage done by newfs. I think at this point I'm better off starting again as like others I've done many upgrades. It's probably not worth trying to fix for the sake of getting a few configuration files and settings back and maybe some files I have elsewhere. I would be interested in finding out a way to access my SATA HDD (sd0) with disklabel and other tools on the ramdisk without first running the install or upgrade programs. Regards Ed Gray On Wed, 10 Feb 2021, 8:33 am Stuart Henderson, wrote: > On 2021-02-09, Ed Gray wrote: > > I have backups and will probably not have lost anything important but I > > just wondered if anyone had any suggestions as to whether this is fixable > > and what steps to take before I give up and re-install? I followed a > how-to > > I found which suggested using scan_ffs to rebuild my disklabel but it's > > finding some of the volumes and not all of them. > > If you were able to recover /var, check in /var/backups where you will > hopefully find some disklabel.* files. > > scan_ffs does not support FFS2, previously used only for large > filesystems but on newer installations now used for all filesystems. > > >
Installation overwritten... Accidental disklabel and newfs
Hi, So I was upgrading my box to 6.8 and managed to accidentally overwrite my disklabel and filesystems. I ran install instead of upgrade and stopped after the filesystem creation when I realized my mistake (see ending paragraphs). The new disklabel was different due to auto allocation changes and newfs has written new data on the disk but the install went no further. I cannot work out exactly where /usr should start because I adjusted some of the auto allocations in the past and I don't therefore know what positions the volumes start at. I have backups and will probably not have lost anything important but I just wondered if anyone had any suggestions as to whether this is fixable and what steps to take before I give up and re-install? I followed a how-to I found which suggested using scan_ffs to rebuild my disklabel but it's finding some of the volumes and not all of them. I am running testdisk as I believe it supports UFS and disklabels and might detect the starting positions of my filesystems if not the data itself. I have also read the FAQ on data recovery. I know this is an odd question but it might help someone in future as well. For background wanting to upgrade 6.7 to 6.8 I was running bsd.rd with the intention of resizing /usr because it became full. On running disklabel sd0 I found my disk was not available and I know from past experience that the installer picks up my SATA HDD but I can't access it until that happens. I ran the install program intending to stop after disk detection and when it got to the disklabel creation I forgot that pressing q results in continuation of the install rather than cancelling the process. I know this is by design in disklabel itself and I should have remembered to press x instead but maybe I'm not the first to try this approach. In my case I wanted to see the disklabel allocation for comparison. I suppose I at least didn't run "rm -rf *"... Regards Ed Gray
Re: Supported PCI USB 3 cards
Has there been a lot of work on this in the last two releases? I cannot provide further details at the moment but with 6.6 I was unable to use a Samsung 1TB USB3 HDD with the onboard USB 3 ports on my desktop and had to use USB 2.0 instead. The drive was not picked up in dmesg output at all. Looks like it has an NEC chip: xhci0 at pci4 dev 0 function 0 "NEC xHCI" rev 0x03: msi, xHCI 0.96 usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "NEC xHCI root hub" rev 3.00/1.00 addr 1 Motherboard is ZOTAC 880GA-ITX-AE. Which is an AMD AM3 board with "AMD RS880 Host" and "AMD RS780 PCIE". I know it's rather old hardware now and a bit specialist being ITX but I would expect these NEC chips to be bundled on quite a few boards. Regards Ed Gray On Wed, 9 Dec 2020, 8:51 am Nils Blomqvist, wrote: > On 27 Nov 2020, at 17:12, Theo de Raadt wrote: > > > Nils Blomqvist wrote: > > > >> I need a PCI card with USB 3 ports. Something like this is what I > >> had in mind: https://amzn.to/2V8NgtT (SEDNA - PCI Express USB 3.1). > >> > >> Can anyone point me in the right direction for finding out if a > >> particular card is supported, or a list of supported ones? > > > > All PCI USB cards should work fine. > > Follow-up: I got the above mentioned card which worked without a hitch. > >
Re: Using ports and updates to the release
Thanks Stuart, That was quite a complete answer. I think in my case to be certain any errors I might find using ports are not due to something outdated on my system I should follow your instructions and pull the updated CVS first especially after doing a release upgrade. Regards Ed Gray On Thu, 29 Oct 2020, 10:35 am Stuart Henderson, wrote: > On 2020-10-28, Ed Gray wrote: > > Hi Marc, > > > > Thanks for your reply. I think maybe this belongs to ports more than > misc. > > But it's a general query about releases and ports as well. > > > > My question was actually about updating the ports tree from an older > > release version before trying to use it rather than whether to use ports > or > > packages. > > The ports tree does not install things directly, it *always* builds > packages. > "make install" runs pkg_add to install the locally built package. Unless > you > modify the ports or there's some non-deterministic build behaviour (which > would > usually be considered a bug in the port) there's no difference whether you > build it yourself or use a pre-built package, just an increased chance of > frustration if things don't work (and there are more things that can go > wrong). > > > I installed 6.2 release I believe and later upgraded to 6.6 release. I > > pulled the release version of ports at some point and later tried to > build > > a port which failed due to an outdated dependency. My version of the > ports > > tree was outdated but even the newer 6.6 stable version was also > outdated. > > When I sent my original email 6.6 was still one of the supported releases > > along with 6.7. > > > > I guess my question is if I run 6.x release and want to build port xyz > can > > I expect a port to build using the ports tree that came with the 6.x > > release or must I always use at least the stable version of the ports > tree? > > If you run release X.Y then the supported options are to use a ports tree > with > cvs tag OPENBSD_X_Y_BASE (the tree at the time of release) or OPENBSD_X_Y > (-stable). > > > The following question is then if I have a problem building a port due to > > an outdated dependency on a supported release should I report it as an > > issue with the port even if a newer release of openbsd does not have the > > issue? > > Excepting minor problems (not usually seen for releases but sometimes seen > in > -current) the tree at a particular checkout should be internally > consistent, > the dependencies needed are in that tree. We build complete sets of > packages > on the faster architectures several times a week so problems with this > would > show up. > > If you mean an outdated dependency *on your system* rather than in the > ports > tree then that would be because you haven't updated installed packages > first. > (There will also likely be a mixture of library versions that will cause > conflicts if you build ports with the system in this stage). > > If you really want to build from ports to update your system then you > either > need to deal with figuring out which to build first to avoid incorrect > combinations (noting that some ports cannot be built, or cannot be > *correctly* > built, while an older version of themselves is already installed), or > uninstall > all packages and build the complete set that you want. > > Otherwise the standard procedure is update base, pkg_add -u, cvs up the > ports > tree for the branch that matches the OpenBSD version you're running, and > then > you can expect that versions of dependencies are usually correct (special > case: > if you run a slow architecture with -current snapshots, the package > snapshot > might be too old to be useful, in that case you will need to build a bunch > more yourself). > > >
Re: Using ports and updates to the release
Hi Marc, Thanks for your reply. I think maybe this belongs to ports more than misc. But it's a general query about releases and ports as well. My question was actually about updating the ports tree from an older release version before trying to use it rather than whether to use ports or packages. I installed 6.2 release I believe and later upgraded to 6.6 release. I pulled the release version of ports at some point and later tried to build a port which failed due to an outdated dependency. My version of the ports tree was outdated but even the newer 6.6 stable version was also outdated. When I sent my original email 6.6 was still one of the supported releases along with 6.7. I guess my question is if I run 6.x release and want to build port xyz can I expect a port to build using the ports tree that came with the 6.x release or must I always use at least the stable version of the ports tree? The following question is then if I have a problem building a port due to an outdated dependency on a supported release should I report it as an issue with the port even if a newer release of openbsd does not have the issue? Regards Ed Gray On Wed, 28 Oct 2020, 7:07 am Marc Espie, wrote: > On Sun, Oct 11, 2020 at 09:12:13PM +0200, Ingo Schwarze wrote: > > Hi Ed, > > > > Ed Gray wrote on Sun, Oct 11, 2020 at 07:21:32PM +0100: > > > > > I'm still fairly new to openbsd and the idea of using ports > > > in general rather than binary packages. > > > > You are usually better off using packages than using ports, > > especially as a new user. > > > > Even as an experienced user doing lots of development and minor > > amounts of ports development, i use packages most of the time. > > As one of the persons *responsible* for keeping the ports system > working, I do use packages all the time. > > Ports are on my development setup. > > The machine I write this mail from uses packages, > with about 3 ports that are just there because not committed yet. >
Using ports and updates to the release
Hi, I'm still fairly new to openbsd and the idea of using ports in general rather than binary packages. Is it necessary to keep the ports tree updated if using a release version of openbsd e.g. pulling the stable tree from CVS before building new software? Regards Ed Fray
Re: XFCE menu does not load with keyboard shortcut
You're right Dumitru, this is an old bug: https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/201 I have been using XFCE for a very long time and in the past there was always a keyboard shortcut to open the applications menu on the panel directly. There is a separate shortcut to open the desktop menu (which Robb at y42 mentioned). I suppose we just have to wait for it to be fixed upstream. The .xsession-errors file was the right place to look which was helpful for me so thanks for that Robb. Regards Ed Gray On Wed, 24 Jun 2020 at 09:07, Dumitru Moldovan wrote: > On Tue, Jun 23, 2020 at 07:33:20PM +0100, Ed Gray wrote: > >Hi, > > > >I have an issue with XFCE on OpenBSD 6.6 and current on an amd64 system. > >XFCE works fine except for accessing the applications menu with the Alt + > >F1 keyboard shortcut. Instead of loading the menu it gets highlighted in > >grey and nothing happens. Clicking the menu loads it straight away. > > > >The shortcut is defined in the keyboard settings as the default for > >xfce4-popup-applicationsmenu which is different from the shortcut for the > >desktop menu. Sometimes in another application such as firefox when I > press > >Alt + F1 a second time I get the desktop menu appear, even though firefox > >is maximised and I'm not on the desktop. > > > >I can't confirm at the moment if it is specific to OpenBSD or XFCE in > >general. > > > >Does anyone else have this problem? > > Have seen this on Void Linux as well. Family member needed Netflix on > her laptop, so I couldn't push OpenBSD, even though it ran fine. (Had > to check, and by the way, it was surprising to see how much slower it > ran compared to Alpine or Void.) > > But this is an older Xfce bug, I remember having similar issues when > I last gave it a shot. This used to work reliably in older versions > though, back when Xfce was based on GTK+ 2.x. > > To end in a positive note, one thing I learned on my OpenBSD adventure > is "the best desktop is no desktop". cwm never fails to open its > menus. Keep it stupid simple. > >
XFCE menu does not load with keyboard shortcut
Hi, I have an issue with XFCE on OpenBSD 6.6 and current on an amd64 system. XFCE works fine except for accessing the applications menu with the Alt + F1 keyboard shortcut. Instead of loading the menu it gets highlighted in grey and nothing happens. Clicking the menu loads it straight away. The shortcut is defined in the keyboard settings as the default for xfce4-popup-applicationsmenu which is different from the shortcut for the desktop menu. Sometimes in another application such as firefox when I press Alt + F1 a second time I get the desktop menu appear, even though firefox is maximised and I'm not on the desktop. I can't confirm at the moment if it is specific to OpenBSD or XFCE in general. Does anyone else have this problem? Regards Ed Gray
