[branden@deadbeast.net: [picone@titan.eti.br: xf86cfg problems]]
Temporarily gone. Explanation cut; i'm tired of typing it. (archives full explanation.) - Forwarded message from Branden Robinson <[EMAIL PROTECTED]> - Envelope-to: [EMAIL PROTECTED] Delivery-date: Fri, 08 Dec 2000 09:28:26 -0800 Resent-Date: Fri, 8 Dec 2000 09:24:50 -0800 (PST) X-Envelope-Sender: [EMAIL PROTECTED] Date: Fri, 8 Dec 2000 12:27:19 -0500 To: debian-x@lists.debian.org Subject: [EMAIL PROTECTED]: xf86cfg problems] Mail-Followup-To: debian-x@lists.debian.org User-Agent: Mutt/1.2.5i From: [EMAIL PROTECTED] (Branden Robinson) Resent-Message-ID: <[EMAIL PROTECTED]> Resent-From: debian-x@lists.debian.org X-Mailing-List: archive/latest/1891 X-Loop: debian-x@lists.debian.org Precedence: list Resent-Sender: [EMAIL PROTECTED] Resent-Bcc: - Forwarded message from Reinaldo Picone Barbosa <[EMAIL PROTECTED]> - From: Reinaldo Picone Barbosa <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: xf86cfg problems Date: Fri, 08 Dec 2000 13:04:37 -0200 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.4.0-test10 i586) X-Accept-Language: en Hi Branden, I am trying to use xf86cfg for a long time but I allways receive the same message: "Cannot open Cards database." I am using the last package version (4.0.1-10). What can I do? What should I do? ;) Tkx, Reinaldo Picone - End forwarded message - -- G. Branden Robinson| If you make people think they're Debian GNU/Linux | thinking, they'll love you; [EMAIL PROTECTED] | but if you really make them think, http://deadbeast.net/~branden/ | they'll hate you. - End forwarded message - -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: r128 driver still borked in XF4.0.1-9pre10
Michael Flaig wrote: > > > > > Does XF4 work on your Pismo now ? > > > > > > > > No, not the -8 packages. Waiting for new ones... > > > > > > Have you downloaded the xfree4 from deb > > > http://people.debian.org/~branden/ woody/powerpc/ > > > > > > they are now -10 ... > > > > Well, I would have if they were still there... The only file in the > > powerpc directory is currently Packages.gz . > > Strange... I can get them all ... I just pointed the browser at http://people.debian.org/~branden/woody/powerpc/ again, only Packages.gz, no .debs ... > > > the bug of -8 packages is fixed but now the packages hang my pismo which > > > > > > is my biggest problem at all. > > > > I have the same problem on my Pismo. That is, actually the screen isn't > > black for me but has an interesting gradient which slowly changes it's > > color and brightness :) The machine is dead as can be. > > > > The strange thing is: The same happens if I take the r128_drv.o from one > > of my build trees, which work as a whole. So the problem doesn't seem to > > be just in the driver. > > Yes I will test it with an Kernel2.4 ... perhaps I'll find time to compile > it this weekend. ... r128_drv.o is the X driver module. My suspicion is that there is a problem in another part of X. It is virtually impossible that this is a kernel problem (I'm using 2.4.0-test11). Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project
Re: the continuing adventures of XFree86 4.0.1
"Christian T. Steigies" wrote: > > On Thu, Dec 07, 2000 at 11:30:15PM +0100, Michel Dänzer wrote: > > "Christian T. Steigies" wrote: > > > > > I have no PCI bus, I don't see PCI mentioned in the config file, is > > > there a way to stop loading that? > > > > Have you worked on the PCI code now? On PPC it also works without PCI, and > > I think it also loads that module, not sure though (I could ask on the > > APUS lists if you'd like). > I did not work on the pci code, I just changed it, like on ppc, to use the > generic(?) linuxpci code (see debian/patches/500_*, I only added Mc68020 to > the long list of non-i386 arches). But something must be different because it doesn't segfault on PPC even if there is no PCI at all. > Please ask some APUS people, I know Ken Tyler is interested to get X4.0 > working on his PPC Amiga. It's working fine on APUS (I made the glint driver work on our Permedia2 boards :), Ken is trying to get the s3virge driver going for his CV64/3D. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project
Re: 24+8 bit color depth overlay for ATI 3D RagePro?
Louis Tsui wrote: > Is 24+8 bit color depth overlay supported for ATI 3D RagePro by XF 4.0.1? Hardly. The only drivers I know support this are glint and mga. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project
[branden@deadbeast.net: [picone@titan.eti.br: xf86cfg problems]]
Temporarily gone. Explanation cut; i'm tired of typing it. (archives full explanation.) - Forwarded message from Branden Robinson <[EMAIL PROTECTED]> - Envelope-to: sarnold@localhost Delivery-date: Fri, 08 Dec 2000 09:28:26 -0800 Resent-Date: Fri, 8 Dec 2000 09:24:50 -0800 (PST) X-Envelope-Sender: [EMAIL PROTECTED] Date: Fri, 8 Dec 2000 12:27:19 -0500 To: [EMAIL PROTECTED] Subject: [[EMAIL PROTECTED]: xf86cfg problems] Mail-Followup-To: [EMAIL PROTECTED] User-Agent: Mutt/1.2.5i From: [EMAIL PROTECTED] (Branden Robinson) Resent-Message-ID: Resent-From: [EMAIL PROTECTED] X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/1891 X-Loop: [EMAIL PROTECTED] Precedence: list Resent-Sender: [EMAIL PROTECTED] Resent-Bcc: - Forwarded message from Reinaldo Picone Barbosa <[EMAIL PROTECTED]> - From: Reinaldo Picone Barbosa <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: xf86cfg problems Date: Fri, 08 Dec 2000 13:04:37 -0200 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.4.0-test10 i586) X-Accept-Language: en Hi Branden, I am trying to use xf86cfg for a long time but I allways receive the same message: "Cannot open Cards database." I am using the last package version (4.0.1-10). What can I do? What should I do? ;) Tkx, Reinaldo Picone - End forwarded message - -- G. Branden Robinson| If you make people think they're Debian GNU/Linux | thinking, they'll love you; [EMAIL PROTECTED] | but if you really make them think, http://deadbeast.net/~branden/ | they'll hate you. - End forwarded message - -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to start X during bootup as user
About starting X from init. --- This works: # tail -1 /etc/inittab t0:2:respawn:/root/bin/runx # cat /root/bin/runx #!/bin/sh /usr/bin/X11/X :1 vt10 & pid=$! sleep 2 export DISPLAY=:1 set > /tmp/set.log /usr/bin/X11/xterm >& /tmp/x.log # or your X application kill $! # or wait $! # grep PATH /tmp/set.log PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin # pstree init-+-atd ... |-runx-+-XF86_SVGA | `-xterm---bash ... And init restarts X when your application finishes. You have probably missed setting PATH to the right thing. Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 70 511 97 84 Computers Sweden Consulting --- From: Joshua Shagam <[EMAIL PROTECTED]> Subject: Re: How to start X during bootup as user Date: Fri, 8 Dec 2000 09:07:04 -0700 > On Fri, Dec 08, 2000 at 09:51:07AM +0100, Cajus Pollmeier wrote: > > Am Friday 08 December 2000 09:33 schrieb Joshua Shagam: > > > Ah, okay, that makes more sense. The shellscript is probably the easiest > > > way in that case. Try starting up a getty using your shellscript instead > > > of /bin/login; I believe you'd want to add '-l /path/to/the/shellscript' > > > to > > > the end of one of your getty lines in your /etc/inittab. > > > > Currently I'm trying it this way: > > X:2:respawn:/etc/init.d/kiosk > > > > But it doesn't work the way as expected - same error than before. What do > > you > > mean with "-l "? I can't find any options starting with "-l" for getty. > > At least in the version of getty I have installed (in util-linux 2.10q-1), > -l specifies an alternate to /bin/login: > >getty [-ihLmnw] [-f issue_file] [-l login_program] [-I >init] [-t timeout] [-H login_host] port baud_rate,... >[term] > > ... > >-l login_program > Invoke the specified login_program instead of > /bin/login. This allows the use of a non-standard > login program (for example, one that asks for a > dial-up password or that uses a different password > file). > > > -- > Joshua Shagam /"\ ASCII Ribbon Campaign > [EMAIL PROTECTED] \ / No HTML/RTF in email > www.cs.nmsu.edu/~joshagam X No Word docs in email > mp3.com/fluffyporcupine/ \ Respect for open standards > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: r128 driver still borked in XF4.0.1-9pre10
Michael Flaig wrote: > > > > > Does XF4 work on your Pismo now ? > > > > > > > > No, not the -8 packages. Waiting for new ones... > > > > > > Have you downloaded the xfree4 from deb > > > http://people.debian.org/~branden/ woody/powerpc/ > > > > > > they are now -10 ... > > > > Well, I would have if they were still there... The only file in the > > powerpc directory is currently Packages.gz . > > Strange... I can get them all ... I just pointed the browser at http://people.debian.org/~branden/woody/powerpc/ again, only Packages.gz, no .debs ... > > > the bug of -8 packages is fixed but now the packages hang my pismo which > > > >is my biggest problem at all. > > > > I have the same problem on my Pismo. That is, actually the screen isn't > > black for me but has an interesting gradient which slowly changes it's > > color and brightness :) The machine is dead as can be. > > > > The strange thing is: The same happens if I take the r128_drv.o from one > > of my build trees, which work as a whole. So the problem doesn't seem to > > be just in the driver. > > Yes I will test it with an Kernel2.4 ... perhaps I'll find time to compile > it this weekend. ... r128_drv.o is the X driver module. My suspicion is that there is a problem in another part of X. It is virtually impossible that this is a kernel problem (I'm using 2.4.0-test11). Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: the continuing adventures of XFree86 4.0.1
"Christian T. Steigies" wrote: > > On Thu, Dec 07, 2000 at 11:30:15PM +0100, Michel Dänzer wrote: > > "Christian T. Steigies" wrote: > > > > > I have no PCI bus, I don't see PCI mentioned in the config file, is > > > there a way to stop loading that? > > > > Have you worked on the PCI code now? On PPC it also works without PCI, and > > I think it also loads that module, not sure though (I could ask on the > > APUS lists if you'd like). > I did not work on the pci code, I just changed it, like on ppc, to use the > generic(?) linuxpci code (see debian/patches/500_*, I only added Mc68020 to > the long list of non-i386 arches). But something must be different because it doesn't segfault on PPC even if there is no PCI at all. > Please ask some APUS people, I know Ken Tyler is interested to get X4.0 > working on his PPC Amiga. It's working fine on APUS (I made the glint driver work on our Permedia2 boards :), Ken is trying to get the s3virge driver going for his CV64/3D. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 24+8 bit color depth overlay for ATI 3D RagePro?
Louis Tsui wrote: > Is 24+8 bit color depth overlay supported for ATI 3D RagePro by XF 4.0.1? Hardly. The only drivers I know support this are glint and mga. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to start X during bootup as user
About starting X from init. --- This works: # tail -1 /etc/inittab t0:2:respawn:/root/bin/runx # cat /root/bin/runx #!/bin/sh /usr/bin/X11/X :1 vt10 & pid=$! sleep 2 export DISPLAY=:1 set > /tmp/set.log /usr/bin/X11/xterm >& /tmp/x.log # or your X application kill $! # or wait $! # grep PATH /tmp/set.log PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin # pstree init-+-atd ... |-runx-+-XF86_SVGA | `-xterm---bash ... And init restarts X when your application finishes. You have probably missed setting PATH to the right thing. Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 70 511 97 84 Computers Sweden Consulting --- From: Joshua Shagam <[EMAIL PROTECTED]> Subject: Re: How to start X during bootup as user Date: Fri, 8 Dec 2000 09:07:04 -0700 > On Fri, Dec 08, 2000 at 09:51:07AM +0100, Cajus Pollmeier wrote: > > Am Friday 08 December 2000 09:33 schrieb Joshua Shagam: > > > Ah, okay, that makes more sense. The shellscript is probably the easiest > > > way in that case. Try starting up a getty using your shellscript instead > > > of /bin/login; I believe you'd want to add '-l /path/to/the/shellscript' to > > > the end of one of your getty lines in your /etc/inittab. > > > > Currently I'm trying it this way: > > X:2:respawn:/etc/init.d/kiosk > > > > But it doesn't work the way as expected - same error than before. What do you > > mean with "-l "? I can't find any options starting with "-l" for getty. > > At least in the version of getty I have installed (in util-linux 2.10q-1), > -l specifies an alternate to /bin/login: > >getty [-ihLmnw] [-f issue_file] [-l login_program] [-I >init] [-t timeout] [-H login_host] port baud_rate,... >[term] > > ... > >-l login_program > Invoke the specified login_program instead of > /bin/login. This allows the use of a non-standard > login program (for example, one that asks for a > dial-up password or that uses a different password > file). > > > -- > Joshua Shagam /"\ ASCII Ribbon Campaign > [EMAIL PROTECTED] \ / No HTML/RTF in email > www.cs.nmsu.edu/~joshagam X No Word docs in email > mp3.com/fluffyporcupine/ \ Respect for open standards > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: building xfree86 4 for debian/arm
On Fri, Dec 08, 2000 at 06:09:51PM +, Peter Maydell wrote: > # remove the upstream symlink X -> XFree86 > rm /.1/usr/local/src/xfree86-4.0.1/debian/tmp/usr/X11R6/bin/X > rm: cannot remove > `/.1/usr/local/src/xfree86-4.0.1/debian/tmp/usr/X11R6/bin/X': No such file or > directory > make: *** [debian/stampdir/install] Error 1 > > This symlink does not exist because the XFree86 server binary was not built > in the first place and therefore no symlink was created. That's bad. > I'm not sure why the server isn't being built; does this imply an error in a > configuration file somewhere or does it mean that there is no upstream > support for the arm architecture? Possibly both. > In particular, the fact that xc/config/cf/xfree86.cf does not mention > Arm32Architecture at all seems somewhat suspicious... Yes. > I have a complete (3MB!) build log generated using script, so can look > through it for anything if necessary. > > [Would I be better off asking this question of the debian-arm list?] The actual porting will probably have to be done by someone familiar with the ARM, but something could likely be cooked up fairly quickly, based on the ARM patches for XFree86 3.x. -- G. Branden Robinson | Debian GNU/Linux| // // // / / [EMAIL PROTECTED] | EI 'AANIIGOO 'AHOOT'E http://www.debian.org/~branden/ | pgpQng2yr4xvT.pgp Description: PGP signature
building xfree86 4 for debian/arm
Has anybody had any success in building xfree86 4 for debian/arm? I tried building 4.0.1-10pre11v1 from the source packages at people.debian.org/~branden/woody/ this successfully made it through the process of building binaries and installing them into the debian/tmp directory, but then fell over trying to remove a non-existent symlink: # remove the upstream symlink X -> XFree86 rm /.1/usr/local/src/xfree86-4.0.1/debian/tmp/usr/X11R6/bin/X rm: cannot remove `/.1/usr/local/src/xfree86-4.0.1/debian/tmp/usr/X11R6/bin/X': No such file or directory make: *** [debian/stampdir/install] Error 1 This symlink does not exist because the XFree86 server binary was not built in the first place and therefore no symlink was created. I'm not sure why the server isn't being built; does this imply an error in a configuration file somewhere or does it mean that there is no upstream support for the arm architecture? In particular, the fact that xc/config/cf/xfree86.cf does not mention Arm32Architecture at all seems somewhat suspicious... I have a complete (3MB!) build log generated using script, so can look through it for anything if necessary. [Would I be better off asking this question of the debian-arm list?] Peter Maydell
[stuart@apk.net: root-only access to X & my fix]
- Forwarded message from Stuart Krivis <[EMAIL PROTECTED]> - From: Stuart Krivis <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: root-only access to X & my fix Date: Fri, 8 Dec 2000 10:12:21 -0500 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Real-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> X-Mailer: Mutt 0.95.6i Branden, I've been running woody, and X 4.0.whatever. :-) We had a power event here last night that was a result of another event last weekend. So, my desktop machine was shut down last weekend and last night (Thursday the 7th). I had no problems when I powered it up after last weekend. It was smooth sailing all the way. This morning, however, I ran into a problem where I could not run X as anything but root. I tried a reinstall of most of the X pieces-parts using apt-get install --reinstall That didn't fix it. I went looking through the docs and found reference to "Xwrapper." But it seems that Debian has no Xwrapper. :-) So, the suggested fix of changing the call of X to Xwrapper in xserverrc didn't bring me joy. What I wound up doing is changing /etc/X11/Xwrapper.config I changed the line that said allowed_users=rootonly to be allowed_user=console That seems to have done the trick and I am working away in X now. Hurray! I can't pinpoint anything, but it would seem that something broke between 12-1 and 12-7. Hope this helps you or someone. :-) Regards, Stu -- Stuart Krivis[EMAIL PROTECTED] Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped - End forwarded message - -- G. Branden Robinson|Somewhere, there is a .sig so funny that Debian GNU/Linux |reading it will cause an aneurysm. This [EMAIL PROTECTED] |is not that .sig. http://deadbeast.net/~branden/ | pgpDloq5RxayQ.pgp Description: PGP signature
[picone@titan.eti.br: xf86cfg problems]
- Forwarded message from Reinaldo Picone Barbosa <[EMAIL PROTECTED]> - From: Reinaldo Picone Barbosa <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: xf86cfg problems Date: Fri, 08 Dec 2000 13:04:37 -0200 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.4.0-test10 i586) X-Accept-Language: en Hi Branden, I am trying to use xf86cfg for a long time but I allways receive the same message: "Cannot open Cards database." I am using the last package version (4.0.1-10). What can I do? What should I do? ;) Tkx, Reinaldo Picone - End forwarded message - -- G. Branden Robinson| If you make people think they're Debian GNU/Linux | thinking, they'll love you; [EMAIL PROTECTED] | but if you really make them think, http://deadbeast.net/~branden/ | they'll hate you. pgpwDVImeEQ1C.pgp Description: PGP signature
xlibs package install error
hi all, FYI, the xlibs package produces the following error on my system (woody) Preparing to replace xlibs 4.0.1-7 (using .../xlibs_4.0.1-10_i386.deb) ... Unpacking replacement xlibs ... dpkg: error processing /var/cache/apt/archives/xlibs_4.0.1-10_i386.deb (--unpack): trying to overwrite `/usr/X11R6/lib/X11/app-defaults', which is also in package xcolorsel dpkg-deb: subprocess paste killed by signal (Broken pipe) this is a new problem, occuring since v4.0.1-9 (maybe -8, not sure). the package causing the conflict is not constant, as i have received the same error mentioning groff, xscreensaver and i think another package as well btw, thanks branden for a great job! i'd like to assist, but i would be worse than useless, given the level of my skills! cheers, john
Read more carefully; mine is the opposite problem.
On Fri, Dec 08, 2000 at 04:50:13PM +0100, Charl P. Botha wrote: > > Please excuse this noise, but whatever the hell happened with searching a > particular mailing list archive before angering everyone on it with a > question that's been answered at least 10 times in the same week?!! > > I'm referring to the whole "user not authorized to run the X server" > issue... I have been following this mailing list fairly well for a while, but in case I missed something, I just checked the archive. Yes, I suffered from the user authorization problem too, but now I have the OPPOSITE problem. My message indicated that now startx and xinit are the ones that WORK for me and that now xdm and gdm are the ones that DON'T WORK. I hope that I haven't angered anyone; I merely posted a message that I thought (and still think) has not been answered. -- Thomas E. Vaughan <[EMAIL PROTECTED]> CIMMS/NSSL, Norman, OK, USA
Re: How to start X during bootup as user
On Fri, Dec 08, 2000 at 09:51:07AM +0100, Cajus Pollmeier wrote: > Am Friday 08 December 2000 09:33 schrieb Joshua Shagam: > > Ah, okay, that makes more sense. The shellscript is probably the easiest > > way in that case. Try starting up a getty using your shellscript instead > > of /bin/login; I believe you'd want to add '-l /path/to/the/shellscript' to > > the end of one of your getty lines in your /etc/inittab. > > Currently I'm trying it this way: > X:2:respawn:/etc/init.d/kiosk > > But it doesn't work the way as expected - same error than before. What do you > mean with "-l "? I can't find any options starting with "-l" for getty. At least in the version of getty I have installed (in util-linux 2.10q-1), -l specifies an alternate to /bin/login: getty [-ihLmnw] [-f issue_file] [-l login_program] [-I init] [-t timeout] [-H login_host] port baud_rate,... [term] ... -l login_program Invoke the specified login_program instead of /bin/login. This allows the use of a non-standard login program (for example, one that asks for a dial-up password or that uses a different password file). -- Joshua Shagam /"\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML/RTF in email www.cs.nmsu.edu/~joshagam X No Word docs in email mp3.com/fluffyporcupine/ \ Respect for open standards
Re: building xfree86 4 for debian/arm
On Fri, Dec 08, 2000 at 06:09:51PM +, Peter Maydell wrote: > # remove the upstream symlink X -> XFree86 > rm /.1/usr/local/src/xfree86-4.0.1/debian/tmp/usr/X11R6/bin/X > rm: cannot remove `/.1/usr/local/src/xfree86-4.0.1/debian/tmp/usr/X11R6/bin/X': No >such file or directory > make: *** [debian/stampdir/install] Error 1 > > This symlink does not exist because the XFree86 server binary was not built > in the first place and therefore no symlink was created. That's bad. > I'm not sure why the server isn't being built; does this imply an error in a > configuration file somewhere or does it mean that there is no upstream > support for the arm architecture? Possibly both. > In particular, the fact that xc/config/cf/xfree86.cf does not mention > Arm32Architecture at all seems somewhat suspicious... Yes. > I have a complete (3MB!) build log generated using script, so can look > through it for anything if necessary. > > [Would I be better off asking this question of the debian-arm list?] The actual porting will probably have to be done by someone familiar with the ARM, but something could likely be cooked up fairly quickly, based on the ARM patches for XFree86 3.x. -- G. Branden Robinson | Debian GNU/Linux| // // // / / [EMAIL PROTECTED] | EI 'AANIIGOO 'AHOOT'E http://www.debian.org/~branden/ | PGP signature
building xfree86 4 for debian/arm
Has anybody had any success in building xfree86 4 for debian/arm? I tried building 4.0.1-10pre11v1 from the source packages at people.debian.org/~branden/woody/ this successfully made it through the process of building binaries and installing them into the debian/tmp directory, but then fell over trying to remove a non-existent symlink: # remove the upstream symlink X -> XFree86 rm /.1/usr/local/src/xfree86-4.0.1/debian/tmp/usr/X11R6/bin/X rm: cannot remove `/.1/usr/local/src/xfree86-4.0.1/debian/tmp/usr/X11R6/bin/X': No such file or directory make: *** [debian/stampdir/install] Error 1 This symlink does not exist because the XFree86 server binary was not built in the first place and therefore no symlink was created. I'm not sure why the server isn't being built; does this imply an error in a configuration file somewhere or does it mean that there is no upstream support for the arm architecture? In particular, the fact that xc/config/cf/xfree86.cf does not mention Arm32Architecture at all seems somewhat suspicious... I have a complete (3MB!) build log generated using script, so can look through it for anything if necessary. [Would I be better off asking this question of the debian-arm list?] Peter Maydell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RANT: reading mailing list archives
Please excuse this noise, but whatever the hell happened with searching a particular mailing list archive before angering everyone on it with a question that's been answered at least 10 times in the same week?!! I'm referring to the whole "user not authorized to run the X server" issue... -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/
gdm and xdm just stopped working
After running dselect this morning, I noticed that gdm would fail to start the X server. So I installed xdm instead, and it has the same problem. xinit and startx still work. --begin /var/log/xdm.log-- X: user not authorized to run the X server, aborting. xdm error (pid 756): server unexpectedly died xdm error (pid 756): Server for display :0 can't be started, session disabled -- end /var/log/xdm.log-- -- Thomas E. Vaughan <[EMAIL PROTECTED]> CIMMS/NSSL, Norman, OK, USA
[stuart@apk.net: root-only access to X & my fix]
- Forwarded message from Stuart Krivis <[EMAIL PROTECTED]> - From: Stuart Krivis <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: root-only access to X & my fix Date: Fri, 8 Dec 2000 10:12:21 -0500 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Real-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> X-Mailer: Mutt 0.95.6i Branden, I've been running woody, and X 4.0.whatever. :-) We had a power event here last night that was a result of another event last weekend. So, my desktop machine was shut down last weekend and last night (Thursday the 7th). I had no problems when I powered it up after last weekend. It was smooth sailing all the way. This morning, however, I ran into a problem where I could not run X as anything but root. I tried a reinstall of most of the X pieces-parts using apt-get install --reinstall That didn't fix it. I went looking through the docs and found reference to "Xwrapper." But it seems that Debian has no Xwrapper. :-) So, the suggested fix of changing the call of X to Xwrapper in xserverrc didn't bring me joy. What I wound up doing is changing /etc/X11/Xwrapper.config I changed the line that said allowed_users=rootonly to be allowed_user=console That seems to have done the trick and I am working away in X now. Hurray! I can't pinpoint anything, but it would seem that something broke between 12-1 and 12-7. Hope this helps you or someone. :-) Regards, Stu -- Stuart Krivis[EMAIL PROTECTED] Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped - End forwarded message - -- G. Branden Robinson|Somewhere, there is a .sig so funny that Debian GNU/Linux |reading it will cause an aneurysm. This [EMAIL PROTECTED] |is not that .sig. http://deadbeast.net/~branden/ | PGP signature
[picone@titan.eti.br: xf86cfg problems]
- Forwarded message from Reinaldo Picone Barbosa <[EMAIL PROTECTED]> - From: Reinaldo Picone Barbosa <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: xf86cfg problems Date: Fri, 08 Dec 2000 13:04:37 -0200 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.4.0-test10 i586) X-Accept-Language: en Hi Branden, I am trying to use xf86cfg for a long time but I allways receive the same message: "Cannot open Cards database." I am using the last package version (4.0.1-10). What can I do? What should I do? ;) Tkx, Reinaldo Picone - End forwarded message - -- G. Branden Robinson| If you make people think they're Debian GNU/Linux | thinking, they'll love you; [EMAIL PROTECTED] | but if you really make them think, http://deadbeast.net/~branden/ | they'll hate you. PGP signature
xlibs package install error
hi all, FYI, the xlibs package produces the following error on my system (woody) Preparing to replace xlibs 4.0.1-7 (using .../xlibs_4.0.1-10_i386.deb) ... Unpacking replacement xlibs ... dpkg: error processing /var/cache/apt/archives/xlibs_4.0.1-10_i386.deb (--unpack): trying to overwrite `/usr/X11R6/lib/X11/app-defaults', which is also in package xcolorsel dpkg-deb: subprocess paste killed by signal (Broken pipe) this is a new problem, occuring since v4.0.1-9 (maybe -8, not sure). the package causing the conflict is not constant, as i have received the same error mentioning groff, xscreensaver and i think another package as well btw, thanks branden for a great job! i'd like to assist, but i would be worse than useless, given the level of my skills! cheers, john -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
woody packages on potato systems (was: Upgrading to Xfree 4.01)
Hm. I have a woody system, so that's not really important for me, but.. Seth Arnold <[EMAIL PROTECTED]> writes: > Emmanuel, 4.0.1 is *not* for potato. If you want to run 4.0.1 on potato, > please search for Charl P. Botha's packages built for potato. Shouldn't all Debian-Packages work always as long as their dependencies are fulfilled? (At least any Debian System should be upgradeable with a simple "apt-get dist-upgrade" from the previous version. Or am I wrong in this point!?) > If things break, recognize that is because 4.0.1 was *never meant* for > potato. If it works, then it is magic. If it breaks, that is to be > expected. My opinion is: If it breaks, the dependencies where not correct. If it's really as Seth says, it would mean that it's impossible (or pure luck) to use a mixture of a stable/unstable Debian system. I used to do this for a long time with slink/potato, however. Sometimes there were problems because Debian unstable is unstable. But usually all those difficulties were fixed after a few days by doing a fresh "apt-get install". [The price to install a woody-XF4.0.1 on a potato is machine is at least a new libc6, of course. So if you don't want to upgrade libc6, you should definitely use Charl P. Botha's potato packages.] jojo P.S.: Maybe this should be discussed on debian-devel!? -- Quitting vi is the most important command of that editor, and should be bound to something easy to type and available in all modes, for example the space bar. -- Per Abrahamsen
Read more carefully; mine is the opposite problem.
On Fri, Dec 08, 2000 at 04:50:13PM +0100, Charl P. Botha wrote: > > Please excuse this noise, but whatever the hell happened with searching a > particular mailing list archive before angering everyone on it with a > question that's been answered at least 10 times in the same week?!! > > I'm referring to the whole "user not authorized to run the X server" > issue... I have been following this mailing list fairly well for a while, but in case I missed something, I just checked the archive. Yes, I suffered from the user authorization problem too, but now I have the OPPOSITE problem. My message indicated that now startx and xinit are the ones that WORK for me and that now xdm and gdm are the ones that DON'T WORK. I hope that I haven't angered anyone; I merely posted a message that I thought (and still think) has not been answered. -- Thomas E. Vaughan <[EMAIL PROTECTED]> CIMMS/NSSL, Norman, OK, USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to start X during bootup as user
On Fri, Dec 08, 2000 at 09:51:07AM +0100, Cajus Pollmeier wrote: > Am Friday 08 December 2000 09:33 schrieb Joshua Shagam: > > Ah, okay, that makes more sense. The shellscript is probably the easiest > > way in that case. Try starting up a getty using your shellscript instead > > of /bin/login; I believe you'd want to add '-l /path/to/the/shellscript' to > > the end of one of your getty lines in your /etc/inittab. > > Currently I'm trying it this way: > X:2:respawn:/etc/init.d/kiosk > > But it doesn't work the way as expected - same error than before. What do you > mean with "-l "? I can't find any options starting with "-l" for getty. At least in the version of getty I have installed (in util-linux 2.10q-1), -l specifies an alternate to /bin/login: getty [-ihLmnw] [-f issue_file] [-l login_program] [-I init] [-t timeout] [-H login_host] port baud_rate,... [term] ... -l login_program Invoke the specified login_program instead of /bin/login. This allows the use of a non-standard login program (for example, one that asks for a dial-up password or that uses a different password file). -- Joshua Shagam /"\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML/RTF in email www.cs.nmsu.edu/~joshagam X No Word docs in email mp3.com/fluffyporcupine/ \ Respect for open standards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: authorized users [rfe]
Ah, now I understand. /etc/Xserver is no longer used. I edited /etc/Xwrapper.config and put allowed_users=console as the first line and my startx problems disappeared. I'm just reiterating it to make it easier to find for everyone else with startx unauthorized user problem. On Thu, 7 Dec 2000, Branden Robinson wrote: > On Thu, Dec 07, 2000 at 04:13:04PM -0800, Seth Arnold wrote: > > Branden, could you add a comment line to the Xwrapper.config file to the > > effect of, ``Valid values are: root, console, everybody'' -- I wasn't > > sure when this one hit me, so I guessed (and got it right, but > > self-documenting config files are nice :). > > No, because it would make my parser too complicated. > > I will, however, write a manpage for the file when I get around to it.
RANT: reading mailing list archives
Please excuse this noise, but whatever the hell happened with searching a particular mailing list archive before angering everyone on it with a question that's been answered at least 10 times in the same week?!! I'm referring to the whole "user not authorized to run the X server" issue... -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gdm and xdm just stopped working
After running dselect this morning, I noticed that gdm would fail to start the X server. So I installed xdm instead, and it has the same problem. xinit and startx still work. --begin /var/log/xdm.log-- X: user not authorized to run the X server, aborting. xdm error (pid 756): server unexpectedly died xdm error (pid 756): Server for display :0 can't be started, session disabled -- end /var/log/xdm.log-- -- Thomas E. Vaughan <[EMAIL PROTECTED]> CIMMS/NSSL, Norman, OK, USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
woody packages on potato systems (was: Upgrading to Xfree 4.01)
Hm. I have a woody system, so that's not really important for me, but.. Seth Arnold <[EMAIL PROTECTED]> writes: > Emmanuel, 4.0.1 is *not* for potato. If you want to run 4.0.1 on potato, > please search for Charl P. Botha's packages built for potato. Shouldn't all Debian-Packages work always as long as their dependencies are fulfilled? (At least any Debian System should be upgradeable with a simple "apt-get dist-upgrade" from the previous version. Or am I wrong in this point!?) > If things break, recognize that is because 4.0.1 was *never meant* for > potato. If it works, then it is magic. If it breaks, that is to be > expected. My opinion is: If it breaks, the dependencies where not correct. If it's really as Seth says, it would mean that it's impossible (or pure luck) to use a mixture of a stable/unstable Debian system. I used to do this for a long time with slink/potato, however. Sometimes there were problems because Debian unstable is unstable. But usually all those difficulties were fixed after a few days by doing a fresh "apt-get install". [The price to install a woody-XF4.0.1 on a potato is machine is at least a new libc6, of course. So if you don't want to upgrade libc6, you should definitely use Charl P. Botha's potato packages.] jojo P.S.: Maybe this should be discussed on debian-devel!? -- Quitting vi is the most important command of that editor, and should be bound to something easy to type and available in all modes, for example the space bar. -- Per Abrahamsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: authorized users [rfe]
Ah, now I understand. /etc/Xserver is no longer used. I edited /etc/Xwrapper.config and put allowed_users=console as the first line and my startx problems disappeared. I'm just reiterating it to make it easier to find for everyone else with startx unauthorized user problem. On Thu, 7 Dec 2000, Branden Robinson wrote: > On Thu, Dec 07, 2000 at 04:13:04PM -0800, Seth Arnold wrote: > > Branden, could you add a comment line to the Xwrapper.config file to the > > effect of, ``Valid values are: root, console, everybody'' -- I wasn't > > sure when this one hit me, so I guessed (and got it right, but > > self-documenting config files are nice :). > > No, because it would make my parser too complicated. > > I will, however, write a manpage for the file when I get around to it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
XFree86 4.0.1 on PowerPC status report
Bad news. 4.0.1h is broken on PowerPC because a clever trick was being played with va_lists that happens not to be portable to PowerPC. Once I have a patch I'll apply it and all will be cool again. -- G. Branden Robinson| If a man ate a pound of pasta and a Debian GNU/Linux | pound of antipasto, would they cancel [EMAIL PROTECTED] | out, leaving him still hungry? http://deadbeast.net/~branden/ | -- Scott Adams pgpj6c71y9KrV.pgp Description: PGP signature
Re: the continuing adventures of XFree86 4.0.1
On Thu, Dec 07, 2000 at 11:30:15PM +0100, Michel Dänzer wrote: > "Christian T. Steigies" wrote: > > > I have no PCI bus, I don't see PCI mentioned in the config file, is there a > > way to stop loading that? > > Have you worked on the PCI code now? On PPC it also works without PCI, and I > think it also loads that module, not sure though (I could ask on the APUS > lists if you'd like). I did not work on the pci code, I just changed it, like on ppc, to use the generic(?) linuxpci code (see debian/patches/500_*, I only added Mc68020 to the long list of non-i386 arches). Please ask some APUS people, I know Ken Tyler is interested to get X4.0 working on his PPC Amiga. Christian -- http://people.debian.org/~cts/
XFree86 4.0.1 on PowerPC status report
Bad news. 4.0.1h is broken on PowerPC because a clever trick was being played with va_lists that happens not to be portable to PowerPC. Once I have a patch I'll apply it and all will be cool again. -- G. Branden Robinson| If a man ate a pound of pasta and a Debian GNU/Linux | pound of antipasto, would they cancel [EMAIL PROTECTED] | out, leaving him still hungry? http://deadbeast.net/~branden/ | -- Scott Adams PGP signature
Re: the continuing adventures of XFree86 4.0.1
On Thu, Dec 07, 2000 at 04:11:57PM -0500, Branden Robinson wrote: > > Please wait until you see source for 10pre11v2. There's no point wasting > your time building v1 since I'm committing some fairly important bug fixes. Its running already... no problem. When will the new source be out? I am kind of "away", today is officially my last day at the university... > > One problem I see right now, I have no libgl1? > > Hrm. I guess the Mesa build crashed? No, right, installed mesa (from that build) and everything was fine. > > I have no PCI bus, I don't see PCI mentioned in the config file, is there a > > way to stop loading that? > > Bummer. This is probably an upstream bug. Is there such a thing as an > m68k box with a PCI bus? Not sure, there might be, maybe some macs? There is supposed to be some new add-on hardware for Amigas which give you PCI slots, but I think none of the "mainstream" m68k machines have PCI. I moved away that module, guess what happens? X crashed, because it does not find that module... so it seems pci must be fixed for m68k. For the debian-68k people, I've put the debs on: http://people.debian.org/~cts/x4.0/ maybe somebody has more luck running these, maybe they are a starting point for further patches to X for somebody. (note: you will need some packages from woody/binary-all to get these installed, you will find out which. It should work on a potato box, thats what I used for compiling/testing). Christian
Re: How to start X during bootup as user
Am Friday 08 December 2000 09:33 schrieb Joshua Shagam: > Ah, okay, that makes more sense. The shellscript is probably the easiest > way in that case. Try starting up a getty using your shellscript instead > of /bin/login; I believe you'd want to add '-l /path/to/the/shellscript' to > the end of one of your getty lines in your /etc/inittab. Currently I'm trying it this way: X:2:respawn:/etc/init.d/kiosk But it doesn't work the way as expected - same error than before. What do you mean with "-l "? I can't find any options starting with "-l" for getty. Thanks, -Cajus
Re: How to start X during bootup as user
On Fri, Dec 08, 2000 at 09:26:47AM +0100, Cajus Pollmeier wrote: > Am Friday 08 December 2000 09:22 schrieb Joshua Shagam: > > On Fri, Dec 08, 2000 at 08:42:57AM +0100, Cajus Pollmeier wrote: > > > Hi! > > > > > > I'm trying to run X from an init script during boot up like this: > > > > > > #!/bin/bash > > > while true; do > > > su - kiosk -c /usr/X11R6/bin/startx > > > done > > > > Why are you doing this? Why not run xdm? It's not THAT time-consuming to > > log in when you need the computer. Unless you run Enlightenment, in which > > case the amount of time it takes you to log in is the least of your > > problems. ;) > > Well - this if for a kind of kiosk system. The user will run into a prog > where he/she will only be able to press the finger on the screen. > The Touchscreen is the only device connected to this box, so logging > in makes no sense here. Ah, okay, that makes more sense. The shellscript is probably the easiest way in that case. Try starting up a getty using your shellscript instead of /bin/login; I believe you'd want to add '-l /path/to/the/shellscript' to the end of one of your getty lines in your /etc/inittab. -- Joshua Shagam /"\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML/RTF in email www.cs.nmsu.edu/~joshagam X No Word docs in email mp3.com/fluffyporcupine/ \ Respect for open standards
Re: How to start X during bootup as user
Am Friday 08 December 2000 09:22 schrieb Joshua Shagam: > On Fri, Dec 08, 2000 at 08:42:57AM +0100, Cajus Pollmeier wrote: > > Hi! > > > > I'm trying to run X from an init script during boot up like this: > > > > #!/bin/bash > > while true; do > > su - kiosk -c /usr/X11R6/bin/startx > > done > > Why are you doing this? Why not run xdm? It's not THAT time-consuming to > log in when you need the computer. Unless you run Enlightenment, in which > case the amount of time it takes you to log in is the least of your > problems. ;) Well - this if for a kind of kiosk system. The user will run into a prog where he/she will only be able to press the finger on the screen. The Touchscreen is the only device connected to this box, so logging in makes no sense here. -Cajus
Re: How to start X during bootup as user
On Fri, Dec 08, 2000 at 08:42:57AM +0100, Cajus Pollmeier wrote: > Hi! > > I'm trying to run X from an init script during boot up like this: > > #!/bin/bash > while true; do > su - kiosk -c /usr/X11R6/bin/startx > done Why are you doing this? Why not run xdm? It's not THAT time-consuming to log in when you need the computer. Unless you run Enlightenment, in which case the amount of time it takes you to log in is the least of your problems. ;) Personally, I prefer not running xdm, and just doing startx when I need to. That way it's easy for me to change bitdepths or whatever. That is, of course, a personal preference, but there's much cleaner ways to keep your system in X at all times anyway. > Starting this manually as root works as expected. While booting I get: > X: user not authorized to run the X server, aborting. > var: allowed_users, value: rootonly. > var: nice_value, value: -10. > > Changing from rootonly to anybody makes no difference. > Ok - that's no login shell from there, but... It probably has to do with the fact that you're not starting it up from a terminal or something. But, again, it's a bad idea to do that anyway. Just use xdm or gdm or the like if it's that important that your system be in X at all times... -- Joshua Shagam /"\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML/RTF in email www.cs.nmsu.edu/~joshagam X No Word docs in email mp3.com/fluffyporcupine/ \ Respect for open standards
How to start X during bootup as user
Hi! I'm trying to run X from an init script during boot up like this: #!/bin/bash while true; do su - kiosk -c /usr/X11R6/bin/startx done Starting this manually as root works as expected. While booting I get: X: user not authorized to run the X server, aborting. var: allowed_users, value: rootonly. var: nice_value, value: -10. Changing from rootonly to anybody makes no difference. Ok - that's no login shell from there, but... Thanks in advance, -Cajus
24+8 bit color depth overlay for ATI 3D RagePro?
Hi, Is 24+8 bit color depth overlay supported for ATI 3D RagePro by XF 4.0.1? Thank you. Louis
Re: the continuing adventures of XFree86 4.0.1
On Thu, Dec 07, 2000 at 11:30:15PM +0100, Michel Dänzer wrote: > "Christian T. Steigies" wrote: > > > I have no PCI bus, I don't see PCI mentioned in the config file, is there a > > way to stop loading that? > > Have you worked on the PCI code now? On PPC it also works without PCI, and I > think it also loads that module, not sure though (I could ask on the APUS > lists if you'd like). I did not work on the pci code, I just changed it, like on ppc, to use the generic(?) linuxpci code (see debian/patches/500_*, I only added Mc68020 to the long list of non-i386 arches). Please ask some APUS people, I know Ken Tyler is interested to get X4.0 working on his PPC Amiga. Christian -- http://people.debian.org/~cts/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: the continuing adventures of XFree86 4.0.1
On Thu, Dec 07, 2000 at 04:11:57PM -0500, Branden Robinson wrote: > > Please wait until you see source for 10pre11v2. There's no point wasting > your time building v1 since I'm committing some fairly important bug fixes. Its running already... no problem. When will the new source be out? I am kind of "away", today is officially my last day at the university... > > One problem I see right now, I have no libgl1? > > Hrm. I guess the Mesa build crashed? No, right, installed mesa (from that build) and everything was fine. > > I have no PCI bus, I don't see PCI mentioned in the config file, is there a > > way to stop loading that? > > Bummer. This is probably an upstream bug. Is there such a thing as an > m68k box with a PCI bus? Not sure, there might be, maybe some macs? There is supposed to be some new add-on hardware for Amigas which give you PCI slots, but I think none of the "mainstream" m68k machines have PCI. I moved away that module, guess what happens? X crashed, because it does not find that module... so it seems pci must be fixed for m68k. For the debian-68k people, I've put the debs on: http://people.debian.org/~cts/x4.0/ maybe somebody has more luck running these, maybe they are a starting point for further patches to X for somebody. (note: you will need some packages from woody/binary-all to get these installed, you will find out which. It should work on a potato box, thats what I used for compiling/testing). Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to start X during bootup as user
Am Friday 08 December 2000 09:33 schrieb Joshua Shagam: > Ah, okay, that makes more sense. The shellscript is probably the easiest > way in that case. Try starting up a getty using your shellscript instead > of /bin/login; I believe you'd want to add '-l /path/to/the/shellscript' to > the end of one of your getty lines in your /etc/inittab. Currently I'm trying it this way: X:2:respawn:/etc/init.d/kiosk But it doesn't work the way as expected - same error than before. What do you mean with "-l "? I can't find any options starting with "-l" for getty. Thanks, -Cajus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to start X during bootup as user
On Fri, Dec 08, 2000 at 09:26:47AM +0100, Cajus Pollmeier wrote: > Am Friday 08 December 2000 09:22 schrieb Joshua Shagam: > > On Fri, Dec 08, 2000 at 08:42:57AM +0100, Cajus Pollmeier wrote: > > > Hi! > > > > > > I'm trying to run X from an init script during boot up like this: > > > > > > #!/bin/bash > > > while true; do > > > su - kiosk -c /usr/X11R6/bin/startx > > > done > > > > Why are you doing this? Why not run xdm? It's not THAT time-consuming to > > log in when you need the computer. Unless you run Enlightenment, in which > > case the amount of time it takes you to log in is the least of your > > problems. ;) > > Well - this if for a kind of kiosk system. The user will run into a prog > where he/she will only be able to press the finger on the screen. > The Touchscreen is the only device connected to this box, so logging > in makes no sense here. Ah, okay, that makes more sense. The shellscript is probably the easiest way in that case. Try starting up a getty using your shellscript instead of /bin/login; I believe you'd want to add '-l /path/to/the/shellscript' to the end of one of your getty lines in your /etc/inittab. -- Joshua Shagam /"\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML/RTF in email www.cs.nmsu.edu/~joshagam X No Word docs in email mp3.com/fluffyporcupine/ \ Respect for open standards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to start X during bootup as user
Am Friday 08 December 2000 09:22 schrieb Joshua Shagam: > On Fri, Dec 08, 2000 at 08:42:57AM +0100, Cajus Pollmeier wrote: > > Hi! > > > > I'm trying to run X from an init script during boot up like this: > > > > #!/bin/bash > > while true; do > > su - kiosk -c /usr/X11R6/bin/startx > > done > > Why are you doing this? Why not run xdm? It's not THAT time-consuming to > log in when you need the computer. Unless you run Enlightenment, in which > case the amount of time it takes you to log in is the least of your > problems. ;) Well - this if for a kind of kiosk system. The user will run into a prog where he/she will only be able to press the finger on the screen. The Touchscreen is the only device connected to this box, so logging in makes no sense here. -Cajus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to start X during bootup as user
On Fri, Dec 08, 2000 at 08:42:57AM +0100, Cajus Pollmeier wrote: > Hi! > > I'm trying to run X from an init script during boot up like this: > > #!/bin/bash > while true; do > su - kiosk -c /usr/X11R6/bin/startx > done Why are you doing this? Why not run xdm? It's not THAT time-consuming to log in when you need the computer. Unless you run Enlightenment, in which case the amount of time it takes you to log in is the least of your problems. ;) Personally, I prefer not running xdm, and just doing startx when I need to. That way it's easy for me to change bitdepths or whatever. That is, of course, a personal preference, but there's much cleaner ways to keep your system in X at all times anyway. > Starting this manually as root works as expected. While booting I get: > X: user not authorized to run the X server, aborting. > var: allowed_users, value: rootonly. > var: nice_value, value: -10. > > Changing from rootonly to anybody makes no difference. > Ok - that's no login shell from there, but... It probably has to do with the fact that you're not starting it up from a terminal or something. But, again, it's a bad idea to do that anyway. Just use xdm or gdm or the like if it's that important that your system be in X at all times... -- Joshua Shagam /"\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML/RTF in email www.cs.nmsu.edu/~joshagam X No Word docs in email mp3.com/fluffyporcupine/ \ Respect for open standards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
