Re: OpenBSD 6.5 on Clevo W840SU: BIOS hangs when booted via (m)SATA
> 22. mar. 2019 kl. 07:16 skrev Peter Nicolai Mathias Hansteen > : >> Dear Peter, can you remember more details how you got OpenBSD to work on that >> Clevo W840-SU by any chance? Did you use SSD or HDD for the booting disk? > > I considered it fairly obvious that I wanted the fastest one (the SSD) for > the system disk. I did not make any special preparations for that one (which > means the MBR would be intact), but it is entirely possible that I went for > the old-style (non-UEFI) option. The MBR removal was on the slightly roomier > HDD which I intended to use for /home. > I should perhaps add to that, I was a little quick in typing up the previous answer. If I remember correctly, I chose the old-style (not «secure boot») BIOS options, did a fairly regular install at first, but ran into something very much like the symptoms you describe. My conclusion then was that for whatever reason the system was trying to boot from the HDD (which then had an MBR but nothing else required for a boot disk), not the SSD. After quite a bit of mucking about with options I never documented properly, as I remember it what gave me a functional system with the SSD as the system disk and I think something very close to the OpenBSD installer’s default partitioning plus the roomier HDD (later replaced with a same-size SSD but that@s another story) involved removing the MBR on the HDD. Then again, this was several years ago so and I did not make any notes that have survived while I was doing this. As you have seen already, you will need an MBR on the disk you intend to boot from. - Peter — Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. signature.asc Description: Message signed with OpenPGP
Re: OpenBSD 6.5 on Clevo W840SU: BIOS hangs when booted via (m)SATA
> 21. mar. 2019 kl. 22:55 skrev fink...@dismail.de: > > Dear Peter and all. > > Unfortunately I celebrated to early it seems. :-/ > > In my last post I described a hack in which I let the OpenBSD partition > start at "sector 0" in order to avoid BIOS hangup. > > When I now tried this way of setup with a SSD disk instead of HDD, > after a succesful install, OpenBSD boots with the following Kernel panic: > > "openbsd panic root filesystem has size 0" > > For this I found the following post talking about "partition offset" [1]. > > It explains: > > "Sector 0 can't be used for a partition, because it's occupied by the MBR > partition table" > > So I believe the "Sector 0" hack is actually breaking things (as the fdisk > output > of the result parition table also suggests). > > Dear Peter, can you remember more details how you got OpenBSD to work on that > Clevo W840-SU by any chance? Did you use SSD or HDD for the booting disk? I considered it fairly obvious that I wanted the fastest one (the SSD) for the system disk. I did not make any special preparations for that one (which means the MBR would be intact), but it is entirely possible that I went for the old-style (non-UEFI) option. The MBR removal was on the slightly roomier HDD which I intended to use for /home. - Peter — Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. signature.asc Description: Message signed with OpenPGP
dhclient.leases.vio0: expecting colon delimited list of hex octets
I installed the Mar 21 snapshot on Google Compute Engine and noticed a
curious entry
on the system console:
starting network
vio0: /var/db/dhclient.leases.vio0 line 30: expecting colon delimited list
of hex octets.
vio0: option domain-search c.
vio0: ^
vio0: bound to 10.128.0.237 from 169.254.169.254 (42:01:0a:80:00:01)
File contents:
openbsd$ doas cat /var/db/dhclient.leases.vio0
lease {
fixed-address 10.0.2.15;
next-server 10.0.2.2;
option subnet-mask 255.255.255.0;
option routers 10.0.2.2;
option domain-name-servers 10.0.2.3;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option dhcp-server-identifier 10.0.2.2;
option dhcp-client-identifier 1:52:54:0:12:34:56;
epoch 1553225096;
renew 5 2019/03/22 15:24:56 UTC;
rebind 6 2019/03/23 00:24:56 UTC;
expire 6 2019/03/23 03:24:56 UTC;
}
lease {
fixed-address 10.128.0.237;
next-server 10.128.0.1;
option subnet-mask 255.255.255.255;
option routers 10.128.0.1;
option domain-name-servers 169.254.169.254;
option host-name "gnezdo-openbsd.c.syzkaller.internal";
option domain-name "c.syzkaller.internal";
option interface-mtu 1460;
option ntp-servers 169.254.169.254;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option dhcp-server-identifier 169.254.169.254;
option dhcp-client-identifier 1:42:1:a:80:0:ed;
option domain-search c.syzkaller.internal. google.internal.;
option classless-static-routes 10.128.0.1/32 0.0.0.0, 0.0.0.0/0
10.128.0.1;
epoch 1553227756;
renew 5 2019/03/22 16:09:16 UTC;
rebind 6 2019/03/23 01:09:16 UTC;
expire 6 2019/03/23 04:09:16 UTC;
}
--
nest.cx is Gmail hosted, use PGP for anything private. Key:
http://goo.gl/6dMsr
Fingerprint: 5E2B 2D0E 1E03 2046 BEC3 4D50 0B15 42BD 8DF5 A1B0
Re: using an USB stick with "openbsd" type partition/slices
On 3/21/19 6:49 AM, Mihai Popescu wrote: > Hello, > > I want to move my usb stick from msdos partition to more specific to > OpenBSD. I use this stick to keep some configuration files and > documents on it. > > sd1 at scsibus2 targ 1 lun 0: SCSI4 > 0/direct fixed serial.07815571010812120514 > sd1: 30532MB, 512 bytes/sector, 62530624 sectors > > Steps I've done to achieve this: > > # fdisk -e sd1 >> reinit ... > # disklabel -E sd1 > Label editor (enter '?' for help at any prompt) ...[create an a partition, proper starting offset, etc.] > # newfs sd1a ... > > For mount I use mount /dev/sd1a /mnt. (no options yet!) > > I want to ask if there are some suggestions in creating > partition(s)/slice(s), types and mount options, please. I don't need > softupdates. Files used are small and I copy a few at the time. Well...if you are just moving files around, I wouldn't worry much about partitioning. If you want to actually make it bootable, that's a different discussion. Only exception I can think of -- if you want to split it between OpenBSD and Windows use, fdisk to make a DOS partition (first) and an OpenBSD fdisk partition (physically after the DOS/FAT partition), disklabel it and format it on Windows, then format it on OpenBSD. Few small files a few at a time? Just use the defaults. If performance matters, mounting with "noatime" and "softdep" are HUGE wins. If you aren't waiting, though, you won't get any benefit, so just use the defaults. Nick.
Re: OpenBSD 6.5 on Clevo W840SU: BIOS hangs when booted via (m)SATA
Dear Peter and all. Unfortunately I celebrated to early it seems. :-/ In my last post I described a hack in which I let the OpenBSD partition start at "sector 0" in order to avoid BIOS hangup. When I now tried this way of setup with a SSD disk instead of HDD, after a succesful install, OpenBSD boots with the following Kernel panic: "openbsd panic root filesystem has size 0" For this I found the following post talking about "partition offset" [1]. It explains: "Sector 0 can't be used for a partition, because it's occupied by the MBR partition table" So I believe the "Sector 0" hack is actually breaking things (as the fdisk output of the result parition table also suggests). Dear Peter, can you remember more details how you got OpenBSD to work on that Clevo W840-SU by any chance? Did you use SSD or HDD for the booting disk? > March 20, 2019 8:46 AM, "Peter N. M. Hansteen" wrote: > "I *think* what I did back then was set the all parts to size zero, except > the OpenBSD part which I set to the largest > the program would let me." What were the other parts (partitions)? Any further ideas and hints what I could try? Thank you very much. Fox --- [1] https://unix.stackexchange.com/questions/148589/partition-offset-at-63-or-64
Golang under Arm or Octeon
Hi Misc, I want to learn if there is any work-in-progress port for Golang under Arm or Octeon cpu architectures? Thanks. -- Best wishes Valdrin Muja
libssl/libtls signal the wrong signature algorithm in ServerKeyExchange message
In case an ECDSA based server certificate with ECDHE based key exchange is used, I've notice that the ServerKeyExchange message (always?) signals that this message has been signed with ecdsa-secp521r1-sha512 (0x0603) [tested on current with TLS 1.2 with P-256 as well as with P-521 server certificates -- the actual signature sizes differ as expected but the signalling of the signature algorithm is identical in both cases]. Example: in case the server certificate contains a P-256 based public key, the actually provided signature for the ServerKeyExchange message is ecdsa-secp256r1-sha256. However, the signature algorithm field signals 0x(0603) [ecdsa-secp521r1-sha512] instead of 0x(0403) [ecdsa-secp256r1-sha256]. Multiple TLS libraries seem to behave this way, but, according to RFCs, I would expect the actually used signature algorithm to be provided with the ServerKeyExchange message. Could someone please clarify if this is a bug? Slightly related: is there a good reason why libtls doesn't provide an API call for explicitly configuring allowed signature algorithms (via Signature Algorithms extension)? (e.g., in order to ensure that ecdsa-sha1 0x(0203) is not included in the list). Best regards Andreas
Re: Leveldb in 6.4
On Thu, Mar 21, 2019 at 03:54:25PM +0100, Flipchan wrote: > Hey all, > > Has anyone been able to install leveldb on 6.4 with header files ? > > > i have installed it with pkg_add > # pkg_info -Q leveldb > leveldb-1.20 (installed) > > but it will not include: > > fatal error: 'leveldb/db.h' file not found > #include "leveldb/db.h" > ^~ > 7 warnings and 1 error generated. > error: command 'cc' failed with exit status 1 You probably need to pass CPPFLAGS (-I/usr/local/include) to your build. -- Antoine
Leveldb in 6.4
Hey all, Has anyone been able to install leveldb on 6.4 with header files ? i have installed it with pkg_add # pkg_info -Q leveldb leveldb-1.20 (installed) but it will not include: fatal error: 'leveldb/db.h' file not found #include "leveldb/db.h" ^~ 7 warnings and 1 error generated. error: command 'cc' failed with exit status 1 - flipchan
using an USB stick with "openbsd" type partition/slices
Hello, I want to move my usb stick from msdos partition to more specific to OpenBSD. I use this stick to keep some configuration files and documents on it. sd1 at scsibus2 targ 1 lun 0: SCSI4 0/direct fixed serial.07815571010812120514 sd1: 30532MB, 512 bytes/sector, 62530624 sectors Steps I've done to achieve this: # fdisk -e sd1 > reinit >q # fdisk sd1 Disk: sd1 geometry: 30532/64/32 [62530624 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: A6 0 2 1 - 30529 49 20 [ 64:62524916 ] OpenBSD # disklabel -E sd1 Label editor (enter '?' for help at any prompt) >p OpenBSD area: 64-62524980; size: 62524916; free: 62524916 #size offset fstype [fsize bsize cpg] c: 625306240 unused > a partition: [a] offset: [64] size: [62524916] FS type: [4.2BSD] > p OpenBSD area: 64-62524980; size: 62524916; free: 20 #size offset fstype [fsize bsize cpg] a: 62524896 64 4.2BSD 2048 16384 1 c: 625306240 unused > w > q No label changes. # newfs sd1a /dev/rsd1a: 30529.7MB in 62524896 sectors of 512 bytes 151 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each super-block backups (for fsck -b #) at: 32, 414688, 829344, 1244000, 1658656, 2073312, 2487968, 2902624, 3317280, 3731936, 4146592, 4561248, 4975904, 5390560, 5805216, 6219872, 6634528, 7049184, 7463840, 7878496, 8293152, 8707808, 9122464, 9537120, 9951776, 10366432, 10781088, 11195744, 11610400, 12025056, 12439712, 12854368, 13269024, 13683680, 14098336, 14512992, 14927648, 15342304, 15756960, 16171616, 16586272, 17000928, 17415584, 17830240, 18244896, 18659552, 19074208, 19488864, 19903520, 20318176, 20732832, 21147488, 21562144, 21976800, 22391456, 22806112, 23220768, 23635424, 24050080, 24464736, 24879392, 25294048, 25708704, 26123360, 26538016, 26952672, 27367328, 27781984, 28196640, 28611296, 29025952, 29440608, 29855264, 30269920, 30684576, 31099232, 31513888, 31928544, 32343200, 32757856, 33172512, 33587168, 34001824, 34416480, 34831136, 35245792, 35660448, 36075104, 36489760, 36904416, 37319072, 37733728, 38148384, 38563040, 38977696, 39392352, 39807008, 40221664, 40636320, 41050976, 41465632, 41880288, 42294944, 42709600, 43124256, 43538912, 43953568, 44368224, 44782880, 45197536, 45612192, 46026848, 46441504, 46856160, 47270816, 47685472, 48100128, 48514784, 48929440, 49344096, 49758752, 50173408, 50588064, 51002720, 51417376, 51832032, 52246688, 52661344, 53076000, 53490656, 53905312, 54319968, 54734624, 55149280, 55563936, 55978592, 56393248, 56807904, 57222560, 57637216, 58051872, 58466528, 58881184, 59295840, 59710496, 60125152, 60539808, 60954464, 61369120, 61783776, 62198432, For mount I use mount /dev/sd1a /mnt. (no options yet!) I want to ask if there are some suggestions in creating partition(s)/slice(s), types and mount options, please. I don't need softupdates. Files used are small and I copy a few at the time. Thank you.
