2.6.19 and SiS5513

deficite · 2007-01-30 04:39:42

I'm completely lost here. I've gone to the 2.6.19-beyond2 kernel and thus I am presented with the ide/pata thing. I've researched on my own and found the module pata_sis and I've included it into my mkinitcpio.conf under the modules. I've tried every configuration I can think of of mkinitcpio and I always get the "Can't find device dev(0,0)" message from kinit, followed by a kernel panic. Here's my mkinitcpio.conf:

MODULES="pata_sis ext3"
HOOKS="base udev autodetect pata"

I've tried this with and without including the scsi hook. I've also tried using the ide hook and changing everything back to the old "hdx" format and I still get the same error. The wiki for mkinitcpio mentions a conflict between drivers for the piix controller (I'm using SiS5513, not piix). Is this the same problem? Do I need to somehow disable a module or something? If so, how? I've tried to get this running for two days and it's a pain because if it doesn't work I have to restart my computer and wait for Archie to boot up and then do a bunch of crap to get my rt2570 working so I can get on the internet. I know brain0 says he's gotten this to work.

edit: I suppose I should mention that the fallback image doesn't work either.

Last edited by deficite (2007-01-30 04:46:17)

brain0 · 2007-01-30 08:52:01

You should have kept a copy of your ide-enabled image there and made the experiments in a separate image. The above mkinitcpio.conf is correct. This is my image:

[thomas@architect ~]$ zcat /boot/kernel26.img | cpio -t | sort
11128 Block
/bin
/bin/cat
/bin/chroot
/bin/cryptsetup
/bin/dd
/bin/dumpkeys
/bin/false
/bin/fstype
/bin/gunzip
/bin/gzip
/bin/halt
/bin/insmod
/bin/ipconfig
/bin/kdb_mode
/bin/kill
/bin/kinit
/bin/kinit.shared
/bin/ln
/bin/loadkeys
/bin/losetup
/bin/lvm
/bin/mdassemble
/bin/minips
/bin/mkdir
/bin/mkfifo
/bin/mknod
/bin/moddeps
/bin/modprobe
/bin/mount
/bin/nfsmount
/bin/nuke
/bin/parseblock
/bin/pivot_root
/bin/poweroff
/bin/readlink
/bin/reboot
/bin/replace
/bin/resume
/bin/run-init
/bin/setfont
/bin/sh
/bin/sleep
/bin/true
/bin/umount
/bin/uname
/bin/zcat
/config
/dev
/dev/console
/dev/mapper
/dev/null
/dev/zero
/etc
/etc/start_udev
/etc/udev
/etc/udev/rules.d
/etc/udev/rules.d/udev.rules
/etc/udev/udev.conf
/hooks
/hooks/encrypt
/hooks/filesystems
/hooks/keymap
/hooks/lvm2
/hooks/udev
/init
/keymap
/lib
/lib/klibc-C2z_DMnqPyftZCYmjdWTcAM2woc.so
/lib/modules
/lib/modules/2.6.19-ARCH
/lib/modules/2.6.19-ARCH/kernel
/lib/modules/2.6.19-ARCH/kernel/arch
/lib/modules/2.6.19-ARCH/kernel/arch/i386
/lib/modules/2.6.19-ARCH/kernel/arch/i386/crypto
/lib/modules/2.6.19-ARCH/kernel/arch/i386/crypto/aes-i586.ko
/lib/modules/2.6.19-ARCH/kernel/arch/i386/crypto/twofish-i586.ko
/lib/modules/2.6.19-ARCH/kernel/crypto
/lib/modules/2.6.19-ARCH/kernel/crypto/anubis.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/arc4.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/blowfish.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/cast5.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/cast6.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/crc32c.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/crypto_null.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/deflate.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/ecb.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/khazad.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/md4.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/michael_mic.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/serpent.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/sha1.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/sha256.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/sha512.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/tcrypt.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/tea.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/tgr192.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/twofish_common.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/twofish.ko
/lib/modules/2.6.19-ARCH/kernel/crypto/wp512.ko
/lib/modules/2.6.19-ARCH/kernel/drivers
/lib/modules/2.6.19-ARCH/kernel/drivers/ata
/lib/modules/2.6.19-ARCH/kernel/drivers/ata/ata_generic.ko
/lib/modules/2.6.19-ARCH/kernel/drivers/ata/libata.ko
/lib/modules/2.6.19-ARCH/kernel/drivers/ata/pata_sis.ko
/lib/modules/2.6.19-ARCH/kernel/drivers/cdrom
/lib/modules/2.6.19-ARCH/kernel/drivers/cdrom/cdrom.ko
/lib/modules/2.6.19-ARCH/kernel/drivers/crypto
/lib/modules/2.6.19-ARCH/kernel/drivers/crypto/padlock.ko
/lib/modules/2.6.19-ARCH/kernel/drivers/crypto/padlock-sha.ko
/lib/modules/2.6.19-ARCH/kernel/drivers/md
/lib/modules/2.6.19-ARCH/kernel/drivers/md/dm-crypt.ko
/lib/modules/2.6.19-ARCH/kernel/drivers/md/dm-mod.ko
/lib/modules/2.6.19-ARCH/kernel/drivers/scsi
/lib/modules/2.6.19-ARCH/kernel/drivers/scsi/sd_mod.ko
/lib/modules/2.6.19-ARCH/kernel/drivers/scsi/sr_mod.ko
/lib/modules/2.6.19-ARCH/kernel/fs
/lib/modules/2.6.19-ARCH/kernel/fs/ext3
/lib/modules/2.6.19-ARCH/kernel/fs/ext3/ext3.ko
/lib/modules/2.6.19-ARCH/kernel/fs/jbd
/lib/modules/2.6.19-ARCH/kernel/fs/jbd/jbd.ko
/lib/modules/2.6.19-ARCH/kernel/fs/mbcache.ko
/lib/modules/2.6.19-ARCH/kernel/lib
/lib/modules/2.6.19-ARCH/kernel/lib/libcrc32c.ko
/lib/modules/2.6.19-ARCH/kernel/lib/zlib_deflate
/lib/modules/2.6.19-ARCH/kernel/lib/zlib_deflate/zlib_deflate.ko
/lib/modules/2.6.19-ARCH/kernel/lib/zlib_inflate
/lib/modules/2.6.19-ARCH/kernel/lib/zlib_inflate/zlib_inflate.ko
/lib/modules/2.6.19-ARCH/modules.alias
/lib/modules/2.6.19-ARCH/modules.dep
/lib/modules/2.6.19-ARCH/modules.symbols
/lib/udev
/lib/udev/ata_id
/lib/udev/cdrom_id
/lib/udev/dasd_id
/lib/udev/edd_id
/lib/udev/firmware.sh
/lib/udev/load-modules.sh
/lib/udev/scsi_id
/lib/udev/usb_id
/lib/udev/vol_id
/proc
/sbin
/sbin/udevd
/sbin/udevsettle
/sbin/udevtrigger
/sys
/usr
/usr/share
/usr/share/kbd
/usr/share/kbd/keymaps
/usr/share/kbd/keymaps/i386
/usr/share/kbd/keymaps/i386/include
/usr/share/kbd/keymaps/i386/include/applkey.map.gz
/usr/share/kbd/keymaps/i386/include/azerty-layout.inc
/usr/share/kbd/keymaps/i386/include/backspace.map.gz
/usr/share/kbd/keymaps/i386/include/ctrl.map.gz
/usr/share/kbd/keymaps/i386/include/euro1.inc
/usr/share/kbd/keymaps/i386/include/euro1.map.gz
/usr/share/kbd/keymaps/i386/include/euro2.map.gz
/usr/share/kbd/keymaps/i386/include/euro.map.gz
/usr/share/kbd/keymaps/i386/include/keypad.map.gz
/usr/share/kbd/keymaps/i386/include/linux-keys-bare.inc
/usr/share/kbd/keymaps/i386/include/linux-keys-extd.inc
/usr/share/kbd/keymaps/i386/include/linux-with-alt-and-altgr.inc
/usr/share/kbd/keymaps/i386/include/linux-with-modeshift-altgr.inc
/usr/share/kbd/keymaps/i386/include/linux-with-two-alt-keys.inc
/usr/share/kbd/keymaps/i386/include/qwerty-layout.inc
/usr/share/kbd/keymaps/i386/include/qwertz-layout.inc
/usr/share/kbd/keymaps/i386/include/unicode.map.gz
/usr/share/kbd/keymaps/i386/include/windowkeys.map.gz
/usr/share/kbd/keymaps/i386/qwerty
/usr/share/kbd/keymaps/i386/qwerty/defkeymap.map.gz
/usr/share/kbd/keymaps/i386/qwerty/defkeymap_V1.0.map.gz
/usr/share/kbd/keymaps/i386/qwertz
/usr/share/kbd/keymaps/i386/qwertz/de_CH-latin1.map.gz
/usr/share/kbd/keymaps/i386/qwertz/de-latin1.map.gz
/usr/share/kbd/keymaps/i386/qwertz/de-latin1-nodeadkeys.map.gz
/usr/share/kbd/keymaps/i386/qwertz/de.map.gz
/usr/share/kbd/keymaps/include
/usr/share/kbd/keymaps/include/compose.8859_7
/usr/share/kbd/keymaps/include/compose.8859_8
/usr/share/kbd/keymaps/include/compose.latin
/usr/share/kbd/keymaps/include/compose.latin1
/usr/share/kbd/keymaps/include/compose.latin2
/usr/share/kbd/keymaps/include/compose.latin3
/usr/share/kbd/keymaps/include/compose.latin4
/usr/share/kbd/keymaps/include/vim-compose.latin1
/usr/share/kbd/keymaps/mac
/usr/share/kbd/keymaps/mac/include
/usr/share/kbd/keymaps/mac/include/mac-azerty-layout.inc
/usr/share/kbd/keymaps/mac/include/mac-euro.map.gz
/usr/share/kbd/keymaps/mac/include/mac-linux-keys-bare.inc
/usr/share/kbd/keymaps/mac/include/mac-qwerty-layout.inc
/usr/share/kbd/keymaps/mac/include/mac-qwertz-layout.inc

You should boot with break=y and investigate what devices exist (echo /sys/block/*), as well as investigate the messages that are spit out. Here is part of the messages I see:

libata version 2.00 loaded.
pata_sis 0000:00:02.5: version 0.4.4
ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xFF00 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xFF08 irq 15
scsi0 : pata_sis
ata1.00: ATA-7, max UDMA/100, 625142448 sectors: LBA48 
ata1.00: ata1: dev 0 multi count 16
ata1.01: ATA-6, max UDMA/100, 234441648 sectors: LBA48 
ata1.01: ata1: dev 1 multi count 16
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/100
scsi1 : pata_sis
ata2.00: ATAPI, max UDMA/33
ata2.01: ATAPI, max MWDMA2
ata2.00: configured for UDMA/33
ata2.01: configured for PIO4
scsi 0:0:0:0: Direct-Access     ATA      ST3320620A       3.AA PQ: 0 ANSI: 5
scsi 0:0:1:0: Direct-Access     ATA      ST3120026A       3.06 PQ: 0 ANSI: 5
scsi 1:0:0:0: CD-ROM            TSSTcorp DVD-ROM SH-D162C TS04 PQ: 0 ANSI: 5
scsi 1:0:1:0: CD-ROM            LITE-ON  LTR-16102B       OS0K PQ: 0 ANSI: 5
SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3
sd 0:0:0:0: Attached scsi disk sda
SCSI device sdb: 234441648 512-byte hdwr sectors (120034 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
SCSI device sdb: 234441648 512-byte hdwr sectors (120034 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
 sdb: sdb1 sdb2 sdb3 < sdb5 sdb6 sdb7 >
sd 0:0:1:0: Attached scsi disk sdb
sr0: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
sr1: scsi3-mmc drive: 129x/40x writer cd/rw xa/form2 cdda tray
sr 1:0:1:0: Attached scsi CD-ROM sr1

I don't use beyond though, but the stock kernel.

deficite · 2007-01-31 04:11:19

I'm going to try the standard kernel out. I don't believe the break=y will work since the kernel panics just as kinit is starting, but I'll try it when I get on my computer anyway.

Thanks.

edit: I tried the standard kernel. Same thing. Break works, but I haven't done a search into the block directory on it yet. I got my image to be the same as yours (I added ata_generic to MODULES) and yet it still doesn't work. I just don't get it. I mean, even the old IDE hook doesn't work. This is frustrating me so much I may either go to an older kernel, build my own kernel, or try out frugalware. I'm probably going to compile my own kernel. Hopefully that'll make it work.

Last edited by deficite (2007-01-31 06:06:12)

brain0 · 2007-01-31 09:48:48

Of course IDE doesn't work if you still have pata_sis in MODULES=. Remove pata_sis and ata_generic from MODULES=, disable the pata hook and reenable the ide hook, then it will use SiS5513 again.

deficite · 2007-02-02 07:17:54

Um....I didn't say I used pata_sis with the ide hook. I actually tried the ide hook before I even knew about pata_sis. The IDE hook gave me the same problem as the pata hook is giving me though.

deficite · 2007-02-05 01:18:20

Well, after putting "sis5513" and "ide_disk" into the MODULES array manually, I can get the ide hook to work. Yay. Now I just hope pata_sis will work before they take the ide subsystem out of the kernel (more than likely. The kernel devs truncate stuff at a glacial rate.) or I get a new computer before then (I want a nForce mobo really bad. I know some people have had problems with it on Linux, but it can't be THAT bad. Plus, nForce mobos are so nice. Our other computer has one and I love it)

Cotton · 2007-05-05 18:06:21

I've had the same problem recently as you described - took a long time to conclude that a missing pata_sis was the culprit. My mkinitcpio.conf is now:

MODULES="usbhid pata_sis"
HOOKS="base udev usb autodetect pata scsi filesystems"

The usbhid was necessary for the usb mouse.

This is with the 2.6.21 kernel (into Current today), so hopefully your problem is now resolvable.

BTW despite the problems, it booted fine with the IDE hook, as long as the kernel26-fallback.img was used.

ravster · 2007-05-05 23:47:34

As far as having your /etc/fstab is concerned, I found that using http://wiki.archlinux.org/index.php/Per … ice_naming is very useful.
I have had problems with the default arch kernels not booting and have given up trying to correct them. Now I always have a working custom kernel on all my systems. Lately the arch kernels have been booting without problems and I use them, and when they stop working I'll use my custom kernel. The custom kernels I make don't use initrds and they still call devices according to the hdX format.
Using persistent block device naming allows me to have a single /etc/fstab no matter what kernel I use.

Arch Linux

#1 2007-01-30 04:39:42

2.6.19 and SiS5513

#2 2007-01-30 08:52:01

Re: 2.6.19 and SiS5513

#3 2007-01-31 04:11:19

Re: 2.6.19 and SiS5513

#4 2007-01-31 09:48:48

Re: 2.6.19 and SiS5513

#5 2007-02-02 07:17:54

Re: 2.6.19 and SiS5513

#6 2007-02-05 01:18:20

Re: 2.6.19 and SiS5513

#7 2007-05-05 18:06:21

Re: 2.6.19 and SiS5513

#8 2007-05-05 23:47:34

Re: 2.6.19 and SiS5513

Board footer