Gowator Posted June 6, 2003 Report Share Posted June 6, 2003 Do you by anychance have your RH7.3 XF6Config file???? Did you try removing the frequency timings altogether? Delete all the other modes except 16bpp x 1024x768 ... ie. just SubSection "Display" Depth 16 Modes "1024x768" EndSubSection Remove the modelines and try again. Alternatively, do you have a conventional monitor capable of 1024x768??? If so plug it in and see if it will work. If so you know its monitr timings that are causing the problem. You might be able to then use xf86cfg to set the modeline for you that fits your range for the hansol. RestartX (CRTL+ALT+BKSPC) If your doing all this can I recommend you do it from Run Level 3 without dm (graphic login). Its much easier firing off X etc. with different XF86Config 's that way Quote Link to comment Share on other sites More sharing options...
spinynorman Posted June 6, 2003 Author Report Share Posted June 6, 2003 I was going to keep Red Hat so I could try dual-booting, but when it didn't appear on the boot list on my first install, I zapped it. Only have the one monitor. I will try some of your suggestions over the weekend. If all else fails, I may try XFree3. This afternoon I'm going to swap my ISDN modem. Wish me luck. 8) Quote Link to comment Share on other sites More sharing options...
spinynorman Posted June 9, 2003 Author Report Share Posted June 9, 2003 First the latest on the modem. The dealer demonstrated it on a Windows machine on a non-ISDN line, so it would seem to be a standard Speedtouch model, which is being wrongly identified. Are there commands I can use outside MCC to try and connect and hopefully get some meaningful error message? :?: As far as the monitor is concerned, I removed the modelines and the frequency timings and left just the 16bpp option. This generated the values listed below. The VR range goes to 76 and the max is 75, which could be a problem I suppose; but the old 'out of range' still appeared - Fh 35.4 Fv 86.9 Pixel 23.5. HOWEVER, when I tried failsafe mode and let the time run out on the Linuxconf menu, I got into KDE without error messages. Is this using the XF86Config-4 file? :?: Section "Monitor" Identifier "monitor1" VendorName "Plug'n Play" ModelName "Flat Panel 1024x768" HorizSync 30-61 VertRefresh 56-76 # Sony Vaio C1(X,XS,VE,VN)? # 1024x480 @ 85.6 Hz, 48 kHz hsync ModeLine "1024x480" 65.00 1024 1032 1176 1344 480 488 494 563 -hsync -vsync # TV fullscreen mode or DVD fullscreen output. # 768x576 @ 79 Hz, 50 kHz hsync ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630 # 768x576 @ 100 Hz, 61.6 kHz hsync ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616 EndSection Section "Device" Identifier "device1" Driver "vesa" Option "DPMS" EndSection Section "Screen" Identifier "screen1" Device "device1" Monitor "monitor1" DefaultColorDepth 16 Subsection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 15 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubsection EndSection I also did a full reinstall to try and use XFree3, as I was given a choice on the original install. However, I found that this only appears with certain cards, and if you can't use the card, it reverts to XFree4. In the time I had available, I made a couple of attempts to run Mandrake Update with my update CD, but it was looking for an internet connection. I've set up /mnt/cdrom2 as a 'security update' source, but perhaps I have to uncheck all the other sources? :?: Quote Link to comment Share on other sites More sharing options...
Gowator Posted June 10, 2003 Report Share Posted June 10, 2003 Been away till today. You can tell which XF86Config its using from the log file in /var/log/XF* Right near the beginiing it should say which one its using. If you kept the Redhat install on a different non mounted partition you could try and find the XF86Config-4 on there. Alternatively override the generated timings with tthe ones from your montitor book. Quote Link to comment Share on other sites More sharing options...
spinynorman Posted June 10, 2003 Author Report Share Posted June 10, 2003 Welcome back, Gowator. :D - Just to bring you up to speed: I only have Mandrake on the machine now, so can't check RH. I have updated the system with my update CD. This has eliminated the ISDN reference on the Speedtouch. Still unable to connect - can I test the connection outside MCC to get a proper error message? :?: My latest XF86Config-4 conforms with the Hansol manual (1024 x 768; HF 48.363 VF 60.004 Clock 65.000): Section "Monitor" Identifier "monitor1" VendorName "Generic" ModelName "Flat Panel 1024x768" HorizSync 31.5-48.5 VertRefresh 40-70 # Sony Vaio C1(X,XS,VE,VN)? # 1024x480 @ 85.6 Hz, 48 kHz hsync ModeLine "1024x480" 65.00 1024 1032 1176 1344 480 488 494 563 -hsync -vsync # TV fullscreen mode or DVD fullscreen output. # 768x576 @ 79 Hz, 50 kHz hsync ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630 # 768x576 @ 100 Hz, 61.6 kHz hsync ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616 EndSection Section "Device" Identifier "device1" Driver "vesa" Option "DPMS" EndSection Section "Screen" Identifier "screen1" Device "device1" Monitor "monitor1" DefaultColorDepth 16 Subsection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 15 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubsection EndSection This works in FAILSAFE mode but in a normal session gives 'out of range Fh 35.4 Fv 86.9 Pixel 23.5'. I will look at the log file this evening, but it's difficult to believe that the XF86Config-4 is being used for the normal session, as the 'out of range' message reports the same figures whatever we put in the file. :? Quote Link to comment Share on other sites More sharing options...
tyme Posted June 10, 2003 Report Share Posted June 10, 2003 by FAILSAFE, do you mean the linux-failsafe option which appears in lilo during boot? Quote Link to comment Share on other sites More sharing options...
spinynorman Posted June 10, 2003 Author Report Share Posted June 10, 2003 by FAILSAFE, do you mean the linux-failsafe option which appears in lilo during boot? Yes. Sorry for not making it clear. Quote Link to comment Share on other sites More sharing options...
tyme Posted June 10, 2003 Report Share Posted June 10, 2003 by FAILSAFE, do you mean the linux-failsafe option which appears in lilo during boot? Yes. Sorry for not making it clear. quite all right, that's what I thought you meant. hmm...anyone know what options FAILSAFE passes to the kernel? Quote Link to comment Share on other sites More sharing options...
Steve Scrimpshire Posted June 10, 2003 Report Share Posted June 10, 2003 I'm not on my Linux box right now, but if I remember correctly, it's devfs=nomount noapic and possibly apci=off Quote Link to comment Share on other sites More sharing options...
ezroller Posted June 10, 2003 Report Share Posted June 10, 2003 I'm not on my Linux box right now, but if I remember correctly, it's devfs=nomount noapic and possibly apci=off You are correct sir! Quote Link to comment Share on other sites More sharing options...
spinynorman Posted June 11, 2003 Author Report Share Posted June 11, 2003 You can tell which XF86Config its using from the log file in /var/log/XF* Have examined the logs after running in normal and linux-failsafe mode, as suggested. The output is basically the same: both use /etc/X11/XF86Config-4 and record the same warning: (WW) VESA(0): config file vrefresh range 40-70Hz not within DDC vrefresh range 56-76Hz The only difference is that the failsafe session fails to display the 'out of range' message. The logs contain information that doesn't appear in the Hansol manual, including the required frequency ranges rather than just the maximums. While looking through various config files, I came across 'XF86Config.test.old'. I don't know where this came from, but it has a list of standard mode timings. With this and the newly discovered ranges, I shall run some more tests tonight. On the subject of the Speedtouch modem, can anyone suggest commands I can use to connect to the internet outside MCC, and hopefully get some meaningful error messages? :?: Thanks for your help so far. Quote Link to comment Share on other sites More sharing options...
Steve Scrimpshire Posted June 11, 2003 Report Share Posted June 11, 2003 modem_run -v -f /usr/share/speedtouch/mgmt.o pppd call adsl (I think that's right) Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted June 11, 2003 Report Share Posted June 11, 2003 On the subject of the Speedtouch modem, can anyone suggest commands I can use to connect to the internet outside MCC, and hopefully get some meaningful error messages? Try running the internet connection routine(drakconnect) from a console as root: # drakconnect At least you'll get error messages printed out from the console which might be helpful. Quote Link to comment Share on other sites More sharing options...
Gowator Posted June 11, 2003 Report Share Posted June 11, 2003 If your booted up in failsafe and everything works then as pointed out the difference is a couple of options in the power management. I guess this could be interfering with power saving on the monitor ?? If the Drake tools havn't worked then I'd try another. Personally xf86cfg works well, I use it especially for mlti-head configs but you can also play with mode timings directly. One nice thing is you can add another card and another monitr and not 'connect them', just make them copies of whats working at the moment then you can try deleting or adding options. From the ACPI stuff I'd get rid of power saving stuff for now. from a quick look comment out Option DPMS OK Ill write the file ::::NOTE your using vesa not the SIS driver !! You still need your layout and keyb mouse parts .... Do this uin run level 3 - then you can CTRL+ALT+BKSPC out and edit if it goes to sh**. Once its loaded you need to change the VESA for the SIS driver....Make sure to comment out the DPMS options for now. Section "Monitor" Identifier "monitor1" VendorName "Generic" ModelName "Flat Panel 1024x768" HorizSync 48 VertRefresh 60 #I think you can specify an exact timing. #My guess is the same chipset is used in the viao, just comment this out # Sony Vaio C1(X,XS,VE,VN)? # 1024x480 @ 85.6 Hz, 48 kHz hsync #ModeLine "1024x480" 65.00 1024 1032 1176 1344 480 488 494 563 -sync -vsync #This might prove useful later !!! # TV fullscreen mode or DVD fullscreen output. # 768x576 @ 79 Hz, 50 kHz hsync #ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630 # 768x576 @ 100 Hz, 61.6 kHz hsync #ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616 #EndSection Section "Device" Identifier "device1" Driver "vesa" #Option "DPMS" EndSection Section "Screen" Identifier "screen1" Device "device1" Monitor "monitor1" DefaultColorDepth 16 #Subsection "Display" #Depth 8 #Modes "1024x768" "800x600" "640x480" #EndSubsection #Subsection "Display" #Depth 15 #Modes "1024x768" "800x600" "640x480" #EndSubsection #This is the safest bet, just get xf86cfg running and you can add more. Subsection "Display" Depth 16 Modes "1024x768" #EndSubsection # Notice I deleted the other resolutions according to the driver it won't support them. #Subsection "Display" #Depth 24 #Modes "1024x768" "800x600" "640x480" #EndSubsection EndSection Quote Link to comment Share on other sites More sharing options...
spinynorman Posted June 12, 2003 Author Report Share Posted June 12, 2003 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.