Re: problems with hal in freebsd 7.2 i386

2009-09-30 Thread chrisa
 I had similar troubles with hal.

 The easiest solutions is to get rid of hal. Deinstall it. The xorg-package
 you can compile without hal (use make configure and uncheck hal) and it
 will work.

 Cheers
 herb langhans

Thank you.

I discovered that compiling all ports on the relevant machine made it
compile and start. Isn't it odd that the ones compiled on a slightly
different i386 machine didn't? Anyway, the mouse still doesn't work in X,
and from what I'm hearing, it's possible to get the mouse to work in X
without it, so I am going to get rid of hal.

By the way, any ideas on why the mouse input mightn't work in X? It's a
usb mouse, but moused in text mode works with it.

Cheers.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: problems with hal in freebsd 7.2 i386

2009-09-30 Thread chrisa
 On Wed, 30 Sep 2009, chr...@uvic.ca wrote:

 I discovered that compiling all ports on the relevant machine made it
 compile and start. Isn't it odd that the ones compiled on a slightly
 different i386 machine didn't?

 Not really.  There are lots of ways for two slightly different
 machines to be really different.

Fair enough. This makes me wonder, though, how the packages downloaded
from the ftp server can be run without problems on most machines. What is
the difference between the machine compiling those for everyone to use and
me compiling my own for another of my machines to use? Is there something
you have to do to make sure they're compatible?

 Anyway, the mouse still doesn't work in X, and from what I'm hearing,
 it's possible to get the mouse to work in X without it, so I am going
 to get rid of hal.

 Or you could fix your configuration.

I'd love to.

 By the way, any ideas on why the mouse input mightn't work in X? It's a
 usb mouse, but moused in text mode works with it.

 Your xorg.conf probably has outdated options in it.  But it's hard to
 tell without seeing it.

Actually, I don't have one at all. I'm letting Xorg autodetect everything.
Evidently it's not autodetecting the mouse. I'm thinking it's time to try
manual configuration.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: problems with hal in freebsd 7.2 i386

2009-09-30 Thread chrisa
 My systems work well with hal. I find overall setup to be faster and
 smoother(at this point in time) with hal enabled although there is much
 adversity to it on this list.

 Do you have xf86-input-mouse installed?

I do have it installed. I'm going to try manual configuration to see if I
can make it work.

By the way, you find it faster and smoother with hal enabled? I recall
reading an earlier thread about hal where some people found everything
slower and less responsive. Interesting.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: problems with hal in freebsd 7.2 i386

2009-09-30 Thread chrisa
 On Wed, 30 Sep 2009, chr...@uvic.ca wrote:

 My systems work well with hal. I find overall setup to be faster and
 smoother(at this point in time) with hal enabled although there is much
 adversity to it on this list.

 Do you have xf86-input-mouse installed?

 I do have it installed. I'm going to try manual configuration to see if
 I
 can make it work.

 If you can tell what graphics card you have, no doubt someone can
 provide a sample.  I can come up with ones for ATI and Intel.

It's a Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or something.
Built-in to the motherboard. That's what Xorg autodetects, anyway, and it
starts up and shows blackbox.

I ran Xorg -configure and started it with the result xorg.conf.new, and
that time the screen stayed black throughout. Odd.


 By the way, you find it faster and smoother with hal enabled? I recall
 reading an earlier thread about hal where some people found everything
 slower and less responsive. Interesting.

 It turns out that hal plus a disable hal option makes things not work.
 The opposite is probably also true.

Interesting.

Anyhow, I looked at my Xorg.0.log. I noticed a line saying it can't find
any input devices, and relies upon hal to find them. Then I ran a ps -ax
and found that hal isn't running, even though it should be, being set to
start in rc.conf, along with dbus. So I started it, the startup script
appeared to work, but hald still isn't running. Then I started dbus first,
then hald, and they were both running, restarted X, and suddenly it works.

I swear both were running last night when the mouse and keyboard input
didn't work. They are, after all, set to start up at boot time. Also, the
most recent Xorg.0.log contains the lines:

(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable
AllowEmptyInput.

even though the mouse and keyboard both work now. To make sure that it was
the most recent log file, I deleted all the Xorg logs, restarted it, and
read the most recent one. And it still contains those lines with the
working mouse and keyboard.

Thanks, all, for your help. Now I only have TWO problems left!

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: problems with hal in freebsd 7.2 i386

2009-09-30 Thread chrisa
 Add the following to your X11 config and see what you come up with.

 Section ServerFlags
  option  AutoAddDevicesoff
  option  AllowEmptyInput   off
 EndSection

 Best regards

All right, I did that. Created a new xorg.conf since it's working with the
autoconfig now. The mouse and keyboard still work, and Xorg.0.log follows.


X.Org X Server 1.6.1
Release Date: 2009-4-14
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 7.2-RELEASE-p3 i386
Current Operating System: FreeBSD nimue.gv.shawcable.net 7.2-RELEASE-p3
FreeBSD 7.2-RELEASE-p3 #0: Tue Sep 29 12:51:56 PDT 2009
chr...@nimue.gv.shawcable.net:/usr/obj/usr/src/sys/NODEBUG i386
Build Date: 29 September 2009  09:08:23PM

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Wed Sep 30 14:56:25 2009
(==) Using config file: /usr/local/etc/X11/xorg.conf
(==) No Layout section.  Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |--Screen Default Screen Section (0)
(**) |   |--Monitor default monitor
(==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
(**) Option AllowEmptyInput off
(**) Option AutoAddDevices off
(**) Not automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
/usr/local/lib/X11/fonts/misc/,
/usr/local/lib/X11/fonts/TTF/,
/usr/local/lib/X11/fonts/OTF,
/usr/local/lib/X11/fonts/Type1/,
/usr/local/lib/X11/fonts/100dpi/,
/usr/local/lib/X11/fonts/75dpi/,
built-ins
(==) ModulePath set to /usr/local/lib/xorg/modules
(==) |--Input Device default pointer
(==) |--Input Device default keyboard
(==) No Layout section. Using the default mouse configuration.
(==) No Layout section. Using the default keyboard configuration.
(II) Loader magic: 0x6a0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on freebsd
(--) Using syscons driver with X support (version 2.0)
(--) using VT number 9

(--) PCI:*(0...@1:0:0) Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP
or 662/761Gx PCIE VGA Display Adapter rev 0, Mem @ 0xe000/134217728,
0xec00/131072, I/O @ 0xd000/128, BIOS @ 0x/65536
(II) System resource ranges:
[0] -1  0   0x000f - 0x000f (0x1) MX[B]
[1] -1  0   0x000c - 0x000e (0x3) MX[B]
[2] -1  0   0x - 0x0009 (0xa) MX[B]
[3] -1  0   0x - 0x (0x1) IX[B]
[4] -1  0   0x - 0x00ff (0x100) IX[B]
(II) LoadModule: extmod
(II) Loading /usr/local/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor=X.Org Foundation
compiled for 1.6.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: dbe
(II) Loading /usr/local/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor=X.Org Foundation
compiled for 1.6.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: glx
(II) Loading /usr/local/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor=X.Org Foundation
compiled for 1.6.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX disabled
(II) Loading extension GLX
(II) LoadModule: record
(II) Loading /usr/local/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor=X.Org Foundation
compiled for 1.6.1, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: dri
(II) Loading /usr/local/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor=X.Org Foundation
compiled for 1.6.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: dri2
(II) Loading /usr/local/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor=X.Org Foundation
compiled for 1.6.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(==) Matched sis for the 

Re: problems with hal in freebsd 7.2 i386

2009-09-30 Thread chrisa
 On Wed, 30 Sep 2009, chr...@uvic.ca wrote:

 Add the following to your X11 config and see what you come up with.

 Section ServerFlags
  option  AutoAddDevicesoff
  option  AllowEmptyInput   off
 EndSection

 Best regards

 All right, I did that.

 What are you trying to fix with those entries?

Nothing. I was just doing it to see what happens.


 Created a new xorg.conf since it's working with the autoconfig now.

 And what is in it?

Only this:

Section ServerFlags
option  AutoAddDevicesoff
option  AllowEmptyInput   off
EndSection

and nothing else.


 The mouse and keyboard still work, and Xorg.0.log follows.

 (EE) config/hal: NewInputDeviceRequest failed (8)
 (II) config/hal: Adding input device AT Keyboard
 (EE) config/hal: NewInputDeviceRequest failed (8)

 Well, that's broken.  Look, there are basically two ways to configure
 keyboard and mouse for xorg.  There's the old way, where you have
 InputDevice entries for them in xorg.conf.

 Then there's the new way, where you run hal and let it handle the
 keyboard and mouse for xorg.  No InputDevice sections are needed.  For
 example, here is my xorg.conf from the Acer Aspire One.  Note the lack
 of InputDevice sections and those magic ServerFlags options.

It does indeed appear broken. The keyboard and mouse still work, though,
which doesn't make any sense to me. I don't have any InputDevice sections,
as you can see, so if hal isn't configuring the keyboard and mouse, what
is?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


problems with hal in freebsd 7.2 i386

2009-09-29 Thread chrisa
I have several related problems with hald on 7.2 i386. First, on one
machine (FreeBSD 7.2-RELEASE-p2), hald will not start at startup, nor by
executing the startup script /usr/local/etc/rc.d/hald start. It doesn't
exit with any error code: it simply produces no output at all, and ps -ax
| grep hal shows that it didn't start. Incidentally, the dbus and cupsd
scripts in the same directory also do nothing.

On the other machine, however (FreeBSD 7.2-RELEASE), hald doesn't *build*.
It errors out with:

/usr/local/lib/libpolkit.so: undefined reference to `strn...@fbsd_1.1'
gmake[4]: *** [hald] Error 1
gmake[4]: Leaving directory `/usr/ports/sysutils/hal/work/hal-0.5.11/hald'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory `/usr/ports/sysutils/hal/work/hal-0.5.11/hald'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/usr/ports/sysutils/hal/work/hal-0.5.11/hald'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/sysutils/hal/work/hal-0.5.11'
gmake: *** [all] Error 2
*** Error code 1

Stop in /usr/ports/sysutils/hal.
*** Error code 1

Stop in /usr/ports/sysutils/hal.

This machine was a new install from the 7.2 i386 CD, so to save time I
used packages that had already been built on the first machine. All of
these packages were built within a day of each other, from a previously
updated ports tree with all previously installed packages removed.

Xorg and hald and dbus and everything related installed just fine, and
Xorg works, except that the mouse doesn't work, which I suspect is caused
by hald not working. On this machine, the hald that was compiled on the
first machine won't start, this time giving an error:

r...@nimue /usr/local/etc/rc.d
# ./hald start
Starting hald.

r...@nimue
/usr/local/etc/rc.d
# /libexec/ld-elf.so.1: /lib/libc.so.7: version FBSD_1.1 required by
/usr/local/lib/libpolkit.so.2 not found

Any thoughts?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Running X without a videocard

2008-11-19 Thread chrisa
 I am running FBSD-stable 6.0 on some Sun Netra X1's so it is sparc64.
 There is no video card on these puppies.  But I seem to recall that we
 ran
 solaris X using WinAXE or VNC or something like that

 for fast network (LAN)


 telnet/rlogin (better not ssh)

 export DISPLAY=IP-of-your-display:0
 then start X apps


 make sure to allow on your local display connecting X program -
 man xhost


 for lower speed connection

 ssh -C -X yournetra

 then run X apps


 for lowest speed connection run VNC.


 if your local display run windoze you probably have only the last choice.

 i don't know if they are working X11 servers for windows.

There are, in fact, in cygwin. The cygwin X11 server works quite well and
is free.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Could not lock the file /var/tmp/gconf-test-locking-file-blah

2008-11-16 Thread chrisa
Hello,

I've installed FreeBSD 7.0-RELEASE #0 on an Acer Aspire 5100 laptop, and
Gnome errors out when I try to start it. The kernel was compiled with no
ehci support in order to get the laptop to not freeze on shutdown after
syncing the disks, but there are no other major changes. I've installed
gnome and all other packages from packages-7-stable/Lastest on the
website, and it gives me the error from the subject line, 'Could not lock
the file /var/tmp/gconf-test-locking-file-blah'. It says that it's an
NFS locking error, but I'm not using NFS.

Do you think that the packages from 7-stable are simply not compatible
with 7.0-RELEASE (kde works fine), or is something else going on?

My dmesg follows:

Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-RELEASE #0: Sat Nov 15 00:34:06 PST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOEHCI
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-50 (1596.01-MHz K8-class CPU)
  Origin = AuthenticAMD  Id = 0x40f82  Stepping = 2
  
Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT
  Features2=0x2001SSE3,CX16
  AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!
  AMD Features2=0x1fLAHF,CMP,SVM,ExtAPIC,CR8
  Cores per package: 2
usable memory = 924700672 (881 MB)
avail memory  = 890621952 (849 MB)
ACPI APIC Table: PTLTD  APIC  
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 Version 2.1 irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
hptrr: HPT RocketRAID controller driver v1.1 (Nov 15 2008 00:33:42)
acpi0: PTLTD   RSDT on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, 1000 (3) failed
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 32-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0
acpi_ec0: Embedded Controller: GPE 0x10 port 0x62,0x66 on acpi0
cpu0: ACPI CPU on acpi0
powernow0: PowerNow! K8 on cpu0
cpu1: ACPI CPU on acpi0
powernow1: PowerNow! K8 on cpu1
acpi_lid0: Control Method Lid Switch on acpi0
acpi_button0: Power Button on acpi0
acpi_button1: Sleep Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
vgapci0: VGA-compatible display port 0x9000-0x90ff mem
0xc800-0xcfff,0xc010-0xc010 irq 17 at device 5.0 on pci1
pcib2: ACPI PCI-PCI bridge at device 4.0 on pci0
pci2: ACPI PCI bus on pcib2
pcib3: ACPI PCI-PCI bridge at device 5.0 on pci0
pci4: ACPI PCI bus on pcib3
ohci0: ATI SB400 USB Controller mem 0xc0004000-0xc0004fff irq 19 at
device 19.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: ATI SB400 USB Controller on ohci0
usb0: USB revision 1.0
uhub0: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0
uhub0: 4 ports with 4 removable, self powered
ohci1: ATI SB400 USB Controller mem 0xc0005000-0xc0005fff irq 19 at
device 19.1 on pci0
ohci1: [GIANT-LOCKED]
ohci1: [ITHREAD]
usb1: OHCI version 1.0, legacy support
usb1: ATI SB400 USB Controller on ohci1
usb1: USB revision 1.0
uhub1: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1
uhub1: 4 ports with 4 removable, self powered
pci0: serial bus, USB at device 19.2 (no driver attached)
pci0: serial bus, SMBus at device 20.0 (no driver attached)
atapci0: ATI IXP400 UDMA133 controller port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8410-0x841f irq 16 at device 20.1 on
pci0
ata0: ATA channel 0 on atapci0
ata0: [ITHREAD]
ata1: ATA channel 1 on atapci0
ata1: [ITHREAD]
pcm0: ATI SB450 High Definition Audio Controller mem
0xc000-0xc0003fff irq 16 at device 20.2 on pci0
pcm0: [ITHREAD]
isab0: PCI-ISA bridge at device 20.3 on pci0
isa0: ISA bus on isab0
pcib4: ACPI PCI-PCI bridge at device 20.4 on pci0
pci6: ACPI PCI bus on pcib4
rl0: RealTek 8139 10/100BaseTX port 0xa000-0xa0ff mem
0xc021-0xc02100ff irq 21 at device 1.0 on pci6
miibus0: MII bus on rl0
rlphy0: RealTek internal media interface PHY 0 on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:16:d4:14:c8:0f
rl0: [ITHREAD]
ath0: Atheros 5212 mem 0xc020-0xc020 irq 22 at device 2.0 on pci6
ath0: [ITHREAD]
ath0: using obsoleted if_watchdog interface
ath0: Ethernet address: 00:16:ce:7f:d8:05
ath0: mac 7.8 phy 4.5 radio 5.6
cbb0: PCI-CardBus Bridge mem 0xc0211000-0xc0211fff irq 20 at device 4.0
on pci6
cardbus0: CardBus bus on cbb0
pccard0: 16-bit PCCard bus on cbb0
cbb0: [ITHREAD]
pci6: memory, flash at device 4.1 (no driver