X.Org 7-4 -> X.Org 7.5 upgrade -- issues and questions

Brandybuck said:
What's the best/easiest way to downgrade to Xorg 7.4? Thanks in advance.
Click to expand...

Did you find how, please? I like to downgrade too.
 
I don't know if it is the best way, but you could give portdowngrade a try:
/usr/ports/ports-mgmt/portdowngrade
I have not used it for XORG, but it worked for me with some other ports.
 
What are the issues that make you want to downgrade, guys? Maybe they can serve as a warning for others. I haven't run into problems with X.Org 7.5 (a Pidgin glitch aside).
 
DutchDaemon said:
@maplecookies, are you on 8-STABLE/amd64? That's my environment. It's not a biggie; I can live without Pidgin.
Click to expand...

I have no issues with pidgin either, 8-STABLE/amd64/nvidia-driver.
 
DutchDaemon, I have no problems with Pidgin & Xfce4 & Xorg 7.5 & 8.0-STABLE/i386. I suppose this must be something in your setup. Have you tried moving your ~/.purple and starting with default config? Might be Xfce/X.org config as well.
 
Well, I have reinstalled all ports, rebuilt the OS, rebuilt the kernel, switched to GENERIC ... I guess playing around with some dotfiles is the only option left ;) Thanks, I'll give it a twirl.

Edit: removing .purple changed nothing.
 
Well, progress after all. I fired up nvidia-settings and nvidia-xconfig, told it to 'rework' my xorg.conf (which was written by them anyway, and worked fine in any other way), and Pidgin starts. This must have been something weird ;)
 
Xorg 7.5 works smoothly and nice.
The other applications the same.
After a complete deinstall of all the packages.
I rebuilt everything from ports as usual.
 
Bunyan said:
Xorg 7.5 works smoothly and nice.
The other applications the same.
After a complete deinstall of all the packages.
I rebuilt everything from ports as usual.
Click to expand...

If I understood correct, first you deinstalled 7.4 and than install 7.5?
I will try downgrade.
 
games/simutrans is barfing for me now. Currently # portupgrade -uvfR simutrans\*-ing to see if that helps*. I have hope (though I'm a bit miffed that it's fnording rebuilding perl, oh well).

*It did, no more crashes.
 
Glad your figured it out, sorry, couldn't reply from work.

I am on 8.0-STABLE/i386 using xf86-video-nv driver.

Have yet to find something that doesn't work, even stuff that runs under linuxcompat like Citrix Receiver works really well.

FreeBSD still kicks a$$
 
Now this is fascinating. I just performed the upgrade, started evolution, and down went the X server. Restarted X, tried pidgin, and it crashed again. And I'm using a radeon card, not an nvidia. Now to see if I can get a backtrace.

Adam
 
Geeqie and Gimp which I use everyday work okay but Konqueror for example has problem also with dissapering icons, black bars...
Resolution I have same as before but looks like that is everything a little larger...
I use radeon too (ati drivers) and KDE 4.3.5
 
extension broken.

Hi

I did an upgrade. And what i see noticeable in
/var/log/Xorg.0.log is:
Code: 
record: record extension enabled at configure time.
record: this extension is known to be broken, disabling extension now.
record: [url]http://bugs.freedesktop.org/show_bug.cgi?id=20500[/url]

After reading the thread, installed libx11, didn't solved my case

Cheers
Tom-Pele
 
You'll likely need to wait for the fixes committed to the Xorg tree to make their way to FreeBSD ports. Is the lack of record extension causing a problem for you?

Adam
 
after portupgrade

adamk said:
You'll likely need to wait for the fixes committed to the Xorg tree to make their way to FreeBSD ports. Is the lack of record extension causing a problem for you?

Adam
Click to expand...

I did update my cvsup through
ports-supfile (current). And that was just after
portupgrade -var it begun.

When I test X -config /root/xorg.conf.new
from shell it has mixed colours. Aside from earlier black/white
windows.

I'll just wait for the patch as You say.

Tom-Pele
 
First, you should never use 'X -config /root/xorg.conf.new' to test Xorg. You should at least use 'X -retro -config /root/xorg.conf.new' though I would recommend just 'startx', honestly.

Having said that, it's very unlikely that the missing RECORD extension has anything to do with screwed up colors. They are certainly separate issues as RECORD should not be working for anyone using Xorg 7.5 in FreeBSD at the moment and it's certainly not causing this problem for others.

Can you grab a screenshot of the mixed color problem?

Adam
 
Hrm, so they've removed (or changed) the default "background" of the bare X server to solid black instead of the black/grey checkerboard? What a stupid change!!

I just spent 2 days re-installing every port on my desktop (300 so far) trying to figure out why the X server wasn't working with my old xorg.conf or xorg.conf.new or no xorg.conf ... only to find out today that everything was working from the get go!!!

On a whim, I ran xinit /usr/local/bin/xterm ... low and behold an xterm appeared. X by itself ... black screen. WTF!!

Wonder how many others will be tripped up by this assinine change.
 
phoenix said:
Hrm, so they've removed (or changed) the default "background" of the bare X server to solid black instead of the black/grey checkerboard? What a stupid change!!
Click to expand...
It has been black for quite some time. They made the change in 7.4, maybe even before I don't remember.
 
Still no X after upgrade FreeBSD 8.0-RELEASE-p2 amd64 nv driver

Still no X, even simply twm, after upgrade.
Normally I run fluxbox, and of course that didn't start either

About every 3 days, I do this:
pkgdb -F;portsclean -CDD;portsnap fetch update

On May 3 I did the above, followed by
portupgrade -a -v -e -l /var/tmp/portupgrade_`date +%Y%m%d_%H%M%S`
which is my normal habit, after first reading /usr/ports/UPDATING

This was successful, including all the xorg:
tail -1 /var/tmp/portupgrade_20100503_211221
+ x11/xorg (xorg-7.4_4)

Note: the above meant, as you know, that it upgraded the xorg port from 7.4_4, at that time, to xorg-7.5, as shown here:
pkg_info -XI xorg-7
xorg-7.5 X.Org complete distribution metaport

More details to demonstrate all ports upgrade successful
wc /var/tmp/portupgrade_20100503_211221
175 525 7219 /var/tmp/portupgrade_20100503_211221
egrep '^+' /var/tmp/portupgrade_20100503_211221 |wc
175 525 7219

Reboot:
upon startx, just a black screen
This was both as root and as user(as a user with no .xinitrc or with a simple xinitrc)

hald and dbus are running
pgrep -fl 'hald|dbus'
1398 hald-addon-storage: /dev/cd0
1389 hald-addon-mouse-sysmouse: /dev/ums0
1358 hald-runner
1354 /usr/local/sbin/hald
1207 /usr/local/bin/dbus-daemon --system

Not using a static xorg.conf
Xorg -configure seemed okay, normal black screen
Ran X -retro -config /root/xorg.conf.new and got the X
The only errors, which I don't think are pertinent were
(==) Using default built-in configuration (30 lines)
(EE) Failed to load module "fbdev" (module does not exist, 0)
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now.

Reboot
portsnap as above

Rebuilt all the ports
portupgrade -af
Every port (635) upgraded successfully

Reboot
startx
Still nothing put a black screen

.xinitrc (as a user) is either empty or simply
exec twm

Video card is
egrep 'NV: Found' /var/log/Xorg.0.log
(--) NV: Found NVIDIA GeForce 9800 GT at 02@00:00:0

The only error in the Xorg log is below, and I believe it's not relevant
(II) LoadModule: "fbdev"
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: "fbdev"
(EE) Failed to load module "fbdev" (module does not exist, 0)

All was working well before the upgrade
Any suggestions? Thanks in advance. Let me know if I've forgotten any relevant info.
uname -irp
8.0-RELEASE-p2 amd64 GENERIC
 
So X worked when you ran 'Xorg -retro -config /root/xorg.conf.new'?

What happens if you move /root/xorg.conf.new to /etc/X11/xorg.conf and simply run:

xinit /usr/local/bin/xterm

Does X start up with a single xterm?

Adam
 
You must log in or register to reply here.
Back
Top