Here are the last few lines (written down and then typed) from the attempted boot TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 drivers/rtc/hcttosys.c: unable to open rtc device (rtc 0) VFS: Cannot open root device "sda5" or unknown -block(0,0) Here are the corresponding lines from dmesg from a successful boot of 2.6.18-r3 TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 drivers/rtc/hctosys.c: unable to open rtc device (rtc0) kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. I'm using for by sata driver (from dmesg) sata_sil 0000:01:05.0: version 2.0 =========== emerge --info ============== Portage 2.1.2_rc2-r3 (default-linux/amd64/2006.0, gcc-4.1.1, glibc-2.5-r0, 2.6.18-gentoo-r3 x86_64) ================================================================= System uname: 2.6.18-gentoo-r3 x86_64 AMD Opteron(tm) Processor 242 Gentoo Base System version 1.12.6 Last Sync: Thu, 30 Nov 2006 22:01:01 +0000 ccache version 2.4 [enabled] dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.4.4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r6 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r1 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=opteron -pipe -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O2 -march=opteron -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks fixpackages metadata-transfer parallel-fetch sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.osuosl.org http://cudlug.cudenver.edu/gentoo http://gentoo.binarycompass.org" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac aiglx alsa apache2 auctex audiofile bash-completion bcmath berkdb bitmap-fonts blas bonobo bzip2 calendar clamav cli cracklib crypt ctype cups dbus debugger dga divx-linux dlloader dri dvd dvdr dvdread elibc_glibc emacs emboss emul-linux86 encode esd fam fastcgi fbcon firefox flac foomaticdb fortran ftp gif glut gnome gphoto2 gpm gstreamer gtk gtk2 iconv imlib input_devices_keyboard input_devices_mouse ipv6 isdnlog java jpeg kde kerberos kernel_linux lapack latin1 leim lesstif libclamav lzw lzw-tiff mbox mcal mime mng mouse mozcalendar mozilla mp3 mpeg mpi mysql mysqli ncurses nls nocd nosendmail nptl nptlonly nsplugin nvidia offensive openal opengl osc oscar oss pam pcre pdf perl png pop pop3d portaudio ppds pppd preview-latex python qt3 quicktime readline reflection samba sasl sdl session sharedmem sockets source sox speex spell spl ssl svg symlink tcltk tcpd tetex threads tiff truetype truetype-fonts type1-fonts usb userland_GNU vhosts video_cards_fbdev video_cards_nvidia video_cards_vesa vorbis xine xmail xorg xpm xv xvid zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Don't reuse .config files on major kernel upgrades, start from the defaults.
(In reply to comment #1) > Don't reuse .config files on major kernel upgrades, start from the defaults. > I've used "make oldconfig" in the past and got in trouble. Now I do this and then do a diff (using emacs) and verify that.nothing that I understand has changed, and try not to let anything I don't understand change. I don't see how I could be as careful starting from scratch, and in fact I think it would be more risk. If this is not a bug, (or even if it is) perhaps someone could suggest where in the configuration I should be looking.
I made an assumption which might not have been correct (but I still think it probably is...) Please attach .config from working and non-working kernels
Oh and you need to be looking in the SCSI/SATA areas as the SATA drivers got moved out of SCSI and are now ATA drivers.
Created attachment 103080 [details] The working .config for 2.16.18-r3
Created attachment 103081 [details] The failing .config for 2.16.19
(In reply to comment #4) > Oh and you need to be looking in the SCSI/SATA areas as the SATA drivers got > moved out of SCSI and are now ATA drivers. Yes, I know, the Silicon SATA driver is in the config.
OK, so my assumption was wrong and you did notice the name change. But, you built sata_sil as a module. Modules are stored on disk, but the kernel cannot access disk without using this very driver. Build it into your kernel like you did in 2.6.18.
(In reply to comment #4) > Oh and you need to be looking in the SCSI/SATA areas as the SATA drivers got > moved out of SCSI and are now ATA drivers. Yes, I know, the Silicon SATA driver is in the config. (In reply to comment #8) > OK, so my assumption was wrong and you did notice the name change. But, you > built sata_sil as a module. Many thanks for seeing this. Unfortunately, I can't seem to do it. Neither make menuconfig nor make xconfig will let me define it to use anything other than a module. Is there something else that might work? Thanks. > > Modules are stored on disk, but the kernel cannot access disk without using > this very driver. Build it into your kernel like you did in 2.6.18. >
You built both CONFIG_ATA and the sata sil as module. If you change ATA to builtin then you can make sata_sil builtin as well
(In reply to comment #4) > Oh and you need to be looking in the SCSI/SATA areas as the SATA drivers got > moved out of SCSI and are now ATA drivers. Yes, I know, the Silicon SATA driver is in the config. (In reply to comment #8) > OK, so my assumption was wrong and you did notice the name change. But, you > built sata_sil as a module. Thanks that should do it. I'll not post anything if this now works (unless requested to.) Many thanks for seeing this. Unfortunately, I can't seem to do it. Neither make menuconfig nor make xconfig will let me define it to use anything other than a module. Is there something else that might work? Thanks. > > Modules are stored on disk, but the kernel cannot access disk without using > this very driver. Build it into your kernel like you did in 2.6.18. > (In reply to comment #10) > You built both CONFIG_ATA and the sata sil as module. If you change ATA to > builtin then you can make sata_sil builtin as well >
