Re: running multiple simultaneous X sessions as different users
On Sat, 21 Mar 2015 14:14:22 -0700 luke...@onemodel.org wrote:
> On 03/16/15 19:38, Jean-Philippe Ouellet wrote:
> > On Sun, Mar 15, 2015 at 07:12:23PM -0400, Ted Unangst wrote:
> >> luke...@onemodel.org wrote:
> >>> The goal: I'd like to run multiple simultaneous X sessions and switch
> >>> among them with Ctrl-Alt-F8, Ctrl-Alt-F9, etc, each one as a different
> >>> user (separation of privileges, like general browsing vs. admin &
> >>> programming, vs. banking, etc, so that if one is compromised by a
> >>> browser flaw etc, the other user accounts are unaffected.
> >> I would probably start with Xnest here.
> > I've had better luck with a slightly hacked up Xephyr for this purpose.
> >
> > Just be aware that screen locking at the top level won't work while nested
> > sessions grabbed exclusive focus (unless you patch it to work differently),
> > and window resizing can be annoying at times.
> >
> > Be sure to actually isolate the different X server processes across
> > different
> > users and such and preferably chroot them and tell pf to block everything
> > for
> > those users.
> >
> > It's annoying and probably doesn't really gain you much anyway.
>
> That sounds doable, but too easy for me to make a mistake that
> invalidates it, and I don't know whether in that strategy a compromised
> app (such as a browser) could watch keystrokes on another app.
>
while i am no X guru by any means, i am pretty sure that the X11 SECURITY
extension prevents that. (that is at least what i take away from the section
for -X in ssh(1)).
> (This other thread is also interesting in this light (from ~2 days
> ago): "isolating untrusted programs in ssh chroot jails".)
that's mine. basically i detail how to do most of what Mssr. Ouellet mentioned
above.
>
> So, I was going to try doing as Miod kindly suggested in another part
> of this thread:
>
> On 03/15/15 04:15, Miod Vallat wrote:
> >> If you run another X server instance, it will use the seventh virtual
> >> console (ctrl-alt-F7). But I am not sure drm-enabled X servers can run
> >> multiple instances.
> > Thanks. Is there a way to turn off drm, such as via a sysctl
> > setting for kern.malloc.kmemstat.DRM, or somehow forcing it to use a
> > different (known stable) driver? Or, if not, anything else I can
> > try except non-drm video hardware?
>
> ...until I stumbled on this which looks the easiest/safest so far:
> > List: openbsd-misc
> > Subject:Re: Almost offtopic question to the "Improving Browser >
> > Security" question
> > From: Stuart Henderson
> > Date: 2015-03-04 8:37:03
> > Message-ID: slrnmfdh1f.8gs.stu () naiad ! spacehopper ! org
> >
> > On 2015-03-03, someone wrote:
> > > Wow, copying the .Xauthority to the "separated" user worked!
> > > But I'm still thinking that the "separated" user can give out the
> > > command:
> > > xinput test 6
> > > and can see what anyone types in via X.
> > See xauth(1) about generating an untrusted auth token. If you're
> > feeling lazy, enabling ssh X forwarding and using ssh -X
> > user@localhost might be easier, but will be slower.
> (http://marc.info/?l=openbsd-misc&m=142545841513214&w=2
> ...which started here (also useful):
> http://undeadly.org/cgi?action=article&sid=20150303075848 )
>
>
> So, if I use xauth after reading the manpage carefully, or use ssh -X
> from one localhost user to another, and launch a bunch of apps as
> different users all in the same X server, what are the risks of
> compromise between accounts?
>
> Thanks to all who've commented: this has been educational & useful.
>
> -Luke A Call
>
there is probably about as little chance of compromise as is possible. the
only real privilege separation on unix is having different users, and
restricting them as much as possible (like with chroot).
if you are running a command as another user, ie:
ssh -X pdf@localhost xpdf file.pdf
then the only way the program has to interact with your display is thru an
ssh tunnel which acts as a filter. so in this case xpdf will write to the
DISPLAY given to it from ssh, which is a tunnel created by ssh which restricts
the commands that can be sent along that tunnel to the real display.
it's not possible to isolate an account completely from the system unless it
is chroot(8)ed. that way that user will not have access to anything else in
the filesystem. if you read my notes though, i note it is not possible for all
programs to be locked up so.
you can skip the chroot part of my notes, near the end i explain using Xephyr.
Xephyr is probably not the most trustworthy, but it's a choice between writing
to it, or to the main server.
the only thing i don't really get into in my notes is what Mssr. Ouellet
mentions regarding using pf to block the user. this obviously is not a good
idea for a web browser, but for something like xpdf it is.
you just need some rules in pf.conf like:
block out log
pass out log quick on $intif proto tcp user { browse, 1000 }
pa
Re: Can't trunk wireless adapter on ThinkPad x240
Stefan Sperling wrote: > On Sat, Mar 21, 2015 at 11:19:18PM +0100, Aram Hăvărneanu wrote: > > I have a ThinkPad x240 (Intel 7620 wireless) running -current (to get > > the new iwm(4) driver). Wireless works fine, but when I try to use a > > trunk(4) device, in the way it's described in the faq[1], it doesn't > > work. > > > > When I boot without wired ethernet plugged in, networking doesn't work > > at all (dhcp times out after a while, then nothing works), even if I > > later plug an ethernet cable in. > > > > When I boot with wired ethernet plugged in, when I remove the cable > > ifconfig(8) tells me trunk0 failed over to iwm0, but in fact > > networking doesn't work. > > > > My configuration is: http://sprunge.us/SDaD > > > > Is it my fault? How can I debug this further? Thanks. > > > > [1] http://www.openbsd.org/faq/faq6.html#Wireless > > > > -- > > Aram Hăvărneanu > > I believe trunk(4) changes the MAC address of its ports, so the following > note from the iwm page applies to your situation. The wording is probably > too specific. The problem was found with 'ifconfig iwm9 lladdr random' but > there are many ways to change the MAC. > > BUGS > The firmware stops passing traffic if the MAC address is changed with > # ifconfig iwm0 lladdr ... > > I could not yet figure out exactly why the firmware stops working when the > MAC address is changed. Help is welcome. trunk uses the MAC of the master device, which is probably going to be em0 in many setups, but it's possible to reorder the devices and make iwm0 the master. A little less convenient as it won't failover to the ethernet automatically.
Re: xkci recommendations
Ed Ahlsen-Girard wrote: > On Sat, 21 Mar 2015 21:48:06 +0100 > ropers wrote: > > > On Sat, Mar 21, 2015 at 08:47:27AM -0500, Ed Ahlsen-Girard wrote: > > > > > > I got a card to exploit the xkci support, > > > > > > > > > On 21 March 2015 at 21:00, Bryan Steele wrote: > > > You didn't send a dmesg. xhci(4) support is new for 5.7 > > > > > > Thank you for this. I got very confused by "xkci" [sic] and couldn't > > figure it out before reading your reply. > > Apologies for typo. I run snapshots, and I omitted the dmesg because > xhci is in the probe, but the system can't drive this card. Manufacturer > wants me to install a Windows driver. > > This is why I asked what cards *work*. The manufacturer will tell you to install a Windows driver for just about every device. That's not well correlated with OpenBSD support. The xhci driver should support all devices which advertise themselves as USB3 hosts. You can read through the cvs history and look for mentions of particular devices, though I'm not sure that will help you find one. http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/xhci.c
Re: iwm0: fatal firmware error on -current
On Thu, Mar 19, 2015 at 08:20:41PM +1100, Jonathan Gray wrote:
> On Thu, Mar 19, 2015 at 09:59:39AM +0100, Mattieu Baptiste wrote:
> > On Thu, Mar 19, 2015 at 9:09 AM, Jonathan Gray wrote:
> > >> It doesn't change anything.
> > >> As soon as I set an address on the interface (manually or with
> > >> dhclient), "mode 11g" is resetted and the errors in the logs are the
> > >> same.
> > >
> > > Can you include the output of pcidump -v?
> > >
> > > It's possible you have an adapter that doesn't support 11a.
> >
> > Here it is:
>
> The way your device is handled in Intel's Linux code is:
>
> {IWL_PCI_DEVICE(0x08B2, 0xC262, iwl7260_n_cfg)},
>
> Which is "Intel(R) Wireless N 7260"
> http://ark.intel.com/products/75174/Intel-Wireless-N-7260
>
> the 7260 adapters that can do multiple bands are
>
> "Intel(R) Dual Band Wireless N 7260" iwl7260_2n_cfg
> http://ark.intel.com/products/75440/Intel-Dual-Band-Wireless-N-7260
> "Intel(R) Dual Band Wireless AC 7260"
> iwl7260_2ac_cfg,iwl7260_2ac_cfg_high_temp
> http://ark.intel.com/products/75439/Intel-Dual-Band-Wireless-AC-7260
>
> The driver wrongly assumes all devices support 11a, this needs to be fixed.
> Though the Linux code seems to make the band decision based on the EEPROM
> not the sub device id.
Try the following.
diff --git sys/dev/pci/if_iwm.c sys/dev/pci/if_iwm.c
index 6072e6a..3bec032 100644
--- sys/dev/pci/if_iwm.c
+++ sys/dev/pci/if_iwm.c
@@ -6410,8 +6410,38 @@ iwm_preinit(struct iwm_softc *sc)
IWM_UCODE_API(sc->sc_fwver),
ether_sprintf(sc->sc_nvm.hw_addr));
- /* Reattach net80211 so MAC address and channel map are picked up. */
- ieee80211_ifdetach(ifp);
+ ic->ic_phytype = IEEE80211_T_OFDM; /* not only, but not used */
+ ic->ic_opmode = IEEE80211_M_STA;/* default to BSS mode */
+ ic->ic_state = IEEE80211_S_INIT;
+
+ /* Set device capabilities. */
+ ic->ic_caps =
+ IEEE80211_C_WEP | /* WEP */
+ IEEE80211_C_RSN | /* WPA/RSN */
+ IEEE80211_C_SCANALL | /* device scans all channels at once */
+ IEEE80211_C_SHSLOT |/* short slot time supported */
+ IEEE80211_C_SHPREAMBLE; /* short preamble supported */
+
+ if (sc->sc_nvm.sku_cap_band_52GHz_enable)
+ ic->ic_sup_rates[IEEE80211_MODE_11A] =
ieee80211_std_rateset_11a;
+ ic->ic_sup_rates[IEEE80211_MODE_11B] = ieee80211_std_rateset_11b;
+ ic->ic_sup_rates[IEEE80211_MODE_11G] = ieee80211_std_rateset_11g;
+
+ /* IBSS channel undefined for now. */
+ ic->ic_ibss_chan = &ic->ic_channels[1];
+
+ /* Max RSSI */
+ ic->ic_max_rssi = IWM_MAX_DBM - IWM_MIN_DBM;
+
+ ifp->if_softc = sc;
+ ifp->if_flags = IFF_BROADCAST | IFF_SIMPLEX | IFF_MULTICAST;
+ ifp->if_ioctl = iwm_ioctl;
+ ifp->if_start = iwm_start;
+ ifp->if_watchdog = iwm_watchdog;
+ IFQ_SET_READY(&ifp->if_snd);
+ memcpy(ifp->if_xname, DEVNAME(sc), IFNAMSIZ);
+
+ if_attach(ifp);
ieee80211_ifattach(ifp);
ic->ic_node_alloc = iwm_node_alloc;
@@ -6421,6 +6451,12 @@ iwm_preinit(struct iwm_softc *sc)
ic->ic_newstate = iwm_newstate;
ieee80211_media_init(ifp, iwm_media_change, ieee80211_media_status);
+#if NBPFILTER > 0
+ iwm_radiotap_attach(sc);
+#endif
+ timeout_set(&sc->sc_calib_to, iwm_calib_timeout, sc);
+ task_set(&sc->init_task, iwm_init_task, sc);
+
return 0;
}
@@ -6441,8 +6477,6 @@ iwm_attach(struct device *parent, struct device *self,
void *aux)
struct pci_attach_args *pa = aux;
pci_intr_handle_t ih;
pcireg_t reg, memtype;
- struct ieee80211com *ic = &sc->sc_ic;
- struct ifnet *ifp = &ic->ic_if;
const char *intrstr;
int error;
int txq_i, i;
@@ -6592,22 +6626,6 @@ iwm_attach(struct device *parent, struct device *self,
void *aux)
/* Clear pending interrupts. */
IWM_WRITE(sc, IWM_CSR_INT, 0x);
- ic->ic_phytype = IEEE80211_T_OFDM; /* not only, but not used */
- ic->ic_opmode = IEEE80211_M_STA;/* default to BSS mode */
- ic->ic_state = IEEE80211_S_INIT;
-
- /* Set device capabilities. */
- ic->ic_caps =
- IEEE80211_C_WEP | /* WEP */
- IEEE80211_C_RSN | /* WPA/RSN */
- IEEE80211_C_SCANALL | /* device scans all channels at once */
- IEEE80211_C_SHSLOT |/* short slot time supported */
- IEEE80211_C_SHPREAMBLE; /* short preamble supported */
-
- ic->ic_sup_rates[IEEE80211_MODE_11A] = ieee80211_std_rateset_11a;
- ic->ic_sup_rates[IEEE80211_MODE_11B] = ieee80211_std_rateset_11b;
- ic->ic_sup_rates[IEEE80211_MODE_11G] = ieee80211_std_rateset_11g;
-
for (i = 0; i < nitems(sc->sc_phyctxt); i++) {
sc->sc_phyctxt[i].id = i;
}
@@ -6615,30 +6633,6 @@ iwm_attach(struct devic
Re: Can't trunk wireless adapter on ThinkPad x240
On Sat, Mar 21, 2015 at 11:19:18PM +0100, Aram Hăvărneanu wrote: > I have a ThinkPad x240 (Intel 7620 wireless) running -current (to get > the new iwm(4) driver). Wireless works fine, but when I try to use a > trunk(4) device, in the way it's described in the faq[1], it doesn't > work. > > When I boot without wired ethernet plugged in, networking doesn't work > at all (dhcp times out after a while, then nothing works), even if I > later plug an ethernet cable in. > > When I boot with wired ethernet plugged in, when I remove the cable > ifconfig(8) tells me trunk0 failed over to iwm0, but in fact > networking doesn't work. > > My configuration is: http://sprunge.us/SDaD > > Is it my fault? How can I debug this further? Thanks. > > [1] http://www.openbsd.org/faq/faq6.html#Wireless > > -- > Aram Hăvărneanu I believe trunk(4) changes the MAC address of its ports, so the following note from the iwm page applies to your situation. The wording is probably too specific. The problem was found with 'ifconfig iwm9 lladdr random' but there are many ways to change the MAC. BUGS The firmware stops passing traffic if the MAC address is changed with # ifconfig iwm0 lladdr ... I could not yet figure out exactly why the firmware stops working when the MAC address is changed. Help is welcome.
Re: Can't trunk wireless adapter on ThinkPad x240
On Mar 21, 2015, at 5:19 PM, Aram Hăvărneanu wrote: > I have a ThinkPad x240 (Intel 7620 wireless) running -current (to get > the new iwm(4) driver). Wireless works fine, but when I try to use a > trunk(4) device, in the way it's described in the faq[1], it doesn't > work. > > When I boot without wired ethernet plugged in, networking doesn't work > at all (dhcp times out after a while, then nothing works), even if I > later plug an ethernet cable in. > > When I boot with wired ethernet plugged in, when I remove the cable > ifconfig(8) tells me trunk0 failed over to iwm0, but in fact > networking doesn't work. > > My configuration is: http://sprunge.us/SDaD > > Is it my fault? How can I debug this further? Thanks. > > [1] http://www.openbsd.org/faq/faq6.html#Wireless > > -- > Aram Hăvărneanu > netstart(8), hostname.if(5) # sh /etc/netstart foo0 where foo0 is your interface
Re: xkci recommendations
On Sat, 21 Mar 2015 21:48:06 +0100 ropers wrote: > On Sat, Mar 21, 2015 at 08:47:27AM -0500, Ed Ahlsen-Girard wrote: > > > > I got a card to exploit the xkci support, > > > > > On 21 March 2015 at 21:00, Bryan Steele wrote: > > You didn't send a dmesg. xhci(4) support is new for 5.7 > > > Thank you for this. I got very confused by "xkci" [sic] and couldn't > figure it out before reading your reply. Apologies for typo. I run snapshots, and I omitted the dmesg because xhci is in the probe, but the system can't drive this card. Manufacturer wants me to install a Windows driver. This is why I asked what cards *work*. I have not RMAd it yet. If some body wants me to put it back in send a dmesg I will. -- Edward Ahlsen-Girard Ft Walton Beach, FL
Can't trunk wireless adapter on ThinkPad x240
I have a ThinkPad x240 (Intel 7620 wireless) running -current (to get the new iwm(4) driver). Wireless works fine, but when I try to use a trunk(4) device, in the way it's described in the faq[1], it doesn't work. When I boot without wired ethernet plugged in, networking doesn't work at all (dhcp times out after a while, then nothing works), even if I later plug an ethernet cable in. When I boot with wired ethernet plugged in, when I remove the cable ifconfig(8) tells me trunk0 failed over to iwm0, but in fact networking doesn't work. My configuration is: http://sprunge.us/SDaD Is it my fault? How can I debug this further? Thanks. [1] http://www.openbsd.org/faq/faq6.html#Wireless -- Aram Hăvărneanu
Re: running multiple simultaneous X sessions as different users
On 03/16/15 19:38, Jean-Philippe Ouellet wrote: On Sun, Mar 15, 2015 at 07:12:23PM -0400, Ted Unangst wrote: luke...@onemodel.org wrote: The goal: I'd like to run multiple simultaneous X sessions and switch among them with Ctrl-Alt-F8, Ctrl-Alt-F9, etc, each one as a different user (separation of privileges, like general browsing vs. admin & programming, vs. banking, etc, so that if one is compromised by a browser flaw etc, the other user accounts are unaffected. I would probably start with Xnest here. I've had better luck with a slightly hacked up Xephyr for this purpose. Just be aware that screen locking at the top level won't work while nested sessions grabbed exclusive focus (unless you patch it to work differently), and window resizing can be annoying at times. Be sure to actually isolate the different X server processes across different users and such and preferably chroot them and tell pf to block everything for those users. It's annoying and probably doesn't really gain you much anyway. That sounds doable, but too easy for me to make a mistake that invalidates it, and I don't know whether in that strategy a compromised app (such as a browser) could watch keystrokes on another app. (This other thread is also interesting in this light (from ~2 days ago): "isolating untrusted programs in ssh chroot jails".) So, I was going to try doing as Miod kindly suggested in another part of this thread: On 03/15/15 04:15, Miod Vallat wrote: If you run another X server instance, it will use the seventh virtual console (ctrl-alt-F7). But I am not sure drm-enabled X servers can run multiple instances. Thanks. Is there a way to turn off drm, such as via a sysctl setting for kern.malloc.kmemstat.DRM, or somehow forcing it to use a different (known stable) driver? Or, if not, anything else I can try except non-drm video hardware? ...until I stumbled on this which looks the easiest/safest so far: > List: openbsd-misc > Subject:Re: Almost offtopic question to the "Improving Browser > > Security" question > From: Stuart Henderson > Date: 2015-03-04 8:37:03 > Message-ID: slrnmfdh1f.8gs.stu () naiad ! spacehopper ! org > > On 2015-03-03, someone wrote: > > Wow, copying the .Xauthority to the "separated" user worked! > > But I'm still thinking that the "separated" user can give out the > > command: > > xinput test 6 > > and can see what anyone types in via X. > See xauth(1) about generating an untrusted auth token. If you're > feeling lazy, enabling ssh X forwarding and using ssh -X > user@localhost might be easier, but will be slower. (http://marc.info/?l=openbsd-misc&m=142545841513214&w=2 ...which started here (also useful): http://undeadly.org/cgi?action=article&sid=20150303075848 ) So, if I use xauth after reading the manpage carefully, or use ssh -X from one localhost user to another, and launch a bunch of apps as different users all in the same X server, what are the risks of compromise between accounts? Thanks to all who've commented: this has been educational & useful. -Luke A Call
Re: Sunfire v120 question
On 2015-03-20 Fri 15:36 PM |, Jeremiah Ford wrote: > > I have recently acquired a SunFire v120. Ace. Join sp...@openbsd.org http://www.openbsd.org/mail.html
Re: xkci recommendations
On 03/21/15 09:47, Ed Ahlsen-Girard wrote: > I got a card to exploit the xkci support, and but it turned out to want > a Windows driver and therefore doesn't work (don't buy Anker® Uspeed > USB 3.0 PCI-E Express Card with 4 USB 3.0 Ports and 5V 4-Pin Power > Connector for Desktops [VL805 Chipset]). > > What are some USB 3 cards that DO work? > > It's not a desktop card but if anyone else out there has a pre-USB3.0 laptop this card was plug-and-play: http://www.ebay.com/itm/121586584316 xhci0 at pci5 dev 0 function 0 "Renesas uPD720202 xHCI" rev 0x02: msi usb1 at xhci0: USB revision 3.0 uhub1 at usb1 "Renesas xHCI root hub" rev 3.00/1.00 addr 1 ~Brian
Re: xkci recommendations
On Sat, Mar 21, 2015 at 08:47:27AM -0500, Ed Ahlsen-Girard wrote: > I got a card to exploit the xkci support, and but it turned out to want > a Windows driver and therefore doesn't work (don't buy Anker?? Uspeed > USB 3.0 PCI-E Express Card with 4 USB 3.0 Ports and 5V 4-Pin Power > Connector for Desktops [VL805 Chipset]). > > What are some USB 3 cards that DO work? > > > -- > > Edward Ahlsen-Girard > Ft Walton Beach, FL You didn't send a dmesg. xhci(4) support is new for 5.7.
xkci recommendations
I got a card to exploit the xkci support, and but it turned out to want a Windows driver and therefore doesn't work (don't buy Anker® Uspeed USB 3.0 PCI-E Express Card with 4 USB 3.0 Ports and 5V 4-Pin Power Connector for Desktops [VL805 Chipset]). What are some USB 3 cards that DO work? -- Edward Ahlsen-Girard Ft Walton Beach, FL
Re: SMP kernel/AMD64 stuck in reboot loop - NIC driver or other bug?
Well, I discovered the issue - the few machines that work properly had a different quad-port nic in them. With certain BIOS settings, you can catch part of the kernel panic before the screen goes crazy. Codes that were visible depending on BIOS settings: "kernel: type 1994916275 trap, code=0" "kernel: type 269 trap. code=0" You can reproduce the error on this hardware by trying to boot the AMD64/MP kernel with a quad-port Intel I340-T4 (Copper) with 82580 chipset on this hardware. (SuperMicro H8SGL-F motherboard, AMD 6344 cpu). I tried this on 4 identical machines, all purchased in the same batch, with four different NICs. Same result always. I have no idea if it's the NIC driver, or something else - but it works fine without the NIC, or with a different one (82573L). If anyone has any ideas, or would like more info, or if a dev suspects it could be the driver, contact me off-list and I can arrange to send hardware if it helps. -John On 03/20/2015 03:09 PM, John E.P. Hynes wrote: I've got three identical boxes that all display the same behavior: Install of 5.6 or the March 18th 5.7 snapshot works, but is painfully slow (no disk access on the CD or disks while "stalled") and on the first reboot, it gets about as far as loading wskbd before rebooting spontaneously. I'm trying to install onto a softraid RAID 1, but I've also tried this with just one disk to the same result. If I boot bsd.sp at the boot prompt, it will run without issue on the SP kernel. dmesg follows. If anyone has any insight, let me know please. OpenBSD 5.6 (GENERIC) #310: Fri Aug 8 00:14:24 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 8571715584 (8174MB) avail mem = 8334798848 (7948MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0x9ac00 (40 entries) bios0: vendor American Megatrends Inc. version "3.5" date 11/25/2013 bios0: Supermicro H8SGL acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET SRAT SSDT acpi0: wakeup devices PC02(S4) PC03(S4) PC04(S4) PC05(S4) PC06(S4) PC07(S4) PC09(S4) PC0A(S4) PC0B(S4) PC0C(S4) SBAZ(S4) PSKE(S4) PSMS(S4) ECIR(S4) P0PC(S4) UHC1(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 32 (boot processor) cpu0: AMD Opteron(tm) Processor 6344 , 2600.39 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,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 12MB 64b/line 128-way L3 cache cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 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 199MHz 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 cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 0 pa 0xfec0, version 21, 24 pins ioapic1 at mainbus0: apid 1 pa 0xfec2, version 21, 32 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PC02) acpiprt2 at acpi0: bus -1 (PC03) acpiprt3 at acpi0: bus -1 (PC04) acpiprt4 at acpi0: bus 2 (PC09) acpiprt5 at acpi0: bus 3 (PC0A) acpiprt6 at acpi0: bus 4 (P0PC) acpicpu0 at acpi0: PSS acpibtn0 at acpi0: PWRB ipmi at mainbus0 not configured cpu0: 2600 MHz: speeds: 2600 2300 2000 1700 1400 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "ATI SR5650 Host" rev 0x02 ppb0 at pci0 dev 2 function 0 "ATI SR5690 PCIE" rev 0x00: msi pci1 at ppb0 bus 1 em0 at pci1 dev 0 function 0 "Intel 82580" rev 0x01: msi, address 90:e2:ba:35:2c:dc em1 at pci1 dev 0 function 1 "Intel 82580" rev 0x01: msi, address 90:e2:ba:35:2c:dd em2 at pci1 dev 0 function 2 "Intel 82580" rev 0x01: msi, address 90:e2:ba:35:2c:de em3 at pci1 dev 0 function 3 "Intel 82580" rev 0x01: msi, address 90:e2:ba:35:2c:df ppb1 at pci0 dev 9 function 0 "ATI SR5690 PCIE" rev 0x00: msi pci2 at ppb1 bus 2 em4 at pci2 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address 00:25:90:86:71:38 ppb2 at pci0 dev 10 function 0 "ATI SR5690 PCIE" rev 0x00: msi pci3 at ppb2 bus 3 em5 at pci3 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address 00:25:90:86:71:39 ahci0 at pci0 dev 17 function 0 "ATI SBx00 SATA" rev 0x00: apic 0 int
Re: Sunfire v120 question
On 2015-03-21, Riccardo Mottola wrote: > Hi, > > Brian McCafferty wrote: >> Just a serial cable, then you can use tip(1). The connections and other >> info are in the V120 user guide which you can download from Oracle. Get >> a usb-serial adapter if you don't have a serial port on the machine >> you're trying to connect to it. > well not just a "serial" cable, but you need to have a RJ45 at one end. > It is a plain ol' RS232 but with an unusual connector. You need an > adapter for these, you can do one yourself if you have the tweezers to > crimp the LAN cables. These are normally made with a "de9-rj45 modular connector" like startech gc98ff, these don't need tools. You can also get all-in-one usb to rj45-rs232 adapters now, search ebay for "ftdi rj45". Most say they're for Cisco, IIRC the Sun pinout is the same but either confirm that for yourself or look for one that specifically says Sun.
Re: frequently wifi athn device timeout
Yes, I do use Irssi and chromium all the time. On Thu, Mar 19, 2015 at 6:02 AM, Henrique Lengler wrote: > On Tue, Mar 17, 2015 at 11:12:34AM +0300, Evgeny Zhavoronkov wrote: > > I have the same problem with the latest snapshot and yes, the problem is > > with any AP and they are in range 1-5 meters. > > Do you use irssi and/or chromium? To me looks like when I am running > these apps, I get more timeouts. > -- > Regards > > Henrique Lengler
Re: Sunfire v120 question
Hi, Brian McCafferty wrote: Just a serial cable, then you can use tip(1). The connections and other info are in the V120 user guide which you can download from Oracle. Get a usb-serial adapter if you don't have a serial port on the machine you're trying to connect to it. well not just a "serial" cable, but you need to have a RJ45 at one end. It is a plain ol' RS232 but with an unusual connector. You need an adapter for these, you can do one yourself if you have the tweezers to crimp the LAN cables. Riccardo
