Bug#293569: Wet, hot and just 18
Give all your mates locker room envy when they see how many inches youve gained. http://www.Pleentoful.com/ Too hot to handle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: Pink and wet
Don't believe the liars - Size DOES matter http://www.Reventeoni.com/ Miracle enhancement formula -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: Smaller than you would like to be
What women REALLY want in their man find out here. http://www.tiahtpa.com/ Molly loves it huge -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: average abbey anglicanism
Get Prescirptions and Medciations while you still can! http://babbleatlanta.abbott%2Eicoraun.com but averageabbey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: abusive adsorbate
Aquire Prescriptoins while you still can! www.abbreviateallen.asteroidal%2Etableget.com a azaleaanonymity abusive it's adsorbate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: Investors report
http://imagecloset.com/uimages/cqs1176820447l.gif He is the man we want. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: kernel-image-2.6.8-2-686-smp incorectly tries to load megaraid2 on a 2.6 kernel
On Mon, Jun 06, 2005 at 03:43:26PM +0200, Bart Verwilst wrote: > I'm having this issue too.. We're switching from Gentoo to Debian 3.1 in the > datacenter, and all our servers are Dell's, mostly 1850's.. We want to use > kernel 2.6 instead of 2.4, but this is not possible for now.. Isn't this a RC > bug for Debian 3.1? I have to say I am a bit confused by this issue. Which driver should be loaded? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569:
On Mon, Jun 06, 2005 at 05:47:32PM +0200, Bart Verwilst wrote: > I tried installing the 2.6.11-1-386 from unstable, it failed to boot too.. It hasn't been released yet (probably should fix that), but you can test a pre-release build at http://debian.vergenet.net/testing/kernel-image-2.6.11-i386/ The version in question is 2.6.11-5.hls.2005052700 which is a build from SVN on the date indicated. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: kernel-image-2.6.8-2-686-smp incorectly tries to load megaraid2 on a 2.6 kernel
Hi, Still nothing.. I installed this kernel, added scsi_mod and megaraid to /etc/mkinitrd/modules.. Still doesn't boot.. Any more ideas? Op maandag 6 juni 2005 19:30, schreef u: > Horm put up some test images a couple of days ago at > > http://debian.vergenet.net/testing/ > The debian version is 5.hls.2005052700 > > You might want to try those, as they have the MEGARAID_NEWGEN drivers > compiled into the kernel. > > They work for booting my 2850. > > Best. > > Satadru
Bug#293569:
I tried installing the 2.6.11-1-386 from unstable, it failed to boot too.. Op maandag 06 juni 2005 16:47, schreef Satadru Pramanik: > afaik, this is patched for 2.6.11 is debian svn... > -Original Message- > From: Bart Verwilst <[EMAIL PROTECTED]> > Date: Monday, Jun 6, 2005 9:53 am > Subject: Bug#293569: kernel-image-2.6.8-2-686-smp incorectly tries to load > megaraid2 on a 2.6 kernel > > I'm having this issue too.. We're switching from Gentoo to Debian 3.1 in > the datacenter, and all our servers are Dell's, mostly 1850's.. We want to > use kernel 2.6 instead of 2.4, but this is not possible for now.. Isn't > this a RC bug for Debian 3.1? > > Kind regards, > > Bart -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569:
afaik, this is patched for 2.6.11 is debian svn... -Original Message- From: Bart Verwilst <[EMAIL PROTECTED]> Date: Monday, Jun 6, 2005 9:53 am Subject: Bug#293569: kernel-image-2.6.8-2-686-smp incorectly tries to load megaraid2 on a 2.6 kernel I'm having this issue too.. We're switching from Gentoo to Debian 3.1 in the datacenter, and all our servers are Dell's, mostly 1850's.. We want to use kernel 2.6 instead of 2.4, but this is not possible for now.. Isn't this a RC bug for Debian 3.1? Kind regards, Bart -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: kernel-image-2.6.8-2-686-smp incorectly tries to load megaraid2 on a 2.6 kernel
I'm having this issue too.. We're switching from Gentoo to Debian 3.1 in the datacenter, and all our servers are Dell's, mostly 1850's.. We want to use kernel 2.6 instead of 2.4, but this is not possible for now.. Isn't this a RC bug for Debian 3.1? Kind regards, Bart -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: Add megaraid to /etc/mkinitrd/modules doesn't work out
Martin Alain Kretschek writes: Hi Horms, Some more background... The machines I'm trying to install the 2.6.8-2-686-smp Debian kernel package are Dell PowerEdge 1850 with a PERC 4e/Si RAID Controller model with one Hitachi 73,2GB SCSI Ultra320 HotSwap HD factory configured in RAID0. I have almost the same configuration on the same machine, except 2 36Gb drives in RIAD1, Dell 1850 same as you. I had also tried adding scsi_mod and megariad, in both orders to the initrd/modules, and only got kernel panics for my trouble. I ahd begun the "building a custom kernel" process, but its about on the limit of my debian-fu, so I'll run with 2.4.27-smp for now. I will continue with my attempts to get 2.6 to work, as I need a 2.6 kernel for later this month on a project. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: Add megaraid to /etc/mkinitrd/modules doesn't work out
Hi Horms, Some more background... The machines I'm trying to install the 2.6.8-2-686-smp Debian kernel package are Dell PowerEdge 1850 with a PERC 4e/Si RAID Controller model with one Hitachi 73,2GB SCSI Ultra320 HotSwap HD factory configured in RAID0. I have used the sarge_i386_netinst.iso serial 20050127 to install the machines and the installer 2.6.8 kernel image (linux26 or expert26) fails to detect the disk (RAID controller) then I've installed the machine with the kernel 2.4.27 image (linux or expert), this installer image succeed to detect de RAID controller using the megaraid2 driver correcting the problem mentioned on http://lists.debian.org/debian-boot/2004/11/msg00742.html Then I've choosed to install the 2.6.8-2-i386 kernel image of the installer and got the 'kernel panic', so I've re-installed the machine using both kernel 2.4.27 images to detect de RAID to install and the installation kernel. And finally got the same problem reported by Robin when trying to install the 2.6.8-2-686-smp kernel image 2.6.8-13 release after the machine was booted with 2.4.27-2-686-smp kernel image. I have done the tests you suggested with *no* success, so let's go to the results and logs: BEFORE actions: ~# cat /etc/mkinitrd/modules # /etc/mkinitrd/modules: Kernel modules to load for initrd. # # This file should contain the names of kernel modules and their arguments # (if any) that are needed to mount the root file system, one per line. # Comments begin with a `#', and everything on the line after them are ignored. # # You must run mkinitrd(8) to effect this change. # # Examples: # # ext2 # wd io=0x300 scsi_mod megaraid ~# ~# mount /boot/initrd.img-2.6.8-2-686-smp /mnt/ -o ro,loop ~# cat /mnt/loadmodules modprobe -k scsi_mod modprobe -k megaraid modprobe -k vesafb > /dev/null 2>&1 modprobe -k fbcon 2> /dev/null modprobe -k unix 2> /dev/null modprobe -k megaraid2 modprobe -k sd_mod Booted the machine and got the kernel panic. Then I've decided to do another test adding the sd_mod to put the modules in the same subset order the mkinitrd do when we don't have modules in the /etc/mkinitrd/modules file. -- Without modules in the /etc/mkinitrd/modules the mkinitrd does, it seems to do not need scsi_mod: modprobe -k vesafb > /dev/null 2>&1 modprobe -k fbcon 2> /dev/null modprobe -k unix 2> /dev/null modprobe -k megaraid2 modprobe -k sd_mod -- BEFORE actions: ~# cat /etc/mkinitrd/modules # /etc/mkinitrd/modules: Kernel modules to load for initrd. # # This file should contain the names of kernel modules and their arguments # (if any) that are needed to mount the root file system, one per line. # Comments begin with a `#', and everything on the line after them are ignored. # # You must run mkinitrd(8) to effect this change. # # Examples: # # ext2 # wd io=0x300 scsi_mod megaraid sd_mod engel:~# dpkg -i /mirrors/debian/pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-686-smp_2.6.8-13_i386.deb Selecionando pacote previamente não selecionado kernel-image-2.6.8-2-686-smp. (Lendo banco de dados ... 23139 arquivos e diretórios atualmente instalados.) Descompactando kernel-image-2.6.8-2-686-smp (de .../kernel-image-2.6.8-2-686-smp_2.6.8-13_i386.deb) ... Instalando kernel-image-2.6.8-2-686-smp (2.6.8-13) ... /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed FATAL: Module megaraid2 not found. WARNING: This failure MAY indicate that your kernel will not boot! but it can also be triggered by needed modules being compiled into the kernel. /initrd.img does not exist. Installing from scratch, eh? Or maybe you don't want a symbolic link here. Hmm? Lets See. /vmlinuz does not exist. Installing from scratch, eh? Or maybe you don't want a symbolic link here. Hmm? Lets See. Searching for GRUB installation directory ... found: /boot/grub . Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . Searching for splash image... none found, skipping... Found kernel: /vmlinuz-2.6.8-2-686-smp Found kernel: /vmlinuz-2.4.27-2-686-smp Updating /boot/grub/menu.lst ... done ~# mount /boot/initrd.img-2.6.8-2-686-smp /mnt/ -o ro,loop ~# cat /mnt/loadmodules modprobe -k scsi_mod modprobe -k megaraid modprobe -k sd_mod modprobe -k vesafb > /dev/null 2>&1 modprobe -k fbcon 2> /dev/null modprobe -k unix 2> /dev/null modprobe -k megaraid2 Then we've got again the kernel panic. I have no logs because the kernel doesn't mount anything so I 'hand paste' what we got from the screen, it is also not possible to page up the screen because the machine freezes. ... ACPI: (supports S0 S4 S5) RAMDISK: cramfs filesystem found at block 0 RAMDISK: Loading 4688 blocks [1 disk] into ram disk... done. VFS: Mounted root (cramfs filesystem) readonly. Freeing unused kernel memory: 168k freed initrd-tools: 0.1.77 SCSI subsystem initiailized vesafb: probe of vesafb0 failed with error -6 NET: Registered protocol family 1 FATAL: Module megraid2 not found. SGI XFS with ACLs, security attributes, realtime, large b
Bug#293569: Add megaraid to /etc/mkinitrd/modules doesn't work out
On Tue, Feb 08, 2005 at 11:07:04AM -0200, Martin Alain Kretschek wrote: > Hi, > > I've tried to add megaraid to /etc/mkinitrd/modules but still doesn't work out > > I've modified the /etc/mkinitrd/modules as sugested by Horms... > > ~# cat /etc/mkinitrd/modules > # /etc/mkinitrd/modules: Kernel modules to load for initrd. > # > # This file should contain the names of kernel modules and their arguments > # (if any) that are needed to mount the root file system, one per line. > # Comments begin with a `#', and everything on the line after them are > ignored. > # > # You must run mkinitrd(8) to effect this change. > # > # Examples: > # > # ext2 > # wd io=0x300 > megaraid > > Then I've installed the kernel-package for 686-smp (I used my > machine's mirror (apt-move generated) to avoid new dowload, I've > checkeout and this is the last kernel-image package available): > > ~# dpkg -i > /mirrors/debian/pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-686-smp_2.6.8-13_i386.deb > Selecting previously deselected package kernel-image-2.6.8-2-686-smp. > (Reading database ... 23224 files and directories currently installed.) > Unpacking kernel-image-2.6.8-2-686-smp (from > .../kernel-image-2.6.8-2-686-smp_2.6.8-13_i386.deb) ... > Setting up kernel-image-2.6.8-2-686-smp (2.6.8-13) ... > /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed > FATAL: Module megaraid2 not found. > WARNING: This failure MAY indicate that your kernel will not boot! > but it can also be triggered by needed modules being compiled into > the kernel. > Searching for GRUB installation directory ... found: /boot/grub . > Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . > Searching for splash image... none found, skipping... > Found kernel: /vmlinuz-2.6.8-2-686-smp > Found kernel: /vmlinuz-2.4.27-2-686-smp > Updating /boot/grub/menu.lst ... done > > So I've checked out mkinitrd works as expected: > > ~# mount /boot/initrd.img-2.6.8-2-686-smp /mnt/ -o ro,loop > ~# cat /mnt/loadmodules > modprobe -k megaraid > modprobe -k vesafb > /dev/null 2>&1 > modprobe -k fbcon 2> /dev/null > modprobe -k unix 2> /dev/null > modprobe -k megaraid2 > modprobe -k sd_mod > ~# cat /mnt/linuxrc.conf > DELAY=0 > BUSYBOX= > FSTYPES=ext3,ext2,xfs,cramfs > IDE_CORE=ide-mod > VERSION=0.1.77 > > Maybe the problem is the order of modules on loadmodules as we can see > on loadmodules file megaraid is the first module and it should be just > before megaraid2 (that won't load because it doesn't exist on kernel > 2.6.8) is this correct or the order doesn't matter? I don't think the order is that important. Though perhaps megaraid doesn't support your card, or perhaps it needs something else. Ok, I just checked, yes, it seems to need scsi_mod. scsi_mod doesn't seem to need anything else. So could you try adding scsi_mod before megaraid in /etc/mkinitrd/modules > > Then I've boot the machine and get the expected "Kernel Panic". Bother. If it fails again could you please paste the boot log like you did in your original post? That information is often quite useful. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: Add megaraid to /etc/mkinitrd/modules doesn't work out
Hi, I've tried to add megaraid to /etc/mkinitrd/modules but still doesn't work out I've modified the /etc/mkinitrd/modules as sugested by Horms... ~# cat /etc/mkinitrd/modules # /etc/mkinitrd/modules: Kernel modules to load for initrd. # # This file should contain the names of kernel modules and their arguments # (if any) that are needed to mount the root file system, one per line. # Comments begin with a `#', and everything on the line after them are ignored. # # You must run mkinitrd(8) to effect this change. # # Examples: # # ext2 # wd io=0x300 megaraid Then I've installed the kernel-package for 686-smp (I used my machine's mirror (apt-move generated) to avoid new dowload, I've checkeout and this is the last kernel-image package available): ~# dpkg -i /mirrors/debian/pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-686-smp_2.6.8-13_i386.deb Selecting previously deselected package kernel-image-2.6.8-2-686-smp. (Reading database ... 23224 files and directories currently installed.) Unpacking kernel-image-2.6.8-2-686-smp (from .../kernel-image-2.6.8-2-686-smp_2.6.8-13_i386.deb) ... Setting up kernel-image-2.6.8-2-686-smp (2.6.8-13) ... /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed FATAL: Module megaraid2 not found. WARNING: This failure MAY indicate that your kernel will not boot! but it can also be triggered by needed modules being compiled into the kernel. Searching for GRUB installation directory ... found: /boot/grub . Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . Searching for splash image... none found, skipping... Found kernel: /vmlinuz-2.6.8-2-686-smp Found kernel: /vmlinuz-2.4.27-2-686-smp Updating /boot/grub/menu.lst ... done So I've checked out mkinitrd works as expected: ~# mount /boot/initrd.img-2.6.8-2-686-smp /mnt/ -o ro,loop ~# cat /mnt/loadmodules modprobe -k megaraid modprobe -k vesafb > /dev/null 2>&1 modprobe -k fbcon 2> /dev/null modprobe -k unix 2> /dev/null modprobe -k megaraid2 modprobe -k sd_mod ~# cat /mnt/linuxrc.conf DELAY=0 BUSYBOX= FSTYPES=ext3,ext2,xfs,cramfs IDE_CORE=ide-mod VERSION=0.1.77 Maybe the problem is the order of modules on loadmodules as we can see on loadmodules file megaraid is the first module and it should be just before megaraid2 (that won't load because it doesn't exist on kernel 2.6.8) is this correct or the order doesn't matter? Then I've boot the machine and get the expected "Kernel Panic". -- Martin Alain Kretschek e-mail: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: kernel-image-2.6.8-2-686-smp incorectly tries to load megaraid2 on a 2.6 kernel
reassign 293569 initrd-tools On Fri, Feb 04, 2005 at 12:56:46PM +, [EMAIL PROTECTED] wrote: > Package: kernel-image-2.6.8-2-686-smp > Version: 2.6.8-2 > Severity: important > Justification: prevents boot > > The package runs mkinitrd to build an initial ramdisk > The hardware is using the Dell 'megaraid' controller which was supported as > megaraid2 under the 2.4 series kernels. > mkinitrd probes the root and finds megaraid2 and add the line to > loadmodules in the initrd: > > modprobe -k vesafb > /dev/null 2>&1 > modprobe -k fbcon 2> /dev/null > modprobe -k unix 2> /dev/null > modprobe -k megaraid2 > modprobe -k sd_mod > > the version of the megaraid module shipped with the 2.6 kernel is v2, and > should support the controller just fine Hi Robin, The name of this module changed from megaraid2 to megaraid for 2.6 as far as I can see. Unfortunately the tool the generates the ramdisk doesn't know how to work this out. Actually, I don't think we know how it could work this out, short of puting everything pluss the kitchen sink into the initrd image. Could you please try adding megaraid to /etc/mkinitrd/modules and rebuilding the intird image using mkinitrd on the command line. This will likely result in an ininitrd image that tries to modprobe megaraid2 and megaraid, but only the latter will succeede as only it will be inculded in the initrd image as only it exists in 2.6. Hopefully this will allow your system to boot. I have reassigned this bug to initrd-tools as the problem seems to lie there rather than with the kernel image itself. > running mkinitrd: > > uk2a:/home/robin# mkinitrd -o /tmp/initrd.img 2.6.8-2-686-smp > /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed > FATAL: Module megaraid2 not found. > WARNING: This failure MAY indicate that your kernel will not boot! > but it can also be triggered by needed modules being compiled into > the kernel. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#293569: kernel-image-2.6.8-2-686-smp incorectly tries to load megaraid2 on a 2.6 kernel
Package: kernel-image-2.6.8-2-686-smp Version: 2.6.8-2 Severity: important Justification: prevents boot The package runs mkinitrd to build an initial ramdisk The hardware is using the Dell 'megaraid' controller which was supported as megaraid2 under the 2.4 series kernels. mkinitrd probes the root and finds megaraid2 and add the line to loadmodules in the initrd: modprobe -k vesafb > /dev/null 2>&1 modprobe -k fbcon 2> /dev/null modprobe -k unix 2> /dev/null modprobe -k megaraid2 modprobe -k sd_mod the version of the megaraid module shipped with the 2.6 kernel is v2, and should support the controller just fine running mkinitrd: uk2a:/home/robin# mkinitrd -o /tmp/initrd.img 2.6.8-2-686-smp /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed FATAL: Module megaraid2 not found. WARNING: This failure MAY indicate that your kernel will not boot! but it can also be triggered by needed modules being compiled into the kernel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
