Re: installboot: broken mbr on 4.4
Michael wrote: On Sun, Nov 02, 2008 at 07:06:04AM -0700, Michael wrote: On Sun, Nov 02, 2008 at 07:39:20AM -0500, Josh Grosse wrote: On Sun, Nov 02, 2008 at 04:28:54AM -0700, Michael wrote: On Sun, Nov 02, 2008 at 07:40:12AM +0530, Girish Venkatachalam wrote: ... cd /mnt # /usr/mdec/installboot -v boot /mnt/biosboot wd0 It should not be /usr/mdec/biosboot. Definitely not. ... Thanks for your answer. If 4.4 doesn't install completely (without the installboot error) on a 120 gig hd, I'll try the command the way you posted it and see if it works vs what Josh sent me. The biosboot file (found in /usr/mdec/biosboot of either the ramdisk kernel or a default install) is the PBR which is placed in the first sector of the partition. The boot file (found in /usr/mdec/biosboot of either the ramdisk kernel or a default install, or in /boot in a default install) is the second stage bootloader program. As far as I know, there is no "/biosboot" file in a standard install, so the "/mnt/biosboot" will not work. Thanks again Josh :) Well, I tried installing 4.4 on my Acer Aspire 3000 with 60 gig hd and got the same problem with installboot. Again, I used the above commands that Josh sent me with my 4.3 cd and the installboot ran fine and now I'm using 4.4 on the Acer. Info on this hd: 117210240 sectors OpenBSD starts at 32788665 with a size of 25270245 "a" partition starts at 32788665 with a size of 102400 sectors. Mike Did you generate and use a new PBR file as discussed in section 4.8 of the FAQ? Once I did, Vista's boot loader works. Regards, Regards
Re: No sound with ATI SBx00 HD Audio
On 07/27/11 16:42, Christiano F. Haesbaert wrote: I found out the datasheet for 0x4383 http://developer.amd.com/assets/43009_sb7xx_rrg_pub_1.00.pdf I've no knowledge of PCI to debug it though. Try something like this in rc.local and see if it works. # Setting "Mother Board Audio Device" as Default Audio Device echo '.' echo -n ' Setting /dev/{audio,sound,audioctl,mixer} to Azalia0' p=1 ln -sf /dev/audio$p /dev/audio ln -sf /dev/sound$p /dev/sound ln -sf /dev/audioctl$p /dev/audioctl ln -sf /dev/mixer$p /dev/mixer echo '.'
Re: Radeon HD 4850 and drmRadeonCmdBuffer: -22.
On 02/28/11 15:16, Tobias Ulmer wrote: On Mon, Feb 28, 2011 at 07:38:27PM +0100, Pascal Stumpf wrote: On Thu, Feb 24, 2011 at 10:03:06AM -0500, Joe Snikeris wrote: On Thu, Feb 24, 2011 at 3:09 AM, Andy Bradford wrote: Is it going to be possible to get acceleration working with this? If so, any pointers? +1 For the record: I've also tried the radeonhd driver instead of radeon. 'glxinfo' reports a lot more GLX Visuals and GLXFBConfigs, OpenGL version 2.1 instead of 1.5, but glxgears does not seem any faster (around 290 FPS). Other applications using GL (supertuxkart ...) still crash when trying to use hardware acceleration. For my part, I'd greatly appreciate *any* feedback from graphics people on this. Is it being worked on? Which component is the culprit (kernel, xorg driver, Mesa)? There is no DRM support for r600 and up in the kernel. Someone first has to finish his PhD first I believe... With the current kernel support you get _some_ benefits like xvideo, but that's about it for the moment. My 3850 (r600) has DRM support on Current: vga1 at pci1 dev 0 function 0 "ATI Radeon HD 3850" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 2 int 16 (irq 10) drm0 at radeondrm0
USB Keyboard - no bell
After getting an USB keyboard, I noticed no beep when hitting the escape key in Vi. Plugged in the PS/2 keyboard and I get the beep back! After doing some googling, it appears that USB keyboards may not support ascii 0x07 (bel). Is this covered in the Man pages or is there any way to work around this? Regards, Greg
Re: USB Keyboard - no bell
Miod, Applied the diff and recompiled current. It works perfectly!! Thank you, Greg Miod Vallat wrote: After getting an USB keyboard, I noticed no beep when hitting the escape key in Vi. Plugged in the PS/2 keyboard and I get the beep back! After doing some googling, it appears that USB keyboards may not support ascii 0x07 (bel). Most keyboards those days do not have built-in beeper devices, especially in the PC world; however in the OpenBSD kernels, the console beep is still routed through the keyboard driver, for the old platforms where the only noise-capable device is the beeper in the keyboard itself. When your console keyboard is an USB keyboard, the software glue to have the beep request sent to the PC speaker is currently missing, so there is currently no way to work around this situation. The following diff should fix that. Miod Index: dev/isa/pcppi.c === RCS file: /cvs/src/sys/dev/isa/pcppi.c,v retrieving revision 1.7 diff -N -u -p dev/isa/pcppi.c --- dev/isa/pcppi.c 12 Feb 2006 20:04:16 - 1.7 +++ dev/isa/pcppi.c 29 Sep 2009 04:35:50 - @@ -45,11 +45,12 @@ #include #include "pckbd.h" -#if NPCKBD > 0 +#include "ukbd.h" +#if NPCKBD > 0 || NUKBD > 0 #include #include - -void pcppi_pckbd_bell(void *, u_int, u_int, u_int, int); +#include +void pcppi_kbd_bell(void *, u_int, u_int, u_int, int); #endif struct pcppi_softc { @@ -169,10 +170,13 @@ pcppi_attach(parent, self, aux) sc->sc_bellactive = sc->sc_bellpitch = sc->sc_slp = 0; + /* Provide a beeper for the keyboard, if there isn't one already. */ #if NPCKBD > 0 - /* Provide a beeper for the PC Keyboard, if there isn't one already. */ - pckbd_hookup_bell(pcppi_pckbd_bell, sc); + pckbd_hookup_bell(pcppi_kbd_bell, sc); #endif +#if NUKBD > 0 + ukbd_hookup_bell(pcppi_kbd_bell, sc); +#endif pa.pa_cookie = sc; while (config_found(self, &pa, 0)); @@ -255,9 +259,9 @@ pcppi_bell_stop(arg) splx(s); } -#if NPCKBD > 0 +#if NPCKBD > 0 || NUKBD > 0 void -pcppi_pckbd_bell(arg, pitch, period, volume, poll) +pcppi_kbd_bell(arg, pitch, period, volume, poll) void *arg; u_int pitch, period, volume; int poll; @@ -268,4 +272,4 @@ pcppi_pckbd_bell(arg, pitch, period, volume, poll) pcppi_bell(arg, volume ? pitch : 0, (period * hz) / 1000, poll ? PCPPI_BELL_POLL : 0); } -#endif /* NPCKBD > 0 */ +#endif /* NPCKBD > 0 || NUKBD > 0 */
Re: How to open PDF that requires Adobe 9
You may want to look at Pdftk at http://www.pdflabs.com/. You may be able to use Pdftk to massage the pdf file you can open it. I don't know if it will build on OpenBSD (although there is a FreeBSD port.) Regards, On 12/07/10 03:47, Sebastian Reitenbach wrote: On Tuesday 07 December 2010 08:40:01 am Clint Pachl wrote: Anthony Bentley wrote: This happens when there are multiple PDFs embedded in a single PDF file. I remember reading a Ghostscript bug about this (could probably find it again if I had the exact error message), but unfortunately Mupdf still doesn't support it. Here is the Ghostscript bug: http://bugs.ghostscript.com/show_bug.cgi?id=690422 From here it looks like you might be able to get it with gs after all. Good research Anthony. That bug describes my situation exactly. The only thing is that I didn't know what the hell a portfolio PDF was until now. Unfortunately, the gs ports is version 8.63 (released 2008-08-01). This bug report/fix happened in April 2009. Shit, now Mr. Schroder is going to be on my ass about patches again. :-P kili@ posted a ghostscript update to ports@ in October IIRC, you may consult the archives. cheers, Sebastian