On Thu, Aug 05, 2004 at 08:35:15AM +0200, Harald Dunkel wrote:
> This is /proc/scsi for my PC (booted from a disk managed by
> sata_sil):
Looks like you used an upstream kernel. It's a feature, but the debian
patches reintroduce these files wrongly because mkinitrd makes invalid
assumptions.
Am Montag, 9. August 2004 15:46 schrieben Sie:
> Christian,
>
> Does /proc/scsi/ exist? If so, can you show an 'ls' of that directory
> and the content of the files in there.
[EMAIL PROTECTED]:/proc/scsi$ ls -la
insgesamt 0
dr-xr-xr-x 5 root root 0 2004-08-09 19:37 .
dr-xr-xr-x 95 root root 0 2
* Christian Leimer <[EMAIL PROTECTED]> [2004-08-09 19:58]:
> > Does /proc/scsi/ exist? If so, can you show an 'ls' of that directory
> > and the content of the files in there.
> [EMAIL PROTECTED]:/proc/scsi$ ls -la
Hm, okay. The error you quoted earlier suggesed that /proc/scsi
doesn't exist...
Package: kernel-image-2.6.7-1-686
Version: 2.6.7-2
Severity: normal
hotplug goes by the modules.pcimap to determine which modules to load.
The modules.pcimap indicates that the sound card should use the snd-cs46xx
driver. Upon loading that module, it indicates otherwise.
lspci
:00:00.0 Host
It still occurs.
I did generate several new initrd variations (and went manually using a
busybox initrd).
the -U commandline on mdadm /w initrd causes it to consistently segfault
(as I mentioned in the bug report).
Once past that issue, lvm2 still segfaults.
There is a slightly newer build of lv
Your message dated Mon, 9 Aug 2004 17:21:44 +0100
with message-id <[EMAIL PROTECTED]>
and subject line mkinitrd needs "raidtool2 OR mdadm" for RAID arrays
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the ca
On Sat, Aug 07, 2004 at 12:33:37PM -0300, Joey Hess wrote:
> Andreas Barth wrote:
> > kernel-image-2.4.25-atari/2.4.25-1
>
> Currently udebs produced by linux-kernel-di-m68k include modules taken
> from this package, as well as 2.4.26-atari. We have switched to the
> 2.4.26 kernel for atari in d-i
Martin Michlmayr wrote:
Herbert said: "Well if mkinitrd didn't check the existence of those
modules then people who don't configure them into the kernel at all
will get an unbootable system.
As checking the kernel config file is pretty much unmaintainable
at the moment, this is the best we can do.
On Mon, 2004-08-09 at 14:44 +0100, Martin Michlmayr wrote:
> * tbm <[EMAIL PROTECTED]> [2004-08-04 17:41]:
> > * Harald Dunkel <[EMAIL PROTECTED]> [2004-08-02 09:05]:
> > > The problem is that sometimes /proc/scsi does not contain the module
> > > name for my swap device. 'sata_sil' does not appear
#cat /proc/scsi/device_info
'Aashima' 'IMAGERY 2400SP' 0x1
'CHINON' 'CD-ROM CDS-431' 0x1
'CHINON' 'CD-ROM CDS-535' 0x1
'DENON' 'DRD-25X' 0x1
'HITACHI' 'DK312C' 0x1
'HITACHI' 'DK314C' 0x1
'IMS' 'CDD521/10' 0x1
'MAXTOR' 'XT-3280' 0x1
'MAXTOR' 'XT-4380S' 0x1
'MAXTOR' 'MXT-1240S' 0x1
'MAXTOR' 'XT-4170S
Il lun, 2004-08-09 alle 15:43, Martin Michlmayr ha scritto:
> * Giuseppe Sacco <[EMAIL PROTECTED]> [2004-08-08 18:15]:
> > I may confirm that if I use dpkg to install the very same kernel package
> > outside of the chroot environment, then the installation succeed.
>
> Do you have lvm installed in
* Harald Dunkel <[EMAIL PROTECTED]> [2004-08-05 08:35]:
> This is /proc/scsi for my PC (booted from a disk managed by
> sata_sil):
>
> # ls -ld $(find /proc/scsi )
> dr-xr-xr-x 3 root root 0 Aug 5 08:32 /proc/scsi
> -r--r--r-- 1 root root 0 Aug 5 08:32 /proc/scsi/device_info
...
What's the co
Max,
Do you have any more information about this problem? Does this still
occur? Can you generate a new initrd and see if that shows the same
problems?
--
Martin Michlmayr
[EMAIL PROTECTED]
* tbm <[EMAIL PROTECTED]> [2004-08-04 17:41]:
> * Harald Dunkel <[EMAIL PROTECTED]> [2004-08-02 09:05]:
> > The problem is that sometimes /proc/scsi does not contain the module
> > name for my swap device. 'sata_sil' does not appear in /proc/scsi. I
> > don't know why its not there, but this is not
Christian,
Does /proc/scsi/ exist? If so, can you show an 'ls' of that directory
and the content of the files in there.
What kernel were you upgrading from?
--
Martin Michlmayr
[EMAIL PROTECTED]
* Bastian Blank <[EMAIL PROTECTED]> [2004-08-03 13:35]:
> mkinitrd fails if the specified storage modules are compiled into the
> kernel. This makes it unusable on s390 as any current kernels have them
> compiled in.
>
> | /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed
> | FATAL: Module
Processing commands for [EMAIL PROTECTED]:
> tags 255390 + pending
Bug#255390: mkinitrd does not find modprobe.conf
There were no tags set.
Tags added: pending
> --
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debia
* Giuseppe Sacco <[EMAIL PROTECTED]> [2004-08-08 18:15]:
> I may confirm that if I use dpkg to install the very same kernel package
> outside of the chroot environment, then the installation succeed.
Do you have lvm installed in the real system?
Is there a reason why the device mapper module is l
Processing commands for [EMAIL PROTECTED]:
> reassign 264482 kernel-source-2.6.7
Bug#264482: using mount with an fstab entry works, specifying
devices/mountpoints manually does not (2.6/sparc64)
Bug reassigned from package `busybox-cvs' to `kernel-source-2.6.7'.
> retitle 264482 sparc64 - compat
unsubscribe
Package: kernel-image-2.6.7-1-k7
Version: 2.6.7-2
Severity: normal
Hello,
I am experiencing machine hangs under severe ide-activity, e.g "hdparm
-t" with this kernel version. The version 2.6.7-k7-smp works fine.
It seems to be exactly the problem described here:
http://bugme.osdl.org/show_bug.c
21 matches
Mail list logo
