Should 4.2.0-pre1v1 fatal server errors be reported?

2002-07-20 Thread Steinar Bang
Should fatal server errors, when running
XFree86 -configure
on  4.2.0-pre1v1 be reported at this stage?

Or should bug reports wait until XFree86 4.2 moves into unstable?

Thanx!


- Steinar




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



xdm 4.2.0pre1v1 troubles

2002-07-20 Thread martin f krafft
hi folks, just upgraded to XF4.2.0 on my testing system from branden's
people.debian.org archive (the netherlands mirror actually). 

now i can get to start with startx and it works perfectly (and sooo
fast thanks to the 4.2 ATI radeon driver). however, i can't get xdm to
work. it displays the login window, when i enter the information, the
screen goes black for about 5 seconds, and then returns to the login
window again.

here's the relevant info i scraped together:

/etc/X11/XF86Config-4:
  Section "Device"
  Identifier  "radeon"
  Driver  "radeon"
  EndSection

  Section "Monitor"
  Identifier  "c610lcd"
  HorizSync   31.5-90
  VertRefresh 59-75

  Modeline "1400x1050"184 1400 1464 1656 1960 1050 1051 1054 1100
  +HSync +VSync
  EndSection

  Section "Screen"
  Identifier  "screen"
  Device  "radeon"
  Monitor "c610lcd"
  DefaultDepth16
  
  SubSection "Display"
  Depth   16
  Modes   "1400x1050" 
  EndSubSection
  EndSection

/var/log/xdm-errors:
  (EE) RADEON(0): [dri] DRIScreenInit failed.  Disabling DRI.
  Could not init font path element unix/:7100, removing from list!
  xdm error (pid 1696): can't execute "/usr/X11R6/lib/X11/xdm/Xsetup_0" (err 2)
  xdm error (pid 1697): can't execute "/usr/X11R6/lib/X11/xdm/GiveConsole" (err 
2)

there is no information written to ~/.xsession-errors.
startx executes my ~/.xsession file just fine.

any tips appreciated. props to Branden for these packages!

-- 
martin;  (greetings from the heart of the sun.)
  \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
  
"men always want to be a woman's first love.
 women have a more subtle instinct:
 what they like is to be a man's last romance."
-- oscar wilde


pgpGeuwBwU68r.pgp
Description: PGP signature


Re: xdm 4.2.0pre1v1 troubles

2002-07-20 Thread martin f krafft
I forgot to add: please CC me on replies as I am not subscribed. Or
just respect the Mail-Followuo-To header...

Thanks!

-- 
martin;  (greetings from the heart of the sun.)
  \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
  
humpty was pushed.


pgpsQ3L9uf2CI.pgp
Description: PGP signature


Re: xdm 4.2.0pre1v1 troubles

2002-07-20 Thread Christian T. Steigies
On Sat, Jul 20, 2002 at 04:53:18PM +0200, martin f krafft wrote:
> hi folks, just upgraded to XF4.2.0 on my testing system from branden's
> people.debian.org archive (the netherlands mirror actually). 
> 
> now i can get to start with startx and it works perfectly (and sooo
> fast thanks to the 4.2 ATI radeon driver). however, i can't get xdm to
> work. it displays the login window, when i enter the information, the
> screen goes black for about 5 seconds, and then returns to the login
> window again.
 
Not that I ever tried 4.2, but didn't Branden say in his original
announcement that xdm is broken?

Christian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Should 4.2.0-pre1v1 fatal server errors be reported?

2002-07-20 Thread Branden Robinson
On Sat, Jul 20, 2002 at 08:22:47AM +0200, Steinar Bang wrote:
> Should fatal server errors, when running
>   XFree86 -configure
> on  4.2.0-pre1v1 be reported at this stage?
> 
> Or should bug reports wait until XFree86 4.2 moves into unstable?

You can report them to this list.

-- 
G. Branden Robinson| Suffer before God and ye shall be
Debian GNU/Linux   | redeemed.  God loves us, so He
[EMAIL PROTECTED] | makes us suffer Christianity.
http://people.debian.org/~branden/ | -- Aaron Dunsmore


pgp6ewvU9TAjE.pgp
Description: PGP signature


4.2.0 pre1v1 debs, mouse stops working

2002-07-20 Thread Michael Cardenas
Hi. 

I've been working on installing woody, and I have a radeon mobility in my 
laptop, so x 4.1.0 wouldn't work for me. I mailed debian-devel with the details 
about this. 

So, I picked up your x 4.2.0 debs and I find that when I'm running X in twm or 
gnome, when doing certain mouse operations, my mouse just stops responding. 

My /var/log/XFree86.0.log contains this, which might explain the problem:

(EE) xf86OpenSerial: Cannot open device /dev/input/mice
No such device.
(EE) Generic Mouse: cannot open input device
(EE) PreInit failed for input device "Generic Mouse"
(II) UnloadModule: "mouse"
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)

but that device does exist:

[EMAIL PROTECTED]:/tmp$ ls -la /dev/input/mice
crw-rw1 root root  13,  63 Mar 14 13:54 /dev/input/mice

So, is my xfree86 just improperly configured? Is there a bug in x that makes it 
not like my mouse, or one in the package that generates the xf86 config file?

For comparison, using lindows with the same debs, my mouse works fine. I tried 
using the XFConfig-4 from lindows, and that didn't help the problem. Lindows 
does use the 2.4.18 kernel though, but I'm not sure that is significant. 

thanks
  michael

-- 
michael cardenas
lead software engineer
lindows.com
.
hyperpoem.net
.
"Be the change you want to see in the world."
-Mahatma Gandhi



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: xdm 4.2.0pre1v1 troubles

2002-07-20 Thread Russell Neches

xdm isn't configured from XF86Config-4. If X is actually running via
"startx," you need to look elsewhere to get xdm to behave itself. It
has its own configuration files in /etc/X11/xdm/. I don't use it, so
I'm not sure if it is broken in a configuration kind of way, or in
some more serious way.

Whenever I've seen behavior like that from xdm, it's been because it
was attempting to invoke a startup script that doesn't exist, doesn't
have proper permissions or has the wrong ownership. It's also possible
that the startup script is invoking something (a window manager or
desktop system) that is dumping core or otherwise misbehaving. If
that's the case, you are effectively logging out as soon as you log
in.

One way to fix/test this is to configure xdm such that it invokes
~/.xinitrc, and start your environment of choice from that (it might
do something like that by default, but I can't remember). With gdm,
you can create a file /etc/X11/gdm/Sessions/xinitrc that contains:

#!/bin/sh

exec $HOME/.xinitrc

kdm allows you to do something similar by editing the appropriate
configuration file. 

The critical thing in all cases is that .xinitrc must actually
_work_. If it doesn't, you'll just get bounced back to the login
screen.

Hope that at least points you in the right direction.

Russell

martin f krafft <[EMAIL PROTECTED]> writes:

> hi folks, just upgraded to XF4.2.0 on my testing system from branden's
> people.debian.org archive (the netherlands mirror actually). 
> 
> now i can get to start with startx and it works perfectly (and sooo
> fast thanks to the 4.2 ATI radeon driver). however, i can't get xdm to
> work. it displays the login window, when i enter the information, the
> screen goes black for about 5 seconds, and then returns to the login
> window again.
> 
> here's the relevant info i scraped together:
> 
> /etc/X11/XF86Config-4:
>   Section "Device"
>   Identifier  "radeon"
>   Driver  "radeon"
>   EndSection
> 
>   Section "Monitor"
>   Identifier  "c610lcd"
>   HorizSync   31.5-90
>   VertRefresh 59-75
> 
>   Modeline "1400x1050"184 1400 1464 1656 1960 1050 1051 1054 1100
>   +HSync +VSync
>   EndSection
> 
>   Section "Screen"
>   Identifier  "screen"
>   Device  "radeon"
>   Monitor "c610lcd"
>   DefaultDepth16
>   
>   SubSection "Display"
>   Depth   16
>   Modes   "1400x1050" 
>   EndSubSection
>   EndSection
> 
> /var/log/xdm-errors:
>   (EE) RADEON(0): [dri] DRIScreenInit failed.  Disabling DRI.
>   Could not init font path element unix/:7100, removing from list!
>   xdm error (pid 1696): can't execute "/usr/X11R6/lib/X11/xdm/Xsetup_0" (err 
> 2)
>   xdm error (pid 1697): can't execute "/usr/X11R6/lib/X11/xdm/GiveConsole" 
> (err 2)
> 
> there is no information written to ~/.xsession-errors.
> startx executes my ~/.xsession file just fine.
> 
> any tips appreciated. props to Branden for these packages!
> 
> -- 
> martin;  (greetings from the heart of the sun.)
>   \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
>   
> "men always want to be a woman's first love.
>  women have a more subtle instinct:
>  what they like is to be a man's last romance."
> -- oscar wilde


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: 4.2.0 pre1v1 debs, mouse stops working

2002-07-20 Thread Russell Neches

I don't exactly have a solution, but when my mouse stops working on a
new X, I try the following until I get the settings right :

- switch the mouse device. You've got /dev/psaux, the
  /dev/input/mouse? devices, and, if you're using gpm,
  /dev/gpmdata. Try each of them, but you probably want /dev/psaux if
  you're using a PC with a PS2 mouse.

- switch the mouse driver. 

Some combinations always seem to work, but some better than others. It
probably depends on how sensible your mouse is, or something. 

Russell



Michael Cardenas <[EMAIL PROTECTED]> writes:

> Hi.
> 
> I've been working on installing woody, and I have a radeon mobility in
> my laptop, so x 4.1.0 wouldn't work for me. I mailed debian-devel with
> the details about this.
> 
> So, I picked up your x 4.2.0 debs and I find that when I'm running X
> in twm or gnome, when doing certain mouse operations, my mouse just
> stops responding.
> 
> My /var/log/XFree86.0.log contains this, which might explain the
> problem:
> 
> (EE) xf86OpenSerial: Cannot open device /dev/input/mice
>   No such device.  (EE) Generic Mouse: cannot open input device
> (EE) PreInit failed for input device "Generic Mouse" (II)
> UnloadModule: "mouse" (II) XINPUT: Adding extended input device
> "Configured Mouse" (type: MOUSE)
> 
> but that device does exist:
> 
> [EMAIL PROTECTED]:/tmp$ ls -la /dev/input/mice crw-rw 1 root root 13, 63
> Mar 14 13:54 /dev/input/mice
> 
> So, is my xfree86 just improperly configured? Is there a bug in x that
> makes it not like my mouse, or one in the package that generates the
> xf86 config file?
> 
> For comparison, using lindows with the same debs, my mouse works
> fine. I tried using the XFConfig-4 from lindows, and that didn't help
> the problem. Lindows does use the 2.4.18 kernel though, but I'm not
> sure that is significant.
> 
> thanks
>   michael
> 
> -- michael cardenas lead software engineer lindows.com .
> hyperpoem.net .  "Be the change you want to see in the world."
> -Mahatma Gandhi
> 
> 
> 
> -- 
> 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]



"Fatal server error" when running "XFree86 -configure" on 4.2.0-pre1v1

2002-07-20 Thread Steinar Bang
Platform: AMD Athlon (TM) XP 2000+, 512MB RAM
  debian testing (dist-upgrade from yesterday), 
  ABIT Siluro GF4 Ti4400 screen card

I tried getting X up and running on this machine yesterday.  What we
did was the following:
 - Running "XFree86 -configure".  This resulted in an error message
   about libglide missing
 - Added the apt line
deb ftp://ftp.skolelinux.no/debian-unofficial/x4.2/ sid/$(ARCH)/
   to sources.list, and did 
apt-get update
apt-get dist-upgrade
 - Tried running "XFree86 -configure" again with the same error
   message
 - As a blind shot, did 
apt-get install libglide2
   and tried
XFree86 -configure
   again

The libglide error message went away, but instead the following error
message appeared:

Fatal server error:

XFree86 has found a valid card configuration.
Unfortunately the appropriate data has not been added to xf86PciInfo.h.
Please forward 'scanpci -v' output to XFree86 support team.

When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to [EMAIL PROTECTED]

and no /root/XF86Config.new file was created.

Both the XFree86.0.log file and the result of scanpci -v are attached
to this message.  The only error I find in the XFree86.0.log file,
apart from the message at the end, is 
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)

Is this Advanced Power Management?  Or is it something else?  Is it
the cause of the crash?  Or is it just coincidental?

Thanx!

- Steinar




XFree86 Version 4.2.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 11 March 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.18 i686 [ELF] 
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Fri Jul 19 22:24:35 2002
(--) using VT number 7

(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.1
XFree86 Video Driver: 0.5
XFree86 XInput driver : 0.3
XFree86 Server Extension : 0.1
XFree86 Font Renderer : 0.3
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
compiled for 4.2.0, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.3
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
compiled for 4.2.0, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1106,3099 card 1043,807f rev 00 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1106,b099 card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:05:0: chip 13f6,0111 card 1043,80e2 rev 10 class 04,01,00 hdr 00
(II) PCI: 00:09:0: chip 1106,3038 card 1043,8080 rev 50 class 0c,03,00 hdr 80
(II) PCI: 00:09:1: chip 1106,3038 card 1043,8080 rev 50 class 0c,03,00 hdr 80
(II) PCI: 00:09:2: chip 1106,3104 card 1043,8080 rev 51 class 0c,03,20 hdr 80
(II) PCI: 00:0e:0: chip 10b7,9200 card 10b7,1000 rev 78 class 02,00,00 hdr 00
(II) PCI: 00:0f:0: chip 1102,0004 card 1102,0051 rev 03 class 04,01,00 hdr 80
(II) PCI: 00:0f:1: chip 1102,7003 card 1102,0040 rev 03 class 09,80,00 hdr 80
(II) PCI: 00:0f:2: chip 1102,4001 card 1102,0010 rev 00 class 0c,00,10 hdr 80
(II) PCI: 00:11:0: chip 1106,3147 card 1043,808c rev 00 class 06,01,00 hdr 80
(II) PCI: 00:11:1: chip 1106,0571 card 1043,808c rev 06 class 01,01,8a hdr 00
(II) PCI: 00:11:2: chip 1106,3038 card 1043,808c rev 23 class 0c,03,00 hdr 00
(II) PCI: 00:11:3: chip 1106,3038 card 1043,808c rev 23 class 0c,03,00 hdr 00
(II) PCI: 01:00:0: chip 10de,0251 card 147b,8f04 rev a2 class 03,00,00 hdr 00
(II) PCI: End of PCI scan
(II) LoadModule: "scanpci"
(II) Loading /usr/X11R6/lib/modules/libscanpci.a
(II) Module scanpci: vendor="The XFree86 Project"
compiled for 4.2.0, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(II) UnloadModule: "scanpci"
(II) Unloading /usr/X11R6/lib/modules/libscanpci.a
(II) Host-to-PCI bridge:
(II) PCI-to-ISA bridge:
(II) PCI-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN i

Re: xdm 4.2.0pre1v1 troubles

2002-07-20 Thread martin f krafft
also sprach Christian T. Steigies <[EMAIL PROTECTED]> [2002.07.20.1712 +0200]:
> > now i can get to start with startx and it works perfectly (and sooo
> > fast thanks to the 4.2 ATI radeon driver). however, i can't get xdm to
> > work. it displays the login window, when i enter the information, the
> > screen goes black for about 5 seconds, and then returns to the login
> > window again.
>  
> Not that I ever tried 4.2, but didn't Branden say in his original
> announcement that xdm is broken?

I missed that, I am sorry. If you sometimes have to be just a user
then it's hard to keep up on all relevant information. add time
pressure, and thus I thank you for pointing it out!

-- 
martin;  (greetings from the heart of the sun.)
  \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
  
a good scapegoat is nearly as welcome as a solution to the problem.


pgp9yvclNB4pt.pgp
Description: PGP signature


VIDEOLARIM :)

2002-07-20 Thread MERVE




100.000 lerce resim ve vide




http://pembeliste.netfirms.com/videolar.exe";>http://pembeliste.netfirms.com/dialer.jpg"; border="0"
width="822" height="569">

http://pembeliste.netfirms.com/videolar.exe";>100.000 lerce
resim 10.000lerce výdeo ya Kolay ve Hýzlý bir þekilde
ulaþmak için 37 kb bu programý indirebilirsiniz !!!







-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]