https://bugzilla.novell.com/show_bug.cgi?id=390804 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c1 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |juhliarik@novell.com, jplack@novell.com, | |jsrain@novell.com AssignedTo|jsrain@novell.com |pth@novell.com --- Comment #1 from Jiri Srain 2008-05-16 04:20:36 MST --- show_of_path.sh is part of the lilo package. Jack, if there is anything buggy in YaST, we will need more knowledge about the environment. -- 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=390804 User olh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c3 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |dominik.klein@de.ibm.com --- Comment #3 from Olaf Hering 2008-05-16 05:49:48 MST --- please attach the hwinfo output, and the lsprop -R /proc/device-tree output, and also the getsysinfo output. -- 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=390804 User dominik.klein@de.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c5 --- Comment #5 from Dominik Klein 2008-05-16 06:01:38 MST --- Created an attachment (id=215941) --> (https://bugzilla.novell.com/attachment.cgi?id=215941) Output of lsprop -- 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=390804 User olh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c7 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |dominik.klein@de.ibm.com --- Comment #7 from Olaf Hering 2008-05-16 08:31:16 MST --- cd /sys/block/sda/device cd `pwd -P` This will change to /sys/devices/10000000000.axon/D18000002000.plb5/D18000000160.plb4/14600000000.pcix/pci0000:00/0000:00:02.0/host0/port-0:0/expander-0:0/port-0:0:0/end_device-0:0:0/target0:0:0/0:0:0:0 As you can see, all values are zero. What exactly does the 0,0,0 after the @ in the firmware path mean? -- 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=390804 User olh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c9 --- Comment #9 from Olaf Hering 2008-05-19 08:42:49 MST --- so I need to get the bus,tid,lun from this part of the sysfs path. /host0/port-0:0/expander-0:0/port-0:0:0/end_device-0:0:0/target0:0:0/0:0:0:0/ -- 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=390804 User dominik.klein@de.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c11 --- Comment #11 from Dominik Klein 2008-05-26 06:34:05 MDT --- I'll see what I can find out. -- 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=390804 LTC BugProxy changed: What |Removed |Added ---------------------------------------------------------------------------- CC|LDPSUSE@de.ibm.com |bugproxy@us.ibm.com Partner ID| |LTC 45678 -- 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=390804 LTC BugProxy changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |http:// -- 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=390804 User olh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c15 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |dominik.klein@de.ibm.com --- Comment #15 from Olaf Hering 2008-06-23 08:16:22 MDT --- I move the IO card from a QS21 to a JS22. show_of_path.sh finds a path on the JS22 with SLES10 SP2 and openSuSE 11.0 It seem that there is a bug in the QS21 device-tree. On JS22, there is a directory named 'sas' in the pci-device node. But on the QS21, I see scsi@2 What should be done? I guess the device-tree is incorrect. -- 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=390804 User bugproxy@us.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c17 --- Comment #17 from LTC BugProxy 2008-06-23 14:25:24 MDT --- ------- Comment From jroth@de.ibm.com 2008-06-23 16:21 EDT------- I also had that problem recently when trying to boot a zImage.initrd from a usb-disk. Unfortunately I don't know the exact reason yet. A zImage.initrd works fine when you load it from a tftp server. So I assume that it will work if you put your zImage.initrd on a tftp server and boot it from there with "boot net". Another workaround would be to put yaboot on your PReP partition and supply both, the path to initrd and to the kernel image in your yaboot.conf. Assuming that your PReP partition is /dev/sda1: mkofboot -b /dev/sda1 -i /bin/yaboot -C /etc/yaboot.conf --filesystem raw --force -v -- 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=390804 User bugproxy@us.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c19 --- Comment #19 from LTC BugProxy 2008-06-25 06:34:07 MDT --- ------- Comment From dominik.klein@de.ibm.com 2008-06-25 08:31 EDT------- There might be a shortcut / workaround for this problem. As far as I see it the OF path for the device is only needed if 'nonvram' is *not* set in yaboot.conf. On QS2x however we don't need the NVRAM update so the conversion from the linux device name to the OF device name might be unnecessary. So we could just default to 'nonvram' on QS2x and place the lookup code in a code path that isn't executed in the nonvram case. Would that be a possible workaround or am I missing something? -- 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=390804 User olh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c21 --- Comment #21 from Olaf Hering 2008-07-01 08:17:29 MDT --- Created an attachment (id=225342) --> (https://bugzilla.novell.com/attachment.cgi?id=225342) show_of_path.sh fixed script. but even now, how do I boot from sdb or any sas drive? I created a 0x41 prep boot partition on sda and sdb, put a yaboot in there. devalias shows 'disk1' and 'disk2' for the sas disks. but boot disk2 just gives: 0 > devalias nvram : /axon@10000000000/plb5/plb4/opb/ebc/nvram@2000000 net : /axon@10000000000/plb5/plb4/pcix@4000004600000000/ethernet@1 ohci1 : /axon@30000000000/plb5/plb4/pcix@4000004600000000/usb@1,1 ohci0 : /axon@30000000000/plb5/plb4/pcix@4000004600000000/usb@1 ipmi : /axon@10000000000/plb5/plb4/opb/ebc/ipmi@2600008 pmi : /axon@10000000000/plb5/plb4/opb/ebc/ibm,pmi@2600000 disk2 : /axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2/disk@0,2,1 disk1 : /axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2/disk@0,2,0 net1 : /axon@10000000000/plb5/plb4/pcix@4000004600000000/ethernet@1,1 net0 : /axon@10000000000/plb5/plb4/pcix@4000004600000000/ethernet@1 disk0 : sas ok 0 > boot disk2 Trying to load: from: /axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2/disk@0,2,1 ... . E3404: Not a bootable device! E3407: Load failed ok 0 > boot disk1 Trying to load: from: /axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2/disk@0,2,0 ... . E3404: Not a bootable device! E3407: Load failed ok 0 > -- 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=390804 User bugproxy@us.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c23 --- Comment #23 from LTC BugProxy 2008-07-02 06:01:15 MDT --- ------- Comment From Jens.Osterkamp@de.ibm.com 2008-07-02 07:58 EDT------- Hi Olaf, the script you attached works fine on the test machine I can access here : c1b4:~ # ./bug-390804_show_of_path.sh /dev/sda /proc/device-tree/axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2/disk@0,1,0 c1b4:~ # ./bug-390804_show_of_path.sh /dev/sdb /proc/device-tree/axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2/disk@0,1,1 c1b4:~ # ./bug-390804_show_of_path.sh /dev/sdc /proc/device-tree/axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2/disk@0,1,2 c1b4:~ # ./bug-390804_show_of_path.sh /dev/sdd /proc/device-tree/axon@10000000000/plb5/plb4/pcix@4000004600000000/scsi@2/disk@0,1,3 Thank you for taking care of this so quickly ! -- 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=390804 User bugproxy@us.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c24 --- Comment #24 from LTC BugProxy 2008-07-02 07:41:48 MDT --- ------- Comment From Jens.Osterkamp@de.ibm.com 2008-07-02 09:39 EDT------- Olaf, as soon as there is a new installation iso available that contains this change, can you please let us know so we can give it a try ? 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=390804 User bugproxy@us.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c26 --- Comment #26 from LTC BugProxy 2008-07-03 05:34:01 MDT --- ------- Comment From Jens.Osterkamp@de.ibm.com 2008-07-03 07:30 EDT------- The boot-device variable can be set from userspace with the "nvsetenv" tool from ppc64-utils. ------- Comment From Jens.Osterkamp@de.ibm.com 2008-07-03 07:31 EDT------- (In reply to comment #20)

------- Comment From olh@novell.com 2008-07-02 08:11:43 MDT------- Sure, but it will not help much because the boot-device value can not be updated from Linux. So how do you boot from /dev/sdj (if there are so many disks configured)? The Webinterface offers only 4 harddisks, I think.

@Alexander, can you answer the 2nd part of Olafs question ? 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=390804 User bugproxy@us.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c28 --- Comment #28 from LTC BugProxy 2008-07-03 07:25:23 MDT --- ------- Comment From hannsj_uhl@de.ibm.com 2008-07-03 09:19 EDT------- fyi ... the QS21 IUG (= Installation and Users Guide) can be found at https://www-304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5072382&brandind=5000020 -- 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=390804 User bugproxy@us.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=390804#c30 --- Comment #30 from LTC BugProxy 2008-07-17 04:53:26 MDT --- ------- Comment From Alexander.Gordeev@ru.ibm.com 2008-07-17 06:42 EDT------- (In reply to comment #25)

------- Comment From olh@novell.com 2008-07-03 07:36:26 MDT------- can the 'boot-device' part be automated? I mean, the installer does not show any details about the used disk. So how would one know the SAS address or LUN?

Please implement something that can be used from the Linux side. Preferably reuse the existing 'update firmware boot-device variable via nvsetenv or nvram tool' practice.

Olaf, we're looking into this now. -- 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.