Re: OpenBSD -current AHCI on HP Probook 450 G0
On Monday, 22 December 2014, 4:02, Doug Hogan d...@acyclic.org wrote: On Sun, Dec 21, 2014 at 10:05:22AM +, ali wrote: Atanas Vladimirov vlado at bsdbg.net writes: This is the first time when I try to install OpenBSD on a such hardware. I used bsd.rd to install it on a usb flash drive. After reboot I choose to boot from the usb drive. Bootloader can't load bsd kernel and the laptop restarts without error. If I change SATA mode in BIOS from AHCI to IDE I can boot from the usb drive. I have the same problem with my HP ProBook 4530s. I don't want to switch to AHCI. Is there another way to install OpenBSD? One of my laptops is a 4530s. I was able to install by using a CD. It's running snapshots so I upgrade with bsd.rd. I'm using BIOS F.41 if that helps. Sorry, I said something mistakenly. I don't want to switch from AHCI to IDE. It seems that OpenBSD kernel will not load correctly when AHCI is enabled. Are you sure that AHCI was enabled during installation?
Re: free ipv6 KVM-based - cloudspin.me [was - Re: DigitalOcean's BSD debut is FreeBSD only]
On Sun, Dec 21, 2014 at 06:08:04PM -0500, Jiri B wrote: On Sun, Dec 21, 2014 at 01:54:50AM +, Some Developer wrote: Vultr already support OpenBSD on their servers (you upload the OpenBSD install ISO and install it yourself) and their servers cost the same as Digital Ocean. Performance is good. They support IPv6 and they have more locations than Digital Ocean. Overall very pleased with them. My coll told me about cloudspin.me, it's oVirt/KVM based service, free of charge, public IPv6 only. oVirt is upstream OSS project for Red Hat Enterprise Virtualization. cloudspin.me does not offer OpenBSD image, what a suprise, but I suppose everybody is able to `dd' minirootXX.fs onto virtio disk :) It now offers an OpenBSD iso, runs just fine... Looks like some random dude finally implemented xkcd 908 j. -- I'm not entirely sure you are real.
Re: Any experience running OpenBSD 5.6 or current on a Shuttle DS437?
On Sun, Dec 21, 2014 at 11:45 PM, Marcus MERIGHI mcmer-open...@tor.at wrote: No boot? With mine (XS35, DS437) it's just no VGA. On my Shuttle, without a display plugged in, it will not boot. Unfortunately, I don't know why since to see any kind of error message...:-) I haven't found anything relevant in the BIOS - the ignore all errors doesn't fix it. It's possible this particular box is buggy.
athn(4) WPA2-PSK software crypto CPU loading
I'm considering setting up a wifi access point using a PC Engines ALIX board (500 MHz AMD Geode LX800 CPU, 256 MB RAM). One way of providing the wifi is via a radio card (e.g., the PC Engines DNMA92) in the ALIX box. This uses the Atheros AR9220 chipset, which has good OpenBSD support -- including 802.11a/b/g WPA2-PSK support (though not 802.11n) -- via athn(4). However, 'man athn' says The athn driver relies on the software 802.11 stack for both encryption and decryption of data frames. Should I be worried about the CPU loading of software WPA2 crypto running on the (relatively slow) ALIX Geode processor? That is, is the software crypto likely to limit the available wifi data rate? ciao, -- -- Jonathan Thornburg [remove -animal to reply] jth...@astro.indiana-zebra.edu Dept of Astronomy IUCSS, Indiana University, Bloomington, Indiana, USA There was of course no way of knowing whether you were being watched at any given moment. How often, or on what system, the Thought Police plugged in on any individual wire was guesswork. It was even conceivable that they watched everybody all the time. -- George Orwell, 1984
Re: DigitalOcean's BSD debut is FreeBSD only
I should mention that RamNode offers OpenBSD -release without the need to upload any images: you can choose OpenBSD i386 or amd64 from the pre-loaded CD images for KVM servers. I have to run `cd /dev ./MAKEDEV all` after installation, though [*], to avoid getting daily insecurity reports. (Thanks, Benjamin!) Cheers! Ezequiel [*] https://www.marc.info/?l=openbsd-miscm=141768511309276w=2
Stop console logging during install
I'm trying to create an appliance like install and want to stop logging to console. So this is during the install process, not a normally running machine. I know this is very useful information, but this would definitely be nice to disable for a bit. In particular when running bioctl to setup a softraid device with CRYPTO, console outputs a new disk is attached, but I don't want this to show. My guess is a boot option but I've looked around a lot and can't find a way. Coming to the conclusion that I'll need to edit and compile the kernel to turn that off, but I hope not. Thanks
Re: free ipv6 KVM-based - cloudspin.me [was - Re: DigitalOcean's BSD debut is FreeBSD only]
On Dec 22, 2014, at 9:43 AM, Florian Obser wrote: On Sun, Dec 21, 2014 at 06:08:04PM -0500, Jiri B wrote: On Sun, Dec 21, 2014 at 01:54:50AM +, Some Developer wrote: Vultr already support OpenBSD on their servers (you upload the OpenBSD install ISO and install it yourself) and their servers cost the same as Digital Ocean. Performance is good. They support IPv6 and they have more locations than Digital Ocean. Overall very pleased with them. My coll told me about cloudspin.me, it's oVirt/KVM based service, free of charge, public IPv6 only. oVirt is upstream OSS project for Red Hat Enterprise Virtualization. cloudspin.me does not offer OpenBSD image, what a suprise, but I suppose everybody is able to `dd' minirootXX.fs onto virtio disk :) It now offers an OpenBSD iso, runs just fine... Looks like some random dude finally implemented xkcd 908 j. -- I'm not entirely sure you are real. Recently started using Vultr due to this post and it works great.
re(4) watchdog timeout on PCEngine APU
Hi, I recently installed PCEngine APU with 4GB ram as a SOHO router/firewall, with OpenBSD 5.6. It works as expected at first, network interfaces started to fail with re1: watchdog timeout messages, and recovered after about an hour. Here's a syslog message during failure. Dec 22 21:42:38 moomin /bsd: re2: watchdog timeout Dec 22 21:42:54 moomin /bsd: re2: watchdog timeout Dec 22 21:44:45 moomin last message repeated 4 times Dec 22 21:51:27 moomin last message repeated 8 times Dec 22 22:03:41 moomin last message repeated 2 times Dec 22 22:14:21 moomin last message repeated 3 times Dec 22 22:23:58 moomin last message repeated 4 times Dec 22 22:26:32 moomin /bsd: re2: watchdog timeout There are several failures after intallation, about one per day. I searched a mailing list but couldn't find similar cases. Is there any suggestions to figure out the root of the problem? Here's more output from dmesg/netstat/... root@moomin:~# dmesg | grep watchdog | sort | uniq -c 32 re1: watchdog timeout 48 re2: watchdog timeout root@moomin:/var/log# netstat -I re0 NameMtu Network Address Ipkts IerrsOpkts Oerrs Colls re0 1500 Link 00:0d:b9:35:ac:94 33742 0 68453304 0 0 re0 1500 221.146.251 221.146.251.225 33742 0 68453304 0 0 root@moomin:/var/log# netstat -I re1 NameMtu Network Address Ipkts IerrsOpkts Oerrs Colls re1 1500 Link 00:0d:b9:35:ac:95 49606510 0 67064308 32 0 re1 1500 10.0.6/24 10.0.6.1 49606510 0 67064308 32 0 root@moomin:/var/log# netstat -I re2 NameMtu Network Address Ipkts IerrsOpkts Oerrs Colls re2 1500 Link 00:0d:b9:35:ac:96 21207498 0 35034490 48 0 re2 1500 10.0.7/24 10.0.7.1 21207498 0 35034490 48 0 Here's dmesg output OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug 8 00:20:21 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4246003712 (4049MB) avail mem = 4124192768 (3933MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdf16d820 (6 entries) bios0: vendor coreboot version SageBios_PCEngines_APU-45 date 04/05/2014 bios0: PC Engines APU acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP SPCR HPET APIC HEST SSDT SSDT SSDT acpi0: wakeup devices AGPB(S4) HDMI(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) PIBR(S4) UOH1(S3) UOH2(S3) UOH3(S3) UOH4(S3) UOH5(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD G-T40E Processor, 1000.12 MHz 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,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: 8 4MB entries fully associative cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, C-substates=0.0.0.0.0, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD G-T40E Processor, 1000.00 MHz 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,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: 8 4MB entries fully associative cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpiprt0 at acpi0: bus -1 (AGPB) acpiprt1 at acpi0: bus -1 (HDMI) acpiprt2 at acpi0: bus 1 (PBR4) acpiprt3 at acpi0: bus 2 (PBR5) acpiprt4 at acpi0: bus 3 (PBR6) acpiprt5 at acpi0: bus -1 (PBR7) acpiprt6 at acpi0: bus 5 (PE20) acpiprt7 at acpi0: bus -1 (PE21) acpiprt8 at acpi0: bus -1 (PE22) acpiprt9 at acpi0: bus -1 (PE23) acpiprt10 at acpi0: bus 0 (PCI0) acpiprt11 at acpi0: bus 4 (PIBR) acpicpu0 at acpi0: C2, PSS acpicpu1 at acpi0: C2, PSS acpibtn0 at acpi0: PWRB cpu0: 1000 MHz: speeds: 1000 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 AMD AMD64 14h Host rev 0x00 ppb0 at pci0 dev 4 function 0 AMD AMD64 14h PCIE rev 0x00: msi pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E (0x2c00), msi, address 00:0d:b9:35:ac:94 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 4 ppb1 at pci0 dev 5 function 0 AMD AMD64 14h PCIE rev 0x00: msi pci2 at ppb1 bus 2 re1 at pci2 dev 0 function 0 Realtek 8168 rev 0x06:
Openbsd broke my hard drive twice! Getting frustrated
Hi, I decided to install openbsd by the first time a month ago, How I was with no internet connection I needed to shutdown the computer in the part that I need to download the packages, because I hadn't it on the cd. I could not acess the command line so I clicked the reset button on the front panel. When I tried to turn on again, the system didn't boot. I discovered that it only worked if I remove the hard drive. Thinking that the problem was the harddrive I sent it to warranty to be repleaced. I took 10 long days (withou my computer) to arrive a new one. When it arrived, I tested and I saw that now it is working. I prepared a cable connection, and I started again the openbsd setup. It sucefully downloaded and installed everything, so I rebooted the system to boot my new fresh install. AND SHIT, everything happened as before, the system don't boot as before, I can't open the bios as before, and I got really mad. I don't know if I will be able to sent it to warranty again, but this isn't the right thing to do now that I discovered that the problem isn't with it, the problem is with Openbsd. Could someone please explain me why this happened? Can you think about a way to fix this without send it to warranty? Any other questions? send me a reply, I'm really in need of help -- Henrique Lengler
Re: Openbsd broke my hard drive twice! Getting frustrated
On Tue, Dec 23, 2014 at 12:04:25AM -0200, Henrique Lengler wrote: Could someone please explain me why this happened? Can you think about a way to fix this without send it to warranty? Any other questions? send me a reply, I'm really in need of help # cd /usr/src/distrib/miniroot/ # grep -B3 'inconsistent state' install.sub At any prompt except password prompts you can escape to a shell by typing '!'. Default answers are shown in []'s and are selected by pressing RETURN. You can exist this program at any time by pressing Control-C, but this can leave your system in an inconsistent state. Did you not see this warning while installing?
Re: Openbsd broke my hard drive twice! Getting frustrated
On 2014-12-23 00:12, OpenBSD lists wrote: # cd /usr/src/distrib/miniroot/ # grep -B3 'inconsistent state' install.sub At any prompt except password prompts you can escape to a shell by typing '!'. Default answers are shown in []'s and are selected by pressing RETURN. You can exist this program at any time by pressing Control-C, but this can leave your system in an inconsistent state. Did you not see this warning while installing? What about my second attempt, in which I did everything normally and the same problem happened? -- Henrique Lengler
Re: Openbsd broke my hard drive twice! Getting frustrated
Have you tried installing something other than OpenBSD since you ran into this issue?
Re: Openbsd broke my hard drive twice! Getting frustrated
On 2014-12-23 00:50, Edgar Pettijohn III wrote: Have you tried installing something other than OpenBSD since you ran into this issue? Since I ran into this issue I can't even access my bios with the HDD sata connected. -- Henrique Lengler
Re: Openbsd broke my hard drive twice! Getting frustrated
On 2014-12-23 00:53, Edgar Pettijohn III wrote: So if you stick in a disk with an iso from some other os it won't boot from the cd without you accessing bios? I didn't and I can't try this because I don't have any other HDD here. But it can boot my CD/DVD reader with a cd containing Linux, wich is connected via a SATA cable too. I tried to change HDD the cable and the port, and anything solved. -- Henrique Lengler
Re: Openbsd broke my hard drive twice! Getting frustrated
On Tue, Dec 23, 2014 at 00:53, Henrique Lengler wrote: On 2014-12-23 00:50, Edgar Pettijohn III wrote: Have you tried installing something other than OpenBSD since you ran into this issue? Since I ran into this issue I can't even access my bios with the HDD sata connected. That can only be a problem with your BIOS. Update it? Get a better one? I don't know. But if your BIOS doesn't work with some drive attached, your BIOS is broken.
Re: Openbsd broke my hard drive twice! Getting frustrated
On 2014-12-23 01:02, Ted Unangst wrote: That can only be a problem with your BIOS. Update it? Get a better one? I don't know. But if your BIOS doesn't work with some drive attached, your BIOS is broken. How can you say this? The problem isn't my BIOS don't booting with a broke HDD. I have evidences it work if I put a working drive. My motherboard is very new and it every worked good in any type of system. -- Henrique Lengler
Re: Openbsd broke my hard drive twice! Getting frustrated
Henrique Lengler henriquel...@openmailbox.org wrote: On 2014-12-23 00:50, Edgar Pettijohn III wrote: Have you tried installing something other than OpenBSD since you ran into this issue? Since I ran into this issue I can't even access my bios with the HDD sata connected. -- Henrique Lengler It would be exceedingly odd for OpenBSD to be able to break that. Has anything ever been installed successfully on this machine? Perhaps the motherboard or power supply causes damage after extended use. -- Martin
Re: Openbsd broke my hard drive twice! Getting frustrated
On 2014-12-23 01:08, mar...@martinbrandenburg.com wrote: Has anything ever been installed successfully on this machine? Perhaps the motherboard or power supply causes damage after extended use. -- Martin Yes, my motherboard and power supply have 1 year of use, it every worked, and still working good. The evidence is that after try to install OpenBSD by the second time, I did a test, I reboot my system three times, accessed bios and everything worked. -- Henrique Lengler
Re: Openbsd broke my hard drive twice! Getting frustrated
On 2014-12-23 01:11, Henrique Lengler wrote: Yes, my motherboard and power supply have 1 year of use, it every worked, and still working good. The evidence is that after try to install OpenBSD by the I mean before -- Henrique Lengler
Re: Openbsd broke my hard drive twice! Getting frustrated
Henrique Lengler henriquel...@openmailbox.org wrote: On 2014-12-23 01:08, mar...@martinbrandenburg.com wrote: Has anything ever been installed successfully on this machine? Perhaps the motherboard or power supply causes damage after extended use. -- Martin Yes, my motherboard and power supply have 1 year of use, it every worked, and still working good. The evidence is that after try to install OpenBSD by the second time, I did a test, I reboot my system three times, accessed bios and everything worked. -- Henrique Lengler Does the disk that you claim OpenBSD damaged still work in a different computer? I was being nice when I said exceedingly odd. It's more like impossible. You come here with an impossible problem and no information. You haven't even said what type of computer this is. I realize a dmesg is impossible when it won't boot (though you could unplug the offending disk and get a dmesg from the CD), but some information would be nice. -- Martin
Re: Openbsd broke my hard drive twice! Getting frustrated
On 2014-12-23 01:18, mar...@martinbrandenburg.com wrote: Does the disk that you claim OpenBSD damaged still work in a different computer? Will be difficult to me can do this, I don't have any other desktop in my house. I will see if I can do this later. I was being nice when I said exceedingly odd. It's more like impossible. You come here with an impossible problem and no information. You haven't even said what type of computer this is. I realize a dmesg is impossible when it won't boot (though you could unplug the offending disk and get a dmesg from the CD), but some information would be nice. Isn't the operating system responsible to recognize and use with a correct driver my HDD? Linux is like this, the kernel have the SATA driver wich handle the drivers. Regards, -- Henrique Lengler
Re: Openbsd broke my hard drive twice! Getting frustrated
On Tue, Dec 23, 2014 at 12:42:25AM -0200, Henrique Lengler wrote: On 2014-12-23 00:12, OpenBSD lists wrote: # cd /usr/src/distrib/miniroot/ # grep -B3 'inconsistent state' install.sub At any prompt except password prompts you can escape to a shell by typing '!'. Default answers are shown in []'s and are selected by pressing RETURN. You can exist this program at any time by pressing Control-C, but this can leave your system in an inconsistent state. Did you not see this warning while installing? What about my second attempt in which I did everything normally? -- Henrique Lengler Here's a silly question...is it an EFI system? I would think the installer wouldn't boot properly if so, but you may have to go into your BIOS and set it up for legacy boot? I don't know. I've never heard of an OS install causing physical damage to a machine (though a few FreeBSD installs I performed around the 6.X/7.X timeframe caused *me* to harm a computer =).
Re: Openbsd broke my hard drive twice! Getting frustrated
On 2014-12-23 02:00, Jonathon Sisson wrote: Here's a silly question...is it an EFI system? I would think the installer wouldn't boot properly if so, but you may have to go into your BIOS and set it up for legacy boot? Yes, it's a EFI system. How this would help if it can't even recognize the disk. Just in case, I already used Linux with a totally BIOS setup and it worked. I don't know. I've never heard of an OS install causing physical damage to a machine (though a few FreeBSD installs I performed around the 6.X/7.X timeframe caused *me* to harm a computer =). I'm also surprised with this, but I'm almost sure that it happened. I think we should study this and find the real problem cause. Regards, -- Henrique Lengler
Re: Openbsd broke my hard drive twice! Getting frustrated
On Mon, Dec 22, 2014, at 10:23 PM, Henrique Lengler wrote: On 2014-12-23 01:18, mar...@martinbrandenburg.com wrote: Does the disk that you claim OpenBSD damaged still work in a different computer? Will be difficult to me can do this, I don't have any other desktop in my house. I will see if I can do this later. I was being nice when I said exceedingly odd. It's more like impossible. You come here with an impossible problem and no information. You haven't even said what type of computer this is. I realize a dmesg is impossible when it won't boot (though you could unplug the offending disk and get a dmesg from the CD), but some information would be nice. Isn't the operating system responsible to recognize and use with a correct driver my HDD? Linux is like this, the kernel have the SATA driver wich handle the drivers. No. This is done by the BIOS. After the computer boots the BIOS then hands over control to the OS. And yes, that is a gross over simplification of what actually happens. There is no way that any OS can 'break' a hard drive. And since your computer is fairly new it probably uses UEFI. You might try to go into your BIOS settings and try a 'Legacy' boot option.
Re: Openbsd broke my hard drive twice! Getting frustrated
Ouch. On Tue, Dec 23, 2014 at 11:04 AM, Henrique Lengler henriquel...@openmailbox.org wrote: Hi, I decided to install openbsd by the first time a month ago, How I was with no internet connection I guess you mean, no other way to access the internet. By the way, how are you accessing the internet now? I needed to shutdown the computer Don't do that. It hurts. I promise. Avoid it if at all possible by planning ahead. in the part that I need to download the packages, Yeah. This is where you need to plan ahead. because I hadn't it on the cd. So, you downloaded the wrong CD image. Perhaps it was cd56.iso? Getting the right CD is part of planning ahead. Or perhaps you forgot to write down the URL for a nearby mirror before you started, so you could tell the installer to get the stuff from a mirror. For example, http://ftp.jaist.ac.jp/pub/OpenBSD/ is a mirror in Japan, which is sort of close to where I am. I have to admit, I hate to write those urls down, too. But this is also part of planning ahead. The file sets for a 32 bit intel or AMD CPU would be in http://ftp.jaist.ac.jp/pub/OpenBSD/5.5/i386/ for the above mirror. Buying the CD set would solve that problem, although you'd have to wait for shipping. Or you could download the install56.iso image, to have enough packages for a working command-line system. As another aside, these pages in the FAQ should help you plan ahead better: http://www.openbsd.org/faq/index.html I could not acess the command line so I clicked the reset button on the front panel. ctrl-C might have gotten you to a command line? When I tried to turn on again, the system didn't boot. That's not too surprising. Although, I wonder, did you notice how far it got in the boot process before it stopped? You might want to read through these, to help you describe how far you are getting: http://en.wikipedia.org/wiki/Booting http://www.openbsd.org/faq/faq14.html#Boot386 I discovered that it only worked if I remove the hard drive. I suppose you mean that it would boot the install CD? There could be boot device order issues. Thinking that the problem was the harddrive I sent it to warranty to be repleaced. Definitely a drastic step. I took 10 long days (withou my computer) to arrive a new one. When it arrived, I tested and I saw that now it is working. I prepared a cable connection, and I started again the openbsd setup. It sucefully downloaded and installed everything, so I rebooted the system to boot my new fresh install. I see from your later posts that you have installed Linux before. You should understand there is a difference between Linux and openbsd. Openbsd does not install a bootloader for you. This part of the FAQ should provide some useful information: http://www.openbsd.org/faq/faq4.html#Multibooting AND SHIT, everything happened as before, the system don't boot as before, I can't open the bios as before, How did you open the BIOS when you were able to open the BIOS? and I got really mad. I don't know if I will be able to sent it to warranty again, but this isn't the right thing to do now that I discovered that the problem isn't with it, the problem is with Openbsd. Or something. Could someone please explain me why this happened? You are the only person at this time with enough information to explain it, but you need to be able to tell us more than you are teling us. Can you think about a way to fix this without send it to warranty? I'm guessing you need to read through FAQ 14.7, on booting, that I mentioned above: http://www.openbsd.org/faq/faq14.html#Boot386 and then back to FAQ 4.9, again: http://www.openbsd.org/faq/faq4.html#Multibooting Any other questions? Did you do anything to tell your BIOS where to find your openbsd install? How did you partition the disks? How many partitions do you have? Are you trying to multiboot with a Linux OS or MSWindows? What kind of motherboard is it? Is the CPU 32 bit or 64 bit? send me a reply, I'm really in need of help :-/ -- Joel Rees Be careful when you look at conspiracy. Look first in your own heart, and ask yourself if you are not your own worst enemy. Arm yourself with knowledge of yourself, as well.
Re: Openbsd broke my hard drive twice! Getting frustrated
On 2014-12-23 03:01, Joel Rees wrote: By the way, how are you accessing the internet now? My mother's notebook via wireless connection. Or perhaps you forgot to write down the URL for a nearby mirror before you started, so you could tell the installer to get the stuff from a mirror. For example, http://ftp.jaist.ac.jp/pub/OpenBSD/ How this would help me if I had no internet connection? When I tried to turn on again, the system didn't boot. That's not too surprising. Although, I wonder, did you notice how far it got in the boot process before it stopped? This is the point had confusion. It stopped on the bios screen. It even began to load the disc, because it didn't recognize it. It didn't booted because my hard drive isn't more recognized. Not because the system isn't correct installed. If the only problem was the system installation I would be able to at least enter the BIOS. I discovered that it only worked if I remove the hard drive. I suppose you mean that it would boot the install CD? There could be boot device order issues. As I said before, my computer does nothing with the hard drive attached, Thinking that the problem was the harddrive I sent it to warranty to be repleaced. Definitely a drastic step. Definitely not a drastic step, since my test showed that it was the problem and it really was because it worked the first time I tried when it arrived new from warranty. I took 10 long days (withou my computer) to arrive a new one. When it arrived, I tested and I saw that now it is working. I prepared a cable connection, and I started again the openbsd setup. It sucefully downloaded and installed everything, so I rebooted the system to boot my new fresh install. I see from your later posts that you have installed Linux before. You should understand there is a difference between Linux and openbsd. Openbsd does not install a bootloader for you. Does a bad OpenBSD install would change how my BIOS detect my HDD, and make all the rest hardware stop working when it is plugged, exactly as it happen when you put a drive in short circuit? AND SHIT, everything happened as before, the system don't boot as before, I can't open the bios as before, How did you open the BIOS when you were able to open the BIOS? Pressing DEL or F2 on boot. Regards, -- Henrique Lengler
Re: Openbsd broke my hard drive twice! Getting frustrated
On 2014-12-23 02:55, Eric Furman wrote: No. This is done by the BIOS. After the computer boots the BIOS then hands over control to the OS. So this it the time the OS is able to do whatfuck it wants with my HDD, and so the OS have control over HDD. Right? And yes, that is a gross over simplification of what actually happens. There is no way that any OS can 'break' a hard drive. So why this happened when using OpenBSD? -- Henrique Lengler
Re: Openbsd broke my hard drive twice! Getting frustrated
On Mon, Dec 22, 2014 at 11:22 PM, Henrique Lengler henriquel...@openmailbox.org wrote: On 2014-12-23 02:55, Eric Furman wrote: No. This is done by the BIOS. After the computer boots the BIOS then hands over control to the OS. So this it the time the OS is able to do whatfuck it wants with my HDD, and so the OS have control over HDD. Right? And yes, that is a gross over simplification of what actually happens. There is no way that any OS can 'break' a hard drive. So why this happened when using OpenBSD? -- Henrique Lengler I forgot to CC the list in the reply, sorry for the duplication: Sometimes vendors do not do extensive testing, and do things like hardcode strings in the firmware to expect Windows or Linux. Here is an article discussing a problem with a Lenovo Thinkcentre that only worked with Windows, Redhat or Fedora: http://mjg59.dreamwidth.org/20187.html There have been a couple of reports similar to this one that were fixed with a firmware update from the motherboard or system vendor. I would presume the firmware basically crashes if it sees a boot code written on the hard drive it does not expect, even if it follows the standards: http://marc.info/?t=13988430601r=1w=2 http://marc.info/?l=openbsd-miscw=2r=1s=Axiomtek+NA570q=b I worked on a new-ish laptop recently that would not boot from a CD or any non-Windows partition unless I first removed the hard drive, entered the EFI/Bios setup, set a password, then disabled EFI secure boot.
Re: Openbsd broke my hard drive twice! Getting frustrated
On Tue, Dec 23, 2014 at 03:22:51AM -0200, Henrique Lengler wrote: On 2014-12-23 02:55, Eric Furman wrote: No. This is done by the BIOS. After the computer boots the BIOS then hands over control to the OS. So this it the time the OS is able to do whatfuck it wants with my HDD, and so the OS have control over HDD. Right? And yes, that is a gross over simplification of what actually happens. There is no way that any OS can 'break' a hard drive. So why this happened when using OpenBSD? -- Henrique Lengler OpenBSD does not support UEFI secure boot. I'm not a developer, so I won't offer an answer as to why support is lacking, but I suspect it has something to do with UEFI being a metric fuckton of bullshit. That said, I'm willing to bet if you disable secure boot, it'll act differently than what it is now. And, depending on what distro of Linux you installed, it may support UEFI (and hence the BIOS boot of Linux may not have been with UEFI disabled).
Re: Openbsd broke my hard drive twice! Getting frustrated
On Tue, Dec 23, 2014 at 2:19 PM, Henrique Lengler henriquel...@openmailbox.org wrote: On 2014-12-23 03:01, Joel Rees wrote: By the way, how are you accessing the internet now? My mother's notebook via wireless connection. Would she mind too much if you took the time to read through the FAQs I suggested? Or perhaps you forgot to write down the URL for a nearby mirror before you started, so you could tell the installer to get the stuff from a mirror. For example, http://ftp.jaist.ac.jp/pub/OpenBSD/ How this would help me if I had no internet connection? Do you plan on accessing the internet once the OS is running? How is that gong to work? But that's not a question for now, I guess. When I tried to turn on again, the system didn't boot. That's not too surprising. Although, I wonder, did you notice how far it got in the boot process before it stopped? This is the point had confusion. It stopped on the bios screen. So, it was booting to the BIOS. It even began to load the disc, because it didn't recognize it. Yeah. You have to tell the BIOS where to look or it doesn't know where to look. If it doesn't know where to look, how can it see enough to recognize anything? It didn't booted because my hard drive isn't more recognized. Not because the system isn't correct installed. This much, you could well be right about. If the only problem was the system installation I would be able to at least enter the BIOS. Why do you want to go back to the BIOS without re-booting? I discovered that it only worked if I remove the hard drive. I suppose you mean that it would boot the install CD? There could be boot device order issues. Or partition/master boot record, or, as others have mentioned, UEFI issues, although I'm guessing you got UEFI worked out (switched to legacy) when you installed a Linux OS a year ago. Something you might try, re-install the Linux OS, but make sure you leave about half the HD for openbsd. Then tell the Linux OS installer you will be multibooting, if it asks. But I think you want to re-read those FAQs first. And while it it installing, read those FAQs I gave you the links to: http://www.openbsd.org/faq/faq14.html#Boot386 http://www.openbsd.org/faq/faq4.html#Multibooting Even if they are hard to understand, reading them again woud be a good idea. As I said before, my computer does nothing with the hard drive attached, Except that it is showing you that is is attempting to boot. It couldn't even attempt to boot if it weren't getting to the BIOS, because it is the BIOS that is going looking for the OS telling you it can't find it. Thinking that the problem was the harddrive I sent it to warranty to be repleaced. Definitely a drastic step. Definitely not a drastic step, Okay, we'll pretend I didn't say it was a drastic step. since my test showed that it was the problem and it really was because it worked the first time I tried when it arrived new from warranty. We can talk about that later. I took 10 long days (withou my computer) to arrive a new one. When it arrived, I tested and I saw that now it is working. I prepared a cable connection, and I started again the openbsd setup. It sucefully downloaded and installed everything, so I rebooted the system to boot my new fresh install. I see from your later posts that you have installed Linux before. You should understand there is a difference between Linux and openbsd. Openbsd does not install a bootloader for you. Does a bad OpenBSD install would change how my BIOS detect my HDD, and make all the rest hardware stop working when it is plugged, exactly as it happen when you put a drive in short circuit? Yeah. Let's talk about that later, too. Except, I'm wondering whether I might be able to set the active partition on the disk and it would then boot for you. If I were there. The problem, I am sure, is not that the install is messed up. I'm pretty sure you just (1) don't have a boot loader, (2) haven't written the master boot record, and/or (3) haven't set the active parttion. AND SHIT, everything happened as before, the system don't boot as before, I can't open the bios as before, How did you open the BIOS when you were able to open the BIOS? Pressing DEL or F2 on boot. Most BIOSses won't let you do that once they decide they can't find an OS to boot. It's normal. -- Joel Rees Be careful when you look at conspiracy. Look first in your own heart, and ask yourself if you are not your own worst enemy. Arm yourself with knowledge of yourself, as well.
Re: Openbsd broke my hard drive twice! Getting frustrated
On Tue, 23 Dec 2014 03:22:51 -0200 Henrique Lengler henriquel...@openmailbox.org wrote: On 2014-12-23 02:55, Eric Furman wrote: No. This is done by the BIOS. After the computer boots the BIOS then hands over control to the OS. So this it the time the OS is able to do whatfuck it wants with my HDD, and so the OS have control over HDD. Right? And yes, that is a gross over simplification of what actually happens. There is no way that any OS can 'break' a hard drive. So why this happened when using OpenBSD? There are so many variables here that the *only* way to find the root cause is the process of eliminations. Guessing that OpenBSD did it will only get you more mad. If this were *my* computer I'd grab a couple blank CDs, go somewhere where you can download, and download and burn System Rescue CD. You can boot that and examine your computer, including the disk. Start ruling out sections of the root cause scope, and pretty soon you'll know the exact root cause. By the way, I think System Rescue CD has SMART programs, so you can see whether your hard disk is damaged, or just has lost its file system or GPT or MBR. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance
Re: free ipv6 KVM-based - cloudspin.me [was - Re: DigitalOcean's BSD debut is FreeBSD only]
I am trying to produce images of all the popular distros, but time is always short and I am a one man show. Having a DNS server that people can create their own resolvable hostnames is more pressing. I have iso's uploaded so people can roll their own. You are also free to create your own image an publish it to the community. I don't limit capabilities, only resources because they are finite. Donny Davis cloudspin.me -Original Message- From: Florian Obser [mailto:flor...@openbsd.org] Sent: Monday, December 22, 2014 8:43 AM To: Jiri B Cc: Some Developer; misc@openbsd.org Subject: Re: free ipv6 KVM-based - cloudspin.me [was - Re: DigitalOcean's BSD debut is FreeBSD only] On Sun, Dec 21, 2014 at 06:08:04PM -0500, Jiri B wrote: On Sun, Dec 21, 2014 at 01:54:50AM +, Some Developer wrote: Vultr already support OpenBSD on their servers (you upload the OpenBSD install ISO and install it yourself) and their servers cost the same as Digital Ocean. Performance is good. They support IPv6 and they have more locations than Digital Ocean. Overall very pleased with them. My coll told me about cloudspin.me, it's oVirt/KVM based service, free of charge, public IPv6 only. oVirt is upstream OSS project for Red Hat Enterprise Virtualization. cloudspin.me does not offer OpenBSD image, what a suprise, but I suppose everybody is able to `dd' minirootXX.fs onto virtio disk :) It now offers an OpenBSD iso, runs just fine... Looks like some random dude finally implemented xkcd 908 j. -- I'm not entirely sure you are real.
Re: Openbsd broke my hard drive twice! Getting frustrated
On 2014-12-23 05:22, Henrique Lengler wrote: On 2014-12-23 02:55, Eric Furman wrote: No. This is done by the BIOS. After the computer boots the BIOS then hands over control to the OS. So this it the time the OS is able to do whatfuck it wants with my HDD, and so the OS have control over HDD. Right? And yes, that is a gross over simplification of what actually happens. There is no way that any OS can 'break' a hard drive. So why this happened when using OpenBSD? I stand to be corrected but I do not think that OpenBSD can support UEFI nor GPT partitions, not yet anyhow.
