Re: Updated Sid today, xorg cannot find nvidia driver
First of all, I'd like to emphasize that I haven't read all the posts related to this problem thoroughly, since there is probably more than one reason of such behavior. Anyway, I wanted to report that I am using nvidia-glx-legacy and after I have upgraded my Debian Sid today, my Xorg refused to start up after reboot. The log message was exactly the same as quoted below. Curt Howland wrote: (II) LoadModule: nvidia (WW) Warning, couldn't load module nvidia (II) UnloadModule: nvidia (EE) Failed to load module nvidia (module does not exist, 0) Ron Johnson, Jr. suggested: /usr/lib/xorg/modules/drivers Ok, I looked there and found nvidia_drv.o All the rest of the files are *.so (...) I put in a link nvidia_drv.so = nvidia_drv.o, and tried again, still no luck. I've tried: ld nvidia_drv.o -shared -o nvidia_drv.so And it worked. Maybe this will help some users and probably attract package maintainers' attention to this issue. I suspect that the Xorg behavior changed so that .o drivers are not loaded anymore. As far as my opinion is concerned, regardless of the advice given and positive reports that could be found here, I still consider this problem as not solved, because a regular update rendered my system unusable. -- Michał Wróbel [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Updated Sid today, xorg cannot find nvidia driver
Andrei Popescu wrote: Michał Wróbel [EMAIL PROTECTED] wrote: Anyway, I wanted to report that I am using nvidia-glx-legacy and after I have upgraded my Debian Sid today, my Xorg refused to start up after reboot. The log message was exactly the same as quoted below. Do you have any special reason for using the legacy driver? I would recommend to upgrade. Unfortunately, I do. It's my old NVidia GeFORCE 2 PRO, which does not seem to be supported by the upstream. I know that the hardware nowadays is cheap, but... I just don't like throwing out good, working hw just because someone decided to stop supporting it. Anyway, Debian decided to support the legacy version as well. I am very glad about this. I have just reported the problem I've encountered and suggested a simple way for the others to solve it. I don't have the problem anymore, at least until next Sid upgrade :). -- Michał Wróbel [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
pppd dialin i problem z PAPem
Witam, System debian sarge. Jest na nim postawiony mgetty+pppd. Standardowa konfiguracja z HOWTO. Wszystko ladnie dzialalo do czasu. Od pewnego momentu nie moglem sie polaczyc. Zaczalem kombinowac. Po paru dniach okazalo sie, ze modem sie zawiesil. Niestety po restarcie modemu nie moge dokonac autentyfikacji PAPem. W pliku /etc/ppp/options mam: 192.168.1.9:192.168.1.30 login auth -chap +pap ms-dns 192.168.1.9 proxyarp debug kdebug 7 W /etc/ppp/pap-secrets: * wrobel* Z tego co pisza w HOWTO to powinno wystarczyc do tego, zeby pppd autoryzowal userow na podstawie /etc/passwd... Niestety gdy lacze sie polaczenie jest zrywane a w /var/log/messages: Mar 14 21:46:10 wrobel pppd[20380]: pppd 2.4.2 started by root, uid 0 Mar 14 21:46:10 wrobel pppd[20380]: Using interface ppp0 Mar 14 21:46:10 wrobel pppd[20380]: Connect: ppp0 -- /dev/ttyS1 Mar 14 21:46:17 wrobel pppd[20380]: no PAP secret found for wrobel Mar 14 21:46:17 wrobel pppd[20380]: PAP peer authentication failed for wrobel Mar 14 21:46:23 wrobel pppd[20380]: Connection terminated. Mar 14 21:46:23 wrobel pppd[20380]: Exit. w /var/log/syslog: Mar 14 21:48:51 wrobel pppd[20416]: pppd 2.4.2 started by root, uid 0 Mar 14 21:48:51 wrobel pppd[20416]: using channel 71 Mar 14 21:48:51 wrobel pppd[20416]: Using interface ppp0 Mar 14 21:48:51 wrobel pppd[20416]: Connect: ppp0 -- /dev/ttyS1 Mar 14 21:48:51 wrobel pppd[20416]: sent [LCP ConfReq id=0x1 asyncmap 0x0 auth pap magic 0x777139ba pcomp accomp] Mar 14 21:48:51 wrobel pppd[20416]: rcvd [LCP ConfAck id=0x1 asyncmap 0x0 auth pap magic 0x777139ba pcomp accomp] Mar 14 21:48:53 wrobel pppd[20416]: rcvd [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x9402a48 pcomp accomp callback CBCP] Mar 14 21:48:53 wrobel pppd[20416]: sent [LCP ConfRej id=0x1 callback CBCP] Mar 14 21:48:53 wrobel pppd[20416]: rcvd [LCP ConfReq id=0x2 asyncmap 0x0 magic 0x9402a48 pcomp accomp] Mar 14 21:48:53 wrobel pppd[20416]: sent [LCP ConfAck id=0x2 asyncmap 0x0 magic 0x9402a48 pcomp accomp] Mar 14 21:48:53 wrobel pppd[20416]: rcvd [LCP code=0xc id=0x3 09 40 2a 48 4d 53 52 41 53 56 35 2e 31 30] Mar 14 21:48:53 wrobel pppd[20416]: sent [LCP CodeRej id=0x2 0c 03 00 12 09 40 2a 48 4d 53 52 41 53 56 35 2e 31 30] Mar 14 21:48:53 wrobel pppd[20416]: rcvd [LCP code=0xc id=0x4 09 40 2a 48 4d 53 52 41 53 2d 30 2d 44 59 52 45 4b 54 4f 52] Mar 14 21:48:53 wrobel pppd[20416]: sent [LCP CodeRej id=0x3 0c 04 00 18 09 40 2a 48 4d 53 52 41 53 2d 30 2d 44 59 52 45 4b 54 4f 52] Mar 14 21:48:53 wrobel pppd[20416]: rcvd [PAP AuthReq id=0xc user=wrobel password=hidden] Mar 14 21:48:53 wrobel pppd[20416]: no PAP secret found for wrobel Mar 14 21:48:53 wrobel pppd[20416]: sent [PAP AuthNak id=0xc Login incorrect] Mar 14 21:48:53 wrobel pppd[20416]: PAP peer authentication failed for wrobel Mar 14 21:48:53 wrobel pppd[20416]: sent [LCP TermReq id=0x4 Authentication failed] Mar 14 21:48:53 wrobel pppd[20416]: rcvd [LCP TermReq id=0x5 09 40 2a 48 00 3c cd 74 00 00 02 b3] Mar 14 21:48:53 wrobel pppd[20416]: sent [LCP TermAck id=0x5] Mar 14 21:48:53 wrobel pppd[20416]: rcvd [LCP TermAck id=0x4 Authentication failed] Mar 14 21:48:53 wrobel pppd[20416]: Connection terminated. Mar 14 21:48:53 wrobel pppd[20416]: Exit. Jezeli w options zahaszuje linie: # auth # -chap # +pap to polaczenie zostaja prawidlowo zestawione. Niestety w ten sposob mozna sie polaczyc bez autoryzacji... Ma ktos jakis pomysl co jest grane? pzdr. Michal Wrobel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
