Date: Sat, 16 Sep 2000 20:57:26 +0000 From: rob <europax@home.com> To: Sean O'Connell <sean@stat.Duke.EDU> Cc: FreeBSD mobile <freebsd-mobile@FreeBSD.ORG>, FreeBSD stable <freebsd-stable@FreeBSD.ORG>, cg@FreeBSD.ORG, nsyaer@FreeBSD.ORG Subject: Re: Follow-up on ACER 600TER vs FreeBSD 4.1-S Message-ID: <39C3DEB5.E34CF830@home.com> References: <20000916202106.A70518@stat.Duke.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
I guess ignorance is bliss. I've been using my 602TER with few problems
for a month now. As far as I know, the 602 just has faster processor
than the 600. I am running 4_stable. I did have to get the OSS sound
driver. I spent some time trying to port the Linux Synaptics pad config
utility with no luck. Probably someone who actually knew what he was
doing would be more successful. Rob.
Sean O'Connell wrote:
>
> Hi All-
>
> A few weeks ago I had posted a missive to the list about an
> ACER 600TER that I was setting up for a faculty member. The
> machine in question was locking up solid on resume from suspend
> (both zzz and bios fn key suspend). The machine would lock up
> solid regardless of whether I suspended in X or on a virtual
> terminal. With the changes listed below, the notebook (pretty
> nice at around 5 lbs with 13.3 XGA TFT and onboard enet and a
> cdrom-writer--not tested as anythign other than cdrom).
>
> This turned out to be locking up for 3 (count'em three) different
> reasons. It still will lock up on resume for X if I suspend before
> a user logs in on xdm ... od, eh? And I am not sure why the machine
> doesn't seem to like the CTRL+ALT+Fn sequence ...
>
> 1) The onboard "Intel Pro 10/100B/100+ Ethernet" would lock up. This
> required me to apply the patches in PR 18756. I would also like to
> vote for this to make it into 4.1.1 ... I am cc'ing -STABLE on this
> to voice my vote :)
>
> 2) The onboard soundchip "ESS Solo-1 (unknown vendor)" would lock up
> on resume. I fixed this by the rather cheesy fix that came to me
> in a moment of inspired lunacy ... simply adding a resume/suspend
> DEVMETHOD entry. ... I am cc'ing Cameron and Nick on this!
>
> *** solo.c.orig Tue Sep 12 23:05:44 2000
> --- solo.c Tue Sep 12 23:05:42 2000
> ***************
> *** 975,978 ****
> --- 975,980 ----
> DEVMETHOD(device_probe, ess_probe),
> DEVMETHOD(device_attach, ess_attach),
> + DEVMETHOD(device_resume, bus_generic_resume),
> + DEVMETHOD(device_suspend, bus_generic_suspend),
>
> { 0, 0 }
>
> 3) The machine has the dreaded the ATI Rage Mobility chipset. I had
> to move to XFree86-4.0.1 with the mouse patch (which still has yet
> to make it into the FreeBSD port ... sigh!) below to fix toggling in
> and out of X and virtual terminals with moused.
>
> --- programs/Xserver/hw/xfree86/input/mouse/mouse.c.orig Sun Jul 23 17:50:10 2000
> +++ programs/Xserver/hw/xfree86/input/mouse/mouse.c Sun Jul 23 17:54:22 2000
> @@ -692,10 +692,15 @@
> pMse->protocolID = protocolID;
> }
> }
> +#ifndef __FreeBSD__
> memcpy(pMse->protoPara, proto[pMse->protocolID], sizeof(pMse->protoPara));
> +#endif
> if (automatic) {
>
> if (name) {
> +#ifdef __FreeBSD__
> + memcpy(pMse->protoPara, proto[pMse->protocolID], sizeof(pMse->protoPara));
> +#endif
> /* Possible protoPara overrides from SetupAuto. */
> for (i = 0; i < sizeof(pMse->protoPara); i++)
> if (protoPara[i] != -1)
> --- programs/Xserver/hw/xfree86/os-support/bsd/bsd_mouse.c.orig Sat Feb 12 22:45:41 2000
> +++ programs/Xserver/hw/xfree86/os-support/bsd/bsd_mouse.c Sun Jul 23 17:50:10 2000
> @@ -165,7 +165,11 @@
> mode.rate = rate > 0 ? rate : -1;
> mode.resolution = res > 0 ? res : -1;
> mode.accelfactor = -1;
> +#ifdef __FreeBSD__
> + mode.level = 1;
> +#else
> mode.level = -1;
> +#endif
> ioctl(pInfo->fd, MOUSE_SETMODE, &mode);
> }
> #endif
>
> --
> 1--------01---------01--------01--------01--------01--------01--------0
> Sean O'Connell sean@stat.Duke.EDU
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-mobile" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39C3DEB5.E34CF830>