https://bugzilla.novell.com/show_bug.cgi?id=349113 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=349113#c1 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com Status|NEW |NEEDINFO Info Provider| |hibr-list@gmx.de --- Comment #1 from Jeff Mahoney 2008-01-03 10:13:03 MST --- Here's what I see looking at the log: scsi0 : sata_via scsi1 : sata_via ata1: SATA max UDMA/133 cmd 0x0001fc00 ctl 0x0001f802 bmdma 0x0001ec00 irq 20 ata2: SATA max UDMA/133 cmd 0x0001f400 ctl 0x0001f002 bmdma 0x0001ec08 irq 20 ata1: SATA link up 1.5 Gbps (SStatus C722FF03 SControl 0) ata2: SATA link up 1.5 Gbps (SStatus C722FF03 SControl 0) scsi2 : pata_via scsi3 : pata_via ata3: PATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001e800 irq 14 ata4: PATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001e808 irq 15 ata4: port disabled. ignoring. There are two SATA ports and 2 pairs of PATA ports. There are devices attached to the two SATA ports and the first pair of PATA ports. The second pair of PATA ports is disabled. If there is a SATA controller in the system with ports that don't have devices attached, you'd see a message like this (from one of my systems): scsi2 : sata_promise ata3: SATA link down (SStatus 0 SControl 0) This may be a silly question, but are you certain the eSATA connector is attached to a working port? Perhaps the external port is connected to a port that can be used both internally or externally, and it's already used internally? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=349113 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=349113#c3 --- Comment #3 from Jeff Mahoney 2008-01-04 14:25:52 MST --- The message would be printed in dmesg and probably in boot.log as well. When did you capture the dmesg output? Was it with the eSATA disk attached? If so, can you provide dmesg output without the disk attached? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=349113 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=349113#c5 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.provo.novell.com |teheo@novell.com Status|NEEDINFO |NEW Info Provider|hibr-list@gmx.de | --- Comment #5 from Jeff Mahoney 2008-01-07 11:40:39 MST --- Ok, what I'm seeing is that even without the disk connected, the card is reporting link up on both SATA channels. It's only finding a disk on one of them though. I'm going to pass this on to Tejun, since I'm at about the end of my knowledge of SATA here. :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=349113 User hibr-list@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=349113#c7 --- Comment #7 from Hani *** 2008-01-09 13:59:02 MST --- Yes, it does. BIOS recognize the external eSATA as "SATA Master 4". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=349113 User hibr-list@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=349113#c9 --- Comment #9 from Hani *** 2008-01-13 11:46:32 MST --- The PC in question is an ALDI MD 8822. The motherboard is probably a MSI MS-7318 (Medion OEM). The chipset is a VIA P4M890. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=349113 User hibr-list@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=349113#c11 --- Comment #11 from Hani *** 2008-01-17 11:40:29 MST --- No, there is VT8251L. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=349113 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=349113#c13 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |hibr-list@gmx.de --- Comment #13 from Tejun Heo 2008-06-28 01:36:55 MDT --- Sorry about the long delay. Can you please test the following kISO? http://htj.dyndns.org/export/kiso/SL110-i386-bug349113_dbg0.kiso For more information on kISO, please read the followings. http://htj.dyndns.org/export/kiso/SL103-kISO-doc.txt Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=349113 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=349113#c15 --- Comment #15 from Tejun Heo 2008-07-03 20:55:02 MDT --- * What was the error message? * You don't really need to do full install to see whether the patch works. Please do the followings... 1. boot the kISO 2. wait it for to finish loading 3. switch to vc9 (ctrl-alt-f9), it will give you a command shell 4. plug in a usb stick. dmesg will tell you which device node it got assigned. 5. mkdir /mnt/tmp; mount /dev/sdX /mnt/tmp 6. cp /var/log/boot.msg /mnt/tmp; dmesg > /mnt/tmp/dmesg.out 7. umount /mnt/tmp 8. Post the files on the usb stick here. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=349113 User hibr-list@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=349113#c17 --- Comment #17 from Hani *** 2008-07-04 13:52:06 MDT --- Created an attachment (id=226091) --> (https://bugzilla.novell.com/attachment.cgi?id=226091) boot.msg from kISO -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=349113 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=349113#c19 --- Comment #19 from Tejun Heo 2008-07-18 08:03:19 MDT --- Ah... right. dmesg and stuff come online after the installation media is loaded. Sorry about the confusion. Hmm... I'm running out of ideas. I'll prep another debug kernel but not really sure what's going on. What's the model of the external drive? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=349113 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=349113#c21 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|hibr-list@gmx.de | --- Comment #21 from Tejun Heo 2008-07-31 20:35:57 MDT --- VIA is working on both pata_via and sata_via to get some loose ends tied. It seems vt6420 might have had issues with IEN manipulation. I'll update you when I know more. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.