I just went through the steps of upgrading two of my machines to Xorg 7.1. And it seems to run fine, after fumbling my way through it on one the second was much easier to complete. I do have a couple of issues, nothing imparing the day to day operations of the box itself, but both a pain. First, Cntrl-Alt-F[0-9] do not seem to work. No alternate consoles what so ever. I have Googled and not find anything that seems to be a match. I found a couple people mentioning that Cntrl-Alt-Bkspc no longer functioned, but that is actually working for me. This is on both of the systems where I tried the upgrade. Second, for some reason x11vnc, although working in that it runs and I can connect to the display, will not allow mouse or keyboard input. I even grabbed the source and compiled, same results. This is a bit of a pain as I often am at my wife's desk in another part of the house and like to bring my live display back there. I have even tried using krfb, which although allowing keyboard/mouse input, for some reason keeps disconnecting within 10 seconds using tight vncviewer on windows... Not sure if this is both systems as I typically do not vnc into my laptop... Any suggestions or pointers to reading would be appreciated. Thanks! Michael
On Oct 10, 06 08:35:32 -0400, Michael Letourneau wrote:
I just went through the steps of upgrading two of my machines to Xorg 7.1. And it seems to run fine, after fumbling my way through it on one the second was much easier to complete.
I do have a couple of issues, nothing imparing the day to day operations of the box itself, but both a pain.
First, Cntrl-Alt-F[0-9] do not seem to work. No alternate consoles what so ever. I have Googled and not find anything that seems to be a match. I found a couple people mentioning that Cntrl-Alt-Bkspc no longer functioned, but that is actually working for me. This is on both of the systems where I tried the upgrade.
Check /etc/X11/xorg.conf for the keyboard InputDevice section. It should
read Driver "kbd" (note the lower case). This is only a simple
possibility, though.
Try creating a new config with sax2 (a newer one from alpha as well, of
course).
Just an idea
Matthias
--
Matthias Hopf
On Oct 10, 06 08:35:32 -0400, Michael Letourneau wrote: [..snip..]
First, Cntrl-Alt-F[0-9] do not seem to work. No alternate consoles what so ever. I have Googled and not find anything that seems to be a match. I found a couple people mentioning that Cntrl-Alt-Bkspc no longer functioned, but that is actually working for me. This is on both of the systems where I tried the upgrade.
Check /etc/X11/xorg.conf for the keyboard InputDevice section. It should read Driver "kbd" (note the lower case). This is only a simple possibility, though.
Try creating a new config with sax2 (a newer one from alpha as well, of course).
Just an idea
Matthias
Good suggestions, unfortunately I did rebuild it using sax2 last night, and unfortunately still the same results there. My kbd inputdevice entry is as follows: Section "InputDevice" Driver "kbd" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbLayout" "us" Option "XkbModel" "pc104" Option "XkbRules" "xfree86" EndSection Which actually looks exactly like it did from my base default install of 10.1 way back when :( Unless there is a new option there thats not getting put in... But that actually does give me pause about my other issue with x11vnc. I seem to remember when I was playing with the vnc module in the xorg.conf long ago that it had some virtual drivers it stuck in there. I wonder if defining those might help my x11vnc issue... Thanks for the suggestions, if you have any others please let me know! Michael
Michael Letourneau wrote:
On Oct 10, 06 08:35:32 -0400, Michael Letourneau wrote:
[..snip..]
First, Cntrl-Alt-F[0-9] do not seem to work. No alternate consoles what so ever. I have Googled and not find anything that seems to be a match. I found a couple people mentioning that Cntrl-Alt-Bkspc no longer functioned, but that is actually working for me. This is on both of the systems where I tried the upgrade.
Check /etc/X11/xorg.conf for the keyboard InputDevice section. It should read Driver "kbd" (note the lower case). This is only a simple possibility, though.
Try creating a new config with sax2 (a newer one from alpha as well, of course).
Just an idea
Matthias
Good suggestions, unfortunately I did rebuild it using sax2 last night, and unfortunately still the same results there. My kbd inputdevice entry is as follows:
Section "InputDevice" Driver "kbd" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbLayout" "us" Option "XkbModel" "pc104" Option "XkbRules" "xfree86" EndSection
Which actually looks exactly like it did from my base default install of 10.1 way back when :( Unless there is a new option there thats not getting put in...
But that actually does give me pause about my other issue with x11vnc. I seem to remember when I was playing with the vnc module in the xorg.conf long ago that it had some virtual drivers it stuck in there. I wonder if defining those might help my x11vnc issue...
Thanks for the suggestions, if you have any others please let me know!
Michael
In the Subject you have Xorg 7.1. On my 10.1 machine the latest delivered by SUSE server is xorg-x11-server-glx-6.9.0-50.17 which I think may be buggy. The latest is 7.1 I believe. Does anyone know if SUSE might release a newer X server for 10.1 or will we have to wait for 10.2 ? Maybe this is related to the above.
Michael Letourneau wrote:
On Oct 10, 06 08:35:32 -0400, Michael Letourneau wrote:
[..snip..]
In the Subject you have Xorg 7.1. On my 10.1 machine the latest delivered by SUSE server is xorg-x11-server-glx-6.9.0-50.17 which I think may be buggy. The latest is 7.1 I believe. Does anyone know if SUSE might release a newer X server for 10.1 or will we have to wait for 10.2 ? Maybe this is related to the above.
Suse/Novell do not upgrade packages on a released version of Suse (as I understand it). They backport any security issues but they do not upgrade the components. So in order to upgrade to 7.1 on 10.1 I had to use an alternate repository that has Xorg 7.1 built for 10.1. The first time the process was somewhat painful, the second time I did it, it went easier. Essentially what I did was grab all the packages from the repository, download them locally. Drop down to runlevel 3, remove all the packages for Xorg 6.9, (which I suppose could be really risky as I did rpm --erase --nodeps <package> definitely not recommended for novices as you are telling the package system to remove the package and not care about any dependency issues). Then I did the same for sax2, and another set of packages I forget which. Then I went and added in the packages I downloaded with rpm -ivh <newpackage>, it would tell you if there was a conflict and if so you had to go erase another package... After it was done and I was up at runlevel 5, I went through and used SMART to try to clean up any dependency issues I had... Which I think it did properly... Hope that helps, but again, unless you are comfortable with what you are doing I would not recommend it... Michael
On Tuesday 10 October 2006 19:57, Michael Letourneau wrote:
Michael Letourneau wrote:
On Oct 10, 06 08:35:32 -0400, Michael Letourneau wrote:
[..snip..]
In the Subject you have Xorg 7.1. On my 10.1 machine the latest delivered by SUSE server is xorg-x11-server-glx-6.9.0-50.17 which I think may be buggy. The latest is 7.1 I believe. Does anyone know if SUSE might release a newer X server for 10.1 or will we have to wait for 10.2 ? Maybe this is related to the above.
Suse/Novell do not upgrade packages on a released version of Suse (as I understand it). They backport any security issues but they do not upgrade the components. So in order to upgrade to 7.1 on 10.1 I had to use an alternate repository that has Xorg 7.1 built for 10.1. The first time the process was somewhat painful, the second time I did it, it went easier.
Essentially what I did was grab all the packages from the repository, download them locally. Drop down to runlevel 3, remove all the packages for Xorg 6.9, (which I suppose could be really risky as I did rpm --erase --nodeps <package> definitely not recommended for novices as you are telling the package system to remove the package and not care about any dependency issues). Then I did the same for sax2, and another set of packages I forget which. Then I went and added in the packages I downloaded with rpm -ivh <newpackage>, it would tell you if there was a conflict and if so you had to go erase another package... After it was done and I was up at runlevel 5, I went through and used SMART to try to clean up any dependency issues I had... Which I think it did properly...
Hope that helps, but again, unless you are comfortable with what you are doing I would not recommend it...
Michael
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Not specifically for SuSE but might be worth a read anyhow. http://gentoo-wiki.com/HOWTO_Modular_Xorg -- /Rikard ----------------------------------------------------------------------------- email : rikard.j@rikjoh.com web : http://www.rikjoh.com mob: : +46 (0)763 19 76 25 ------------------------ Public PGP fingerprint ---------------------------- < 15 28 DF 78 67 98 B2 16 1F D3 FD C5 59 D4 B6 78 46 1C EE 56 >
On Tuesday 10 October 2006 19:57, Michael Letourneau wrote:
Michael Letourneau wrote:
On Oct 10, 06 08:35:32 -0400, Michael Letourneau wrote:
[..snip..]
[snip]
Not specifically for SuSE but might be worth a read anyhow. http://gentoo-wiki.com/HOWTO_Modular_Xorg
-- /Rikard
Thanks for the link, I thought it might have the solution to my alternate console issue, unfortunately I tried the change from xfree86 to xorg in the xkdb definition and it did not work. Anyone trying out 10.2 Alpha [1-5] ? I believe they are using 7.1 on there, curious if cntrl-alt-F[0-9] is working there. If so could you send me (off list) a copy of your xorg.conf? Thanks! Michael
On Oct 10, 06 13:21:15 -0400, Michael Letourneau wrote:
On Oct 10, 06 08:35:32 -0400, Michael Letourneau wrote: Good suggestions, unfortunately I did rebuild it using sax2 last night, and unfortunately still the same results there. My kbd inputdevice entry is as follows:
Section "InputDevice" Driver "kbd" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbLayout" "us" Option "XkbModel" "pc104" Option "XkbRules" "xfree86" EndSection
Looks good.
Which actually looks exactly like it did from my base default install of 10.1 way back when :( Unless there is a new option there thats not getting put in...
Still the driver shouldn't behave the way you're seing. Maybe Stefan can help here...
But that actually does give me pause about my other issue with x11vnc. I seem to remember when I was playing with the vnc module in the xorg.conf long ago that it had some virtual drivers it stuck in there. I wonder if defining those might help my x11vnc issue...
The last time I tried enabling in sax2 was perfectly enough, it included
all needed options and virtual device drivers.
Matthias
--
Matthias Hopf
On Oct 10, 06 13:21:15 -0400, Michael Letourneau wrote:
On Oct 10, 06 08:35:32 -0400, Michael Letourneau wrote: Good suggestions, unfortunately I did rebuild it using sax2 last night, and unfortunately still the same results there. My kbd inputdevice entry is as follows:
Section "InputDevice" Driver "kbd" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbLayout" "us" Option "XkbModel" "pc104" Option "XkbRules" "xfree86" EndSection
Looks good.
[snip] Following the link that was given for the gentoo site http://gentoo-wiki.com/HOWTO_Modular_Xorg , I did try changing the Option "XkbRules" "xfree86" to Option "XkbRules" "xorg" and restarting X, but still no go. :(
participants (4)
-
Matthias Hopf -
Michael Letourneau -
Rikard Johnels -
Robert Lewis