On Wednesday 15 March 2006 21:57, C Shore wrote:
Abstract
snip
Sven is certainly not quiet, however from what I have seen of
type of response his suggestions and posts get, he is justifiably
frustrated. I am personally surprised he hasn't gotten disgusted
with the project and left, or
Just to let you know that the 'fix' did not work. :-(
The hard drives will still randomly go to sleep and not wake up.
What's more, even a sysrq forced reboot does not wake the drive up -
only a cold boot works!
The end result is that we are gradually replacing these crappy disks
in our
reassign 357224 initramfs-tools
thanks
On Mar 16, Tonda Míšek [EMAIL PROTECTED] wrote:
Package: udev
Version: 0.087-2
I have unstable Debian. I upgraded to new version of udev (from
udev_0.087-1_i386.deb).
The system cannot boot with message like Kernel panic, cannot found root
system.
Processing commands for [EMAIL PROTECTED]:
reassign 357224 initramfs-tools
Bug#357224: Kernel panic after udev update
Bug reassigned from package `udev' to `initramfs-tools'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Processing commands for [EMAIL PROTECTED]:
tags 357224 moreinfo
Bug#357224: Kernel panic after udev update
There were no tags set.
Tags added: moreinfo
stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian
Package: linux-image-2.6.16-rc5-686
Version: 2.6.15+2.6.16-rc5-0experimental
Greetings,
The last time sound worked on my Fujitsu Lifebook P2120 was with 2.6.3
(or maybe 2.6.5, but not with 2.6.8 or anything since). An identical
ALSA setup worked with sarge under 2.6.3 but not 2.6.8. Tried
On Thu, Mar 16, 2006 at 04:23:05AM -0600, Adam C Powell IV wrote:
The last time sound worked on my Fujitsu Lifebook P2120 was with 2.6.3
(or maybe 2.6.5, but not with 2.6.8 or anything since). An identical
ALSA setup worked with sarge under 2.6.3 but not 2.6.8. Tried running
alsaconf again
Title: unsuscribe
Balbir Pabla
Environment Canada
Ph : (416)739-4670
Fax : (416)739-4288
E-mail : [EMAIL PROTECTED]
Package: initramfs-tools
Version: 0.53c
Hi,
I am trying to boot a notebook from an external USB harddisk with
grub, a debian 2.6.15.1 kernel and an initrd generated with
mkinitramfs.
The kernel boots, but then does not find it's root partition. It says
that /dev/sda1 does not exist, and opens
On Thu, 16 Mar 2006, Manuel Bilderbeek wrote:
2006/3/15, maximilian attems [EMAIL PROTECTED]:
I'll first try with lilo if you can confirm that I should indeed run
udev as you said, ignoring the very strong warning.
please use grub if lilo didn't work out.
I understand, but do
On Wed, Mar 15, 2006 at 10:57:42PM -0500, C Shore wrote:
Abstract
Thanks for your message, this indeed sums up my feeling very well.
As for mediation, seeing the thing go into an impass, i asked Andreas Barth
(on the technical comittee) to mediate on thursday/friday, and went into
offline land,
Package: initramfs-tools
Version: 0.53
Severity: normal
The man page for mkinitramfs never defines what is meant by the argument
'version'. An explicit example would be useful to avoid confusion, since
the value of the 'Version' string that is output by
dpkg --status linux-image-NNN | grep
Package: kernel
Version: 2.6.15-8
Severity: important
Hi,
this system has an Asus A8V motherboard with an integrated 2 channels
SATA controller. It has 2 SATA disks (/dev/sda and /dev/sdb) that are
assembled in a RAID1 array (/dev/md0).
A few days ago I mistakingly unplugged the power
Only problem was that the network interface did not come up. Trying to
manually start it resulted in:
# ifup eth0
Ignoring unknown interface eth0=eth0.
This looks like an issue related to udev persistent device naming.
Further info:
- The ctc module was loaded:
# lsmod
Module
Hi,
I could find a solution. I've put a script in scripts/init-premount
which simply waits for 10 seconds. Just to find the problem.
However, the script should be a little bit more elaborated and use a
case statement for the different types of root devices (hd? sd?
by-label, by-uuid) and so on.
On Thu, Mar 16, 2006 at 04:09:38PM +0100, Hadmut Danisch wrote:
I could find a solution. I've put a script in scripts/init-premount
which simply waits for 10 seconds. Just to find the problem.
However, the script should be a little bit more elaborated and use a
case statement for the
On Thu, Mar 16, 2006 at 04:13:21PM +0100, Frans Pop wrote:
Only problem was that the network interface did not come up. Trying to
manually start it resulted in:
You need a 2.6.16-rc5 kernel and sysconfig-hardware.
The new kernel properly loads the network modules, the later is used to
I don't really understand what's happening here. 2.6.15 images install
perfectly and use initramfs-tools, but 2.6.16 seems to get totally
confused and tries to use yaird instead.
The system is running 2.4.27.
ii initramfs-tools 0.55btools for generating an initramfs
ii udev
On Thursday 16 March 2006 18:41, Frans Pop wrote:
I don't really understand what's happening here. 2.6.15 images install
perfectly and use initramfs-tools, but 2.6.16 seems to get totally
confused and tries to use yaird instead.
After creating the initramfs manually using
mkinitramfs
posted mailed
Jonas Smedegaard wrote:
I believe udev cintained within ramdisk needs to match udev outside -
so if udev on the system is updated then (all!) initramfs-based
ramdisks needs to be regenerated in order to survive _next_ boot.
Ouch! If this is true, it'd seem that somehow, the
On Thu, Mar 16, 2006 at 06:41:27PM +0100, Frans Pop wrote:
I don't really understand what's happening here. 2.6.15 images install
perfectly and use initramfs-tools, but 2.6.16 seems to get totally
confused and tries to use yaird instead.
Yes, this is the definition until now. If you don't want
On Qui, 2006-03-16 at 16:41 +0100, Ivan Warren wrote:
Only problem was that the network interface did not come up. Trying to
manually start it resulted in:
# ifup eth0
Ignoring unknown interface eth0=eth0.
This looks like an issue related to udev persistent device naming.
Thanks Bastian.
On Thursday 16 March 2006 17:29, Bastian Blank wrote:
On Thu, Mar 16, 2006 at 04:13:21PM +0100, Frans Pop wrote:
Only problem was that the network interface did not come up. Trying
to manually start it resulted in:
You need a 2.6.16-rc5 kernel and sysconfig-hardware.
Yes,
On Thu, Mar 16, 2006 at 07:23:40PM +0100, Frans Pop wrote:
I see that the experimental kernel image does not depend on
sysconfig-hardware. Should it (to ensure that users upgrading from Sarge
will have it installed)?
Hmm. It is no dependency as the kernel can work without. Also it needs a
On Thursday 16 March 2006 19:26, Bastian Blank wrote:
Yes, this is the definition until now. If you don't want to wait for
the next snapshot, you have to force it with /etc/kernel-img.conf.
Shouldn't it at least have seen that initramfs-tools was installed and
used that as yaird was not even
On Thu, Mar 16, 2006 at 07:21:40PM +0100, Frans Pop wrote:
cio: Was not able to determine available CHSCs.
HHCCP014I CPU: Operand exception CODE=0015 ILC=4
PSW=070C2000 802035AC INST=B2342000 STSCH 0(2)
V:03976C10:K:04=
On Thu, Mar 16, 2006 at 07:50:02PM +0100, Frans Pop wrote:
Shouldn't it at least have seen that initramfs-tools was installed and
used that as yaird was not even installed?
Yes. initramfs-tools fullfills the dependency because of the
linux-initramfs-tool provides.
Bastian
--
Killing is
Hi,We are using (Redhat 32bit ) and (Suse 64bit) machines . The g++ compiler version we use is "gcc version 2.96 2731 (Red Hat Linux 7.2 2.96-124.7.2)"The gcc compiler for suse is "gcc version3.3.3 (SUSE Linux)"We're using these compilers and we're not sure what versions of
Package: initramfs-tools
Version: 0.55b
Severity: important
Tags: patch
Symptoms:
-
- System doesn't boot, complaining
Target filesystem doesn't have /sbin/init
(or wherever you init is supposed to be)
- / (the root-fs) is on e.g. /dev/hdb1
or any other partition where the minor
On Thu, Mar 16, 2006 at 07:33:59PM +0100, Bastian Blank wrote:
Hmm. It is no dependency as the kernel can work without. Also it needs a
converter for chandev to the new config format.
Which will only work automaticaly in the easiest config: only one
device/type as there is not longer any order.
This has also been happening to me quite frequently for sometime now.
Any ideas of a workaround/fix?
Alan
Bootdata ok (command line is root=/dev/sda5 ro console=tty0 )
Linux version 2.6.15-1-amd64-k8 (Debian 2.6.15-8) ([EMAIL PROTECTED]) (gcc
version 4.0.3 20060304 (prerelease) (Debian
I probably should have added the following further info in my previous
email:
a) Windows/memtest run fine
b) It was running really quite stable until quite a few changes happened
- I upgraded after having not for quite a while, I also got a BIOS
update to fix another bug and got a wifi card
On Thu, Mar 16, 2006 at 01:20:16PM -0500, Anthony DeRobertis wrote:
posted mailed
Jonas Smedegaard wrote:
I believe udev cintained within ramdisk needs to match udev outside -
so if udev on the system is updated then (all!) initramfs-based
ramdisks needs to be regenerated in order to
Daniel,
Please provide the output of:
lspci -v
lspci -n
--
dann frazier [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
34 matches
Mail list logo
