This may not be a genuine bug, but maybe an understanding problem that
I have not been able to solve in other media.
I have two systems that are supposed to use KMS. One is working fine,
having an i915 graphics chip. On this system, i915.ko is copied into
the initramfs, and autoloaded if video=i915:modeset=1 is given on the
kernel command line.
The second one has an
01:00.0 VGA compatible controller: ATI Technologies Inc M56GL [Mobility FireGL V5200]
and is not working properly. I understand that radeon.ko needs to be
in the initrd for early loading to work, and this doesn't happen, and
I am at a loss to explain why this doesn happen.
For what it's worth, I didn't find any configuration that explicitly
causes the i915.ko to be included in the initramfs on the Intel
system, so I couldn't reproduce this configuration for radeon on the
other box.
Who is responsible to include the intel module into the initramfs on
the Intel box, and who should change what to do the same for radeon?
Kernel: Linux 2.6.33.1-zgws1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages initramfs-tools depends on:
ii cpio 2.11-1 GNU cpio -- a program to manage ar
ii findutils 4.4.2-1 utilities for finding files--find,
ii klibc-utils 1.5.17-4 small utilities built with klibc f
ii module-init-tools 3.12~pre2-2 tools for managing Linux kernel mo
ii udev 151-3 /dev/ and hotplug management daemo
Versions of packages initramfs-tools recommends:
ii busybox 1:1.15.3-1 Tiny utilities for small and embed
initramfs-tools suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100326113132.16051.90028.reportbug@swivel.zugsch lus.de">http://lists.debian.org/20100326113132.16051.90028.reportbug@swivel.zugsch lus.de
03-26-2010, 11:04 AM
Bastian Blank
Bug#575501: initramfs-tools: radeon.ko not included into initrd
On Fri, Mar 26, 2010 at 12:31:32PM +0100, Marc Haber wrote:
> I have two systems that are supposed to use KMS. One is working fine,
> having an i915 graphics chip. On this system, i915.ko is copied into
> the initramfs, and autoloaded if video=i915:modeset=1 is given on the
> kernel command line.
This is incorrect, loading the driver from the initramfs is not
supported. The module is loaded by udev later and KMS is enabled by the
xorg driver.
> The second one has an
> 01:00.0 VGA compatible controller: ATI Technologies Inc M56GL [Mobility FireGL V5200]
> and is not working properly. I understand that radeon.ko needs to be
> in the initrd for early loading to work, and this doesn't happen, and
> I am at a loss to explain why this doesn happen.
Loading drivers which needs firmware this early is currently broken.
> For what it's worth, I didn't find any configuration that explicitly
> causes the i915.ko to be included in the initramfs on the Intel
> system,
It is not included.
Bastian
--
Pain is a thing of the mind. The mind can be controlled.
-- Spock, "Operation -- Annihilate!" stardate 3287.2
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100326120440.GA11017@wavehammer.waldi.eu.org">ht tp://lists.debian.org/20100326120440.GA11017@wavehammer.waldi.eu.org
03-26-2010, 11:25 AM
Marc Haber
Bug#575501: initramfs-tools: radeon.ko not included into initrd
On Fri, Mar 26, 2010 at 01:04:40PM +0100, Bastian Blank wrote:
> On Fri, Mar 26, 2010 at 12:31:32PM +0100, Marc Haber wrote:
> > The second one has an
> > 01:00.0 VGA compatible controller: ATI Technologies Inc M56GL [Mobility FireGL V5200]
> > and is not working properly. I understand that radeon.ko needs to be
> > in the initrd for early loading to work, and this doesn't happen, and
> > I am at a loss to explain why this doesn happen.
>
> Loading drivers which needs firmware this early is currently broken.
I see. So there is no KMS for radeon at this time?
Is there a bug report about that for reference?
> > For what it's worth, I didn't find any configuration that explicitly
> > causes the i915.ko to be included in the initramfs on the Intel
> > system,
>
> It is not included.
< /boot/inird.img-2.6.33-zgws1 gunzip | cpio -i leads to a directory
tree which includes a file lib/modules/*/i915.ko. This I clearly
remember.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100326122538.GE6518@torres.zugschlus.de">http://lists.debian.org/20100326122538.GE6518@torres.zugschlus.de
03-26-2010, 12:20 PM
Bastian Blank
Bug#575501: initramfs-tools: radeon.ko not included into initrd
On Fri, Mar 26, 2010 at 01:25:38PM +0100, Marc Haber wrote:
> On Fri, Mar 26, 2010 at 01:04:40PM +0100, Bastian Blank wrote:
> > On Fri, Mar 26, 2010 at 12:31:32PM +0100, Marc Haber wrote:
> > > The second one has an
> > > 01:00.0 VGA compatible controller: ATI Technologies Inc M56GL [Mobility FireGL V5200]
> > > and is not working properly. I understand that radeon.ko needs to be
> > > in the initrd for early loading to work, and this doesn't happen, and
> > > I am at a loss to explain why this doesn happen.
> > Loading drivers which needs firmware this early is currently broken.
> I see. So there is no KMS for radeon at this time?
There is. The radeon module is loaded by udev later from the real
system.
> Is there a bug report about that for reference?
#575241
> > > For what it's worth, I didn't find any configuration that explicitly
> > > causes the i915.ko to be included in the initramfs on the Intel
> > > system,
> > It is not included.
> < /boot/inird.img-2.6.33-zgws1 gunzip | cpio -i leads to a directory
> tree which includes a file lib/modules/*/i915.ko. This I clearly
> remember.
--
Without facts, the decision cannot be made logically. You must rely on
your human intuition.
-- Spock, "Assignment: Earth", stardate unknown
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100326132006.GA11882@wavehammer.waldi.eu.org">ht tp://lists.debian.org/20100326132006.GA11882@wavehammer.waldi.eu.org
03-26-2010, 12:39 PM
Marc Haber
Bug#575501: initramfs-tools: radeon.ko not included into initrd
Hi,
On Fri, Mar 26, 2010 at 02:20:06PM +0100, Bastian Blank wrote:
> On Fri, Mar 26, 2010 at 01:25:38PM +0100, Marc Haber wrote:
> > On Fri, Mar 26, 2010 at 01:04:40PM +0100, Bastian Blank wrote:
> > > On Fri, Mar 26, 2010 at 12:31:32PM +0100, Marc Haber wrote:
> > > > The second one has an
> > > > 01:00.0 VGA compatible controller: ATI Technologies Inc M56GL [Mobility FireGL V5200]
> > > > and is not working properly. I understand that radeon.ko needs to be
> > > > in the initrd for early loading to work, and this doesn't happen, and
> > > > I am at a loss to explain why this doesn happen.
> > > Loading drivers which needs firmware this early is currently broken.
> > I see. So there is no KMS for radeon at this time?
>
> There is. The radeon module is loaded by udev later from the real
> system.
This doesn't seem to work here, as the modeset-parameter never gets
its way to the module, despite /etc/modprobe.d/radeon-kms.conf saying
"options radeon modeset=1".
Also, in my understanding, if I want a splashscreen to be shown, the
graphics driver moduled needs to be loaded early, right?
Are the directfb-based splash screens such as splahy compatible with
KMS in the first place?
Greetings
Marc
> > < /boot/inird.img-2.6.33-zgws1 gunzip | cpio -i leads to a directory
> > tree which includes a file lib/modules/*/i915.ko. This I clearly
> > remember.
>
> | $ gunzip -c initrd.img-2.6.32-4-686-bigmem | cpio -tv | grep -a i915
> | -rw-r--r-- 1 root root 23 Jan 7 23:51 etc/modprobe.d/i915-kms.conf
> | 12920 blocks
What are you trying to say? You need to be a little bit more verbose
to be actually helpful.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100326133947.GG6518@torres.zugschlus.de">http://lists.debian.org/20100326133947.GG6518@torres.zugschlus.de
03-26-2010, 01:07 PM
Bastian Blank
Bug#575501: initramfs-tools: radeon.ko not included into initrd
On Fri, Mar 26, 2010 at 02:39:47PM +0100, Marc Haber wrote:
> On Fri, Mar 26, 2010 at 02:20:06PM +0100, Bastian Blank wrote:
> > On Fri, Mar 26, 2010 at 01:25:38PM +0100, Marc Haber wrote:
> > > I see. So there is no KMS for radeon at this time?
> > There is. The radeon module is loaded by udev later from the real
> > system.
> This doesn't seem to work here,
You either have to set DRM_RADEON_KMS to enable auto-loading---this is
done partially in the Debian kernels to provide an upgrade path---or
load it somewhere early, via /etc/modules for example.
> as the modeset-parameter never gets
> its way to the module, despite /etc/modprobe.d/radeon-kms.conf saying
> "options radeon modeset=1".
I'm not sure how this module is loaded in the traditional way. But maybe
the Xorg and kernel logs shows something.
> Also, in my understanding, if I want a splashscreen to be shown, the
> graphics driver moduled needs to be loaded early, right?
You ignore the first step ("make it work") and directly go to the second
("make it right"). You have not shown anything (logs for example,
installed packages with i-t hooks) that suggests that i-t does anything
wrong; the case that you use a different kernel config than the official
kernels does not make it easier.
> Are the directfb-based splash screens such as splahy compatible with
> KMS in the first place?
KMS provides a framebuffer device, so I would say yes.
> > | $ gunzip -c initrd.img-2.6.32-4-686-bigmem | cpio -tv | grep -a i915
> > | -rw-r--r-- 1 root root 23 Jan 7 23:51 etc/modprobe.d/i915-kms.conf
> What are you trying to say? You need to be a little bit more verbose
> to be actually helpful.
There is no i915 module in a initramfs generated on my rather generic
system. So it is included either by your config or by another package.
Bastian
--
The sight of death frightens them [Earthers].
-- Kras the Klingon, "Friday's Child", stardate 3497.2
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100326140726.GA13734@wavehammer.waldi.eu.org">ht tp://lists.debian.org/20100326140726.GA13734@wavehammer.waldi.eu.org
Bug#575501: initramfs-tools: radeon.ko not included into initrd
