I suggest that this become a different bug -- I thought I had fixed this
already :/
I would like to know more about your system. Do you know if you are
suing a framebuffer console? What is your BIOS?
Can you provide the versions of your related packages:
dpkg -l xserver-xorg-video-geode xs
** Attachment added: "amd-wide-mode.patches"
http://launchpadlibrarian.net/12327650/amd-wide-mode.patches
--
xserver-xorg-video-amd: wide resolutions don't work
https://bugs.launchpad.net/bugs/197069
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Public bug reported:
Binary package hint: xserver-xorg-video-amd
GeodeLX with the video-amd driver does not support native resolutions of
wide monitors (1920x1200, 1680x1050, 1440x900, etc).
I have tracked it down to code in the LXValidMode() code that checks
each mode against the Cimarron table
I figured out the issues in the original patch. Fix outlined on the
geode mailing list:
http://lists.x.org/archives/xorg-driver-geode/2008-March/000257.html
Here is my test .deb for hardy:
http://www.jukie.net/~bart/tmp/xserver-xorg-video-amd-
dbg_2.7.7.6-1bartman2_i386.deb
With this driver ru
the packages for Hardy and Gutsy are in my PPA
https://launchpad.net/%7Ebart-jukie/+archive
--
xserver-xorg-video-amd: wide resolutions don't work
https://bugs.launchpad.net/bugs/197069
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
That's correct. This patch is very new and has not made its way into
any repository or package.
Updating your xserver package will revert your system to the not working
code-base.
--
xf86-video-amd: switching to a vcons fails
https://bugs.launchpad.net/bugs/180742
You received this bug notifica
That might have been confusing.
I meant to say that updating your xserver via apt to a Gutsy release of
the package would overwrite the patched package you built and undo the
fix. Although, if you see a new update from Gutsy, you could apply this
patch to the new sources and build again.
--
xf8
* Martin-?ric Racine <[EMAIL PROTECTED]> [080206 03:25]:
> The build log for my PPA shows that the server fails to build on the
> AMD64 platform when the CPUID patch is applied:
>
> https://launchpad.net/~q-funk/+archive/+builds?build_text=&build_state=failed
>
> It successfully built on LPIA and
Another repost of the CPUID patch for systems that don't need it :)
** Attachment added: "X86EMU: handle CPUID instruction"
http://launchpadlibrarian.net/11814633/0001-X86EMU-handle-CPUID-instruction.patch
--
xf86-video-amd: switching to a vcons fails
https://bugs.launchpad.net/bugs/180742
Y
I am going to port the patches to Hardy's 1.4 debs. I have not started
to build a development environment yet.
Can someone in the know, tell me if it's easy to build 1.4 debs under
Gutsy, or if I have to setup Hardy.
--
amd driver fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
Yo
I started looking into this. When we exit we attempt to execute INT
0x10 to restore the VGA mode.
On GSW BIOS I get this in the logs... c000:0282: A2 ILLEGAL EXTENDED X86
OPCODE!
I am going to watch the emulator a bit more closely and try to see where
it goes wrong.
--
xf86-video-amd: switchin
To follow up on yesterday's discovery of an x86emu ILLEGAL OPCODE
message..
The opcode was 0F A2, or CPUID; it was not implemented in the emulator.
I have created a simple patch that emulates this instruction by passing
it the exact values of the instruction ran on the real hardware. Patch
is att
://wiki.hungrycats.org/mediawiki/index.php/Bartman%27s_Question#and_the_result_is
A LUG-buddy offered to resurrect his old 486 to get me the right values.
http://wiki.hungrycats.org/mediawiki/index.php/Bartman%27s_Question#and_the_result_is
--
xf86-video-amd: switching to a vcons fails
https://bugs.launchpad.net
On Gutsy, the fewest number of steps would be to...
apt-get source xserver-xorg-core
sudo apt-get build-dep xserver-xorg-core fakeroot devscripts
cd xorg-server-1.3.0.0*/
./debian/rules patch
patch -s -p1 < ...path/to/the/patch/...
debuild -b -nc
sudo debi
Take note of the patch step -- it should
This another take at the patch that obsoletes the one posted on
2008-02-02. It is still against Gutsy sources (after all other patches
were applied), but because it is more complex it does not apply on a
clean 1.3.0.0 xorg tree. My instructions above should still work for
you.
** Attachment adde
Romeo,
if I am reading your message correctly... you missed the < in applying
the patch:
patch -s -p1 < file
...and not...
patch -s -p1 file
-Bart
--
xf86-video-amd: switching to a vcons fails
https://bugs.launchpad.net/bugs/180742
You received this bug notification because you are a member
* Romeo <[EMAIL PROTECTED]> [080203 14:15]:
> if i need to obtain original source code (without patches applied) what
> should i do? simply tell "apt-get source xserver-xorg-core" again?
Yes, you could do that. You can also unapply the patch I have provided:
patch -s -p1 -R < ...thepatch...
The
More about the Geode LX crash with Generla Software BIOS...
There seems to be an inconsistency between what the x86emu gets from the
PCI handling code and by accessing hardware directly. x86emu relies on
a set of functions to emulate PCI access. When things goes wrong, the
emulator is asked to e
With reference to:
>> I meant confirmation of whether these two x86emu patches fix the bug
or not.
My two patches do not solve the "DDC not working" bug. They fix two
bugs in x86emu that cause the freeze.
I plan on working on the DDC/EDID issues later this week.
--
amd driver fails to autocon
Martin-Eric sent me a new Linutop (GeodeLX, General BIOS) to test on.
Booting vanilla Hardy on it froze the system (GeodeLX); shortly after DDC
probing.
I then loaded up Bryce's deb's from 2008-01-23; it fixed the bug.
--
xf86-video-amd: fails to autoconfigure
https://bugs.launchpad.net/bugs/140
The discussion started here continued on the xorg mailing list. Here is
the thread...
http://lists.x.org/archives/xorg-driver-geode/2007-December/02.html
I have been debugging the problem on and off and made some headway
recently...
http://lists.x.org/archives/xorg-driver-geode/2007-Decembe
Thanks. I had a feeling I could have fixed the problem by specifying the
values. Is there a way this could be fixed so people wouldn't have to edit
there xorg.conf. Having the drivers install the way they do now is great but
it's kind of moot if they can't select the proper resolutions.
Thanks,
Ba
Did you need any new info? Was a change made that you'd like me to test?
On 4/17/07 1:16 AM, "Timo Aaltonen" <[EMAIL PROTECTED]> wrote:
> ** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
> Sourcepackagename: xorg => linux-restricted-modules-2.6.20
--
ATI driver sets rez to 1024x768, if
xorg.conf
** Attachment added: "xorg.conf"
http://librarian.launchpad.net/7180057/xorg.conf
--
ATI driver sets rez to 1024x768, if I change xorg to 1280 it forces 95hz refresh
https://bugs.launchpad.net/bugs/103035
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Attachment added: "Xorg.0.log"
http://librarian.launchpad.net/7180059/Xorg.0.log
--
ATI driver sets rez to 1024x768, if I change xorg to 1280 it forces 95hz refresh
https://bugs.launchpad.net/bugs/103035
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
After posting the log I realized it's not going to have the fault
logged. Here is an updated xorg.conf and xorg.log. I added "1280x1024"
to the default color depth of 24 and rebooted. The display went blank
trying to load X and showed it was trying to run at 1280x1024 93.2Hz(or
close). I went to th
Public bug reported:
I know this looks a lot like the other reports but I noticed another
problem. I have integrated ATI 200m video. After installing the
restricted driver I can only select 60Hz and up to 1024x768 rez.
If I manually edit the xorg file to add "1280x1024" then restart it
tries to r
Sure, will do asap
On 4/4/07 4:59 PM, "Brian Murray" <[EMAIL PROTECTED]> wrote:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. Could you please add your '/etc/X11/xorg.conf' file and your
> '/var/log/Xorg.0.log' file as attachments to your bug report? Than
Just checked with Ubuntu 16.04 and Dell XPS 15 9530 - still same
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415880
Title:
14e4:4365 bcmwl-kernel source: fix for null pointer crash
To
I have some workaround (distable/enable wl module when suspend)
- check this
http://askubuntu.com/questions/620494/ubuntu-15-04-suspend-doesnt-run-pm-suspend
(needed for 15.04 or higher)
- in /etc/pm/sleep.d create file with some name (for example 01_wifi_wl) with
content:
Can anyone confirm that
https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.248+bdcom-0ubuntu0.0.3
fixes problem?
I just tried this package and I have still same problem - laptop don't want to
back to work after suspend (Dell XPS 15 9530)
--
You received this bug notification because you are a
31 matches
Mail list logo
