On Monday, May 8, 2023, Ben Westover wrote:
> Is this something I can fix, or does modern Xorg just need more VRAM?
try 640x480 and/or 16bpp.
l.
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
Hi!
On Sun, 2023-05-07 at 20:20 -0400, Ben Westover wrote:
> Hello,
>
> On 5/7/23 3:14 AM, Paul Wise wrote:
> > If you add a return statement like this, does that fix the crash?
> >
> > /* non-x86 platform */
> > if (!info->VBIOS) {
> > otypes[0] = OUTPUT_VGA;
> > ret
On Sun, 2023-05-07 at 20:20 -0400, Ben Westover wrote:
...
> (EE) AddScreen/ScreenInit failed for driver 0
>
> Is this something I can fix, or does modern Xorg just need more VRAM?
I don't know enough about the Xorg codebase to answer this.
It would be a good idea to ask o
(EE) AddScreen/ScreenInit failed for driver 0
Is this something I can fix, or does modern Xorg just need more VRAM?
Thanks,
--
Ben Westover
OpenPGP_signature
Description: OpenPGP digital signature
On Sat, 2023-05-06 at 16:56 -0400, Ben Westover wrote:
> (gdb) print info
> $1 = (R128InfoPtr) 0x776ed0
> (gdb) print info.VBIOS
> $2 = (uint8_t *) 0x0
If you add a return statement like this, does that fix the crash?
/* non-x86 platform */
if (!info->VBIOS) {
otypes[0] = OUTPUT_
On 4/18/23 10:44 PM, Paul Wise wrote:
These are the macro definitions.
#define R128_BIOS8(v) ((info->VBIOS[(v)]))
#define R128_BIOS16(v) ((info->VBIOS[(v)]) | \
(info->VBIOS[(v) + 1] << 8))
#define R128_BIOS32(v) ((info->VBIOS[(v)]) | \
On Tue, 2023-04-18 at 09:42 +0100, Luke Kenneth Casson Leighton wrote:
> On Tuesday, April 18, 2023, Ben Westover wrote:
> > /* non-x86 platform */
> > if (!info->VBIOS) {
> > otypes[0] = OUTPUT_VGA;
> > }
> >
> > bios_header = R128_BIOS16(0x48);
>
> al
On Tuesday, April 18, 2023, Ben Westover wrote:
> Hello,
>
> On 4/16/23 10:18 PM, Paul Wise wrote:
>>
>> There is also the case where you launch Xorg via gdb and then run it.
>>
>> $ gdb `which Xorg`
>> (gdb) run
>> (gdb) bt full
>
>
Hello,
On 4/16/23 10:18 PM, Paul Wise wrote:
There is also the case where you launch Xorg via gdb and then run it.
$ gdb `which Xorg`
(gdb) run
(gdb) bt full
Perfect! I was able to get a full backtrace, which is attached. Here's
the part that I think is important:
Pr
On Sun, 2023-04-16 at 15:08 -0400, Ben Westover wrote:
> I'm probably doing something wrong (never used gdb before), but Xorg
> closes almost instantly after I run it so there's not enough time to
> launch gdb before it's already segfaulted. It sounds like these t
Hi,
On 4/15/23 10:56 PM, Paul Wise wrote:
I think you will need to do some debugging, there are some tips here:
https://x.org/wiki/Development/Documentation/ServerDebugging/
I'm probably doing something wrong (never used gdb before), but Xorg
closes almost instantly after I run
On Sat, 2023-04-15 at 15:46 -0400, Ben Westover wrote:
> My system is up to date as of April 15, 2023; I'm running kernel
> 6.1.0-7-powerpc with Mesa 22.3.6. Does anyone how to fix this problem?
I think you will need to do some debugging, there are some tips here:
https://x.org/wiki/Development
Hello,
I have an iMac G3 with a Rage 128 Pro and 1 GB of RAM. I tried to
install and run Xfce4, but Xorg segfaults when I try to start it.
The full Xorg log is attached, but here is the backtrace at the end:
(EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x240) [0xac4a60]
(EE) 1: linux-vdso32.so
On 10/18/2021 07:50 PM, Alex McKeever wrote:
> Essentially, my screen can be found (I have an iMac G3 in which I’ve ran Sid
> on)… however it can’t find any usable configurations, and manually generating
> an XOrg configuration (editing it to give certain options) doesn’t help. Is
Hello!
On 10/18/21 19:39, Alex McKeever wrote:
> Essentially, my screen can be found (I have an iMac G3 in which I’ve ran Sid
> on)…
> however it can’t find any usable configurations, and manually generating an
> XOrg
> configuration (editing it to give certain options) doesn’t h
Essentially, my screen can be found (I have an iMac G3 in which I’ve ran Sid
on)… however it can’t find any usable configurations, and manually generating
an XOrg configuration (editing it to give certain options) doesn’t help. Is
this an XOrg, driver, or kernel issue?
I’d like to know as this
On Tue, 21 Apr 2020 at 14:22, John Paul Adrian Glaubitz
wrote:
>
> On 4/21/20 3:09 PM, Julien Cristau wrote:
> >> After some xorg driver packages were removed from the archive in #955603
> >> [1]
> >> that we still need for Debian Ports, I was wondering whethe
Hi!
Ed Robbins wrote:
This sounds like a good idea. I have a number of machines affected by
this issue (both G4 and x86). Is it possible to bring these packages
back into debian? They work well enough for many users.
I second that.. especially some of these are very useful on x86, some
also o
On Tue, 21 Apr 2020 at 12:23, John Paul Adrian Glaubitz
wrote:
>
> Hi!
>
> After some xorg driver packages were removed from the archive in #955603 [1]
> that we still need for Debian Ports, I was wondering whether it's okay when
> I take over maintainership and upload the
Hi,
John Paul Adrian Glaubitz wrote:
> Hi!
>
> After some xorg driver packages were removed from the archive in #955603 [1]
> that we still need for Debian Ports, I was wondering whether it's okay when
> I take over maintainership and upload the packages to unstable as w
On 4/21/20 3:09 PM, Julien Cristau wrote:
>> After some xorg driver packages were removed from the archive in #955603 [1]
>> that we still need for Debian Ports, I was wondering whether it's okay when
>> I take over maintainership and upload the packages to unstable as w
On 4/21/20 2:31 PM, Alex McKeever wrote:
> Looks like the r128 driver isn’t necessary on its own as it’s provided by
> this package digging a little deeper. I also have xserver-XOrg-legacy
> installed which isn’t promising. Would the standalone r128 driver even help
> in this scenar
Adrian,
I have the driver installed but I’m getting a segmentation fault.
xorg.0.log
Description: Binary data
Attached is my Xorg.0.log file
- Alex
On Tue, Apr 21, 2020 at 13:23:40 +0200, John Paul Adrian Glaubitz wrote:
> Hi!
>
> After some xorg driver packages were removed from the archive in #955603 [1]
> that we still need for Debian Ports, I was wondering whether it's okay when
> I take over maintainership and up
ng a little deeper. I also have xserver-XOrg-legacy installed
which isn’t promising. Would the standalone r128 driver even help in this
scenario?
Sent from AT&T Yahoo Mail for iPhone
Looks like the r128 driver isn’t necessary on its own as it’s provided by this
package digging a little deeper. I also have xserver-XOrg-legacy installed
which isn’t promising. Would the standalone r128 driver even help in this
scenario?
Sent from AT&T Yahoo Mail for iPhone
Hi!
After some xorg driver packages were removed from the archive in #955603 [1]
that we still need for Debian Ports, I was wondering whether it's okay when
I take over maintainership and upload the packages to unstable as we need
them.
I understand that the timing is a bit unfortunate,
(who works on VoidPPC) said r128 needs patched to even work….
I don’t even know what he did to get it working over there.
I suggest asking him what he did and then - if it's a patch that's necessary -
we can include it in the xorg package for the r128 driver.
The r128 driver package w
ng to?
>>
>> This might be relevant [1] although I haven't checked whether
>> the patch was ever merged upstream.
>
> It is:
>
>> https://cgit.freedesktop.org/xorg/driver/xf86-video-r128/commit/?id=562681414f38c6925da01b3fec0802f532cd9e53
>
>> Either
On 4/20/20 10:37 PM, Alex McKeever wrote:
> Here’s a link to the patch for r128’s Xorg driver on Github:
> https://github.com/void-linux/void-packages/blob/master/srcpkgs/xf86-video-r128/patches/fix-non-x86.patch
>
> <https://github.com/void-linux/void-packages/blob/master/src
On 4/20/20 10:44 PM, John Paul Adrian Glaubitz wrote:
> On 4/20/20 10:39 PM, Ed Robbins wrote:
>> What rage 128 patches are you alluding to?
>
> This might be relevant [1] although I haven't checked whether
> the patch was ever merged upstream.
It is:
> https://cgit.f
On 4/20/20 10:39 PM, Ed Robbins wrote:
> What rage 128 patches are you alluding to?
This might be relevant [1] although I haven't checked whether
the patch was ever merged upstream.
Either way, the Rage-128 driver package is gone, so we need
to use a something like xserver-xorg-video-mod
Hello!
> xserver-xorg-video-ast
> xserver-xorg-video-geode
> xserver-xorg-video-mach64
> xserver-xorg-video-neomagic
> xserver-xorg-video-r128
> xserver-xorg-video-savage
> xserver-xorg-video-siliconmotion
> xserver-xorg-video-sisusb
> xserver-xorg-video-tdfx
> x
now what he did to get it working over there.
"Tried everything" is not very informative. Reports on this list are
that you need to install xserver-xorg-legacy (and
x-server-xorg-video-r128) for rage 128 [1]. Have you tried that?
What xorg.conf have you tried?
What rage 128 patches are
PC) said r128 needs patched to even
>> work….
>> I don’t even know what he did to get it working over there.
>
> I suggest asking him what he did and then - if it's a patch that's necessary -
> we can include it in the xorg package for the r128 driver.
The r128 dri
t he did to get it working over there.
I suggest asking him what he did and then - if it's a patch that's necessary -
we can include it in the xorg package for the r128 driver.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.or
Tried everything to get X working (needed working for LXDE), including a new
xorg.conf with modelines. NO SUCCESS AT ALL.
Another developer (who works on VoidPPC) said r128 needs patched to even work….
I don’t even know what he did to get it working over there.
On Wed, Dec 25, 2019 at 2:09 AM Bertrand Dekoninck
wrote:
>
> On 24/12/2019 22:39, John Paul Adrian Glaubitz wrote:
> > On 12/24/19 10:15 PM, bertrand.dekoni...@gmail.com wrote:
> >>> How did you do that.
> >> umount /dev/sda2
> >> fsck.hfs /dev/sda2
> >>
> >> And then I had got an error.
> > What
On 24/12/2019 22:39, John Paul Adrian Glaubitz wrote:
On 12/24/19 10:15 PM, bertrand.dekoni...@gmail.com wrote:
How did you do that.
umount /dev/sda2
fsck.hfs /dev/sda2
And then I had got an error.
What error did you get? FWIW, the hfsprogs package also needs to be updated
to a newer upstream
On 12/24/19 10:15 PM, bertrand.dekoni...@gmail.com wrote:
>> How did you do that.
> umount /dev/sda2
> fsck.hfs /dev/sda2
>
> And then I had got an error.
What error did you get? FWIW, the hfsprogs package also needs to be updated
to a newer upstream version - something which is on my TODO list
Envoyé de mon iPhone
> Le 24 déc. 2019 à 20:42, John Paul Adrian Glaubitz
> a écrit :
>
> Hi!
Hi! Tanks for your answer.
>
>> On 12/24/19 2:04 PM, Bertrand Dekoninck wrote:
>> I’ve installed firmware-linux-nonfree_0.43 from Jessie
>
> You can just add the following line to your /etc/apt/so
Hi!
On 12/24/19 2:04 PM, Bertrand Dekoninck wrote:
> I’ve installed firmware-linux-nonfree_0.43 from Jessie
You can just add the following line to your /etc/apt/sources.list:
deb [arch=all] http://ftp.de.debian.org/debian unstable contrib non-free
and then just install the firmware using apt. I
e failed, living me with an unusable console and I
>> couldn’t with to another VT.
>> From ssh on another machine,I’ve tracked the failing service (lightdm), run
>> Xorg -configure and tried to launch it with the created config file. I
>> finally could see error messages on my s
e end of the boot, the system left me
with a big black screen and a little « —« cursor at the top left of
the screen. display-manager.service failed, living me with an unusable
console and I couldn’t with to another VT.
From ssh on another machine,I’ve tracked the failing service
(lightdm), run
On 03/24/2017 06:13 PM, Riccardo Mottola wrote:
> yes, that works even when using the stock kernel and I can stop disabling the
> atyfb.
That's great to hear!
> Very good - we have a better solution than compiling different kernels!
> Perhaps it
> could be at least be mentioned or best pre-conf
Hi Cascardo,
Thadeu Lima de Souza Cascardo wrote:
Can you boot the default Debian kernel (the one with
CONFIG_IO_STRICT_DEVMEM=y) with the following boot parameter and see if
it works for you?
iomem=relaxed
If that works, you are open to some "security" issues, but no need to
build a new kerne
only? Especially since we know it has a
> larger legacy hardware base than others. Probably on 64bit nobody has such
> video cards, I imagine I am not the only one running Xorg legacy.
>
> Compiling a kernel is not really difficult but quite time consuming.
>
> I still think a bug
and a browser like firefox!
Can it be kept on on PPC 32bit only? Especially since we know it has a
larger legacy hardware base than others. Probably on 64bit nobody has
such video cards, I imagine I am not the only one running Xorg legacy.
Compiling a kernel is not really difficult but quite tim
On 03/24/2017 11:34 AM, John Paul Adrian Glaubitz wrote:
> That's actually a difficult question. Looking at what the option does,
> it's actually a security feature [1] and disabling it would take away
> security for a lot of users.
Sorry, forgot to provide the link:
> http://cateee.net/lkddb/web
the setting is incompatible with with
> legacy Xorg, which is the one I am using.
Yes, indeed. Thanks for verifying this. Glad to hear you figured out
how to get X.Org working on your machine again.
> Adrian, can you open the bug or should I, where ?
That's actually a difficult question.
13 kernel using this guide:
>
> https://www.debian.org/releases/jessie/i386/ch08s06.html.en
>
> I used the debian supplied config except the IO strict devmem setting.
> It took almost 2 days to build on the iBook using a SSD! :)
>
> X11 now works, so this is the proof.
> Fur
pt the IO strict devmem setting.
It took almost 2 days to build on the iBook using a SSD! :)
X11 now works, so this is the proof.
Furthermore the description says that the setting is incompatible with
with legacy Xorg, which is the one I am using.
Maybe with an updated ATI driver the usage
On 16/03/17 08:21 AM, Riccardo Mottola wrote:
>
> X11 doesn't start, but the error message changed and goes further.
> Before it essentially failed to detect my card, now I see in Xorg.log:
[...]
> [ 175.085] (EE) MACH64(0): Unable to map linear aperture. Invalid
> argument (22)
This could st
the framebuffer off.
> To test this I would need to run the new kernel without
> the kernel atyfb and see if then Xorg starts.
> I asked for advice on how to
I actually mentioned that in my first post:
video=atyfb:off
You should just be able to append this on the yaboot com
nel atyfb and see if then Xorg starts.
> I asked for advice on how to
I actually mentioned that in my first post:
video=atyfb:off
You should just be able to append this on the yaboot command line.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Deve
o
let the kernel atyfb driver or the Xorg mach64 driver access the GPU's
MMIO register aperture.
could we turn that option back (if proven that it is it)?
To test this I would need to run the new kernel without the kernel atyfb
and see if then Xorg starts.
I asked for advice on how to, if it
ing I/O memory ranges which are already
claimed by a kernel driver. I.e. you have to choose whether you want to
let the kernel atyfb driver or the Xorg mach64 driver access the GPU's
MMIO register aperture.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
On 03/15/2017 12:44 AM, Riccardo Mottola wrote:
> Interesting is that this is 4.8.0-1 while the header advertises 4.8.5!
Not really. 4.8.0 is the ABI version while 4.8.5 is the kernel version.
This means that modules built for a 4.8.3 kernel will also work for a
4.8.5 kernel without having to reco
Hi,
Michel Dänzer wrote:
Can you provide the two /boot/config-4.8* files? If you attach them
> directly, maybe compress them e.g. with gzip to avoid running into
> mailing list size limits.
Or maybe just attach the output of diff -u for the two files.
attached (well, I forgot unified, but it
Hi,
Michel Dänzer wrote:
Can you provide the two /boot/config-4.8* files? If you attach them
> directly, maybe compress them e.g. with gzip to avoid running into
> mailing list size limits.
Or maybe just attach the output of diff -u for the two files.
attached (well, I forgot unified, but it
On 09/03/17 10:34 AM, Michel Dänzer wrote:
> On 09/03/17 04:19 AM, Riccardo Mottola wrote:
>>
>> Did debian change something in the kernel between rc8 and -1 (patches,
>> config options) or did we uncover an upstream kernel bug?
>
> Can you provide the two /boot/config-4.8* files? If you attach th
On 09/03/17 04:19 AM, Riccardo Mottola wrote:
> On 03/07/17 13:11, Riccardo Mottola wrote:
>>
>> For the 4.8 series instead:
>>
>> 4.8.0-rc8-powerpc #1 Debian 4.8~rc8-1~exp1 (2016-09-26)
>> 4.8.0-1 Debian 4.8.5 -> broken
>>
>> Since I saw no other 4.7 series, I can see that the breakage happened
>>
Hi,
On 03/07/17 13:11, Riccardo Mottola wrote:
For the 4.8 series instead:
4.8.0-rc8-powerpc #1 Debian 4.8~rc8-1~exp1 (2016-09-26)
4.8.0-1 Debian 4.8.5 -> broken
Since I saw no other 4.7 series, I can see that the breakage happened
already in the 4.8 series:, somewhere between:
linux-image-
On 03/07/2017 01:11 PM, Riccardo Mottola wrote:
> How can I know when an update was available? Or, better which intermediate
> versions are or have been available between my two kernels versions?
You search for the "linux" source package on the snapshots page:
> http://snapshot.debian.org/packag
Hi,
John Paul Adrian Glaubitz wrote:
Then you need to provide as many datapoints as possible. Trying to
bisect the
kernel version which broke the driver is already the right idea.
I would start working with snapshot.debian.org to find the Debian kernel
version which broke the driver. Then we c
s, having a more detailed description
of the difference and seeing the full Xorg log files corresponding to
both cases would be interesting.
well - i Idsabled things to avoid some bugs I do not remember :)
Currently my working setup is:
Section "Device"
Identifier "
onf has options disabling all hardware acceleration of
>> xserver-xorg-video-mach64 anyway. In that case there's no benefit in
>> using that vs xserver-xorg-video-fbdev.
>
> Not all acceleration, but most of it - that is the best I could get
> about a year ago withotu having very st
On 06/03/17 10:08 PM, John Paul Adrian Glaubitz wrote:
> On Mon, Mar 06, 2017 at 02:00:03PM +0100, Wolfgang Pfeiffer wrote:
>> No. He wasn't rude. Not a bit.
>
> Yes, *I* perceived that as rude.
>
>> He simply was - as most of the time here
>> - very specific, terse and up to the relevant technic
On Mon, Mar 06, 2017 at 02:00:03PM +0100, Wolfgang Pfeiffer wrote:
> No. He wasn't rude. Not a bit.
Yes, *I* perceived that as rude.
> He simply was - as most of the time here
> - very specific, terse and up to the relevant technical points.
He was talking to me as if I was an idiot. It is alrig
, but in order to use atyfb you have to
> > > use
> > > the fbdev xorg driver. That's my main point.
> >
> > If you mean for Xorg to use atyfb, that's technically correct, but
> > I'm
> > not sure how it's relevant.
>
> It's re
On 03/06/2017 11:04 AM, Riccardo Mottola wrote:
> Exactly, that "proof" means that the changes comes from the kernel or
> that the driver needs updating to work with the new kernel.
Or the kernel needs to be fixed in case it's a regression.
> Compiling kernels is a bit tight on this iBook. What r
Hi,
John Paul Adrian Glaubitz wrote:
Your machine is loading the framebuffer kernel driver which will only work
when you configure X.Org to use the "fbdev" driver. You can either set your
display driver to "fbdev" (see further below) or disable the framebuffer driver
on the kernel command line w
again and noticed that his
xorg.conf has options disabling all hardware acceleration of
xserver-xorg-video-mach64 anyway. In that case there's no benefit in
using that vs xserver-xorg-video-fbdev.
Not all acceleration, but most of it - that is the best I could get
about a year ago withotu ha
On 03/06/2017 09:06 AM, Michel Dänzer wrote:
>> On a sidenote: Please be more polite on this list. There is no need to
>> be that rude and condescending.
>
> What specifically did you find rude and condescending? It's an honest
> question. I know my writing tends to be too concise, but I'm honestl
On 06/03/17 04:59 PM, John Paul Adrian Glaubitz wrote:
>> On Mar 6, 2017, at 8:36 AM, Michel Dänzer wrote:
>>
>> Anyway, I looked at Riccardo's original post again and noticed that his
>> xorg.conf has options disabling all hardware acceleration of
>> xserve
> On Mar 6, 2017, at 8:36 AM, Michel Dänzer wrote:
>
>> On 06/03/17 04:20 PM, John Paul Adrian Glaubitz wrote:
>> Correct me if I'm wrong, but in order to use atyfb you have to use
>> the fbdev xorg driver. That's my main point.
>
> If you mean f
On 06/03/17 04:20 PM, John Paul Adrian Glaubitz wrote:
> Correct me if I'm wrong, but in order to use atyfb you have to use
> the fbdev xorg driver. That's my main point.
If you mean for Xorg to use atyfb, that's technically correct, but I'm
not sure how it's releva
Correct me if I'm wrong, but in order to use atyfb you have to use the fbdev
xorg driver. That's my main point.
Regarding "mach64" I just said it *may* not work properly when atyfb is loaded
because it needs to access the hardware itself, so I would try disabling aty
On 06/03/17 02:29 PM, John Paul Adrian Glaubitz wrote:
> Please re-read what I wrote. I never claimed it's a KMS driver.
Nor did I claim that you claimed that. Just what you wrote would make
sense if mach64 was a KMS driver, but it doesn't because it's not.
--
Earthling Michel Dänzer
Please re-read what I wrote. I never claimed it's a KMS driver.
> On Mar 6, 2017, at 4:05 AM, Michel Dänzer wrote:
>
>> On 04/03/17 04:49 AM, John Paul Adrian Glaubitz wrote:
>>> On 03/02/2017 07:44 PM, Riccardo Mottola wrote:
>>> [4.174055] atyfb :00:10.0: enabling device (0086 -> 0087)
On 04/03/17 04:49 AM, John Paul Adrian Glaubitz wrote:
> On 03/02/2017 07:44 PM, Riccardo Mottola wrote:
>> [4.174055] atyfb :00:10.0: enabling device (0086 -> 0087)
>> [4.174138] atyfb: using auxiliary register aperture
>> [4.174809] atyfb: 3D RAGE Mobility L (Mach64 LN, AGP 2x) [0
On 03/03/2017 08:49 PM, John Paul Adrian Glaubitz wrote:
> Then it should be possible to use the "mach64" driver *if* the kernel has
> support for the hardware. However, looking at the information available in
> the X.Org wiki [1], it seems the mach64 DRM module is currently not part of
> the Linux
Hi!
On 03/02/2017 07:44 PM, Riccardo Mottola wrote:
> [4.174055] atyfb :00:10.0: enabling device (0086 -> 0087)
> [4.174138] atyfb: using auxiliary register aperture
> [4.174809] atyfb: 3D RAGE Mobility L (Mach64 LN, AGP 2x) [0x4c4e rev 0x64]
> [4.174896] atyfb: 4M SDRAM (2:1)
Hi,
luigi burdo wrote:
another thing.
is the gpu in slot 0:16:0 ?
can you share an lspci ?
Yes it is (should be actually AGP). I already posted dmesg and lspci
with the "new" kernel.
This is with the working one. Looks identical to me:
:00:0b.0 Host bridge: Apple Inc. UniNorth AGP
0
another thing.
is the gpu in slot 0:16:0 ?
can you share an lspci ?
Luigi
Da: luigi burdo
Inviato: giovedì 2 marzo 2017 10.23
A: Riccardo Mottola; debian-powerpc@lists.debian.org
Oggetto: Re: Xorg fails on ATI after update (mmio aperture)
Hi Riccardo,
can
Hi,
luigi burdo wrote:
can it be something related the kernel?
I fear it is! I still had 4.7.0-1 instead of 4.9.0-2 and booted that.
All the rest being equals, X starts and works.
So either it is a kernel issue or still a bad X-kernel interaction.
Maybe John Paul gets wiser?
This lspci f
Hi John Paul,
John Paul Adrian Glaubitz wrote:
Can you please post the output of the dmesg and lspci commands?
if course, this is lspci:
:00:0b.0 Host bridge: Apple Inc. UniNorth AGP
:00:10.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Device 4c4e (rev 64)
0001:
On 03/02/2017 10:01 AM, Riccardo Mottola wrote:
> any clue about this? I saw some updates, but no X package and the issue still
> happens.
> It looks like my card can't be detected at all.
> Anybody else is running on Mac hardwware with ATI currently?
Can you please post the output of the dmesg a
Hi Riccardo,
can it be something related the kernel?
Ciao
Luigi
Da: Riccardo Mottola
Inviato: giovedì 2 marzo 2017 10.01
A: debian-powerpc@lists.debian.org
Oggetto: Re: Xorg fails on ATI after update (mmio aperture)
Hi all,
any clue about this? I saw some
rrent.
X doesn't start and in the xorg log I see the section below.
How can I solve this? What happened?
Riccardo
[ 392.682] (II) systemd-logind: took control of session
/org/freedesktop/login1/session/_31
[ 392.688] (--) PCI:*(0:0:16:0) 1002:4c4e:: rev 100, Mem @
0x910
Hi,
I did update debian on my iBook G3 with current.
X doesn't start and in the xorg log I see the section below.
How can I solve this? What happened?
Riccardo
[ 392.682] (II) systemd-logind: took control of session
/org/freedesktop/login1/session/_31
[ 392.688] (--) PCI:*(0:0
;> I really dislike certain choices debian and more generally most Linux
>> distros are taking...
>
> Let's clear up some FUD here:
>
> systemd is only required for running Xorg as a non-root user, which is
> desirable from a security POV.
>
> Running Xorg as
are taking...
Let's clear up some FUD here:
systemd is only required for running Xorg as a non-root user, which is
desirable from a security POV.
Running Xorg as non-root is only possible using a KMS kernel driver. For
configurations which don't / can't use a KMS kernel driver
I have a radeon 9550 card. 3D acceleration is broken but I have 2D
acceleration when I force the card to PCI mode. It could be more an issue
with the video card rather than systemd.
On Tue, Dec 22, 2015 at 2:03 PM, Riccardo Mottola <
riccardo.mott...@libero.it> wrote:
> Herminio Hernandez, Jr. ha
Herminio Hernandez, Jr. ha scritto:
what is your video card? I am running Debian Sid on my IBook G4 and
just did a dist-upgrade and am not seeing this issue.
ATI 3d Rage Mobility L (Mach64 card)
Riccardo
what is your video card? I am running Debian Sid on my IBook G4 and just
did a dist-upgrade and am not seeing this issue.
On Tue, Dec 22, 2015 at 1:49 PM, Riccardo Mottola <
riccardo.mott...@libero.it> wrote:
> Hi,
>
> Herminio Hernandez Jr. ha scritto:
>
>> Are you running Sid?
>>
>
> yes, I do.
Hi,
Herminio Hernandez Jr. ha scritto:
Are you running Sid?
yes, I do.
I just installed legacy server and now I have X again.
I really dislike certain choices debian and more generally most Linux
distros are taking...
Riccardo
Are you running Sid?
Sent from my iPhone
> On Dec 22, 2015, at 10:50 AM, Riccardo Mottola
> wrote:
>
> Hi,
>
> I have seen with regret that debian moved to some X needing systemd and a
> kernel driver.
> After my update, I don't get X starting anymore on my iBook with ATI video.
>
> Do we n
Hi,
I have seen with regret that debian moved to some X needing systemd and
a kernel driver.
After my update, I don't get X starting anymore on my iBook with ATI video.
Do we need to use the legacy server now?
Riccardo
In Stretch and Sid the latest package of xorg-core fixed the bug that hit
PPC machines that run the latest version of X in Ubuntu and Debian. I do
not know if this has made it down stream to Ubuntu. Checking now.
1 - 100 of 474 matches
Mail list logo
