PS/2 mouse problem
I experienced that same issue one time, and the problem was the mouse protocall chosen during X configuration. For me the problem was corrected by choosing mouse systems when re-running the X configuration. i.e. as root: xorgcfg -text mode Byron - WA4GEG ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PS/2 mouse problem
When X system is loaded my mouse freezes on upper-right corner and when i try to move it then screen blinks. What could be wrong? Oops, correction: I experienced that same issue one time, and the problem was the mouse protocall chosen during X configuration. For me the problem was corrected by choosing mouse systems when re-running the X configuration. i.e. as root: xorgcfg -text mode xorgcfg -textmode Byron - WA4GEG ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
A strategic question
This posting doesn't contain a technical question about FreeBSD, rather a strategic one. Some time ago, I wanted to migrate to a Unix environment, because I wanted to have a secure, stable, convenient and efficient environment for developing and running programs, no longer having to buy a new PC with a new OS and applications software every 3 years to support Bill Gates' only goal (becoming and remaining the richest man of the USA). At the end of the 20th century, it took us only a few years to have to upgrade from Win 95 to Win 95SE, to Win 98, to Win 98SE, and to Win ME, only to remain with a poor OS. Now, when reinstalling my version of Windows XP, it takes me more time to download and install the SP2 than to install Windows XP. I wonder how people with a low-bandwidth Internet connection do to download the SP2 for Windows XP. I downloaded Solaris 10 and a lot of documentation about it, then installed Solaris 10. As opposed to Linux and free BSD implementations of UNIX, Solaris looks like a professionally developed operating system. It seems to be1 a very advanced operating system. However, I soon realized that, when one wants a yacht, it is not a good idea to acquire the Queen Mary II, just as it costs too much time to acquire a hotel to have a cup of coffee. Then I downloaded what I thought being one of the best Linux distributions, Suse Linux. I tried to install it, but the system got locked up by something so stupid as my nVidia modem. Together with the heterogeneous quality of Linux components, and not at all liking Linus Torvald's arrogance, I decided to abandon Linux. I came to FreeBSD, with the idea that it had a more homogeneous quality development model, downloaded the FreeBSD 6.0 boot CD and CD 1 and 2, and installed it on my PC, following the handbook. I knew UNIX is a toolkit intended to IT knowledge people, so it will never perform a breakthrough to the average desktop user. But my disappointment with FreeBSD was great. In fact, to install FreeBSD, one needs already a lot of knowledge about the system. To acquire that knowledge, one needs experience on an installed system. But to have an installed system, one needs already a lot of knowledge about the system. That's the problem. I too, coming from a M$ Windows Desktop environment, found the learning curve for Unix to be a straight vertical line. But I was tired of fighting worms, viruses and etc. and decided to invest in leaning Unix. And it didn't hurt matters reading somewhere that FreeBSD is the base for Mac OS-X. If it is secure enough for OS-X, it is plenty secure enough for my desktop workstation needs. The handbook doesn't tell you that, at the last chance message, you have to take out the boot CD and to insert CD 1. But if you don't do so, nothing gets installed. If you have CD1 you do not need the boot CD. Boot and install from CD1. Then CD2 will be called for during package_add as needed for the installation of user selected packages, that is, for those packages not residing on CD1. There is more than one way to do anything. And I've managed to not have to use a CLI editor ever (FreeBSD 4.x to 6.0) Although I do plan to learn vi. That's the beauty of FreeBSD. There are many paths and one can learn at ones own pace. For me this means getting the FreeBSD workstation PC up and going first and foremost so I can get some work done. To do this I choose from the install menu All system sources, binaries, docs and X window system. Once that is done and the user and root accounts are set up, making sure that the one standard user is a member of groups wheel and operator, exit the install process which reboots the system. Then I test that I log in as both user and root. All being well I proceed with the installation of KDE desktop. I like to use KDE's GUI editor KATE for doing the final system configuration, i.e. to set up ppp, devfs, fstab, configure the firewall and etc. And for my office needs, KDE (KOffice) has all the apps. I need which keeps me M$ free. Other FreeBSD enthusiast will have their own individual approach. I tried to setup an X Window environment (nVidia Geforce video adapter), but the horizontal and vertical refresh rates of the manufacturer didn't work, I had to experiment to find out the one X likes. Then I could startup X, only to not having configured at all my German keyboard. Keep in mind that the vertical refresh rate and horizontal scan rate to use are not those specifications of the video adapter, but rather those of your monitor. I tried to install emacs during installation, but it didn't succeed. Returning to the post-installation tasks after having installed the system resulted in a successfull installation of emacs (working only after a system reboot). I have had similar difficulties in installing packages from the CD during the main system installation. So these days I first install All system sources,
Re: X fails after upgrade to xorg-7.2; FreeBSD AMD64 w/ Radeon 9600 Pro
On Wednesday 20 June 2007 12:07:49 am Andy Fawcett wrote: One thing that *might* make a difference could be the drm stuff. I have it built into my kernel, you might be (auto)loading it as modules. Relevant lines from my kernel config: device radeondrm device drm Could be worth trying, if you don't already have it. Thanks for the tip. I'm just now getting back to this issue after installing 6.2 Stable AMD64 on a newly acquired hard drive. And I have the above drm lines in my kernel, but the display still goes blank when I startx. Some small headway: The problem with the display (which is now a SyncMaster 940t connected to the Radeon 9600 Pro DVI out) being driven out of range (I assume) and going blank was solved by setting the option NoAccel in the device section of my xorg.conf file. I've also tired both the ati and radeon drivers, and both give identical results. With acceleration disabled image tearing is bad, jumpy really, that is when one is dragging an X-term around on the desktop (xfce4.) But at least I've got a workable display now. I've been trying several and varied radeon driver option settings / combinations to see if I can get a viewable display with acceleration, but no luck yet. Maybe someone using the Radeon 9600 Pro [RV350 AP] video card with a similar TFT flatpanel will chime in with their experiences and / or workable settings. Byron - WA4GEG - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
X fails after upgrade to xorg-7.2; FreeBSD AMD64 w/ Radeon 9600 Pro[SOLVED]
This is weird, but the fix for my system (thanks Albert) is to force the AGP to PCI bus by setting the appropriate (or maybe inappropriate:-) option in the Device section of my xorg.conf, i.e: Section Device Option BusType PCI Identifier Card0 Driver radeon VendorName ATI Technologies Inc BoardName RV350 AP [Radeon 9600] BusID PCI:1:0:0 EndSection Haven't tried to play video clips yet, but dragging an xterm around the on desktop (xfce4) is very smooth now. Byron - WA4GEG ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
X fails after upgrade to xorg-7.2; FreeBSD AMD64 w/ Radeon 9600 Pro
Help, X was working just fine until I did a portupgrade of xorg 6.9.0 to 7.2. Looks like X is starting but my LCD monitor just goes black with the monitor's OSD reporting video input, out of range. I've gone back through Xorg configuration (via xorgcfg -textmode) and verified correct settings for my graphics card and the monitor's Horz. / Vert. scan frequencies etc., everything being in order. #Xorg -configure gives Driver ati, Boardname RV350 AP [Radeon 9600] and BusID PCI:1:0:0 I've also run #xorgcfg -textmode choosing Driver radeon and Card ** ATI Radeon (generic).. and still no luck. Please help. Anyone have their Radeon 9600 card working in Xorg-7.2 with just a basic / non accelerated setup, or any setup? Thanks, Byron System info: FreeBSD 6.2 stable (AMD64) Graphics card: ATI Radeon 9600 Pro (using the VGA monitor connection jack) Mainboard: MSI KT8 Neo2-F ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X fails after upgrade to xorg-7.2; FreeBSD AMD64 w/ Radeon 9600 Pro
On Sunday 17 June 2007 7:21:03 pm Mark Kirkwood wrote: Byron Campbell wrote: Help, X was working just fine until I did a portupgrade of xorg 6.9.0 to 7.2. Looks like X is starting but my LCD monitor just goes black with the monitor's OSD reporting video input, out of range. I've gone back through Xorg configuration (via xorgcfg -textmode) and verified correct settings for my graphics card and the monitor's Horz. / Vert. scan frequencies etc., everything being in order. #Xorg -configure gives Driver ati, Boardname RV350 AP [Radeon 9600] and BusID PCI:1:0:0 I've also run #xorgcfg -textmode choosing Driver radeon and Card ** ATI Radeon (generic).. and still no luck. Please help. Anyone have their Radeon 9600 card working in Xorg-7.2 with just a basic / non accelerated setup, or any setup? Thanks, Byron System info: FreeBSD 6.2 stable (AMD64) Graphics card: ATI Radeon 9600 Pro (using the VGA monitor connection jack) Mainboard: MSI KT8 Neo2-F I've seen this with VGA connections - e.g I've a 9550 (RV350 AS) and for DVI connection it works fine with the file generated by 'Xorg -configure' with accel and drm, but with VGA fails with 'out of range'. I needed to tell it which display resolution to use by adding a 'Modes' clause to the Display subsection of xorg.conf e.g: Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 24 Modes 1680x1050 # whatever mode your monitor uses here EndSubSection EndSection Cheers Mark Thanks for the suggestion Mark. I do have the modes entered, and even set it to the single mode of 1280x1024 but no luck. I went back and ran Xorg -configure again, and noted the following error messages: dlopen: /usr/local/lib/xorg/modules/drivers//atimisc_drv.so: Undefined symbol ATIMemoryTypeNames_88800CX (EE) Failed to load /usr/local/lib/xorg/modules/drivers//atimisc_drv.so (EE) Failed to load module atimisc (loader failed, 7) (++) Using config file: /root/xorg.conf.new (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (**) RADEON(0) : RADEONPreInit atimisc_drv.so is present in the above mentioned directory. My graphics card is the PowerColor ATI Radeon 9600 Pro (RV350 AP) Byron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X fails after upgrade to xorg-7.2; FreeBSD AMD64 w/ Radeon 9600 Pro
On Sunday 17 June 2007 10:23:19 pm Mark Kirkwood wrote: AFAICS the symbol is defined in: /usr/local/lib/xorg/modules/drivers/ati_drv.so e.g: $ nm ati_drv.so|grep ATIMemoryTypeNames_88800CX b5c0 D ATIMemoryTypeNames_88800CX What does it show on your system (I'm wondering if your ati drivers have not been upgraded properly). Ah, good point. The output here is: 00e940 D ATIMemoryTypeNames_88800CX -- Byron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X fails after upgrade to xorg-7.2; FreeBSD AMD64 w/ Radeon 9600 Pro
On Monday 18 June 2007 7:52:55 pm Mark Kirkwood wrote: Byron Campbell wrote: On Sunday 17 June 2007 10:23:19 pm Mark Kirkwood wrote: AFAICS the symbol is defined in: /usr/local/lib/xorg/modules/drivers/ati_drv.so e.g: $ nm ati_drv.so|grep ATIMemoryTypeNames_88800CX b5c0 D ATIMemoryTypeNames_88800CX What does it show on your system (I'm wondering if your ati drivers have not been upgraded properly). Ah, good point. The output here is: 00e940 D ATIMemoryTypeNames_88800CX Well - seems to be defined there hmmm. not sure why you are getting 'undefined symbol' in atimisc_drv.so in that case. I am wondering if the problem is tied up with amd64 specifically - hopefully someone else will have some ideas :-). In the meantime you could hack your xorg.conf to use 'vesa' driver and see if you can actually startup X - try adding modeline settings in there for your monitor if you still get 'out of range' (tho I must say I've *never* needed to put them in with Xorg...). Also worth trying might be borrowing a DVI cable (assuming your monitor has a DVI input) and seeing if X works with it connected instead of the VGA one. Cheers Mark Thanks for the input Mark. I did a make deinstall / reinstall of both xorg-7.2 and xorg-drivers-7.2. Xorg -configure no longer reports the undefind symbol but I still get a black screen when testing the config, with out of range OSD when using a VGA to monitor cable, and just a black screen (no OSD message) with the DVI cable. Tried a second monitor also, same results. And under these conditions I can't Alt F2 etc. to console, but must hit the reset for a dirty reboot. Xorg -configure now reports: (++) Using config file: /root/xorg.conf.new (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (**) RADEON(0): RADEONPreInit Manually doing the config by running xorgcfg -textmode gives a different BusID in the xorg.conf file -- BusID PCI:1:0:0 Andy's xorg.conf is identical to mine, except for the Horz / Vert monitor scan frequencies of course. And I've tried the vesa driver with the same blank / black screen results. I'm also getting a sporadic stray irq7 kernel message from time to time. Something weird is going on, huh? Booted Knoppix-Live and it runs just fine. Copied its xorg.conf detected mode lines into FreeBSD xorg.conf but still no luck. Thanks Andy, Mark for your help. But it looks like it is time for plan #2; Reinstall from scratch but no X, cvsup ports to latest and then do a fresh install of xorg-7.2. Maybe this weekend's project... Best regards, Byron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
