Norbert, can you please try the savage driver 2.2.1+git20081230
.aea0496f-0ubuntu0tormod3 in my PPA
https://launchpad.net/~tormodvolden/+archive for Jaunty?
It is best if you boot the Jaunty alpha 3 live CD with the "text" kernel (boot)
parameter, then install the package:
Mount your hard drive o
** Description changed:
Binary package hint: ubiquity
On my desktop PC, installing from the Hardy Beta iso fails unless "safe
graphics mode" is chosen (which results in an install that uses a low
graphics resolution). Ehat happens when trying to install in normal
mode is not always t
And my Xsesion error
** Attachment added: "Xsession errors"
http://launchpadlibrarian.net/20419805/xerror
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member of Ubunt
My attention in the lines:
II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(--) SAVAGE(0): No DDC signal
** Attachment added: "Xorg.O.log"
http://launchpadlibrarian.net/20419659/Xorg.0.log
--
[hardy beta] install failure (regression) with ProSavageDDR
More of this bug, but unfortunately the developer do not have a idea
that the issue.
** Attachment added: "Xorg generated with Gutsy"
http://launchpadlibrarian.net/20419609/xorg.conf
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bu
I can confirm that the bug is NOT fixed in Intrepid 8.10 for me either.
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is NOT fixed with Intrepid 8.10 for my gBox computer with a S3
Inc. VT8375 [ProSavage8 KM266/KL266] display controller, connected to a
Samsung SyncMaster 570S TFT display. (see above).
I downloaded the 8.10 desktop ISO, and booted that on this system as a
live CD. The system was unable to
** Tags added: valid-xorg-conf
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
In my case, the issue is the Samsung SyncMaster 570S TFT monitor not
being recognized by automatic configuration. The workaround I used was
to boot a 7.04 live CD, save the xorg.conf file generated by that, and
then to copy that to /etc/X11 after rebooting to 8.04.1. After that I
reboot to make th
I have attached Xorg.0.log for the system *I* have been reporting on in
this bug report.
It shows the reason the system rejected the 1024x768 screen mode - "(II)
VESA(0): Not using built-in mode "1024x768" (width too large for virtual
size)"
This is the same reason shown in the log for my system
I just submitted another bug (# 255561) regarding a similar problem with
the same Samsung monitor on another system (Dell PowerEdge 400SC), where
Ubuntu fails to set up xorg.conf properly, but Knoppix does.
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bu
Also I was able to run successfully at 1024x768 using a Gentoo live CD,
version 1.6.14. I have attached the xorg.conf file from that.
** Attachment added: "xorg.conf from Gentoo live CD"
http://launchpadlibrarian.net/16542895/xorg.conf.gentoo-2006
--
[hardy beta] install failure (regression)
** Attachment added: "xorg.conf running feisty - 800x600"
http://launchpadlibrarian.net/16540454/xorg.conf.feisty
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member
** Attachment added: "xorg.conf running Mandriva live CD"
http://launchpadlibrarian.net/16540447/xorg.conf.mandriva
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a membe
** Attachment added: "xorg.conf running Knoppix - works at 1024x768"
http://launchpadlibrarian.net/16540440/xorg.conf.knoppix
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you a
I am having a similar problem with a gBox system with a S3 ProSavageDDR
display chip and VIA chipset on the motherboard.
I have Ubuntu 8.04.1 installed.
Here's some lspci info:
# lscpi
01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266]
# lspci -n
01:00.0 0300: 5333:8d04
What happens in gutsy's install process is that during xserver-xorg
postinst, MONITOR_IDENTIFIER is set to "Generic Monitor", for which
(somewhat reasonable) hsync and vrefresh values are then obtained from
the monitors database.
--
[hardy beta] install failure (regression) with ProSavageDDR grap
Maybe in the case that no useful hsync and vrefresh info can be obtained
from the monitor (in my case, a Highscreen MS 2195P), the installation
system should ask the user to make a selection from a list?
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.
The driver seems to be buggy. The monitor does not provide any DDC
information, and then the driver uses these values by default:
(II) SAVAGE(0): Configured Monitor: Using hsync value of 0.00 kHz
(II) SAVAGE(0): Configured Monitor: Using vrefresh value of 0.00 Hz
which, obviously, is going to fai
Sounds like an X problem rather than an installer problem, unless I'm
misunderstanding the report.
** Changed in: xorg (Ubuntu)
Sourcepackagename: ubiquity => xorg
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received
** Attachment added: "dmesg from the hardy beta install made with "safe
graphics mode""
http://launchpadlibrarian.net/13414635/dmesg
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification becau
** Attachment added: "Xorg.0.log from the install made with "safe grphics mode""
http://launchpadlibrarian.net/13414620/Xorg.0.log
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because
** Attachment added: "dmesg from gutsy"
http://launchpadlibrarian.net/13414612/dmesg
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Attachment added: "'lspci -vvnn' output from gutsy"
http://launchpadlibrarian.net/13414598/lspci
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member of Ubuntu
Bugs
Xorg.0.log from gutsy
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/13414584/Xorg.0.log
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member of Ubunt
** Attachment added: "dmesg from hardy beta ("Normal" install mode) when I
arrived in console text mode"
http://launchpadlibrarian.net/13414566/dmesg
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug n
** Attachment added: "'lspci -vvnn' output from hardy bety"
http://launchpadlibrarian.net/13414555/lspci
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received this bug notification because you are a member of Ubuntu
** Attachment added: "Xorg.0.log from hardy beta ("Normal" install mode) when I
arrived in console text mode"
http://launchpadlibrarian.net/13414136/Xorg.0.log
--
[hardy beta] install failure (regression) with ProSavageDDR graphics chipset
https://bugs.launchpad.net/bugs/217004
You received
28 matches
Mail list logo
