Re: Linux 2.4.0 root fs problem (*help*, *help*)
Sven - who is desparate to run 2.4.0 # # Multi-device support (RAID and LVM) # CONFIG_MD=y # CONFIG_BLK_DEV_MD is not set # CONFIG_MD_LINEAR is not set # CONFIG_MD_RAID0 is not set # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID5 is not set CONFIG_BLK_DEV_LVM=y CONFIG_LVM_PROC_FS=y try to leave this out ... ? greetings, martin
RE: Linux 2.4.0 root fs problem
This guy is in deep trouble guys, try helping him out ... Apperently i couldn't help him -Original Message- From: Patrick Cheong Shu Yang [mailto:[EMAIL PROTECTED] Sent: Friday, January 12, 2001 2:12 AM To: debian-user@lists.debian.org Subject: Re: Linux 2.4.0 root fs problem On Thu, Jan 11, 2001 at 04:42:02PM -0500, David B. Harris wrote: To quote Pollywog [EMAIL PROTECTED], # I wonder why this is even an option; is there a reason anyone would # install Linux without ext2 support? # I have always wondered why the option was given. ReiserFS/ext3: Some people run ReiserFS or ext3, so they don't need ext2 support built into the kernel. I am one of those personsI am running a HP SCSI-based machine in a production environment for web- and e-mail-hosting purposes and I have compiled (2.2.17) with reiserfs builtin and ext2 as a module...just in case.
Re: Linux 2.4.0 root fs problem
» Joris Lambrecht said this and I say that: This guy is in deep trouble guys, try helping him out ... Apperently i couldn't help him Count me in this trouble too. My guess is that it's something about modules - I compiled two 2.4 test12 kernels - one of them had _almost_ everything as modules (except for ext2 support and other fundamental things), the other one had everything built-in. The first had the same problem - with an IDE device - and the other one worked fine. Should it be a kernel bug? On Thu, Jan 11, 2001 at 04:42:02PM -0500, David B. Harris wrote: To quote Pollywog [EMAIL PROTECTED], # I wonder why this is even an option; is there a reason anyone would # install Linux without ext2 support? # I have always wondered why the option was given. ReiserFS/ext3: Some people run ReiserFS or ext3, so they don't need ext2 support built into the kernel. I am one of those personsI am running a HP SCSI-based machine in a production environment for web- and e-mail-hosting purposes and I have compiled (2.2.17) with reiserfs builtin and ext2 as a module...just in case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Abracos e briagdeiros, francisco m. neto (a.k.a ikari himura keiichi) Linux User #192809 ICQ #78493934 http://socrates.if.usp.br/~einstein Toke au kokoro ga, watashi o kowasu -- Ayanami Rei
Linux 2.4.0 root fs problem
Hello After having built and installed my custom linux-2.4.0-deb, I get the following when booting: [boot msgs] VFS: Cannot open root device 803 or 08:03 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 08:03 After which booting halts. $ rdev /boot/vmlinuz-2.2.18 Root device /dev/sda3 $ rdev /boot/vmlinuz-2.4.0 Root device /dev/sda3 Weird. Help, anyone? Thanks, Sven
Re: Linux 2.4.0 root fs problem
Just to clarify: On Thu, Jan 11, 2001 at 07:35:08PM +0100, Sven Burgener wrote: $ rdev /boot/vmlinuz-2.2.18 Root device /dev/sda3 (Booting with 2.2.18 works) $ rdev /boot/vmlinuz-2.4.0 Root device /dev/sda3 ... but not with 2.4.0. Thanks in advance! Sven
Re: Linux 2.4.0 root fs problem
Sven Burgener [EMAIL PROTECTED] writes: Just to clarify: On Thu, Jan 11, 2001 at 07:35:08PM +0100, Sven Burgener wrote: $ rdev /boot/vmlinuz-2.2.18 Root device /dev/sda3 (Booting with 2.2.18 works) $ rdev /boot/vmlinuz-2.4.0 Root device /dev/sda3 ... but not with 2.4.0. That's a bit strange. You did compile your 2.4.0 kernel with the appropriate SCSI driver built into the kernel, right? Gary
Re: Linux 2.4.0 root fs problem
On Thu, Jan 11, 2001 at 07:35:08PM +0100, Sven Burgener wrote: VFS: Cannot open root device 803 or 08:03 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 08:03 Did you remember to say 'yes' *not* 'module' for ext2 support in the kernel (under General Setup) and scsi disks? I once built my kernel with ext2 support as a module late one night. Needless to say, my machine was very unhappy with me. :-) bob -- bob billson email: [EMAIL PROTECTED]ham: kc2wz [EMAIL PROTECTED] Linux geek/) Níl aon tinteán mar do thinteán féin. beekeeper -8|||} --Dorothy\) Athbhliain faoi Shéan agus faoi Shona Dhuit!
Re: Linux 2.4.0 root fs problem
On Thu, Jan 11, 2001 at 12:07:00PM -0700, Gary Hennigan wrote: Sven Burgener [EMAIL PROTECTED] writes: Just to clarify: $ rdev /boot/vmlinuz-2.2.18 Root device /dev/sda3 (Booting with 2.2.18 works) $ rdev /boot/vmlinuz-2.4.0 Root device /dev/sda3 ... but not with 2.4.0. That's a bit strange. You did compile your 2.4.0 kernel with the appropriate SCSI driver built into the kernel, right? Yes, I did: $ grep '^[^#]' /boot/config-2.2.18 | grep -i scsi CONFIG_SCSI=y CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_AM53C974=y $ grep '^[^#]' /boot/config-2.4.0 | grep -i scsi CONFIG_SCSI=y CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_AM53C974=y It *is* strange, indeed. Still seeking help! Cheers, Sven
Re: Linux 2.4.0 root fs problem
On Thu, Jan 11, 2001 at 02:13:25PM -0500, Bob Billson wrote: On Thu, Jan 11, 2001 at 07:35:08PM +0100, Sven Burgener wrote: VFS: Cannot open root device 803 or 08:03 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 08:03 Did you remember to say 'yes' *not* 'module' for ext2 support in the kernel (under General Setup) and scsi disks? I simply used the configurations for my 2.2.18 kernel and then did a make oldconfig. So, yes, I did select ext2 support built-in, as I did in 2.2.18. Still seeking help! Sven
Re: Linux 2.4.0 root fs problem
Sven Burgener [EMAIL PROTECTED] writes: On Thu, Jan 11, 2001 at 02:13:25PM -0500, Bob Billson wrote: On Thu, Jan 11, 2001 at 07:35:08PM +0100, Sven Burgener wrote: VFS: Cannot open root device 803 or 08:03 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 08:03 Did you remember to say 'yes' *not* 'module' for ext2 support in the kernel (under General Setup) and scsi disks? I simply used the configurations for my 2.2.18 kernel and then did a make oldconfig. So, yes, I did select ext2 support built-in, as I did in 2.2.18. Still seeking help! Well, it's a pain but I'd go through the config the old-fashioned way, eg.: make clean make-kpkg clean make distclean make (xconfig|config|menuconfig) make-kpkg whatever Something obviously didn't get built right in your 2.4 kernel. At least I can't think of any other possible reason it can't see you're HD, especially with 2.2.18 booting fine. Gary
Re: Linux 2.4.0 root fs problem
I simply used the configurations for my 2.2.18 kernel and then did a make oldconfig. So, yes, I did select ext2 support built-in, as I did in 2.2.18. I wonder why this is even an option; is there a reason anyone would install Linux without ext2 support? I have always wondered why the option was given. -- Andrew
Re: Linux 2.4.0 root fs problem
On Thu, Jan 11, 2001 at 08:36:54PM +, Pollywog wrote: I wonder why this is even an option; is there a reason anyone would install Linux without ext2 support? I have always wondered why the option was given. In a word: choice. Before ext2 there was the original ext. Or was it called extfs? I forget. Soon there will be ext3 and others to choose from. hhmm... Can ext2 be replaced with, say, romfs for embedded apps? I'm glad Linus and the others gave us this flexibility unlike that choice-less OS ahem out there. bob -- bob billson email: [EMAIL PROTECTED]ham: kc2wz [EMAIL PROTECTED] Linux geek/) Níl aon tinteán mar do thinteán féin. beekeeper -8|||} --Dorothy\) Athbhliain faoi Shéan agus faoi Shona Dhuit!
Re: Linux 2.4.0 root fs problem
To quote Pollywog [EMAIL PROTECTED], # I wonder why this is even an option; is there a reason anyone would # install Linux without ext2 support? # I have always wondered why the option was given. A number of reasons; Embedded applications: typical embedded applications are *extremely* memory-sensitive. Every extra kilobyte of space is begrudged. Add to this that the minix FS is often used for space-constrained storage systems(like floppies, or Flash cards), if there's no need to bloat the kernel with a whole extra filesystem, then don't. ReiserFS/ext3: Some people run ReiserFS or ext3, so they don't need ext2 support built into the kernel. Dave
Re: Linux 2.4.0 root fs problem (*help*, *help*)
On Thu, Jan 11, 2001 at 01:19:41PM -0700, Gary Hennigan wrote: Well, it's a pain but I'd go through the config the old-fashioned way, eg.: make clean make-kpkg clean make distclean make (xconfig|config|menuconfig) make-kpkg whatever Something obviously didn't get built right in your 2.4 kernel. At least I can't think of any other possible reason it can't see you're HD, especially with 2.2.18 booting fine. Well, I have done just that now but the problem persists. I don't know what to do. I am attaching my .config for 2.4.0 to this mail, so that perhaps someone could point out what I might be missing. Cheers, Sven - who is desparate to run 2.4.0 # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # # CONFIG_EXPERIMENTAL is not set # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODVERSIONS is not set CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set CONFIG_M586TSC=y # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_M686FXSR is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_X86_USE_STRING_486=y CONFIG_X86_ALIGNMENT_16=y CONFIG_X86_TSC=y # CONFIG_TOSHIBA is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set CONFIG_X86_CPUID=y CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_SMP is not set # CONFIG_X86_UP_IOAPIC is not set # # General setup # CONFIG_NET=y # CONFIG_VISWS is not set CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y # CONFIG_PCI_NAMES is not set # CONFIG_EISA is not set # CONFIG_MCA is not set # CONFIG_HOTPLUG is not set # CONFIG_PCMCIA is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_PM is not set # CONFIG_APM is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play configuration # # CONFIG_PNP is not set # CONFIG_ISAPNP is not set # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_LOOP is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_BLK_DEV_INITRD is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y # CONFIG_BLK_DEV_MD is not set # CONFIG_MD_LINEAR is not set # CONFIG_MD_RAID0 is not set # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID5 is not set CONFIG_BLK_DEV_LVM=y CONFIG_LVM_PROC_FS=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_NETLINK=y CONFIG_RTNETLINK=y # CONFIG_NETLINK_DEV is not set CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y # CONFIG_IP_MULTICAST is not set CONFIG_IP_ADVANCED_ROUTER=y CONFIG_RTNETLINK=y CONFIG_NETLINK=y # CONFIG_IP_MULTIPLE_TABLES is not set # CONFIG_IP_ROUTE_MULTIPATH is not set # CONFIG_IP_ROUTE_TOS is not set # CONFIG_IP_ROUTE_VERBOSE is not set # CONFIG_IP_ROUTE_LARGE_TABLES is not set # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_INET_ECN is not set # CONFIG_SYN_COOKIES is not set # # IP: Netfilter Configuration # CONFIG_IP_NF_CONNTRACK=y CONFIG_IP_NF_FTP=y CONFIG_IP_NF_IPTABLES=y CONFIG_IP_NF_MATCH_LIMIT=y CONFIG_IP_NF_MATCH_MAC=y CONFIG_IP_NF_MATCH_MARK=y CONFIG_IP_NF_MATCH_MULTIPORT=y CONFIG_IP_NF_MATCH_TOS=y CONFIG_IP_NF_MATCH_STATE=y CONFIG_IP_NF_FILTER=y CONFIG_IP_NF_TARGET_REJECT=y CONFIG_IP_NF_NAT=y CONFIG_IP_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=y CONFIG_IP_NF_TARGET_REDIRECT=y CONFIG_IP_NF_MANGLE=y CONFIG_IP_NF_TARGET_TOS=y CONFIG_IP_NF_TARGET_MARK=y CONFIG_IP_NF_TARGET_LOG=y # # # # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_DECNET is not set # CONFIG_BRIDGE is not set # # Telephony Support # # CONFIG_PHONE is not set # CONFIG_PHONE_IXJ is not set # # ATA/IDE/MFM/RLL support # CONFIG_IDE=y # # IDE, ATA and ATAPI Block devices # CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_HD_IDE is not set # CONFIG_BLK_DEV_HD is not set CONFIG_BLK_DEV_IDEDISK=y # CONFIG_IDEDISK_MULTI_MODE is not set # CONFIG_BLK_DEV_IDEDISK_VENDOR is not set #
Re: Linux 2.4.0 root fs problem
Pollywog == Pollywog [EMAIL PROTECTED] writes: I simply used the configurations for my 2.2.18 kernel and then did a make oldconfig. So, yes, I did select ext2 support built-in, as I did in 2.2.18. Pollywog I wonder why this is even an option; is there a reason Pollywog anyone would install Linux without ext2 support? I have Pollywog always wondered why the option was given. Yes. For any system that does not require ext2... Examples: root file system is on NFS or Reiserfs or ... -- Brian May [EMAIL PROTECTED]
Re: Linux 2.4.0 root fs problem
On Thu, Jan 11, 2001 at 04:42:02PM -0500, David B. Harris wrote: To quote Pollywog [EMAIL PROTECTED], # I wonder why this is even an option; is there a reason anyone would # install Linux without ext2 support? # I have always wondered why the option was given. ReiserFS/ext3: Some people run ReiserFS or ext3, so they don't need ext2 support built into the kernel. I am one of those personsI am running a HP SCSI-based machine in a production environment for web- and e-mail-hosting purposes and I have compiled (2.2.17) with reiserfs builtin and ext2 as a module...just in case. pgpweZ5jQJgPw.pgp Description: PGP signature
