Re: Call For Testers: Synaptics touchpads
On Wednesday 08 April 2015 22:38:33 Jakob Alvermark wrote: Hi, Tested on my Acer E3-112 with a TouchPad. It works, thank you! I have been missing two-finger scrolling, it was quite awkward using edge scrolling IMHO. It does feel like it sometimes gets stuck in scrolling mode. When trying to move the pointer just after having scrolled, it scrolls even using just one finger. I've seen this problem too and I think it's related to my patch. I'll see what I can do to fix it. Three-finger tapping also works. (Generating a button 3 event) That should've worked before. Clicking on the pad (pushing it down until it clicks sends button events for both button 1 and 2. (Which is seems to sometimes be interpreted as button 3...) Was it only sending one button before? The biggest improvement though; before it would get totally crazy at random intervals with the pointer moving all over the screen and clicking at random points. Quite annoying... This patch seems to have eliminated that! Hmm, not sure how this patch would've fixed that. I'd suggest testing a bit more just to be sure... Also, does it support horizontal scrolling? Yes, but Xorg needs to be patched. -- Rui Paulo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Dual booting FreeBSD and Win95
On Wed, Apr 8, 2015 at 12:30 PM, Ryan Stone ryst...@gmail.com wrote: We're looking at dual-booting FreeBSD and Win95. We're thinking of booting Wow, I like your problem. It's really weird, and I like weird problems. :) Since you are looking at automating a complicated process, here is a crazy idea which you might want to consider (1) Get two machines, interconnect them via a small Ethernet switch. (2) Designate one machine as a PXE server, and the other as your test machine (3) Set up a FreeBSD PXE boot environment wit NFS root, as per: https://www.freebsd.org/doc/handbook/network-diskless.html#network-pxe-nfs (4) Figure out how to PXE boot a Windows95 environment. There are articles out there for PXE booting FreeDOS which might be a place to start: http://www.cs.waikato.ac.nz/~dbaird/work/2013/11/05/pxe-boot-freedos-hard-disk-image/ On the DHCP server, you can modify dhcpd.conf to change which OS will boot via PXE boot. If you can: - automate the reboot of your test server - automate the modification of dhcpd.conf on your PXE server via some process then you might be able to get it to work. :) -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Dual booting FreeBSD and Win95
... why's stuff have to be complicated? Win95 has minimal if any boot sector protection. Just go look at what boot0cfg does, figure out which sector you have to read/modify/write, and do that. Of course, I'd also check first to ensure it's updating a freebsd bootblock, or you may render a non-dualbooting machine dead. :) -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Call For Testers: Synaptics touchpads
Hi,
The attached patch adds support for newer touchpad features and implements two
finger scrolling. This is such a common feature these days that I think we
should enable it by default and disable edge scrolling. I've implemented some
detection code to keep edge scrolling enabled when the touchpad has a
dedicated area for scrolling.
Please test it and report back your experience. To enable synaptics support,
you need:
hw.psm.synaptics_support=1
in loader.conf.
Thanks,
--
Rui Paulocommit 20e2f66c4b38429853ef98689d359451be087de3 (HEAD, master)
Author: Rui Paulo rpa...@felyko.com
Date: Sun Apr 5 20:51:35 2015
Improve Synaptics support for newer touchpads.
Enable two finger scrolling by default and disable the edge scrolling if
the touchpad has no physical zone for it. Disable directional scrolling
by default to avoid using extended buttons as scroll buttons.
Add support for ClickPad. On Lenovo laptops, this is the button
reported when one presses the touchpad.
While there, fix a problem where the extended button where not reporting
the button release event correctly: we need to save the state of the
buttons and report it to sysmouse until we receive a packet from the
touchpad indicating the button has been released. This makes it
possible to use an extended button to resize a window. On Lenovo
laptops, the major buttons are actually reported as extended buttons.
Tested on a Lenovo X1 (3rd gen).
diff --git a/sys/dev/atkbdc/psm.c b/sys/dev/atkbdc/psm.c
index 5703daf..3c3a27c 100644
--- a/sys/dev/atkbdc/psm.c
+++ b/sys/dev/atkbdc/psm.c
@@ -198,6 +198,7 @@ typedef struct synapticsinfo {
struct sysctl_ctx_list sysctl_ctx;
struct sysctl_oid *sysctl_tree;
int directional_scrolls;
+ int two_finger_scroll;
int min_pressure;
int max_pressure;
int max_width;
@@ -336,6 +337,7 @@ struct psm_softc { /* Driver status information */
int lasterr;
int cmdcount;
struct sigio *async; /* Processes waiting for SIGIO */
+ int extended_buttons;
};
static devclass_t psm_devclass;
@@ -2752,7 +2754,15 @@ proc_synaptics(struct psm_softc *sc, packetbuf_t *pb, mousestatus_t *ms,
if (pb-ipacket[5] 0x02)
touchpad_buttons |= MOUSE_BUTTON7DOWN;
} else {
-touchpad_buttons |= MOUSE_BUTTON2DOWN;
+if (pb-ipacket[4] 0x01)
+ touchpad_buttons |= MOUSE_BUTTON1DOWN;
+if (pb-ipacket[5] 0x01)
+ touchpad_buttons |= MOUSE_BUTTON3DOWN;
+if (pb-ipacket[4] 0x02)
+ touchpad_buttons |= MOUSE_BUTTON2DOWN;
+if (pb-ipacket[5] 0x02)
+ touchpad_buttons |= MOUSE_BUTTON4DOWN;
+sc-extended_buttons = touchpad_buttons;
}
/*
@@ -2774,13 +2784,25 @@ proc_synaptics(struct psm_softc *sc, packetbuf_t *pb, mousestatus_t *ms,
mask = (1 maskedbits) - 1;
pb-ipacket[4] = ~(mask);
pb-ipacket[5] = ~(mask);
+ } else if (!sc-syninfo.directional_scrolls) {
+ /*
+ * Keep reporting MOUSE DOWN until we get a new packet
+ * indicating otherwise.
+ */
+ touchpad_buttons |= sc-extended_buttons;
}
}
+ /* Handle ClickPad. */
+ if (sc-synhw.capClickPad
+ ((pb-ipacket[0] ^ pb-ipacket[3]) 0x01))
+ touchpad_buttons |= MOUSE_BUTTON1DOWN;
ms-button = touchpad_buttons | guest_buttons;
- /* Check pressure to detect a real wanted action on the
- * touchpad. */
+ /*
+ * Check pressure to detect a real wanted action on the
+ * touchpad.
+ */
if (*z = sc-syninfo.min_pressure) {
synapticsaction_t *synaction;
int cursor, peer, window;
@@ -2793,7 +2815,7 @@ proc_synaptics(struct psm_softc *sc, packetbuf_t *pb, mousestatus_t *ms,
int weight_current, weight_previous, weight_len_squared;
int div_min, div_max, div_len;
int vscroll_hor_area, vscroll_ver_area;
-
+ int two_finger_scroll;
int len, weight_prev_x, weight_prev_y;
int div_max_x, div_max_y, div_x, div_y;
@@ -2820,6 +2842,7 @@ proc_synaptics(struct psm_softc *sc, packetbuf_t *pb, mousestatus_t *ms,
div_len = sc-syninfo.div_len;
vscroll_hor_area = sc-syninfo.vscroll_hor_area;
vscroll_ver_area = sc-syninfo.vscroll_ver_area;
+ two_finger_scroll = sc-syninfo.two_finger_scroll;
/* Palm detection. */
if (!(
@@ -2980,23 +3003,35 @@ proc_synaptics(struct psm_softc *sc, packetbuf_t *pb, mousestatus_t *ms,
dxp = sc-syninfo.vscroll_min_delta ||
dyp = sc-syninfo.vscroll_min_delta) {
/* Check for horizontal scrolling. */
-if ((vscroll_hor_area 0
+if (!two_finger_scroll
+((vscroll_hor_area 0
synaction-start_y = vscroll_hor_area) ||
(vscroll_hor_area 0
synaction-start_y =
- 6143 + vscroll_hor_area))
+ 6143 + vscroll_hor_area)))
synaction-in_vscroll += 2;
/* Check for vertical scrolling. */
-if ((vscroll_ver_area 0
+if (!two_finger_scroll
+((vscroll_ver_area 0
synaction-start_x = vscroll_ver_area) ||
(vscroll_ver_area 0
Re: mfi timeouts at boot on ASUS Z97 motherboard with LSI 9240-4i
On Wed, Apr 8, 2015 at 1:08 AM, Garrett Cooper yaneurab...@gmail.com wrote: On Apr 8, 2015, at 0:49, Garrett Cooper yaneurab...@gmail.com wrote: On Apr 7, 2015, at 19:35, Konstantin Belousov kostik...@gmail.com wrote: On Tue, Apr 07, 2015 at 12:04:44PM -0700, Garrett Cooper wrote: Hi, I just tried to upgrade my system from a Nehalem style era CPU/motherboard (a W series Xeon/P6T-WS) to a Haswell style CPU/motherboard (an E-series Haswell/Z97 motherboard), and I?ve run into some fun issues with my LSI 9240-4i controller. In particular, it?s timing out because of issues noted similar to here: https://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064404.html . I?ve done the following so far to try and diagnose the issue: - Upgraded the firmware on the card and in the BIOS - Tweaked with the PCI-E settings (2.0/3.0; disabled power savings mode in the BIOS; etc) - Turned off 4GB ?remapping? on the PCM. - Booted USB key fob-based images running: 9.3-RELEASE, 10.1-RELEASE, 10-STABLE, 11-CURRENT - Booted my original drive running 9.3-RELEASE - Booted with hw.mfi.msi=0 set in loader. - Booted with boot -v. One more thing to try, is to put the card into PCIe slot handled by the south bridge instead of the CPU slot. I have two Drake Skinnies card which I cannot use, since all my machines are desktop class, and the only available PCIe 8x+ slots are connected to CPU. I was never able to get a satisfactory explanation why the thing does not like CPU' PCIe. Northbridge, Southbridge, didn’t seem to matter :/… I’ve tried all 3 PCI-E slots to no avail. One thing that I’m thinking might be a problem is the fact that it’s sharing resources between the onboard graphics and the storage controller, and plus the other two slots were supposedly dedicated for storage purposes or some such (NVME, etc). Guess I’ll try neutering the onboard GPU and see what happens... Nope. Still timing out with onboard GPU off… I give up with this motherboard... If your motherboard is not listed in the following lists as suitable for Linux , it may cause problems under Unix like operating systems : http://www.asus.com/Static_WebPage/OS_Compatibility/ http://www.asus.com/websites/global/aboutASUS/OS/Linux1410.pdf http://www.asus.com/Static_WebPage/Server/ Thank you very much . Mehmet Erol Sanliturk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: mfi timeouts at boot on ASUS Z97 motherboard with LSI 9240-4i
On Apr 7, 2015, at 19:35, Konstantin Belousov kostik...@gmail.com wrote: On Tue, Apr 07, 2015 at 12:04:44PM -0700, Garrett Cooper wrote: Hi, I just tried to upgrade my system from a Nehalem style era CPU/motherboard (a W series Xeon/P6T-WS) to a Haswell style CPU/motherboard (an E-series Haswell/Z97 motherboard), and I?ve run into some fun issues with my LSI 9240-4i controller. In particular, it?s timing out because of issues noted similar to here: https://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064404.html . I?ve done the following so far to try and diagnose the issue: - Upgraded the firmware on the card and in the BIOS - Tweaked with the PCI-E settings (2.0/3.0; disabled power savings mode in the BIOS; etc) - Turned off 4GB ?remapping? on the PCM. - Booted USB key fob-based images running: 9.3-RELEASE, 10.1-RELEASE, 10-STABLE, 11-CURRENT - Booted my original drive running 9.3-RELEASE - Booted with hw.mfi.msi=0 set in loader. - Booted with boot -v. One more thing to try, is to put the card into PCIe slot handled by the south bridge instead of the CPU slot. I have two Drake Skinnies card which I cannot use, since all my machines are desktop class, and the only available PCIe 8x+ slots are connected to CPU. I was never able to get a satisfactory explanation why the thing does not like CPU' PCIe. Northbridge, Southbridge, didn’t seem to matter :/… I’ve tried all 3 PCI-E slots to no avail. One thing that I’m thinking might be a problem is the fact that it’s sharing resources between the onboard graphics and the storage controller, and plus the other two slots were supposedly dedicated for storage purposes or some such (NVME, etc). Guess I’ll try neutering the onboard GPU and see what happens... signature.asc Description: Message signed with OpenPGP using GPGMail
Re: mfi timeouts at boot on ASUS Z97 motherboard with LSI 9240-4i
On Apr 7, 2015, at 12:04, Garrett Cooper yaneurab...@gmail.com wrote: Hi, I just tried to upgrade my system from a Nehalem style era CPU/motherboard (a W series Xeon/P6T-WS) to a Haswell style CPU/motherboard (an E-series Haswell/Z97 motherboard), and I’ve run into some fun issues with my LSI 9240-4i controller. In particular, it’s timing out because of issues noted similar to here: https://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064404.html . I’ve done the following so far to try and diagnose the issue: - Upgraded the firmware on the card and in the BIOS - Tweaked with the PCI-E settings (2.0/3.0; disabled power savings mode in the BIOS; etc) - Turned off 4GB “remapping” on the PCM. - Booted USB key fob-based images running: 9.3-RELEASE, 10.1-RELEASE, 10-STABLE, 11-CURRENT - Booted my original drive running 9.3-RELEASE - Booted with hw.mfi.msi=0 set in loader. - Booted with boot -v. Every time I run into MFI send command timeouts that eventually turn into Here’s the message I got (transcribed) with 11-CURRENT with boot -v: mfi0: Drake Skinny port 0xe000-0xe0ff mem 0xdfc6-0x…. on pci2 mfi0: attempting to allocate 1 MSI vectors (1 supported) pci: routing MSI IRQ 264 to local APIC 0 vector 59 mfi0: using IRQ 264 for MSI mfi0: using MSI mfi0: Megaraid SAS driver Ver 4.23 mfi0: Frame 0xfe07f719f280 timed out command 0x101 Error 60 in callback from mfi_send_frame The complete screenshot for that timeout can be found here: https://people.freebsd.org/~ngie/mfi-timeout-boot-verbose.jpg What I haven’t done yet: - Exporting the volume with the old motherboard and importing it with the new motherboard (I need to do some reading before I do this though because I don’t want to toast my data by accident :(…). - Booted either Linux or Windows to make sure the controller works with the motherboard CentOS 7.1 release is no bueno either with similar errors. So it’s most likely a hardware compatibility issue. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: mfi timeouts at boot on ASUS Z97 motherboard with LSI 9240-4i
On Apr 8, 2015, at 0:49, Garrett Cooper yaneurab...@gmail.com wrote: On Apr 7, 2015, at 19:35, Konstantin Belousov kostik...@gmail.com wrote: On Tue, Apr 07, 2015 at 12:04:44PM -0700, Garrett Cooper wrote: Hi, I just tried to upgrade my system from a Nehalem style era CPU/motherboard (a W series Xeon/P6T-WS) to a Haswell style CPU/motherboard (an E-series Haswell/Z97 motherboard), and I?ve run into some fun issues with my LSI 9240-4i controller. In particular, it?s timing out because of issues noted similar to here: https://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064404.html . I?ve done the following so far to try and diagnose the issue: - Upgraded the firmware on the card and in the BIOS - Tweaked with the PCI-E settings (2.0/3.0; disabled power savings mode in the BIOS; etc) - Turned off 4GB ?remapping? on the PCM. - Booted USB key fob-based images running: 9.3-RELEASE, 10.1-RELEASE, 10-STABLE, 11-CURRENT - Booted my original drive running 9.3-RELEASE - Booted with hw.mfi.msi=0 set in loader. - Booted with boot -v. One more thing to try, is to put the card into PCIe slot handled by the south bridge instead of the CPU slot. I have two Drake Skinnies card which I cannot use, since all my machines are desktop class, and the only available PCIe 8x+ slots are connected to CPU. I was never able to get a satisfactory explanation why the thing does not like CPU' PCIe. Northbridge, Southbridge, didn’t seem to matter :/… I’ve tried all 3 PCI-E slots to no avail. One thing that I’m thinking might be a problem is the fact that it’s sharing resources between the onboard graphics and the storage controller, and plus the other two slots were supposedly dedicated for storage purposes or some such (NVME, etc). Guess I’ll try neutering the onboard GPU and see what happens... Nope. Still timing out with onboard GPU off… I give up with this motherboard... signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Early use of log() does not end up in kernel msg buffer
On Monday, April 06, 2015 09:11:21 PM Poul-Henning Kamp wrote:
In message 2033248.eu3rhs8...@ralph.baldwin.cx, John Baldwin writes:
I think phk@ broke this back in 70239. Before that the log() function did
this:
log()
{
/* log to the msg buffer */
kvprintf(fmt, msglogchar, ...);
if (!log_open) {
/* log to console */
kvprintf(fmt, putchar, ...);
}
}
I think your patch is fine unless phk@ (cc'd) has a reason for not wanting to
do this.
The reason was systems not running syslog having slow serial consoles.
To be clear, you didn't turn off printing to the console, you turned off
writing to the msglog.
That is, before your change:
- If syslog wasn't running, the message was sent to the msglog (so that a
subsequently started syslog would see it) and to the console.
- If syslog was running, the message was only sent to the msglog, but not
the console.
After your change:
- If syslog isn't running, the message is only sent to the console.
- If syslog is running, the message is only sent to the msglog.
The direct result is that less data is sent to the msglog. Is the concern
that when syslogd starts up any pre-boot log messages can be sent over the
console a second time by the syslogd process writing to /dev/console?
Note that this does mean that any messages logged before syslogd are lost
and cannot be accessed by any software on the box that wants to do parse
syslogd output, etc. (which is what is probably causing problems for the
OP).
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call For Testers: Synaptics touchpads
On Wednesday 08 April 2015 17:04:41 Oliver Pinter wrote: Is there any special settings / requirements for xorg.conf to enable the palm detection and similar features? No, it's done in the kernel. See sysctl hw.psm. -- Rui Paulo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call For Testers: Synaptics touchpads
On Wed, 2015-04-08 at 09:19 -0700, Rui Paulo wrote: On Wednesday 08 April 2015 09:13:51 Shawn Webb wrote: On Wed, 2015-04-08 at 00:19 -0700, Rui Paulo wrote: Hi, The attached patch adds support for newer touchpad features and implements two finger scrolling. This is such a common feature these days that I think we should enable it by default and disable edge scrolling. I've implemented some detection code to keep edge scrolling enabled when the touchpad has a dedicated area for scrolling. Please test it and report back your experience. To enable synaptics support, you need: hw.psm.synaptics_support=1 in loader.conf. Hey Rui, I'm excited to have this and will test this out this week. Do I need to recompile any ports (namely, the xf86-input-synaptics port) after applying this patch? No, it's all in the kernel. It's not working in the slightest to me. Looking at the patch, you expose additional sysctls. None of those sysctls are visible to me. Is there something I need to do besides apply the patch and recompile my kernel? If not, then the patch doesn't work in the slightest. Thanks, Shawn signature.asc Description: This is a digitally signed message part
Re: Call For Testers: Synaptics touchpads
On Wed, 2015-04-08 at 00:19 -0700, Rui Paulo wrote: Hi, The attached patch adds support for newer touchpad features and implements two finger scrolling. This is such a common feature these days that I think we should enable it by default and disable edge scrolling. I've implemented some detection code to keep edge scrolling enabled when the touchpad has a dedicated area for scrolling. Please test it and report back your experience. To enable synaptics support, you need: hw.psm.synaptics_support=1 in loader.conf. Hey Rui, I'm excited to have this and will test this out this week. Do I need to recompile any ports (namely, the xf86-input-synaptics port) after applying this patch? Thanks, Shawn signature.asc Description: This is a digitally signed message part
Re: Call For Testers: Synaptics touchpads
Is there any special settings / requirements for xorg.conf to enable the palm detection and similar features? On Wed, Apr 8, 2015 at 3:13 PM, Shawn Webb shawn.w...@hardenedbsd.org wrote: On Wed, 2015-04-08 at 00:19 -0700, Rui Paulo wrote: Hi, The attached patch adds support for newer touchpad features and implements two finger scrolling. This is such a common feature these days that I think we should enable it by default and disable edge scrolling. I've implemented some detection code to keep edge scrolling enabled when the touchpad has a dedicated area for scrolling. Please test it and report back your experience. To enable synaptics support, you need: hw.psm.synaptics_support=1 in loader.conf. Hey Rui, I'm excited to have this and will test this out this week. Do I need to recompile any ports (namely, the xf86-input-synaptics port) after applying this patch? Thanks, Shawn ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Nothing can boot anymore - video issues
On Mon, 2015-04-06 at 16:55 -0700, Devin Teske wrote: On Apr 6, 2015, at 1:35 PM, Shawn Webb shawn.w...@hardenedbsd.org wrote: On Mon, 2015-04-06 at 13:59 -0400, Shawn Webb wrote: On Sun, 2015-04-05 at 12:07 -0700, Rui Paulo wrote: On Apr 5, 2015, at 09:11, Shawn Webb shawn.w...@hardenedbsd.org wrote: So I just updated my laptop and desktop to a recent HEAD. Both machines boot using gptzfsboot. The boot spinner shows, then when it's supposed to transition to the Beastie logo screen, the monitor funks out. Booting never finishes. Below is a link to a picture of my laptop. http://imgur.com/l3mLDBX Try reverting the Forth changes. That's all that comes to mind. -- Rui Paulo I'm going through commit-by-commit from April 3rd to March 31st, which will take a big chunk of time. It's really weird that no one else has reported this since even my VirtualBox VMs have this same issue. Thanks, Shawn I've figured out the commit that caused the breakage. Looks like the boot Forth changes are pretty bad. The commit that caused the breakage, as far as I can tell is, r280974. Reverting that and the two commits above that revision regarding sys/boot/forth allowed me to boot again. Now the boot screen looks like this: http://imgur.com/I9SVHfT I can now boot, but as you see, the boot screen's messed up. Why the screen looks that way (no brand and no logo): You were caught in a small window of broken-ness. Window was between: https://svnweb.freebsd.org/base?view=revisionrevision=280933 and https://svnweb.freebsd.org/base?view=revisionrevision=281002 A window of approximately 2 days. As for why the screen got wonky … well… your comp and my comp don’t agree on ANSI sequences. I’ve reverted the offending changes so that we may once-again agree on ANSI codes. ;D It now appears that the problem was specific to HardenedBSD: we had a custom loader_version setting in sys/boot/forth/loader.conf. I'm unsure which commit caused the breakage, but now having a custom loader_version will break booting. Thanks, Shawn signature.asc Description: This is a digitally signed message part
Re: Call For Testers: Synaptics touchpads
On Wednesday 08 April 2015 09:13:51 Shawn Webb wrote: On Wed, 2015-04-08 at 00:19 -0700, Rui Paulo wrote: Hi, The attached patch adds support for newer touchpad features and implements two finger scrolling. This is such a common feature these days that I think we should enable it by default and disable edge scrolling. I've implemented some detection code to keep edge scrolling enabled when the touchpad has a dedicated area for scrolling. Please test it and report back your experience. To enable synaptics support, you need: hw.psm.synaptics_support=1 in loader.conf. Hey Rui, I'm excited to have this and will test this out this week. Do I need to recompile any ports (namely, the xf86-input-synaptics port) after applying this patch? No, it's all in the kernel. -- Rui Paulo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Nothing can boot anymore - video issues
On Apr 8, 2015, at 8:18 AM, Shawn Webb shawn.w...@hardenedbsd.org wrote: On Mon, 2015-04-06 at 16:55 -0700, Devin Teske wrote: On Apr 6, 2015, at 1:35 PM, Shawn Webb shawn.w...@hardenedbsd.org wrote: On Mon, 2015-04-06 at 13:59 -0400, Shawn Webb wrote: On Sun, 2015-04-05 at 12:07 -0700, Rui Paulo wrote: On Apr 5, 2015, at 09:11, Shawn Webb shawn.w...@hardenedbsd.org wrote: So I just updated my laptop and desktop to a recent HEAD. Both machines boot using gptzfsboot. The boot spinner shows, then when it's supposed to transition to the Beastie logo screen, the monitor funks out. Booting never finishes. Below is a link to a picture of my laptop. http://imgur.com/l3mLDBX Try reverting the Forth changes. That's all that comes to mind. -- Rui Paulo I'm going through commit-by-commit from April 3rd to March 31st, which will take a big chunk of time. It's really weird that no one else has reported this since even my VirtualBox VMs have this same issue. Thanks, Shawn I've figured out the commit that caused the breakage. Looks like the boot Forth changes are pretty bad. The commit that caused the breakage, as far as I can tell is, r280974. Reverting that and the two commits above that revision regarding sys/boot/forth allowed me to boot again. Now the boot screen looks like this: http://imgur.com/I9SVHfT I can now boot, but as you see, the boot screen's messed up. Why the screen looks that way (no brand and no logo): You were caught in a small window of broken-ness. Window was between: https://svnweb.freebsd.org/base?view=revisionrevision=280933 and https://svnweb.freebsd.org/base?view=revisionrevision=281002 A window of approximately 2 days. As for why the screen got wonky … well… your comp and my comp don’t agree on ANSI sequences. I’ve reverted the offending changes so that we may once-again agree on ANSI codes. ;D It now appears that the problem was specific to HardenedBSD: we had a custom loader_version setting in sys/boot/forth/loader.conf. I'm unsure which commit caused the breakage, but now having a custom loader_version will break booting. Thanks for narrowing it further. Let me do some additional testing and I’ll report back what I find. — Devin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Dual booting FreeBSD and Win95
No, this isn't a late April Fools joke. :( I find myself in a situation where I need to integrate my employer's manufacturing process with a third-party OEM's process. My employer's hardware tests are all FreeBSD-based while the OEM is Windows 95 based. I need to come up with a way to integrate them together. We're looking at dual-booting FreeBSD and Win95. We're thinking of booting into Win95, the OEM can do their thing, switch to booting FreeBSD, run our tests and produce a .csv file with the results, and then boot back into Win95 for them to finish up. Ideally we would like to switch the boot slice without human interaction. I've been playing around with trying to set one only slice as active to make the loader boot it, but it appears that doesn't actually work. boot0cfg would cover half of the use case (switching from FreeBSD back to Win95), but I'm not sure how I could do the original switch from Win95 to FreeBSD. We've discussed just switching hard drives, but we really want to shoot for a 100% automated process. Anybody have any ideas? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Dual booting FreeBSD and Win95
On Wed, 8 Apr 2015, Ryan Stone wrote: No, this isn't a late April Fools joke. :( We've discussed just switching hard drives, but we really want to shoot for a 100% automated process. Anybody have any ideas? I guess due to hardware interfacing virtualization is not an option? I've seen some testing equipment running Win98 only because it allows direct access to serial ports, not exposing some kind of virtual device driver. //arcin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Dual booting FreeBSD and Win95
Hi, You can just write a little command line win32 program that writes to the boot blocks. it's win95; unless your BIOS somehow is blocking things you should be able to set the same area that boot0cfg does to tell the bootloader about what to do. -adrian On 8 April 2015 at 12:30, Ryan Stone ryst...@gmail.com wrote: No, this isn't a late April Fools joke. :( I find myself in a situation where I need to integrate my employer's manufacturing process with a third-party OEM's process. My employer's hardware tests are all FreeBSD-based while the OEM is Windows 95 based. I need to come up with a way to integrate them together. We're looking at dual-booting FreeBSD and Win95. We're thinking of booting into Win95, the OEM can do their thing, switch to booting FreeBSD, run our tests and produce a .csv file with the results, and then boot back into Win95 for them to finish up. Ideally we would like to switch the boot slice without human interaction. I've been playing around with trying to set one only slice as active to make the loader boot it, but it appears that doesn't actually work. boot0cfg would cover half of the use case (switching from FreeBSD back to Win95), but I'm not sure how I could do the original switch from Win95 to FreeBSD. We've discussed just switching hard drives, but we really want to shoot for a 100% automated process. Anybody have any ideas? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Dual booting FreeBSD and Win95
On 08 Apr 2015, at 21:30, Ryan Stone ryst...@gmail.com wrote: No, this isn't a late April Fools joke. :( I find myself in a situation where I need to integrate my employer's manufacturing process with a third-party OEM's process. My employer's hardware tests are all FreeBSD-based while the OEM is Windows 95 based. I need to come up with a way to integrate them together. We're looking at dual-booting FreeBSD and Win95. We're thinking of booting into Win95, the OEM can do their thing, switch to booting FreeBSD, run our tests and produce a .csv file with the results, and then boot back into Win95 for them to finish up. Ideally we would like to switch the boot slice without human interaction. I've been playing around with trying to set one only slice as active to make the loader boot it, but it appears that doesn't actually work. boot0cfg would cover half of the use case (switching from FreeBSD back to Win95), but I'm not sure how I could do the original switch from Win95 to FreeBSD. We've discussed just switching hard drives, but we really want to shoot for a 100% automated process. Anybody have any ideas? What are you testing? The hardware this is running on? Your tests as well as the OEM's? If not I would suggest booting FreeBSD and running win95 in qemu. A long time ago I dual booted BSD and DOS (or maybe it was OS/2 and Linux, it's been quite a while) and I did so by using two primary partitions, only marking one of them active/bootable at a time. You might be able to do the same in an automated way on windows and FreeBSD to alternate between the OSes. - Michael ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Dual booting FreeBSD and Win95
As dirty hack, try to save two state of MBR, one when FreeBSD selected (MBR.FBSD) , and one when Win95 selected (MBR.W95). When the windows booted up properly, then write the MBR.FBSD to the disc, on the same schema do the reverse on freebsd with dd. http://www.fccps.cz/download/adv/frr/wipembr.html Or just do what Adrian has said, flip the active bits with a custom tool. On Wed, Apr 8, 2015 at 9:30 PM, Ryan Stone ryst...@gmail.com wrote: No, this isn't a late April Fools joke. :( I find myself in a situation where I need to integrate my employer's manufacturing process with a third-party OEM's process. My employer's hardware tests are all FreeBSD-based while the OEM is Windows 95 based. I need to come up with a way to integrate them together. We're looking at dual-booting FreeBSD and Win95. We're thinking of booting into Win95, the OEM can do their thing, switch to booting FreeBSD, run our tests and produce a .csv file with the results, and then boot back into Win95 for them to finish up. Ideally we would like to switch the boot slice without human interaction. I've been playing around with trying to set one only slice as active to make the loader boot it, but it appears that doesn't actually work. boot0cfg would cover half of the use case (switching from FreeBSD back to Win95), but I'm not sure how I could do the original switch from Win95 to FreeBSD. We've discussed just switching hard drives, but we really want to shoot for a 100% automated process. Anybody have any ideas? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Dual booting FreeBSD and Win95
On Wed, Apr 08, 2015 at 03:30:41PM -0400, Ryan Stone wrote: No, this isn't a late April Fools joke. :( I find myself in a situation where I need to integrate my employer's manufacturing process with a third-party OEM's process. My employer's hardware tests are all FreeBSD-based while the OEM is Windows 95 based. I need to come up with a way to integrate them together. We're looking at dual-booting FreeBSD and Win95. We're thinking of booting into Win95, the OEM can do their thing, switch to booting FreeBSD, run our tests and produce a .csv file with the results, and then boot back into Win95 for them to finish up. Ideally we would like to switch the boot slice without human interaction. I've been playing around with trying to set one only slice as active to make the loader boot it, but it appears that doesn't actually work. boot0cfg would cover half of the use case (switching from FreeBSD back to Win95), but I'm not sure how I could do the original switch from Win95 to FreeBSD. We've discussed just switching hard drives, but we really want to shoot for a 100% automated process. Anybody have any ideas? If hardware recognised by Win95 do next: 1. create MBR patition table. first patition dedicate to Win95. next partiton to freebsd 2. install Win95 3. Install FreeBSD with FreeBSD boot manager. 4. (optional) create windows95 boot.ini for fail back load FreeBSD ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Dual booting FreeBSD and Win95
On Wed, 8 Apr 2015, Slawa Olhovchenkov wrote: On Wed, Apr 08, 2015 at 03:30:41PM -0400, Ryan Stone wrote: 4. (optional) create windows95 boot.ini for fail back load FreeBSD http://support.microsoft.com/en-us/kb/157992 I think boot.ini comes with ntldr, and Win95/98 started DOS-like.. //Marcin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call For Testers: Synaptics touchpads
On Wed, April 8, 2015 09:19, Rui Paulo wrote: Hi, The attached patch adds support for newer touchpad features and implements two finger scrolling. This is such a common feature these days that I think we should enable it by default and disable edge scrolling. I've implemented some detection code to keep edge scrolling enabled when the touchpad has a dedicated area for scrolling. Please test it and report back your experience. To enable synaptics support, you need: hw.psm.synaptics_support=1 in loader.conf. Thanks, -- Rui Paulo___ Hi, Tested on my Acer E3-112 with a TouchPad. It works, thank you! I have been missing two-finger scrolling, it was quite awkward using edge scrolling IMHO. It does feel like it sometimes gets stuck in scrolling mode. When trying to move the pointer just after having scrolled, it scrolls even using just one finger. Three-finger tapping also works. (Generating a button 3 event) Clicking on the pad (pushing it down until it clicks sends button events for both button 1 and 2. (Which is seems to sometimes be interpreted as button 3...) The biggest improvement though; before it would get totally crazy at random intervals with the pointer moving all over the screen and clicking at random points. Quite annoying... This patch seems to have eliminated that! Also, does it support horizontal scrolling? Jakob Alvermark ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call For Testers: Synaptics touchpads
On Wed, Apr 08, 2015 at 01:32:06PM -0400, Shawn Webb wrote: On Wed, 2015-04-08 at 09:19 -0700, Rui Paulo wrote: On Wednesday 08 April 2015 09:13:51 Shawn Webb wrote: On Wed, 2015-04-08 at 00:19 -0700, Rui Paulo wrote: Hi, The attached patch adds support for newer touchpad features and implements two finger scrolling. This is such a common feature these days that I think we should enable it by default and disable edge scrolling. I've implemented some detection code to keep edge scrolling enabled when the touchpad has a dedicated area for scrolling. Please test it and report back your experience. To enable synaptics support, you need: hw.psm.synaptics_support=1 Did you add this to loader.conf? It's not working in the slightest to me. Looking at the patch, you expose additional sysctls. None of those sysctls are visible to me. Is there something I need to do besides apply the patch and recompile my kernel? If not, then the patch doesn't work in the slightest. Does grep -i synaptics /var/run/dmesg.boot show anything? pgpTFD8vuVLex.pgp Description: PGP signature
Re: Dual booting FreeBSD and Win95
On Wed, Apr 08, 2015 at 08:09:42PM +, Marcin Cieslak wrote: On Wed, 8 Apr 2015, Slawa Olhovchenkov wrote: On Wed, Apr 08, 2015 at 03:30:41PM -0400, Ryan Stone wrote: 4. (optional) create windows95 boot.ini for fail back load FreeBSD http://support.microsoft.com/en-us/kb/157992 I think boot.ini comes with ntldr, and Win95/98 started DOS-like.. Oh, yes. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call For Testers: Synaptics touchpads
On Apr 8, 2015 4:27 PM, Lars Engels lars.eng...@0x20.net wrote: On Wed, Apr 08, 2015 at 01:32:06PM -0400, Shawn Webb wrote: On Wed, 2015-04-08 at 09:19 -0700, Rui Paulo wrote: On Wednesday 08 April 2015 09:13:51 Shawn Webb wrote: On Wed, 2015-04-08 at 00:19 -0700, Rui Paulo wrote: Hi, The attached patch adds support for newer touchpad features and implements two finger scrolling. This is such a common feature these days that I think we should enable it by default and disable edge scrolling. I've implemented some detection code to keep edge scrolling enabled when the touchpad has a dedicated area for scrolling. Please test it and report back your experience. To enable synaptics support, you need: hw.psm.synaptics_support=1 Did you add this to loader.conf? It's not working in the slightest to me. Looking at the patch, you expose additional sysctls. None of those sysctls are visible to me. Is there something I need to do besides apply the patch and recompile my kernel? If not, then the patch doesn't work in the slightest. Does grep -i synaptics /var/run/dmesg.boot show anything? I ran through some tests, it looks like my synaptics touchpad isn't supported. I'll have to add support for the device itself before his patch is useful. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
