Urmas Posted February 10, 2010 Posted February 10, 2010 Uh... email it to me... I'll see if I can make any sense of it (or do a snippety snip snip at least) tomorrow (soon midnight in Urmas Time Zone). :thumbsup:P.S. Just open it with Gedit... easier for you to deal with it thattaway. Quote
Cluttermagnet Posted February 10, 2010 Author Posted February 10, 2010 Uh... email it to me... I'll see if I can make any sense of it (or do a snippety snip snip at least) tomorrow (soon midnight in Urmas Time Zone). :thumbsup:P.S. Just open it with Gedit... easier for you to deal with it thattaway.Ah, yes- good old gedit. OK, will email it to you soon. Meanwhile, I will continue to reread that piece about "Re: How to find HorizSync / VertRefresh rates?" for better understanding. Quote
Urmas Posted February 11, 2010 Posted February 11, 2010 Uh... it's using VESA? See: (II) VESA(0): initializing int10(II) VESA(0): Primary V_BIOS segment is: 0xc000(II) VESA(0): VESA BIOS detected(II) VESA(0): VESA VBE Version 2.0(II) VESA(0): VESA VBE Total Mem: 65536 kB(II) VESA(0): VESA VBE OEM: ATI RADEON 9200(II) VESA(0): VESA VBE OEM Software Rev: 1.0(II) VESA(0): VESA VBE OEM Vendor: ATI Technologies Inc.(II) VESA(0): VESA VBE OEM Product: V280(II) VESA(0): VESA VBE OEM Product Rev: 01.00(II) VESA(0): Creating default Display subsection in Screen section "Default Screen" for depth/fbbpp 24/32(==) VESA(0): Depth 24, (--) framebuffer bpp 32(==) VESA(0): RGB weight 888(==) VESA(0): Default visual is TrueColor(==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)(snip)(II) VESA(0): Total Memory: 1024 64KB banks (65536kB)(II) VESA(0): Configured Monitor: Using hsync range of 30.00-70.00 kHz(II) VESA(0): Configured Monitor: Using vrefresh range of 50.00-150.00 Hz(WW) VESA(0): Unable to estimate virtual size(II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)(II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)(II) VESA(0): Not using built-in mode "800x600" (no mode of this name)(II) VESA(0): Not using built-in mode "640x480" (no mode of this name)(II) VESA(0): Not using built-in mode "640x400" (no mode of this name)(II) VESA(0): Not using built-in mode "640x350" (no mode of this name)(II) VESA(0): Not using built-in mode "512x384" (no mode of this name)(II) VESA(0): Not using built-in mode "400x300" (no mode of this name)(II) VESA(0): Not using built-in mode "320x240" (no mode of this name)(II) VESA(0): Not using built-in mode "320x200" (no mode of this name)(WW) VESA(0): No valid modes left. Trying less strict filter...(II) VESA(0): Configured Monitor: Using hsync range of 30.00-70.00 kHz(II) VESA(0): Configured Monitor: Using vrefresh range of 50.00-150.00 Hz(WW) VESA(0): Unable to estimate virtual size(--) VESA(0): Virtual size is 1280x1024 (pitch 1280)(**) VESA(0): *Built-in mode "1280x1024"(**) VESA(0): *Built-in mode "1024x768"(**) VESA(0): *Built-in mode "800x600"(**) VESA(0): *Built-in mode "640x480"(**) VESA(0): *Built-in mode "640x400"(**) VESA(0): *Built-in mode "640x350"(**) VESA(0): *Built-in mode "512x384"(**) VESA(0): *Built-in mode "400x300"(**) VESA(0): *Built-in mode "320x240"(**) VESA(0): *Built-in mode "320x200"(==) VESA(0): DPI set to (96, 96)(II) VESA(0): Attempting to use 60Hz refresh for mode "1280x1024" (124)(II) VESA(0): Attempting to use 85Hz refresh for mode "1024x768" (123)(II) VESA(0): Attempting to use 85Hz refresh for mode "800x600" (122)(II) VESA(0): Attempting to use 85Hz refresh for mode "640x480" (121)(II) VESA(0): Attempting to use 85Hz refresh for mode "640x400" (186)(II) VESA(0): Attempting to use 85Hz refresh for mode "640x350" (1c6)(**) VESA(0): Using "Shadow Framebuffer"(snip)(II) Reloading /usr/lib/xorg/modules//libint10.so(II) VESA(0): initializing int10(II) VESA(0): Primary V_BIOS segment is: 0xc000(II) VESA(0): VESA BIOS detected(II) VESA(0): VESA VBE Version 2.0(II) VESA(0): VESA VBE Total Mem: 65536 kB(II) VESA(0): VESA VBE OEM: ATI RADEON 9200(II) VESA(0): VESA VBE OEM Software Rev: 1.0(II) VESA(0): VESA VBE OEM Vendor: ATI Technologies Inc.(II) VESA(0): VESA VBE OEM Product: V280(II) VESA(0): VESA VBE OEM Product Rev: 01.00(II) VESA(0): virtual address = 0xb3778000, physical address = 0xf0000000, size = 67108864(II) VESA(0): VBESetVBEMode failed...Tried again without customized values.(==) VESA(0): Default visual is TrueColor(==) VESA(0): Backing store disabled(II) VESA(0): DPMS enabledPheew. Do a "Synaptic search" and see if "ati" and/or "radeon" are installed.Defaulting to VESA? I'll be... <grumble grumble grumble>... never seen a wreck like that before... Quote
Urmas Posted February 11, 2010 Posted February 11, 2010 Tried forcing the resolution by tweaking the screen section? Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1024x768" "800x600" EndSubSectionEndSection Does that help?Anyway, the "radeon" driver should work... edit the device section in xorg.conf: Section "Device" Identifier "Configured Video Device" Driver "radeon"EndSection Reboot. And, after the smoke has cleared... Another thing: do you have a 9.10 (Karmic) CD available? Might be worth a try...https://bugs.launchpad.net/ubuntu/+source/linux/+bug/297119 Quote
Cluttermagnet Posted February 11, 2010 Author Posted February 11, 2010 (edited) Thanks, Urmas! Well, regarding Karmic, I had been avoiding it because it installs grub2 and various other horrors I've seen described on the net. But I guess I could try it if all else fails. Yes, I burned a 9.10 CD as soon as it was fully released. And have played with it at least some- but never, so far, have actually installed it anywhere.Amazingly, when I finally got around to checking Synaptic, I found that both the ati and the radeon video drivers were already installed. Who would have guessed? :rolleyes:VESA? Yeah, who would have thunk it? Pretty weird indeed. I think your two proposed changes to xorg.conf are likely winners. I will try that as soon as I get back home (late this evening). Yes, I have to go out and continue my snow clearing, both at home and at my friend's house. The Mid Atlantic just got clobbered this past week. The locals are in no way prepared for a snow removal op as massive as this one- so it will be digging out for at least several more days, so far as the messed up roads around here. Edited February 11, 2010 by Cluttermagnet Quote
Urmas Posted February 11, 2010 Posted February 11, 2010 “Getting an inch of snow is like winning 10 cents in the lottery.”--Calvin Quote
securitybreach Posted February 12, 2010 Posted February 12, 2010 Do not feel bad we have gotten 29 inches in the last 4 days. Although, it is always a pain to shovel snow no matter how much falls. Quote
Cluttermagnet Posted February 14, 2010 Author Posted February 14, 2010 (edited) Tried forcing the resolution by tweaking the screen section?Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1024x768" "800x600" EndSubSectionEndSection Does that help?Anyway, the "radeon" driver should work... edit the device section in xorg.conf: Section "Device" Identifier "Configured Video Device" Driver "radeon"EndSection Reboot. And, after the smoke has cleared... Yes, that helps (the first set of changes to the Screen section). In fact, it helps a lot. After I changed Screen in xorg.conf, it rebooted into 1024x768. Yay! I took a look at System/ Preferences/ Display, and there were now a bunch of options with the largest being 1024x768.Now- I'm just wondering- If I also do the second set of changes to "Device", would the 1280x1024 option return? Or something close to that but in 4:3 configuration? Just curious. But for now, 1024x768 will work on this monitor. BTW I noticed I had to use the horizontal scrollbar while editing my reply here. That was not the case with the larger screen. So the Forum software apparently assumes nobody would be using such a small screen size, eh?Thanks, Urmas! Edited February 14, 2010 by Cluttermagnet Quote
Urmas Posted February 15, 2010 Posted February 15, 2010 Now- I'm just wondering- If I also do the second set of changes to "Device", would the 1280x1024 option return? Or something close to that but in 4:3 configuration?Nope. It'll return if you add "1280x1024" to that Modes "1024x768" "800x600" line.BTW I noticed I had to use the horizontal scrollbar while editing my reply here. That was not the case with the larger screen.That's strange. I'm typing this reply with a vintage HP lappy @1024x768, and it all fits in. No horizontal scrollbars in sight. Quote
securitybreach Posted February 15, 2010 Posted February 15, 2010 BTW I noticed I had to use the horizontal scrollbar while editing my reply here. That was not the case with the larger screen. So the Forum software apparently assumes nobody would be using such a small screen size, eh?This may be caused by your font settings in Firefox-Preferences. Did you fiddle with them when you had the 1280x1024 resolution? That would be the first place to look to get rid of the scrollbar issue. Quote
Cluttermagnet Posted February 15, 2010 Author Posted February 15, 2010 This may be caused by your font settings in Firefox-Preferences. Did you fiddle with them when you had the 1280x1024 resolution? That would be the first place to look to get rid of the scrollbar issue.Good guess, and you're probably about right. It's not so much that I messed with choosing other fonts and such, but I am a liberal user of CTRL + Plus Sign to get the size bigger. I thought I cranked it back down, but maybe one click less than needed to get rid of those control bars. Quote
Cluttermagnet Posted February 15, 2010 Author Posted February 15, 2010 Nope. It'll return if you add "1280x1024" to that Modes "1024x768" "800x600" line.I'll do that, Urmas. Thanks.So does it still make sense to add the Device info?Driver "Radeon" Quote
Cluttermagnet Posted February 15, 2010 Author Posted February 15, 2010 (edited) You guys are the best! This latest lesson about Ubuntu video and ATI is going into my little spiral notebook with other important "Linux lessons learned". No doubt I will encounter this again.They keep changing things so fast, and I see this decreased emphasis on xorg now. Heck, besides the grub2 thing, the de-emphasis of xorg is another thing discouraging me from moving forward with 7.10. I think I'll stick with Jaunty a bit longer... Edited February 16, 2010 by Cluttermagnet Quote
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.