2.6.0-test3 cannot mount root fs

2.6.0-test3 cannot mount root fs

[Norbert Preining]

Hi friends!

I am trying 2.6.0-test3 but cannot get the kernel to mount /dev/hdb1
which is the root fs.

I tells me all the usual stuff concerning that it finds the controllers
(VIA and HPT) and disks/cdroms, but than hangs with
	cannot mount rootfs "NULL" or hdb1
I have compile in (of course) the filesystems of my root fs (ext3) and
everything else I thought may be necessary, or at least what has been
necessary up to 2.4.22-rc2.

hardware: athlon, via686 ide + hpt366/370 ide, linux is un hdb

here my config options for ide:
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_IDEDISK_STROKE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
CONFIG_IDE_TASKFILE_IO=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y

for FS:
CONFIG_EXT2_FS=y
CONFIG_EXT3_FS=y
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=m
CONFIG_ISO9660_FS=m
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_NTFS_FS=m
CONFIG_PROC_FS=y
CONFIG_DEVPTS_FS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_HFS_FS=m
CONFIG_CRAMFS=m

Unfortunately I cannot capture the output of the boot of 2.6.0, but I
would happily compare it to one's dmesg output. So if you have 2.6.0
running with via686 can you send me the dmesg after boot, so that I can
check what there should be or what I  am missing.

Thanks a lot

Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
WIDDICOMBE (n.)
The sort of person who impersonates trim phones.
			--- Douglas Adams, The Meaning of Liff

Re: 2.6.0-test3 cannot mount root fs

[Norbert Preining]

On Sam, 09 Aug 2003, gaxt wrote:
> Try changing in your bootloader root=/dev/hdb1 to root=341

tried it already with 
	root=0341
and 
	root=341
on the lilo prompt. No change.

(Beside the kernel telling me:
	VFS: Cannot mount root fs "341" or "hdb1"

Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
BENBURB
The sort of man who becomes a returning officer.
			--- Douglas Adams, The Meaning of Liff

2.6.0-test3 cannot mount root fs

[gaxt]

 > I am trying 2.6.0-test3 but cannot get the kernel to mount /dev/hdb1
 > which is the root fs.

Try changing in your bootloader root=/dev/hdb1 to root=341

Re: 2.6.0-test3 cannot mount root fs

[Herbert Pötzl]

On Sat, Aug 09, 2003 at 12:40:24PM +0200, Norbert Preining wrote:
> On Sam, 09 Aug 2003, gaxt wrote:
> > Try changing in your bootloader root=/dev/hdb1 to root=341
> 
> tried it already with 
> 	root=0341
> and 
> 	root=341
> on the lilo prompt. No change.
> 
> (Beside the kernel telling me:
> 	VFS: Cannot mount root fs "341" or "hdb1"

are you using devfs? if so, the devfs device name
would be apropriate root=/dev/ide/host0/bus0/target1/lun0/part1

how does the lilo config look like, and what kernel
command line is reported on boot ...

best,
Herbert

> Best wishes
> 
> Norbert

Re: 2.6.0-test3 cannot mount root fs

[Henrik Storner]

In <20030809104024.GA12316@gamma.logic.tuwien.ac.at> Norbert Preining <preining@logic.at> writes:

>On Sam, 09 Aug 2003, gaxt wrote:
>> Try changing in your bootloader root=/dev/hdb1 to root=341

>tried it already with 
>	root=0341
>and 
>	root=341
>on the lilo prompt. No change.

Did you patch up or install the full tree ? I had this problem 
when I patched 2.6.0-test1 -> 2.6.0-test2.

Rebuilding a fully downloaded source tree appears to have fixed
it for me in -test2. Will try -test3 now.
-- 
Henrik Storner <henrik@hswn.dk> 

Re: 2.6.0-test3 cannot mount root fs

[Felipe Alfaro Solana]

On Sat, 2003-08-09 at 12:40, Norbert Preining wrote:
> On Sam, 09 Aug 2003, gaxt wrote:
> > Try changing in your bootloader root=/dev/hdb1 to root=341

Justa stupid guess, but the format has been changed. Instead, try

root=03:41

Re: 2.6.0-test3 cannot mount root fs

[Mr. James W. Laferriere]

	He3llo Gaxt ,  Is this change to the lilo.conf funtionality
	documented someplace ?  It is not in the halloween-2.5 document .
		Tia ,  JimL

On Sat, 9 Aug 2003, gaxt wrote:
>  > I am trying 2.6.0-test3 but cannot get the kernel to mount /dev/hdb1
>  > which is the root fs.
> Try changing in your bootloader root=/dev/hdb1 to root=341
-- 
       +------------------------------------------------------------------+
       | James   W.   Laferriere | System    Techniques | Give me VMS     |
       | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
       | babydr@baby-dragons.com | Coudersport PA 16915 |   only  on  AXP |
       +------------------------------------------------------------------+

Re: 2.6.0-test3 cannot mount root fs

[Mr. James W. Laferriere]

	Hello Gaxt ,  I take it that there is no documentation of the
	change to the 'Kernel's 'root' parameter syntax ?  Tia ,  JimL

On Sat, 9 Aug 2003, gaxt wrote:
> It's not a lilo issue (ie. I use grub) I ran into the issue when I first
> started with the 2.6.0 series test kernels.

> Mr. James W. Laferriere wrote:
> > 	He3llo Gaxt ,  Is this change to the lilo.conf funtionality
> > 	documented someplace ?  It is not in the halloween-2.5 document .
> > 		Tia ,  JimL

> > On Sat, 9 Aug 2003, gaxt wrote:
> >> > I am trying 2.6.0-test3 but cannot get the kernel to mount /dev/hdb1
> >> > which is the root fs.
> >>Try changing in your bootloader root=/dev/hdb1 to root=341
-- 
       +------------------------------------------------------------------+
       | James   W.   Laferriere | System    Techniques | Give me VMS     |
       | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
       | babydr@baby-dragons.com | Coudersport PA 16915 |   only  on  AXP |
       +------------------------------------------------------------------+

Re: 2.6.0-test3 cannot mount root fs

[gaxt]

It's not a lilo issue (ie. I use grub) I ran into the issue when I first 
started with the 2.6.0 series test kernels.


Mr. James W. Laferriere wrote:
> 	He3llo Gaxt ,  Is this change to the lilo.conf funtionality
> 	documented someplace ?  It is not in the halloween-2.5 document .
> 		Tia ,  JimL
> 
> On Sat, 9 Aug 2003, gaxt wrote:
> 
>> > I am trying 2.6.0-test3 but cannot get the kernel to mount /dev/hdb1
>> > which is the root fs.
>>Try changing in your bootloader root=/dev/hdb1 to root=341

Re: 2.6.0-test3 cannot mount root fs

[Henrik Ræder Clausen]

----- Original Message ----- 
From: "gaxt" <gaxt@rogers.com>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>

> It's not a lilo issue (ie. I use grub) I ran into the issue when I first
> started with the 2.6.0 series test kernels.

   I had it occasionally in the 2.5.X series, as well as with 2.6.0-test2.
To me it seems like some apparently unrelated config setting causes this.
I'd go over the config again, change a few settings that seem to make
sense - but nothing obvious - then recompile and get a healthy kernel.

   I'm using Grub and ext3, for the record.


    -Henrik

DVD Problems 2.6.0-test3 & 2.6.0-test2-mm5

[gaxt]

DVDs play fine in 2.4.21 but will not play in 2.6.0-test2-mm5 or 
2.6.0-test3. With ogle, this is what spits out:

dave@localhost dave $ ogle
libdvdread: Using libdvdcss version 1.2.6 for DVD access
libdvdread: Using libdvdcss version 1.2.6 for DVD access

libdvdread: Attempting to retrieve all CSS keys
libdvdread: This can take a _long_ time, please be patient

libdvdread: Get key for /VIDEO_TS/VTS_01_0.VOB at 0x00000182
libdvdread: Error cracking CSS key for /VIDEO_TS/VTS_01_0.VOB (0x00000182)
libdvdread: Elapsed time 0
libdvdread: Get key for /VIDEO_TS/VTS_01_1.VOB at 0x00020316
libdvdread: Error cracking CSS key for /VIDEO_TS/VTS_01_1.VOB (0x00020316)!!
libdvdread: Elapsed time 0
libdvdread: Found 1 VTS's
libdvdread: Elapsed time 0
FATAL[ogle_mpeg_ps]: dvdreadblocks failed
dave@localhost dave $

I tried several DVDs and three gave the above error and one worked but I 
suspect the working one had no copy-protection encoding (low budget 
release unlike the two others: Jeeves & Wooster and Blackadder and Dirty 
Harry).

Unfortunately, I never tested DVD with the other 2.6.0 kernel releases.

Re: 2.6.0-test3 cannot mount root fs

[Norbert Preining]

Thanks to all of you for the several suggestions, but none was
successfull till now:

I tried as boot cmd line:
	s root=03:41 acpi=off
and still it didn't work. Same problem.

And I am not using devfs.

My lilo looks like this:
boot = /dev/hda2
install = /boot/boot-bmp.b
bitmap = /boot/debian-bootscreen-woody.bmp
bmp-colors=1,,0,2,,0
bmp-table=120p,173p,1,15,17
bmp-timer=254p,432p,1,0,0
read-only
prompt
timeout=100
password=""
  mandatory
vga=0x317
...
image=/boot/vmlinuz-2.6.0-test3
        label=2.6.0-test3
        append="amd_disconnect=yes"
        read-only
        restricted

Where amd_disconnect a patch is which sets a bit in the pci register to
allow the athlon to disconnect during idle, which greatly decreases my
cpu/mobo temperature. But this is not done till the place were the root
fs should have been loaded.


Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
CLUN (n.)
A leg which has gone to sleep and has to be hauled around after you.
			--- Douglas Adams, The Meaning of Liff

Re: 2.6.0-test3 cannot mount root fs

[Andrew Morton]

Norbert Preining <preining@logic.at> wrote:
>
> I tried as boot cmd line:
>  	s root=03:41 acpi=off
>  and still it didn't work. Same problem.

It is decimal.  You want 03:65.


Could you test this patch?  It should put things back to the way
they were before this mini-fisaco. root=0341 should work as well.


 init/do_mounts.c |   18 ++++++++++++------
 1 files changed, 12 insertions(+), 6 deletions(-)

diff -puN init/do_mounts.c~handle-old-dev_t-format init/do_mounts.c
--- 25/init/do_mounts.c~handle-old-dev_t-format	2003-08-09 16:15:24.000000000 -0700
+++ 25-akpm/init/do_mounts.c	2003-08-09 16:17:25.000000000 -0700
@@ -71,13 +71,19 @@ static dev_t __init try_name(char *name,
 	if (len <= 0 || len == 32 || buf[len - 1] != '\n')
 		goto fail;
 	buf[len - 1] = '\0';
-	/*
-	 * The format of dev is now %u:%u -- see print_dev_t()
-	 */
-	if (sscanf(buf, "%u:%u", &maj, &min) == 2)
+	if (sscanf(buf, "%u:%u", &maj, &min) == 2) {
+		/*
+		 * Try the %u:%u format -- see print_dev_t()
+		 */
 		res = MKDEV(maj, min);
-	else
-		goto fail;
+	} else {
+		/*
+		 * Nope.  Try old-style "0321"
+		 */
+		res = (dev_t)simple_strtoul(buf, &s, 16);
+		if (*s)
+			goto fail;
+	}
 
 	/* if it's there and we are not looking for a partition - that's it */
 	if (!part)

_

Re: 2.6.0-test3 cannot mount root fs

[Norbert Preining]

On Son, 10 Aug 2003, Andrew Morton wrote:
> > I tried as boot cmd line:
> >  	s root=03:41 acpi=off
> >  and still it didn't work. Same problem.
> 
> It is decimal.  You want 03:65.

Still no success. With acpi=off and without.


> Could you test this patch?  It should put things back to the way
> they were before this mini-fisaco. root=0341 should work as well.

Also no success.

Maybe I am stupid, but 
	make mrproper
	make distclean
	make config deb bzImage modules modules_install
should be enough to make a clean kernel? And, AFAIK, I compiled in ext3
and all other necessary stuff. Soon I give up.

Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
BEAULIEU HILL
The optimum vantage point from which one to view people undressing in
the bedroom across the street.
			--- Douglas Adams, The Meaning of Liff

Re: 2.6.0-test3 cannot mount root fs

[Herbert Pötzl]

On Mon, Aug 11, 2003 at 07:34:37AM +0200, Norbert Preining wrote:
> On Son, 10 Aug 2003, Andrew Morton wrote:
> > > I tried as boot cmd line:
> > >  	s root=03:41 acpi=off
> > >  and still it didn't work. Same problem.
> > 
> > It is decimal.  You want 03:65.
> 
> Still no success. With acpi=off and without.
> 
> 
> > Could you test this patch?  It should put things back to the way
> > they were before this mini-fisaco. root=0341 should work as well.
> 
> Also no success.
> 
> Maybe I am stupid, but 
> 	make mrproper
> 	make distclean
> 	make config deb bzImage modules modules_install
> should be enough to make a clean kernel? And, AFAIK, I compiled in ext3
> and all other necessary stuff. Soon I give up.

make config
make

should be sufficient (dep, bzImage, modules is not required)

maybe you could provide your .config?

best,
Herbert

> Best wishes
> 
> Norbert
> 
> -------------------------------------------------------------------------------
> Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
> gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
> -------------------------------------------------------------------------------
> BEAULIEU HILL
> The optimum vantage point from which one to view people undressing in
> the bedroom across the street.
> 			--- Douglas Adams, The Meaning of Liff
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.0-test3 cannot mount root fs

[Norbert Preining]

On Mon, 11 Aug 2003, Herbert Pötzl wrote:
> > Maybe I am stupid, but 
> > 	make mrproper
> > 	make distclean
> > 	make config deb bzImage modules modules_install
> > should be enough to make a clean kernel? And, AFAIK, I compiled in ext3
> > and all other necessary stuff. Soon I give up.
> 
> make config
> make

OK, I used the old way ;-)

I sent the vital parts (or the parts I thought vital) in my first email,
bu there is my current .config:

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=16
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_X86_MCE_P4THERMAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_SOFTWARE_SUSPEND is not set

#
# ACPI Support
#
CONFIG_ACPI=y
# CONFIG_ACPI_HT_ONLY is not set
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_APM is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
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_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=m

#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
# CONFIG_PARPORT_SERIAL is not set
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play support
#
# CONFIG_PNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# 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_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_LBD is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
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_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y

#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDE_TCQ is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
CONFIG_BLK_DEV_HPT366=y
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
CONFIG_BLK_DEV_PDC202XX_NEW=m
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_REPORT_LUNS is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_SYM53C8XX is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
CONFIG_NET_KEY=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_UNCLEAN=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_MIRROR=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
# CONFIG_IP_NF_NAT_LOCAL is not set
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
CONFIG_XFRM_USER=m

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=y
# CONFIG_TYPHOON is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
# CONFIG_PPP_MULTILINK is not set
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
# CONFIG_PPP_SYNC_TTY is not set
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
# CONFIG_PPPOE is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y

#
# Obsolete Wireless cards support (pre-802.11)
#
# CONFIG_STRIP is not set

#
# Wireless 802.11b ISA/PCI cards support
#
CONFIG_AIRO=m
CONFIG_HERMES=m
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
CONFIG_PCI_HERMES=m
CONFIG_NET_WIRELESS=y

#
# Token Ring devices (depends on LLC=y)
#
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1280
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1024
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
CONFIG_GAMEPORT=m
CONFIG_SOUND_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
# CONFIG_GAMEPORT_L4 is not set
CONFIG_GAMEPORT_EMU10K1=m
# CONFIG_GAMEPORT_VORTEX is not set
# CONFIG_GAMEPORT_FM801 is not set
# CONFIG_GAMEPORT_CS461x is not set
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
# CONFIG_JOYSTICK_A3D is not set
CONFIG_JOYSTICK_ADI=m
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
# CONFIG_JOYSTICK_IFORCE is not set
CONFIG_JOYSTICK_WARRIOR=m
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDDLER is not set
# CONFIG_JOYSTICK_DB9 is not set
# CONFIG_JOYSTICK_GAMECON is not set
# CONFIG_JOYSTICK_TURBOGRAFX is not set
# CONFIG_INPUT_JOYDUMP is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_UINPUT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
# CONFIG_SERIAL_8250_ACPI is not set
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set

#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_ALGOBIT=m
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_PHILIPSPAR is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_ALGOPCF is not set
CONFIG_I2C_CHARDEV=m

#
# I2C Hardware Sensors Mainboard support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_SIS96X is not set
CONFIG_I2C_VIAPRO=m

#
# I2C Hardware Sensors Chip support
#
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM78 is not set
CONFIG_SENSORS_VIA686A=m
# CONFIG_SENSORS_W83781D is not set
CONFIG_I2C_SENSOR=m

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=y
CONFIG_NVRAM=m
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD_8151 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
CONFIG_AGP_VIA=m
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_MGA is not set
# CONFIG_MWAVE is not set
CONFIG_RAW_DRIVER=y
CONFIG_HANGCHECK_TIMER=m

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m

#
# Video For Linux
#
CONFIG_VIDEO_PROC_FS=y

#
# Video Adapters
#
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_BWQCAM is not set
# CONFIG_VIDEO_CQCAM is not set
# CONFIG_VIDEO_W9966 is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_ZR36120 is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set

#
# Radio Adapters
#
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
# CONFIG_VIDEO_BTCX is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=m
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
CONFIG_HFS_FS=m
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=m
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_NEC98_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-15"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
# CONFIG_NLS_CODEPAGE_863 is not set
CONFIG_NLS_CODEPAGE_864=m
# CONFIG_NLS_CODEPAGE_865 is not set
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=m
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=y
CONFIG_NLS_KOI8_R=m
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y

#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
# CONFIG_SND_SEQUENCER is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_RTCTIMER=m
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
CONFIG_SND_EMU10K1=m
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_SONICVIBES is not set
CONFIG_SND_VIA82XX=m
# CONFIG_SND_VX222 is not set

#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set

#
# Open Sound System
#
CONFIG_SOUND_PRIME=m
# CONFIG_SOUND_BT878 is not set
# CONFIG_SOUND_CMPCI is not set
CONFIG_SOUND_EMU10K1=m
# CONFIG_MIDI_EMU10K1 is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_CS4281 is not set
# CONFIG_SOUND_ES1370 is not set
# CONFIG_SOUND_ES1371 is not set
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_MAESTRO3 is not set
# CONFIG_SOUND_ICH is not set
# CONFIG_SOUND_RME96XX is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_VIA82CXXX is not set
# CONFIG_SOUND_OSS is not set
# CONFIG_SOUND_TVMIXER is not set
# CONFIG_SOUND_ALI5455 is not set
# CONFIG_SOUND_FORTE is not set
# CONFIG_SOUND_AD1980 is not set

#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set

#
# USB Host Controller Drivers
#
# CONFIG_USB_EHCI_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=m

#
# USB Device Class drivers
#
CONFIG_USB_AUDIO=m
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
CONFIG_USB_WACOM=m
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
CONFIG_USB_SCANNER=m
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_OV511 is not set
CONFIG_USB_PWC=m
# CONFIG_USB_SE401 is not set
# CONFIG_USB_STV680 is not set

#
# USB Network adaptors
#
# CONFIG_USB_AX8817X is not set
# CONFIG_USB_CATC is not set
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_TEST is not set
CONFIG_USB_GADGET=m
# CONFIG_USB_NET2280 is not set
# CONFIG_USB_ZERO is not set
# CONFIG_USB_ETH is not set

#
# Bluetooth support
#
# CONFIG_BT is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_TEST is not set

#
# Library routines
#
CONFIG_CRC32=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_X86_BIOS_REBOOT=y



Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
`The best way to get a drink out of a Vogon is to stick
your finger down his throat...'
                 --- The Book, on one of the Vogon's social inadequacies.
                 --- Douglas Adams, The Hitchhikers Guide to the Galaxy

Re: 2.6.0-test3 cannot mount root fs

[Herbert Pötzl]

Hi Norbert!

your config seems reasonable to me ...

> I tells me all the usual stuff concerning that it finds 
> the controllers (VIA and HPT) and disks/cdroms, but than 
> hangs with
>        cannot mount rootfs "NULL" or hdb1

AFAIK, there is no such message in 2.6.0-test3 ...

if, on the other hand, the message looks like ...

-----------
VFS: Cannot open root device "hdb1" or unknown-block(0,0)
Please append a correct "root=" boot option
-----------

then this means that "hdb1" was the device given at
the kenel command line (as root=/dev/hdb1) and the
'unknown-block(0,0)' is the major/minor the kernel 
recognized ...

you should pay special attention to the disc/partition
discovery done by the IDE subsystem ...

-----------
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 65537 sectors (33 MB) w/256KiB Cache, CHS=65/16/63
hda: hda1 
hdb: 131074 sectors (67 MB) w/256KiB Cache, CHS=130/16/63
hdb: hdb1 hdb2 hdb3
...
-----------

maybe you could attach a serial console (line)
and capture the boot process, and report it ...

HTH,
Herbert

Re: 2.6.0-test3 cannot mount root fs

[Norbert Preining]

On Mon, 11 Aug 2003, Herbert Pötzl wrote:
> your config seems reasonable to me ...

Good to know.

> -----------
> VFS: Cannot open root device "hdb1" or unknown-block(0,0)
> Please append a correct "root=" boot option
> -----------

Yes, it is like this.

> maybe you could attach a serial console (line)
> and capture the boot process, and report it ...

I copied most of it to paper, so here it is, for sure with some typing
errors:

Everything up to hear I couldn't read (maybe I find a laptop or other
device for serial communication):
VP_IDE: IDE controller at PCI slot 0000:00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on
pci0000::00:07.1
    ide0: BM-DMA at 0xa000-0xa007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xa008-0xa00f, BIOS settings: hdc:DMA, hdd:DMA
hda: IC35L040AVER07-0 ....
hda: IRQ probe failed (0xfffffcfa)  **** this line only with acpi
                                    **** when running with acpi=off it
                                    **** does not occur
hdb: IC35L040AVER07-0 ....
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: TOSHIBA DVD-ROM SD-M1402, ATAPI CD/DVD-ROM drive
hdd: PLEXTOR CD-R PREMIUM, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
HPT370A: IDE controller at PCI slot 0000:00:0e.0
HPT370A: chipset revision 4
HPT37X: using 33MHz PCI clock
HPT370A: 100% native mode on IRQ 11
    ide2: BM-DMA at 0xe000-0xe007, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xe008-0xe00f, BIOS settings: hdg:DMA, hdh:pio
hde: Maxtor 52049H4, ATA DISK drive
ide2 at 0xd000-0xd007,0xd402 on irq 11
hdg: IBM-DTTA-350840, ATA DISK drive
ide3 at 0xd800-0xd807,0xdc02 on irq 11
hda: max request size 128 KiB
hda: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=5005/255/63,
UDMA(100)
        hda: hda1 hda2 hda3
hdb: max request size 128 KiB
hdb: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=79780/16/63,
UDMA(100)
        hdb: hdb1 hdb2 hdb3 hdb4 < hdb5 hdb6 hdb7 hdb8 hdb9 hdb10 hdb11
hdb12>
hde: max request size 128 KiB
hde: 40020624 sectors (20491 MB) w/2048KiB Cache, CHS=39703/16/63,
UDMA(100)
        hde: hde1
hdg: max request size 128 KiB
hdg: 16514064 sectors (8455 MB) w/467KiB Cache, CHS=16383/16/63,
UDMA(33)
        hdg: hdg1
hdc: ATAPI 40X DVD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.31
hdd: ATAPI 40X CD-ROM ....
Console ...
...
blabla
...
VFS: cannot mount ...


So it looks like my disks are recognized, the partitions are recognized,
but somehow I am missing the
	ide-disk attached
or similar message.


Maybe this helps someone to have an idea!

Best wishes and thanks a lot

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
WIVENHOE (n.)
The cry of alacrity with which a sprightly eighty-year-old breaks the
ice on the lake when going for a swim on Christmas Eve.
			--- Douglas Adams, The Meaning of Liff

Re: 2.6.0-test3 cannot mount root fs

[Herbert Pötzl]

On Mon, Aug 11, 2003 at 11:50:58PM +0200, Norbert Preining wrote:
> On Mon, 11 Aug 2003, Herbert Pötzl wrote:
> > your config seems reasonable to me ...
> 
> Good to know.
> 
> > -----------
> > VFS: Cannot open root device "hdb1" or unknown-block(0,0)
> > Please append a correct "root=" boot option
> > -----------
> 
> Yes, it is like this.

like or exactly like? 

unfortunately this line is missing in your copy ...
(as well as the lines regarding hdb discovery ;)

best,
Herbert

> 
> > maybe you could attach a serial console (line)
> > and capture the boot process, and report it ...
> 
> I copied most of it to paper, so here it is, for sure with some typing
> errors:
> 
> Everything up to hear I couldn't read (maybe I find a laptop or other
> device for serial communication):
> VP_IDE: IDE controller at PCI slot 0000:00:07.1
> VP_IDE: chipset revision 6
> VP_IDE: not 100% native mode: will probe irqs later
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on
> pci0000::00:07.1
>     ide0: BM-DMA at 0xa000-0xa007, BIOS settings: hda:DMA, hdb:DMA
>     ide1: BM-DMA at 0xa008-0xa00f, BIOS settings: hdc:DMA, hdd:DMA
> hda: IC35L040AVER07-0 ....
> hda: IRQ probe failed (0xfffffcfa)  **** this line only with acpi
>                                     **** when running with acpi=off it
>                                     **** does not occur
> hdb: IC35L040AVER07-0 ....
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hdc: TOSHIBA DVD-ROM SD-M1402, ATAPI CD/DVD-ROM drive
> hdd: PLEXTOR CD-R PREMIUM, ATAPI CD/DVD-ROM drive
> ide1 at 0x170-0x177,0x376 on irq 15
> HPT370A: IDE controller at PCI slot 0000:00:0e.0
> HPT370A: chipset revision 4
> HPT37X: using 33MHz PCI clock
> HPT370A: 100% native mode on IRQ 11
>     ide2: BM-DMA at 0xe000-0xe007, BIOS settings: hde:pio, hdf:pio
>     ide3: BM-DMA at 0xe008-0xe00f, BIOS settings: hdg:DMA, hdh:pio
> hde: Maxtor 52049H4, ATA DISK drive
> ide2 at 0xd000-0xd007,0xd402 on irq 11
> hdg: IBM-DTTA-350840, ATA DISK drive
> ide3 at 0xd800-0xd807,0xdc02 on irq 11
> hda: max request size 128 KiB
> hda: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=5005/255/63,
> UDMA(100)
>         hda: hda1 hda2 hda3
> hdb: max request size 128 KiB
> hdb: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=79780/16/63,
> UDMA(100)
>         hdb: hdb1 hdb2 hdb3 hdb4 < hdb5 hdb6 hdb7 hdb8 hdb9 hdb10 hdb11
> hdb12>
> hde: max request size 128 KiB
> hde: 40020624 sectors (20491 MB) w/2048KiB Cache, CHS=39703/16/63,
> UDMA(100)
>         hde: hde1
> hdg: max request size 128 KiB
> hdg: 16514064 sectors (8455 MB) w/467KiB Cache, CHS=16383/16/63,
> UDMA(33)
>         hdg: hdg1
> hdc: ATAPI 40X DVD-ROM drive, 128kB Cache, UDMA(33)
> Uniform CD-ROM driver Revision: 3.31
> hdd: ATAPI 40X CD-ROM ....
> Console ...
> ...
> blabla
> ...
> VFS: cannot mount ...
> 
> 
> So it looks like my disks are recognized, the partitions are recognized,
> but somehow I am missing the
> 	ide-disk attached
> or similar message.
> 
> 
> Maybe this helps someone to have an idea!
> 
> Best wishes and thanks a lot
> 
> Norbert
> 
> -------------------------------------------------------------------------------
> Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
> gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
> -------------------------------------------------------------------------------
> WIVENHOE (n.)
> The cry of alacrity with which a sprightly eighty-year-old breaks the
> ice on the lake when going for a swim on Christmas Eve.
> 			--- Douglas Adams, The Meaning of Liff
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.0-test3 cannot mount root fs

[Mark W. Alexander]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=UTF-8, Size: 700 bytes --]

On Tue, 12 Aug 2003, Herbert [iso-8859-1] Pötzl wrote:

> > hdg: max request size 128 KiB
> > hdg: 16514064 sectors (8455 MB) w/467KiB Cache, CHS=16383/16/63,
> > UDMA(33)
> >         hdg: hdg1
> > hdc: ATAPI 40X DVD-ROM drive, 128kB Cache, UDMA(33)
> > Uniform CD-ROM driver Revision: 3.31
> > hdd: ATAPI 40X CD-ROM ....
> > Console ...
> > ...
> > blabla
> > ...
> > VFS: cannot mount ...

Are you using an initrd image and if so, are you using the new
initrd-tools?  I was having this problem before upgrading
initrd-tools. 2.6 does not support compressed ROM initrd images, so
even though it sees your partitions it can't load the _initial_ root.

mwa
--
Mark W. Alexander
slash@dotnetslash.net

Re: 2.6.0-test3 cannot mount root fs

[Norbert Preining]

On Die, 12 Aug 2003, Herbert Pötzl wrote:
> > > -----------
> > > VFS: Cannot open root device "hdb1" or unknown-block(0,0)
> > > Please append a correct "root=" boot option
> > > -----------
> > 
> > Yes, it is like this.
> 
> like or exactly like? 

Ok, here is the exact output with different root= options:

root=/dev/hdb1
	Cannot open root device "<NULL>" or hdb1
	Please append a correct "root=" boot option

root=0341
	Cannot open root device "0341" or hdb1
	Please append a correct "root=" boot option

root=03:41
	Cannot open root device "03:41" or unknown-block(0,0)
	Please append a correct "root=" boot option

root=03:65
	Cannot open root device "03:65" or unknown-block(0,0)
	Please append a correct "root=" boot option

> (as well as the lines regarding hdb discovery ;)

Why? Isnt't this line what you meant: (From my previous email)

> > hdb: IC35L040AVER07-0 ....
...
> > hdb: max request size 128 KiB
> > hdb: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=79780/16/63, UDMA(100)
> >         hdb: hdb1 hdb2 hdb3 hdb4 < hdb5 hdb6 hdb7 hdb8 hdb9 hdb10 hdb11 hdb12>
...

Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
FROSSES (pl.n.)
The lecherous looks exchanged between sixteen-year-olds at a party
given by someone's parents.
			--- Douglas Adams, The Meaning of Liff

Re: 2.6.0-test3 cannot mount root fs

[Norbert Preining]

On Mon, 11 Aug 2003, Mark W. Alexander wrote:
> > > VFS: cannot mount ...
> 
> Are you using an initrd image and if so, are you using the new

No, but to be on the sure side I rebuild a kernel with
	CONFIG_INITRD is not set
and got the same effect.

I think I give up. Hundreds of Alt-PrintScr-b are disturbing ;-)

Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
DUDOO (n.)
The most deformed potato in any given collection of potatoes.
			--- Douglas Adams, The Meaning of Liff

Re: 2.6.0-test3 cannot mount root fs

[Herbert Pötzl]

On Tue, Aug 12, 2003 at 07:39:56AM +0200, Norbert Preining wrote:
> On Die, 12 Aug 2003, Herbert Pötzl wrote:
> > > > -----------
> > > > VFS: Cannot open root device "hdb1" or unknown-block(0,0)
> > > > Please append a correct "root=" boot option
> > > > -----------
> > > 
> > > Yes, it is like this.
> > 
> > like or exactly like? 
> 
> Ok, here is the exact output with different root= options:

now this makes some sense ...

> root=/dev/hdb1
> 	Cannot open root device "<NULL>" or hdb1
> 	Please append a correct "root=" boot option

here obviously root wasn't set to a string, but
device hdb1 is passed as in kernel setting?

> root=0341
> 	Cannot open root device "0341" or hdb1
> 	Please append a correct "root=" boot option

this seems correct, but maybe some bug kicks in ...

> root=03:41
> 	Cannot open root device "03:41" or unknown-block(0,0)
> 	Please append a correct "root=" boot option
> 
> root=03:65
> 	Cannot open root device "03:65" or unknown-block(0,0)
> 	Please append a correct "root=" boot option

the other options are obviously passed as root=
but can not be interpreted/resolved to a device

my assumption would be that you use the lilo root option
and do not pass the root= as kenel boot option ...

I would suggest to give append="root=/dev/hdb1" a try,
and/or update lilo or change to grub ...

> > (as well as the lines regarding hdb discovery ;)
> 
> Why? Isnt't this line what you meant: (From my previous email)

because IC35L040AVER07-0 .... is very unlikely to be a kernel message ...

> > > hdb: IC35L040AVER07-0 ....
> ...
> > > hdb: max request size 128 KiB
> > > hdb: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=79780/16/63, UDMA(100)
> > >         hdb: hdb1 hdb2 hdb3 hdb4 < hdb5 hdb6 hdb7 hdb8 hdb9 hdb10 hdb11 hdb12>
> ...

best,
Herbert

> Best wishes
> 
> Norbert
> 
> -------------------------------------------------------------------------------
> Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
> gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
> -------------------------------------------------------------------------------
> FROSSES (pl.n.)
> The lecherous looks exchanged between sixteen-year-olds at a party
> given by someone's parents.
> 			--- Douglas Adams, The Meaning of Liff

Re: 2.6.0-test3 cannot mount root fs

[Norbert Preining]

On Die, 12 Aug 2003, Herbert Pötzl wrote:
> my assumption would be that you use the lilo root option
> and do not pass the root= as kenel boot option ...
> 
> I would suggest to give append="root=/dev/hdb1" a try,
> and/or update lilo or change to grub ...

I tried *all* the variants with passing
	root=....
on the lilo line, so it is passed to the kernel and not via rdev or
something else.

> > > (as well as the lines regarding hdb discovery ;)
> > 
> > Why? Isnt't this line what you meant: (From my previous email)
> 
> because IC35L040AVER07-0 .... is very unlikely to be a kernel message ...

The hard disk is an IC35L...:
(running 2.4.22-rc2):

[~] cat /proc/ide/hdb/model 
IC35L040AVER07-0

> > > > hdb: max request size 128 KiB
> > > > hdb: 80418240 sectors (41174 MB) w/1916KiB Cache, CHS=79780/16/63, UDMA(100)
> > > >         hdb: hdb1 hdb2 hdb3 hdb4 < hdb5 hdb6 hdb7 hdb8 hdb9 hdb10 hdb11 hdb12>


So it *IS* recognized. But why not mounted.

Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
WIKE (vb.)
To rip a piece of sticky plaster off your skin as fast as possible in
the hope that it will (a) show how brave you are, and (b) not hurt.
			--- Douglas Adams, The Meaning of Liff

Re: 2.6.0-test3 cannot mount root fs

[jeff millar]

----- Original Message ----- 
From: "Herbert Pötzl" <herbert@13thfloor.at>
To: "Norbert Preining" <preining@logic.at>
Cc: <linux-kernel@vger.kernel.org>
Sent: Tuesday, August 12, 2003 8:26 AM
Subject: Re: 2.6.0-test3 cannot mount root fs
>
> I would suggest to give append="root=/dev/hdb1" a try,
> and/or update lilo or change to grub ...
>

I'm getting the same sorts of error messages with grub.  Here's the
grub.conf file...originally generated by a Redhat 9 install.

2.4.20 works with root=0303.  But I've tried all the variants after root=
(03:03, 0303, hda3, /dev/hda3) and nothing works

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/hda3
#          initrd /initrd-version.img
#       boot=/dev/hda
# 2.6.0-test kernels apparently have bug
#       in processing root=device names
#       changed to major:minor where minor is letter*64 + partition number
#       hdb1 = 03:65, hda3=03:03
# But, that didn't work for 2.4.20...trying 0303 now
#
default=1
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.6.0-test3)
        root (hd0,0)
        kernel /vmlinuz-2.6.0-test3 ro root=03:03
#       initrd /initrd-2.6.0-test3.img
title Red Hat Linux (2.4.20-19.9)
        root (hd0,0)
        Kernel /vmlinuz-2.4.20-19.9 ro root=0303
        initrd /initrd-2.4.20-19.9.img
title Red Hat Linux (2.4.20-18.9)
        root (hd0,0)
        kernel /vmlinuz-2.4.20-18.9 ro root=/dev/hda3
        initrd /initrd-2.4.20-18.9.img

Re: 2.6.0-test3 cannot mount root fs

[Thomas Molina]

> > I would suggest to give append="root=/dev/hdb1" a try,
> > and/or update lilo or change to grub ...
> >
> 
> I'm getting the same sorts of error messages with grub.  Here's the
> grub.conf file...originally generated by a Redhat 9 install.
> 
> 2.4.20 works with root=0303.  But I've tried all the variants after root=
> (03:03, 0303, hda3, /dev/hda3) and nothing works
> 
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to this file
> # NOTICE:  You have a /boot partition.  This means that
> #          all kernel and initrd paths are relative to /boot/, eg.
> #          root (hd0,0)
> #          kernel /vmlinuz-version ro root=/dev/hda3
> #          initrd /initrd-version.img
> #       boot=/dev/hda
> # 2.6.0-test kernels apparently have bug
> #       in processing root=device names
> #       changed to major:minor where minor is letter*64 + partition number
> #       hdb1 = 03:65, hda3=03:03
> # But, that didn't work for 2.4.20...trying 0303 now

I have a hard time believing that 2.6.0-test kernels have this bug.  There 
must be something else going on here.  This is my grub.conf file:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this 
file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd0,7)
#          kernel /boot/vmlinuz-version ro root=/dev/hda8
#          initrd /boot/initrd-version.img
#boot=/dev/hda
default=1
timeout=10
splashimage=/boot/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-19.8)
        root (hd0,7)
        kernel /boot/vmlinuz-2.4.20-19.8 ro root=/dev/hda8 vga=792 
        initrd /boot/initrd-2.4.20-19.8.img
title Red Hat Linux (2.6.0-test2-0808)
        root (hd0,7)
        kernel /boot/vmlinuz-2.6.0-test2-0808 ro root=/dev/hda8 vga=792 

SOLUTION Re: 2.6.0-test3 cannot mount root fs

[Norbert Preining]

On Die, 12 Aug 2003, Christian Mautner wrote:
> Hast du auch einen kompletten Kernel tarball versucht? Wahrscheinlich

The solution is:
	Get a COMPLETE linux-2.6.0-test3.tar.bz2
and 
	DO NOT USE patch

I patched up the kernel from 2.5.20 or something and there seemed to be
an error somewhere on the way up. Getting a *clean* kernel tar file,
compile with the same .config, running.

This is the use of patches!

Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
AINDERBY STEEPLE (n.)
One who asks you a question with the apparent motive of wanting to
hear your answer, but who cuts short your opening sentence by leaning
forward and saying 'and I'll tell you why I ask...' and then talking
solidly for the next hour.
			--- Douglas Adams, The Meaning of Liff

Re: SOLUTION Re: 2.6.0-test3 cannot mount root fs

["Andrey Borzenkov"]

congratulations :)

-----Original Message-----

> 
> On Die, 12 Aug 2003, Christian Mautner wrote:
> > Hast du auch einen kompletten Kernel tarball versucht? Wahrscheinlich
> 
> The solution is:
> 	Get a COMPLETE linux-2.6.0-test3.tar.bz2
> and 
> 	DO NOT USE patch
> 
> I patched up the kernel from 2.5.20 or something and there seemed to be
> an error somewhere on the way up. Getting a *clean* kernel tar file,
> compile with the same .config, running.
> 
> This is the use of patches!
> 

well, I always do make distclean after patch ... I cannot afford
loading 30MB every week.

Re: SOLUTION Re: 2.6.0-test3 cannot mount root fs

[Norbert Preining]

On Mit, 13 Aug 2003, "Andrey Borzenkov"  wrote:
> congratulations :)

:-)))

> well, I always do make distclean after patch ... I cannot afford
> loading 30MB every week.

I *ALWAYS* do 
	make distclean
and
	make mrproper
and all other incantations of cleaning, too! This was NOT the problem,
but a wrongly diff file obviously messed up the kernel.

Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
Zaphod grinned two manic grins, sauntered over to the bar
and bought most of it.
                 --- Zaphod in paradise.
                 --- Douglas Adams, The Hitchhikers Guide to the Galaxy

Re: SOLUTION Re: 2.6.0-test3 cannot mount root fs

[jeff millar]

Nope...  For the reported problem I had with grub and root=/dev/hda3, it was
with a fresh tar file.

As someone said, this "can't happen".  And as someone else said, "It comes
and goes with random changes in .config file"

jeff

----- Original Message ----- 
From: "Norbert Preining" <preining@logic.at>
To: "gaxt" <gaxt@rogers.com>; "Henrik Ræder Clausen" <henrik@fangorn.dk>;
"Francois Romieu" <romieu@fr.zoreil.com>; <linux-kernel@vger.kernel.org>;
"Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>; "Mr. James W.
Laferriere" <babydr@baby-dragons.com>; "Brown, Len" <len.brown@intel.com>;
"Andrew Morton" <akpm@osdl.org>; "Mark W. Alexander"
<slash@dotnetslash.net>; "jeff millar" <wa1hco@adelphia.net>; "Thomas
Molina" <tmolina@cablespeed.com>; "Christian Mautner" <chm@istop.com>;
"Andrey Borzenkov" <arvidjaar@mail.ru>; "Herbert Pötzl"
<herbert@13thfloor.at>
Sent: Wednesday, August 13, 2003 2:15 AM
Subject: SOLUTION Re: 2.6.0-test3 cannot mount root fs


> On Die, 12 Aug 2003, Christian Mautner wrote:
> > Hast du auch einen kompletten Kernel tarball versucht? Wahrscheinlich
>
> The solution is:
> Get a COMPLETE linux-2.6.0-test3.tar.bz2
> and
> DO NOT USE patch
>
> I patched up the kernel from 2.5.20 or something and there seemed to be
> an error somewhere on the way up. Getting a *clean* kernel tar file,
> compile with the same .config, running.
>
> This is the use of patches!
>
> Best wishes
>
> Norbert
>
> --------------------------------------------------------------------------
-----
> Norbert Preining <preining AT logic DOT at>         Technische Universität
Wien
> gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5
B094
> --------------------------------------------------------------------------
-----
> AINDERBY STEEPLE (n.)
> One who asks you a question with the apparent motive of wanting to
> hear your answer, but who cuts short your opening sentence by leaning
> forward and saying 'and I'll tell you why I ask...' and then talking
> solidly for the next hour.
> --- Douglas Adams, The Meaning of Liff
>

Re: SOLUTION Re: 2.6.0-test3 cannot mount root fs

[Herbert Pötzl]

On Wed, Aug 13, 2003 at 08:07:20AM -0400, jeff millar wrote:
> Nope...  For the reported problem I had with grub and root=/dev/hda3, it was
> with a fresh tar file.
> 
> As someone said, this "can't happen".  And as someone else said, "It comes
> and goes with random changes in .config file"

so is there still somebody who is not able to boot,
despite of 16 different versions of root=wossname?

if so, I'm willing to make a small patch, which does
_a_lot_of_ status output and checks around this
code ... so it might be possible to track down any
issues/bugs ...

pleas let me know,
Herbert

> jeff
> 
> ----- Original Message ----- 
> From: "Norbert Preining" <preining@logic.at>
> To: "gaxt" <gaxt@rogers.com>; "Henrik Ræder Clausen" <henrik@fangorn.dk>;
> "Francois Romieu" <romieu@fr.zoreil.com>; <linux-kernel@vger.kernel.org>;
> "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>; "Mr. James W.
> Laferriere" <babydr@baby-dragons.com>; "Brown, Len" <len.brown@intel.com>;
> "Andrew Morton" <akpm@osdl.org>; "Mark W. Alexander"
> <slash@dotnetslash.net>; "jeff millar" <wa1hco@adelphia.net>; "Thomas
> Molina" <tmolina@cablespeed.com>; "Christian Mautner" <chm@istop.com>;
> "Andrey Borzenkov" <arvidjaar@mail.ru>; "Herbert Pötzl"
> <herbert@13thfloor.at>
> Sent: Wednesday, August 13, 2003 2:15 AM
> Subject: SOLUTION Re: 2.6.0-test3 cannot mount root fs
> 
> 
> > On Die, 12 Aug 2003, Christian Mautner wrote:
> > > Hast du auch einen kompletten Kernel tarball versucht? Wahrscheinlich
> >
> > The solution is:
> > Get a COMPLETE linux-2.6.0-test3.tar.bz2
> > and
> > DO NOT USE patch
> >
> > I patched up the kernel from 2.5.20 or something and there seemed to be
> > an error somewhere on the way up. Getting a *clean* kernel tar file,
> > compile with the same .config, running.
> >
> > This is the use of patches!
> >
> > Best wishes
> >
> > Norbert
> >
> > --------------------------------------------------------------------------
> -----
> > Norbert Preining <preining AT logic DOT at>         Technische Universität
> Wien
> > gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5
> B094
> > --------------------------------------------------------------------------
> -----
> > AINDERBY STEEPLE (n.)
> > One who asks you a question with the apparent motive of wanting to
> > hear your answer, but who cuts short your opening sentence by leaning
> > forward and saying 'and I'll tell you why I ask...' and then talking
> > solidly for the next hour.
> > --- Douglas Adams, The Meaning of Liff
> >

Re: SOLUTION Re: 2.6.0-test3 cannot mount root fs

[Herbert Pötzl]

On Wed, Aug 13, 2003 at 08:42:12AM -0400, jeff millar wrote:
> I didn't try 16 versions but did try at least
> 
>     /dev/hda3, 0303, 03:03, hda3
> 
> All with grub.conf similar to below
> 
> Please let me know if I need to try something else with grub.. If you have a
> patch, I'll try it tonite and email the results to you and the list.

here is the patch, please try to capture/copy
all lines starting with $$ (and the ones immediately
following) ... 

boot okay ...

$$ name_to_dev_t() >/dev/hda1<
$$ check >hda1<
$$ check >hda1< (<31)
$$ try_name() I
$$ try_name() >hda1<,0
$$ open >/sys/block/hda1/dev< = -1
$$ fail
$$ strtoul >1< -> 1
$$ try_name() II
$$ try_name() >hda<,1
$$ open >/sys/block/hda/dev< = 0
$$ read 0[32] = >3:0
< (4)
$$ buf: >3:0<
$$ mkdev (3,0) -> 768
$$ open2 >/sys/block/hda/range< = 0
$$ read2 0[32] = >64
< (3)
$$ buf: >64<
$$ strtoul >64< -> 64
$$ 1 < 64 ?
$$ name_to_dev_t() done
VFS: Mounted root (ext2 filesystem) readonly.


device not present ...

$$ name_to_dev_t() >/dev/hdc1<
$$ check >hdc1<
$$ check >hdc1< (<31)
$$ try_name() I
$$ try_name() >hdc1<,0
$$ open >/sys/block/hdc1/dev< = -1
$$ fail
$$ strtoul >1< -> 1
$$ try_name() II
$$ try_name() >hdc<,1
$$ open >/sys/block/hdc/dev< = -1
$$ fail
$$ name_to_dev_t() failed
$$ name_to_dev_t() done
VFS: Cannot open root device "hdc1" or unknown-block(0,0)


patch below ...
-----------------

diff -NurP --minimal linux-2.6.0-test3/init/do_mounts.c linux-2.6.0-test3-debug/init/do_mounts.c
--- linux-2.6.0-test3/init/do_mounts.c	2003-08-09 16:31:35.000000000 +0200
+++ linux-2.6.0-test3-debug/init/do_mounts.c	2003-08-13 15:15:23.000000000 +0200
@@ -62,11 +62,14 @@
 
 	/* read device number from .../dev */
 
+	printk("$$ try_name() >%s<,%d\n", name, part);
 	sprintf(path, "/sys/block/%s/dev", name);
 	fd = open(path, 0, 0);
+	printk("$$ open >%s< = %d\n", path, fd);
 	if (fd < 0)
 		goto fail;
 	len = read(fd, buf, 32);
+	printk("$$ read %d[32] = >%*s< (%d)\n", fd, len, buf, len);
 	close(fd);
 	if (len <= 0 || len == 32 || buf[len - 1] != '\n')
 		goto fail;
@@ -74,9 +77,11 @@
 	/*
 	 * The format of dev is now %u:%u -- see print_dev_t()
 	 */
-	if (sscanf(buf, "%u:%u", &maj, &min) == 2)
+	printk("$$ buf: >%s<\n", buf);
+	if (sscanf(buf, "%u:%u", &maj, &min) == 2) {
 		res = MKDEV(maj, min);
-	else
+		printk("$$ mkdev (%d,%d) -> %d\n", maj, min, res);
+	} else
 		goto fail;
 
 	/* if it's there and we are not looking for a partition - that's it */
@@ -86,21 +91,27 @@
 	/* otherwise read range from .../range */
 	sprintf(path, "/sys/block/%s/range", name);
 	fd = open(path, 0, 0);
+	printk("$$ open2 >%s< = %d\n", path, fd);
 	if (fd < 0)
 		goto fail;
 	len = read(fd, buf, 32);
+	printk("$$ read2 %d[32] = >%*s< (%d)\n", fd, len, buf, len);
 	close(fd);
 	if (len <= 0 || len == 32 || buf[len - 1] != '\n')
 		goto fail;
 	buf[len - 1] = '\0';
+	printk("$$ buf: >%s<\n", buf);
 	range = simple_strtoul(buf, &s, 10);
+	printk("$$ strtoul >%s< -> %d\n", buf, range);
 	if (*s)
 		goto fail;
 
 	/* if partition is within range - we got it */
+	printk("$$ %d < %d ?\n", part, range);
 	if (part < range)
 		return res + part;
 fail:
+	printk("$$ fail\n");
 	return (dev_t) 0;
 }
 
@@ -130,27 +141,32 @@
 	dev_t res = 0;
 	int part;
 
+	printk("$$ name_to_dev_t() >%s<\n", name);
 	sys_mkdir("/sys", 0700);
 	if (sys_mount("sysfs", "/sys", "sysfs", 0, NULL) < 0)
 		goto out;
 
 	if (strncmp(name, "/dev/", 5) != 0) {
 		res = (dev_t) simple_strtoul(name, &p, 16);
+		printk("$$ strtoul >%s< -> %d\n", name, res);
 		if (*p)
 			goto fail;
 		goto done;
 	}
 	name += 5;
 	res = Root_NFS;
+	printk("$$ check >%s<\n", name);
 	if (strcmp(name, "nfs") == 0)
 		goto done;
 
+	printk("$$ check >%s< (<31)\n", name);
 	if (strlen(name) > 31)
 		goto fail;
 	strcpy(s, name);
 	for (p = s; *p; p++)
 		if (*p == '/')
 			*p = '.';
+	printk("$$ try_name() I\n");
 	res = try_name(s, 0);
 	if (res)
 		goto done;
@@ -160,7 +176,9 @@
 	if (p == s || !*p || *p == '0')
 		goto fail;
 	part = simple_strtoul(p, NULL, 10);
+	printk("$$ strtoul >%s< -> %d\n", p, part);
 	*p = '\0';
+	printk("$$ try_name() II\n");
 	res = try_name(s, part);
 	if (res)
 		goto done;
@@ -168,19 +186,23 @@
 	if (p < s + 2 || !isdigit(p[-2]) || p[-1] != 'p')
 		goto fail;
 	p[-1] = '\0';
+	printk("$$ try_name() III\n");
 	res = try_name(s, part);
 done:
+	printk("$$ name_to_dev_t() done\n");
 	sys_umount("/sys", 0);
 out:
 	sys_rmdir("/sys");
 	return res;
 fail:
+	printk("$$ name_to_dev_t() failed\n");
 	res = (dev_t) 0;
 	goto done;
 }
 
 static int __init root_dev_setup(char *line)
 {
+	printk("$$ root_dev_setup() >%s<\n", line);
 	strlcpy(saved_root_name, line, sizeof(saved_root_name));
 	return 1;
 }

Re: SOLUTION Re: 2.6.0-test3 cannot mount root fs

[Christian Mautner]

On Wed, Aug 13, 2003 at 08:15:46AM +0200, Norbert Preining wrote:
> On Die, 12 Aug 2003, Christian Mautner wrote:
> > Hast du auch einen kompletten Kernel tarball versucht? Wahrscheinlich
> 
> The solution is:
> 	Get a COMPLETE linux-2.6.0-test3.tar.bz2
> and 
> 	DO NOT USE patch

I'm pretty sure the problem is related to the file 
usr/initramfs_data.S. This file is automatically created by the
usr/Makefile, but not deleted by mrproper or distclean (in -test1). 

See l-k thread "remove initramfs temp files" of Aug 8.

The patch to -test2 contained the file usr/initramfs_data.S, and the
patch process fails since it's trying to create it. I ended up
accidently with garbage in usr/initramfs_data.S, to the effect that
the symbol .init.ramfs was empty (could be told from System.map),
which in turn had the effect that in init/initramfs.c the function
unpack_to_rootfs() was called with a length of 0 (&__initramfs_end ==
&__initramfs_start), which in turn prevented this very initial root
file system which is needed to mount root.

A warning message in unpack_to_rootfs() if it is called with a length
of 0 would have been very helpful.

Having make distclean remove initramfs_data.S would be very good
practice as well.

chm.

-- 
christian mautner -- chm bei istop punkt com -- ottawa, canada

Re: 2.6.0-test3 cannot mount root fs

[Paul Dickson]

On Tue, 12 Aug 2003 18:52:50 -0500 (CDT), Thomas Molina wrote:

> > I'm getting the same sorts of error messages with grub.  Here's the
> > grub.conf file...originally generated by a Redhat 9 install.
> > 
> > 2.4.20 works with root=0303.  But I've tried all the variants after root=
> > (03:03, 0303, hda3, /dev/hda3) and nothing works
> > 
> > # grub.conf generated by anaconda
> > #
> > # Note that you do not have to rerun grub after making changes to this file
> > # NOTICE:  You have a /boot partition.  This means that
> > #          all kernel and initrd paths are relative to /boot/, eg.
> > #          root (hd0,0)
> > #          kernel /vmlinuz-version ro root=/dev/hda3
> > #          initrd /initrd-version.img
> > #       boot=/dev/hda
> > # 2.6.0-test kernels apparently have bug
> > #       in processing root=device names
> > #       changed to major:minor where minor is letter*64 + partition number
> > #       hdb1 = 03:65, hda3=03:03
> > # But, that didn't work for 2.4.20...trying 0303 now
> 
> I have a hard time believing that 2.6.0-test kernels have this bug.  There 
> must be something else going on here.  This is my grub.conf file:

If you're running RH9, try the non-kernel RPMs found at
http://people.redhat.com/arjanv/2.5/RPMS.kernel/

I haven't had any trouble getting 2.6.0-test started with these.

	-Paul

Re: 2.6.0-test3 cannot mount root fs

[jeff millar]

----- Original Message ----- 
From: "Paul Dickson" <dickson@permanentmail.com>
To: <linux-kernel@vger.kernel.org>
Cc: <wa1hco@adelphia.net>; <herbert@13thfloor.at>; <preining@logic.at>;
"Thomas Molina" <tmolina@cablespeed.com>
Sent: Wednesday, August 13, 2003 12:59 PM
Subject: Re: 2.6.0-test3 cannot mount root fs


> If you're running RH9, try the non-kernel RPMs found at
> http://people.redhat.com/arjanv/2.5/RPMS.kernel/
>
> I haven't had any trouble getting 2.6.0-test started with these.

Already have all those installed

2.6.0-test3 _still_ cannot mount root fs

[jeff millar]

Redhat's 2.4.20 will boot with root=/dev/hda3 pointing to an ext3
filesystem, without an initrd, with the following message

   ext2fs warning (device IDE0(3,3) )  ext2_read_super: mounting ext3
filesystem as ext2
   VFS: mounted root (ext2 filesystem) readonly

So I assumed that 2.6.0-test3 will also work with ext3 compiled as a module.
I tried the various suggestions root=/dev/hda3, root=0303, root=03:03
without any luck.

I then tested a suggestion that ext3 should get compiled in but get the same
results

> > > ============================================
> > > Case 2: grub, no initrd, kernel=/vmlinux-2.6.0-test3 ro root=/dev/hda3
> > >
> > > ...stuff scrolled off the screen...
> > > check >hda3<
> > > check <hda3< (<31)
> > > try_name() I
> > > try_name() >hda3<,0
> > > open > /dys/block/hda3/dev< = -1
> > > fail
> > > strtoul >3< -> 3
> > > try_name() II
> > > try_name hda < 3
> > > open >/sys/block/hda/dev< = 0
> > > read 0[32]=>3:0
> > > 5^(4)
> > > buf: >3:0<
> > > mkdev(3,0) -> 768
> > > open2 >/sys/block/hda/range< = 0
> > > read2 0[32] => 764
> > > < (3)
> > > buf: >64<
> > > strtoul >64< -> 64
> > > name to dev_t() done
> > > VFS: cannot open root dev "hda3" or hda3

Herbert's debug patch produced the same messages with ext3 compiled in.

Any suggestions for what to try next?

jeff

Re: 2.6.0-test3 _still_ cannot mount root fs

[Herbert Pötzl]

Hi Jeff!

On Fri, Aug 15, 2003 at 08:34:37PM -0400, jeff millar wrote:
> Redhat's 2.4.20 will boot with root=/dev/hda3 pointing to an ext3
> filesystem, without an initrd, with the following message
> 
>    ext2fs warning (device IDE0(3,3) )  ext2_read_super: mounting ext3
> filesystem as ext2
>    VFS: mounted root (ext2 filesystem) readonly
> 
> So I assumed that 2.6.0-test3 will also work with ext3 compiled as a module.
> I tried the various suggestions root=/dev/hda3, root=0303, root=03:03
> without any luck.
> 
> I then tested a suggestion that ext3 should get compiled in but get the same
> results
> 
> Herbert's debug patch produced the same messages with ext3 compiled in.
> 
> Any suggestions for what to try next?

appended a short patch, which goes ontop of my other
debug patch ... this time, please concentrate on the
%% lines and the lines immediately above and below ...

best,
Herbert

> jeff

--- linux-2.6.0-test3-debug/init/do_mounts.c	2003-08-13 15:15:23.000000000 +0200
+++ linux-2.6.0-test3-debug-P1/init/do_mounts.c	2003-08-16 16:57:02.000000000 +0200
@@ -277,7 +277,11 @@
 	get_fs_names(fs_names);
 retry:
 	for (p = fs_names; *p; p += strlen(p)+1) {
-		int err = do_mount_root(name, p, flags, root_mount_data);
+                int err;
+                
+                printk("%%%% do_mount_root() >%s<,>%s<, %08x ...\n", name, p, flags);
+                err = do_mount_root(name, p, flags, root_mount_data);
+                printk("%%%% ret = %d\n", err);
 		switch (err) {
 			case 0:
 				goto out;

Re: 2.6.0-test3 cannot mount root fs

["Andrey Borzenkov"]

-----Original Message-----

> 
> On Die, 12 Aug 2003, "Andrey Borzenkov"  wrote:
> > > 	cannot mount rootfs "NULL" or hdb1
> > > I have compile in (of course) the filesystems of my root fs (ext3)
> > 
> > and you have tried to add rootfstype=ext3?
> 
> Yes. No change. Also in combination with all root= options and also with
> ext2.
> 

would you mind adding printk to mount_block_root to show
on which filesystem it fails and with which error? Something like

printk("VFS: Cannot open root device \"%s\" or %s for fs %s error=%d\n",
                               root_device_name, b, p, err);

-andrey

Re: 2.6.0-test3 cannot mount root fs

[Norbert Preining]

On Die, 12 Aug 2003, "Andrey Borzenkov"  wrote:
> > 	cannot mount rootfs "NULL" or hdb1
> > I have compile in (of course) the filesystems of my root fs (ext3)
> 
> and you have tried to add rootfstype=ext3?

Yes. No change. Also in combination with all root= options and also with
ext2.

Best wishes

Norbert

-------------------------------------------------------------------------------
Norbert Preining <preining AT logic DOT at>         Technische Universität Wien
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
SCONSER (n.)
A person who looks around then when talking to you, to see if there's
anyone more interesting about.
			--- Douglas Adams, The Meaning of Liff

Re: 2.6.0-test3 cannot mount root fs

[Christophe Saout]

Am Di, 2003-08-12 um 16.06 schrieb Herbert Pötzl:

> please provide the file and line number, where
> linux-2.6.0-test3 contains the string "cannot mount rootfs".
> (or where this string is synthesized)
> I am not able to locate it ...

I think he means:

init/do_mounts.c - line 278

panic("VFS: Unable to mount root fs on %s", __bdevname(ROOT_DEV, b));

--
Christophe Saout <christophe@saout.de>
Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html

Re: 2.6.0-test3 cannot mount root fs

["Andrey Borzenkov"]

>> 
>> > > cannot mount rootfs "NULL" or hdb1
>> > 
>> > AFAIK, there is no such message in 2.6.0-test3 ...
>> 
>> there is
>
> please provide the file and line number, where
> linux-2.6.0-test3 contains the string "cannot mount rootfs".
> (or where this string is synthesized)
> I am not able to locate it ...

oops, I actualy meant "Cannot open root device". Apparently the
above is synthesized message :)

Re: 2.6.0-test3 cannot mount root fs

[Herbert Pötzl]

On Tue, Aug 12, 2003 at 05:22:13PM +0400, "Andrey Borzenkov"  wrote:
> 
> >>        cannot mount rootfs "NULL" or hdb1
> >
> > AFAIK, there is no such message in 2.6.0-test3 ...
> 
> there is

please provide the file and line number, where
linux-2.6.0-test3 contains the string "cannot mount rootfs".
(or where this string is synthesized)
I am not able to locate it ...

> > if, on the other hand, the message looks like ...
> >
> > -----------
> > VFS: Cannot open root device "hdb1" or unknown-block(0,0)
> > Please append a correct "root=" boot option
> > -----------
> 
> he does not pass it in append line. He is using root= option in lilo.
> actually my lilo does pass "root=341" in this case while the above means lilo omits any root= command line option and relies on compiled-in ROOT_DEV

already suggested that, but he says, it doesn't
work either ... 

best,
Herbert

> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.0-test3 cannot mount root fs

["Andrey Borzenkov"]

> 	cannot mount rootfs "NULL" or hdb1
> I have compile in (of course) the filesystems of my root fs (ext3)

and you have tried to add rootfstype=ext3?

-andrey

Re: 2.6.0-test3 cannot mount root fs

["Andrey Borzenkov"]

>>        cannot mount rootfs "NULL" or hdb1
>
> AFAIK, there is no such message in 2.6.0-test3 ...

there is


> if, on the other hand, the message looks like ...
>
> -----------
> VFS: Cannot open root device "hdb1" or unknown-block(0,0)
> Please append a correct "root=" boot option
> -----------

he does not pass it in append line. He is using root= option in lilo.
actually my lilo does pass "root=341" in this case while the above means lilo omits any root= command line option and relies on compiled-in ROOT_DEV

Re: 2.6.0-test3 cannot mount root fs

[Daniel Blueman]

Norbert,

Try changing the entry in /etc/fstab from 'LABEL=/' to '/dev/hda' (sda, hdb,
etc) as appropriate.

-- 
Daniel J Blueman

COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test
--------------------------------------------------
1. GMX TopMail - Platz 1 und Testsieger!
2. GMX ProMail - Platz 2 und Preis-Qualitätssieger!
3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post