Re: ATI Radeon HD6570
Le 24/11/2012 02:21, Nigel Taylor a écrit : > Your audio is being picked up already as 6670, audio was added together > with the video for a 6670 card. There maybe a range of cards that use > the same id for audio. > > To recreate the includes. > cd /usr/src/sys/dev/pci > make > > Now follow instructions for building a kernel, and Installing kernel > Reboot and check dmesg. > Hum... ok it's detected now, i didn't know that i had to "make" in /pci: vga1 at pci1 dev 0 function 0 "ATI Radeon HD 6570" rev 0x00 (maybe commit that ? --- pcidevs 2012-11-17 16:42:29.0 +0100 +++ pcidevs 2012-11-23 12:58:50.357249029 +0100 @@ -1262,6 +1262,7 @@ product ATI RADEON_X700_SE 0x5e4f Radeon X700 SE product ATI RADEON_X700_SE_S 0x5e6f Radeon X700 SE Sec product ATI RADEON_HD6670 0x6758 Radeon HD 6670 +product ATI RADEON_HD6570 0x6759 Radeon HD 6570 product ATI RADEON_HD5800 0x6899 Radeon HD 5800 product ATI RADEON_HD5700 0x68b8 Radeon HD 5700 product ATI RADEON_HD5670 0x68d8 Radeon HD 5670 ) > This will not fix your driver problems, for that there needs to be KMS > support, or try and hope one of the other chip families works. Yes I still have the same issue. So, finally, I can't use my GPU correctly ? Thanks
Re: ATI Radeon HD6570
On 11/23/12 21:26, rustyBSD wrote: > Le 23/11/2012 21:44, Nigel Taylor a écrit : >> On 11/23/12 16:56, rustyBSD wrote: >>> Le 23/11/2012 17:35, Nigel Taylor a écrit : That is not a REDWOOD chip, it's TURKS, and both should be supported, >>> >>> Ahh yes I didn't see this in xorg.0.log >>> the man page is wrong 6570 occurs both under REDWOOD and TURKS. REDWOOD are 5x50 series. Could still be in the wrong chip family. The Xorg.0.log should tell you if the card is detected, it can be rejected for some other reason, then fall back to next driver. Do you get a message in Xorg.0.log like, >>> >>> Yes, I have: >>> >>> [94.501] (II) VESA: driver for VESA chipsets: vesa >>> [94.502] (II) GPU only supported with KMS, using vesa instead. >>> [94.502] (II) Loading sub module "vbe" >>> GPU only supported with KMS, using vesa instead. >>> >>> I don't know if I'm wrong, but if I add >>>product ATI RADEON_HD65700x6759 Radeon HD 6570 >>> it should at least appear in dmesg, no ? >>> >>> >> Should appear in the dmesg, providing the include files have been >> updated, then you rebuilt the kernel and install it. By running make the >> pcidevs change should cause pcidevs.h pcidevs_data.h to be updated. >> >> You may need two product ID's, there may be audio also, as below the >> graphics is 0x6758 and audio is 0xaa90. >> >> pcidevs:product ATI RADEON_HD6670 0x6758 Radeon HD 6670 >> pcidevs:product ATI RADEON_HD6670_HDA 0xaa90 Radeon HD 6670 Audio >> >> pcidevs.h:#define PCI_PRODUCT_ATI_RADEON_HD6670 0x6758 >> /* Radeon HD 6670 */ >> pcidevs.h:#define PCI_PRODUCT_ATI_RADEON_HD6670_HDA 0xaa90 >> /* Radeon HD 6670 Audio */ >> >> pcidevs_data.h: PCI_VENDOR_ATI, PCI_PRODUCT_ATI_RADEON_HD6670, >> pcidevs_data.h: "Radeon HD 6670", >> pcidevs_data.h: PCI_VENDOR_ATI, PCI_PRODUCT_ATI_RADEON_HD6670_HDA, >> pcidevs_data.h: "Radeon HD 6670 Audio", >> >> >> >> >> There is a test in radeon_probe that the chip family SUMO and those >> after will only be supported with KMS, that includes the TURKS family of >> chips. >> >> The confusion between REDWOOD and TURKS is 6570 is TURKS, the mobility >> version of 6570 is REDWOOD and should be 6570M. >> >> >> >> >> > > So, what do I do ? > Here is the full dmesg, I should have post it before > > > OpenBSD 5.2-current (GENERIC.MP) #2: Fri Nov 23 22:13:59 CET 2012 > root@JackBSD:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 2144862208 (2045MB) > avail mem = 2065338368 (1969MB) > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.5 @ 0x9f000 (58 entries) > bios0: vendor American Megatrends Inc. version "2202" date 08/19/2010 > bios0: ASUSTeK Computer INC. M4A77T > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S1 S3 S4 S5 > acpi0: tables DSDT FACP APIC MCFG OEMB SRAT HPET SSDT > acpi0: wakeup devices PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PCE7(S4) > PCE9(S4) PCEA(S4) RLAN(S4) PCEB(S4) PCEC(S4) SBAZ(S4) PS2M(S4) PS2K(S4) > UAR1(S4) P0PC(S4) UHC1(S4) UHC2(S4) UHC3(S4) USB4(S4) UHC5(S4) UHC6(S4) > UHC7(S4) > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD Athlon(tm) II X3 455 Processor, 3315.29 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,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC > cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > 64b/line 16-way L2 cache > cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative > cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative > cpu0: AMD erratum 721 detected and fixed > cpu0: apic clock running at 200MHz > cpu1 at mainbus0: apid 1 (application processor) > cpu1: AMD Athlon(tm) II X3 455 Processor, 3314.90 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,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC > cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > 64b/line 16-way L2 cache > cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative > cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative > cpu1: AMD erratum 721 detected and fixed > cpu2 at mainbus0: apid 2 (application processor) > cpu2: AMD Athlon(tm) II X3 455 Processor, 3314.90 MHz > cpu2: > 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,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC > cpu2: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > 64b/line 16-way L2 cache > cpu2: ITLB 3
Can't use PerlMagick
Hello! I'm running into a weird problem with PerlMagick: $ perl -e 'use Image::Magick' Can't load '/usr/local/libdata/perl5/site_perl/amd64-openbsd/auto/Image/Magick/Magick.so' for module Image::Magick: Cannot load specified object at /usr/libdata/perl5/amd64-openbsd/5.12.2/DynaLoader.pm line 200. at -e line 1 Compilation failed in require at -e line 1. BEGIN failed--compilation aborted at -e line 1. &Image::Magick::constant not defined. The required ImageMagick libraries are not installed or not installed properly. END failed--call queue aborted at -e line 1. Am I missing something obvious? Is there anything I can do about it? OpenBSD -current amd64 (latest snapshot), PerlMagick from ImageMagick-6.7.7.7p2 package. Thanks in advance. -- Dmitrij D. Czarkoff
Re: ATI Radeon HD6570
Le 23/11/2012 21:44, Nigel Taylor a écrit : > On 11/23/12 16:56, rustyBSD wrote: >> Le 23/11/2012 17:35, Nigel Taylor a écrit : >>> That is not a REDWOOD chip, it's TURKS, and both should be supported, >> >> Ahh yes I didn't see this in xorg.0.log >> >>> the man page is wrong 6570 occurs both under REDWOOD and TURKS. >>> REDWOOD are 5x50 series. Could still be in the wrong chip family. >>> >>> The Xorg.0.log should tell you if the card is detected, it can be >>> rejected for some other reason, then fall back to next driver. >>> >>> Do you get a message in Xorg.0.log like, >> >> Yes, I have: >> >> [94.501] (II) VESA: driver for VESA chipsets: vesa >> [94.502] (II) GPU only supported with KMS, using vesa instead. >> [94.502] (II) Loading sub module "vbe" >> >>> GPU only supported with KMS, using vesa instead. >> >> I don't know if I'm wrong, but if I add >>product ATI RADEON_HD6570 0x6759 Radeon HD 6570 >> it should at least appear in dmesg, no ? >> >> > Should appear in the dmesg, providing the include files have been > updated, then you rebuilt the kernel and install it. By running make the > pcidevs change should cause pcidevs.h pcidevs_data.h to be updated. > > You may need two product ID's, there may be audio also, as below the > graphics is 0x6758 and audio is 0xaa90. > > pcidevs:product ATI RADEON_HD6670 0x6758 Radeon HD 6670 > pcidevs:product ATI RADEON_HD6670_HDA 0xaa90 Radeon HD 6670 Audio > > pcidevs.h:#define PCI_PRODUCT_ATI_RADEON_HD6670 0x6758 > /* Radeon HD 6670 */ > pcidevs.h:#define PCI_PRODUCT_ATI_RADEON_HD6670_HDA 0xaa90 > /* Radeon HD 6670 Audio */ > > pcidevs_data.h: PCI_VENDOR_ATI, PCI_PRODUCT_ATI_RADEON_HD6670, > pcidevs_data.h: "Radeon HD 6670", > pcidevs_data.h: PCI_VENDOR_ATI, PCI_PRODUCT_ATI_RADEON_HD6670_HDA, > pcidevs_data.h: "Radeon HD 6670 Audio", > > > > > There is a test in radeon_probe that the chip family SUMO and those > after will only be supported with KMS, that includes the TURKS family of > chips. > > The confusion between REDWOOD and TURKS is 6570 is TURKS, the mobility > version of 6570 is REDWOOD and should be 6570M. > > > > > So, what do I do ? Here is the full dmesg, I should have post it before OpenBSD 5.2-current (GENERIC.MP) #2: Fri Nov 23 22:13:59 CET 2012 root@JackBSD:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2144862208 (2045MB) avail mem = 2065338368 (1969MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0x9f000 (58 entries) bios0: vendor American Megatrends Inc. version "2202" date 08/19/2010 bios0: ASUSTeK Computer INC. M4A77T acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB SRAT HPET SSDT acpi0: wakeup devices PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PCE7(S4) PCE9(S4) PCEA(S4) RLAN(S4) PCEB(S4) PCEC(S4) SBAZ(S4) PS2M(S4) PS2K(S4) UAR1(S4) P0PC(S4) UHC1(S4) UHC2(S4) UHC3(S4) USB4(S4) UHC5(S4) UHC6(S4) UHC7(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) II X3 455 Processor, 3315.29 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,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu0: AMD erratum 721 detected and fixed cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) II X3 455 Processor, 3314.90 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,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu1: AMD erratum 721 detected and fixed cpu2 at mainbus0: apid 2 (application processor) cpu2: AMD Athlon(tm) II X3 455 Processor, 3314.90 MHz cpu2: 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,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC cpu2: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu2: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu2: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu2: AMD erratum 721 detected and fixed ioa
Re: ATI Radeon HD6570
On 11/23/12 16:56, rustyBSD wrote: > Le 23/11/2012 17:35, Nigel Taylor a écrit : >> That is not a REDWOOD chip, it's TURKS, and both should be supported, > > Ahh yes I didn't see this in xorg.0.log > >> the man page is wrong 6570 occurs both under REDWOOD and TURKS. >> REDWOOD are 5x50 series. Could still be in the wrong chip family. >> >> The Xorg.0.log should tell you if the card is detected, it can be >> rejected for some other reason, then fall back to next driver. >> >> Do you get a message in Xorg.0.log like, > > Yes, I have: > > [94.501] (II) VESA: driver for VESA chipsets: vesa > [94.502] (II) GPU only supported with KMS, using vesa instead. > [94.502] (II) Loading sub module "vbe" > >> GPU only supported with KMS, using vesa instead. > > I don't know if I'm wrong, but if I add >product ATI RADEON_HD6570 0x6759 Radeon HD 6570 > it should at least appear in dmesg, no ? > > Should appear in the dmesg, providing the include files have been updated, then you rebuilt the kernel and install it. By running make the pcidevs change should cause pcidevs.h pcidevs_data.h to be updated. You may need two product ID's, there may be audio also, as below the graphics is 0x6758 and audio is 0xaa90. pcidevs:product ATI RADEON_HD6670 0x6758 Radeon HD 6670 pcidevs:product ATI RADEON_HD6670_HDA 0xaa90 Radeon HD 6670 Audio pcidevs.h:#define PCI_PRODUCT_ATI_RADEON_HD6670 0x6758 /* Radeon HD 6670 */ pcidevs.h:#define PCI_PRODUCT_ATI_RADEON_HD6670_HDA 0xaa90 /* Radeon HD 6670 Audio */ pcidevs_data.h: PCI_VENDOR_ATI, PCI_PRODUCT_ATI_RADEON_HD6670, pcidevs_data.h: "Radeon HD 6670", pcidevs_data.h: PCI_VENDOR_ATI, PCI_PRODUCT_ATI_RADEON_HD6670_HDA, pcidevs_data.h: "Radeon HD 6670 Audio", There is a test in radeon_probe that the chip family SUMO and those after will only be supported with KMS, that includes the TURKS family of chips. The confusion between REDWOOD and TURKS is 6570 is TURKS, the mobility version of 6570 is REDWOOD and should be 6570M.
Re: ATI Radeon HD6570
Le 23/11/2012 17:35, Nigel Taylor a écrit : > That is not a REDWOOD chip, it's TURKS, and both should be supported, Ahh yes I didn't see this in xorg.0.log > the man page is wrong 6570 occurs both under REDWOOD and TURKS. > REDWOOD are 5x50 series. Could still be in the wrong chip family. > > The Xorg.0.log should tell you if the card is detected, it can be > rejected for some other reason, then fall back to next driver. > > Do you get a message in Xorg.0.log like, Yes, I have: [94.501] (II) VESA: driver for VESA chipsets: vesa [94.502] (II) GPU only supported with KMS, using vesa instead. [94.502] (II) Loading sub module "vbe" > GPU only supported with KMS, using vesa instead. I don't know if I'm wrong, but if I add product ATI RADEON_HD65700x6759 Radeon HD 6570 it should at least appear in dmesg, no ?
Support for BCM5720
Hi all, i have bought 2 new dell R320 serveurs to replace my old dell 1650 servers (7 years old). The problem is network card (unfortunately the machines will be routers/gateways). I tried to backport FreeBSD 9.1 RC3 driver, which works, but not totally succesful (card recognized, link negotiation ok, but no network trafic). Moreover, only the port 1 is partially functionnal. When i make ifconfig bge1 up, a kernel panic occurs. (no problem for dual port cards with intel pro 1000 PT) Dell choose to use BCM5720 for all its new servers (R530, R320), with dual ports. New Dell servers cannot be used if we don't buy/change the cards. Broadcom politics is very bad, i know. My question is, will you backport FreeBSD working driver to OpenBSD for a next OpenBSD release (5.3 or 5.4) ? Can i make a trunk with bge0 and em0 or must i do a trunk with bge0 and bge1 ? What's the impact ? Thanks for advance -- Cordialement, Loïc BLOT, Expert en Systèmes UNIX, Sécurité et Réseau
Re: ATI Radeon HD6570
On 11/23/12 14:00, rustyBSD wrote: > Hi, > I have an ATI Radeon HD6570 card. Dmesg gives me: > vga1 at pci1 dev 0 function 0 vendor "ATI", unknown product 0x6759 rev 0x00 > and the driver used seems to be VESA. > > I naturally changed to: > > --- src/sys/dev/pci/pcidevs 2012-11-17 16:42:29.0 +0100 > +++ src/sys/dev/pci/pcidevs 2012-11-23 12:58:50.357249029 +0100 > @@ -1262,6 +1262,7 @@ > product ATI RADEON_X700_SE 0x5e4f Radeon X700 SE > product ATI RADEON_X700_SE_S 0x5e6f Radeon X700 SE Sec > product ATI RADEON_HD66700x6758 Radeon HD 6670 > +product ATI RADEON_HD65700x6759 Radeon HD 6570 > product ATI RADEON_HD58000x6899 Radeon HD 5800 > product ATI RADEON_HD57000x68b8 Radeon HD 5700 > product ATI RADEON_HD56700x68d8 Radeon HD 5670 > > > But it's still not recognized. I looked at pci/drm/radeon_drv.c, > but I'm not sure I can add my card, as - according to man radeon - > it's a REDWOOD chip, which doesn't seem to be supported on openbsd. > > My questions are: > Are REDWOOD chips supported ? > If yes, how can I get my card work correctly ? > If no, is there any support planned ? > > Thanks > > That is not a REDWOOD chip, it's TURKS, and both should be supported, the man page is wrong 6570 occurs both under REDWOOD and TURKS. REDWOOD are 5x50 series. Could still be in the wrong chip family. The Xorg.0.log should tell you if the card is detected, it can be rejected for some other reason, then fall back to next driver. Do you get a message in Xorg.0.log like, GPU only supported with KMS, using vesa instead.
Re: OpenBSD support for Lenovo ThinkPad X230?
On 23 Nov 2012, at 03:13, Byron Klippert wrote: > I picked up one recently; went with the following options. > > - Intel Core i5-3360M > - 128GB SSD (SATA3) > - 8GB PC3-12800 DDR3 > - Intel Centrino WL-N 2200 > > > > Had to use the Nov. 3 snapshot to take advantage of the recent ivy > bridge graphic changes (affecting Intel HD Graphics 4000). > > http://marc.info/?l=openbsd-tech&m=134909742604779&w=2 > > X is usable, although I've had issues switching between console > (Ctl-Alt-F1) and back to X. Also had issues when display goes to sleep. > ie: display resumes with strange effects on display (vertical lines - > like bad resolution or refresh rate). This can sometimes be remedied by > switch between console and back to X several times. I see the same issues with the X1 Carbon (along with the occasional hard freeze when switching X displays, but more often you get a white noise overlay). Not had a chance to track it down yet. -anil > > > I recall having issues with USB3 or something, before trying current > snapshot. Might have to play with BIOS settings. I also disabled the > touchpad, it was causing strange errors whenever finger came in contact > with surface. > > > Suspend/resume works. > > > The Intel Centrino WL-N 2200 does not work. > > > Haven't tried ethernet (em0). > > > Keyboard is nice. > > > Display doesn't dim using Fn keys (acpithinkpad0: unknown event 0x6050). > > > Mute changes output_muted. Volume +/- changes play.gain. Mic mute don't > know. > > > > Currently dual-booting with stock Win7 OS. Wiped hibernate partition and > installed 5.2 within (see fdisk output). Disabled hibernation within > Win7. > > > > OpenBSD 5.2-current (GENERIC.MP) #96: Sat Nov 3 14:43:34 MDT 2012 >dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8270311424 (7887MB) > avail mem = 8027672576 (7655MB) > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9d000 (70 entries) > bios0: vendor LENOVO version "G2ET82WW (2.02 )" date 09/11/2012 > bios0: LENOVO 2306CTO > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT > FPDT ASF! UEFI UEFI POAT SSDT SSDT UEFI DBG2 > acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP3(S4) XHCI(S3) > EHC1(S3) EHC2(S3) HDEF(S4) > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpihpet0 at acpi0: 14318179 Hz > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i5-3360M CPU @ 2.80GHz, 2794.19 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,FSGSBASE,SMEP,ERMS > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: apic clock running at 99MHz > cpu1 at mainbus0: apid 1 (application processor) > cpu1: Intel(R) Core(TM) i5-3360M CPU @ 2.80GHz, 2793.66 MHz > cpu1: > 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,FSGSBASE,SMEP,ERMS > cpu1: 256KB 64b/line 8-way L2 cache > cpu2 at mainbus0: apid 2 (application processor) > cpu2: Intel(R) Core(TM) i5-3360M CPU @ 2.80GHz, 2793.66 MHz > cpu2: > 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,FSGSBASE,SMEP,ERMS > cpu2: 256KB 64b/line 8-way L2 cache > cpu3 at mainbus0: apid 3 (application processor) > cpu3: Intel(R) Core(TM) i5-3360M CPU @ 2.80GHz, 2793.66 MHz > cpu3: > 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,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,FSGSBASE,SMEP,ERMS > cpu3: 256KB 64b/line 8-way L2 cache > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins > acpimcfg0 at acpi0 addr 0xf800, bus 0-63 > acpiec0 at acpi0 > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus -1 (PEG_) > acpiprt2 at acpi0: bus 2 (EXP1) > acpiprt3 at acpi0: bus 3 (EXP2) > acpiprt4 at acpi0: bus 4 (EXP3) > acpicpu0 at acpi0: C3, C2, C1, PSS > acpicpu1 at acpi0: C3, C2, C1, PSS > acpicpu2 at acpi0: C3, C2, C1, PSS > acpicpu3 at acpi0: C3, C2, C1, PSS > acpipwrres0 at acpi0: PUBS > acpitz0 at acpi0: critical temperature is 103 degC > acpibtn0 at acpi0: LID_ > acpibtn1 at acpi0: SLPB > acpibat0 at acpi0: BAT0 model "45N1029" serial 4430 type LION oem "LGC" > acpibat1 at acpi0: BAT1 not present > acp
Re: trunk(4) and non-standard MTU
Can you show the output of "ifconfig trunk0" after you have run this? And uname -a since a moderately recent -current wont allow mtus >1500 when I test. 2012/9/18 mxb : > /etc/hostname.em0: > up mtu 9000 > > /etc/hostname.em1 > up mtu 9000 > > /etc/hostname.trunk0 > trunkproto lacp trunkport em0 trunkport em1 10.10.10.10 netmask > 255.255.255.0 -inet6 mtu 9000 > > "mtu 9000" in hostname.trunk0 probably not needed as it will get its' > correct mtu from em0. > > //mxb > > On 09/18/2012 10:04 AM, Scott wrote: >> On 18 September 2012 03:47, mxb wrote: >>> Yes you can, but the real hw has to support it as well. >>> >>> On 09/18/2012 02:34 AM, S. Scott wrote: Is it possible to use non-standard (1500) MTU on a trunk(4) pseudo-interface or on the real em(4) interfaces that comprise the trunk0 interface, or on the VLANs carried therein. We'd like to use jumbo frames on the link-aggregate between a Cisco catalyst switch (port group) and the openBSD router and firewall. $ uname -a 5.1 GENERIC.MP#207 amd64 With thanks, — iThing: Big thumbs & little keys. Please excuse typo, spelling and grammar errors • Good planets are hard to find – think before you print • My desire to be well-informed is currently at odds with my desire to remain sane. • Last night I played a blank CD at full blast. The Mime next door went nuts. >>> >> >> Could you please explain how. >> >> ifconfig trunk0 mtu , where > 1500 results in the error, >> >> ifconfig: SIOCSIFMTU: Invalid argument >> >> em(4) hardware does support jumbo's ( > 1500) > -- To our sweethearts and wives. May they never meet. -- 19th century toast
ATI Radeon HD6570
Hi, I have an ATI Radeon HD6570 card. Dmesg gives me: vga1 at pci1 dev 0 function 0 vendor "ATI", unknown product 0x6759 rev 0x00 and the driver used seems to be VESA. I naturally changed to: --- src/sys/dev/pci/pcidevs 2012-11-17 16:42:29.0 +0100 +++ src/sys/dev/pci/pcidevs 2012-11-23 12:58:50.357249029 +0100 @@ -1262,6 +1262,7 @@ product ATI RADEON_X700_SE 0x5e4f Radeon X700 SE product ATI RADEON_X700_SE_S 0x5e6f Radeon X700 SE Sec product ATI RADEON_HD6670 0x6758 Radeon HD 6670 +product ATI RADEON_HD6570 0x6759 Radeon HD 6570 product ATI RADEON_HD5800 0x6899 Radeon HD 5800 product ATI RADEON_HD5700 0x68b8 Radeon HD 5700 product ATI RADEON_HD5670 0x68d8 Radeon HD 5670 But it's still not recognized. I looked at pci/drm/radeon_drv.c, but I'm not sure I can add my card, as - according to man radeon - it's a REDWOOD chip, which doesn't seem to be supported on openbsd. My questions are: Are REDWOOD chips supported ? If yes, how can I get my card work correctly ? If no, is there any support planned ? Thanks
Re: how to make power off button work like halt -p
??? wrote: > do you mean that i should compile the acpictn device to the > kernel.default 5.2 kernel have acpi device, but without acpibtn. > If your dmesg doesn't show a acpibtn device, apart from checking hardware setup (e.g. BIOS settings), I'm out of ideas. > -- Original --From: > "Remco";Date: Fri, Nov 23, 2012 04:00 AMTo: > "ç¼éè"; "misc"; Subject: Re: how > to make power off button work like halt -p > ??? wrote: > >> i need to install openbsd on a blind computer(without monitor).so i > need >> to press power off button to shutdown the computer.i know that use ssh > is >> a right way. but press power off is more effective way. >> >> >> >> >> >> in the version 5.2, i just press power off, and the computer shutdown >> directly without clean the file system. i think this would do harm to > the >> database server. i want to know how to make power off button work link >> halt -p command. > > You may need to enable something in your BIOS along the lines of "press > the > power button for 4 seconds in order to power off". > > From the software perspective, I think you also need the acpibtn(4) > device. > (check your dmesg for that)
Re: -lcrypt error when I try to compile libcli
On Fri, Nov 23, 2012 at 11:03 AM, C. L. Martinez wrote: > Hi all, > > I am trying to compile libcli (http://code.google.com/p/libcli/) > library under OpenBSD 5.2 amd64, and returns me this error: > > gcc -g -O3 -Wall -std=c99 -pedantic -Wformat-security > -Wno-format-zero-length -Werror -Wwrite-strings -Wformat > -fdiagnostics-show-option -Wextra -Wsign-compare -Wcast-align > -Wno-unused-parameter -fPIC -o libcli.o -c libcli.c > gcc -o libcli.so.1.9.6 libcli.o -shared -Wl,-soname,libcli.so.1.9 -lcrypt > /usr/bin/ld: cannot find -lcrypt > collect2: ld returned 1 exit status > gmake: *** [libcli.so] Error 1 > > But according to this message > http://old.nabble.com/-DBMail-554-%3A-%22-lcrypt%22-not-necessary-on-OpenBSD-td9783582.html, > "-lcrypt" flag is not needed. Is it correct?? It is. On OpenBSD, crypt() is part of libc. Ciao, David
Re: how to make power off button work like halt -p
??? wrote: > i need to install openbsd on a blind computer(without monitor).so i need > to press power off button to shutdown the computer.i know that use ssh is > a right way. but press power off is more effective way. > > > > > > in the version 5.2, i just press power off, and the computer shutdown > directly without clean the file system. i think this would do harm to the > database server. i want to know how to make power off button work link > halt -p command. You may need to enable something in your BIOS along the lines of "press the power button for 4 seconds in order to power off". >From the software perspective, I think you also need the acpibtn(4) device. (check your dmesg for that)
