Re: ath atheros 5424/2424 on the CQ60 Presario
I never got the light to turn blue, but it does work. -Original Message- From: Kenneth kennet...@earthlink.net Sent: Sep 14, 2009 12:26 AM To: Jules Gilbert jules.sto...@gmail.com Cc: freebsd-questions@freebsd.org Subject: ath atheros 5424/2424 on the CQ60 Presario Anyone been able to use the ath driver on an atheros 5424/2424? I have a Compaq Presario CQ60 and can not get the wireless light to turn blue? -Original Message- From: Jules Gilbert jules.sto...@gmail.com Sent: Sep 13, 2009 7:14 PM To: Kenneth kennet...@earthlink.net Cc: freebsd-questions@freebsd.org, freebsd-...@freebsd.org, ges...@yahoo.com Subject: Re: configuring X on the Presario with the 8200M driver Thanks, guys! I intend to set aside some time late this week to try this. I bought one but have not been able to configure the X environment yet; I notice that PC-BSD comes up fine; I thought of doing that and copying the file, but that's about a half day or more of effort that way... Not good. Anyway, a couple questions... Is this likely to be compatible with FBSD 8.0? Or no, and I will just use 7.2. --jg On Sat, Sep 12, 2009 at 2:12 AM, Kenneth kennet...@earthlink.net wrote: Moving this discussion to freebsd-x11. I have a Presario CQ60 with the NVIDIA 8200M G, and X is working! Here are the steps to get there. Do everything as root: 1) Update your ports to the most recent. Follow the FreeBSD manual, section 4.5 Using the Ports Collection, nuke the contents of /usr/ports, and install a new base using portsnap or cvsup. 2) Install the nvidia-driver. # cd /usr/ports/x11-driver/nvidia-driver # make install clean (I built with options FREEBSD_AGP checked, ACPI checked, LINUX unchecked). 3) You can install 2 more optional tools for configuring the nvidia card settings. I have not used them, but I installed them. # cd /usr/ports/x11-driver/nvidia-settings # make install clean # cd /usr/ports/x11-driver/nvidia-xconfig # make install clean 4) I also installed the fbdev driver from X.Org. # cd /usr/ports/x11-drivers/xf86-video-fbdev # make install clean 5) Add the nvidia driver as a dynamically loaded kernel module. # cd /boot # vi loader.conf (you better know how to use vi to edit) --- add the line nvidia_load=YES --- it is the only line I have in my loader.conf file 6) Reboot the system # reboot 7) If you want to see the version you just installed (your versions may be newer than mine below)... # pkg_info | grep nvidia nvidia-driver-185.18.29 nvidia-settings-190.32 nvidia-xconfig-190.32 # pkg_info | grep fbdev xf86-video-fbdev-0.4.0_2 8) Generate your xorg.conf.new file. # cd /root # Xorg -configure 9) Edit the xorg.conf.new file. # vi xorg.conf.new --- change the line Driver nv to read Driver nvidia 10) Test the config file. # Xorg -config xorg.conf -retro --- you should get a grey screen and your mouse should work, especially if your mouse worked when installing FreeBSD --- to kill the test, press CTRL-ALT-BKSP 11) If everything worked, move and rename (drop the new extension) the config file to the /etc directory # mv xorg.conf.new /etc/X11/xorg.conf 12) Test again. Log in as another user belonging to the wheel group (or login as root). % startx --- you should get 3 green windows --- you can kill X by clicking on the large window on the left, and typing exit ___ 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: am I the only one, wrt gcc44 -- it is failing and I can't build octave or much else
I believe ports and packages to be 2 separate items. pkg_info hasto do with what packages you have installed. The ports system has to = do with creating the packages. Different mechanisms are available to manage the source tree that t he ports system uses to create packages. I believe each of these diff= erent mechanisms start with an entire tree in your /usr/ports directory, an= d then makes incremental changes to it based on published changes. Yo= u can even build or rebuild any of these ports at any time, even if you don= 't have the latest ports tree updates, or never install the built port.nbs= p; So, I believe the answer to your 1st question is that you begin wit= h a one size fits all, followed by updates that you manage. So far, I have not talked about installing yet. Once a port has been built, you can install it. Unless you save th= e built port as a package (the 'make package' command), you will not be abl= e to reinstall the built port if you clean it (the 'make clean' command).n= bsp; You can save as many built ports as packages as you want. = Each time you install a built port (the 'make install' command), the packag= es database gets updated in your system. This database is what pkg_in= fo uses. Some commands in the different mechanisms you have availablen= bsp;to manage your ports source, can be used to help select which pack ages need updating when you install an update to a package. About your 2nd question, I have no idea. I keep track of how to bu ild a system, keeping copies of config files, then I make backups= of file or data systems on an ongoing basis. Re gc44. FreeBSD 7.2 comes with 4.2 already installed. Maybe= when you installed 4.4 on top of it, something got messed up, or an option must be set for both to co-exist. I don't know, but I would try to k eep with the version that came with the system ( just an unjustified p= hobia I have about mixing new compiler binaries with old compiler binaries = ). -Original Message- From: Henry Olyer Sent: Nov 3, 2009 8:21 AM To: Kenneth Freidank Cc: freebsd-questions@freebsd.org, Chris Whitehouse Subject: Re: am I the only one, wrt gcc44 -- it is fa= iling and I can't build octave or much else I'm sorry fellows. You guys have given me great support and apparently I didn't get back = to you. I'm sorry, I'm not very polite some times. I will try t= o be more careful about this. Okay -- I was able to get my mouse working. I made a ServerFlags section in my xorg.conf and suddenly!, my mouse m= oved. (Here you can assume a remark not in evidence...) Next, I have wonderful X sessions now. Next, I am prepared to nuke the /usr/ports area if I am told to do tha= t -- I know it can be mechanically rebuilt in about an hour. (A past = note from Kenneth gave me this instruction and while I was a little nervous= I did it; And wow!, I was so impressed as I watched it come back.) Question: Does the rebuild process examine the pkg_info results = and load up the directory appropriately?. or is it one size fits all? Question: Does anyone have a solution for doing a general machin= e backup to one file? So that I can back the machine up and later, su bsequently, perform a simple restore. Because I've been using the mac= hine very heavily now, and I usually find that my own manual backups miss o= ne thing or another... You've probably had the same experience. = ;Now, I see others asking for such a feature/mechanism. What's possib= le? As for gcc44, I am fairly certain that it's actually broken -- that th= e port itself is broken and that it isn't my incompetence, that the port it= self is mis-configured or mis-coded. Oh., and in a conversation with an HP technical representative recentl= y, he told me that my taking down windoz to install FreeBSD constituted a = machine downgrade. On Mon, Nov 2, 2009 at 11:13 PM, Kenneth Freidank [1]kennet...@earthlink.net wrote: Here are partial listings of my co= nfig files. Add these entries to your config files and see if that do= es the trick. I can't be 100% sure that everything is required, but i= t is what I have, and it works. Attached is the xorg.conf file I gene= rated. Place it in the directory /etc/X11/. When you have done = these things, make sure your user belongs to the group wheel, then login.= To start X, give the command: startx You should get 3 wi= ndows, one of them labeled login in the title bar. If you type exi= t while inside this window, then return, that will end your X session. nb= sp;You will have some fatal error messages in your console window when X = finishes. Also, make sure you have installed the nvidia drivers per = my other postings. You can
Re: am I the only one, wrt gcc44 -- it is failing and I can't build octave or much else
Here are partial listings of my config files. Add these entries to your config files and see if that does the trick. I can't be 100% sure that everything is required, but it is what I have, and it works. Attached is the xorg.conf file I generated. Place it in the directory /etc/X11/. When you have done these things, make sure your user belongs to the group wheel, then login. To start X, give the command: startx You should get 3 windows, one of them labeled login in the title bar. If you type exit while inside this window, then return, that will end your X session. You will have some fatal error messages in your console window when X finishes. Also, make sure you have installed the nvidia drivers per my other postings. You can check if you have the package installed by typing: pkg_info | grep nvidia You should see at a minimum: nidia-driver-185.18.29 NVidia graphics card binary drivers for hardware OpenGL ren You have to build this packages and install it. This process is documented in the NetBSD documents and my other postings for installing FreeBSD on a Compaq Presario CQ60. File /etc/rc.conf linux_enable=YES moused_enable=YES keyrate=fast saver=star hald_enable=YES dbus_enable=YES vesa_load=YES File /boot/loader.conf nvidia_load=YES -Original Message- From: Henry Olyer henry.ol...@gmail.com Sent: Oct 26, 2009 2:53 AM To: freebsd-questions@freebsd.org Cc: Kenneth kennet...@earthlink.net, Chris Whitehouse cwhi...@onetel.com Subject: am I the only one, wrt gcc44 -- it is failing and I can't build octave or much else 'everything; is dying in /usr/ports/lang/gcc44 I know, (in all likelihood,) I'll have to scratch this area and do a complete re-install. Fine. The thing is, I didn't change anything to mess this area up in the first place. I've just been going to various directories in /usr/ports and saying, make install clean and now this... I was trying to put up octave when this happened. So I could use a little help here, please... I also want/need to run X, and my X session (just put up,) doesn't yet let me move the mouse. I installed hal and dbus but what do I do now? And where or where do I put the ServerFlags entry in my xorg.conf file. I'm sorry, I just don't know these things... === Building for gcc-4.4.2.20091006 echo stage3 stage_final gmake[1]: Entering directory `/usr/ports/lang/gcc44/work/build' gmake[2]: Entering directory `/usr/ports/lang/gcc44/work/build' gmake[3]: Entering directory `/usr/ports/lang/gcc44/work/build' rm -f stage_current gmake[3]: Leaving directory `/usr/ports/lang/gcc44/work/build' gmake[2]: Leaving directory `/usr/ports/lang/gcc44/work/build' gmake[2]: Entering directory `/usr/ports/lang/gcc44/work/build' gmake[3]: Entering directory `/usr/ports/lang/gcc44/work/build/libiberty' gmake[4]: Entering directory `/usr/ports/lang/gcc44/work/build/libiberty/testsuite' gmake[4]: Nothing to be done for `all'. gmake[4]: Leaving directory `/usr/ports/lang/gcc44/work/build/libiberty/testsuite' gmake[3]: Leaving directory `/usr/ports/lang/gcc44/work/build/libiberty' gmake[3]: Entering directory `/usr/ports/lang/gcc44/work/build/intl' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/lang/gcc44/work/build/intl' gmake[3]: Entering directory `/usr/ports/lang/gcc44/work/build/build-i386-portbld-freebsd7.2/libiberty' gmake[4]: Entering directory `/usr/ports/lang/gcc44/work/build/build-i386-portbld-freebsd7.2/libiberty/testsuite' gmake[4]: Nothing to be done for `all'. gmake[4]: Leaving directory `/usr/ports/lang/gcc44/work/build/build-i386-portbld-freebsd7.2/libiberty/testsuite' gmake[3]: Leaving directory `/usr/ports/lang/gcc44/work/build/build-i386-portbld-freebsd7.2/libiberty' gmake[3]: Entering directory `/usr/ports/lang/gcc44/work/build/build-i386-portbld-freebsd7.2/fixincludes' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/lang/gcc44/work/build/build-i386-portbld-freebsd7.2/fixincludes' gmake[3]: Entering directory `/usr/ports/lang/gcc44/work/build/zlib' true AR_FLAGS=rc CC_FOR_BUILD=cc CFLAGS=-g -fkeep-inline-functions CXXFLAGS=-g -fkeep-inline-functions CFLAGS_FOR_BUILD=-O2 -fno-strict-aliasing -pipe -I/usr/l ocal/include CFLAGS_FOR_TARGET=-g -O2 -fno-strict-aliasing -pipe -I/usr/local/include INSTALL=/usr/bin/install -c -o root -g wheel INSTALL_DATA=install -o root - g wheel -m 444 INSTALL_PROGRAM=install -s -o root -g wheel -m 555 INSTALL_SCRIPT=install -o root -g wheel -m 555 LDFLAGS= LIBCFLAGS=-g -O2 -fno-strict-aliasin g -pipe -I/usr/local/include LIBCFLAGS_FOR_TARGET=-g -O2 -fno-strict-aliasing -pipe -I/usr/local/include MAKE=gmake MAKEINFO=makeinfo --no-split --split-size=5000 000 --split-size=500 --split-size=500 PICFLAG= PICFLAG_FOR_TARGET= SHELL=/bin/sh EXPECT=expect RUNTEST=runtest RUNTESTFLAGS= exec_prefix=/usr/loca l infodir=/usr/local/info/gcc44 libdir=/usr/local/lib/gcc44 prefix=/usr/local
Re: looking for /usr/ports/x11-driver, not /usr/ports/x11-drivers
Sorry, the correct directory is #cd /usr/ports/x11/nvidia-driver -Original Message- From: Henry Olyer henry.ol...@gmail.com Sent: Oct 23, 2009 11:33 AM To: freebsd-questions@freebsd.org Subject: looking for /usr/ports/x11-driver, not /usr/ports/x11-drivers I'm trying to X (re)configure a CQ60, which is not so trivial to do... Kenneth CF once wrote: 2) Install the nvidia-driver. # cd /usr/ports/x11-driver/nvidia-driver # make install clean (I built with options FREEBSD_AGP checked, ACPI checked, LINUX unchecked). And this was not a typo. ___ 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
