Re: [SLUG] X11 modeline calculator?
lukekendall == lukekendall [EMAIL PROTECTED] writes: lukekendall I have a spiffy new monitor that is capable of doing lukekendall [EMAIL PROTECTED] and even [EMAIL PROTECTED], but the modes lukekendall don't seem to be recognised. The closest I get is: lukekendall Is there an X11 modelines calculator that you can feed lukekendall the specs of the display modes into, to get correct lukekendall modelines to add in manually? I confess that the lukekendall description in the howto either leaves some terms lukekendall undefined, or else the failing is with me and I just lukekendall can't wrap my head around how to calculate it manually lukekendall from the info I have in the vendor's specs. It's not actually that hard to calculate the modeline. You need to know the maximum clock frequency and vertical refresh frequency of your monitor, and the minimum vertical and horiz sync times. Then the modeline is in two halves -- horizontal and vertical. I usually use the new format now. Then your modeline will be something like: Mode 1920x1440 DotClock 300 # Max frequency HTimings 1920 H H H VTimings 1440 V V V EndMode where H is 1920 plus how many dot clocks after the scan before the horizontal sync pulse, H is H plus the Hsync width divided by the dot clock, and H is the total time for each horzontal scan. Vertical timings are similar. Anyway, the standard VESA GTF timings for 1920x1440 are close to: Mode 1920x1440 DotClock 341.35 HTimings 1920 2072 2299 2656 VTimings 1440 1441 1444 1512 Flags -HSync +VSync EndMode And for [EMAIL PROTECTED] they are Mode 2048x1536 DotClock 340.5 HTimings 2048 2216 2440 2832 VTimings 1536 1537 1540 1603 Flags -HSync +VSync EndMode You can tweak them a little if you need to. -- Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au The technical we do immediately, the political takes *forever* -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] X11 modeline calculator?
On 26 Jan, Peter Chubb wrote: It's not actually that hard to calculate the modeline. You need to know the maximum clock frequency and vertical refresh frequency of your monitor, and the minimum vertical and horiz sync times. Then the modeline is in two halves -- horizontal and vertical. I usually use the new format now. Then your modeline will be something like: Mode 1920x1440 DotClock 300 # Max frequency HTimings 1920 H H H VTimings 1440 V V V EndMode where H is 1920 plus how many dot clocks after the scan before the horizontal sync pulse, H is H plus the Hsync width divided by the dot clock, and H is the total time for each horzontal scan. Ah. Yes, I remember the problem I had, now: not enough knowledge. :-) How do you work out the horizontal sync pulse? If X says: (II) NV(0): Supported additional Video Mode: (II) NV(0): clock: 229.5 MHz Image Size: 392 x 294 mm (II) NV(0): h_active: 1600 h_sync: 1664 h_sync_end 1856 h_blank_end 2160 h_border: 0 (II) NV(0): v_active: 1200 v_sync: 1201 v_sync_end 1204 v_blanking: 1250 v_border: 0 (II) NV(0): Serial No: 24-CD405 (II) NV(0): Monitor name: IBM C220P CRT (II) NV(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 130 kHz, PixClock max 370 MHz (II) NV(0): end of DDC Monitor info (==) NV(0): Using gamma correction (1.0, 1.0, 1.0) (II) NV(0): IBM C220P CR: Using hsync range of 30.00-130.00 kHz (II) NV(0): IBM C220P CR: Using vrefresh range of 50.00-160.00 Hz (II) NV(0): Clock range: 12.00 to 350.00 MHz I assume this means the maximum clock frequency is 350 MHZ (dot clock 350)? Or is it PixClock max, 370? And if the manual says it can do 1920x1440 at 85HZ, then that means the vertical frequency is 85? The minimum vertical and hztl sync times ...? I have no idea. Are they related to V min (50) and H min (30)? What is the hsync width? Sigh. There are just too many variables that I don't have a definition for, and only a vague understanding of. :-( Vertical timings are similar. Anyway, the standard VESA GTF timings for 1920x1440 are close to: Mode 1920x1440 DotClock 341.35 HTimings 1920 2072 2299 2656 VTimings 1440 1441 1444 1512 Flags -HSync +VSync EndMode And for [EMAIL PROTECTED] they are Mode 2048x1536 DotClock 340.5 HTimings 2048 2216 2440 2832 VTimings 1536 1537 1540 1603 Flags -HSync +VSync EndMode You can tweak them a little if you need to. I tried this in the Monitor section: Mode 1920x1440 DotClock 350 HTimings 1920 2072 2299 2656 VTimings 1440 1441 1444 1512 Flags -HSync +VSync EndMode Mode 2048x1536 DotClock 350 HTimings 2048 2216 2440 2832 VTimings 1536 1537 1540 1603 Flags -HSync +VSync EndMode But got the error: Parse error on line 59 of section Monitor in file /etc/X11/XF86Config-4 Unknown flag string (EE) Problem parsing the config file (EE) Error from xf86HandleConfigFile() By commenting out the Flags lines, I was able to get the 2048x1536 mode to work, though the 1920x1440 mode looks dangerous - the screen sort of folds back over itself and looks dark. You can recognise where the windows (folded horizontally) are. Should I have left the DotClock at your 341.5, or perhaps tried 370? Does that affect the other numbers? Since it divides the dot clock, you said, I thought it should. Sorry for being so thick. luke -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Copying a CD to disk image
Sluggers, I've always been able to make a copy of a cd or floppy onto the hard disk by using dd. I.E dd if=/dev/cdrom of=myimage.iso I've been trying to do this with some FC3 cd's but after copying about 630Mb the process starts throwing messages up onto the console about bad block read's. This goes on for several minutes and trying to kill the dd process doesn't seem to work, though it eventually dies. When I mount the resulting .iso images with -o loop they appear ok and I can see all the directories and file names but if I try to copy an .rpm from the mounted file system it's no good. So obviously the cd's are dud right! BUT! I've just done an install of a working system from the very same CD's and even ran through the little check media utility at the start which said the CD's were OK. What give's? Pete P.S I've tried using dd's bs=512, 1024 and 2048 but the result is unchanged. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Copying a CD to disk image
sounds like you're out of luck. as a last resort, you could try mounting the cd, copying recursivley the contents to a temporary directory then using mkisofs to make the iso. fwiw. i've only ever had this problem on burnt disks. they appear fine in some cd devices and have difficulties in others. regards, brett On Thursday 27 January 2005 08:57, Peter Rundle wrote: Sluggers, I've always been able to make a copy of a cd or floppy onto the hard disk by using dd. I.E dd if=/dev/cdrom of=myimage.iso I've been trying to do this with some FC3 cd's but after copying about 630Mb the process starts throwing messages up onto the console about bad block read's. This goes on for several minutes and trying to kill the dd process doesn't seem to work, though it eventually dies. When I mount the resulting .iso images with -o loop they appear ok and I can see all the directories and file names but if I try to copy an .rpm from the mounted file system it's no good. So obviously the cd's are dud right! BUT! I've just done an install of a working system from the very same CD's and even ran through the little check media utility at the start which said the CD's were OK. What give's? Pete P.S I've tried using dd's bs=512, 1024 and 2048 but the result is unchanged. -- Brett Fenton NetRegistry Pty Ltd ___ http://www.netregistry.com.au/ Tel: +61 2 96996099 | Fax: +61 2 96996088 PO Box 270 Broadway | NSW 2007, Australia Your Total Internet Business Services Provider Trusted by 10,000s of Oz Businesses Since 1997 -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] X11 modeline calculator?
lukekendall == lukekendall [EMAIL PROTECTED] writes: lukekendall On 26 Jan, Peter Chubb wrote: It's not actually that hard to calculate the modeline. where H is 1920 plus how many dot clocks after the scan before the horizontal sync pulse, H is H plus the Hsync width divided by the dot clock, and H is the total time for each horzontal scan. lukekendall Ah. Yes, I remember the problem I had, now: not enough lukekendall knowledge. :-) How do you work out the horizontal sync lukekendall pulse? If X says: lukekendall (II) NV(0): Supported additional Video Mode: (II) NV(0): lukekendall clock: 229.5 MHz Image Size: 392 x 294 mm (II) NV(0): lukekendall h_active: 1600 h_sync: 1664 h_sync_end 1856 h_blank_end lukekendall 2160 h_border: 0 (II) NV(0): v_active: 1200 v_sync: 1201 lukekendall v_sync_end 1204 v_blanking: 1250 v_border: 0 (II) NV(0): lukekendall Serial No: 24-CD405 (II) NV(0): Monitor name: IBM C220P lukekendall CRT (II) NV(0): Ranges: V min: 50 V max: 160 Hz, H min: lukekendall 30 H max: 130 kHz, PixClock max 370 MHz (II) NV(0): end lukekendall of DDC Monitor info lukekendall I assume this means the maximum clock frequency is 350 lukekendall MHZ (dot clock 350)? Or is it PixClock max, 370? And if No, 370MHz. But you need to use a lower freq. to get the characteristics you want.lukekendall I tried this in the Monitor section: lukekendall Mode 1920x1440 DotClock 350 HTimings 1920 2072 lukekendall 2299 2656 VTimings 1440 1441 1444 1512 Flags -HSync lukekendall +VSync EndMode Mode 2048x1536 DotClock 350 HTimings lukekendall 2048 2216 2440 2832 VTimings 1536 1537 1540 1603 Flags lukekendall -HSync +VSync EndMode lukekendall But got the error: lukekendall Parse error on line 59 of section Monitor in file lukekendall /etc/X11/XF86Config-4 Unknown flag string (EE) Problem lukekendall parsing the config file (EE) Error from lukekendall xf86HandleConfigFile() lukekendall By commenting out the Flags lines, I was able to get the lukekendall 2048x1536 mode to work, though the 1920x1440 mode looks lukekendall dangerous - the screen sort of folds back over itself and lukekendall looks dark. You can recognise where the windows (folded lukekendall horizontally) are. That implies the HSync pulse is wrong. Try running xvidtune, and adjusting it. lukekendall Should I have left the DotClock at your 341.5, or perhaps Yes. lukekendall tried 370? Does that affect the other numbers? And yes. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Copying a CD to disk image
Brett Fenton wrote: sounds like you're out of luck. as a last resort, you could try mounting the cd, copying recursivley the contents to a temporary directory then using mkisofs to make the iso. fwiw. i've only ever had this problem on burnt disks. they appear fine in some cd devices and have difficulties in others. regards, brett On Thursday 27 January 2005 08:57, Peter Rundle wrote: Sluggers, I've always been able to make a copy of a cd or floppy onto the hard disk by using dd. I.E dd if=/dev/cdrom of=myimage.iso I've been trying to do this with some FC3 cd's but after copying about 630Mb the process starts throwing messages up onto the console about bad block read's. This goes on for several minutes and trying to kill the dd process doesn't seem to work, though it eventually dies. When I mount the resulting .iso images with -o loop they appear ok and I can see all the directories and file names but if I try to copy an .rpm from the mounted file system it's no good. So obviously the cd's are dud right! BUT! I've just done an install of a working system from the very same CD's and even ran through the little check media utility at the start which said the CD's were OK. Did you install this working system using the very same CDROM drive that you are using with dd ? Your problem may be related to media/hardware quality rather than data corruption. The drive you are using to do the dd with may simply not like that cd media. Just last night I was having problems reading my Q3/UrbanTerror CD using both a Sony a Mitsubishi CDROM drive. However the same disk worked perfectly fine in an Optorite CDROM. I've since copied that to another brand CD (TDK) and now all my workstations drives are happy and I can play UrT3.1 again :) - Rocci -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] FusionPHP.net News PHP Script
FusionPHP.NET Visit us today, fullfilling your PHP needs!!! http://www.fusionphp.net/ We have the BEST free php news script in the world. Please spread the word about our website and our scripts!!! Forward this email to 250 people and we'll pay you $5.00 US dollars via paypal. Thank you, Patatten Boerken http://fusionphp.net/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Re: Copying a CD to disk image
I'd suggest that it may be the drive if it is a different drive from that used for the install. I have 3 PCs and 3 DVDrs, 1CDRW and 1 DVDRW. Of the 8 drives, one ( a liteonit DVDR) will not read DVD+R or RW's or DVD-R or RWs, and sometimes CDRWs. Fortunately the DVD+ - RW is external firewire/usb drive, so no problems. Why not try K3B to copy iso to hard disk? or try a LiveCD distro to copy the CDs? Another thought - are the cd's that you are copying from 650 or 700 mb ? That's something that needs to be watched with some distros these days. Bill -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] X11 modeline calculator?
[EMAIL PROTECTED] wrote:
Ah. Yes, I remember the problem I had, now: not enough knowledge. :-)
Umm, {:-), have you read the Video-Timings(?)-HowTO (or RTFM politely).
It is a bit head turning.
My 2c, can your video card handle these modes?
Sorry for being so thick.
Naah, just don't try the readings or calcs after a party in the week
prior. {:-).
--
Terry Collins {:-)}}} email: terryc at woa.com.au www:
http://www.woa.com.au
Wombat Outdoor Adventures Bicycles, Computers, GIS, Printing,
Publishing
People without trees are like fish without clean water
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Re: Copying a CD to disk image
On Thu, 2005-01-27 at 12:58, Bill wrote: I'd suggest that it may be the drive if it is a different drive from that used for the install. The problem is not the drive, it's with a gray area in the POSIX standards. Drives with removable media don't have an end-of-file concept. Thus, you _can't_ stat /dev/cdrom and get the length of the disc image in bytes from the st_size field, you get zero. Quite literally, the kernel doesn't know, even if the device drive does... and the stat call isn't passed to the device driver to fill in. Even if it was, it wouldn't help for things like tape drives which don't know where the end is until they go past it. Typically, you have to seek within a device like this, reading a byte at a time and seeing what you get back. With a binary chop, you can determine the size of the disc in the CD drive fairly quickly. Once you have the size, you can plug it into dd. Or: you can read the iso9660 header and discover the exact length that way (it's a bug in mkisofs if the two methods don't match). The gray area is this: some device drivers report end-of-file when you attempt to read a block past the end if the disc (read returns 0), while others report I/O error (read returns -1 with errno set to EIO or similar). The dd command works just fine with the first form, but not with the second form. And device drivers run about 50/50 for what the author chose to return. -- Peter Miller [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] X11 modeline calculator?
[EMAIL PROTECTED] wrote: I have a spiffy new monitor that is capable of doing [EMAIL PROTECTED] and even [EMAIL PROTECTED], but the modes don't seem to be recognised. The closest I get is: (II) NV(0): Supported Future Video Modes: (II) NV(0): #0: hsize: 1920 vsize 1440 refresh: 85 vid: 22993 (--) NV(0): Virtual size is 1920x1440 (pitch 1920) (**) NV(0): Default mode 1600x1200: 229.5 MHz, 106.2 kHz, 85.0 Hz (**) NV(0): Default mode 1920x1440: 297.0 MHz, 112.5 kHz, 75.0 Hz Is there an X11 modelines calculator that you can feed the specs of the display modes into, to get correct modelines to add in manually? I confess that the description in the howto either leaves some terms undefined, or else the failing is with me and I just can't wrap my head around how to calculate it manually from the info I have in the vendor's specs. luke This is what I use: /usr/X11R6/bin/gtf Geoff -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] X11 modeline calculator?
The solutions in the thread so far seem a little labor intensive: are y'all aware it should be possible to get exact modelines from your Windows monitor.inf file? I think there's even tools to put them into the format you'd use in xorg.conf (or XF86ConFiGrANdoMCAPS.CONFOMGWTFBBQ for those so inclined). Mike -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
