How to set default resolution in XF86?
Whenever I start X, it comes up with a default resolution of (I think) 640x480. I normally run at 1280x1024, which means I have to hit CTRLALTKP+ two or three times to select the correct resolution. Is there any way I can specify that as the default resolution? Is it a matter of just resequencing some lines in my XF86Config file? I'd also like to use a resolution of 1152x870, but that resolution wasn't provided under xf86config. Is there some way I can calculate the vertical and horizontal frequencies for this resolution and add them to my XF86Config file? 1280x1024 is a little much for my .31DP monitor... Thanks! -- Tracy Nelson
Re: diald -- help or source!
From: John Hasler [EMAIL PROTECTED] To: Tracy Nelson [EMAIL PROTECTED] Cc: debian-user@lists.debian.org debian-user@lists.debian.org Date: Monday, June 21, 1999 20:41 Subject: Re: diald -- help or source! In the message log I see that it attempts to open the connection, and immediately reports that the connection script failed. It doesn't seem to access the modem or anything. Please post the script, the log, and /etc/diald/diald.options. My connection script is simple editing of the original to whit: +++ MODEM_INIT=ATZC1D2%C0 connect 130 lines, 3693 characters # The phone number to dial # PHONE_NUMBER=5551212 PHONE_NUMBER=6109433278 # The chat sequence to recognize that the remote system # is asking for your user name. # USER_CHAT_SEQ=name:--name:--name:--name:--name:--name:--name: USER_CHAT_SEQ=ogin:--ogin:--ogin:--ogin:--ogin:--ogin:--ogin: # The string to send in response to the request for your user name. USER_NAME=tnelson # The chat sequence to recongnize that the remote system # is asking for your password. PASSWD_CHAT_SEQ=word: # The string to send in response to the request for your password. PASSWORD=*elided* # The prompt the remote system will give once you are logged in # If you do not define this then the script will assume that # there is no command to be issued to start up the remote protocol. PROMPT=tion } # Initialize the modem. Usually this just resets it. message Initializing Modem chat $DEBUG TIMEOUT 5 $MODEM_INIT TIMEOUT 5 OK if [ $? != 0 ]; then message Failed to initialize modem exit 1 fi # Dial the remote system. message Dialing system chat $DECONNECT HONE_NUMBER \ case $? in 0) message Connected;; 1) message Chat Error; exit 1;; 2) message Chat Script Error; exit 1;; 3) message Chat Timeout; exit 1;; 4) message No Carrier; exit 1;; 5) message Busy; exit 1;; 6) message No DialTone; exit 1;; 7) message Modem Error; exit 1;; *) esac exit 1 fi fi if [ $START_ACK != ]; then chat $DEBUG TIMEOUT 15 $START_ACK if [exit 1e Failed to start Protocol fi fi # Success! message Protocol started === The log file is pretty simple, just: +++ Jun 21 09:12:48 spicerack diald[24824]: Running connect (pid = 24973). Jun 21 09:12:48 spicerack diald[24824]: Connect script failed. Jun 21 09:12:49 spicerack diald[24824]: Delaying 30 seconds before clear to dial . === My options file looks like this: +++ mode ppp connect /etc/diald/connect device /dev/ttyS0 speed 115200 modem lock crtscts local 10.0.0.3 remote 192.168.0.2 dynamic defaultroute include /etc/diald/standard.filter === I can't get chat to run a simple connect script either. What do you mean by that? Whenever I try something simple like chat -V 'ATZ' I get no response for several seconds (I suspect a timeout) and if I ^C during this time I get an I/O operation incomplete error (or something like that). Thanks very much for any clues anyone can drop in my general direction! Cheers! -- Tracy
diald -- help or source!
diald is dying when trying to run the connect script. In the message log I see that it attempts to open the connection, and immediately reports that the connection script failed. It doesn't seem to access the modem or anything. pppd works just fine, but I can't get chat to run a simple connect script either. Can someone tell me what to look for? Or, alternately, tell me where I might find the source for diald? I'm not afraid to get into it with a debugger and really screw things up... ;) Cheers! -- Tracy
Re: PS/2 mouse rolling away
I've seen this happen with cheap mice exposed to bright light. Seems the plastic shell is so thin that they let enough light in to trigger the protoreceptors. The next time it happens, try just shading the mouse with your hand. If that stop it, then you can disassemble the mouse and spray the inside with some paint. Or just work in the dark ;)... -Original Message- From: David Wright [EMAIL PROTECTED] To: Colin Marquardt [EMAIL PROTECTED] Cc: Debian-User List debian-user@lists.debian.org Date: Wednesday, June 16, 1999 07:37 Subject: Re: PS/2 mouse rolling away Quoting Colin Marquardt ([EMAIL PROTECTED]): * Armin Wegner [EMAIL PROTECTED] writes: my logitech ps/2 mouse behaves oddly. Sometimes, the pointer rolls to the top or bottom of the screen when pressing a button while moving left or right in X and on console. I can stop this by moving the mouse. But I can't Are you sure this isn´t a mechanical problem? Is the movement that steady? I have seen something like that with an old mouse of mine... Maybe this when pressing a button is pure coincidence? I get this with a MS serial mouse sometimes. I'm not even touching the mouse and the cursor starts to fall slowly and jerkily down the screen. I guess even mice get fleas ;-) Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
