- WLUG - wlug.mailman3.com

Re: [Wlug] problem hardware?

by Baris Hasdemir

no. The region should be "1" I got this dvd from the shrewsbury public library. and actually it is playing the dvd without any problems. I am using xine to play it. the only problem is those error messages. On Tue, 2003-10-14 at 15:33, gboyce(a)badbelly.com wrote: > The error given here "Media region code is mismatched to logical unit" > sounds like the drive believes that it's not allowed to read content of > that type. Are you trying to view a non-US/Canada movie in the drive? > > On Tue, 14 Oct 2003, Baris Hasdemir wrote: > > > Hello all, > > > > Today I received my slot loading pioneer dvd rom drive from newegg.com. > > But linux tells me there are problems with it. The problem is my new > > hardware right? Or should I upgrade my kernel? I wanted to be sure > > before sending it back. > > > > kernel 2.4.22(slackware 9.1) > > > > thanks, > > baris > > > > # tail -f /var/log/syslog > > Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:45 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:45 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:45 penguen kernel: "a4 00 00 00 01 26 00 00 00 0c c4 00 " > > Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:45 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:45 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:45 penguen kernel: "a4 00 00 00 02 3d 00 00 00 0c c4 00 " > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 ad 00 00 00 0c c4 00 " > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 dc 00 00 00 0c c4 00 " > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 0a 2b 00 00 00 0c c4 00 " > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:46 penguen kernel: "a4 00 00 20 f9 76 00 00 00 0c c4 00 " > > Oct 14 14:39:47 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:47 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:47 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:47 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:47 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:47 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:47 penguen kernel: "a4 00 00 20 f9 e6 00 00 00 0c c4 00 " > > > > > > > > _______________________________________________ > > Wlug mailing list > > Wlug(a)mail.wlug.org > > http://mail.wlug.org/mailman/listinfo/wlug > > > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > >

Oct. 14, 2003

Re: [Wlug] problem hardware?

by gboyce＠badbelly.com

The error given here "Media region code is mismatched to logical unit" sounds like the drive believes that it's not allowed to read content of that type. Are you trying to view a non-US/Canada movie in the drive? On Tue, 14 Oct 2003, Baris Hasdemir wrote: > Hello all, > > Today I received my slot loading pioneer dvd rom drive from newegg.com. > But linux tells me there are problems with it. The problem is my new > hardware right? Or should I upgrade my kernel? I wanted to be sure > before sending it back. > > kernel 2.4.22(slackware 9.1) > > thanks, > baris > > # tail -f /var/log/syslog > Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:45 penguen kernel: ATAPI device hdd: > Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:45 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:45 penguen kernel: "a4 00 00 00 01 26 00 00 00 0c c4 00 " > Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:45 penguen kernel: ATAPI device hdd: > Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:45 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:45 penguen kernel: "a4 00 00 00 02 3d 00 00 00 0c c4 00 " > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 ad 00 00 00 0c c4 00 " > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 dc 00 00 00 0c c4 00 " > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 0a 2b 00 00 00 0c c4 00 " > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:46 penguen kernel: "a4 00 00 20 f9 76 00 00 00 0c c4 00 " > Oct 14 14:39:47 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:47 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:47 penguen kernel: ATAPI device hdd: > Oct 14 14:39:47 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:47 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:47 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:47 penguen kernel: "a4 00 00 20 f9 e6 00 00 00 0c c4 00 " > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Oct. 14, 2003

problem hardware?

by Baris Hasdemir

Hello all, Today I received my slot loading pioneer dvd rom drive from newegg.com. But linux tells me there are problems with it. The problem is my new hardware right? Or should I upgrade my kernel? I wanted to be sure before sending it back. kernel 2.4.22(slackware 9.1) thanks, baris # tail -f /var/log/syslog Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:45 penguen kernel: ATAPI device hdd: Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:45 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:45 penguen kernel: "a4 00 00 00 01 26 00 00 00 0c c4 00 " Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:45 penguen kernel: ATAPI device hdd: Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:45 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:45 penguen kernel: "a4 00 00 00 02 3d 00 00 00 0c c4 00 " Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:46 penguen kernel: ATAPI device hdd: Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:46 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 ad 00 00 00 0c c4 00 " Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:46 penguen kernel: ATAPI device hdd: Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:46 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 dc 00 00 00 0c c4 00 " Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:46 penguen kernel: ATAPI device hdd: Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:46 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:46 penguen kernel: "a4 00 00 00 0a 2b 00 00 00 0c c4 00 " Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:46 penguen kernel: ATAPI device hdd: Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:46 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:46 penguen kernel: "a4 00 00 20 f9 76 00 00 00 0c c4 00 " Oct 14 14:39:47 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:47 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:47 penguen kernel: ATAPI device hdd: Oct 14 14:39:47 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:47 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:47 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:47 penguen kernel: "a4 00 00 20 f9 e6 00 00 00 0c c4 00 "

Oct. 14, 2003

RE: [Wlug] Fw: RE: show

by mlong＠datalong.com

That sounds like a great topic. This could be expanded to include mini tutorials scattered about in subsequent shows explaining how to achieve the same functionality in the various apps. Cheers, Mike > Yury, > > You can count me in. I also know my way around a TV production studio. > > We had talked about doing an introduction to linux. As an aside to that I > was thinking that possibly we could do a show on equivalent pieces of > software on the linux side of things that could replace (perceived) > missing > functionality. This would include stuff like Evolution, Mozilla, GnuCash, > OpenOffice, mplayer, xmms, etc. > > What do people think?

Oct. 14, 2003

RE: [Wlug] Fw: RE: show

by Keller, Tim

Yury, You can count me in. I also know my way around a TV production studio. We had talked about doing an introduction to linux. As an aside to that I was thinking that possibly we could do a show on equivalent pieces of software on the linux side of things that could replace (perceived) missing functionality. This would include stuff like Evolution, Mozilla, GnuCash, OpenOffice, mplayer, xmms, etc. What do people think? Thanks, Tim. -----Original Message----- From: Yury I Vashugin [mailto:vashugins@juno.com] Sent: Tuesday, October 14, 2003 12:56 PM To: wlug(a)mail.wlug.org Cc: wlug(a)wlug.org Subject: [Wlug] Fw: RE: show hi, everyone. since we talked about producing an educational show about linux and putting it 'in-the-air' at the last wlug meeting and i saw a very enthusiastic response so i've reserved the studio for oct.21(see below). there's a problem with a converter but i'm sure we can find a laptop with a video output. for the show we need two cameramen(anyone can do that; very simple duties and can be learned within 3-5 min), a show host and guests. please, bring any suggestions or/and recommendations. thanks. yury --------- Forwarded message ---------- From: Marc Serra <mserra(a)ci.shrewsbury.ma.us> To: 'Yury I Vashugin' <vashugins(a)juno.com> Date: Fri, 10 Oct 2003 13:42:56 -0400 Subject: RE: show Message-ID: <A7F72312FF5DB348BE2D037A6FE5F1C1407EC2@selpnt2> Yes. Does anybody in the group have access to a scan converter or can you use a computer with a video card output? Since we spoke about it, our last scan converter was put into service to be used on one of our channel's for our bulletin board. For you to use it, we would have to take a channel off the air. I know that a lot of laptops have video out. -----Original Message----- From: Yury I Vashugin [mailto:vashugins@juno.com] Sent: Friday, October 10, 2003 11:48 AM To: mserra(a)ci.shrewsbury.ma.us Subject: show marc, can i reserve the studio for half-an-hour show on tuesday, october 21 at 6:30 (actually it will not be a show; just a preliminary stuff- what light, what background, what settings we want for 'linux show', to try a scanner converter etc)? yury ________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today! _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

Oct. 14, 2003

Fw: RE: show

by Yury I Vashugin

hi, everyone. since we talked about producing an educational show about linux and putting it 'in-the-air' at the last wlug meeting and i saw a very enthusiastic response so i've reserved the studio for oct.21(see below). there's a problem with a converter but i'm sure we can find a laptop with a video output. for the show we need two cameramen(anyone can do that; very simple duties and can be learned within 3-5 min), a show host and guests. please, bring any suggestions or/and recommendations. thanks. yury --------- Forwarded message ---------- From: Marc Serra <mserra(a)ci.shrewsbury.ma.us> To: 'Yury I Vashugin' <vashugins(a)juno.com> Date: Fri, 10 Oct 2003 13:42:56 -0400 Subject: RE: show Message-ID: <A7F72312FF5DB348BE2D037A6FE5F1C1407EC2@selpnt2> Yes. Does anybody in the group have access to a scan converter or can you use a computer with a video card output? Since we spoke about it, our last scan converter was put into service to be used on one of our channel's for our bulletin board. For you to use it, we would have to take a channel off the air. I know that a lot of laptops have video out. -----Original Message----- From: Yury I Vashugin [mailto:vashugins@juno.com] Sent: Friday, October 10, 2003 11:48 AM To: mserra(a)ci.shrewsbury.ma.us Subject: show marc, can i reserve the studio for half-an-hour show on tuesday, october 21 at 6:30 (actually it will not be a show; just a preliminary stuff- what light, what background, what settings we want for 'linux show', to try a scanner converter etc)? yury ________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!

Oct. 14, 2003

Re: [Wlug] You can't get there from here...

by Gregory Avedissian

Andy Stewart wrote: > On Monday 13 October 2003 2:28 pm, Gregory Avedissian wrote: > >>Lowres won't work. The problem is it sees the S3Virge chip on the vid >>card and wants to use the s3virge driver, when it should really be using >>the 3DLabs driver. In the old sax, it tries to run in lowres first, and >>it comes up very large and hanging way over the edge of my screen. What >>I've found to work is this - >>sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs > > > The "very large and hanging way over the edge of my screen" problem is most > likely a funky "modelines" line in your XF86Config file. This can often be > remedied by manually adjusting your monitor, or by running (carefully!) > xvidtune and noting the new mode line once the screen is properly adjusted. > This new mode line would then be hand edited into your XF86Config file. If > the XFree86 v3.x driver (XF86_3DLabs) works for you, there may be no need to > fuss with the v4.x XFree86 driver. > > >>I've read the help screen for sax2 a bunch of times, and I don't >>understand how to give it the same information. >> >>sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom >>half of my screen and bleeds way off the right edge. >> >>sax2 -m 0=glint quits and gives me error messages (no device found - the >>card has a glint 500tx accelerator) >> >>sax2 -m 0=s3virge goes black and locks up, only reset button gets me out >> > > > Which version of XFree86 4.x are you trying to use? If you are having > problems like this, you most likely need the latest and greatest. However, I > have seen cases where XFree86 v3.x works better than v4.x, especially on > "weird" video cards that are getting on in years. > > Later, > > Andy I'm trying to use 4.1.0. The 3Dlabs driver didn't come with 3.3.6. I had to find it online and unpack it. I also ran the Xinstall script that came with the 4.1.0 tarballs. I thought it had replaced all my files, so I can't tell you for sure which version is really running. I just tried again to run sax2 -m 0=vga, and it ran fine at 640x480. I'm not sure what's different now, but I did install some other packages this afternoon, like openmotif devel and some font packages. Anyway, sax2 does not list my vid card, but sax does. Maybe I should just leave this alone for now, since it works. If it's the source of the kde problem, I can live with it as long as my function keys work. BTW, I had asked you about my other machine, which wouldn't let me switch virtual screens. Turns out my nifty new keyboard has about 10 special buttons for web surfing, and one of them turns off the function keys. Thanks, Greg

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Andy Stewart

On Monday 13 October 2003 2:28 pm, Gregory Avedissian wrote: > > Lowres won't work. The problem is it sees the S3Virge chip on the vid > card and wants to use the s3virge driver, when it should really be using > the 3DLabs driver. In the old sax, it tries to run in lowres first, and > it comes up very large and hanging way over the edge of my screen. What > I've found to work is this - > sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs The "very large and hanging way over the edge of my screen" problem is most likely a funky "modelines" line in your XF86Config file. This can often be remedied by manually adjusting your monitor, or by running (carefully!) xvidtune and noting the new mode line once the screen is properly adjusted. This new mode line would then be hand edited into your XF86Config file. If the XFree86 v3.x driver (XF86_3DLabs) works for you, there may be no need to fuss with the v4.x XFree86 driver. > > I've read the help screen for sax2 a bunch of times, and I don't > understand how to give it the same information. > > sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom > half of my screen and bleeds way off the right edge. > > sax2 -m 0=glint quits and gives me error messages (no device found - the > card has a glint 500tx accelerator) > > sax2 -m 0=s3virge goes black and locks up, only reset button gets me out > Which version of XFree86 4.x are you trying to use? If you are having problems like this, you most likely need the latest and greatest. However, I have seen cases where XFree86 v3.x works better than v4.x, especially on "weird" video cards that are getting on in years. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Andy Stewart

On Monday 13 October 2003 2:28 pm, Gregory Avedissian wrote: > >> > >>I'm thinking it might have to do with my funky vid card (ELSA GLoria-L). > >>Sax2 won't run on this machine - it goes to a black screen that won't > >>respond to any keystrokes except the reset button. I had to setup XFree > >>4.1 with the old sax, passing monitor and server parameters to it on the > >>command line for it to run correctly (hsync, vsync, screen resolution > >>and server). Sax2 doesn't seem to have the same switches. Is it bad to > >>setup newer versions of X with sax instead of sax2? > >> > >>BTW, I had a lot of trouble setting up the older version of XFree from > >>the CD's, too. > >> > >>Greg > > > > HI Greg, > > > > I think sax2 has a command line switch to force it to run in a low res > > mode, and I believe it is "-l" (minus ell). I've succeeded in using this > > with all sorts of strange hardware. This switch is not the default. > > > > sax is designed for XFree86 3.x, while sax2 is designed for XFree86 4.x. > > SuSE seems to be geared to more easily handle XFree86 4.x. > > > > See if you can get this graphics card to run in 640x480 8-bit color mode > > first, and if you succeed, then get brave and attempt higher resolutions > > afterwards. > > > > Later, > > > > Andy > > Andy, > > Lowres won't work. The problem is it sees the S3Virge chip on the vid > card and wants to use the s3virge driver, when it should really be using > the 3DLabs driver. In the old sax, it tries to run in lowres first, and > it comes up very large and hanging way over the edge of my screen. What > I've found to work is this - > sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs > > I've read the help screen for sax2 a bunch of times, and I don't > understand how to give it the same information. > > sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom > half of my screen and bleeds way off the right edge. > > sax2 -m 0=glint quits and gives me error messages (no device found - the > card has a glint 500tx accelerator) > > sax2 -m 0=s3virge goes black and locks up, only reset button gets me out > > Can't figure out the proper syntax for the --xmode option to set the > screen resolution or hsync, and setting vsync doesn't seem to be an > option. If you know this secret, I'll buy you a beer. > > > Greg > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 13, 2003

RE: [Wlug] FW: Authentication on outgoing SMTP, how to set with postfix?

by Jim & Toni

Well, found the answer here. http://sdb.suselinux.hu/en/sdb/html/rsimai_imap_smtp_auth.html -----Original Message----- From: Jim & Toni [mailto:jntdibb@bellatlantic.net] Sent: Monday, October 13, 2003 2:28 PM To: 'wlug(a)wlug.org' Subject: Authentication on outgoing SMTP, how to set with postfix? I've almost got postfix setup as a mail relay from my local linux box to 'outgoing.verizon.net'. But, the postfix howto doesn't specify how to provide login/password authentication for smtp servers that require it. The error was '554: Authentication required' Going to search more, but appreciate any help. Thanks.

Oct. 13, 2003