Re: Issues with X and Gnome on OpenBSD new install
January 8, 2020 8:11 AM, "Michael G Workman" wrote: > Hello, > > OpenBSD is a great operating system, glad to have been to installed it > successfully. > > I installed OpenBSD on a Dell Vostro 1500 laptop with dual core 2ghz intel > processor, 2 GB of RAM, and 120 GB hard drive (circa 2008 laptop) > > I had problems with firefox, but installed Chromium instead and Chrome > works great for web browsing. > > I also installed bash and nano, and also installed Gnome. Hoping to use > Gnome instead of the default window manager. > > But encountered a fatal error, the X server could not be found, and also a > driver called xf86OpenConsole was missing, causing a fatal server error. > > When I installed it, I chose openbsd-dell for the hostname, and then > OpenBSD tacked on attlocal.net to it to make it openbsd-dell.attlocal.net, > but not sure how that happened, an nslookup on attlocal.net says it is an > invalid domain. > > I am sure it must be a simple fix, here is my Xorg.1.log file: > > Thanks. > > [ 6760.324] > X.Org X Server 1.20.5 > X Protocol Version 11, Revision 0 > [ 6760.324] Build Operating System: OpenBSD 6.6 amd64 > [ 6760.324] Current Operating System: OpenBSD openbsd-dell.attlocal.net > 6.6 GENERIC.MP#372 amd64 > [ 6760.324] Build Date: 12 October 2019 11:22:22AM > [ 6760.324] > [ 6760.325] Current version of pixman: 0.38.4 > [ 6760.325] Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [ 6760.325] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 6760.325] (==) Log file: > "/home/mworkman72/.local/share/xorg/Xorg.1.log", Time: Tue Jan 7 15:01:09 > 2020 > [ 6760.341] (==) Using system config directory > "/usr/X11R6/share/X11/xorg.conf.d" > [ 6760.351] (==) No Layout section. Using the first Screen section. > [ 6760.351] (==) No screen section available. Using defaults. > [ 6760.351] (**) |-->Screen "Default Screen Section" (0) > [ 6760.351] (**) | |-->Monitor "" > [ 6760.352] (==) No monitor specified for screen "Default Screen Section". > Using a default monitor configuration. > [ 6760.352] (==) Automatically adding devices > [ 6760.352] (==) Automatically enabling devices > [ 6760.352] (==) Not automatically adding GPU devices > [ 6760.352] (==) Max clients allowed: 256, resource mask: 0x1f > [ 6760.401] (==) FontPath set to: > /usr/X11R6/lib/X11/fonts/misc/, > /usr/X11R6/lib/X11/fonts/TTF/, > /usr/X11R6/lib/X11/fonts/OTF/, > /usr/X11R6/lib/X11/fonts/Type1/, > /usr/X11R6/lib/X11/fonts/100dpi/, > /usr/X11R6/lib/X11/fonts/75dpi/ > [ 6760.401] (==) ModulePath set to "/usr/X11R6/lib/modules" > [ 6760.401] (II) The server relies on wscons to provide the list of input > devices. > If no devices become available, reconfigure wscons or disable > AutoAddDevices. > [ 6760.401] (II) Loader magic: 0xef025473000 > [ 6760.402] (II) Module ABI versions: > [ 6760.402] X.Org ANSI C Emulation: 0.4 > [ 6760.402] X.Org Video Driver: 24.0 > [ 6760.402] X.Org XInput driver : 24.1 > [ 6760.404] X.Org Server Extension : 10.0 > [ 6760.404] (EE) > Fatal server error: > [ 6760.404] (EE) xf86OpenConsole: No console driver found > Supported drivers: wscons > Check your kernel's console driver configuration and /dev entries(EE) > [ 6760.404] (EE) > Please consult the The X.Org Foundation support > at http://wiki.x.org > for help. > [ 6760.404] (EE) Please also check the log file at > "/home/mworkman72/.local/share/xorg/Xorg.1.log" for additional information. > [ 6760.405] (EE) > [ 6760.406] (EE) Server terminated with error (1). Closing log file. from the looks of things you are using startx(1) read https://www.openbsd.org/faq/faq11.html#StartingX and use xenodm(1) instead also look at your dmesg and look for something "drm" something. if you have errors do a fw_update(1). > > *Michael G. Workman* > (321) 432-9295 > michael.g.work...@gmail.com yorosiku ~
Re: Re-organising partitions without re-installation
December 24, 2019 4:42 AM, "Dumitru Moldovan" wrote: > On Sun, Dec 22, 2019 at 10:56:20AM +1000, Stuart Longland wrote: > >> So, a few years ago now, I deployed a router VM with OpenBSD 6.1 AMD64. >> Later that got updated to 6.2, then 6.3, 6.4… >> >> Yesterday I updated it to 6.5, then 6.6… now I'm trying to run syspatch: > > I have a similar issue with my desktop. I tried to outsmart the > automatic installer to squeeze as much space as possible for /home on a > desktop with an 80GB SSD. Which worked out OK for a few upgrade cycles, > always from stable version to next stable version. > > However, after a couple of years, I had to unbreak an update that didn't > fit any more in /usr. To my surprise, I had lots of old libs from > previous releases left on disk. Had to manually remove a few of the > older unused libs from /usr to be able to redo the update successfully. > > My understanding is that this is by design. In an update, some libs are > overwritten (if they keep the same file name), but others are left on > disk (theoretically unused) when lib versions are incremented. I can > see a few ways in which this eases updates for people following > -current, such as the OpenBSD devs, so it's a small price to pay. one thing that is useful is sysclean(8) my process now after a doas sysupgrade is 1) doas sysclean; and review the output 2) vise /etc/sysclean.ignore; so that sysclean ignores special files i created 3) doas sysclean | xargs doas rm -rf yorosiku ~
Re: umass device disklabel not detected properly in macppc
thanks for the reply and clarifications. much appreciated. after reading the reply i went back and checked the disk. on amd64 Linux and OpenBSD fdisk shows the GPT properly. (output of Linux fdisk) Disk /dev/sdc: 235.58 GiB, 252933308416 bytes, 494010368 sectors Disk model: SSD-PEU3 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 15420EC6-BC4C-4DAB-BA8E-D4BAAD59640A Device Start End Sectors Size Type /dev/sdc1 2048 494008319 494006272 235.6G Linux filesystem (output of amd64 OpenBSD fdisk) sd2: 1> Disk: sd2 Usable LBA: 34 to 494010334 [494010368 Sectors] GUID: 15420ec6-bc4c-4dab-ba8e-d4baad59640a #: type [ start: size ] guid name 0: Linux files* [2048:494006272 ] 1c5211a4-927b-4836-b2cf-92660b3d7988 2 on macppc OpenBSD fdisk replies "Not Found" ... BUT "fdisk -e" shows: (output of macppc OpenBSD fdisk) Enter 'help' for information sd0: 1> Disk: sd0 geometry: 30750/255/63 [494010368 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: EE 0 0 2 - 30750 184 26 [ 1: 494010367 ] EFI GPT 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused i have very limited knowledge of GPT/MBR/disklabels but that start seems odd. maybe it was created by the original SW used when the device was manufactured? 3 tested MBR on a separate USB drive, and the device got properly detected by macppc > MBR or GPT label? Yes. based on the simple test with the MBR on USB drive and that in mind i nuked the problem disk's GPT. created an MBR partition matching the size of the original partition. fsck on a Linux machine didn't return any errors. so ~ (output of Linux fdisk) Disk /dev/sdc: 235.58 GiB, 252933308416 bytes, 494010368 sectors Disk model: SSD-PEU3 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Device Boot Start End Sectors Size Id Type /dev/sdc4 * 2048 494008319 494006272 235.6G 83 Linux (output of macppc OpenBSD fdisk) Disk: sd0 geometry: 30750/255/63 [494010368 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: 83 0 32 33 - 30750 151 57 [2048: 494006272 ] Linux files* checking on macppc, disklabel has been kept intact !! now were rolling ~ # /dev/rsd0c: type: SCSI disk: SCSI disk label: SSD-PEU3 duid: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 30750 total sectors: 494010368 boundstart: 0 boundend: 494010368 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c:4940103680 unused i:494006272 2048 ext2fs checking on macppc, mount was OK: /dev/sd0i on /mnt/sd0 type ext2fs (local) mounted without problems on amd64 Linux and OpenBSD too maybe i just got lucky lesson for the day ... stay old skool MBR yorosiku ~ December 19, 2019 9:17 AM, "Theo de Raadt" wrote: > The disklabel sector is a not a machine-independent format, and it > moves between different sectors on some machines. > > You'll find we make no promises about this type of disk-portability. > MBR or GPT label? Yes. > > Our own disklabels, unfortunately not. > > rgci...@disroot.org wrote: > >> dear all, >> >> to transfer files between an amd64 Linux, amd64 OpenBSD-current, and macppc >> OpenBSD-current i have a USB drive. last night was the first time i tried to >> use the drive on the macpcc. >> >> Dec 19 06:09:06 apbg4 /bsd: umass0 at uhub0 port 2 configuration 1 interface >> 0 "BUFFALO SSD-PEU3" >> rev 2.10/1.10 addr 2 >> Dec 19 06:09:06 apbg4 /bsd: umass0: using SCSI over Bulk-Only >> Dec 19 06:09:06 apbg4 /bsd: scsibus4 at umass0: 2 targets, initiator 0 >> Dec 19 06:09:06 apbg4 /bsd: sd0 at scsibus4 targ 1 lun 0: >
umass device disklabel not detected properly in macppc
dear all, to transfer files between an amd64 Linux, amd64 OpenBSD-current, and macppc OpenBSD-current i have a USB drive. last night was the first time i tried to use the drive on the macpcc. Dec 19 06:09:06 apbg4 /bsd: umass0 at uhub0 port 2 configuration 1 interface 0 "BUFFALO SSD-PEU3" rev 2.10/1.10 addr 2 Dec 19 06:09:06 apbg4 /bsd: umass0: using SCSI over Bulk-Only Dec 19 06:09:06 apbg4 /bsd: scsibus4 at umass0: 2 targets, initiator 0 Dec 19 06:09:06 apbg4 /bsd: sd0 at scsibus4 targ 1 lun 0: serial.04110210357B1BD7B099 Dec 19 06:09:06 apbg4 /bsd: sd0: 241216MB, 512 bytes/sector, 494010368 sectors the disklabel was not detected properly. this is the disklabel on macppc OpenBSD-current (#638: Mon Dec 16): # /dev/rsd0c: type: SCSI disk: SCSI disk label: SSD-PEU3 duid: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 30750 total sectors: 494010368 boundstart: 0 boundend: 494010368 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c:4940103680 unused i tried both USB ports of the Powerbook5,8. same results. this is the **correct** disklabel on amd64 OpenBSD-current (#637: Sun Dec 15): # /dev/rsd1c: type: SCSI disk: SCSI disk label: SSD-PEU3 duid: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 30750 total sectors: 494010368 boundstart: 0 boundend: 494010368 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c:4940103680 unused i:494006272 2048 ext2fs partition can be mounted properly on amd64 Linux and OpenBSD. IIRC the drive was initialized / created on Linux. i have other USB drives (whole disk, msdos format) that work properly across all 3 machines. what am i missing here? looking forward to some pointers. yorosiku ~
