Re: i-buddie
On 09-Oct-2002 Guido Van Hoecke wrote: > i4o beke wrote: >> Hi Guido. I've seen your question on freebsd-mobile, without answer. >> I'd like to buy i-buddie, 3c or 4. So your problems with setup are >> really interesting for me. >> Is your sis network card working? Is it possible to >> run XWin on i-buddie? Thank you for your answer. > > I am afraid I have had no luck with freebsd. My sis900 network card is > recognized but fails with a 'MII without any PHY!', and 3 more devices > are showing up as unknown: That I can't help you with, sorry. > pci0 2.7 is a sis7012 audio driver Sound isn't configured in teh default kernel. Try doing a 'kldload snd_driver' and seeing if pcm0 attaches to it. > pci0 5.0 is a conexant 56k modem Probably a win modem. There are some ports that might work with this. > pci0 7.0 ia a VIA OHCI Compliant IEEE1394 host controller This is firewire. Only supported in -current. > Further more, XF86 as available in freebsd 4.6.2-RELEASE #0 does not > recognize my lcd panel, so I can't run a desktop environment. Sometimes X has to be futzed with to work right. I had to add bogus horizontal and vertical refresh rates for X to work right on my laptop. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: i-buddie
i4o beke wrote: > Hi Guido. I've seen your question on freebsd-mobile, without answer. > I'd like to buy i-buddie, 3c or 4. So your problems with setup are > really interesting for me. > Is your sis network card working? Is it possible to > run XWin on i-buddie? Thank you for your answer. I am afraid I have had no luck with freebsd. My sis900 network card is recognized but fails with a 'MII without any PHY!', and 3 more devices are showing up as unknown: pci0 2.7 is a sis7012 audio driver pci0 5.0 is a conexant 56k modem pci0 7.0 ia a VIA OHCI Compliant IEEE1394 host controller Further more, XF86 as available in freebsd 4.6.2-RELEASE #0 does not recognize my lcd panel, so I can't run a desktop environment. I have not yet posted about the X problem, I wanted to have the sis900 network problem resolved first. FYI, I've installed mandrake 8.2 without a single hickup: all hardware recognized and configured properly in a very neat and smooth installation. Other distros which I've tried with less success are Red Hat 7.3, and Debian 3.0 I do like the iBuddy though! -- Guido Van Hoecke <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: i-Buddie 4: Synaptics touch pad FreeBSD support?
Guido Van Hoecke <[EMAIL PROTECTED]> writes earlier: > I specifically would like support for the Synaptics touch pad, but did > not find much in the FreeBSD documentation, nor in the ports collection. and now: > Just for the record: the touchpad acts as a normal ps2 mouse and needs > no special driver at all! > > (Thanx 2 hacker Brandon D. Valentine for the info) > > Hail FreeBSD! Don't forget the better record for the info you've learned. Please do your pay-back duty so future Synaptics and "i-Buddie 4" users can't say they did not find much in the FreeBSD documentation. You can file a quick PR in category "doc" at http://www.freebsd.org/send-pr.html (or even a slow PR with patches to the documentation sources). P.S. As I look into things a bit, I have to warn you that your PR might get rejected because the hardware document seems to totally ignore pointers and video cards (but not keyboards)! Presumably, someone wanted to leave those to XFree86 documentation, but as many people run "moused" without an X server and as your experience shows, the documentation should at least have a pointer section. Please submit your PR anyway and I'll submit another, suggesting a pointer section and also a referral to the XFree86 documentation. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: i-Buddie 4: Synaptics touch pad FreeBSD support?
> I specifically would like support for the Synaptics touch pad, but did > not find much in the FreeBSD documentation, nor in the ports collection. > > So I went to see at http://www.synaptics.com/support/downloads.cfm and > found a pointer to a linux 'tpconfig' touch pad driver available at > http://compass.com/synaptics/ which has not yet been ported to FreeBSD. Just for the record: the touchpad acts as a normal ps2 mouse and needs no special driver at all! (Thanx 2 hacker Brandon D. Valentine for the info) Hail FreeBSD! Guido. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: i-Buddie 4: Synaptics touch pad FreeBSD support?
> So I went to see at http://www.synaptics.com/support/downloads.cfm and > found a pointer to a linux 'tpconfig' touch pad driver available at > http://compass.com/synaptics/ which has not yet been ported to FreeBSD. If it's a driver in the sense of some kernel code then it's going to need a lot of work. > "Makefile", line 254: Need an operator But this is just because you need to use gmake instead of make. -- Richard To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
i-Buddie 4: Synaptics touch pad FreeBSD support?
I am experimenting with FreeBSD to be prepared when my new i-Buddie 4
arrives. (Specs at http://desknote.biz/sub/spec-i-buddie4.htm). I wonder
whether anybody has any experience with this new 'desknote' computer.
I specifically would like support for the Synaptics touch pad, but did
not find much in the FreeBSD documentation, nor in the ports collection.
So I went to see at http://www.synaptics.com/support/downloads.cfm and
found a pointer to a linux 'tpconfig' touch pad driver available at
http://compass.com/synaptics/ which has not yet been ported to FreeBSD.
So I tried to use this on my little FreeBSD testbox:
~/tpconfig-3.1.3 # ./configure
loading cache ./config.cache
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... (cached) gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking for fcntl.h... (cached) yes
checking for unistd.h... (cached) yes
updating cache ./config.cache
creating ./config.status
creating Makefile
~/tpconfig-3.1.3 # ./make
"Makefile", line 254: Need an operator
make: fatal errors encountered -- cannot continue
~/tpconfig-3.1.3 #
I used vim to add line numbers in the Makefile and copypasted the result:
1 # Generated automatically from Makefile.in by configure.
2 # Makefile.in generated automatically by automake 1.4 from Makefile.am
3
4 # Copyright (C) 1994, 1995-8, 1999 Free Software Foundation, Inc.
5 # This Makefile.in is free software; the Free Software Foundation
6 # gives unlimited permission to copy and/or distribute it,
7 # with or without modifications, as long as this notice is preserved.
8
9 # This program is distributed in the hope that it will be useful,
10 # but WITHOUT ANY WARRANTY, to the extent permitted by law; without
11 # even the implied warranty of MERCHANTABILITY or FITNESS FOR A
12 # PARTICULAR PURPOSE.
13
14 # Source: $Id: Makefile.am,v 1.2 2000/11/05 21:50:25 cph Exp $
15
16
17 SHELL = /bin/sh
18
19 srcdir = .
20 top_srcdir = .
21 prefix = /usr/local
22 exec_prefix = ${prefix}
23
24 bindir = ${exec_prefix}/bin
25 sbindir = ${exec_prefix}/sbin
26 libexecdir = ${exec_prefix}/libexec
27 datadir = ${prefix}/share
28 sysconfdir = ${prefix}/etc
29 sharedstatedir = ${prefix}/com
30 localstatedir = ${prefix}/var
31 libdir = ${exec_prefix}/lib
32 infodir = ${prefix}/info
33 mandir = ${prefix}/man
34 includedir = ${prefix}/include
35 oldincludedir = /usr/include
36
37 DESTDIR =
38
39 pkgdatadir = $(datadir)/tpconfig
40 pkglibdir = $(libdir)/tpconfig
41 pkgincludedir = $(includedir)/tpconfig
42
43 top_builddir = .
44
45 ACLOCAL = aclocal
46 AUTOCONF = autoconf
47 AUTOMAKE = automake
48 AUTOHEADER = autoheader
49
50 INSTALL = /usr/bin/install -c
51 INSTALL_PROGRAM = ${INSTALL} $(AM_INSTALL_PROGRAM_FLAGS)
52 INSTALL_DATA = ${INSTALL} -m 644
53 INSTALL_SCRIPT = ${INSTALL_PROGRAM}
54 transform = s,x,x,
55
56 NORMAL_INSTALL = :
57 PRE_INSTALL = :
58 POST_INSTALL = :
59 NORMAL_UNINSTALL = :
60 PRE_UNINSTALL = :
61 POST_UNINSTALL = :
62 CC = gcc
63 MAKEINFO = makeinfo
64 PACKAGE = tpconfig
65 VERSION = 3.1.3
66
67 AUTOMAKE_OPTIONS = "VERSION=1.2"
68 bin_PROGRAMS = tpconfig
69 tpconfig_SOURCES = tpconfig.c synaptics.c ALPS.c utils.c
70 MAINTAINERCLEANFILES = Makefile.in configure aclocal.m4
install-sh
missing mkinstalldirs COPYING INSTALL
71
72 # don't know why this is being omitted...
73 EXTRA_DIST = configure
74 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
75 mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
76 CONFIG_CLEAN_FILES =
77 PROGRAMS = $(bin_PROGRAMS)
78
79
80 DEFS = -DPACKAGE=\"tpconfig\" -DVERSION=\"3.1.3\" -DHAVE_FCNTL_H=1
-DHAVE_UNISTD_H=1 -I. -I$(srcdir)
81 CPPFLAGS =
82 LDFLAGS =
83 LIBS =
84 tpconfig_OBJECTS = tpconfig.o synaptics.o ALPS.o utils.o
85 tpconfig_LDADD = $(LDADD)
86 tpconfig_DEPENDENCIES =
87 tpconfig_LDFLAGS =
88 CFLAGS = -g -O2
89 COMPILE = $(CC) $(DEFS) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS)
