I'm not sure what's going on. I finally went from xorg-6.8.2-r2 to
xorg-7.
Everything seems to be working fine. (i'm happy that there wasn't much
issues) (yet??)
The only thing which is bugging me is the Switching Windows. (Alt-Tab)
in Gnome-2.14
When I do an Alt-Tab, the whole window (the curren
060924 Walter Dnes wrote:
> On Thu, Sep 21, 2006 at 05:24:44PM -0400, Philip Webb wrote
>> I've never quite understood why it's Ctl-Alt-F7 which returns,
>> Another test reveals that Ctl-Alt-F3 returns to the X session,
>> so perhaps the command to return uses the next free F key.
-- lots of inter
Resuming Nvidia with modular X proved to be easy using the Guide,
which anyway agrees to my home-made help file from previous occasions.
The ~x86 driver pkg 8774 offered no difficulties with kernel 2.6.18 ,
except that I had to add a line to xorg.conf :
Section "Monitor"
...
DisplaySize 28
On Thu, Sep 21, 2006 at 05:24:44PM -0400, Philip Webb wrote
> I've never quite understood why it's Ctl-Alt-F7 which returns,
> when the TTY's involved seem to be 1 & 2 . In fact,
> I've suppressed higher-numbered TTY 3-6 in /etc/inittab .
> Another test reveals that Ctl-Alt-F3 returns to the X s
060921 Philip Webb wrote:
> I've updated to modular X
> and everything seems to be working as before, but where is xorg.conf ?
Modular X does create its own version on the fly,
but it's better to have the file in /etc/X11 in case of further change.
On the raw console (outside X) I ran 'Xorg -co
Philip Webb wrote:
> 060922 Bo ?rsted Andresen wrote:
>
>> On Friday 22 September 2006 02:35, Philip Webb wrote:
>>
>>> I've updated to modular X
>>> and everything seems to be working as before, but where is xorg.conf ?
>>> root: X11> pwd
>>> /etc/X11
>>> root: X11> ls -l
>>>
060922 Bo ?rsted Andresen wrote:
> On Friday 22 September 2006 02:35, Philip Webb wrote:
>> I've updated to modular X
>> and everything seems to be working as before, but where is xorg.conf ?
>> root: X11> pwd
>> /etc/X11
>> root: X11> ls -l
>> total 8
>> drwxr-xr-x 2 root root 7
On Friday 22 September 2006 02:35, Philip Webb wrote:
> I've updated to modular X
[...]
> and everything seems to be working as before, but where is xorg.conf ?
>
> root: X11> pwd
> /etc/X11
> root: X11> ls -l
> total 8
> drwxr-xr-x 2 root root 72 Sep 20 15:56 Sessions
> -rwx
Philip Webb wrote:
> I've updated to modular X
>
> root: share> eix xorg-x11
> [I] x11-base/xorg-x11
> Available versions: [M]6.8.2-r8 [M]6.9.0-r3 7.0-r1 ~7.1
> Installed: 7.0-r1
>
> and everything seems to be working as before, but where is xorg.conf ?
>
> root: X11
I've updated to modular X
root: share> eix xorg-x11
[I] x11-base/xorg-x11
Available versions: [M]6.8.2-r8 [M]6.9.0-r3 7.0-r1 ~7.1
Installed: 7.0-r1
and everything seems to be working as before, but where is xorg.conf ?
root: X11> pwd
/etc/X11
root: X11> ls -
060922 Benno Schulenberg wrote:
> Philip Webb wrote:
>> I've never quite understood why it's Ctl-Alt-F7 which returns,
>> when the TTY's involved seem to be 1 & 2 .
> Because on most machines inittab tells init to start agetty
> on the first six VTs, and X then takes the first free VT.
>> Another t
Philip Webb wrote:
> I've never quite understood why it's Ctl-Alt-F7 which returns,
> when the TTY's involved seem to be 1 & 2 .
Because on most machines inittab tells init to start agetty on the
first six VTs, and X then takes the first free VT.
> In fact,
> I've suppressed higher-numbered TTY
060921 Andrew Frink wrote:
> On 9/20/06, Philip Webb <[EMAIL PROTECTED]> wrote:
>> I've just updated to modular X & everything seems to be working,
>> except that after Ctl-Alt-F2 I can't get back to X with Ctl-Alt-F7 .
>> I can get back to the original raw terminal with Ctl-Alt-F1 ,
>> which s
On Thursday 21 September 2006 14:16, Andrew Frink wrote:
> On 9/20/06, Philip Webb <[EMAIL PROTECTED]> wrote:
> > I've just updated to modular X & everything seems to be working,
> > except that after Ctl-Alt-F2 I can't get back to X with Ctl-Alt-F7 .
> > I can get back to the original raw termi
On 9/20/06, Philip Webb <[EMAIL PROTECTED]> wrote:
I've just updated to modular X & everything seems to be working,except that after Ctl-Alt-F2 I can't get back to X with Ctl-Alt-F7 .I can get back to the original raw terminal with Ctl-Alt-F1 ,which shows 3 identical error messages. I tried
I've just updated to modular X & everything seems to be working,
except that after Ctl-Alt-F2 I can't get back to X with Ctl-Alt-F7 .
I can get back to the original raw terminal with Ctl-Alt-F1 ,
which shows 3 identical error messages. I tried remerging Xkeyboard-config
(from a previous repl
> > Please file a bug with this information, xorg.conf, /var/log/Xorg.0.log
> > and emerge --info.
Sorry again. You said file a bug didn't you.
Must be the heat... I'm filing a bug now. :-\
--
// Andrew MacKenzie | http://www.edespot.com
// GPG public key: http://www.edespot.com/~amackenz
> > If I run "X -configure" it complains about XAACreateInfoRec when loading
> > i810_drv.so, and vgaHWGetIndex when loading "vga_drv.so." It also
> > complains about VBEExtendedInit when loading the VESA driver.
> Please file a bug with this information, xorg.conf, /var/log/Xorg.0.log
> and emerg
Matthew Daubenspeck wrote:
> (II) Loading /usr/lib/xorg/modules/libddc.so
> (II) Module ddc: vendor="X.Org Foundation"
> compiled for 7.0.0, module version = 1.0.0
> ABI class: X.Org Video Driver, version 0.8
>
> That's where it stops. I've ssh-ed in and tried to kill X (which is
>
I've already done the new modular upgrade on several machines and they
all worked perfectly, except my main multi video card machine. I have
some older S3 Virge PCI video cards that aren't playing nice with the
new xorg.
In VIDEO_CARDS I have nvidia and s3virge, and the proper drivers are
being c
Andrew MacKenzie wrote:
> My last email didn't seem to make it to the list, I hope this isn't a
> duplicate.
>
> I've converted 4 machines to modular X, and one is having an issue.
> My laptop (Thinkpad T43) is getting the following error when I start X:
>
> dlopen: /usr/lib/xorg/modules/drive
My last email didn't seem to make it to the list, I hope this isn't a
duplicate.
I've converted 4 machines to modular X, and one is having an issue.
My laptop (Thinkpad T43) is getting the following error when I start X:
dlopen: /usr/lib/xorg/modules/drivers/i810_drv.so: undefined symbol
vgaH
It appears that the nvidia driver wants something that isn't available
when the "minimal" use flag is present during the xorg-server
compile. Eliminating this use flag got rid of the unresolved symbols.
--
gentoo-user@gentoo.org mailing list
Heitor wrote:
> Hello,
>
> I dont know if it helps you butn I had the following problem.
>
> With the stable nvidia driver i got these "unresolved messages" and I
> couldn't load the module when I emerge the testing driver. I saw on
> the list that there was a
> "x11-drivers/nvidia-legacy-drivers"
Hello,
I dont know if it helps you butn I had the following problem.
With the stable nvidia driver i got these "unresolved messages" and I
couldn't load the module when I emerge the testing driver. I saw on
the list that there was a
"x11-drivers/nvidia-legacy-drivers" (I have a very old Geforce
John Blinka wrote:
> Symbol fbCloseScreen from module
> /usr/lib/xorg/modules/drivers/nvidia_drv.o is unresolved!
See how all your nvidia driver ends with .o instead of .so? That means
you didn't build the drivers with USE=dlloader (which is now set by
default).
Thanks,
Donnie
signature.asc
De
On 7/8/06, John Blinka <[EMAIL PROTECTED]> wrote:
Hi,
I've successfully upgraded to modular X on 4 machines without any
issues, but the 5th box is fighting me. The 5th box, a Dell Inspiron
8200, has an nvidia card, and I've used the proprietary nvidia
video drivers for years without problems.
Hi,
I've successfully upgraded to modular X on 4 machines without any
issues, but the 5th box is fighting me. The 5th box, a Dell Inspiron
8200, has an nvidia card, and I've used the proprietary nvidia
video drivers for years without problems. I've followed the
instructions in
http://www.gentoo
Thanks, this is what I will do.
BillK
On Tue, 2006-06-06 at 11:46 -0400, JimD wrote:
...
>
> unmerge x11-misc/xscreensaver.
>
> If you use Gnome emerge:
> gnome-extra/gnome-screensaver
>
--
gentoo-user@gentoo.org mailing list
W.Kenworthy wrote:
> I have just brought my X up to date (modular Xorg 7.1) and am finding
> that xscreensaver is crashing the xserver. Of course there is nothing
> in the logs, or onscreen as X either stops or reboots. Eventually it
> takes out the OS and a system reboot is required.
>
> Is any
W.Kenworthy wrote:
> I have just brought my X up to date (modular Xorg 7.1) and am finding
> that xscreensaver is crashing the xserver. Of course there is nothing
> in the logs, or onscreen as X either stops or reboots. Eventually it
> takes out the OS and a system reboot is required.
>
> Is anyo
Le mardi 06 juin 2006 à 12:49 +0800, W.Kenworthy a écrit :
> I have just brought my X up to date (modular Xorg 7.1) and am finding
> that xscreensaver is crashing the xserver. Of course there is nothing
> in the logs, or onscreen as X either stops or reboots. Eventually it
> takes out the OS and
I have just brought my X up to date (modular Xorg 7.1) and am finding
that xscreensaver is crashing the xserver. Of course there is nothing
in the logs, or onscreen as X either stops or reboots. Eventually it
takes out the OS and a system reboot is required.
Is anyone else seeing this (in which
Toby 'qubit' Cubitt wrote:
On Mon, Apr 03, 2006 at 08:23:41AM +0200, Alexander Skwar wrote:
Toby 'qubit' Cubitt wrote:
>The only downside to freeNX was it was more complicated to get
>working.
The big downside of NX for me is, that your session ends
as soon as NX is stopped. Not so with VNC (n
On Mon, Apr 03, 2006 at 08:23:41AM +0200, Alexander Skwar wrote:
> Toby 'qubit' Cubitt wrote:
>
> >The only downside to freeNX was it was more complicated to get
> >working.
>
> The big downside of NX for me is, that your session ends
> as soon as NX is stopped. Not so with VNC (no matter which
>
Toby 'qubit' Cubitt wrote:
The only downside to freeNX was it was more complicated to get
working.
The big downside of NX for me is, that your session ends
as soon as NX is stopped. Not so with VNC (no matter which
VNC).
Alexander Skwar
--
BTW: I have a better name for the software Micro
On Sun, Apr 02, 2006 at 04:26:00PM +0200, Rick van Hattem wrote:
> On Saturday 01 April 2006 23:47, Jim wrote:
> > On Sat, 2006-04-01 at 22:29 +0200, Alexander Skwar wrote:
> > > [EMAIL PROTECTED] /var/db/pkg $ epm -qf `which xmkmf `
> > > imake-1.0.1-r1
> > >
> > > Please file a bug against tightv
On Saturday 01 April 2006 23:47, Jim wrote:
> On Sat, 2006-04-01 at 22:29 +0200, Alexander Skwar wrote:
> > [EMAIL PROTECTED] /var/db/pkg $ epm -qf `which xmkmf `
> > imake-1.0.1-r1
> >
> > Please file a bug against tightvnc, as it's missing
> > a dependency.
>
> Will do.
>
> > BTW: Why use tightvn
Try using zebedee to both compress and encrypt (if neccessary) the vnc
connection. Provided a nice usability increase when using vnc through a
modem, though tightvnc was a little better than vnc.
BillK
On Sat, 2006-04-01 at 16:47 -0500, Jim wrote:
> On Sat, 2006-04-01 at 22:29 +0200, Alexander
On Sat, 2006-04-01 at 22:29 +0200, Alexander Skwar wrote:
> [EMAIL PROTECTED] /var/db/pkg $ epm -qf `which xmkmf `
> imake-1.0.1-r1
>
> Please file a bug against tightvnc, as it's missing
> a dependency.
Will do.
> BTW: Why use tightvnc at all? Realvnc 4 is as fast in
> my experience and there's
On Saturday 01 April 2006 22:29, Alexander Skwar wrote:
> BTW: Why use tightvnc at all? Realvnc 4 is as fast in
> my experience and there's still somebody workign on it -
> seeing that the last update to tightvnc is dated
> July 2005, I doubt that anybody maintains it anymore.
>
Realvnc lacks jpeg
Jim wrote:
Would this be a problem with the EBuild or with the app? I am try to
install tightvnc and get the following error.
Source unpacked.
Compiling source
in /var/tmp/portage/tightvnc-1.2.9-r1/work/vnc_unixsrc ...
/usr/portage/net-misc/tightvnc/tightvnc-1.2.9-r1.ebuild: line 41: xmkmf:
c
Would this be a problem with the EBuild or with the app? I am try to
install tightvnc and get the following error.
>>> Source unpacked.
>>> Compiling source
in /var/tmp/portage/tightvnc-1.2.9-r1/work/vnc_unixsrc ...
/usr/portage/net-misc/tightvnc/tightvnc-1.2.9-r1.ebuild: line 41: xmkmf:
command
43 matches
Mail list logo
