This bug was fixed in the package xserver-xorg-video-savage -
1:2.3.0-1ubuntu1
---
xserver-xorg-video-savage (1:2.3.0-1ubuntu1) karmic; urgency=low
[ Tormod Volden ]
* Merge with Debian, remaining changes:
- 10_bustype_pci_by_default.diff (LP: #33617, #37218)
-- Timo
I filed bug #429700 for a Karmic update.
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
When can we expect it to be fixed in the Karmic development series?
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
The bug has re-appeared on Karmic.
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
The package got synced with Debian and we lost
debian/patches/10_bustype_pci_by_default.diff.
** Changed in: xserver-xorg-video-savage (Ubuntu)
Status: Fix Released = Confirmed
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You
I already discussed this patch on #xorg-devel (although Alex did not
respond). The responses ranged from who are using savage cards
nowadays to fix AGP yourself. I am not sure upstream would like to
disable a feature they have invested in just for the sake of stability
and usability. I will post
I can add, I will make a quirk system if I get proof that anyone having
DRI enabled and working can resume correctly with AGP (I haven't heard
of any) and if they can measure a substantial performance drop going
from AGP to PCI :)
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
** Attachment added: debdiff for Jaunty
http://launchpadlibrarian.net/24055350/xserver-xorg-video-savage_2.2.1-4ubuntu1.debdiff
** Changed in: xserver-xorg-video-savage (Ubuntu)
Assignee: (unassigned) = Bryce Harrington (bryceharrington)
--
[agp] X.org does not initialize screen on
Tormod, thanks, uploaded.
Please make sure to forward this patch upstream so they're aware of it.
I suspect this works around the problem for many, but may cause
regressions for anyone for whom AGP does happen to work properly.
Perhaps what would be a better solution would be to implement a
This bug was fixed in the package xserver-xorg-video-savage -
1:2.2.1-4ubuntu1
---
xserver-xorg-video-savage (1:2.2.1-4ubuntu1) jaunty; urgency=low
* Add debian/patches/10_bustype_pci_by_default.diff:
Use BusType PCI by default (LP: #33617, #37218)
-- Tormod Volden
I forgot explicitly to ask you all to test this package. Unless we get
some testing and feedback, nothing will be done.
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug notification because you are a member of Ubuntu
Bugs,
I'll test this patch when I upgrade to jaunty (once the beta is out) but
I certainly can't put alpha software on a machine I use so much. Thanks
for putting the time in.
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug
I would appreciate if you test with a live CD. Boot with the text
kernel parameter so X will not be automatically started. Then log in and
update the driver (having it downloaded to an accessible drive*, or 1)
configure xorg.conf to use the vesa driver 2) start X using startx 3)
download the
Ok, I had given up on this a week ago because nothing would get X not to
lockup but then I discovered bug #319210 and realized it was something
else causing the lockup.
Anyway, after I got the network up I updated the system and I tested
with the savage snapshot package above, a default xorg.conf
I have uploaded a Jaunty package with a BusType PCI by default patch
to my PPA https://launchpad.net/~tormodvolden/+archive/ppa
** Attachment added: Makes BusType PCI default instead of AGP
http://launchpadlibrarian.net/23612788/0001-default-to-BusType-PCI.patch
--
[agp] X.org does not
Please add the PCI bus as default patch to the jaunty driver soon so
we can test it.
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
I tried to use Mark's workaround on Jaunty Alpha 4 but it did not work.
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
I just confirmed that this bug is present the default Intrepid. Here's a
recipe to workaround it, as tested with a T22:
1. Install from the Alternate install CD (which avoids graphics issues)
2. On first boot, press escape as you briefly pass through the GRUB
bootloader stage, and select
I second the motion to default to PCI and allow people to switch to AGP
if they want.
I just spent 3 evenings after work trying to get Ubuntu/Xubuntu
installed onto my old T-20. Once I found this bug it only took 30
minutes to get Xorg working.
These old thinkpads are great, I got a replacement
@Gabriel M:
@ Tormod: What do we have to do to test the patch, anyways? It seems an
earlier version was provided in .deb format, but I assume for this one we
have to get the src deb, patch, then hopefully a debian command can
auto-compile and package the whole thing? If you give simple
I have a T20 which is still in use and going strong. I came accross this
during a fresh install and have tried the patch out but there were 2
problems:
1. The VENDOR_ID/DEVICE_ID calls need to be compared against.. well..
the vendor device IDs not the subsystem IDs
2. drmAgpVendorId and
Reopen bug now a fix can be committed
** Changed in: xserver-xorg-video-savage (Ubuntu)
Status: Fix Committed = Confirmed
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug notification because you are a member of
Bryce proposed a patch in April, but since none of you have bothered to
test it, don't expect much to happen. When developers don't have access
to the hardware, they are depending on the affected users'
participation.
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
@Mark: If I was a Linux system programmer, I'd be already fixing the
bug. If I had money to spare, I would probably have already donated a
Thinkpad T22 to a developer or paid him to fix the bug (or bought my
friend a new computer with a preinstalled OS, if I didn't care about the
environment). But
actually, now that I thought about it a bit more, all of these laptops
have a 1400x1050 screen, which means that when using 24bit depth DRI is
not used, so that's why they are stable. If 16bit is used, 3D-progs tend
to hang the machine.. I haven't tried forcing PCI, but I take your word
on it and
On Thu, 13 Nov 2008 06:56:35 -
Gabriel M. [EMAIL PROTECTED] wrote:
I'm about to attempt an install of Intrepid on a Thinkpad T22 and a T23
for some friends, so I disagree with the this card is now too old to
support statement. What are you doing of Linux's reputation of running
on old
I have three laptops of this vintage - a T21 and two T23s. All run
Dapper, and are to be upgraded to 8.04 shortly. They all see daily use.
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug notification because you are a
I'm about to attempt an install of Intrepid on a Thinkpad T22 and a T23
for some friends, so I disagree with the this card is now too old to
support statement. What are you doing of Linux's reputation of running
on old computers better than Windows XP? Nothing indicates these
computers are dying,
non-LTS releases don't get point-releases.
Intrepid works just fine on my T23, and I don't remember seeing any
problems with the T21/T22's sitting idle on my desk. But I'll test
intrepid live.
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
** Tags added: valid-xorg-conf
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Unassigning myself, I have no further plans to put effort into this
driver (#98 points out the hw is long dead anyway).
Here's my final take at this patch. Last time only Tom Shaw tested my
patch and it didn't work, so I'm probably wasting my time. If it
happens that the patch works well and
[Declining distro task; unassigning self]
** Changed in: xserver-xorg-video-savage (Ubuntu Hardy)
Assignee: Bryce Harrington (bryceharrington) = (unassigned)
Status: In Progress = Invalid
** Changed in: xserver-xorg-video-savage (Ubuntu Hardy)
Status: Invalid = Won't Fix
**
Where is the consensus being questioned? AGP is often so broken on
savage cards (especially if you use hibernation and sleep) so forcing
all savage cards to PCI would be a good thing IMHO. Even better, it
should default to PCI and let people experiment with AGP if they want
and know how.
I have
Ok, I agree with you. This card is now too old to support. Maybe the PCI
enforcement should be implemented then. However, like Tormod said, there
should be an option to enable AGP and let some people test it.
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
Tormod Volden wrote:
Where is the consensus being questioned? AGP is often so broken on
savage cards (especially if you use hibernation and sleep) so forcing
all savage cards to PCI would be a good thing IMHO. Even better, it
should default to PCI and let people experiment with AGP if they
I'm not looking to get in deep with this driver; it sounded like
incorporating the PCI enforcement would be quick and easy to do. Since
it seems some are not in consensus with doing that, I'll cease my
efforts. If someone else comes up with a better patch, I'd be happy to
review/upload though.
** Changed in: xserver-xorg-video-savage (Ubuntu Hardy)
Status: Fix Committed = In Progress
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Bryce, I believe you can read out the bridge ID like this (from
SAVAGEDRIAgpInit() in src/savage_dri.c)
vendor = drmAgpVendorId( psav-drmFD );
device = drmAgpDeviceId( psav-drmFD );
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You
Hmmm, you are still trying to force the driver to use PCI if it is in
combination with the T22 Intel AGP bridge? I thought someone could try
to fix the source of the problem and try to get back AGP. Forcing the
driver to be with PCI, that would be an ugly patch. Is there someone
here who is trying
Hmm, so it's failing in between these two lines. Ok, I'll investigate
it more after the weekend.
(--) SAVAGE(0): AGP card detected
(**) SAVAGE(0): BusType set to PCI
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug
** Description changed:
On the IBM T20 laptop using the Savage drivers, when gdm starts X, the
screen stays black with a _. The sound is initialized (I can hear the
startup sound) and I can login through SSH. The screen gets initalized
every 3 to 4 times of startup but I can't decern a
Looks like what this needs is a patch to set psav-IsPCI = TRUE when
using this particular graphics card / AGP bridge combo:
* S3 Inc. 86C270-294 Savage/IX-MV (rev 13)
* chip 5333,8c12 card 1014,017f
Well, here's a first cut at a patch. I don't know how to check the
bridge ID for savage, so I've left that out for now.
Can someone experiencing this issue test this patch after removing the
BusType option in xorg.conf to check that this fix actually does fix it,
without having to specify that
Just tried your patch without the BusType line on my T20, X wouldn't
start but reported no errors either but was lacking the PCI bus line
loading and all other things that come along when that loads. Network
isn't coming up on it now or i'd post some logs but nothing that
relevant except the
@Tom: Weird, and unexpected that it'd fail without reporting an error.
Can you try again, and run X by first shutting off gdm (/etc/init.d/gdm
stop), and then launch X via `startx startx.log 21`. Then post both
the startx.log and /var/log/Xorg.0.log from right after it failed?
I'm guessing the
Ok, it does this, I'm using the xorg.conf listed above in one of my
comments. The system seems to continue on but it is frozen so I can't do
anything except power off. From the syslog.
Mar 21 20:23:58 tom-thinkpad kdm[4767]: X server terminated: [1, 0, 127]
Mar 21 20:23:58 tom-thinkpad kdm[4767]:
Log when it's working.
** Attachment added: Xorg.t20.20089321.working.log
http://launchpadlibrarian.net/12804057/Xorg.t20.20089321.working.log
--
[agp] X.org does not initialize screen on IBM T20, T21, T22
https://bugs.launchpad.net/bugs/33617
You received this bug notification because you
47 matches
Mail list logo
