Re: Xorg 7.5 and OpenMotif: mouse stuck in box
Dear William, excellent! The patch you pointed me to works for me too. Thank you so much for your help, I am going to send an email to the port maintainers to see whether they can fix this in the ports tree. very best giuseppe On Mon, Oct 11, 2010 at 6:43 PM, William Bulley wrote: > According to Giuseppe Pagnoni on Mon, 10/11/10 at 10:57: >> >> thank you very much for your reply, it does seem to be the same type >> of bug. However, and I apologize for being dense here, it is not >> immediate to me how to proceed practically to apply the patch from >> within the ports framework. Also, I still wonder why the patch hasn't >> been incorporated in the tree given that the bug is known > > I am not able to answer your final question - that is left to the ports > maintainers to address. > > I simply installed the latest (was it 1.7.5) xorg-server at that time > and added those half dozen patches. If 1.7.7 solved the problem, then > I'm not sure what issue(s) you have. If you want to have FreeBSD ports > upgraded, I would contact the port's maintainers directly. > > I chose not to install xorg-server 1.7.7 since I was unsure if there > were other dependencies or issues that might arise from doing so. I'm > not used to "patch"ing a mature, released port, so for me even that was > a leap of faith! :-) > > Just for clarity, I did not formally "patch" this port (xorg-server). > I went into the directory tree beneath the "work" directory, found the > dit/events.c file, and made those above mentioned (about six or so) > small source code patches. I then re-made the port and re-installed > the port. After it tested successfully, I reported my results to the > -questions list in case it would help others. YMMV. And good luck! > > Regards, > > web... > > -- > William Bulley Email: w...@umich.edu > > 72 characters width template ->| > -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41125 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5336 ___ 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: Xorg 7.5 and OpenMotif: mouse stuck in box
Dear William, thank you very much for your reply, it does seem to be the same type of bug. However, and I apologize for being dense here, it is not immediate to me how to proceed practically to apply the patch from within the ports framework. Also, I still wonder why the patch hasn't been incorporated in the tree given that the bug is known thanks again giuseppe On Mon, Oct 11, 2010 at 4:07 PM, William Bulley wrote: > > Giuseppe Pagnoni wrote: >> >> I am resending this because it seems to me a really critical bug >> (prevents you from using OpenMotif or lesstif applications), but >> apparently nothing has been changed since last july. Upgrading xorg >> to 1.7.7 does fix the problem, but I wonder if this may cause >> dependency problems in the ports tree. Also, if this is the correct >> fix, is there a reason why it hasn't been integrated in the ports yet? >> >> thanks again >> >> giuseppe >> >> >>>> >> I am having a problem with xorg 1.7.5 and OpenMotif resulting in the >> mouse being stuck in certain areas of the Motif windows that are >> supposed to open dialog boxes when right-clicked. I noticed that >> somebody else reported the problem already in this list, and that it >> seems to have been fixed in xorg 1.7.7. However xorg 1.7.7 is not yet >> available in the ports tree, nor it looks like a patch is in for the >> current version (I tried to recompile xorg today after a port tree >> update). Is manually compiling Xorg the only solution right now? >> >> thanks in advance for any advice >> >> giuseppe >> >> >>>>> > > This is what I found recently. Hope this helps you. > > - Forwarded message from William Bulley - > > To: FreeBSD Questions > From: William Bulley > Date: Thu, 2 Sep 2010 11:31:15 -0400 > Subject: SOLVED: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE > Cc: x...@freebsd.org, st...@freebsd.org > > See below for details of solution. > > - Forwarded message from William Bulley - > > To: FreeBSD Questions > From: William Bulley > Date: Wed, 25 Aug 2010 07:38:34 -0400 > Subject: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE > > For years I have run Open-Motif on FreeBSD without issue. > > I use a USB keyboard and a USB three button mouse attached to a Dell > Optiplex 960. This combination has worked fine for the past year. > > This week I upgraded from 8.0-STABLE circa January 2010 to 8.1-STABLE. > I do this by doing a buildworld/installworld sequence after csup-ing > stable-supfile and rebooting. In this case I also pkg_deleted all of > my ports and am rebuilding them from source. Building Xorg is one of > the very first ports I attempt since I prefer to work in xterms not > virtual terminals. > > This upgrade moved me from Xorg 7.3 to Xorg 7.5, but Open-Motif stayed > the same - open-motif-2.2.3_6 - it hasn't changed in years. > > After building Xorg, as root, I ran the "Xorg -configure" command to > generate my xorg.conf.new file. Since a working /etc/X11/xorg.conf > file was still around after the upgrade from 8.0-STABLE/Xorg 7.3, I > felt no need to change anything in that file (later file comparisons > confirmed that nothing had changed). > > My only relevant additions to /etc/X11/xorg.conf are these: > > Section "ServerFlags" > Option "AutoAddDevices" "off" > Option "DontZap" "false" > EndSection > > In my /etc/rc.conf file I have dbus and hald enabled, and that has > not changed since the beginning of 2010 after the confusion abated. > > As a normal user, I start Xorg using /usr/local/bin/xinit as always. > I have several xterms configured in my ~/.xinitrc file. All those > came up in the correct location and state. I was able to open those > that started in iconic mode. In an open/raised xterm I could enter > carriage returns and see my shell prompt move down the window. But > when I tried to close/minimize an open/raised xterm, things failed. > > I use the following keyboard/mouse combination (configured in my > .mwmrc file) to close (minimize) an xterm (and other applications): > > Shift window f.minimize > > This is also unchanged for some years. This particular setting has > no bearing on the problem I came across yesterday. I merely state > it for the record. However, this configuration triggers the "bug". > > The problem is as soon as I use that Shift/Btn3Click combination, > my arrow cursor disappears, then I cannot move to or select other > xterms - I am frozen, or locked, into the xterm
Xorg 7.5 and OpenMotif: mouse stuck in box
Dear all, I am resending this because it seems to me a really critical bug (prevents you from using OpenMotif or lesstif applications), but apparently nothing has been changed since last july. Upgrading xorg to 1.7.7 does fix the problem, but I wonder if this may cause dependency problems in the ports tree. Also, if this is the correct fix, is there a reason why it hasn't been integrated in the ports yet? thanks again giuseppe >>>> I am having a problem with xorg 1.7.5 and OpenMotif resulting in the mouse being stuck in certain areas of the Motif windows that are supposed to open dialog boxes when right-clicked. I noticed that somebody else reported the problem already in this list, and that it seems to have been fixed in xorg 1.7.7. However xorg 1.7.7 is not yet available in the ports tree, nor it looks like a patch is in for the current version (I tried to recompile xorg today after a port tree update). Is manually compiling Xorg the only solution right now? thanks in advance for any advice giuseppe >>>>> -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41125 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5336 ___ 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"
pyglet font load segmentation fault
Dear all,
I posted about this problem a few months ago and have been scouring
the web ever since but I cannot find the slightest hint at a solution.
Actually, it seems that nobody else has reported a similar problem,
which I find really weird since the function is such a basic one in
pyglet -- quoting Zoolander, "I feel like I am taking crazy pills!"
The problem is that I cannot use the pyglet.font.load() function at
all without causing a segmentation fault:
python
import pyglet
arial = pyglet.font.load('Arial')
Segmentation fault
My system is running FreeBSD 8.1/amd64 with an Nvidia GeForce 9500GT
and the latest driver from Nvidia (256.53), and with all the ports
up-to-date as of today.
python26-2.6.5_1 was compiled with standard options:
WITH_THREADS=true
WITHOUT_HUGE_STACK_SIZE=true
WITHOUT_SEM=true
WITHOUT_PTH=true
WITH_UCS4=true
WITH_PYMALLOC=true
WITH_IPV6=true
WITHOUT_FPECTL=true
Any help would be tremendously appreciated,
thanks in advance
giuseppe
___
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"
pyglet segfaults on FreeBSD 8.0/amd64/nVidia
Hi Michael, thanks for replying. Unfortunately changing the driver to the "nv" one does not work since "nv" does not support GLX which is required by pyglet. I appreciate your suggestion, though. cheers, giuseppe -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 ___ 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"
pyglet segfaults on FreeBSD 8.0/amd64/nVidia
Hello,
First of all, let me apologize for the re- and cross-posting , but
after a couple of weeks scouring the web and forums to no avail, I
thought I would try again and query the FreeBSD mother source...
I installed pyglet from the ports (latest version as of yesterday,
py26-pyglet-1.1.2_1) on a FreeBSD 8.0 amd64 box, running the latest
version of the ports' nvidia driver (nvidia-driver-195.36.15). I
found that I cannot use either font.Text or text.label without causing
segfaults. Here is some sample code that makes python crash:
- SNIPPET 1
import pyglet
luxi = pyglet.font.load('Luxi Sans', 14)
--- > SEGMENTATION FAULT
- SNIPPET 2
import pyglet
window = pyglet.window.Window()
label = pyglet.text.Label('Hello, world',
font_name='Luxi Sans',
font_size=36,
x=window.width//2,
y=window.height//2,
anchor_x='center',
anchor_y='center')
--- > SEGMENTATION FAULT
It seems that the problem arises already at the stage of font loading.
I am not at all a python expert, perhaps somebody can suggest a
way to narrow down the problem?
Here is some more information on my system reported by a routine
included in a python package (PsychoPy) I am trying to use:
System info:
FreeBSD-8.0-RELEASE-p2-amd64-64bit-ELF
Python info
/usr/local/bin/python
2.6.4 (r264:75706, Mar 23 2010, 15:20:14)
[GCC 4.2.1 20070719 [FreeBSD]]
numpy 1.4.0
scipy 0.7.1
matplotlib 0.99.1
pyglet 1.1.2
PsychoPy 1.60.03
OpenGL info:
vendor: NVIDIA Corporation
rendering engine: GeForce 9500 GT/PCI/SSE2
OpenGL version: 3.2.0 NVIDIA 195.36.15
(Selected) Extensions:
True GL_ARB_multitexture
True GL_EXT_framebuffer_object
True GL_ARB_fragment_program
True GL_ARB_shader_objects
True GL_ARB_vertex_shader
True GL_ARB_texture_non_power_of_two
True GL_ARB_texture_float
Thanks in advance for any suggestion/comment,
cheers,
giuseppe
--
Giuseppe Pagnoni
Dip. Scienze Biomediche
Sezione Fisiologia
Univ. di Modena e Reggio Emilia
Via Campi 287
I-41125 Modena, Italy
Tel: +39-059-205-5742
Fax: +39-059-205-5336
___
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"
pyglet segfaults on FreeBSD 8.0/amd64
Hi,
I installed pyglet from the ports (latest version as of yesterday) on
a FreeBSD 8.0 amd64 box, running the ports' nvidia driver. I found
that I cannot use either font.Text or text.label without causing
segfaults. Here is some sample code that makes python crash:
- SNIPPET 1
import pyglet
window = pyglet.window.Window()
luxi = pyglet.font.load('Luxi Sans', 14)
--- > SEGMENTATION FAULT
- SNIPPET 12
import pyglet
window = pyglet.window.Window()
label = pyglet.text.Label('Hello, world',
font_name='Luxi Sans',
font_size=36,
x=window.width//2,
y=window.height//2,
anchor_x='center',
anchor_y='center')
--- > SEGMENTATION FAULT
It seems that the problem arises already at the stage of font loading.
I am not at all a python expert, but perhaps somebody can suggest a
way to narrow down the problem?
Here is some more information on my system reported by a routine
included in a python package (PsychoPy) I am trying to use, in case
that's useful:
System info:
FreeBSD-8.0-RELEASE-p2-amd64-64bit-ELF
Python info
/usr/local/bin/python
2.6.4 (r264:75706, Mar 23 2010, 15:20:14)
[GCC 4.2.1 20070719 [FreeBSD]]
numpy 1.4.0
scipy 0.7.1
matplotlib 0.99.0
pyglet 1.1.2
PsychoPy 1.60.03
OpenGL info:
vendor: NVIDIA Corporation
rendering engine: GeForce 9500 GT/PCI/SSE2
OpenGL version: 3.2.0 NVIDIA 195.22
(Selected) Extensions:
True GL_ARB_multitexture
True GL_EXT_framebuffer_object
True GL_ARB_fragment_program
True GL_ARB_shader_objects
True GL_ARB_vertex_shader
True GL_ARB_texture_non_power_of_two
True GL_ARB_texture_float
Thanks in advance for any suggestion/comment,
very best
giuseppe
--
Giuseppe Pagnoni
Dip. Scienze Biomediche
Sezione Fisiologia
Univ. di Modena e Reggio Emilia
Via Campi 287
I-41125 Modena, Italy
Tel: +39-059-205-5742
Fax: +39-059-205-5336
___
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"
lxde
hello, I installed the lxde-meta in a new FreeBSD 8.0 i386 machine, but when I start it (via "exec startlxde" in ~.xinitrc) only a black desktop appears with no panel or menu bars. Right-clicking on the desktop a *very* minimal menu appears (basically containing xterm, firefox and the file manager). I was wondering whether this is the intended behavior or I am missing something... Does anyone know how to get the panel up? Also, I don't think lxterminal is present in the ports... is there any plan to include it? thanks in advance for any comments or suggestions regards giuseppe -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41125 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5336 ___ 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: dbus/hal in freebsd 7.2 hangs X11
Hi William, thank you very much for your reply. I believe, though, that if you disable hal and dbus in rc.conf, then you are not using them at all (the corresponding daemons don't start up at boot time). For me too the window managers work fine *without* hal/dbus, but I was trying to get these working. best, giuseppe On Fri, Sep 25, 2009 at 2:32 PM, William Bulley wrote: > According to Giuseppe Pagnoni on Fri, 09/25/09 at 03:32: >> >> I am trying to use hal/dbus on a i386 machine with FreeBSD 7.2 (ports >> updated to the latest tree snapshot as of yesterday), but despite >> spending a full day looking up the handbook, faq, and google, I cannot >> make it work properly. More specifically, when I use either xfce4 or >> xmonad after having enabled dbus/hald in rc.conf: >> >> hald_enable="YES" >> dbus_enable="YES" >> >> both window managers become very unresponsive and hang as if hal was >> trying to access/mount something. For example, the terminal may take >> *seconds* to display typed in characters and in xfce if you click on >> the desktop icons for home directory etc., they don't open up at all >> in the thunar file manager (they do though, if you right click on them >> and choose 'open'). > > I, too, have seen this same problem, but with OpenMotif (mwm) as my > window manager. I have solved the problem by changing the lines: > > dbus_enable="YES" > hald_enable="YES" > > to > > dbus_enable="NO" > hald_enable="NO" > > in my /etc/rc.conf file. This makes things in xorg-7.4_2 and > open-motif-2.2.3_6 > and 7.2-STABLE FreeBSD 7.2-STABLE #0: Tue Sep 15 14:33:54 EDT 2009 work for > me. > > Regards, > > web... > > -- > William Bulley Email: w...@umich.edu > > 72 characters width template ->| > -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 ___ 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"
dbus/hal in freebsd 7.2 hangs X11
Hi all, I am trying to use hal/dbus on a i386 machine with FreeBSD 7.2 (ports updated to the latest tree snapshot as of yesterday), but despite spending a full day looking up the handbook, faq, and google, I cannot make it work properly. More specifically, when I use either xfce4 or xmonad after having enabled dbus/hald in rc.conf: hald_enable="YES" dbus_enable="YES" both window managers become very unresponsive and hang as if hal was trying to access/mount something. For example, the terminal may take *seconds* to display typed in characters and in xfce if you click on the desktop icons for home directory etc., they don't open up at all in the thunar file manager (they do though, if you right click on them and choose 'open'). I read on the freebsd/gnome/halfaq that you should not have in your /etc/fstab entries that are supposed to be used by hal, so I commented out the lines for cdrom and flash USB drive in fstab: # DeviceMountpoint FStype Options DumpPass# /dev/ad6s1b noneswapsw 0 0 /dev/ad6s1a / ufs rw 1 1 /dev/ad6s1e /tmpufs rw 2 2 /dev/ad6s1f /usrufs rw 2 2 /dev/ad6s1d /varufs rw 2 2 #/dev/acd0 /cdrom cd9660 ro,noauto 0 0 # Changed the above for the following (ATAPI-CAM) #/dev/cd0 /mnt/cdrom cd9660 ro,noauto 0 0 #/dev/da0s1 /mnt/flash msdosfs rw,noauto 0 0 # For linux compat linproc/usr/compat/linux/proc linprocfs rw 0 0 # For VirtualBox, truss(1) proc/proc procfs rw 00 However, this produces no improvement. Also, following the instruction in the mentioned FAQ, I added the following lines to the /usr/local/etc/PolicyKit/PolicyKit.conf file: alas, with no improvement either... Before trying to use hal (which I needed for VirtualBox), I had changed system settings for making the flash USB drive and CD-rom user mountable, following the instructions in the handbook at: http://www.freebsd.org/doc/en/books/handbook/usb-disks.html that is: 1) adding myself to the operator group 2) adding the following lines to /etc/devfs.rules [localrules=5] add path 'cd*' mode 0660 group operator [localrules=6] add path 'da*' mode 0660 group operator 3) enable devfs.rules(5) in /etc/rc.conf: devfs_system_ruleset="localrules" 4) adding the line to /etc/sysctl.conf vfs.usermount=1 5) create user accessible mount points: mkdir /mnt/cdrom /mnt/flash chown giuseppe:giuseppe /mnt/cdrom /mnt/flash It seems to me that this should not have any relevance for the misbehavior of hal/dbus, but I am reporting it here just in case there is some weird interaction that I am not aware of. I am kind of stumped at this point, I would be very grateful is somebody has any suggestion to share. thanks in advance! giuseppe ___ 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"
linux-nx-client: connection error
Hi all, I am trying to connect from my machine (i386, FreeBSD 7.2 Rel) to a remote machine using linux-nx-client. I get through the authentication phase just fine, but soon after that the connection stops. Here is the message that comes up when I hit the "Details" button: NXPROXY - Version 2.1.0 Copyright (C) 2001, 2006 NoMachine. See http://www.nomachine.com/ for more information. Info: Proxy running in client mode with pid '29650'. Session: Starting session at 'Thu Aug 27 14:57:33 2009'. Error: Failed to set TCP_NODELAY flag on FD#9 to 1. Error is 22 'Invalid argument'. Info: Aborting the procedure due to signal '15'. Even when I check the option: "Disable no-delay on TCP connection" under the Configuration settings (Advanced tab), the error does not change. Does anybody have any suggestion? thanks in advance giuseppe -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 ___ 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"
freenx
Dear all, I am trying to use nxclient on a FreeBSD machine (i386, 7.2 Rel). I installed freenx but I can't figure out how to use it to connect to a remote machine. It seems that the port does not put any executable into any standard path. If I enter in a terminal: /usr/local/NX/bin/nxclient I get the following message: getopt: illegal option -- o Terminating... I had previously used NXclient but through a GUI interface. I couldn't find a way to start a GUI here or even figure out the required command line syntax (no man pages installed, no --help option available,...). Did anybody know how to make this work (if it actually does..)? thanks in advance for any suggestion best giuseppe -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 ___ 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"
xview problem
Dear alll pardon the re-post, I thought I would check again if somebody has found a solution for this, since my last e-mail. I am running FreeBSD 7.1-RELEASE-p4 on an i386 machine and I am unable to use applications that depend on xview. For example, when I try to run "clock", I get: Assertion failed: (ret != inval_id), function _XAllocID, file xcb_io.c, line 378. Abort and I get the same error for any other application using xview. I have updated the installed software to the latest (as of today) version of the ports tree, and I have also run the following command listed in /usr/ports/UPDATING: portupgrade -rf libxcb but to no avail. I have also googled the error message, but the only link that comes up is in Japanese Any suggestions? thank you very much in advance -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy ___ 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"
xview problem
Dear alll I am running FreeBSD 7.1-RELEASE-p4 on an i386 machine and I am unable to use applications that depend on xview. For example, when I try to run "clock", I get: Assertion failed: (ret != inval_id), function _XAllocID, file xcb_io.c, line 378. Abort and I get the same error for any other application using xview. I have updated the installed software to the latest (as of today) version of the ports tree, and I have also run the following command listed in /usr/ports/UPDATING: portupgrade -rf libxcb but to no avail. I have also googled the error message, but the only link that comes up is in Japanese Any suggestions? thank you very much in advance -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 ___ 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: FreeBSD 7.1, nvidia-driver, GeForce 8500 GT
perhaps, I need to deinstall and reinstall nvidia-driver after having changed boot/loader.conf? g. On Fri, Jan 9, 2009 at 9:17 AM, Paul B. Mahol wrote: > On 1/9/09, Giuseppe Pagnoni wrote: >> -- Forwarded message -- >> From: Giuseppe Pagnoni >> Date: Thu, Jan 8, 2009 at 6:11 PM >> Subject: Re: FreeBSD 7.1, nvidia-driver, GeForce 8500 GT >> To: Pieter de Goeje >> >> >> Dear Pieter, >> >> thanks for the information. Unfortunately, putting the line >> hw.physmem="3G" in /boot/loader.conf as you suggested does not prevent >> the system from crashing when starting X (even using "2G"), while > > You rebooted after that change? > >> taking physically out the 2G memory bank from the motherboard does. >> That's a pity because this being a dual boot system, I could have left >> the 4 GB of RAM in when using the other OS Is there any other >> option that you would be aware of? >> >> thanks again >> >> giuseppe >> >> On Thu, Jan 8, 2009 at 1:44 PM, Pieter de Goeje wrote: >>>> >>>> How much memory do you have? Freebsd/Nvidia doesn't work with 4Gigs >>>> >>>> of memory OR PAE enabled kernels. Nvidia's forums have lots more >>>> >>>> information >>>> >>>> regarding this. >>>> >> >>>> >> I'm not sure of the internals exactly, but the amount of onboard >>>> >> memory >>>> >> plus the memory that comes with the card can't exceed 4G. (I could be >>>> >> wrong, but I think this is accurate). In this case, assuming you have >>>> >> a >>>> >> 512M card or similar then 3 Gigs of memory should work. I have seen >>>> >> reports of 2Gigs of memory working (i386) and am sure that works >>>> >> without >>>> >> problems. amd64 doesn't work at all, as you have already stated. >>>> >> >>>> >> If you have a requirement to use the nvidia based graphics driver, >>>> >> then >>>> >> you really don't have an alternative at this time, then to remove >>>> >> system >>>> >> memory from your main board. >>>> >> >>>> >> ~Paul >>> >>> Putting hw.physmem="3G" in /boot/loader.conf might also work. >>> >>> -- >>> Pieter de Goeje >>> >>> >> >> >> >> -- >> Giuseppe Pagnoni >> Dip. Scienze Biomediche >> Sezione Fisiologia >> Univ. di Modena e Reggio Emilia >> Via Campi 287 >> I-41100 Modena, Italy >> Tel: +39-059-205-5742 >> Fax: +39-059-205-5363 >> >> >> >> -- >> Giuseppe Pagnoni >> Dip. Scienze Biomediche >> Sezione Fisiologia >> Univ. di Modena e Reggio Emilia >> Via Campi 287 >> I-41100 Modena, Italy >> Tel: +39-059-205-5742 >> Fax: +39-059-205-5363 >> ___ >> 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" >> > > > -- > Paul > -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 ___ 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: FreeBSD 7.1, nvidia-driver, GeForce 8500 GT
Yes, I did. And although the system appears to list the specified amount of RAM (3GB or 2GB), the X server crashes nonetheless... On Fri, Jan 9, 2009 at 9:17 AM, Paul B. Mahol wrote: > On 1/9/09, Giuseppe Pagnoni wrote: >> -- Forwarded message -- >> From: Giuseppe Pagnoni >> Date: Thu, Jan 8, 2009 at 6:11 PM >> Subject: Re: FreeBSD 7.1, nvidia-driver, GeForce 8500 GT >> To: Pieter de Goeje >> >> >> Dear Pieter, >> >> thanks for the information. Unfortunately, putting the line >> hw.physmem="3G" in /boot/loader.conf as you suggested does not prevent >> the system from crashing when starting X (even using "2G"), while > > You rebooted after that change? > >> taking physically out the 2G memory bank from the motherboard does. >> That's a pity because this being a dual boot system, I could have left >> the 4 GB of RAM in when using the other OS Is there any other >> option that you would be aware of? >> >> thanks again >> >> giuseppe >> >> On Thu, Jan 8, 2009 at 1:44 PM, Pieter de Goeje wrote: >>>> >>>> How much memory do you have? Freebsd/Nvidia doesn't work with 4Gigs >>>> >>>> of memory OR PAE enabled kernels. Nvidia's forums have lots more >>>> >>>> information >>>> >>>> regarding this. >>>> >> >>>> >> I'm not sure of the internals exactly, but the amount of onboard >>>> >> memory >>>> >> plus the memory that comes with the card can't exceed 4G. (I could be >>>> >> wrong, but I think this is accurate). In this case, assuming you have >>>> >> a >>>> >> 512M card or similar then 3 Gigs of memory should work. I have seen >>>> >> reports of 2Gigs of memory working (i386) and am sure that works >>>> >> without >>>> >> problems. amd64 doesn't work at all, as you have already stated. >>>> >> >>>> >> If you have a requirement to use the nvidia based graphics driver, >>>> >> then >>>> >> you really don't have an alternative at this time, then to remove >>>> >> system >>>> >> memory from your main board. >>>> >> >>>> >> ~Paul >>> >>> Putting hw.physmem="3G" in /boot/loader.conf might also work. >>> >>> -- >>> Pieter de Goeje >>> >>> >> >> >> >> -- >> Giuseppe Pagnoni >> Dip. Scienze Biomediche >> Sezione Fisiologia >> Univ. di Modena e Reggio Emilia >> Via Campi 287 >> I-41100 Modena, Italy >> Tel: +39-059-205-5742 >> Fax: +39-059-205-5363 >> >> >> >> -- >> Giuseppe Pagnoni >> Dip. Scienze Biomediche >> Sezione Fisiologia >> Univ. di Modena e Reggio Emilia >> Via Campi 287 >> I-41100 Modena, Italy >> Tel: +39-059-205-5742 >> Fax: +39-059-205-5363 >> ___ >> 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" >> > > > -- > Paul > -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 ___ 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: FreeBSD 7.1, nvidia-driver, GeForce 8500 GT
-- Forwarded message -- From: Giuseppe Pagnoni Date: Thu, Jan 8, 2009 at 6:11 PM Subject: Re: FreeBSD 7.1, nvidia-driver, GeForce 8500 GT To: Pieter de Goeje Dear Pieter, thanks for the information. Unfortunately, putting the line hw.physmem="3G" in /boot/loader.conf as you suggested does not prevent the system from crashing when starting X (even using "2G"), while taking physically out the 2G memory bank from the motherboard does. That's a pity because this being a dual boot system, I could have left the 4 GB of RAM in when using the other OS Is there any other option that you would be aware of? thanks again giuseppe On Thu, Jan 8, 2009 at 1:44 PM, Pieter de Goeje wrote: >> >>>> How much memory do you have? Freebsd/Nvidia doesn't work with 4Gigs >> >>>> of memory OR PAE enabled kernels. Nvidia's forums have lots more >> >>>> information >> >>>> regarding this. >> >> >> >> I'm not sure of the internals exactly, but the amount of onboard memory >> >> plus the memory that comes with the card can't exceed 4G. (I could be >> >> wrong, but I think this is accurate). In this case, assuming you have a >> >> 512M card or similar then 3 Gigs of memory should work. I have seen >> >> reports of 2Gigs of memory working (i386) and am sure that works without >> >> problems. amd64 doesn't work at all, as you have already stated. >> >> >> >> If you have a requirement to use the nvidia based graphics driver, then >> >> you really don't have an alternative at this time, then to remove system >> >> memory from your main board. >> >> >> >> ~Paul > > Putting hw.physmem="3G" in /boot/loader.conf might also work. > > -- > Pieter de Goeje > > -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 ___ 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"
PATA DVD on Asus P5Q Pro
Dear all, although I posted a previous email to the list about this issue some months ago, I thought I would check again to see whether anything has changed with the 7.1 release. I have an LG cd/dvd combo (model GH22LP20) that attaches to the PATA(/IDE) connector of an Asus P5Q Pro motherboard. The specs for the motherboard are the following: N° sockets (max memory): 4xDDR2 (max 8GB) Chipset: Intel P45 (LGA775 platform)+ ICH10R Sound Card: Realtek ALC1200 7.1 Channel High Definition Audio SATA support, N° connectors: 8x SATA2, 1x PATA LAN: Atheros AR8121 10/100/1000 Mb/s RAID: 0,1,0+1,5 Connectors: * 2 slots for PCI Express 16x 2.0 * 3 slots PCI Express x1 * 2 slots PCI 2.2 * 12 x USB * 2 x Firewire The PATA-133/IDE interface is implemented via an additional Marvell 88SE6111controller (SATA is driven via ICH10R). My problem is that the DVD drive is not seen by FreeBSD, although it is seen by the BIOS in the boot up phase. In the previous post Jeremy Chadwick pointed out that the Marvell 88SE6111controller may not be supported by FreeBSD. I was wondering if this is still the case with the 7.1 Release and whether somebody could suggest a workaround that does not involve replacing the drive (e.g., is it possible to use some sort of converter cable from SATA to PATA? I apologize if this is complete nonsense, but I know close to nothing about buses and connector types). By the way, the Atheros onboard NIC appears to work fine with the driver "ale" (disabled by default in the GENERIC kernel), and sound works too with the kernel module snd_hda. thanks in advance for any suggestion very best giuseppe -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 ___ 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: FreeBSD 7.1, nvidia-driver, GeForce 8500 GT
Dear Paul, thank you very much for your help, that surely clarifies things. best giuseppe On Wed, Jan 7, 2009 at 12:51 AM, Paul Procacci wrote: > Paul Procacci wrote: >> >> Giuseppe Pagnoni wrote: >>> >>> Hello, >>> >>> well that is interesting. I do have 4 Gigs of RAM but I thought that >>> the nvidia driver would not work only if the 64 bit version of FreeBSD >>> was installed. I installed the i386 version, so I assumed that I was >>> just wasting some memory. In case I would want to use the nvidia >>> driver, would you suggest to remove 1GB stick of RAM? >>> >>> thank you very much >>> >>> >>> >>> On Tue, Jan 6, 2009 at 11:21 PM, Paul Procacci >>> wrote: >>> >>>> >>>> Giuseppe Pagnoni wrote: >>>> >>>>> >>>>> Dear all, >>>>> >>>>> I have just installed FreeBSD 7.1 Release on a machine with a GeForce >>>>> 8500 GT (I think this is the card, but more about that later...) and >>>>> an LCD screen with a native resolution of 1680 x 1050. >>>>> >>>>> Xorg works fine with the standard "nv" driver. However, if I try to >>>>> install the x11/nvidia-driver (which should bring better graphic >>>>> performance, right?) I get a total system freeze when I start the X >>>>> server. >>>>> >>>>> Here are the details of what I have done: >>>>> >>>>> 1) install x11/nvidia-driver >>>>> 2) add nvidia_load="YES" to /boot/loader.conf >>>>> 3) modify /etc/X11/xorg.conf by substituting "nvidia" to "nv" in the >>>>> Driver line. >>>>> >>>>> At this point (after rebooting), if I start the X server with startx, >>>>> I get a black screen and the system *completely* hangs (neither >>>>> ctrl-alt-backspace, nor even ctrl-alt-delete work). The only way to >>>>> get back the system is to power it off and on (which corrupts the >>>>> filesystem because it has not been properly dismounted). >>>>> >>>>> I also looked at the xorg log file in: >>>>> >>>>> /var/log/Xorg.0.log >>>>> >>>>> Interestingly it seems to detect the card as a GeForce 9500 GT rather >>>>> than a 8500 GT (which makes me wonder whether I got the right info >>>>> from the vendor receipt): >>>>> >>>>> (--) Assigning device section with no busID to primary device >>>>> (--) Chipset GeForce 9500 GT found >>>>> >>>>> But this should not be an issue because in the same log file it says >>>>> that both GeForce 8500 GT and GeForce 9500 GT are supported by the >>>>> "nv" driver. >>>>> >>>>> As for the monitor, the xorg log file says: >>>>> >>>>> II) NV(0): Supported additional Video Mode: >>>>> (II) NV(0): clock: 146.2 MHz Image Size: 473 x 296 mm >>>>> (II) NV(0): h_active: 1680 h_sync: 1784 h_sync_end 1960 h_blank_end >>>>> 2240 h_border: 0 >>>>> (II) NV(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: >>>>> 1089 v_border: 0 >>>>> (II) NV(0): Ranges: V min: 56 V max: 75 Hz, H min: 28 H max: 83 kHz, >>>>> PixClock max 150 MHz(II) >>>>> >>>>> NV(0): Monitor name: L226WA >>>>> (II) NV(0): Supported additional Video Mode: >>>>> (II) NV(0): clock: 119.0 MHz Image Size: 473 x 296 mm >>>>> (II) NV(0): h_active: 1680 h_sync: 1728 h_sync_end 1760 h_blank_end >>>>> 1840 h_border: 0 >>>>> (II) NV(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: >>>>> 1080 v_border: 0 >>>>> >>>>> Then the log file says: >>>>> >>>>> (II) NV(0): Output VGA1 disconnected >>>>> (II) NV(0): Output DVI0 disconnected >>>>> (II) NV(0): Output VGA2 disconnected >>>>> (II) NV(0): Output DVI1 connected >>>>> (II) NV(0): Output DVI1 using initial mode 1680x1050 >>>>> (--) NV(0): Virtual size is 1680x1680 (pitch 1792) >>>>> (**) NV(0): Driver mode "1680x1050": 146.2 MHz (scaled from 0.0 MHz), >>>>> 65.3 kHz, 60.0 Hz >>>>> (II) NV(0): Modeline "1680x1050"x60.0 146.2
Re: FreeBSD 7.1, nvidia-driver, GeForce 8500 GT
Hello, well that is interesting. I do have 4 Gigs of RAM but I thought that the nvidia driver would not work only if the 64 bit version of FreeBSD was installed. I installed the i386 version, so I assumed that I was just wasting some memory. In case I would want to use the nvidia driver, would you suggest to remove 1GB stick of RAM? thank you very much On Tue, Jan 6, 2009 at 11:21 PM, Paul Procacci wrote: > Giuseppe Pagnoni wrote: >> >> Dear all, >> >> I have just installed FreeBSD 7.1 Release on a machine with a GeForce >> 8500 GT (I think this is the card, but more about that later...) and >> an LCD screen with a native resolution of 1680 x 1050. >> >> Xorg works fine with the standard "nv" driver. However, if I try to >> install the x11/nvidia-driver (which should bring better graphic >> performance, right?) I get a total system freeze when I start the X >> server. >> >> Here are the details of what I have done: >> >> 1) install x11/nvidia-driver >> 2) add nvidia_load="YES" to /boot/loader.conf >> 3) modify /etc/X11/xorg.conf by substituting "nvidia" to "nv" in the >> Driver line. >> >> At this point (after rebooting), if I start the X server with startx, >> I get a black screen and the system *completely* hangs (neither >> ctrl-alt-backspace, nor even ctrl-alt-delete work). The only way to >> get back the system is to power it off and on (which corrupts the >> filesystem because it has not been properly dismounted). >> >> I also looked at the xorg log file in: >> >> /var/log/Xorg.0.log >> >> Interestingly it seems to detect the card as a GeForce 9500 GT rather >> than a 8500 GT (which makes me wonder whether I got the right info >> from the vendor receipt): >> >> (--) Assigning device section with no busID to primary device >> (--) Chipset GeForce 9500 GT found >> >> But this should not be an issue because in the same log file it says >> that both GeForce 8500 GT and GeForce 9500 GT are supported by the >> "nv" driver. >> >> As for the monitor, the xorg log file says: >> >> II) NV(0): Supported additional Video Mode: >> (II) NV(0): clock: 146.2 MHz Image Size: 473 x 296 mm >> (II) NV(0): h_active: 1680 h_sync: 1784 h_sync_end 1960 h_blank_end >> 2240 h_border: 0 >> (II) NV(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: >> 1089 v_border: 0 >> (II) NV(0): Ranges: V min: 56 V max: 75 Hz, H min: 28 H max: 83 kHz, >> PixClock max 150 MHz(II) >> >> NV(0): Monitor name: L226WA >> (II) NV(0): Supported additional Video Mode: >> (II) NV(0): clock: 119.0 MHz Image Size: 473 x 296 mm >> (II) NV(0): h_active: 1680 h_sync: 1728 h_sync_end 1760 h_blank_end >> 1840 h_border: 0 >> (II) NV(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: >> 1080 v_border: 0 >> >> Then the log file says: >> >> (II) NV(0): Output VGA1 disconnected >> (II) NV(0): Output DVI0 disconnected >> (II) NV(0): Output VGA2 disconnected >> (II) NV(0): Output DVI1 connected >> (II) NV(0): Output DVI1 using initial mode 1680x1050 >> (--) NV(0): Virtual size is 1680x1680 (pitch 1792) >> (**) NV(0): Driver mode "1680x1050": 146.2 MHz (scaled from 0.0 MHz), >> 65.3 kHz, 60.0 Hz >> (II) NV(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 >> 1050 1053 1059 1089 -hsync +vsync (65.3 kHz) >> (**) NV(0): Driver mode "1680x1050": 119.0 MHz (scaled from 0.0 MHz), >> 64.7 kHz, 59.9 Hz >> (II) NV(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 >> 1050 1053 1059 1080 +hsync -vsync (64.7 kHz) >> (**) NV(0): Driver mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), >> 80.0 kHz, 75.0 Hz >> (II) NV(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 >> 1024 1025 1028 1066 +hsync +vsync (80.0 kHz) >> (**) NV(0): Driver mode "1280x1024": 109.0 MHz (scaled from 0.0 MHz), >> 63.7 kHz, 59.9 Hz >> (II) NV(0): Modeline "1280x1024"x59.9 109.00 1280 1368 1496 1712 >> 1024 1027 1034 1063 -hsync +vsync (63.7 kHz) >> (**) NV(0): Driver mode "1440x900": 136.8 MHz (scaled from 0.0 MHz), >> 70.6 kHz, 75.0 Hz >> (II) NV(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 >> 903 909 942 -hsync +vsync (70.6 kHz) >> (**) NV(0): Driver mode "1440x900": 106.5 MHz (scaled from 0.0 MHz), >> 55.9 kHz, 59.9 Hz >> (II) NV(0): Modeline "1440x900"x59.9 106.50 1440 1528 1672 1904 900 >>
FreeBSD 7.1, nvidia-driver, GeForce 8500 GT
4"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz) (**) NV(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz (II) NV(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz) (**) NV(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz (II) NV(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (**) NV(0): Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz (II) NV(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz) (**) NV(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz (II) NV(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz) (**) NV(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (II) NV(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (**) NV(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz (II) NV(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz) (==) NV(0): DPI set to (96, 96) After this rather long post (I apologize), I have two simple questions: 1) is there a way to use the "nvidia" driver on this system? 2) is it worthwhile or does "nv" work just as well? Thanks in advance for any help or suggestion. best giuseppe -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 ___ 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"
LG combo drive and installation: drive not found
Dear FreeBSD experts, I am trying to install FreeBSD 7.0 on a new i386 machine with no OS installed yet. I start the install process with the 1st CD of the distribution, and I go through the partition phase with no problem. However, when I get to the point where I select the installation media (CD/DVD) it says that it cannot find the CD/DVD. I read on the FAQ list on the FreeBSD site that this can happen when the drive is configured as a slave with no master. So I opened up the box, and I saw that the drive has its own ATAPI/IDE cable/slot on the motherboard and the jumpers on the drive are set as MASTER. The drive is a new LG combo drive, I believe GH22LP20 or something close to it. I also tried to install Ubuntu and it works fine (but I really would like FreeBSD!). Any help or suggestion will be highly appreciated, thanks in advance giuseppe -- Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
linux programs accessing non-linux programs
Hi all, I have been having trouble figuring out how to make linux programs (installed and running under /compat/linux) access other FreeBSD binaries that are *not* located under /compat/linux. For instance, I am running linux-thunderbird and when I want to open a *.doc file attachment, thunderbird asks me which application I would like to use: I would like to point it to /usr/X11R6/bin/abiword , but unfortunately when I chdir to /usr/X11R6/bin in the dialog box, it goes actually to /compat/linux/usr/X11R6/bin (and abiword is *not* there). Is there a way to make linux programs be able to jump out of /compat/linux/ when looking for helper applications? thanks in advance for any advice best giuseppe -- - Giuseppe Pagnoni Psychiatry and Behavioral Sciences Emory University School of Medicine 1639 Pierce Drive, Suite 4000 Atlanta, GA, 30322 tel: 404.712.8431 fax: 404.727.3233 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
limit datasize
Dear all, I am running into a memory problem when using large datasets. The limit command shows: cputime unlimited filesize unlimited datasize 524288 kbytes stacksize65536 kbytes coredumpsize unlimited memoryuseunlimited vmemoryuse unlimited descriptors 11095 memorylocked unlimited maxproc 5547 sbsize unlimited however, /etc/login.conf shows that the default setting is "unlimited": default:\ :passwd_format=md5:\ :copyright=/etc/COPYRIGHT:\ :welcome=/etc/motd:\ :setenv=MAIL=/var/mail/$,BLOCKSIZE=K,FTP_PASSIVE_MODE=YES:\ :path=/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/ sbin /usr/local/bin /usr/X11R6/bin ~/bin:\ :nologin=/var/run/nologin:\ :cputime=unlimited:\ :datasize=unlimited:\ :stacksize=unlimited:\ :memorylocked=unlimited:\ :memoryuse=unlimited:\ :filesize=unlimited:\ :coredumpsize=unlimited:\ :openfiles=unlimited:\ :maxproc=unlimited:\ :sbsize=unlimited:\ :vmemoryuse=unlimited:\ :priority=0:\ :ignoretime@:\ :umask=022: Any suggestion on how to increase the limits? thank you very much in advance giuseppe Giuseppe Pagnoni Dept. of Psychiatry 101 Woodruff Circle Altanta, GA 30322 Tel: 404-712-9582 Fax: 404-727-3233 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
usb device problem
Dear list I am running 4.8stable and I have a problem with a USB disk on key. When I insert it into one of the USB ports, I get the error message: uhub0: device problem, disabling port 1 In the kernel, both da and umass are enabled. Any suggestion? thanks -- Giuseppe Pagnoni, Ph.D. Dept. of Psychiatry and Behavioral Sciences 1639 Pierce Drive, Suite 4000 WMB Bldg., Atlanta, GA 30322, U.S. phone: 404-712-8431 fax: 404-727-3233 e-mail: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cd sound on onboard card
I guess you guys are right I opened the box and indeed the CD is connected to the motherboard only via IDE. I am going to find some audio cable and try it. thanks! Toomas Aas wrote: Hi! also the CD is connected to the sound card because it does work in windows. This doesn't necessarily mean that the audio cable is connected. If you're using Windows Media Player to play audio CDs in Windows then you may be using the "digital playback" feature, in which case the data is read off the CD via IDE and then fed to sound card. If you can play CDs in windows using good old 'CD Player' or Winamp 2.7x (not sure about newer versions of Winamp) then we can indeed assume that the audio cable is connected. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Be sure to use DEVICE=EXXON to screw up your environment. -- -------- Giuseppe Pagnoni, Ph.D. Dept. of Psychiatry and Behavioral Sciences 1639 Pierce Drive, Suite 4000 WMB Bldg., Atlanta, GA 30322, U.S. phone: 404-712-8431 fax: 404-727-3233 e-mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: cd sound on onboard card
Dear Justin thanks for your suggestion. I checked the mixer settings and they're fine, also the CD is connected to the sound card because it does work in windows. I suspect it has to do with the fact that the sound module is onboard because I never encountered this problem with proper sound cards... giuseppe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
cd sound on onboard card
I have installed freebsd 4.8 prerelease on a Dell Dimension 8250. This box has onboard sound which I managed to make work adding the lines: device pcm options PNPBIOS Now general sound works (e.g. playing .wav files) but I can't get the cd to output sound (it reads music cds, plays them, gets the right CDDB infos but no sound). Does anybody have any idea on how to fix this? thanks giuseppe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
