FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 03-26-2010, 10:31 AM
Marc Haber
 
Default Bug#575501: initramfs-tools: radeon.ko not included into initrd

Package: initramfs-tools
Version: 0.93.4
Severity: wishlist

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?

Greetings
Marc


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.33.1-zgws1 root=/dev/mapper/root ro resume=/dev/mapper/swap0 quiet splash video=radeon:modeset=1

-- /proc/filesystems
ext3
udf
iso9660
vfat

-- lsmod
Module Size Used by
vfat 6820 0
fat 36008 1 vfat
isofs 25174 0
nls_utf8 928 0
udf 62456 0
tun 8884 2
snd_intel8x0m 8400 0
snd_ac97_codec 80225 1 snd_intel8x0m
ac97_bus 742 1 snd_ac97_codec
ppdev 4294 0
lp 5768 0
parport 12962 2 ppdev,lp
sco 6231 2
bnep 7203 2
l2cap 25549 3 bnep
crc16 1011 1 l2cap
bluetooth 38935 5 sco,bnep,l2cap
ipt_ULOG 4461 1
vboxnetadp 5186 0
vboxnetflt 10598 0
vboxdrv 116590 2 vboxnetadp,vboxnetflt
acpi_cpufreq 5059 1
cpufreq_powersave 606 0
cpufreq_userspace 1372 0
cpufreq_conservative 7036 0
cpufreq_ondemand 6169 2
freq_table 1743 2 acpi_cpufreq,cpufreq_ondemand
iptable_filter 1030 0
ipt_MASQUERADE 1130 10
iptable_nat 2798 1
nf_nat 10767 2 ipt_MASQUERADE,iptable_nat
nf_conntrack_ipv4 7663 3 iptable_nat,nf_nat
nf_conntrack 39683 4 ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv 4
nf_defrag_ipv4 799 1 nf_conntrack_ipv4
ip_tables 7397 2 iptable_filter,iptable_nat
x_tables 9112 4 ipt_ULOG,ipt_MASQUERADE,iptable_nat,ip_tables
binfmt_misc 4883 1
8021q 14027 0
bridge 35340 0
stp 1032 1 bridge
llc 2613 2 bridge,stp
ipv6 195878 40
mmc_block 6589 0
snd_hda_codec_analog 46653 1
snd_hda_intel 16049 4
snd_hda_codec 42520 2 snd_hda_codec_analog,snd_hda_intel
snd_pcm_oss 28573 0
arc4 994 2
snd_mixer_oss 11983 1 snd_pcm_oss
ecb 1489 2
snd_pcm 48151 5 snd_intel8x0m,snd_ac97_codec,snd_hda_intel,snd_hda _codec,snd_pcm_oss
snd_seq_dummy 959 0
snd_seq_oss 21024 0
snd_seq_midi 3496 0
snd_rawmidi 13140 1 snd_seq_midi
iwl3945 62461 0
pcmcia 23354 0
snd_seq_midi_event 3968 2 snd_seq_oss,snd_seq_midi
iwlcore 75518 1 iwl3945
snd_seq 35503 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
sdhci_pci 5047 0
firewire_ohci 17740 0
mac80211 106608 2 iwl3945,iwlcore
tifm_sd 6410 0
snd_timer 13290 2 snd_pcm,snd_seq
ata_generic 2063 0
tg3 96671 0
tifm_7xx1 3114 0
yenta_socket 8878 1
sdhci 11863 1 sdhci_pci
snd_seq_device 3965 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
cfg80211 92531 3 iwl3945,iwlcore,mac80211
firewire_core 33273 1 firewire_ohci
ata_piix 17129 0
rsrc_nonstatic 7483 1 yenta_socket
mmc_core 39316 3 mmc_block,tifm_sd,sdhci
uhci_hcd 16204 0
rfkill 11140 3 bluetooth,cfg80211
libphy 12387 1 tg3
led_class 1873 1 sdhci
tifm_core 3448 2 tifm_sd,tifm_7xx1
crc_itu_t 1015 2 udf,firewire_core
ehci_hcd 26606 0
snd 36436 21 snd_intel8x0m,snd_ac97_codec,snd_hda_codec_analog, snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
pcmcia_core 22364 3 pcmcia,yenta_socket,rsrc_nonstatic
rng_core 2398 0
soundcore 4143 1 snd
rtc_cmos 6858 0
intel_agp 19857 0
i2c_i801 5880 0
snd_page_alloc 5185 3 snd_intel8x0m,snd_hda_intel,snd_pcm
rtc_core 9649 1 rtc_cmos
psmouse 28437 0
rtc_lib 1349 1 rtc_core
video 15566 0
evdev 5985 16
output 1292 1 video
ext3 87857 8
jbd 33535 1 ext3
mbcache 3990 1 ext3
sha256_generic 11161 18
aes_i586 6860 21
aes_generic 25762 1 aes_i586
cbc 1995 9
dm_crypt 8931 9
dm_mirror 10125 0
dm_region_hash 5776 1 dm_mirror
dm_log 7044 2 dm_mirror,dm_region_hash
dm_snapshot 24771 9
dm_mod 46730 73 dm_crypt,dm_mirror,dm_log,dm_snapshot
raid456 40328 0
async_raid6_recov 2806 1 raid456
async_pq 1392 2 raid456,async_raid6_recov
raid6_pq 77980 2 async_raid6_recov,async_pq
async_xor 865 3 raid456,async_raid6_recov,async_pq
xor 13829 1 async_xor
async_memcpy 586 2 raid456,async_raid6_recov
async_tx 1169 5 raid456,async_raid6_recov,async_pq,async_xor,async _memcpy
raid1 16725 0
md_mod 71947 2 raid456,raid1
sd_mod 22964 2
ahci 27320 2
libata 118312 3 ata_generic,ata_piix,ahci
radeon 543820 2
ttm 34118 1 radeon
drm_kms_helper 18609 1 radeon
drm 116985 4 radeon,ttm,drm_kms_helper
agpgart 20836 3 intel_agp,ttm,drm
firmware_class 5326 4 iwl3945,pcmcia,tg3,radeon
i2c_algo_bit 3715 1 radeon
i2c_core 12538 5 i2c_i801,radeon,drm_kms_helper,drm,i2c_algo_bit

-- /etc/kernel-img.conf
do_symlinks = no
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = /usr/sbin/update-grub
postrm_hook = /usr/sbin/update-grub

-- /etc/initramfs-tools/initramfs.conf
MODULES=dep
BUSYBOX=y
KEYMAP=n
BOOT=local
DEVICE=eth0
NFSROOT=auto

-- /etc/crypttab
# <target device> <source device> <key file> <options>
root /dev/mapper/swivel-c_root none luks,keyscript=/etc/keyscript_swivel
boot /dev/mapper/swivel-c_boot none luks,keyscript=/etc/keyscript_swivel
swap0 /dev/mapper/swivel-c_swap0 none luks,keyscript=/etc/keyscript_swivel
usr /dev/mapper/swivel-c_usr none luks,keyscript=/etc/keyscript_swivel
var /dev/mapper/swivel-c_var none luks,keyscript=/etc/keyscript_swivel
home /dev/mapper/swivel-c_home none luks,keyscript=/etc/keyscript_swivel
bigstuff /dev/mapper/swivel-c_bigstuff none luks,keyscript=/etc/keyscript_swivel
vm /dev/mapper/swivel-c_vm none luks,keyscript=/etc/keyscript_swivel
scyw00225 /dev/mapper/swivel-c_scyw00225 none luks,keyscript=/etc/keyscript_swivel

-- /sys/block
dm-0
dm-1
dm-10
dm-11
dm-12
dm-13
dm-14
dm-15
dm-16
dm-17
dm-18
dm-19
dm-2
dm-20
dm-21
dm-22
dm-23
dm-24
dm-25
dm-26
dm-27
dm-28
dm-29
dm-3
dm-4
dm-5
dm-6
dm-7
dm-8
dm-9
mmcblk0
sda


-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)

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
 
Old 03-26-2010, 11:04 AM
Bastian Blank
 
Default 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
 
Old 03-26-2010, 11:25 AM
Marc Haber
 
Default 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
 
Old 03-26-2010, 12:20 PM
Bastian Blank
 
Default 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.

| $ 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

Bastian

--
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
 
Old 03-26-2010, 12:39 PM
Marc Haber
 
Default 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
 
Old 03-26-2010, 01:07 PM
Bastian Blank
 
Default 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
 

Thread Tools




All times are GMT. The time now is 09:22 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org