Building foxtrotgps from source on 5.1
I just attempted to build foxtrotgps-1.1.1 from source on an i386 OpenBSD 5.1 stable system. The make fails: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR="\"/usr/local/from_source/share\"" -DPACKAGE_PIXMAPS_DIR="\"/usr/local/from_source/share/pixmaps\"" -DPACKAGE_LOCALE_DIR="\"/usr/local/from_source/share/locale\"" -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/X11R6/include -I/usr/local/include/gdk-pixbuf-2.0 -pthread -I/usr/local/include/cairo -I/usr/X11R6/include/pixman-1 -I/usr/X11R6/include/freetype2 -I/usr/include/dev/pci/drm -I/usr/local/include/libpng -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/libglade-2.0 -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/X11R6/include -I/usr/local/include/cairo -I/usr/local/include/atk-1.0 -I/usr/X11R6/include/pixman-1 -I/usr/include/dev/pci/drm -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/libpng -pthread -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/X11R6/include/freetype2 -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/local/include/gconf/2 -I/usr/local/include/dbus-1.0 -I/usr/local/lib/dbus-1.0/include -pthread -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include/libexif -I/usr/local/include/libxml2 -I/usr/local/include-g -O2 -MT geo_photos.o -MD -MP -MF .deps/geo_photos.Tpo -c -o geo_photos.o geo_photos.c In file included from /usr/local/include/curl/curl.h:2173, from util.h:4, from geo_photos.c:11: /usr/local/include/curl/multi.h:131: error: expected declaration specifiers or '...' before 'fd_set' /usr/local/include/curl/multi.h:132: error: expected declaration specifiers or '...' before 'fd_set' /usr/local/include/curl/multi.h:133: error: expected declaration specifiers or '...' before 'fd_set' /usr/local/include/curl/curl.h needs a small fix: RCS file: RCS/curl.h,v retrieving revision 1.1 diff -r1.1 curl.h 70c70 < #if defined(_AIX) || defined(__NOVELL_LIBC__) || defined(__NetBSD__) || \ --- > #if defined(_AIX) || defined(__NOVELL_LIBC__) || defined(__NetBSD__) || defined(__OpenBSD__) || \ # With this change, this package builds and works. Hopefully this will save someone else some time. /Don Allen
XIV Ateneo 2012 Ricardo Bartis en E.S.A. - 17 de agosto, 19hs
Escuela Sistémica Argentina Institución dedicada a la formación, asistencia e investigación psicológica. Hoy nos acercamos a Uds. para invitarlos a la realización del XIV Ateneo 2012 "TEATRO, LOCURA, AMOR Y HAMBRE" Día: Viernes 17 de Agosto de 2012, 19hs. Coordina: RICARDO BARTIS Nació en Buenos Aires en 1949. Es actor, director y dramaturgo. Algunas de sus obras son "Postales argentinas", "Hamlet o la guerra de los teatros", "El corte", "El pecado no se puede nombrar" y "Donde más duele". Desde el año 1986, dirige el Sportivo Teatral de Buenos Aires. Ha recibido los mas importantes premios y distinciones tanto a nivel nacional como internacional. En 2011 la Bienal di Venezia lo considera uno de los mejores 7 directores teatrales del mundo, invitado a presentar sus trabajos en el marco de la 42ª edición. Presentador: Dr. HORACIO SEREBRINSKY ENTRADA LIBRE Y GRATUITA (Sin inscripción previa) Escuela Sistémica Argentina Fray J. S. María de Oro 1843 (C1414DBC) Telf: (5411) 4774-2875/ 6112 / 4899-1053
Re: Sierra Wireless AC595U Device problems in OpenBSD -current/-stable.
On Fri, Aug 10, 2012 at 02:02:45PM -0400, Ted Unangst wrote: > On Thu, Aug 09, 2012 at 18:51, Sergey Prysiazhnyi wrote: > > Hello misc@. > > > > Did anybody have experience of the successful use of Subj device in > > OpenBSD?.. > > The problem is that the device attached quite normal by the system: > > # dmesg | grep umsm > > umsm0 at uhub2 port 2 configuration 1 interface 0 "Sierra Wireless, > > Incorporated > > Sierra Wireless AC595U Device" rev 1.10/0.02 addr 2 > > I'm not sure of the model number, but the sierra wireless hotspot I > had worked because it attaches a cdce device. You may want to try > trading for one of those. > > http://marc.info/?l=openbsd-misc&m=128963089902577&w=2 Ted, thank you for the hint, I'll try it asap and report about the test results.
Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver
> Since I havn't seen a dmesg i guess that wsdisplay0 is your graphics card > on your pc (/dev/ttyC0). udl0 is wsdisplay1 (/dev/ttyD0). So udl1 is > wsdisplay2 (/dev/ttyE0). > > You can use wsconsctl to verify which device it should be. You're right (my dmesg is at the end of my reply) : # wsconsctl -f /dev/ttyC0 display.type display.type=vga-pci # wsconsctl -f /dev/ttyD0 display.type display.type=displaylink # wsconsctl -f /dev/ttyE0 display.type display.type=displaylink > Just giving wsconsctl will show both display.* and display1.* display.type=vga-pci display.emulations=vt100 display.screentypes=80x25,80x25bf,80x40,80x40bf,80x50,80x50bf display.focus=4 display.screen_on=250 display.screen_off=60 display.vblank=off display.kbdact=off display.msact=off display.outact=off display1.type=displaylink display1.emulations=vt100 display1.screentypes=std display1.focus=0 display1.screen_on=250 display1.screen_off=60 display1.vblank=off display1.kbdact=off display1.msact=off display1.outact=off display2.type=displaylink display2.emulations=vt100 display2.screentypes=std display2.focus=0 display2.screen_on=250 display2.screen_off=60 display2.vblank=off display2.kbdact=off display2.msact=off display2.outact=off For the moment, I am trying to get the 2 udl devices working (i.e., I have not configured the primary display ttyC0 in my xorg.conf). And I still have the same error (wsudl(1): We are not attached to the udl driver). Here is the complete dmesg : OpenBSD 5.1-stable (GENERIC) #0: Sat Aug 11 17:03:48 CEST 2012 root@test:/usr/src/sys/arch/amd64/compile/GENERIC RTC BIOS diagnostic error 7e real mem = 8495775744 (8102MB) avail mem = 8255488000 (7873MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (81 entries) bios0: vendor Apple Inc. version "MM51.88Z.0077.B10.1201241549" date 01/24/2012 bios0: Apple Inc. Macmini5,3 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT MCFG SSDT SSDT SSDT acpi0: wakeup devices P0P2(S4) GFX0(S4) PEG1(S4) EC__(S4) GMUX(S3) HDEF(S4) GIGE(S4) SDXC(S3) RP01(S4) ARPT(S4) RP02(S4) RP03(S4) EHC1(S3) EHC2(S3) 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) i7-2635QM CPU @ 2.00GHz, 1995.73 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,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG,LAHF 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 ioapic0: misconfigured as apic 0, remapped to apid 2 acpiec0 at acpi0 acpimcfg0 at acpi0 addr 0xe000, bus 0-156 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P2) acpiprt2 at acpi0: bus 6 (PEG1) acpiprt3 at acpi0: bus 2 (RP01) acpiprt4 at acpi0: bus 3 (RP02) acpiprt5 at acpi0: bus 4 (RP03) acpicpu0 at acpi0: C3, C2, C1, PSS acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpivideo0 at acpi0: IGPU cpu0: Enhanced SpeedStep 1995 MHz: speeds: 2001, 2000, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200, 1100, 1000, 900, 800 MHz memory map conflict 0xe00f8000/0x1000 memory map conflict 0xfed1c000/0x4000 memory map conflict 0xffed/0x3 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09 ppb0 at pci0 dev 1 function 0 "Intel Core 2G PCIE" rev 0x09: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 1 function 1 "Intel Core 2G PCIE" rev 0x09: msi pci2 at ppb1 bus 6 ppb2 at pci2 dev 0 function 0 vendor "Intel", unknown product 0x1513 rev 0x00 pci3 at ppb2 bus 7 ppb3 at pci3 dev 0 function 0 vendor "Intel", unknown product 0x1513 rev 0x00: msi pci4 at ppb3 bus 8 vendor "Intel", unknown product 0x1513 (class system subclass miscellaneous, rev 0x00) at pci4 dev 0 function 0 not configured ppb4 at pci3 dev 3 function 0 vendor "Intel", unknown product 0x1513 rev 0x00: msi pci5 at ppb4 bus 9 ppb5 at pci3 dev 4 function 0 vendor "Intel", unknown product 0x1513 rev 0x00: msi pci6 at ppb5 bus 10 ppb6 at pci3 dev 5 function 0 vendor "Intel", unknown product 0x1513 rev 0x00: msi pci7 at ppb6 bus 59 ppb7 at pci3 dev 6 function 0 vendor "Intel", unknown product 0x1513 rev 0x00: msi pci8 at ppb7 bus 108 vga1 at pci0 dev 2 function 0 "Intel GT2 Video" rev 0x09 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0x9000, size 0x1000 inteldrm0 at vga1: apic 2 int 16 drm0 at inteldrm0 "Intel 6 Series MEI" rev 0x04 at pci0 dev
KOLTUK KILIFI
ÝÞE KOLTUKLARINIZA ÇOK ÇOK ÖZEL KILIF YAPTIRMAKLA BAÞLAYABÝLÝRSÝNÝZ. Kýlýfý olan koltuklarýnýzý temizlemek kolay: Yýkanabilen kýlýflar sayesinde lekeler düþmanýnýz olmaktan çýkar. Kilifi makinaya atarsýnýz ve iþiniz biter! Peki ya normal koltuklar? Sabunlu bezlerle kendinizi yormaktan vazgeçin, makul fiyata kýlýf diktirin. Üstelik artýk bunu yapmak için koltuklarýnýzdan ayrý kalmanýza da gerek yok. ÝSTANBUL`da ÝSENÝZ SÝZÝN ÝÇÝN UYGUN BÝR GÜN VE SAATTE KUMAÞ KATALOÐUMUZLA GELELÝM KOLTUKLARINIZIN ÖLÇÜLERÝNÝ BÝZ ALALIM. Ýstanbul dýþýnda iseniz Ýnternet sitemize girin, belirtilen ölçüleri alýp yazýn, fotoðraflarýný yollayýn kýlýflarýnýz 15 gün içinde elinizde olsun. ÜSTELÝK ÇOK DA EKONOMÝK BÝR FÝYATA VE ÇOK DA KOLAYCA, KUMAÞ VE TERZÝ PEÞÝNDE KOÞMADAN... Ayrýntýlý Bilgi ve SÝPARÝÞ ÝÇÝN TIKLAYINIZ
Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver
On Sat, 11 Aug 2012, Alexis de BRUYN wrote: > On 11.08.2012 20:22, Mats O Jansson wrote: > >> So I did sh MAKEDEV ttyD1, and modify my xorg.conf like, > > Where did you get ttyD1 from? Try to add ttyE0. > > > I have chosen ttyD1 because I think I had to choose the next ttyD* after > ttyD0. > > Unfortunately, I have the same error with ttyE0. Just for the record, if someone is having problems in the future... Since I havn't seen a dmesg i guess that wsdisplay0 is your graphics card on your pc (/dev/ttyC0). udl0 is wsdisplay1 (/dev/ttyD0). So udl1 is wsdisplay2 (/dev/ttyE0). You can use wsconsctl to verify which device it should be. on my laptop i get (with one udl device)... # wsconsctl -f /dev/ttyC0 display.type display.type=vga-pci # wsconsctl -f /dev/ttyD0 display.type display.type=displaylink # wsconsctl -f /dev/ttyE0 display.type wsconsctl: /dev/ttyE0: No such file or directory if I add /dev/ttyE0, with MAKEDEV, i'll get wsconctl: /dev/ttyE0: Device not configured Just giving wsconsctl will show both display.* and display1.* -moj > Thanks for your help. > > -- > Alexis de BRUYN
Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver
On 11.08.2012 20:22, Mats O Jansson wrote: >> So I did sh MAKEDEV ttyD1, and modify my xorg.conf like, > Where did you get ttyD1 from? Try to add ttyE0. > I have chosen ttyD1 because I think I had to choose the next ttyD* after ttyD0. Unfortunately, I have the same error with ttyE0. Thanks for your help. -- Alexis de BRUYN
Re: Dilemma: between OpenBSD and NetBSD
> You will find idiots on @misc. It's one of the few things not in the > FAQ. We'd rather not have idiots in the FAQ (-: Miod
Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver
On Sat, 11 Aug 2012, Alexis de BRUYN wrote: > On 02.08.2012 22:31, Alexis de BRUYN wrote: > > On 02.08.2012 21:48, Matthieu Herrb wrote: > >> > >> This is the xorg.conf I use to test wsudl: > >> > >> Section "Devicë > >> Identifier "Card0" > >> Driver "wsudl" > >> Option "Devicë "/dev/ttyD0" > >> EndSection > >> > >> (Yes that's it. Modern X can figure out everything else). > > Thanks for your help Matthieu, but I still have the issue (with OpenBSD > > snapshot amd64) : > > > > [ 22191.865] (II) LoadModule: "wsudl" > > [ 22191.865] (II) Loading /usr/X11R6/lib/modules/drivers/wsudl_drv.so > > [ 22191.865] (II) Module wsudl: vendor="X.Org Foundation" > > [ 22191.865]compiled for 1.12.2, module version = 0.2.1 > > [ 22191.865]ABI class: X.Org Video Driver, version 12.0 > > [ 22191.865] (II) wsudl: driver for: DisplayLink > > [ 22191.865] (WW) Falling back to old probe method for wsudl > > [ 22191.865] (II) wsudl(0): using /dev/ttyD0 > > [ 22191.865] (EE) wsudl(0): We are not attached to the udl driver > > [ 22191.865] (II) UnloadModule: "wsudl" > > [ 22191.865] (EE) Screen(s) found, but none have a usable configuration. > > [ 22191.865] > > Fatal server error: > > [ 22191.865] no screens found > > > Hi Everybody, > > I have restarted my tests, and found that /dev/ttyDO was missing, so I > did a sh MAKEDEV ttyD0 in /dev and now I can launch X. Thanks Matthieu. > > I am trying now to add a second usb display : > > udl0 at uhub6 port 2 "DisplayLink CONV-USB2DVI" rev 2.00/0.03 addr 4 > no data for est. mode 832x768x74 > no data for est. mode 640x480x67 > no data for est. mode 720x400x70 > max_dotclock according to supported modes: 162000 > wsdisplay1 at udl0 mux 1 > wsdisplay1: screen 0 added (std, vt100 emulation) > udl1 at uhub6 port 3 "DisplayLink CONV-USB2DVI" rev 2.00/0.03 addr 5 > no data for est. mode 832x768x74 > no data for est. mode 640x480x67 > no data for est. mode 720x400x70 > max_dotclock according to supported modes: 162000 > wsdisplay2 at udl1 mux 1 > wsdisplay2: screen 0 added (std, vt100 emulation) > > So I did sh MAKEDEV ttyD1, and modify my xorg.conf like, Where did you get ttyD1 from? Try to add ttyE0. -mojx > Section "ServerLayout" > Identifier "Server Layout" > Screen 0 "Screen1" 0 0 > Screen 1 "Screen2" RightOf "Screen1" > Option "Xinerama" "On" > EndSection > > Section "Screen" > Identifier "Screen1" > Device "Card1" > EndSection > > Section "Screen" > Identifier "Screen2" > Device "Card2" > EndSection > > Section "Device" > Identifier "Card1" > Driver "wsudl" > Option "Device" "/dev/ttyD0" > EndSection > > Section "Device" > Identifier "Card2" > Driver "wsudl" > Option "Device" "/dev/ttyD1" > EndSection > > I have just one display working and the following error (complete log > after) : > [377893.438] (EE) wsudl(1): We are not attached to the udl driver > > Is my xorg.conf right? > Do I need to be more specific with BusID? > Can I use more than one ttyD* device? > > Thanks again for your help.
Re: Any T410/T420 with suspend/resume fully working in 5.1 or current?
Christiano F. Haesbaert: > > On the other hand, the Ivy-Bridge-based X230 works reasonably well: > > > > * No accelerated X11, only VESA driver. You can't switch to a text > > console or watch HD videos. > > Do you get the correct resolution at least ? Yes. With no xorg.conf, I get a 1368x768 virtual screen on a 1366x768 display. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Any T410/T420 with suspend/resume fully working in 5.1 or current?
On 11 August 2012 19:25, Christian Weisgerber wrote: > Ted Unangst wrote: > >> While we're on the subject, the T430 and T430s (ivy bridge update) do >> not work at present, or at least my T430s didn't. ahci times out >> initializing, so there's no hard drive. The wireless didn't seem to be >> detected either, and of course the usb3 ports don't work, only the >> usb2 port. > > On the other hand, the Ivy-Bridge-based X230 works reasonably well: > > * No accelerated X11, only VESA driver. You can't switch to a text > console or watch HD videos. Do you get the correct resolution at least ? > * No suspend/resume. > * No USB3 support obviously. The blue ports work fine for USB1/2, > though. > * The brightness buttons don't work, "unknown event 0x6050". > * The gigabit Ethernet only negotiates 100Base-TX. > > -- > Christian "naddy" Weisgerber na...@mips.inka.de
Re: Any T410/T420 with suspend/resume fully working in 5.1 or current?
Ted Unangst wrote: > While we're on the subject, the T430 and T430s (ivy bridge update) do > not work at present, or at least my T430s didn't. ahci times out > initializing, so there's no hard drive. The wireless didn't seem to be > detected either, and of course the usb3 ports don't work, only the > usb2 port. On the other hand, the Ivy-Bridge-based X230 works reasonably well: * No accelerated X11, only VESA driver. You can't switch to a text console or watch HD videos. * No suspend/resume. * No USB3 support obviously. The blue ports work fine for USB1/2, though. * The brightness buttons don't work, "unknown event 0x6050". * The gigabit Ethernet only negotiates 100Base-TX. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver
On 02.08.2012 22:31, Alexis de BRUYN wrote: > On 02.08.2012 21:48, Matthieu Herrb wrote: >> >> This is the xorg.conf I use to test wsudl: >> >> Section "Devicë >> Identifier "Card0" >> Driver "wsudl" >> Option "Devicë "/dev/ttyD0" >> EndSection >> >> (Yes that's it. Modern X can figure out everything else). > Thanks for your help Matthieu, but I still have the issue (with OpenBSD > snapshot amd64) : > > [ 22191.865] (II) LoadModule: "wsudl" > [ 22191.865] (II) Loading /usr/X11R6/lib/modules/drivers/wsudl_drv.so > [ 22191.865] (II) Module wsudl: vendor="X.Org Foundation" > [ 22191.865]compiled for 1.12.2, module version = 0.2.1 > [ 22191.865]ABI class: X.Org Video Driver, version 12.0 > [ 22191.865] (II) wsudl: driver for: DisplayLink > [ 22191.865] (WW) Falling back to old probe method for wsudl > [ 22191.865] (II) wsudl(0): using /dev/ttyD0 > [ 22191.865] (EE) wsudl(0): We are not attached to the udl driver > [ 22191.865] (II) UnloadModule: "wsudl" > [ 22191.865] (EE) Screen(s) found, but none have a usable configuration. > [ 22191.865] > Fatal server error: > [ 22191.865] no screens found > Hi Everybody, I have restarted my tests, and found that /dev/ttyDO was missing, so I did a sh MAKEDEV ttyD0 in /dev and now I can launch X. Thanks Matthieu. I am trying now to add a second usb display : udl0 at uhub6 port 2 "DisplayLink CONV-USB2DVI" rev 2.00/0.03 addr 4 no data for est. mode 832x768x74 no data for est. mode 640x480x67 no data for est. mode 720x400x70 max_dotclock according to supported modes: 162000 wsdisplay1 at udl0 mux 1 wsdisplay1: screen 0 added (std, vt100 emulation) udl1 at uhub6 port 3 "DisplayLink CONV-USB2DVI" rev 2.00/0.03 addr 5 no data for est. mode 832x768x74 no data for est. mode 640x480x67 no data for est. mode 720x400x70 max_dotclock according to supported modes: 162000 wsdisplay2 at udl1 mux 1 wsdisplay2: screen 0 added (std, vt100 emulation) So I did sh MAKEDEV ttyD1, and modify my xorg.conf like, Section "ServerLayout" Identifier "Server Layout" Screen 0 "Screen1" 0 0 Screen 1 "Screen2" RightOf "Screen1" Option "Xinerama" "On" EndSection Section "Screen" Identifier "Screen1" Device "Card1" EndSection Section "Screen" Identifier "Screen2" Device "Card2" EndSection Section "Device" Identifier "Card1" Driver "wsudl" Option "Device" "/dev/ttyD0" EndSection Section "Device" Identifier "Card2" Driver "wsudl" Option "Device" "/dev/ttyD1" EndSection I have just one display working and the following error (complete log after) : [377893.438] (EE) wsudl(1): We are not attached to the udl driver Is my xorg.conf right? Do I need to be more specific with BusID? Can I use more than one ttyD* device? Thanks again for your help. Here my Xorg.0.log # cat /var/log/Xorg.0.log [378524.137] (--) checkDevMem: using aperture driver /dev/xf86 [378524.151] (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32) [378524.227] X.Org X Server 1.11.4 Release Date: 2012-01-27 [378524.227] X Protocol Version 11, Revision 0 [378524.227] Build Operating System: OpenBSD 5.1 amd64 [378524.227] Current Operating System: OpenBSD test 5.1 GENERIC#0 amd64 [378524.227] Build Date: 11 February 2012 09:52:29PM [378524.227] [378524.227] Current version of pixman: 0.22.2 [378524.227]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [378524.227] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [378524.228] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 11 18:41:27 2012 [378524.247] (==) Using config file: "/etc/X11/xorg.conf" [378524.247] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [378524.272] (==) ServerLayout "Server Layout" [378524.272] (**) |-->Screen "Screen1" (0) [378524.272] (**) | |-->Monitor "" [378524.297] (**) | |-->Device "Card1" [378524.297] (==) No monitor specified for screen "Screen1". Using a default monitor configuration. [378524.297] (**) |-->Screen "Screen2" (1) [378524.297] (**) | |-->Monitor "" [378524.297] (**) | |-->Device "Card2" [378524.297] (==) No monitor specified for screen "Screen2". Using a default monitor configuration. [378524.297] (**) Option "Xinerama" "On" [378524.297] (==) Disabling SIGIO handlers for input devices [378524.297] (==) Automatically adding devices [378524.297] (==) Automatically enabling devices [378524.313] (**) Xinerama: enabled [378524.428] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fo
Re: Any T410/T420 with suspend/resume fully working in 5.1 or current?
On Fri, Aug 10, 2012 at 22:03, James Hartley wrote: > On Tue, Aug 7, 2012 at 9:06 PM, Ted Unangst wrote: > >> While we're on the subject, the T430 and T430s (ivy bridge update) do >> not work at present, or at least my T430s didn't. ahci times out >> initializing, so there's no hard drive. The wireless didn't seem to be >> detected either, and of course the usb3 ports don't work, only the >> usb2 port. >> >> > I'm curious, as I am currently looking at the T series to replace an aging > T43. Is the hard drive SATA3 or solid state? Likewise, which wireless > chipset is installed? Lenovo has options on both of these fronts. It was the X25 drive from my previous laptop, but it's the controller that doesn't work, not the hard drive. I have the 2200 wireless, which I think could be supported. I didn't fiddle too long with it, but I don't think OpenBSD's ivy bridge support is great right now (unless you want to help! :)).
Re: top res column > size column
Sorry for my mistaken, but according the manual page for the top utility, the SIZE column is: The total size of the process (the text, data, and stack segments). On Sat, Aug 11, 2012 at 1:51 AM, Ted Unangst wrote: > On Sat, Aug 11, 2012 at 00:30, Friedrich Locke wrote: >> I am monitoring my process using the top program. >> I started vim on a file with 55 lines and 939 character. >> >> Top reports the vim using 6008K of the res column and 2944K of the size >> column. >> My questions is (based on the fact that res means resident set size >> and size means data+stack+text of the process): >> >> How may a process uses more page of memory than the amount necessary >> for the sum of its data, stack and text segments ? > > Any other type of allocation, like shm or mmap.
Re: Dilemma: between OpenBSD and NetBSD
On 11 August 2012 03:49, wrote: > On 2012-08-11 03:21, Andres Perera wrote: >> >> i find it hard to believe you're involved in such project. "more >> portable", "more secure" don't mean anything unless details are >> involved. i mean, if it runs on your target hosts, what could "more >> portable" possibly mean? >> >> it's better to say: i'm trying out these two and i want a comparison. > > >> lying, saying your boss wants a bsd solution, doesn't make it seem >> more important! >> > I didn't expect to find a clairvoyant on this mailing list. > > Only, for the record: I said "client", not "boss"; I did not > say "I was involved", but that simply that "I was asked", > which is different; and I did candidly admit upfront that I > do not know much about BSDs, and that I was collecting > information; lastly, details *are*, of course, involved (as > with any project), but I simply did not feel the need to > mention them, since to me they seemed (and still seem) > irrelevant to the specific question I was asking. > > So, I really do not understand the rationale of you > accusing me of lying on the basis of one email > (incidentally, my very first email to this list). Above all, I > do not understand the aggressive tone... > Well there are a lot of people in misc, in time you'll learn who to listen and who to ignore :/
