Re: USB install image for OpenBSD 5.5 - TESTING REQUIRED
On Tue, Mar 18, 2014 at 12:39 PM, Chris Cappuccio wrote: > sven falempin [sven.falem...@gmail.com] wrote: > > Some issue here, using install55.fs (today 18/3/2014 downloaded snaps) > > > > boot is ok (warn: entropy file missing) > > > > but /dev has no /dev/sd1 (is the usb key) and so i cannot look for the > sets . > > > > I did MAKEDEV all so i can mount keys to get the dmesg. > > > > The install script will create the devices on demand, as needed to mount > the source sets > the installer proposed http and i was not able to the right disk > > > currently outputing dmesg on usb3 key, the machine has no plug for the > > com port, no idea how to get the boot infos (i am bad at soldering) > > > > I fdisk the key, but i cannot disklabel it ( out of inode ) > > > > This is because you ran MAKEDEV all, the ramdisk has only minimal inodes > available > -- - () ascii ribbon campaign - against html e-mail /\
Re: USB install image for OpenBSD 5.5 - TESTING REQUIRED
sven falempin [sven.falem...@gmail.com] wrote: > Some issue here, using install55.fs (today 18/3/2014 downloaded snaps) > > boot is ok (warn: entropy file missing) > > but /dev has no /dev/sd1 (is the usb key) and so i cannot look for the sets . > > I did MAKEDEV all so i can mount keys to get the dmesg. > The install script will create the devices on demand, as needed to mount the source sets > currently outputing dmesg on usb3 key, the machine has no plug for the > com port, no idea how to get the boot infos (i am bad at soldering) > > I fdisk the key, but i cannot disklabel it ( out of inode ) > This is because you ran MAKEDEV all, the ramdisk has only minimal inodes available
Re: USB install image for OpenBSD 5.5 - TESTING REQUIRED
Some issue here, using install55.fs (today 18/3/2014 downloaded snaps) boot is ok (warn: entropy file missing) but /dev has no /dev/sd1 (is the usb key) and so i cannot look for the sets . I did MAKEDEV all so i can mount keys to get the dmesg. currently outputing dmesg on usb3 key, the machine has no plug for the com port, no idea how to get the boot infos (i am bad at soldering) I fdisk the key, but i cannot disklabel it ( out of inode ) OpenBSD 5.5-current (RAMDISK_CD) #2: Mon Mar 17 17:19:05 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 4143271936 (3951MB) avail mem = 4027494400 (3840MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb630 (78 entries) bios0: vendor American Megatrends Inc. version "7920D103" date 01/07/2013 bios0: NORCO BPC-7920 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT SSDT SSDT ASF! acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, 2197.54 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 99MHz cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus -1 (PEG3) acpiprt5 at acpi0: bus -1 (P0P1) acpiprt6 at acpi0: bus 1 (RP01) acpiprt7 at acpi0: bus 2 (RP02) acpiprt8 at acpi0: bus 3 (RP03) acpiprt9 at acpi0: bus 4 (RP04) acpiprt10 at acpi0: bus 5 (RP05) acpiprt11 at acpi0: bus -1 (RP06) acpiprt12 at acpi0: bus -1 (RP07) acpiprt13 at acpi0: bus -1 (RP08) pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09 vga1 at pci0 dev 2 function 0 "Intel HD Graphics 3000" rev 0x09 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) "Intel 7 Series xHCI" rev 0x04 at pci0 dev 20 function 0 not configured "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured "Intel 7 Series KT" rev 0x04 at pci0 dev 22 function 3 not configured em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address 00:50:c2:21:60:70 ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 16 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 "Intel 7 Series HD Audio" rev 0x04 at pci0 dev 27 function 0 not configured ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi pci1 at ppb0 bus 1 em1 at pci1 dev 0 function 0 "Intel 82583V" rev 0x00: msi, address 00:50:c2:21:60:6b ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi pci2 at ppb1 bus 2 em2 at pci2 dev 0 function 0 "Intel 82583V" rev 0x00: msi, address 00:50:c2:21:60:6c ppb2 at pci0 dev 28 function 2 "Intel 7 Series PCIE" rev 0xc4: msi pci3 at ppb2 bus 3 em3 at pci3 dev 0 function 0 "Intel 82583V" rev 0x00: msi, address 00:50:c2:21:60:6d ppb3 at pci0 dev 28 function 3 "Intel 7 Series PCIE" rev 0xc4: msi pci4 at ppb3 bus 4 em4 at pci4 dev 0 function 0 "Intel 82583V" rev 0x00: msi, address 00:50:c2:21:60:6e ppb4 at pci0 dev 28 function 4 "Intel 7 Series PCIE" rev 0xc4: msi pci5 at ppb4 bus 5 em5 at pci5 dev 0 function 0 "Intel 82583V" rev 0x00: msi, address 00:50:c2:21:60:6f ehci1 at pci0 dev 29 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 23 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1 "Intel QM77 LPC" rev 0x04 at pci0 dev 31 function 0 not configured ahci0 at pci0 dev 31 function 2 "Intel 7 Series AHCI" rev 0x04: msi, AHCI 1.3 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed naa.5000c50022660557 sd0: 152627MB, 512 bytes/sector, 312581808 sectors "Intel 7 Series SMBus" rev 0x04 at pci0 dev 31 function 3 not configured isa0 at mainbus0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 uhub2 at uhub0 port 1 "vendor 0x8087 product 0x0024" rev 2.00/0.00 addr 2 uhidev0 at uhub2 port 2 configuration 1 interface 0 "Dell Dell USB Keyboard" rev 1.10/3.06 addr 3 uhidev0: iclass 3/1 ukbd0 at uhidev0 wskbd1 at ukbd0 mux 1 wskbd1: connecting to wsdisplay0 uhub3 at uhub1 port 1 "vendor 0x8087 product 0x0024" rev 2.00/0.00 addr 2 umass0 at uhub3 port 4 configuration 1 interface 0 "Kingston Dat
Re: USB install image for OpenBSD 5.5 - TESTING REQUIRED
Works ok for me. Tested on a Lenovo M58, and could go into installation. For those with Mac OSC: to be able to create the USB stick on Macintosh (MBPro), I used these commands (in a Terminal window): bash-3.2$ diskutil list /dev/disk0 #: TYPE NAMESIZE IDENTIFIER 0: GUID_partition_scheme*1.0 TB disk0 1:EFI 209.7 MB disk0s1 2: Microsoft Basic Data 50.1 GB ... disk0s5 /dev/disk1 #: TYPE NAMESIZE IDENTIFIER 0: FDisk_partition_scheme*529.2 MB disk1 1: DOS_FAT_32 DATA529.2 MB disk1s1 bash-3.2$ diskutil unmountDisk /dev/disk1 Unmount of all volumes on disk1 was successful bash-3.2$ sudo dd if=/dev/zero of=/dev/rdisk1 bs=512 count=1 1+0 records in 1+0 records out 512 bytes transferred in 0.002362 secs (216764 bytes/sec) bash-3.2$ sudo dd if=140226_install55.fs of=/dev/rdisk1 bs=1m > Am 28.02.2014 um 23:51 schrieb Chris Cappuccio : > > Here are some potential USB installer images for OpenBSD/amd64 5.5 > > http://www.nmedia.net/chris/install55.fs > http://www.nmedia.net/chris/miniroot55.fs > > The install55.fs contains full installation packages. The > miniroot55.fs is a ramdisk-kernel only (for network installation or > troubleshooting.) > > Please test either on as many amd64 machines as you can with any USB > flash and any USB-CF adapters that you have. > > Report failures and success of each image ASAP. Test as many flash > types (USB, CF-USB, old USB, new USB...) as you can. > > SPECIFICALLY, IF you have a boot failure, I need to see the dmesg output > (and the fdisk and disklabel output from the machine if possible to boot > it another way). Any error messages displayed from the boot blocks or > BIOS are also essential. om the boot blocks or > BIOS are also essential.
Re: USB install image for OpenBSD 5.5 - TESTING REQUIRED
On Mon, Mar 3, 2014 at 7:16 PM, Chris Cappuccio wrote: > Loganaden Velvindron [logana...@gmail.com] wrote: >> >> That's OpenBSD -current right ? I'm going to test it in the afternoon, >> as the CDROM >> drive has issues on my OpenBSD development machine. >> > > Yes. The correct .fs images for testing are now the i386 and amd64 snapshot > versions on the OpenBSD sites. Hi Chris, I followed your instructions, and it works fine. It loads the installer, and there are no errors. Tested on my OpenBSD dev box (AMD64) using a USB pendrive (2GB). It's currently installing by fetching remote installation files. Would you like a dmesg when the installation is completed ? -- This message is strictly personal and the opinions expressed do not represent those of my employers, either past or present.
Re: USB install image for OpenBSD 5.5 - TESTING REQUIRED
Loganaden Velvindron [logana...@gmail.com] wrote: > > That's OpenBSD -current right ? I'm going to test it in the afternoon, > as the CDROM > drive has issues on my OpenBSD development machine. > Yes. The correct .fs images for testing are now the i386 and amd64 snapshot versions on the OpenBSD sites.
Re: USB install image for OpenBSD 5.5 - TESTING REQUIRED
On Sat, Mar 1, 2014 at 7:59 AM, Chris Cappuccio wrote: > Chris Cappuccio [ch...@nmedia.net] wrote: >> The installation entails: >> >> dd if=miniroot55.fs of=/dev/rsd2c >> > > Actually, for the install55.fs image, you want to specify a block size, > (or wait ages.) > > dd if=install55.fs of=/dev/rsd2c bs=1m > > It's something like 20x faster to specify a block size on some of mine. > > The 512 byte default block size is so small, it must cause the USB key > to re-write the same physical block multiple times. These devices have > underlying blocks of 4K and larger. > That's OpenBSD -current right ? I'm going to test it in the afternoon, as the CDROM drive has issues on my OpenBSD development machine. -- This message is strictly personal and the opinions expressed do not represent those of my employers, either past or present.
Re: USB install image for OpenBSD 5.5 - TESTING REQUIRED
On Sat, Mar 1, 2014 at 5:15 AM, Alexander Hall wrote: > On 02/28/14 23:51, Chris Cappuccio wrote: > >> Here are some potential USB installer images for OpenBSD/amd64 5.5 >> >> http://www.nmedia.net/chris/install55.fs >> http://www.nmedia.net/chris/miniroot55.fs >> >> The install55.fs contains full installation packages. The >> miniroot55.fs is a ramdisk-kernel only (for network installation or >> troubleshooting.) >> > > It might be obvious, but since it confused me for a bit, I'd like to > correct this an say that miniroot55.fs *contains* a ramdisk kernel only. It > is still a complete disk image. > > /Alexander > > > >> Please test either on as many amd64 machines as you can with any USB >> flash and any USB-CF adapters that you have. >> >> Report failures and success of each image ASAP. Test as many flash >> types (USB, CF-USB, old USB, new USB...) as you can. >> >> SPECIFICALLY, IF you have a boot failure, I need to see the dmesg output >> (and the fdisk and disklabel output from the machine if possible to boot >> it another way). Any error messages displayed from the boot blocks or >> BIOS are also essential. >> >> > Works well for me, an error about the entropy pool not being created seemed reasonable to me. Only tried on it from USB on an old Net-Burst era system. Installed very nicely, way faster than cd or lan, and also quicker than my previous USB installs, although this media's new to me.
Re: USB install image for OpenBSD 5.5 - TESTING REQUIRED
On 02/28/14 23:51, Chris Cappuccio wrote: Here are some potential USB installer images for OpenBSD/amd64 5.5 http://www.nmedia.net/chris/install55.fs http://www.nmedia.net/chris/miniroot55.fs The install55.fs contains full installation packages. The miniroot55.fs is a ramdisk-kernel only (for network installation or troubleshooting.) It might be obvious, but since it confused me for a bit, I'd like to correct this an say that miniroot55.fs *contains* a ramdisk kernel only. It is still a complete disk image. /Alexander Please test either on as many amd64 machines as you can with any USB flash and any USB-CF adapters that you have. Report failures and success of each image ASAP. Test as many flash types (USB, CF-USB, old USB, new USB...) as you can. SPECIFICALLY, IF you have a boot failure, I need to see the dmesg output (and the fdisk and disklabel output from the machine if possible to boot it another way). Any error messages displayed from the boot blocks or BIOS are also essential.
Re: USB install image for OpenBSD 5.5 - TESTING REQUIRED
Chris Cappuccio [ch...@nmedia.net] wrote: > The installation entails: > > dd if=miniroot55.fs of=/dev/rsd2c > Actually, for the install55.fs image, you want to specify a block size, (or wait ages.) dd if=install55.fs of=/dev/rsd2c bs=1m It's something like 20x faster to specify a block size on some of mine. The 512 byte default block size is so small, it must cause the USB key to re-write the same physical block multiple times. These devices have underlying blocks of 4K and larger.
Re: USB install image for OpenBSD 5.5 - TESTING REQUIRED
The installation entails: dd if=miniroot55.fs of=/dev/rsd2c Assuming your USB key is identified as 'sd2' after you plug it in (Be careful not to write over a system disk!) Also you can use physdiskwrite or other tools on Windows or other platforms. All tests are welcome.
USB install image for OpenBSD 5.5 - TESTING REQUIRED
Here are some potential USB installer images for OpenBSD/amd64 5.5 http://www.nmedia.net/chris/install55.fs http://www.nmedia.net/chris/miniroot55.fs The install55.fs contains full installation packages. The miniroot55.fs is a ramdisk-kernel only (for network installation or troubleshooting.) Please test either on as many amd64 machines as you can with any USB flash and any USB-CF adapters that you have. Report failures and success of each image ASAP. Test as many flash types (USB, CF-USB, old USB, new USB...) as you can. SPECIFICALLY, IF you have a boot failure, I need to see the dmesg output (and the fdisk and disklabel output from the machine if possible to boot it another way). Any error messages displayed from the boot blocks or BIOS are also essential.
