Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
On Thu, Dec 01, 2005 at 08:25:13AM +0100, Sven Luther wrote: Well, at 2.6.14 release time, initramfs-tools, and his klibc dependency, had some maturation problems, and is also regularly broken by udev, so for now, yaird, provided it works, is still the more solid solution, and at least it will fail cleanly, and give you an error message or such, while initramfs-tools may or not fail during boot time. In case this was not clear, this applied to the time 2.6.14 was released. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337065: yaird does not work with labels on XFS either
Hello, see bug #341498. Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341498: does not find valid filesystem label from fstab LABEL= option
Am Mittwoch 30 November 2005 23:59 schrieb Jonas Smedegaard: On Wed, 30 Nov 2005 23:40:04 +0100 Martin Steigerwald [EMAIL PROTECTED] wrote: The offending line in /etc/fstab is: LABEL=debian / xfs defaults0 1 This bug may or may not be related to: bug #337168 and bug #337415. Sounds like #337065 - could you please check... Hello Jonas, well I cannot use a UUID either with yaird and replacing LABEL=debian by /dev/disk/by-label/debian seems to work, so the bug I reported appears to be similar to #337065. I have no reiserfs oder ext3 root partition to test whether it would work with other filesystems. Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: fixed in between
Processing commands for [EMAIL PROTECTED]: tags 338406 moreinfo Bug#338406: initramfs-tools: Doesn't create /dev/hda* device nodes on LVM system There were no tags set. Tags added: moreinfo tags 337045 moreinfo Bug#337045: linux-image-2.6.14-1-686: race condition?: sometimes fails to correctly detect my harddisk There were no tags set. Tags added: moreinfo tags 337033 moreinfo Bug#337033: linux-image-2.6.14-1-powerpc64: does not boot, failed to mount root fs There were no tags set. Tags added: moreinfo tags 336317 moreinfo Bug#336317: initramfs-tools: created initramfs is unable to boot a system with mirrored rootdisks There were no tags set. Tags added: moreinfo tags 332824 moreinfo Bug#332824: linux-image-2.6.13-1-686: Cannot find LVM root fs There were no tags set. Tags added: moreinfo End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 08:25:13 +0100 Sven Luther [EMAIL PROTECTED] wrote: Maybe the best idea would be to have yaird as first default as now, but have the dependencies install both, which would guarantee it always works. A better approach IMHO is to recommend (not depend on) alternative ramdisk tool than the one picked as default. initramfs-tools will pull in udev which is unwanted for some, and yaird will similarly pull in perl dependencies that is unwanted for some. Sure, both can be seen as weird complaints (I have had my fights with convincing the php4 maintainer to not depend on X11 by default when sanely avoidable), but I don't think disliking udev should force one to either recompile kernels or use equivs. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDjtvFn7DbMsAkQLgRAtUiAJ41fFeCsOqGJL0Thd0y34hUyWVvwwCeLy7e Z/lO7oCK9c7D8OS+8wuAimQ= =xFwx -END PGP SIGNATURE-
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
On Thu, Dec 01, 2005 at 12:17:25PM +0100, Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 08:25:13 +0100 Sven Luther [EMAIL PROTECTED] wrote: Maybe the best idea would be to have yaird as first default as now, but have the dependencies install both, which would guarantee it always works. A better approach IMHO is to recommend (not depend on) alternative ramdisk tool than the one picked as default. Well, with tools like aptitude, there is not much of a difference. initramfs-tools will pull in udev which is unwanted for some, and yaird will similarly pull in perl dependencies that is unwanted for some. perl dependencies are hardly problematic, especially since we have perl-base, altough it would be good to make yaird depend on perl-base only, but we discussed this already. Udev might be more legitimate to not want though. Sure, both can be seen as weird complaints (I have had my fights with convincing the php4 maintainer to not depend on X11 by default when This is also a sane complaint, we divided ocaml packages between the x version and the nox stuff too. sanely avoidable), but I don't think disliking udev should force one to either recompile kernels or use equivs. Yep, that makes sense. Too bad dependencies don't allow us to do something more advanced. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
Package: yaird Version: 0.0.11-12 Severity: important This is a Old-world IDE-based Macintosh Performa 5400, running unstable on a 2.6.8-12 kernel. Unpacking linux-image-2.6-powerpc (from .../linux-image-2.6-powerpc_2.6.14-4_powerpc.deb) ... Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA Failed to create initrd image. dpkg: error processing linux-image-2.6.14-2-powerpc (--configure): subprocess post-installation script returned error exit status 2 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-powerpc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages yaird depends on: ii cpio 2.6-3 GNU cpio -- a program to manage ar ii dash 0.5.2-7 The Debian Almquist Shell ii libc62.3.5-4 GNU C Library: Shared libraries an ii libhtml-template-perl2.7-1 HTML::Template : A module for usin ii libparse-recdescent-perl 1.94.free-1 Generates recursive-descent parser ii perl 5.8.7-4 Larry Wall's Practical Extraction yaird recommends no packages. -- no debconf information signature.asc Description: Digital signature
Bug#341522: Drivers for sbus devices are not included in initrd on sparc
On Wed, Nov 30, 2005 at 09:54:46PM -0800, Jurij Smakov wrote: Package: yaird Version: 0.0.11-12 Severity: important Hi, As I've mentioned on d-k, the sbus devices found in some early Ultras are not properly sysfs-trained. As a result, yaird currently fails to include the SCSI driver if the controller is an sbus device. As modifying the drivers may be too complicated, a possible workaround is to always force-include the esp.ko driver (I believe it is the only sbus-based SCSI controller) on sparc. If anyone volunteers to test the code I could look into converting sbus to the driver model. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 12:37:23PM +0100, Hans Ekbrand wrote: Package: yaird Version: 0.0.11-12 Severity: important This is a Old-world IDE-based Macintosh Performa 5400, running unstable on a 2.6.8-12 kernel. Hi Hans, ... Do you happen to know exactly which driver is needed for this device ? Unpacking linux-image-2.6-powerpc (from .../linux-image-2.6-powerpc_2.6.14-4_powerpc.deb) ... Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA Could you send us a : find /sys/devices/pci:00/:00:10.0/0.f300:ohare output, so we know this ? I suppose this is just that yaird doesn't know about the intermediary nodes between the actual block driver and the hardware it knows of, so will be rather easy to fix. Erik, Jonas, what about a i know what i do option, which would allow to ignore this kind of in-between nodes, provided that the final block driver is known ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote: On Thu, Dec 01, 2005 at 12:37:23PM +0100, Hans Ekbrand wrote: Package: yaird Version: 0.0.11-12 Severity: important This is a Old-world IDE-based Macintosh Performa 5400, running unstable on a 2.6.8-12 kernel. Hi Hans, ... Do you happen to know exactly which driver is needed for this device ? Do you mean which module to drive this IDE harddisk? Unpacking linux-image-2.6-powerpc (from .../linux-image-2.6-powerpc_2.6.14-4_powerpc.deb) ... Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA Could you send us a : find /sys/devices/pci:00/:00:10.0/0.f300:ohare /sys/devices/pci:00/:00:10.0/0.f300:ohare /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0 /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0 /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3 /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/devspec
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Other suitable ramdisk generating tools : /usr/sbin/mkinitramfs. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA Failed to create initrd image. dpkg: error processing linux-image-2.6.14-2-powerpc (--configure): -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] Q. What is that strange attachment in this mail? A. My digital signature, see www.gnupg.org for info on how you could use it to ensure that this mail is from me and has not been altered on the way to you. signature.asc Description: Digital signature
Bug#341559: yaird: fails to create initrd
clone 341559 -1 reassign -1 initramfs-tools stop On Thu, Dec 01, 2005 at 01:33:10PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. well you are still using yaird. please try temporarly adding to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd (you might need to comment that as soon as you want to test yaird). Other suitable ramdisk generating tools : /usr/sbin/mkinitramfs. so it's installed ;) -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: yaird: fails to create initrd
Processing commands for [EMAIL PROTECTED]: clone 341559 -1 Bug#341559: yaird: fails to create initrd Bug 341559 cloned as bug 341567. reassign -1 initramfs-tools Bug#341567: yaird: fails to create initrd Bug reassigned from package `yaird' to `initramfs-tools'. stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote:
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote:
On Thu, Dec 01, 2005 at 12:37:23PM +0100, Hans Ekbrand wrote:
Package: yaird
Version: 0.0.11-12
Severity: important
This is a Old-world IDE-based Macintosh Performa 5400, running unstable
on a 2.6.8-12 kernel.
Hi Hans, ...
Do you happen to know exactly which driver is needed for this device ?
Do you mean which module to drive this IDE harddisk?
Unpacking linux-image-2.6-powerpc (from
.../linux-image-2.6-powerpc_2.6.14-4_powerpc.deb) ...
Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ...
Using /usr/sbin/mkinitrd.yaird to build the ramdisk.
Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd
/usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs.
yaird error: unrecognised device:
/sys/devices/pci:00/:00:10.0/0.f300:ohare
yaird error: unrecognised device:
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
Could you send us a :
find /sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block
This is probably similar to the problem we had :
/sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-io/0.0002:ata-3/ide1
so instead of ignoring 0.8000:mac-io and 0.0002:ata-3, you need to
ignore 0.f300:ohare and 0.0002:ATA.
So, in /usr/lib/yaird/perl/Hardware.pm, at line 81, you need to copy one of the
two
above lines :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:mac-io$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ata-\d+$!) {
# Apple IDE bus; harmless
}
for your case, maybe something like :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA\d+$!) {
# Apple IDE bus; harmless
}
but i am no perl expert, and may have gotten the exact magic wrong.
Friendly,
Sven Luther
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 01:41:01PM +0100, Maximilian Attems wrote: clone 341559 -1 reassign -1 initramfs-tools stop On Thu, Dec 01, 2005 at 01:33:10PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. well you are still using yaird. OK. I thought installing initramfs-tools would suffice, I didn't know that it was an alternativ to yaird, nor that it would not be used by default. please try temporarly adding to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd OK. Now it worked! the initrd was created and the boot successful. -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? signature.asc Description: Digital signature
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 01:52:34PM +0100, Sven Luther wrote:
On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote:
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote:
Could you send us a :
find /sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block
This is probably similar to the problem we had :
/sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-io/0.0002:ata-3/ide1
so instead of ignoring 0.8000:mac-io and 0.0002:ata-3, you need to
ignore 0.f300:ohare and 0.0002:ATA.
So, in /usr/lib/yaird/perl/Hardware.pm, at line 81, you need to copy one of
the two
above lines :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:mac-io$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ata-\d+$!) {
# Apple IDE bus; harmless
}
for your case, maybe something like :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA\d+$!) {
# Apple IDE bus; harmless
}
but i am no perl expert, and may have gotten the exact magic wrong.
OK, I will try that but does not have enough time for the moment.
--
Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED]
Q. What is that strange attachment in this mail?
A. My digital signature, see www.gnupg.org for info on how you could
use it to ensure that this mail is from me and has not been
altered on the way to you.
signature.asc
Description: Digital signature
Bug#341567: marked as done (yaird: fails to create initrd)
Your message dated Thu, 1 Dec 2005 14:29:03 +0100 with message-id [EMAIL PROTECTED] and subject line yaird: fails to create initrd 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 case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 1 Dec 2005 11:37:27 + From [EMAIL PROTECTED] Thu Dec 01 03:37:27 2005 Return-path: [EMAIL PROTECTED] Received: from emac140.socio.gu.se ([130.241.119.140] ident=mail) by spohr.debian.org with esmtp (Exim 4.50) id 1Ehmkh-00048p-3w for [EMAIL PROTECTED]; Thu, 01 Dec 2005 03:37:27 -0800 Received: from hans by emac140.socio.gu.se with local (Exim 3.35 #1 (Debian)) id 1Ehmkd-0001VD-00 for [EMAIL PROTECTED]; Thu, 01 Dec 2005 12:37:23 +0100 Date: Thu, 1 Dec 2005 12:37:23 +0100 From: Hans Ekbrand [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: yaird: fails to create initrd Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=ZPt4rx8FFjLCG7dd Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.5.9i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: yaird Version: 0.0.11-12 Severity: important This is a Old-world IDE-based Macintosh Performa 5400, running unstable on = a 2.6.8-12 kernel. Unpacking linux-image-2.6-powerpc (from .../linux-image-2.6-powerpc_2.6.14-= 4_powerpc.deb) ... Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin= /mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f3= 00:ohare yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f3= 00:ohare/0.0002:ATA Failed to create initrd image. dpkg: error processing linux-image-2.6.14-2-powerpc (--configure): subprocess post-installation script returned error exit status 2 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-powerpc Locale: LANG=3DC, LC_CTYPE=3DC (charmap=3DANSI_X3.4-1968) Versions of packages yaird depends on: ii cpio 2.6-3 GNU cpio -- a program to manag= e ar ii dash 0.5.2-7 The Debian Almquist Shell ii libc62.3.5-4 GNU C Library: Shared librarie= s an ii libhtml-template-perl2.7-1 HTML::Template : A module for = usin ii libparse-recdescent-perl 1.94.free-1 Generates recursive-descent pa= rser ii perl 5.8.7-4 Larry Wall's Practical Extract= ion=20 yaird recommends no packages. -- no debconf information --ZPt4rx8FFjLCG7dd Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDjuByfCyHKnBQYU4RAmxLAKC5NkdRuMnSym2cCxu3InIFTgztjgCeIaOe Fl89vkBmSrFHX3o1bKtJUm8= =H2W9 -END PGP SIGNATURE- --ZPt4rx8FFjLCG7dd-- --- Received: (at 341567-close) by bugs.debian.org; 1 Dec 2005 13:31:12 + From [EMAIL PROTECTED] Thu Dec 01 05:31:12 2005 Return-path: [EMAIL PROTECTED] Received: from baikonur.stro.at ([213.239.196.228]) by spohr.debian.org with esmtp (Exim 4.50) id 1EhoUL-0001r5-Ds for [EMAIL PROTECTED]; Thu, 01 Dec 2005 05:28:41 -0800 Received: by baikonur.stro.at (Postfix, from userid 1001) id B6FCF5C001; Thu, 1 Dec 2005 14:29:03 +0100 (CET) Date: Thu, 1 Dec 2005 14:29:03 +0100 From: Maximilian Attems [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: yaird: fails to create initrd Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.5.9i
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 12:25:02 +0100 Sven Luther [EMAIL PROTECTED] wrote: On Thu, Dec 01, 2005 at 12:17:25PM +0100, Jonas Smedegaard wrote: On Thu, 1 Dec 2005 08:25:13 +0100 Sven Luther [EMAIL PROTECTED] wrote: Maybe the best idea would be to have yaird as first default as now, but have the dependencies install both, which would guarantee it always works. A better approach IMHO is to recommend (not depend on) alternative ramdisk tool than the one picked as default. Well, with tools like aptitude, there is not much of a difference. Yes there is: Aptitude treats recommends as they are: Recommended but acceptable to explicitly avoid. Or, as I do for some setups: explicitly avoid recommended packages *always* by passing it - --with-recommends. initramfs-tools will pull in udev which is unwanted for some, and yaird will similarly pull in perl dependencies that is unwanted for some. perl dependencies are hardly problematic, especially since we have perl-base, altough it would be good to make yaird depend on perl-base only, but we discussed this already. Udev might be more legitimate to not want though. Stop spreading FUD, please. this has been discussed before and it does not seem likely to have yaird use only perl-base without extensive changes. Sure, both can be seen as weird complaints (I have had my fights with convincing the php4 maintainer to not depend on X11 by default when This is also a sane complaint, we divided ocaml packages between the x version and the nox stuff too. Please note that I did not claim insanity. I wrote that it _can_ be seen as weird. Agreeing with me is no argument that others can see it as weird. If interested then I'd appreciate help making libgd dependent packages build-depend on the -noxpm variant development packages, but really that is irrelevant for this bugreport. sanely avoidable), but I don't think disliking udev should force one to either recompile kernels or use equivs. Yep, that makes sense. Too bad dependencies don't allow us to do something more advanced. I just porposed a possible approach: When depending on yaird then recommend initramfs-tools, and vice versa. I am aware that apt-get ignores recommends, but that is a bug with apt, and everytime people are hit by that bug we get a chance to advertise aptitude (and if such advertisement is refused with apt-get is good enough for me, well - then it's their own fault they get hurt by things like this). - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDjwDMn7DbMsAkQLgRAnnZAJ9JPKevwJ6LklwoWJ4RPy5eUMSZnACdHMmh hCrRrAG92MmkxDLEmG6ku9c= =nzYT -END PGP SIGNATURE-
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 02:08:14PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 01:41:01PM +0100, Maximilian Attems wrote: clone 341559 -1 reassign -1 initramfs-tools stop On Thu, Dec 01, 2005 at 01:33:10PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. well you are still using yaird. OK. I thought installing initramfs-tools would suffice, I didn't know that it was an alternativ to yaird, nor that it would not be used by default. please try temporarly adding to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd OK. Now it worked! the initrd was created and the boot successful. Can you try the same thing also using MODULES=dep (or whatever that option is called) in /etc/mkinitramfs/mkinitramfs.conf please ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 03:16:04PM +0100, Sven Luther wrote: On Thu, Dec 01, 2005 at 02:08:14PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 01:41:01PM +0100, Maximilian Attems wrote: clone 341559 -1 reassign -1 initramfs-tools stop On Thu, Dec 01, 2005 at 01:33:10PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. well you are still using yaird. OK. I thought installing initramfs-tools would suffice, I didn't know that it was an alternativ to yaird, nor that it would not be used by default. please try temporarly adding to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd OK. Now it worked! the initrd was created and the boot successful. Can you try the same thing also using MODULES=dep (or whatever that option is called) in /etc/mkinitramfs/mkinitramfs.conf please ? no please dont!! svenl stop givine bad advices to users. #341559 is an yaird bug, the initramfs one was cloned as #341567 and is fixede. -- maks ps one last time cc 341559, sorry for the noise jonas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 15:27:35 +0100 Maximilian Attems [EMAIL PROTECTED] wrote: Now it worked! the initrd was created and the boot successful. Can you try the same thing also using MODULES=dep (or whatever that option is called) in /etc/mkinitramfs/mkinitramfs.conf please ? no please dont!! svenl stop givine bad advices to users. #341559 is an yaird bug, the initramfs one was cloned as #341567 and is fixede. Why not? Is that option somehow unsupported? We have here a chance to test initramfs-tools on a tricky machine - and Sven suggests to then extend the test to not only the default setting but also the more compact one. It is no secret that Sven and I is fond of yaird, but this is no competition: Do you prefer discovering possible bugs closer to release? - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDjw3Gn7DbMsAkQLgRAqnIAJ9krhuSG/SsQGqIcPXKdJ45NHye1wCffZ55 Y8zhxM+Tu5VAbLDtnfXTekM= =87uc -END PGP SIGNATURE-
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 03:27:35PM +0100, Maximilian Attems wrote: On Thu, Dec 01, 2005 at 03:16:04PM +0100, Sven Luther wrote: On Thu, Dec 01, 2005 at 02:08:14PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 01:41:01PM +0100, Maximilian Attems wrote: clone 341559 -1 reassign -1 initramfs-tools stop On Thu, Dec 01, 2005 at 01:33:10PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. well you are still using yaird. OK. I thought installing initramfs-tools would suffice, I didn't know that it was an alternativ to yaird, nor that it would not be used by default. please try temporarly adding to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd OK. Now it worked! the initrd was created and the boot successful. Can you try the same thing also using MODULES=dep (or whatever that option is called) in /etc/mkinitramfs/mkinitramfs.conf please ? no please dont!! Huh ? You don't want people to test initramfs-tools in MODULES=dep mode ? svenl stop givine bad advices to users. Huh again ? #341559 is an yaird bug, the initramfs one was cloned as #341567 and is fixede. Who cares, his stuff worked in initramfs-tools with MODULES=most, but was it tested in MODULES=dep ? Friendly, Sven Luther -- maks ps one last time cc 341559, sorry for the noise jonas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] --- Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail. Aucun virus connu a ce jour par nos services n'a ete detecte. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 03:50:46PM +0100, Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 15:27:35 +0100 Maximilian Attems [EMAIL PROTECTED] wrote: Now it worked! the initrd was created and the boot successful. Can you try the same thing also using MODULES=dep (or whatever that option is called) in /etc/mkinitramfs/mkinitramfs.conf please ? no please dont!! svenl stop givine bad advices to users. #341559 is an yaird bug, the initramfs one was cloned as #341567 and is fixede. Why not? Is that option somehow unsupported? We have here a chance to test initramfs-tools on a tricky machine - and Sven suggests to then extend the test to not only the default setting but also the more compact one. It is no secret that Sven and I is fond of yaird, but this is no competition: Do you prefer discovering possible bugs closer to release? defaults are set out of *dam-good-reasons*. :) if you wana play around with them do it on your dev machine. if svenl is serious about his little pet option than he would have followed up to his bug report long since 5th november. it's none of the business of this bug reporter. it seems like that very nice old world mac had np booting an full featured initramfs and reporter wanted to get his machine up quickly. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: next upload
Processing commands for [EMAIL PROTECTED]: tags #341162 pending Bug#341162: initramfs-tools: add mptspi module Tags were: patch Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337318: initramfs-tools: No way to specify module options for initramfs
tags 337318 moreinfo stop On Thu, 03 Nov 2005, Martin Wilck wrote: ramfs. This means that vital module options cannot be passed to the initramfs system. For my laptop I need the line options libata atapi_enabled=1 to be able to use my CD drive. in which file to you add that line? For other systems (e.g. fibre channel with persistent binding) the problems will be more severe. newer initramfs-tools ubuntu upstream copies across modprobe aliases and will add blacklist too. thanks for your feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 16:37:30 +0100 Maximilian Attems [EMAIL PROTECTED] wrote: On Thu, Dec 01, 2005 at 03:50:46PM +0100, Jonas Smedegaard wrote: Why not? Is that option somehow unsupported? defaults are set out of *dam-good-reasons*. :) Thanks for the clarification! - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDjyIqn7DbMsAkQLgRAqz4AJ9++7Z44MEN02bPaCZ8jv+YvZhhHwCgk2Dj BjVns+DrgbevigESZiJnEMs= =R+Un -END PGP SIGNATURE-
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 04:37:30PM +0100, Maximilian Attems wrote: On Thu, Dec 01, 2005 at 03:50:46PM +0100, Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 15:27:35 +0100 Maximilian Attems [EMAIL PROTECTED] wrote: Now it worked! the initrd was created and the boot successful. Can you try the same thing also using MODULES=dep (or whatever that option is called) in /etc/mkinitramfs/mkinitramfs.conf please ? no please dont!! svenl stop givine bad advices to users. #341559 is an yaird bug, the initramfs one was cloned as #341567 and is fixede. Why not? Is that option somehow unsupported? We have here a chance to test initramfs-tools on a tricky machine - and Sven suggests to then extend the test to not only the default setting but also the more compact one. It is no secret that Sven and I is fond of yaird, but this is no competition: Do you prefer discovering possible bugs closer to release? defaults are set out of *dam-good-reasons*. :) if you wana play around with them do it on your dev machine. if svenl is serious about his little pet option than he would have followed up to his bug report long since 5th november. it's none of the business of this bug reporter. Ok, since we go this way, i notice that you didn't even bother to post a single post to said bug report, and that when i used my time to test initramfs-tools on the pegasos, you ended up being uncivile to me (again) on irc, so really, i am a bit sick of your behavior. it seems like that very nice old world mac had np booting an full featured initramfs and reporter wanted to get his machine up quickly. So, what does it cost asking that he goes the full way and tries out MODULES=dep, or are you afraid it will be broken, and will need to coerce someone else to fix the bug for you ? Like you not even bothering to look at how to build klibc with l-k-h as it should, and me having to do it for you ? Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#314954: logitech usb mouse dies
I have already reported this bug in the Debian BTS with many details: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314954 I have now tested with a second logitech mouse attached. Bus 004 Device 004: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 TetraHub Bus 004 Device 001: ID : Bus 002 Device 006: ID 046a:0004 Cherry GmbH Bus 002 Device 001: ID : Bus 001 Device 007: ID 046d:c00e Logitech, Inc. Optical Mouse Bus 001 Device 006: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse Bus 001 Device 001: ID : Bus 003 Device 001: ID : It also loses the connection after a random amount of time (or maybe mouse move distance), but they lose the connection independently of each other. (Note that both mice are wheel mice, and share the same design, doesn't make sense to me that one is named .. Mouse and one .. Wheel Mouse) Willi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337176: initramfs-tools: initrd unusable on amd64
tags 337176 moreinfo tags 337607 moreinfo stop On Wed, 02 Nov 2005, Daniel Jacobowitz wrote: The generated initrd has ld.so in /lib, but no /lib64 symlink. But the ELF interpreter of all amd64 binaries points to /lib64. So the kernel fails to load /bin/sh. I'm going to try with the directory manually created next. please retest with latest initramfs-tools and udev from unstable, that issue should be fixed, i`ve at least 2 reported successes. in order to regenerate your initramfs you need to dpkg-reconfigure your linux image package. or you want to call update-initramfs -t -u -k 2.6.14-1-686 replace 2.6.14-1-686 with your exact uname -r output. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#337176: initramfs-tools: initrd unusable on amd64
Processing commands for [EMAIL PROTECTED]: tags 337176 moreinfo Bug#337176: initramfs-tools: initrd unusable on amd64 There were no tags set. Tags added: moreinfo tags 337607 moreinfo Bug#337607: initramfs-tools: Boot scripts tries to use evms_activate (and mdrun?), which isn't inside initrd.img 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 Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Impossible to find CD-ROM using sata drivers
Dear all, I am new to Debian and welcome your kind help. I bought a new laptop to install free software from top to bottom. Debian SID installs fine, except the DVD. $lscpi :00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 04) :00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 04) :00:1b.0 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04) :00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04) :00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04) :00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 04) :00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 04) :00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 04) :00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d4) :00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 04) :00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 04) :00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 04) :01:03.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 02) :01:07.0 Network controller: Intel Corporation PRO/Wireless 2915ABG MiniPCI Adapter (rev 05) :01:0a.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) :01:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) :03:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce Go 6600] (rev a2) 10 PC card Cardbus Controller (rev 02) :01:07.0 Network controller: Intel Corporation PRO/Wireless 2915ABG MiniPCI Adapter (rev 05) :01:0a.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) :01:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) :03:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce Go 6600] (rev a2) $lshw cebop description: Notebook product: 255/259 Series vendor: American Megatrends Inc width: 32 bits capabilities: smbios-2.3 dmi-2.3 configuration: boot=normal chassis=notebook uuid=00020003-0004-0005-0006-000700080009 *-core description: Motherboard product: 255/259 Series vendor: American Megatrends Inc physical id: 0 *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 2.00 (06/06/2005) size: 64KB capacity: 448KB capabilities: isa pci pnp apm upgrade shadowing escd cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb ls120boot zipboot biosbootspecification *-cpu description: CPU product: Intel(R) Pentium(R) M processor 1.86GHz vendor: Intel Corp. physical id: 4 bus info: [EMAIL PROTECTED] version: 6.13.8 slot: CPU 1 size: 1862MHz capacity: 1862MHz width: 32 bits clock: 532MHz capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx est tm2 *-cache:0 description: L1 cache physical id: 5 slot: L1-Cache size: 32KB capacity: 32KB capabilities: pipeline-burst internal varies data *-cache:1 description: L2 cache physical id: 6 slot: L2-Cache size: 2MB capacity: 2MB capabilities: pipeline-burst internal varies unified *-cache:2 DISABLED description: L3 cache physical id: 7 slot: L3-Cache capabilities: internal *-memory description: System Memory physical id: 29 slot: System board or motherboard size: 1GB *-bank:0 description: DIMM DDR Synchronous product: PartNum0 vendor: Manufacturer0 physical id: 0 serial: SerNum0 slot: DIMM0 size: 512MB width: 64 bits *-bank:1 description: DIMM [empty] product: PartNum1 vendor: Manufacturer1 physical id: 1 serial: SerNum1 slot: DIMM1 *-bank:2 description: DIMM DDR Synchronous product: PartNum2 vendor: Manufacturer2
Preparing 2.6.15 - i386: drop M386 support in favour of M486?
Hi all, we should start making 2.6.15-rc ready in experimental, so we can again upload the final version the same day upstream releases, and maybe do it in time through the NEW queue this time. But before that, every arch maintainer needs to check their configs and maybe rediff some (now commented out) patches. For the start, the orig tarball for 2.6.15-rc4 is at http://people.debian.org/~fs/linux-2.6_2.6.14+2.6.15-rc4.orig.tar.gz I have the amd64 configs in sync, and would like to upload a first try to experimental. Unfortunately, I cannot upload amd64 binaries to the archive yet, so I worked on the i386 parts too. This leads us to the following problem: The 386 flavour used to have CONFIG_M386 set, wich currently fails to build due to missing CONFIG_X86_CMPXCHG (which is !M386), which in turn is needed for example by ACPI. Currently the 386 flavour breaks after some warnings about this. I wonder why we don't drop M386 support at all, and switch to M486? The alternative would be investigate the changes and fix all concerned code, which I sincerely don't have the time to do. Current post-sarge kernels won't work on real i386 systems anyway, since we dropped x86-i486_emu.dpatch. So, what shall we do? Best regards Frederik Schueler -- ENOSIG signature.asc Description: Digital signature
Bug#340344: yaird: Fail to create initrd on s390/s390x
On Thu, Dec 01, 2005 at 12:03:58PM +0100, Ivan Warren wrote: 1) Hardware.pm was missing load CcwDev and load CcwMap (easy fix) Oops, thanks for the fix, is in the repo now. 2) The initramfs gets built : OK, looks normal. 3) Boot fails : Device /sys/block/dasda/dev seems to be down. Debugging opportunity, type ^D to continue. So there's something extra we need to figure out ... Possible explanation : dasd_mod won't autodetect dasds unless specifically requested to do so ! Apparently, the appropriate parameter would be : dasd=autodetect (based on drivers/s390/block/dasd_devmap.c) Possibly. If you do echo options dasd_mod /etc/modprobe.d/test123 and rerun yaird, the parameter should be added to the image (you can see this happening in the -v and -d output) However, I'm curious why this would be necessary now and not for your old kernel. Lets see if we can get this to work without needing changes to your modprobe configuration. If I'm correct, you're running under 2.6.11 with initrd-tools, trying to get 2.6.14 to boot with yaird. Could you extract the /sbin/init script from a 2.6.11 initrd and post it? If it's convenient to place the whole content of initrd somewhere online that could also be usefull, but mostly i'm after the /sbin/init. Is there any difference in kernel command line parameters when booting? However, this would mean guaranteed failure on some dasd configuration changes (this requires a small explanation of the S/390 and z/Arch I/O architecture : Each device is known by 2 ids : A subchannel number and a device number. The device number represents the 'physical' connection (ex : 010A means device 0A on channel 01).. The subchannel number is a sequence number in the configuration, and *THAT* is what is used to perform I/O operations (a device cannot be addressed directly by its device number - ONLY by its subchannel number).. Furthermore, any autodetection scheme would most probably use that subchannel numbering to name devices (or more exactly to assign minor numbers). If 0108 is your 1st dasd device it will most probably be named 'dasda'.. If a new dasd is inserted at 0100, chances are 0108 will now be called 'dasdb' - *however* if dasd_mod is passed a specific list of dasd devices, the naming will probably remain unchanged - regardless of any configuration change - the 1st device listed will be named 'dasda'). The sequence numbering is also model dependent. on IBM real iron, they are usually related to the order in which they appear in the IOCDS (a microcode configuration file that describes the system's I/O configuration). On z/VM (IBM's virtualization solution) the numbering is related to the order in which the devices are declared in the CP directory (The virtual machines definition file). On hercules (an open source S/370, S/390 and z/Arch emulator, which I am using for these tests) the subchannels are numbered based on the order in which they appear in the hercules configuration file... However, the architecture makes *NO* guarantee whatsoever as to the actual order and even whether that number remains identical between each POR (Power On Reset) - The only architectural guarantee is that the numbering is contiguous (no holes). There's a known issue that if the hardware changes, the yaird image will not automatically cope with that. However, for the case you describe the path in /sys/devices may change, but the path in /sys/block should remain stable. Otherwise your initrd would need to use /dev/disk/by-label/ to boot reliably, and I don't think support for that is in initrd-tools. For now, lets look at differences between initrd and yaird-generated image, and keep the sequence numbering in mind as a possible alternative lead. Thanks, Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Impossible to find CD-ROM using sata drivers
Sorry, dmesg was missing : dmesg Linux version 2.6.14-2-686 (Debian 2.6.14-4) ([EMAIL PROTECTED]) (gcc version 4.0.3 2005 (prerelease) (Debian 4.0.2-4)) #1 Sat Nov 26 13:10:11 UTC 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e - 0010 (reserved) BIOS-e820: 0010 - 3ffd (usable) BIOS-e820: 3ffd - 3ffde000 (ACPI data) BIOS-e820: 3ffde000 - 4000 (ACPI NVS) BIOS-e820: e000 - f000 (reserved) BIOS-e820: fed13000 - fed1a000 (reserved) BIOS-e820: fed1c000 - fed2 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: fff8 - 0001 (reserved) 127MB HIGHMEM available. 896MB LOWMEM available. found SMP MP-table at 000ff780 On node 0 totalpages: 262096 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 225280 pages, LIFO batch:31 HighMem zone: 32720 pages, LIFO batch:15 DMI 2.3 present. Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: TEMPLATE Product ID: ETEMPLATEAPIC at: 0xFEE0 Processor #0 6:13 APIC version 20 I/O APIC #1 Version 32 at 0xFEC0. Enabling APIC mode: Flat. Using 1 I/O APICs Processors: 1 Allocating PCI resources starting at 5000 (gap: 4000:a000) Built 1 zonelists Kernel command line: root=/dev/sda1 ro acpi=off mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 1867.328 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1034548k/1048384k available (1875k kernel code, 13000k reserved, 536k data, 180k init, 130880k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 3737.05 BogoMIPS (lpj=1868526) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: afe9fbff 0010 0180 CPU: After vendor identify, caps: afe9fbff 0010 0180 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 2048K CPU: After all inits, caps: afe9fbff 0010 0040 0180 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. mtrr: v2.0 (20020519) CPU: Intel(R) Pentium(R) M processor 1.86GHz stepping 08 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. ENABLING IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=0 checking if image is initramfs... it is Freeing initrd memory: 1085k freed softlockup thread 0 started up. NET: Registered protocol family 16 PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=3 PCI: Using configuration type 1 ACPI: Subsystem revision 20050902 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled PnPBIOS: Scanning system for PnP BIOS support... PnPBIOS: Found PnP BIOS installation structure at 0xc00f52a0 PnPBIOS: PnP BIOS version 1.0, entry 0xf:0x625a, dseg 0xf PnPBIOS: Missing SMALL_TAG_ENDDEP tag PnPBIOS: 14 nodes reported by PnP BIOS; 14 recorded by driver PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) PCI: Ignoring BAR0-3 of IDE controller :00:1f.2 Boot video device is :03:00.0 PCI: Transparent bridge - :00:1e.0 PCI: Discovered primary peer bus ff [IRQ] PCI: Using IRQ router PIIX/ICH [8086/2641] at :00:1f.0 PCI-APIC IRQ transform: :00:01.0[A] - IRQ 129 PCI-APIC IRQ transform: :00:1b.0[A] - IRQ 129 PCI-APIC IRQ transform: :00:1d.0[A] - IRQ 161 PCI-APIC IRQ transform: :00:1d.1[B] - IRQ 153 PCI-APIC IRQ transform: :00:1d.2[C] - IRQ 145 PCI-APIC IRQ transform: :00:1d.3[D] - IRQ 129 PCI-APIC IRQ transform: :00:1d.7[A] - IRQ 161 PCI-APIC IRQ transform: :00:1f.2[B] - IRQ 153 PCI-APIC IRQ transform: :00:1f.3[B] - IRQ 153 PCI-APIC IRQ transform: :03:00.0[A] - IRQ 129 PCI-APIC IRQ transform: :01:03.0[A] - IRQ 137 PCI-APIC IRQ transform: :01:07.0[A] - IRQ 153 PCI-APIC IRQ transform: :01:0a.0[A] - IRQ 145 PCI-APIC IRQ transform: :01:0c.0[A] - IRQ 153 pnp: 00:0a: ioport range 0x4d0-0x4d1 has been reserved pnp: 00:0a: ioport range 0xcf8-0xcff could not be reserved pnp: 00:0a: ioport range 0x480-0x4bf has been reserved pnp: 00:0a: ioport range 0x800-0x87f has been reserved PCI: Bridge: :00:01.0 IO window: disabled. MEM window: f4a0-feaf PREFETCH window: bfe0-dfef PCI: Bus 2, cardbus bridge:
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 01:52:34PM +0100, Sven Luther wrote:
On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote:
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote:
[...]
find /sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block
This is probably similar to the problem we had :
/sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-io/0.0002:ata-3/ide1
so instead of ignoring 0.8000:mac-io and 0.0002:ata-3, you need to
ignore 0.f300:ohare and 0.0002:ATA.
So, in /usr/lib/yaird/perl/Hardware.pm, at line 81, you need to copy one of
the two
above lines :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:mac-io$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ata-\d+$!) {
# Apple IDE bus; harmless
}
for your case, maybe something like :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA\d+$!) {
# Apple IDE bus; harmless
}
but i am no perl expert, and may have gotten the exact magic wrong.
Attached is a patch that made it match the two problematic lines:
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
With the patch applied, the initrd was successfully created, and the
kernel booted without any problems.
--
Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED]
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
78a79,81
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Another Apple bus; harmless
}
81a85,87
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA$!) {
# Apple IDE bus; harmless
}
signature.asc
Description: Digital signature
Bug#341522: Drivers for sbus devices are not included in initrd on sparc
On Thu, 1 Dec 2005, Christoph Hellwig wrote: If anyone volunteers to test the code I could look into converting sbus to the driver model. Hi Cristoph, I don't have any sbus hardware myself, but I should be able to build kernel packages including any patches you produce and we'll definitely be able to find people on d-sparc to test them out. Your effort will be greatly appreciated too. Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 11:25:34PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 01:52:34PM +0100, Sven Luther wrote: On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote: Attached is a patch that made it match the two problematic lines: /sys/devices/pci:00/:00:10.0/0.f300:ohare /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA With the patch applied, the initrd was successfully created, and the kernel booted without any problems. Thanks, applied to development repository, revno 14. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
tags 341559 + patch
thanks
On Thu, Dec 01, 2005 at 11:25:34PM +0100, Hans Ekbrand wrote:
On Thu, Dec 01, 2005 at 01:52:34PM +0100, Sven Luther wrote:
On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote:
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote:
[...]
find /sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block
This is probably similar to the problem we had :
/sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-io/0.0002:ata-3/ide1
so instead of ignoring 0.8000:mac-io and 0.0002:ata-3, you need to
ignore 0.f300:ohare and 0.0002:ATA.
So, in /usr/lib/yaird/perl/Hardware.pm, at line 81, you need to copy one of
the two
above lines :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:mac-io$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ata-\d+$!) {
# Apple IDE bus; harmless
}
for your case, maybe something like :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA\d+$!) {
# Apple IDE bus; harmless
}
but i am no perl expert, and may have gotten the exact magic wrong.
Attached is a patch that made it match the two problematic lines:
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
With the patch applied, the initrd was successfully created, and the
kernel booted without any problems.
Hehe, thanks, i guess a diff -u is prefered, but i am sure Erik and Jonas will
be able to adapt.
Friendly,
Sven Luther
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#339295: psmouse.c: Failed to reset mouse on isa0060/serio1 - works fine with 2.6.13-1-k7
Ok, I just upgraded to the latest sid and therefore also upgraded to the Linux version 2.6.14-4 of the linux-image-2.6.14-2-k7 package and for some reason the mouse does work again. Don't know whether the kernel itself or some udev or whatever fixed this problem. Attached you can the the latest dmesg, lsmod and ioports output. Kind regards, Jörg. Module Size Used by binfmt_misc11912 1 lp 12036 0 autofs419268 3 nfs 234056 7 lockd 66312 2 nfs nfs_acl 3712 1 nfs sunrpc148860 4 nfs,lockd,nfs_acl ipv6 267136 10 tsdev 7616 0 snd_cmipci 34912 3 snd_pcm92360 1 snd_cmipci snd_page_alloc 11016 1 snd_pcm snd_opl3_lib 11008 1 snd_cmipci snd_timer 24836 2 snd_pcm,snd_opl3_lib snd_hwdep 9248 1 snd_opl3_lib snd_mpu401_uart 7424 1 snd_cmipci snd_rawmidi25504 1 snd_mpu401_uart snd_seq_device 8844 2 snd_opl3_lib,snd_rawmidi snd55972 14 snd_cmipci,snd_pcm,snd_opl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_rawmidi,snd_seq_device soundcore 9824 1 snd parport_pc 36932 1 parport37192 2 lp,parport_pc dm_mod 60988 0 rtc12664 0 i810 23872 0 usbhid 39392 0 usbmouse5504 0 floppy 63620 0 pcspkr 3488 0 mga68352 0 drm74068 2 i810,mga amd_k7_agp 9036 1 agpgart35656 2 drm,amd_k7_agp ide_cd 43780 0 cdrom 40800 1 ide_cd uhci_hcd 33104 0 usbcore 127296 4 usbhid,usbmouse,uhci_hcd ac97_codec 20108 0 via686a17736 0 w83781d34340 0 hwmon_vid 2688 1 w83781d i2c_isa 4800 2 via686a,w83781d i2c_viapro 8208 0 i2c_core 4 4 via686a,w83781d,i2c_isa,i2c_viapro thermal13448 0 processor 22780 1 thermal button 6544 0 ac 4740 0 gameport 15112 1 snd_cmipci sis900 22464 0 mii 5696 1 sis900 ext3 143816 1 jbd56532 1 ext3 mbcache 9284 1 ext3 ide_disk 18944 3 ide_generic 1280 0 [permanent] generic 4484 0 [permanent] via82cxxx 13788 0 [permanent] ide_core 130908 5 ide_cd,ide_disk,ide_generic,generic,via82cxxx evdev 9664 0 mousedev 11680 1 psmouse39492 0 Linux version 2.6.14-2-k7 (Debian 2.6.14-4) ([EMAIL PROTECTED]) (gcc version 4.0.3 2005 (prerelease) (Debian 4.0.2-4)) #1 Sat Nov 26 14:04:05 UTC 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 1ffec000 (usable) BIOS-e820: 1ffec000 - 1ffef000 (ACPI data) BIOS-e820: 1ffef000 - 1000 (reserved) BIOS-e820: 1000 - 2000 (ACPI NVS) BIOS-e820: - 0001 (reserved) 0MB HIGHMEM available. 511MB LOWMEM available. On node 0 totalpages: 131052 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 126956 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 DMI 2.3 present. ACPI: RSDP (v000 ASUS ) @ 0x000f6ac0 ACPI: RSDT (v001 ASUS A7M266 0x30303031 MSFT 0x31313031) @ 0x1ffec000 ACPI: FADT (v001 ASUS A7M266 0x30303031 MSFT 0x31313031) @ 0x1ffec080 ACPI: DSDT (v001 ASUS A7M266 0x1000 MSFT 0x010b) @ 0x ACPI: PM-Timer IO Port: 0xe408 Allocating PCI resources starting at 3000 (gap: 2000:dfff) Built 1 zonelists Kernel command line: BOOT_IMAGE=Linux ro root=302 acpi=on apm=off pci=routeirq Local APIC disabled by BIOS -- you can enable it with lapic mapped APIC to d000 (01402000) Initializing CPU#0 PID hash table entries: 2048 (order: 11, 32768 bytes) Detected 1533.541 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 514900k/524208k available (1868k kernel code, 8776k reserved, 543k data, 180k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 3068.86 BogoMIPS (lpj=1534434) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM
