This page gives the supported modes for this Samsung TFT monitor:
http://www.pcstats.com/articleview.cfm?articleid=610&page=5
Resolution Freq Hor. Freq Ver. Pixel Clock Standard
640x350 31.5kHz 70Hz25.2MHz VGA
720x400 31.5kHz 70Hz
Can you please file a new bug with the "0 Hz" mode seen with the VESA
driver in comment #41?
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
When I connected without the KVM switch, I used no special cables or
adapters - the monitor's cable was plugged directly into the gBox
computer.
By the way I haven't recorded the output of the get-edid | parse-edid on
the gBox - I couldn't install those for Jaunty and the installed system
on that
Thanks, the two logs are practically identical, so maybe the kvm switch
is not at fault for the missing EDID info. Do you have any other special
arrangements, like socket adapters or long cables? This belongs to the
other bug though.
Anyway, it confirmed that my patch worked, since it came up with
I got the same resolutions with the monitor plugged back into the kvm
switch. Another log appended!
"MiniView" 2-port KVM
** Attachment added: "Xorg.0.log - Jaunty - using kvm switch now."
http://launchpadlibrarian.net/21493740/Xorg.0.log
--
No signal with Samsung SyncMaster 750s and ProSava
I just ran the 2.2.1+git20081230.aea0496f-0ubuntu0tormod3 driver, and it
started into 800x600 mode (with allowable modes
800x600, 640x480, ). At the moment I have the monitor plugged directly
into the gBox computer. I'll retry with the kvm switch.
** Attachment added: "Xorg.conf using the
BTW, please test as before using the kvm switch (which you didn't
mention here...). This particular bug only kicks in when there is no
EDID.
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member
Please test the 2.2.1+git20081230.aea0496f-0ubuntu0tormod3 in my PPA. It
should fix the invalid (0 Hz) mode issue, so X should start with the
default sync ranges (using the default xorg.conf or none at all).
Not having EDID info, and thus not starting in the monitor's 1024x768
mode is a separate i
Thanks!
Now I'm going to revisit bug #255561 - which refers to the same Samsung
display but a different display card on a Dell machine.
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of
Thanks, that was successful! I think we are circling in on the issue.
This graphic card is a laptop chipset and usually has an LCD connected.
The driver is able to detect that the LCD is not there, but looks up the
sync range information from the panel driver anyway, which is just
nulls. This is ad
Log file for second case
** Attachment added: "Xorg.0.log for second case"
http://launchpadlibrarian.net/21440895/Xorg.0.log4
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of Ubuntu
B
1) I tried first editiing the original xorg.conf, changing 'vesa' to
'savage'.
2) Then I tried the above way: booting with "text", but not specifying
safe mode.
In each case, a compatible screen mode was not found, and the X server
failed to start.
Here, I have attached the log file for the fi
The simplest is if you boot with the "text" parameter, leave the
xorg.conf as it is (savage should be picked anyway) and install and run
the new driver.
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you a
I think the xorg.conf generated when the system started up in failsafe
mode specifies "vesa" just because the system was started in failsafe
mode. So I should have changed "vesa" to "savage".
Now my xorg.conf with all the screen parameters does specify "savage",
so the right driver would have been
This evening I repeated the experiment, this time with my old xorg.conf
file containing explicit driver settings, such as:
Section "Device"
Identifier "S3 Inc. VT8375 [ProSavage8 KM266/KL266]"
Driver "savage"
BusID "PCI:1:0:0"
Option
It can be seen in the log that X started with the "vesa" driver - the
one used by "failsafe mode", instead of the debug savage driver. I don't
know why, it worked fine with my own savage laptop. Well, I now included
the debug stuff in the new xserver-xorg-video-savage 2.2.1+git20081230
.aea0496f-0u
The date in the log file is in UTC - I hadn't set the time zone.
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I tried the new debug package containing a screen driver. It was able to start
X , arriving at a screen resolution of 848x600 at 61 Hz.
Once I started, the user switcher was aborted (as usual) I suspect that is due
to my starting with 'startx' rather than a login.
Trying to switch screen modes,
BTW, Guido's bug 212510 was a bit different, because he had EDID
transfer working.
You have two problems:
1) EDID can't be retrieved from the monitor. The monitor should be fine (since
Guido has the same) but there is something specific to your prosavage card that
fails.
2) In lack of probed s
The EDID transfer (over DDC) fails so the driver can not retrieve the
sync ranges from the monitor. I can imagine that Hardy used to supply
some default sync ranges, which made it come up in 800x600. When you
specify the wider ranges in xorg.conf, 1024x768 is found to be possible.
I am not sure if
This Xorg.0.log file was generated as requested - with no xorg.conf
file.
There was no crash - no screen was found, as the log file says, so
console 1 stayed in text mode.
Putting in the old xorg.conf (as in the previous posting) allows X to
start.
** Attachment added: "Xorg.0.log - no xorg.conf
Here's the xorg.conf file - we seem to have some problem getting the
right files! :)
** Attachment added: "xorg.conf - jaunty"
http://launchpadlibrarian.net/21273903/xorg.conf
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bu
Great! But this is supposed to work out-of-the-box without any modified
xorg.conf. Can you please try without any xorg.conf? It might be a challenge to
fish out the log if the monitor goes off, but there are some ways:
On a virtual console (alt-F2 for instance, not the one where you run startx),
Here is the latest xorg.conf that works with the 9.04 driver
The log file shows complaints about things like nonexistent fonts,
nothing serious.
The real remaining issue, in my opinion, is whether the installer will
recognize which driver to use, and set up the right screen mode, and
when that wi
Here is the latest xorg.conf that works with the 9.04 driver
The log file shows complaints about things like nonexistent fonts,
nothing serious.
The real remaining issue, in my opinion, is whether the installer will
recognize which driver to use, and set up the right screen mode, and
when that wi
That was the wrong xorg.conf file.
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
With that driver, I was able to startx ok!
The only glitch was that the user-switcher applet wouldn't start (or
kept stopping each time I clicked on the popup which announced that it
was failing).
I'll attach the log file here.
** Attachment added: "Xorg.0.log - jaunty"
http://launchpadlibrar
Yes, that is the right file.
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
The nearest file I find is
xserver-xorg-video-savage_2.2.1+git20081230.aea0496f-0ubuntu0tormod_i386.deb
(96.6 KiB)
On Thu, Jan 15, 2009 at 2:26 PM, Tormod Volden wrote:
> The right version for Jaunty would be xserver-xorg-video-savage -
> 1:2.2.1+git20081230.aea0496f-0ubuntu0tormod . On the PP
I can't find the file. Could you send me the exact URL for the page it's
on?
On Thu, Jan 15, 2009 at 2:26 PM, Tormod Volden wrote:
> The right version for Jaunty would be xserver-xorg-video-savage -
> 1:2.2.1+git20081230.aea0496f-0ubuntu0tormod . On the PPA page there is a
> column called "Series
Thanks! I'll download that tonight or tomorrow, and try it. I suspect
it will work. And I'll post my results.
It's good this is going upstream - this problem affects not only
Ubuntu and Debian, but Fedora as well, when I've tried recent live
CDs. Probably several other distros, including Gentoo. I
The right version for Jaunty would be xserver-xorg-video-savage -
1:2.2.1+git20081230.aea0496f-0ubuntu0tormod . On the PPA page there is a
column called "Series" which tells which versions are for Jaunty. I am
sorry if this was not clear.
The reason I am pestering you to get a ModeDebug log from J
I went back to trying the 8.10 Intrepid live CD - using 'text' and
eliminating 'splash' in the boot line enables it to boot in text mode,
then using the old xorg.conf from 7.04 enables X to start.
On Wed, Jan 14, 2009 at 3:49 PM, Tormod Volden wrote:
> If you add "text" to the boot parameters (th
Here is the log, trying to startx with the driver on the Jaunty alpha
disk.
As I said above, I was unable to install the driver under development:
xserver-xorg-video-savage_2.2.1+git20081117.aea0496f-
0ubuntu0tormod_i386.deb
** Attachment added: "Xorg.0.log 14 Jan 2009"
http://launchpadlib
I made some progress - I was able to boot into text mode after
modifying the boot parameters - adding 'text' and removing the
'splash', and specifying the vesa mode.
At this point, I was able copy files to this system from another, using
scp.
I then copied the experimental driver and my old xorg
Oh, good. I was wondering whether there was a way to boot in text
mode. That will make it MUCH easier to proceed!
Also removing the splash progress bar might help, I'll see.
I'll be home in a couple of hours to try this! Then I can try either
the new driver, or my old xorg.conf file, or both. I e
If you add "text" to the boot parameters (the kernel line, F6 in the CD
boot menu), it will not start X. You can then log in on the console and
install the driver like mentioned above. To start X an X session, type
"startx".
I don't think the driver is trying out different modes, it's just the
mon
I just tried again to boot the 9.04 'jaunty' CD - I was unable to get
a console with ctrl-alt-F1, trying several times before and after the
screen started displaying the little windows saying the current screen
mode. Apparently the driver is trying a number of modes, and doesn't
get feedback from t
Is it not possible to switch to a console with ctrl-alt-F1?
I was hoping you could get X running with the vesa driver, and then
install the patched driver from the internet. If you have it already
downloaded on the hard drive, that's even better, especially in the case
vesa won't work. As long as
I can't get the Jaunty CD to boot into X, even in 'safe' mode.
The Samsung Syncmaster display won't accept any of the modes the driver
tries.
Peter
On Sun, Jan 11, 2009 at 12:04 PM, Tormod Volden
wrote:
> This certainly looks wrong in your original log file:
> (II) SAVAGE(0): Configured Monitor
So I should download the normal Jaunty live CD, boot in failsafe vesa
mode, also have your downloaded driver on my HD. How do I install your
driver from where it is?
Peter
On Sun, Jan 11, 2009 at 3:28 PM, Tormod Volden wrote:
> Please also add
> Option "ModeDebug" "true"
> to the Device sectio
Please also add
Option "ModeDebug" "true"
to the Device section of your xorg.conf.
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
This certainly looks wrong in your original log file:
(II) SAVAGE(0): Configured Monitor: Using hsync value of 0.00 kHz
(II) SAVAGE(0): Configured Monitor: Using vrefresh value of 0.00 Hz
It would be nice if you could test Jaunty and provide an Xorg.0.log.
Unfortunately there are reports that the
I finally succeeded in getting a log file from an attempt to boot the
8.10 disk. Also I was able to get the screen to start in a 1024x768
mode.
I was able to get into a console after identification of the display
failed. At that point, I was able to save the Xorg.0.log file, as
before. it is alrea
I also have the xorg.conf and Xorg.0.log files from Hardy 8.04.1
attached above.
I'll make another attempt to get the files from the failed attempts to
boot or to start installing 8.10.
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received
I sent the 8.04 Feisty xorg.conf and Xorg.0.log files on 2008-11-08 -
see above.
I can send hardy 8.04 files if that will help - that's a case where I
had to overwrite the xorg.conf with the Feisty version.
I'll see what I can do regarding 8.10 files. I didn't get very far into
the live boot or i
Peter send the xorg.conf generated at 7.04 via attach mail, when boot at
800 x 600 download the xorg.conf and overwrite this in 8.10, This
impossible?
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are
This is marked as 'incomplete'. What is needed?
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
xorg.conf file from alternate install of hardy 8.04.1
The maximum screen resolution with this file was 800x600.
I was able to get 1024x768 resolution by replacing this with the
xorg.conf from Feisty 7.04 (see above).
** Attachment added: "xorg.conf from hardy alternate install"
http://launchp
Here is an Xorg.0.log file generated from installing hardy on the same
system, using the alternate CD.
An attempt to boot from the live CD (desktop CD) failed. I wasn't able
to save the log file from that failed attempt.
** Attachment added: "Xorg.0.log from alternate install of hardy 8.04.1"
Here is the xorg.conf file generated by booting feisty as a live CD.
This file may be used to solve resolution problems under Hardy as well.
** Attachment added: "xorg.conf on feisty"
http://launchpadlibrarian.net/19496270/xorg.conf
--
No signal with Samsung SyncMaster 750s and ProSavage8
htt
Here is the /var/log/Xorg.0.log from booting Feisty 7.04. The display
was initialized properly in 1024x768 resolution, the maximum supported
byt the Samsung display.
** Attachment added: "Xorg.0.log - feisty"
http://launchpadlibrarian.net/19496191/Xorg.0.log
--
No signal with Samsung SyncMas
Here is the /var/log/Xorg.0.log
In this case, I went through the motions of an actual install, rather
than a live boot. The boot failed, without installing anything, but
ended up in a shell, so that I could copy the log file to the hard disk.
A quick glance at the file tells me there is useful in
That would be from hardy, since I can't boot intrepid and get at a
shell.
On Fri, Nov 7, 2008 at 1:26 AM, Bryce Harrington
<[EMAIL PROTECTED]> wrote:
> Hi peterbe,
>
>
> Thanks for including the attached files. Could you also include your
> /var/log/Xorg.0.log?
>
>
> ** Changed in: xserver-xorg-
Hi peterbe,
Thanks for including the attached files. Could you also include your
/var/log/Xorg.0.log?
** Changed in: xserver-xorg-video-savage (Ubuntu)
Status: New => Incomplete
--
No signal with Samsung SyncMaster 750s and ProSavage8
https://bugs.launchpad.net/bugs/294899
You receiv
** Attachment added: "This is the xorg.conf file which works under hardy,
generated by booting a 7.04 CD. lspci shows VGA compatible controller: S3 Inc.
VT8375 [ProSavage8 KM266/KL266]"
http://launchpadlibrarian.net/19441069/xorg.conf
--
No signal with Samsung SyncMaster 750s and ProSavage
56 matches
Mail list logo
