On Fri, Apr 10, 2015 at 05:39:50PM -0400, Milan Kupcevic wrote:
> The module landed in sid D-I. It gets loaded automatically as it is not
> blacklisted in D-I. I've been able to boot and run the installer on an
> XServe G4 DP, a G4 Mac Mini, and a Pegasos II. All three machines have
> radeon cards
On 12/08/2015 06:30 PM, John Paul Adrian Glaubitz wrote:
> On Fri, Apr 10, 2015 at 05:39:50PM -0400, Milan Kupcevic wrote:
> > The module landed in sid D-I. It gets loaded automatically as it is not
>> blacklisted in D-I. I've been able to boot and run the installer on an
>> XServe G4 DP, a G4 Mac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/09/2015 03:39 AM, Milan Kupcevic wrote:
> The module in question gets loaded and is used in D-I only. Pay
> attention to the case you are pointing at: the graphics does not
> work on boot/reboot into an installed system. At this point this
> m
Package: src:linux
Version: 3.16.7-ckt7-1
Severity: important
Tags: d-i jessie
The last line seen on the screen after installer CD boots is
'returning from prom_init'. This is a regression introduced in
d-i rc2 which persist in daily builds.
Connecting serial terminal and booting with 'consol
Hi Milan!
I just stumbled across this bug report and was actually wondering why
your Pegasos-II board won't work properly with the radeon KMS driver.
As far as I know, the Radeon 9250 found on the Pegasos-II board is fully
supported by the radeon KMS driver, so I'd expect it to work out-of
the-bo
Control: reopen -1
Hi!
On 04/08/2015 09:51 PM, Milan Kupcevic wrote:
> In Wheezy and in Jessie RC1 radenfb was compiled in the kernel itself
> while debian installer worked fine on this machine.
Well, yes. As you could see from the bug report you linked above,
compiling radeonfb into the kernel
On 04/08/2015 02:03 PM, John Paul Adrian Glaubitz wrote:
> Hi Milan!
>
> I just stumbled across this bug report and was actually wondering why
> your Pegasos-II board won't work properly with the radeon KMS driver.
>
> As far as I know, the Radeon 9250 found on the Pegasos-II board is fully
> sup
On 04/09/2015 08:21 AM, Ben Hutchings wrote:
[...]
>
> It isn't reverted. All I've done is to add radeonfb.ko to the drivers
> that are included *in the installer*.
>
> Neither radeon.ko nor xserver-xorg-video-radeon are included in the
> installer, so how could they possibly be used? If you t
On Fri, 2015-04-10 at 17:39 -0400, Milan Kupcevic wrote:
> On 04/09/2015 08:21 AM, Ben Hutchings wrote:
> [...]
>
> >
> > It isn't reverted. All I've done is to add radeonfb.ko to the drivers
> > that are included *in the installer*.
> >
> > Neither radeon.ko nor xserver-xorg-video-radeon are i
On 04/09/2015 12:29 PM, Ben Hutchings wrote:
>
> Let's try to keep this civil, please.
>
> Ben.
>
Sorry, my reaction to personal attacks was too harsh. Will stick to
technical issues and ignore any personal slurs from now on.
Milan
signature.asc
Description: OpenPGP digital signature
On 04/09/2015 02:21 PM, Ben Hutchings wrote:
> It isn't reverted. All I've done is to add radeonfb.ko to the
> drivers that are included *in the installer*.
Yes, I understand that. I still disagree with the change.
> Neither radeon.ko nor xserver-xorg-video-radeon are included in
> the installer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/09/2015 12:38 AM, Milan Kupcevic wrote:
>> Well, yes. As you could see from the bug report you linked above,
>> compiling radeonfb into the kernel broke X on basically all
>> Radeon cards.
>>
>
> It seems that radeonfb was compiled into the
On 04/08/2015 04:02 PM, John Paul Adrian Glaubitz wrote:
> Control: reopen -1
>
> On 04/08/2015 09:51 PM, Milan Kupcevic wrote:
>> In Wheezy and in Jessie RC1 radenfb was compiled in the kernel
>> itself while debian installer worked fine on this machine.
>
> Well, yes. As you could see from the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/09/2015 10:08 AM, John Paul Adrian Glaubitz wrote:
> The only reason it was compiled into the powerpc kernel without
> anyone complaining is the fact that the xf86-video-ati (= Radeon
> X.Org) driver in Wheezy was still old enough [1] to suppor
On 04/09/2015 04:08 AM, John Paul Adrian Glaubitz wrote:
> On 04/09/2015 12:38 AM, Milan Kupcevic wrote:
>>> Well, yes. As you could see from the bug report you linked above,
>>> compiling radeonfb into the kernel broke X on basically all
>>> Radeon cards.
>>>
>
>> It seems that radeonfb was comp
On Thu, 2015-04-09 at 08:24 -0400, Milan Kupcevic wrote:
[...]
> Your understanding of the consequences of your changes is trully stellar.
[...]
> Well, I've asked, no one complained until you showed up. The resulting
> discussion spreads very interesting scent.
[...]
Let's try to keep this civil,
On Thu, 2015-04-09 at 10:08 +0200, John Paul Adrian Glaubitz wrote:
> On 04/09/2015 12:38 AM, Milan Kupcevic wrote:
> >> Well, yes. As you could see from the bug report you linked above,
> >> compiling radeonfb into the kernel broke X on basically all
> >> Radeon cards.
> >>
> >
> > It seems tha
On 04/10/2015 06:05 PM, Ben Hutchings wrote:
> On Fri, 2015-04-10 at 17:39 -0400, Milan Kupcevic wrote:
>> On 04/09/2015 08:21 AM, Ben Hutchings wrote:
>> [...]
>>
>>>
>>> It isn't reverted. All I've done is to add radeonfb.ko to the drivers
>>> that are included *in the installer*.
>>>
>>> Neithe
18 matches
Mail list logo
