- main - earth.li

Re: My Xorg video setup
by John Seago 26 Nov '04

26 Nov '04

This may be a rather silly question, but have you run xorgconfig, or did you just use the setting of xorg which arises at the end of the install? -- John Seago Linux User #219566 (http://counter.li.org) AFFS http://www.affs.org.uk/

2 1

RE: [ALUG] Another printer problem
by Keith Watson 26 Nov '04

26 Nov '04

> From: Hyperbit Sent: 26 November 2004 16:43 > Finally, Linux will be hardware friendly ah, but when will hardware be Linux friendly? :o) Keith ____________ What you think you own, owns you. - Zen Saying

1 0

RE: [ALUG] Printers problem
by Keith Watson 26 Nov '04

26 Nov '04

> From: Nick Daniels Sent: 25 November 2004 20:13 > > Hi > I have a Canon BJC1000 running under Suse 9.1, > this printer has worked O.K. on all Suse distros since > Suse 7.0 (and other distros) However on Suse 9.1 > the pages are being printed in "half width" A4. > Have I overlooked anything obvious? > Regards > Nick Daniels > I had something like this when I installed my Canon S600. IIRC I resolved it by playing around with the dpi resolution in the printer config page in CUPS. Which may or may not apply in your case but.... Regards, Keith ____________ The beginning of wisdom is calling things by their right names. - Chinese Proverb

1 0

My Xorg video setup
by Chris Green 26 Nov '04

26 Nov '04

I've taken a look at my Xorg.0.log file and, among other things, it has:- (--) GLINT(0): FIFO Size is 256 DWORDS (==) GLINT(0): Min pixel clock is 16 MHz (--) GLINT(0): Max pixel clock is 110 MHz (II) GLINT(0): LGFlatron: Using hsync range of 30.00-107.00 kHz (II) GLINT(0): LGFlatron: Using vrefresh range of 50.00-200.00 Hz (II) GLINT(0): Clock range: 16.25 to 110.00 MHz (II) GLINT(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) GLINT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) ... ... ... (II) GLINT(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan) ... ... ... (II) GLINT(0): Not using mode "1600x1200" (no mode of this name) ... ... ... (--) GLINT(0): Virtual size is 1280x1024 (pitch 1280) (**) GLINT(0): *Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz (II) GLINT(0): Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (**) GLINT(0): *Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz (II) GLINT(0): Modeline "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (**) GLINT(0): Default mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0 Hz (II) GLINT(0): Modeline "1280x960" 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (**) GLINT(0): Default mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz (II) GLINT(0): Modeline "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (**) GLINT(0): Default mode "1152x768": 65.0 MHz, 44.2 kHz, 54.8 Hz The 1280x1024 line is the highest resolution one that appears with that "Modeline" start, does that mean that it's the highest resolution that Xorg thinks is possible? -- Chris Green (chris(a)areti.co.uk) "Never ascribe to malice, that which can be explained by incompetence."

4 8

Reminder: Meeting Sunday@Syleham
by John Woodard 25 Nov '04

25 Nov '04

Memory Jog Meeting this Sunday at Syleham Village Hall 2:00 - 6:00pm bring kit if you want. The bar will be open. Details on http://www.alug.org.uk/meetings. Cheers, BJ -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.4.2 - Release Date: 24/11/2004

1 0

Further video info/questions
by Chris Green 25 Nov '04

25 Nov '04

Further to my lat post my Xorg.0.log file also has the following lines:- (II) GLINT(0): Manufacturer's mask: 10 (II) GLINT(0): Supported Future Video Modes: (II) GLINT(0): #0: hsize: 640 vsize 480 refresh: 60 vid: 16433 (II) GLINT(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853 (II) GLINT(0): #2: hsize: 1024 vsize 768 refresh: 85 vid: 22881 (II) GLINT(0): #3: hsize: 1280 vsize 1024 refresh: 75 vid: 36737 (II) GLINT(0): #4: hsize: 1280 vsize 1024 refresh: 85 vid: 39297 (II) GLINT(0): #5: hsize: 1600 vsize 1200 refresh: 75 vid: 20393 (II) GLINT(0): #6: hsize: 1600 vsize 1200 refresh: 85 vid: 22953 (II) GLINT(0): #7: hsize: 1152 vsize 864 refresh: 75 vid: 20337 Does this mean it thinks I *can* have a 1600x1200 setup? -- Chris Green (chris(a)areti.co.uk) "Never ascribe to malice, that which can be explained by incompetence."

1 0

xorgconfig, video resolution, xdm and gdm - queries and tips
by Chris Green 25 Nov '04

25 Nov '04

This is as much a story of my upgrade as anything but there are some tips and questions embedded in it as well. As I said the Slackware 9.1 to 10 upgrade went pretty smoothly, all the really vital things like the networking started up with no problems at all after the upgrade. The two things that needed some work were the xfree -> xorg move and xdm. After finding xorgconfig (thank you whoever it was) the basics of video configuration were quite easy. Just copying my xfree config file to xorg.conf worked reasonably well and I then ran xorgconfig to check it as much as to change it. The next issue was that xdm didn't work, since I use a Win2k system to display my Linux desktop (via the Cygwin/X server) this was rather vital to me. I found that 'startx' would bring my xfce desktop up OK on the local display but xdm gave an error in its log file saying that XDMCP failed to open a socket with errno 97. A bit of investigation (Google search) suggested that this might be that the xdm I had was expecting IPV6. So I sidestepped the problem by trying gdm instead, this works perfectly and looks a bit prettier too so I'm happy. I did have a bit of a problem initially when trying to login on my Win2k machine but that turned out to be because I was typing away on the wrong keyboard! The one remaining video issue is that I can't get the native video resolution that I want, the card supports the 1600x1200 that I want and so does the display but I can't get it to actually do it. The remote desktop via gdm is at 1600x1200 but when I fire up a local desktop I get only 1024x768. I've put the 1600x1200 resolutions as my first choice in the xorg.conf file, what is limiting it to less? -- Chris Green (chris(a)areti.co.uk) "Never ascribe to malice, that which can be explained by incompetence."

4 9

Printer fonts
by Chris Green 25 Nov '04

25 Nov '04

What decides the fonts available for printers? I want to make a few more fonts available when printing from knoda (a KDE application) as there isn't a decent sans-serif font at the moment. How do I add a printer font for use in a specific application? -- Chris Green (chris(a)areti.co.uk) "Never ascribe to malice, that which can be explained by incompetence."

2 2

Fonts (well typefaces actually) and printers in Linux
by Chris Green 24 Nov '04

24 Nov '04

My upgrade to Slackware 10 went fairly smoothly last night and I seem to have most of the system back to normal - with the intended bonus that I now have a set of compatible and reasonably up to date libraries to build against. The next task in my migration of an Access 97 application to Linux is to make more fonts available for printing from a couple of KDE applications. I can't at the moment get my mind round where the fonts on the system come from as each application I run seems to have a different view of what's available. However the particular requirement at the moment is to get a decent looking sans-serif font for knoda to print with. Many applications (and most of KDE) seem to have the Bitstream Vera font family available as screen and print fonts. However knoda doesn't show these as available, all it shows is an odd collection (from memory):- Courier Utopia Cursor Monospace a.n.other (Dingbats?) In reality when I print anything in size 10 from knoda it looks like Courier to me. I installed knoda using a Slackware package (i.e. it was pre-compiled in a .tgz file), could this be the problem? I.e. whoever built knoda and packaged it had a different set of fonts which don't match what I have? If so it's not a problem to build it myself. As a more generic question it would be useful to know how applications decide what printer fonts are available. All the FAQs and HOWTOs I've looked at don't seem to address the issue of printer fonts at all, they seem to assume that once you can see the font on screen everything is done. -- Chris Green (chris(a)areti.co.uk) "Never ascribe to malice, that which can be explained by incompetence."

1 1

xdm error
by Chris Green 23 Nov '04

23 Nov '04

OK, now I have the xorg.conf file on the run I'm left with the xdm error. There is an error in the xdm.log file:- xdm error (pid 7439): XDMCP socket creation failed, errno 97 A Google search hasn't brought up much but the one thing that's possible is that xdm is expecting IPV6 and I don't have IPV6, this seems odd as I've installed a well debugged distribution. Any ideas anyone? -- Chris Green (chris(a)areti.co.uk) "Never ascribe to malice, that which can be explained by incompetence."

2 1