* [FYI] linux 2.6 still not working with PReP (ppc32) @ 2004-12-04 22:45 Christian Kujau 2004-12-05 0:41 ` Sebastian Heutling 0 siblings, 1 reply; 41+ messages in thread From: Christian Kujau @ 2004-12-04 22:45 UTC (permalink / raw) To: linuxppc-dev; +Cc: linux-kernel -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, upon receiving some calls about the status on this issue, i decided to update http://bugme.osdl.org/show_bug.cgi?id=1494 , which i reported a while back. yes, this is "just a PReP" and i am fully aware that PReP is not used in recent setups any more and i too will not my PReP for HPC applications. but perhaps someone has an idea about what's goin on here. the bugreport should give you th full details, in short: linux 2.5.30 is the last working kernel for ppc32/PReP with networking enabled. (net)booting a recent 2.6 kernels spit out lots of these: (with tulip NIC) Dec 3 23:56:39 192.168.10.9 irq 9: nobody cared! Dec 3 23:56:39 192.168.10.9 Call trace: Dec 3 23:56:39 192.168.10.9 [c002e99c] __report_bad_irq+0x34/0xac Dec 3 23:56:39 192.168.10.9 [c002eb00] note_interrupt+0xd0/0x104 Dec 3 23:56:39 192.168.10.9 [c002e480] __do_IRQ+0x174/0x184 Dec 3 23:56:39 192.168.10.9 [c00053e0] do_IRQ+0x38/0x98 Dec 3 23:56:39 192.168.10.9 [c00044cc] ret_from_except+0x0/0x14 Dec 3 23:56:39 192.168.10.9 [c002e748] setup_irq+0xd8/0x138 Dec 3 23:56:39 192.168.10.9 [c002e938] request_irq+0x90/0xc0 Dec 3 23:56:39 192.168.10.9 [c0103504] tulip_open+0x30/0xb6c Dec 3 23:56:39 192.168.10.9 [c0117274] dev_open+0xb0/0xd8 Dec 3 23:56:39 192.168.10.9 [c0118a7c] dev_change_flags+0x6c/0x144 Dec 3 23:56:39 192.168.10.9 [c0123db4] netpoll_setup+0x1c4/0x364 Dec 3 23:56:39 192.168.10.9 [c0106fe0] init_netconsole+0x3c/0x94 Dec 3 23:56:39 192.168.10.9 [c0003a64] init+0xb8/0x230 Dec 3 23:56:39 192.168.10.9 [c0006524] kernel_thread+0x44/0x60 Dec 3 23:56:39 192.168.10.9 handlers: Dec 3 23:56:39 192.168.10.9 [<c010101c>] (tulip_interrupt+0x0/0xd3c) Dec 3 23:56:39 192.168.10.9 Disabling IRQ #9 (with 3c59x NIC) 192.168.10.9 NETDEV WATCHDOG: eth0: transmit timed out 192.168.10.9 eth0: transmit timed out, tx_status 00 status e800. 192.168.10.9 diagnostics: net 0cc0 media 8802 dma 002000b3 fifo 0000 192.168.10.9 eth0: Interrupt posted but not delivered -- IRQ blocked by another device? 192.168.10.9 Flags; bus-master 1, dirty 67(3) current 68(4) 192.168.10.9 Transmit list 806fe480 vs. c06fe3e0. 192.168.10.9 0: @c06fe200 length 80000054 status 00000054 192.168.10.9 1: @c06fe2a0 length 8000005e status 0000005e 192.168.10.9 2: @c06fe340 length 80000064 status 00000064 192.168.10.9 3: @c06fe3e0 length 80000075 status 00000075 192.168.10.9 4: @c06fe480 length 8000005b status 0000005b 192.168.10.9 5: @c06fe520 length 80000051 status 00000051 192.168.10.9 6: @c06fe5c0 length 8000005a status 0000005a 192.168.10.9 7: @c06fe660 length 8000005a status 0000005a 192.168.10.9 8: @c06fe700 length 8000005a status 0000005a 192.168.10.9 9: @c06fe7a0 length 8000005a status 0000005a 192.168.10.9 10: @c06fe840 length 8000005a status 0000005a 192.168.10.9 11: @c06fe8e0 length 8000005a status 0000005a 192.168.10.9 12: @c06fe980 length 8000005a status 0000005a 192.168.10.9 13: @c06fea20 length 8000005a status 0000005a 192.168.10.9 14: @c06feac0 length 8000005a status 0000005a 192.168.10.9 13: @c06fea20 length 8000005a status 0000005a 192.168.10.9 14: @c06feac0 length 8000005a status 0000005a 192.168.10.9 15: @c06feb60 length 8000005a status 0000005a is it possible to use another irq for the network-device driver? Documentation/kernel-parameters.txt gives some options about other drivers, but i can't tell how to specify "use this irq" for tulip/3c59x. especially the "IRQ blocked by another device?" message makes me think, that manual irq config could help here. but maybe i'm wrong. the results posted on http://nerdbynature.de/bits/sheep/2.6.10-rc2/ are from current 2.6 kernels: the offical tree and the linuxppc25 tree was used. thank you for comments, Christian. - -- BOFH excuse #441: Hash table has woodworm -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBsj3y+A7rjkF8z0wRAldLAJ9QFTfr8UeOtXbnSCGWBVJr7IAAKgCgiHRV iB/ozetyCDIMSfAa+1MRxVc= =b5BK -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2004-12-04 22:45 [FYI] linux 2.6 still not working with PReP (ppc32) Christian Kujau @ 2004-12-05 0:41 ` Sebastian Heutling 2004-12-05 17:41 ` Christian Kujau 2004-12-05 19:57 ` [PATCH] linux 2.6 " Christian Kujau 0 siblings, 2 replies; 41+ messages in thread From: Sebastian Heutling @ 2004-12-05 0:41 UTC (permalink / raw) To: linuxppc-dev You got the powerstack booting from scsi (reading and interpreting the bug report). I had problems booting 2.6 kernels as well (never tested any 2.5 kernels). It turned out that the pci slot numbering has changed sometime and this wasn't reflected in arch/ppc/platforms/prep_pci.c. After having set up the slot0...slot8 using the values of slot10...slot18 (except for slot1 which got value 4 so IDE is usable out of the box), the machine booted a 2.6 kernel (2.6.8). Sebastian On Sat, 2004-12-04 at 23:45 +0100, Christian Kujau wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > hi, > > upon receiving some calls about the status on this issue, i decided to > update http://bugme.osdl.org/show_bug.cgi?id=1494 , which i reported a > while back. yes, this is "just a PReP" and i am fully aware that PReP is > not used in recent setups any more and i too will not my PReP for HPC > applications. but perhaps someone has an idea about what's goin on here. > > the bugreport should give you th full details, in short: linux 2.5.30 is > the last working kernel for ppc32/PReP with networking enabled. > (net)booting a recent 2.6 kernels spit out lots of these: > > (with tulip NIC) > Dec 3 23:56:39 192.168.10.9 irq 9: nobody cared! > Dec 3 23:56:39 192.168.10.9 Call trace: > Dec 3 23:56:39 192.168.10.9 [c002e99c] __report_bad_irq+0x34/0xac > Dec 3 23:56:39 192.168.10.9 [c002eb00] note_interrupt+0xd0/0x104 > Dec 3 23:56:39 192.168.10.9 [c002e480] __do_IRQ+0x174/0x184 > Dec 3 23:56:39 192.168.10.9 [c00053e0] do_IRQ+0x38/0x98 > Dec 3 23:56:39 192.168.10.9 [c00044cc] ret_from_except+0x0/0x14 > Dec 3 23:56:39 192.168.10.9 [c002e748] setup_irq+0xd8/0x138 > Dec 3 23:56:39 192.168.10.9 [c002e938] request_irq+0x90/0xc0 > Dec 3 23:56:39 192.168.10.9 [c0103504] tulip_open+0x30/0xb6c > Dec 3 23:56:39 192.168.10.9 [c0117274] dev_open+0xb0/0xd8 > Dec 3 23:56:39 192.168.10.9 [c0118a7c] dev_change_flags+0x6c/0x144 > Dec 3 23:56:39 192.168.10.9 [c0123db4] netpoll_setup+0x1c4/0x364 > Dec 3 23:56:39 192.168.10.9 [c0106fe0] init_netconsole+0x3c/0x94 > Dec 3 23:56:39 192.168.10.9 [c0003a64] init+0xb8/0x230 > Dec 3 23:56:39 192.168.10.9 [c0006524] kernel_thread+0x44/0x60 > Dec 3 23:56:39 192.168.10.9 handlers: > Dec 3 23:56:39 192.168.10.9 [<c010101c>] (tulip_interrupt+0x0/0xd3c) > Dec 3 23:56:39 192.168.10.9 Disabling IRQ #9 > > (with 3c59x NIC) > 192.168.10.9 NETDEV WATCHDOG: eth0: transmit timed out > 192.168.10.9 eth0: transmit timed out, tx_status 00 status e800. > 192.168.10.9 diagnostics: net 0cc0 media 8802 dma 002000b3 fifo 0000 > 192.168.10.9 eth0: Interrupt posted but not delivered -- IRQ blocked by > another device? > 192.168.10.9 Flags; bus-master 1, dirty 67(3) current 68(4) > 192.168.10.9 Transmit list 806fe480 vs. c06fe3e0. > 192.168.10.9 0: @c06fe200 length 80000054 status 00000054 > 192.168.10.9 1: @c06fe2a0 length 8000005e status 0000005e > 192.168.10.9 2: @c06fe340 length 80000064 status 00000064 > 192.168.10.9 3: @c06fe3e0 length 80000075 status 00000075 > 192.168.10.9 4: @c06fe480 length 8000005b status 0000005b > 192.168.10.9 5: @c06fe520 length 80000051 status 00000051 > 192.168.10.9 6: @c06fe5c0 length 8000005a status 0000005a > 192.168.10.9 7: @c06fe660 length 8000005a status 0000005a > 192.168.10.9 8: @c06fe700 length 8000005a status 0000005a > 192.168.10.9 9: @c06fe7a0 length 8000005a status 0000005a > 192.168.10.9 10: @c06fe840 length 8000005a status 0000005a > 192.168.10.9 11: @c06fe8e0 length 8000005a status 0000005a > 192.168.10.9 12: @c06fe980 length 8000005a status 0000005a > 192.168.10.9 13: @c06fea20 length 8000005a status 0000005a > 192.168.10.9 14: @c06feac0 length 8000005a status 0000005a > 192.168.10.9 13: @c06fea20 length 8000005a status 0000005a > 192.168.10.9 14: @c06feac0 length 8000005a status 0000005a > 192.168.10.9 15: @c06feb60 length 8000005a status 0000005a > > is it possible to use another irq for the network-device driver? > Documentation/kernel-parameters.txt gives some options about other > drivers, but i can't tell how to specify "use this irq" for tulip/3c59x. > > especially the "IRQ blocked by another device?" message makes me think, > that manual irq config could help here. but maybe i'm wrong. > > the results posted on http://nerdbynature.de/bits/sheep/2.6.10-rc2/ are > from current 2.6 kernels: the offical tree and the linuxppc25 tree was used. > > thank you for comments, > Christian. > - -- > BOFH excuse #441: > > Hash table has woodworm > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.5 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFBsj3y+A7rjkF8z0wRAldLAJ9QFTfr8UeOtXbnSCGWBVJr7IAAKgCgiHRV > iB/ozetyCDIMSfAa+1MRxVc= > =b5BK > -----END PGP SIGNATURE----- > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2004-12-05 0:41 ` Sebastian Heutling @ 2004-12-05 17:41 ` Christian Kujau 2004-12-06 1:46 ` Sebastian Heutling 2004-12-05 19:57 ` [PATCH] linux 2.6 " Christian Kujau 1 sibling, 1 reply; 41+ messages in thread From: Christian Kujau @ 2004-12-05 17:41 UTC (permalink / raw) To: sheutlin; +Cc: linuxppc-dev, Sven Hartge, linux-kernel [-- Attachment #1: Type: text/plain, Size: 1555 bytes --] -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sebastian Heutling schrieb: > You got the powerstack booting from scsi (reading and interpreting the yes, but now the disk is gone and i have to use nfsroot. > bug report). I had problems booting 2.6 kernels as well (never tested > any 2.5 kernels). It turned out that the pci slot numbering has changed > sometime and this wasn't reflected in arch/ppc/platforms/prep_pci.c. > After having set up the slot0...slot8 using the values of > slot10...slot18 (except for slot1 which got value 4 so IDE is usable out > of the box), the machine booted a 2.6 kernel (2.6.8). boy! this *is* an early christmas present, for sure! how did you come to this conclusion? something *must* have changed in the pci setup after 2.5.30, because the problem did not go away when i used a different NIC driver. but i could not fiddle out the changeset to blame here, because i failed to compile many kernels > 2.5.30. changing one line in arch/ppc/platforms/prep_pci.c made my PReP booting a recent 2.6-BK, patch attached. it's booting now, "init=/bin/bash" is working, but i still can't ping to the outside world, which is still a bit strange, but i hope i can work it out. tausend dank (really), Christian. - -- BOFH excuse #304: routing problems on the neural net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBs0hj+A7rjkF8z0wRAo3RAKDF+QYA6cosLH+kWtiAmiWtRzlQkQCeKcpx FXOiNRfl9/vOynE8d4hDJJg= =sKOm -----END PGP SIGNATURE----- [-- Attachment #2: prep_pci_2.6.10-rc2.patch --] [-- Type: text/x-patch, Size: 499 bytes --] --- linux-2.5-PPC-BK/arch/ppc/platforms/prep_pci.c 2004-12-05 18:20:04.000000000 +0100 +++ linux-2.5-PPC-BK/arch/ppc/platforms/prep_pci.c.edited 2004-12-05 18:21:33.000000000 +0100 @@ -61,7 +61,7 @@ 0, /* Slot 11 - unused */ 5, /* Slot 12 - SCSI - NCR825A */ 0, /* Slot 13 - unused */ - 3, /* Slot 14 - enet */ + 1, /* Slot 14 - enet */ 0, /* Slot 15 - unused */ 2, /* Slot 16 - unused */ 3, /* Slot 17 - unused */ ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2004-12-05 17:41 ` Christian Kujau @ 2004-12-06 1:46 ` Sebastian Heutling 2004-12-06 4:15 ` [FYI] linux 2.6 still not^Wnow " Christian Kujau 0 siblings, 1 reply; 41+ messages in thread From: Sebastian Heutling @ 2004-12-06 1:46 UTC (permalink / raw) To: Christian Kujau; +Cc: linuxppc-dev, Sven Hartge, linux-kernel On Sun, 2004-12-05 at 18:41 +0100, Christian Kujau wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Sebastian Heutling schrieb: > > You got the powerstack booting from scsi (reading and interpreting the > > yes, but now the disk is gone and i have to use nfsroot. > > > bug report). I had problems booting 2.6 kernels as well (never tested > > any 2.5 kernels). It turned out that the pci slot numbering has changed > > sometime and this wasn't reflected in arch/ppc/platforms/prep_pci.c. > > After having set up the slot0...slot8 using the values of > > slot10...slot18 (except for slot1 which got value 4 so IDE is usable out > > of the box), the machine booted a 2.6 kernel (2.6.8). > > boy! this *is* an early christmas present, for sure! how did you come to > this conclusion? something *must* have changed in the pci setup after :-) Pure trial and error in the first time. When realising that something is wrong with the assigned interrupts (looking at the kernel output) we tried to set the ones that were working in a 2.4 kernel. When the machine finally booted a "lspci" showed that the slot number changed. > 2.5.30, because the problem did not go away when i used a different NIC > driver. but i could not fiddle out the changeset to blame here, because i > failed to compile many kernels > 2.5.30. > > changing one line in arch/ppc/platforms/prep_pci.c made my PReP booting a > recent 2.6-BK, patch attached. > > it's booting now, "init=/bin/bash" is working, but i still can't ping to > the outside world, which is still a bit strange, but i hope i can work it out. Is it that onboard network tulip kind of thingy? Do you have some other PCI cards installed? I used to have an extra symbios logic scsi-host-adapter installed. On high network load and loading/writing to a HD (using onboard scsi), I noticed a lot of problems: either the scsi-host-adapter lost the interrupt or the network driver lost some packets or both. After having removed the extra scsi-host-adapter it works fine now. > > tausend dank (really), You are welcome! Sebastian ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not^Wnow working with PReP (ppc32) 2004-12-06 1:46 ` Sebastian Heutling @ 2004-12-06 4:15 ` Christian Kujau 0 siblings, 0 replies; 41+ messages in thread From: Christian Kujau @ 2004-12-06 4:15 UTC (permalink / raw) To: sheutlin; +Cc: linuxppc-dev, Sven Hartge -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sebastian Heutling schrieb: > > Pure trial and error in the first time. When realising that something is > wrong with the assigned interrupts (looking at the kernel output) we > tried to set the ones that were working in a 2.4 kernel. When the > machine finally booted a "lspci" showed that the slot number changed. lspci, sounds easy ;-) but i never would have looked at slot numbering.... > > Is it that onboard network tulip kind of thingy? Do you have some other > PCI cards installed? the card is onboard. since i had some issues with this card in early 2.4 kernels too, i used to have another NIC. in fact, very often i only compiled with 3c59x enabled - OF cared about the onboard NIC (tulip) and once the kernel is loaded, the tulip is not needed any more and 3c59x takes over. http://nerdbynature.de/bits/sheep/2.6.10-rc3/ has some details. > I used to have an extra symbios logic scsi-host-adapter installed. > On high network load and loading/writing to a HD (using onboard scsi), I > noticed a lot of problems: either the scsi-host-adapter lost the > interrupt or the network driver lost some packets or both. After having > removed the extra scsi-host-adapter it works fine now. hm, when i had 3 scsi-disks in this machine (fine IBM ones, hmmmm..) i only used the on-board scsi-bus. there was no other scsi-host-adapter inside, but i noticed the very same problems: upon massive i/o, the machine got stuck for 30sec, sometimes longer, load increased to 30..40 or so, then the machine got back, with a syslog full of scsi errors. it's still so incredible that a 3-liner solved this issue. the bug-report was opened over a year ago... thanks again, Christian. - -- BOFH excuse #13: we're waiting for [the phone company] to fix that line -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBs9zX+A7rjkF8z0wRArwBAKDZ2ywiukQl/b/uPTG1/1jWHrIsxQCeIcKb ltnS8407uSUM+J6jiJABxxc= =Ts4X -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 41+ messages in thread
* [PATCH] linux 2.6 not^Wnow working with PReP (ppc32) 2004-12-05 0:41 ` Sebastian Heutling 2004-12-05 17:41 ` Christian Kujau @ 2004-12-05 19:57 ` Christian Kujau 2004-12-06 18:49 ` Tom Rini 1 sibling, 1 reply; 41+ messages in thread From: Christian Kujau @ 2004-12-05 19:57 UTC (permalink / raw) To: sheutlin; +Cc: linuxppc-dev, Sven Hartge, linux-kernel [-- Attachment #1: Type: text/plain, Size: 577 bytes --] -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 whoops! a bit too early, i had to change 3 lines, not one. Signed-off-by: Christian Kujau <evil@g-house.de> (new patch attached; credits should go to Sebastian Heutling aka sheutlin@gmx.de) thanks, Christian. - -- BOFH excuse #304: routing problems on the neural net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBs2hE+A7rjkF8z0wRAi+3AJ42GZlqMZen6lqMwtyQSMbS61tkbwCeMNET nKgGhTpgwAcCJJ0hWUKoFqg= =xyi5 -----END PGP SIGNATURE----- [-- Attachment #2: prep_pci_renumbered-2.6.10-rc3.patch --] [-- Type: text/x-patch, Size: 793 bytes --] --- linux-2.6-BK/arch/ppc/platforms/prep_pci.c 2004-12-05 20:46:33.000000000 +0100 +++ linux-2.6-BK/arch/ppc/platforms/prep_pci.c.edited 2004-12-05 20:45:55.000000000 +0100 @@ -49,10 +49,10 @@ 0, /* Slot 1 - unused */ 5, /* Slot 2 - SCSI - NCR825A */ 0, /* Slot 3 - unused */ - 1, /* Slot 4 - Ethernet - DEC2114x */ + 3, /* Slot 4 - Ethernet - DEC2114x */ 0, /* Slot 5 - unused */ - 3, /* Slot 6 - PCI Card slot #1 */ - 4, /* Slot 7 - PCI Card slot #2 */ + 2, /* Slot 6 - PCI Card slot #1 */ + 3, /* Slot 7 - PCI Card slot #2 */ 5, /* Slot 8 - PCI Card slot #3 */ 5, /* Slot 9 - PCI Bridge */ /* added here in case we ever support PCI bridges */ ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [PATCH] linux 2.6 not^Wnow working with PReP (ppc32) 2004-12-05 19:57 ` [PATCH] linux 2.6 " Christian Kujau @ 2004-12-06 18:49 ` Tom Rini 2004-12-06 19:33 ` Christian 0 siblings, 1 reply; 41+ messages in thread From: Tom Rini @ 2004-12-06 18:49 UTC (permalink / raw) To: Christian Kujau; +Cc: linuxppc-dev, Sven Hartge, linux-kernel [-- Attachment #1: Type: text/plain, Size: 528 bytes --] On Sun, Dec 05, 2004 at 08:57:57PM +0100, Christian Kujau wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > whoops! a bit too early, i had to change 3 lines, not one. > > > Signed-off-by: Christian Kujau <evil@g-house.de> > > > (new patch attached; credits should go to Sebastian Heutling aka > sheutlin@gmx.de) This doesn't cause anything bad to happen on mine (and it shouldn't, being a Blackhawk and all :)), so I'll send this on. Thanks. -- Tom Rini http://gate.crashing.org/~trini/ [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 189 bytes --] ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [PATCH] linux 2.6 not^Wnow working with PReP (ppc32) 2004-12-06 18:49 ` Tom Rini @ 2004-12-06 19:33 ` Christian 0 siblings, 0 replies; 41+ messages in thread From: Christian @ 2004-12-06 19:33 UTC (permalink / raw) To: linuxppc-dev On Mon, December 6, 2004 19:49, Tom Rini said: > > This doesn't cause anything bad to happen on mine (and it shouldn't, > being a Blackhawk and all :)), so I'll send this on. Thanks. oh, fine! sounds good! thanks, Christian. -- make bzImage, not war ^ permalink raw reply [flat|nested] 41+ messages in thread
* [FYI] linux 2.6 still not working with PReP (ppc32)
@ 2004-12-26 13:35 Marc Dietrich
2004-12-27 2:47 ` Christian
[not found] ` <200501051733.06350.marvin24@gmx.de>
0 siblings, 2 replies; 41+ messages in thread
From: Marc Dietrich @ 2004-12-26 13:35 UTC (permalink / raw)
To: linuxppc-dev
Hi all,
I read this thread about booting a PowerStack with newer kernels. Motivated by
this, I tried to compile a 2.6.10 kernel on my machine (with sym53c825a
onboard). Sadly, the scsi controller always timeouts during initialisation. I
had this problem also with the 2.4er kernels, but this was solved in later
versions (I'm running 2.4.21 now). Now the old driver seem to be removed (or
merged with sym53c8xx_2) and is only available to MCA and GSC devices.
I also tried to change the irq routings in prep_pci.c like in the latest patch
with the sym53c8xx_2 driver,
Slot 12 -> IRQ 15 (sym53c825)
Slot 15 -> IRQ 11 (dec 21140)
but this didn't helped.
Has anyone a working config file for this machine (PowerStack II 4000/Utah)?
Thanks
Marc
^ permalink raw reply [flat|nested] 41+ messages in thread* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2004-12-26 13:35 [FYI] linux 2.6 still not " Marc Dietrich @ 2004-12-27 2:47 ` Christian 2004-12-27 21:37 ` Marc Dietrich 2004-12-31 9:55 ` Sven Luther [not found] ` <200501051733.06350.marvin24@gmx.de> 1 sibling, 2 replies; 41+ messages in thread From: Christian @ 2004-12-27 2:47 UTC (permalink / raw) To: linuxppc-dev; +Cc: Marc Dietrich [-- Attachment #1: Type: text/plain, Size: 1611 bytes --] Marc Dietrich schrieb: > Hi all, > > I read this thread about booting a PowerStack with newer kernels. Motivated by > this, I tried to compile a 2.6.10 kernel on my machine (with sym53c825a > onboard). Sadly, the scsi controller always timeouts during initialisation. I yes, booting is fine now, but i don't have a scsi disk (well, i only need the right cable...) in the PReP and booting diskless atm. > had this problem also with the 2.4er kernels, but this was solved in later > versions (I'm running 2.4.21 now). Now the old driver seem to be removed (or > merged with sym53c8xx_2) and is only available to MCA and GSC devices. yes, i had scsi timeout issues too with 2.4 and early 2.5 kernels. i've never tried newer 2.4 kernels with scsi-disk inside and i am happy to hear that the issues have been resolved. > I also tried to change the irq routings in prep_pci.c like in the latest patch > with the sym53c8xx_2 driver, > Slot 12 -> IRQ 15 (sym53c825) > Slot 15 -> IRQ 11 (dec 21140) > but this didn't helped. i'm still working these out too, gotta find some time... > Has anyone a working config file for this machine (PowerStack II 4000/Utah)? i've found and attached a file called "config-2.6-minimal" from 19-12-2003, linux 2.6.0 was released 17-Dec-2003. in there scsi is enabled, but i doubt i was able to boot this, because of the network issues. however, i only did "yes '' | make oldconfig" from 2.5.30 on, so the scsi part of this .config shouldn't have changed much. thanks, Christian. -- BOFH excuse #387: Your computer's union contract is set to expire at midnight. [-- Attachment #2: config-2.6-minimal --] [-- Type: text/plain, Size: 12079 bytes --] # # Automatically generated make config: don't edit # CONFIG_MMU=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_HAVE_DEC_LOCK=y CONFIG_PPC=y CONFIG_PPC32=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_STANDALONE=y CONFIG_BROKEN_ON_SMP=y # # General setup # CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_IKCONFIG=y # CONFIG_IKCONFIG_PROC is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_IOSCHED_NOOP=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 # CONFIG_6xx=y # CONFIG_40x is not set # CONFIG_44x is not set # CONFIG_POWER3 is not set # CONFIG_POWER4 is not set # CONFIG_8xx is not set # CONFIG_ALTIVEC is not set # CONFIG_TAU is not set # CONFIG_CPU_FREQ is not set # CONFIG_PPC601_SYNC_FIX is not set CONFIG_PPC_STD_MMU=y # # Platform options # CONFIG_PPC_MULTIPLATFORM=y # CONFIG_APUS is not set # CONFIG_WILLOW is not set # CONFIG_PCORE is not set # CONFIG_POWERPMC250 is not set # CONFIG_EV64260 is not set # CONFIG_SPRUCE is not set # CONFIG_LOPEC is not set # CONFIG_MCPN765 is not set # CONFIG_MVME5100 is not set # CONFIG_PPLUS is not set # CONFIG_PRPMC750 is not set # CONFIG_PRPMC800 is not set # CONFIG_SANDPOINT is not set # CONFIG_ADIR is not set # CONFIG_K2 is not set # CONFIG_PAL4 is not set # CONFIG_GEMINI is not set # CONFIG_EST8260 is not set # CONFIG_SBS8260 is not set # CONFIG_RPX6 is not set # CONFIG_TQM8260 is not set CONFIG_PPC_CHRP=y CONFIG_PPC_PMAC=y CONFIG_PPC_PREP=y CONFIG_PPC_OF=y CONFIG_PPCBUG_NVRAM=y # CONFIG_SMP is not set # CONFIG_PREEMPT is not set # CONFIG_HIGHMEM is not set CONFIG_KERNEL_ELF=y CONFIG_BINFMT_ELF=y # CONFIG_BINFMT_MISC is not set CONFIG_PROC_DEVICETREE=y # CONFIG_PPC_RTAS is not set # CONFIG_PREP_RESIDUAL is not set CONFIG_CMDLINE_BOOL=y CONFIG_CMDLINE="root=/dev/sda5 2" # # Bus options # # CONFIG_ISA is not set CONFIG_GENERIC_ISA_DMA=y CONFIG_PCI=y CONFIG_PCI_DOMAINS=y # CONFIG_PCI_LEGACY_PROC is not set CONFIG_PCI_NAMES=y # CONFIG_HOTPLUG is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Advanced setup # # CONFIG_ADVANCED_OPTIONS is not set # # Default settings for advanced configuration options are used # CONFIG_HIGHMEM_START=0xfe000000 CONFIG_LOWMEM_SIZE=0x30000000 CONFIG_KERNEL_START=0xc0000000 CONFIG_TASK_SIZE=0x80000000 CONFIG_BOOT_LOAD=0x00800000 # # Generic Driver Options # # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Plug and Play support # # CONFIG_PNP is not set # # Block devices # # CONFIG_BLK_DEV_FD 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 is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_LBD is not set # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # # ATA/ATAPI/MFM/RLL support # # CONFIG_IDE is not set # # SCSI device support # CONFIG_SCSI=y # CONFIG_SCSI_PROC_FS is not set # # 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 is not set # CONFIG_CHR_DEV_SG is not set # # 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_ADVANSYS is not set # CONFIG_SCSI_MEGARAID is not set # CONFIG_SCSI_SATA 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_INIA100 is not set CONFIG_SCSI_SYM53C8XX_2=y CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0 CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16 CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64 # CONFIG_SCSI_SYM53C8XX_IOMAPPED 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_NSP32 is not set # CONFIG_SCSI_DEBUG is not set # CONFIG_SCSI_MESH is not set # CONFIG_SCSI_MAC53C94 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=y # CONFIG_NETLINK_DEV is not set CONFIG_UNIX=y # CONFIG_NET_KEY is not set 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 is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_IPV6 is not set # CONFIG_DECNET is not set # CONFIG_BRIDGE is not set # CONFIG_NETFILTER is not set # # 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_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK 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 # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y # CONFIG_MII is not set # CONFIG_MACE is not set # CONFIG_BMAC is not set # CONFIG_OAKNET is not set # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=m # CONFIG_TYPHOON is not set # # Tulip family network device support # CONFIG_NET_TULIP=y CONFIG_DE2104X=m CONFIG_TULIP=m # CONFIG_TULIP_MWI is not set # CONFIG_TULIP_MMIO is not set CONFIG_DE4X5=m # CONFIG_WINBOND_840 is not set # CONFIG_DM9102 is not set # CONFIG_HP100 is not set # CONFIG_NET_PCI 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_SIS190 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_PPP is not set # CONFIG_SLIP is not set # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Token Ring devices # # CONFIG_TR is not set # 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 # # Bluetooth support # # CONFIG_BT is not set # # ISDN subsystem # # CONFIG_ISDN_BOOL is not set # # Graphics support # # CONFIG_FB is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_MDA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y # # Input device support # CONFIG_INPUT=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set # CONFIG_INPUT_EVDEV is not set # CONFIG_INPUT_EVBUG is not set # # Input I/O drivers # # CONFIG_GAMEPORT is not set CONFIG_SOUND_GAMEPORT=y CONFIG_SERIO=y CONFIG_SERIO_I8042=y # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 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 is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Macintosh device drivers # # CONFIG_ADB_CUDA is not set # CONFIG_ADB_PMU is not set # CONFIG_MAC_FLOPPY is not set # CONFIG_MAC_SERIAL is not set # CONFIG_ADB 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 is not set # # Non-8250 serial port support # # CONFIG_SERIAL_PMACZILOG is not set CONFIG_UNIX98_PTYS=y CONFIG_UNIX98_PTY_COUNT=256 # # I2C support # # CONFIG_I2C is not set # # I2C Algorithms # # # I2C Hardware Bus support # # # I2C Hardware Sensors Chip support # # CONFIG_I2C_SENSOR is not set # # 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_NVRAM is not set CONFIG_GEN_RTC=m CONFIG_GEN_RTC_X=y # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_AGP is not set # CONFIG_DRM is not set # CONFIG_RAW_DRIVER is not set # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # CONFIG_DVB 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 is not set # CONFIG_ROMFS_FS is not set # CONFIG_QUOTA is not set # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # # CD-ROM/DVD Filesystems # # CONFIG_ISO9660_FS is not set # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # # CONFIG_FAT_FS is not set # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y # CONFIG_DEVFS_FS is not set CONFIG_DEVPTS_FS=y # CONFIG_DEVPTS_FS_XATTR is not set CONFIG_TMPFS=y # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # 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 is not set CONFIG_MSDOS_PARTITION=y # # Sound # # CONFIG_SOUND is not set # # USB support # # CONFIG_USB is not set # CONFIG_USB_GADGET is not set # # Library routines # CONFIG_CRC32=m # # Kernel hacking # CONFIG_DEBUG_KERNEL=y # CONFIG_DEBUG_SLAB is not set CONFIG_MAGIC_SYSRQ=y # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_KGDB is not set CONFIG_XMON=y # CONFIG_BDI_SWITCH is not set # CONFIG_DEBUG_INFO is not set CONFIG_BOOTX_TEXT=y # # Security options # # CONFIG_SECURITY is not set # # Cryptographic options # # CONFIG_CRYPTO is not set ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2004-12-27 2:47 ` Christian @ 2004-12-27 21:37 ` Marc Dietrich 2005-01-02 0:31 ` Sebastian Heutling 2004-12-31 9:55 ` Sven Luther 1 sibling, 1 reply; 41+ messages in thread From: Marc Dietrich @ 2004-12-27 21:37 UTC (permalink / raw) To: Christian; +Cc: linuxppc-dev [-- Attachment #1: Type: text/plain, Size: 3220 bytes --] Hallo Christian, Am Montag, 27. Dezember 2004 03:47 schrieben Sie: > Marc Dietrich schrieb: > > > I also tried to change the irq routings in prep_pci.c like in the latest > > patch with the sym53c8xx_2 driver, > > Slot 12 -> IRQ 15 (sym53c825) > > Slot 15 -> IRQ 11 (dec 21140) > > but this didn't helped. > > i'm still working these out too, gotta find some time... maybe this helps: I used the config file you sent me (and added serial console). when booting a working 2.4.24-pre1 I get: [...] PCI: Probing PCI hardware Setting PCI interrupts for a "Utah (Powerstack II Pro4000)" PCI: moved device 00:0b.1 resource 4 (101) to 1480 PCI: moved device 00:0b.1 resource 5 (101) to 1490 PCI: moved device 00:11.0 resource 0 (1208) to 0 [...] SCSI subsystem driver Revision: 1.00 new devtbl [4096] @c049e000. PCI: Enabling device 00:0c.0 (0000 -> 0003) sym53c8xx: at PCI bus 0, device 12, function 0 sym53c8xx: setting PCI_COMMAND_MASTER PCI_COMMAND_PARITY...(fix-up) sym53c8xx: changing PCI_LATENCY_TIMER from 0 to 80. sym53c8xx: 53c825a detected sym53c825a-0: rev 0x13 on pci bus 0 device 12 function 0 irq 15 new MPOOL [ 188] @c049f000. new VTOB [ 12] @c049f100. new NCB [2408] @c049c000. new SQUEUE [2336] @c049d000. new VTOB [ 12] @c049f110. new DQUEUE [2336] @c049a000. new TARGTBL [ 256] @c049b000. new VTOB [ 12] @c049f120. new SCRIPT [3504] @c0498000. new SCRIPTH [1504] @c049b800. new CCB [1300] @c0499000. sym53c825a-0: ID 7, Fast-10, Parity Checking while booting a non working 2.6.10 I get: I already changed the irq of slot 12 to 15 and slot 14 to irq 11. [...] PCI: Probing PCI hardware Setting PCI interrupts for a "Utah (Powerstack II Pro4000)" PCI: Cannot allocate resource region 5 of device 0000:00:01.1 SCSI subsystem initialized [...] PCI: Enabling device 0000:00:02.0 (0000 -> 0003) sym0: <825a> rev 0x13 at pci 0000:00:02.0 irq 15 new MPOOL [ 180] @c7d99000. new VTOB [ 12] @c7d99100. new HCB [1784] @c7d9a000. sym0: No NVRAM, ID 7, Fast-10, SE, parity checking new VTOB [ 12] @c7d99110. new SQUEUE [3600] @c7d9b000. new VTOB [ 12] @c7d99120. new DQUEUE [3600] @c7d9c000. new TARGTBL [ 256] @c7d9a800. new VTOB [ 12] @c7d99130. new SCRIPTA0 [3024] @c7d9d000. new VTOB [ 12] @c7d99140. new SCRIPTB0 [1324] @c7d9e000. new SCRIPTZ0 [ 32] @c7d9a900. new CCBH [1024] @c7d99400. new CCB [ 988] @c7d9ac00. new SNS_BBUF [ 32] @c7d9a920. [...] new BADLUNTBL [ 256] @c7d9aa00. sym0: SCSI BUS has been reset. scsi0 : sym-2.1.18m elevator: using anticipatory as default io scheduler sym0:0:0:ccb @c7d9ac00 using tag 256. sym0: queuepos=2. sym0:0:0: ABORT operation started. sym0:0:0: ABORT operation timed-out. sym0:0:0: DEVICE RESET operation started. sym0:0:0: DEVICE RESET operation timed-out. sym0:0:0: BUS RESET operation started. sym0:0:0: BUS RESET operation timed-out. sym0:0:0: HOST RESET operation started. sym0:0:0:ccb @c7d9ac00 freeing tag 256. sym0: SCSI BUS has been reset. [ hangs here ] Indeed, there seems to be something wrong with the pci resources - but I can't say what. I attached the compete boot logs. I also attached the lspci -v output. Greetings Marc [-- Attachment #2: boot.log-2.4.24-pre1.bz2 --] [-- Type: application/x-bzip2, Size: 3130 bytes --] [-- Attachment #3: boot.log-2.6.10.bz2 --] [-- Type: application/x-bzip2, Size: 1181 bytes --] [-- Attachment #4: lspci-v --] [-- Type: text/plain, Size: 2348 bytes --] 00:0b.0 ISA bridge: Symphony Labs W83C553 (rev 10) Flags: bus master, medium devsel, latency 0 00:0b.1 IDE interface: Symphony Labs SL82c105 (rev 05) (prog-if 8f [Master SecP SecO PriP PriO]) Flags: medium devsel I/O ports at 01f0 [disabled] [size=8] I/O ports at 03f4 [disabled] [size=4] I/O ports at 0170 [disabled] [size=8] I/O ports at 0374 [disabled] [size=4] I/O ports at 1480 [disabled] [size=16] I/O ports at 1490 [disabled] [size=16] 00:0c.0 SCSI storage controller: LSI Logic / Symbios Logic 53c825 (rev 13) Flags: bus master, medium devsel, latency 80, IRQ 15 I/O ports at 1000 [size=256] Memory at c200c000 (32-bit, non-prefetchable) [size=256] Memory at c200d000 (32-bit, non-prefetchable) [size=4K] 00:0e.0 Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 22) Flags: bus master, medium devsel, latency 0, IRQ 11 I/O ports at 1400 [size=128] Memory at c200e000 (32-bit, non-prefetchable) [size=128] Expansion ROM at c1040000 [disabled] [size=256K] 00:11.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00 [VGA]) Flags: medium devsel, IRQ 11 Memory at c0000000 (32-bit, prefetchable) [size=16M] Expansion ROM at c2000000 [disabled] [size=32K] 00:12.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) (prog-if 10 [OHCI]) Subsystem: ALi Corporation USB 1.1 Controller Flags: 66Mhz, medium devsel, IRQ 15 Memory at c2008000 (32-bit, non-prefetchable) [disabled] [size=4K] Capabilities: <available only to root> 00:12.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) (prog-if 10 [OHCI]) Subsystem: ALi Corporation USB 1.1 Controller Flags: 66Mhz, medium devsel, IRQ 15 Memory at c2009000 (32-bit, non-prefetchable) [disabled] [size=4K] Capabilities: <available only to root> 00:12.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) (prog-if 10 [OHCI]) Subsystem: ALi Corporation USB 1.1 Controller Flags: 66Mhz, medium devsel, IRQ 15 Memory at c200a000 (32-bit, non-prefetchable) [disabled] [size=4K] Capabilities: <available only to root> 00:12.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01) (prog-if 20 [EHCI]) Subsystem: ALi Corporation USB 2.0 Controller Flags: 66Mhz, medium devsel, IRQ 15 Memory at c200b000 (32-bit, non-prefetchable) [disabled] [size=256] Capabilities: <available only to root> ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2004-12-27 21:37 ` Marc Dietrich @ 2005-01-02 0:31 ` Sebastian Heutling 2005-01-03 12:26 ` Marc Dietrich 0 siblings, 1 reply; 41+ messages in thread From: Sebastian Heutling @ 2005-01-02 0:31 UTC (permalink / raw) To: Marc Dietrich; +Cc: linuxppc-dev [-- Attachment #1: Type: text/plain, Size: 4438 bytes --] Hi Marc, On Mon, 2004-12-27 at 22:37 +0100, Marc Dietrich wrote: > Hallo Christian, > > Am Montag, 27. Dezember 2004 03:47 schrieben Sie: > > Marc Dietrich schrieb: > > > > > I also tried to change the irq routings in prep_pci.c like in the latest > > > patch with the sym53c8xx_2 driver, > > > Slot 12 -> IRQ 15 (sym53c825) > > > Slot 15 -> IRQ 11 (dec 21140) > > > but this didn't helped. > > > > i'm still working these out too, gotta find some time... > > maybe this helps: > > I used the config file you sent me (and added serial console). > > when booting a working 2.4.24-pre1 I get: > > [...] > PCI: Probing PCI hardware > Setting PCI interrupts for a "Utah (Powerstack II Pro4000)" > PCI: moved device 00:0b.1 resource 4 (101) to 1480 > PCI: moved device 00:0b.1 resource 5 (101) to 1490 > PCI: moved device 00:11.0 resource 0 (1208) to 0 > [...] > SCSI subsystem driver Revision: 1.00 > new devtbl [4096] @c049e000. > PCI: Enabling device 00:0c.0 (0000 -> 0003) > sym53c8xx: at PCI bus 0, device 12, function 0 > sym53c8xx: setting PCI_COMMAND_MASTER PCI_COMMAND_PARITY...(fix-up) > sym53c8xx: changing PCI_LATENCY_TIMER from 0 to 80. > sym53c8xx: 53c825a detected > sym53c825a-0: rev 0x13 on pci bus 0 device 12 function 0 irq 15 > new MPOOL [ 188] @c049f000. > new VTOB [ 12] @c049f100. > new NCB [2408] @c049c000. > new SQUEUE [2336] @c049d000. > new VTOB [ 12] @c049f110. > new DQUEUE [2336] @c049a000. > new TARGTBL [ 256] @c049b000. > new VTOB [ 12] @c049f120. > new SCRIPT [3504] @c0498000. > new SCRIPTH [1504] @c049b800. > new CCB [1300] @c0499000. > sym53c825a-0: ID 7, Fast-10, Parity Checking > > > while booting a non working 2.6.10 I get: > > I already changed the irq of slot 12 to 15 and slot 14 to irq 11. You don't really need to change any IRQ above slot 9 on a 2.6.? kernel because the slot is 2 (while it was on 12 in 2.4 kernels). > > [...] > PCI: Probing PCI hardware > Setting PCI interrupts for a "Utah (Powerstack II Pro4000)" > PCI: Cannot allocate resource region 5 of device 0000:00:01.1 This is the IDE chip which gets IRQ 0 and therefore results in an error. Try changing the value of Slot 1 from 0 to 4 (which is IRQ 14). I don't really think it changes the SCSI timeouts maybe it helps - no one knows for sure ;). > SCSI subsystem initialized > [...] > PCI: Enabling device 0000:00:02.0 (0000 -> 0003) > sym0: <825a> rev 0x13 at pci 0000:00:02.0 irq 15 > new MPOOL [ 180] @c7d99000. > new VTOB [ 12] @c7d99100. > new HCB [1784] @c7d9a000. > sym0: No NVRAM, ID 7, Fast-10, SE, parity checking > new VTOB [ 12] @c7d99110. > new SQUEUE [3600] @c7d9b000. > new VTOB [ 12] @c7d99120. > new DQUEUE [3600] @c7d9c000. > new TARGTBL [ 256] @c7d9a800. > new VTOB [ 12] @c7d99130. > new SCRIPTA0 [3024] @c7d9d000. > new VTOB [ 12] @c7d99140. > new SCRIPTB0 [1324] @c7d9e000. > new SCRIPTZ0 [ 32] @c7d9a900. > new CCBH [1024] @c7d99400. > new CCB [ 988] @c7d9ac00. > new SNS_BBUF [ 32] @c7d9a920. > [...] > new BADLUNTBL [ 256] @c7d9aa00. > sym0: SCSI BUS has been reset. > scsi0 : sym-2.1.18m > elevator: using anticipatory as default io scheduler > sym0:0:0:ccb @c7d9ac00 using tag 256. > sym0: queuepos=2. > sym0:0:0: ABORT operation started. > sym0:0:0: ABORT operation timed-out. > sym0:0:0: DEVICE RESET operation started. > sym0:0:0: DEVICE RESET operation timed-out. > sym0:0:0: BUS RESET operation started. > sym0:0:0: BUS RESET operation timed-out. > sym0:0:0: HOST RESET operation started. > sym0:0:0:ccb @c7d9ac00 freeing tag 256. > sym0: SCSI BUS has been reset. > [ hangs here ] Hmmm strange ... is there anything attached on scsi? > Indeed, there seems to be something wrong with the pci resources - but I can't > say what. I attached the compete boot logs. I also attached the lspci -v > output. ... wait a second ... looking at the lspci output ... you use a USB PCI card? The IRQ-sharing doesn't work well and the USB PCI card is on the same slot as the SCSI controller resulting in both using the same IRQ. Remove the USB card and check wether it changes anything. If it does work now: Did it ever work with USB using another kernel? If so maybe there is something else wrong, if not it's a HW Problem. I also attached a config file from my powerstack (which I use as a router and runs a 2.6 kernel since june last year or so) Sebastian Heutling [-- Attachment #2: config-powerstack --] [-- Type: text/plain, Size: 27391 bytes --] # # Automatically generated make config: don't edit # CONFIG_MMU=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_HAVE_DEC_LOCK=y CONFIG_PPC=y CONFIG_PPC32=y CONFIG_GENERIC_NVRAM=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # CONFIG_CLEAN_COMPILE is not set CONFIG_BROKEN=y CONFIG_BROKEN_ON_SMP=y # # General setup # CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_POSIX_MQUEUE is not set # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HOTPLUG=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor # CONFIG_6xx=y # CONFIG_40x is not set # CONFIG_44x is not set # CONFIG_POWER3 is not set # CONFIG_POWER4 is not set # CONFIG_8xx is not set # CONFIG_E500 is not set # CONFIG_ALTIVEC is not set # CONFIG_TAU is not set # CONFIG_CPU_FREQ is not set # CONFIG_PPC601_SYNC_FIX is not set CONFIG_PPC_STD_MMU=y # # Platform options # CONFIG_PPC_MULTIPLATFORM=y # CONFIG_APUS is not set # CONFIG_WILLOW is not set # CONFIG_PCORE is not set # CONFIG_POWERPMC250 is not set # CONFIG_EV64260 is not set # CONFIG_SPRUCE is not set # CONFIG_LOPEC is not set # CONFIG_MCPN765 is not set # CONFIG_MVME5100 is not set # CONFIG_PPLUS is not set # CONFIG_PRPMC750 is not set # CONFIG_PRPMC800 is not set # CONFIG_SANDPOINT is not set # CONFIG_ADIR is not set # CONFIG_K2 is not set # CONFIG_PAL4 is not set # CONFIG_GEMINI is not set # CONFIG_EST8260 is not set # CONFIG_SBC82xx is not set # CONFIG_SBS8260 is not set # CONFIG_RPX8260 is not set # CONFIG_TQM8260 is not set # CONFIG_ADS8272 is not set # CONFIG_LITE5200 is not set CONFIG_PPC_CHRP=y CONFIG_PPC_PMAC=y CONFIG_PPC_PREP=y CONFIG_PPC_OF=y CONFIG_PPCBUG_NVRAM=y # CONFIG_SMP is not set CONFIG_PREEMPT=y # CONFIG_HIGHMEM is not set CONFIG_KERNEL_ELF=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m CONFIG_PROC_DEVICETREE=y CONFIG_PREP_RESIDUAL=y CONFIG_PROC_PREPRESIDUAL=y CONFIG_CMDLINE_BOOL=y CONFIG_CMDLINE="root=/dev/sda2 console=ttyS0" # # Bus options # CONFIG_ISA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_PCI=y CONFIG_PCI_DOMAINS=y # CONFIG_PCI_LEGACY_PROC is not set CONFIG_PCI_NAMES=y # # PCMCIA/CardBus support # # CONFIG_PCMCIA is not set CONFIG_PCMCIA_PROBE=y # # Advanced setup # CONFIG_ADVANCED_OPTIONS=y CONFIG_HIGHMEM_START=0xfe000000 # CONFIG_LOWMEM_SIZE_BOOL is not set CONFIG_LOWMEM_SIZE=0x30000000 # CONFIG_KERNEL_START_BOOL is not set CONFIG_KERNEL_START=0xc0000000 # CONFIG_TASK_SIZE_BOOL is not set CONFIG_TASK_SIZE=0x80000000 CONFIG_BOOT_LOAD=0x00800000 # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y # CONFIG_PREVENT_FIRMWARE_BUILD is not set # CONFIG_FW_LOADER is not set # CONFIG_DEBUG_DRIVER 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 is not set # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_OTHER is not set CONFIG_PARPORT_1284=y # # Plug and Play support # CONFIG_PNP=y # CONFIG_PNP_DEBUG is not set # # Protocols # CONFIG_ISAPNP=y # # Block devices # CONFIG_BLK_DEV_FD=m # CONFIG_MAC_FLOPPY is not set # CONFIG_BLK_DEV_XD is not set # 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=y # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 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_IDE_SATA is not set CONFIG_BLK_DEV_IDEDISK=y # CONFIG_IDEDISK_MULTI_MODE is not set CONFIG_BLK_DEV_IDECD=m # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set # CONFIG_IDE_TASK_IOCTL is not set # CONFIG_IDE_TASKFILE_IO is not set # # IDE chipset support/bugfixes # CONFIG_IDE_GENERIC=y # CONFIG_BLK_DEV_IDEPNP 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_SL82C105=y CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDEDMA_FORCED is not set CONFIG_IDEDMA_PCI_AUTO=y # CONFIG_IDEDMA_ONLYDISK 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 is not set # 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=m # CONFIG_PDC202XX_BURST is not set CONFIG_BLK_DEV_PDC202XX_NEW=m # CONFIG_PDC202XX_FORCE is not set # CONFIG_BLK_DEV_SVWKS is not set # CONFIG_BLK_DEV_SIIMAGE is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_VIA82CXXX is not set # CONFIG_BLK_DEV_IDE_PMAC is not set # CONFIG_IDE_ARM is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_IVB is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_HD is not set # # SCSI device support # CONFIG_SCSI=y CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y CONFIG_CHR_DEV_ST=y # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=y CONFIG_BLK_DEV_SR_VENDOR=y CONFIG_CHR_DEV_SG=y # CONFIG_CHR_DEV_SCH is not set # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set CONFIG_SCSI_CONSTANTS=y # CONFIG_SCSI_LOGGING is not set # # SCSI Transport Attributes # CONFIG_SCSI_SPI_ATTRS=y # CONFIG_SCSI_FC_ATTRS is not set # # SCSI low-level drivers # # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_3W_9XXX is not set # CONFIG_SCSI_7000FASST is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AHA152X is not set # CONFIG_SCSI_AHA1542 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_IN2000 is not set # CONFIG_SCSI_MEGARAID is not set # CONFIG_SCSI_SATA is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_CPQFCTS is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_DTC3280 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_GENERIC_NCR5380 is not set # CONFIG_SCSI_GENERIC_NCR5380_MMIO 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 is not set # CONFIG_SCSI_NCR53C406A is not set CONFIG_SCSI_SYM53C8XX_2=y CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0 CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16 CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64 # CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_PAS16 is not set # CONFIG_SCSI_PCI2000 is not set # CONFIG_SCSI_PCI2220I is not set # CONFIG_SCSI_PSI240I is not set # CONFIG_SCSI_QLOGIC_FAS 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_SYM53C416 is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_T128 is not set # CONFIG_SCSI_U14_34F is not set # CONFIG_SCSI_NSP32 is not set # CONFIG_SCSI_DEBUG is not set # CONFIG_SCSI_MESH is not set # CONFIG_SCSI_MAC53C94 is not set # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI 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 # # CONFIG_IEEE1394 is not set # # I2O device support # # CONFIG_I2O is not set # # Macintosh device drivers # # CONFIG_ADB is not set # CONFIG_ADB_CUDA is not set # CONFIG_ADB_PMU is not set # CONFIG_MAC_SERIAL 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 is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_FWMARK=y CONFIG_IP_ROUTE_NAT=y CONFIG_IP_ROUTE_MULTIPATH=y CONFIG_IP_ROUTE_TOS=y # CONFIG_IP_ROUTE_VERBOSE is not set CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y CONFIG_IP_PNP_BOOTP=y CONFIG_IP_PNP_RARP=y # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set CONFIG_SYN_COOKIES=y # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # # IP: Virtual Server Configuration # # CONFIG_IP_VS is not set # CONFIG_IPV6 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_IPRANGE is not set 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 is not set 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_OWNER=m CONFIG_IP_NF_FILTER=m CONFIG_IP_NF_TARGET_REJECT=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_TARGET_NETMAP is not set # CONFIG_IP_NF_TARGET_SAME is not set # 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_CLASSIFY is not set 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 is not set # CONFIG_IP_NF_COMPAT_IPCHAINS is not set # CONFIG_IP_NF_COMPAT_IPFWADM is not set # CONFIG_IP_NF_RAW is not set # CONFIG_IP_NF_MATCH_ADDRTYPE is not set # CONFIG_IP_NF_MATCH_REALM is not set # # SCTP Configuration (EXPERIMENTAL) # # CONFIG_IP_SCTP is not set # CONFIG_ATM is not set # CONFIG_BRIDGE is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set CONFIG_LLC=m # CONFIG_LLC2 is not set # CONFIG_IPX is not set CONFIG_ATALK=m # CONFIG_DEV_APPLETALK 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_HW_FLOWCONTROL is not set # # QoS and/or fair queueing # CONFIG_NET_SCHED=y CONFIG_NET_SCH_CLK_JIFFIES=y # CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set # CONFIG_NET_SCH_CLK_CPU is not set # CONFIG_NET_SCH_CBQ is not set # CONFIG_NET_SCH_HTB is not set # CONFIG_NET_SCH_HFSC is not set # CONFIG_NET_SCH_PRIO is not set # CONFIG_NET_SCH_RED is not set # CONFIG_NET_SCH_SFQ is not set # CONFIG_NET_SCH_TEQL is not set # CONFIG_NET_SCH_TBF is not set # CONFIG_NET_SCH_GRED is not set # CONFIG_NET_SCH_DSMARK is not set # CONFIG_NET_SCH_NETEM is not set # CONFIG_NET_SCH_INGRESS is not set CONFIG_NET_QOS=y CONFIG_NET_ESTIMATOR=y # CONFIG_NET_CLS is not set # CONFIG_NET_CLS_ROUTE is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set CONFIG_NETDEVICES=y # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # CONFIG_NET_SB1000 is not set # # ARCnet devices # # CONFIG_ARCNET is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=m # CONFIG_MACE is not set # CONFIG_BMAC is not set # CONFIG_OAKNET is not set # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set # CONFIG_NET_VENDOR_3COM is not set # CONFIG_LANCE is not set # CONFIG_NET_VENDOR_SMC is not set # CONFIG_NET_VENDOR_RACAL is not set # # Tulip family network device support # CONFIG_NET_TULIP=y CONFIG_DE2104X=m CONFIG_TULIP=m # CONFIG_TULIP_MWI is not set # CONFIG_TULIP_MMIO is not set # CONFIG_TULIP_NAPI is not set # CONFIG_DE4X5 is not set # CONFIG_WINBOND_840 is not set # CONFIG_DM9102 is not set # CONFIG_AT1700 is not set # CONFIG_DEPCA is not set # CONFIG_HP100 is not set # CONFIG_NET_ISA 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_AC3200 is not set # CONFIG_APRICOT is not set # CONFIG_B44 is not set # CONFIG_FORCEDETH is not set # CONFIG_CS89x0 is not set CONFIG_EEPRO100=m # CONFIG_EEPRO100_PIO is not set # CONFIG_E100 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set CONFIG_NE2K_PCI=m # CONFIG_8139CP is not set # CONFIG_8139TOO is not set # CONFIG_SIS900 is not set CONFIG_EPIC100=m # CONFIG_SUNDANCE is not set # CONFIG_TLAN is not set # CONFIG_VIA_RHINE is not set # CONFIG_VIA_VELOCITY is not set # CONFIG_NET_POCKET is not set # # Ethernet (1000 Mbit) # # 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 # CONFIG_MV64340_ETH is not set # # Ethernet (10000 Mbit) # # CONFIG_IXGB is not set # CONFIG_S2IO is not set # # Token Ring devices # # CONFIG_TR is not set # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Wan interfaces # # CONFIG_WAN 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=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m CONFIG_PPPOE=m # CONFIG_SLIP is not set # CONFIG_NET_FC is not set # CONFIG_SHAPER is not set # CONFIG_NETCONSOLE is not set # # ISDN subsystem # # CONFIG_ISDN 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=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_MOUSEDEV_PSAUX_ENABLE=y # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input I/O drivers # # CONFIG_GAMEPORT is not set CONFIG_SOUND_GAMEPORT=y 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_LKKBD 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=m # CONFIG_MOUSE_INPORT is not set # CONFIG_MOUSE_LOGIBM is not set # CONFIG_MOUSE_PC110PAD is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC 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=y CONFIG_SERIAL_8250_NR_UARTS=4 # CONFIG_SERIAL_8250_EXTENDED is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y # CONFIG_SERIAL_PMACZILOG is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # CONFIG_PRINTER is not set # CONFIG_PPDEV is not set # CONFIG_TIPAR is not set # CONFIG_QIC02_TAPE is not set # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set CONFIG_NVRAM=y CONFIG_GEN_RTC=m CONFIG_GEN_RTC_X=y # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # # Ftape, the floppy tape device driver # # CONFIG_AGP is not set # CONFIG_DRM is not set # CONFIG_RAW_DRIVER is not set # # I2C support # # CONFIG_I2C is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Misc devices # # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set # # Graphics support # CONFIG_FB=y CONFIG_FB_CIRRUS=y # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_OF is not set # CONFIG_FB_CONTROL is not set # CONFIG_FB_PLATINUM is not set # CONFIG_FB_VALKYRIE is not set # CONFIG_FB_CT65550 is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_S3TRIO is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_RIVA is not set CONFIG_FB_MATROX=y CONFIG_FB_MATROX_MILLENIUM=y # CONFIG_FB_MATROX_MYSTIQUE is not set # CONFIG_FB_MATROX_G450 is not set # CONFIG_FB_MATROX_G100A is not set # CONFIG_FB_MATROX_MULTIHEAD is not set # CONFIG_FB_RADEON_OLD 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_KYRO 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 is not set # CONFIG_MDA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_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_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_HWDEP=m CONFIG_SND_RAWMIDI=m CONFIG_SND_SEQUENCER=m CONFIG_SND_SEQ_DUMMY=m CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=m CONFIG_SND_PCM_OSS=m # CONFIG_SND_SEQUENCER_OSS is not set # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set # # Generic devices # CONFIG_SND_MPU401_UART=m CONFIG_SND_OPL3_LIB=m # CONFIG_SND_DUMMY is not set # CONFIG_SND_VIRMIDI is not set # CONFIG_SND_MTPAV is not set CONFIG_SND_SERIAL_U16550=m CONFIG_SND_MPU401=m # # ISA devices # # CONFIG_SND_AD1816A is not set # CONFIG_SND_AD1848 is not set # CONFIG_SND_CS4231 is not set CONFIG_SND_CS4232=m # CONFIG_SND_CS4236 is not set # CONFIG_SND_ES968 is not set # CONFIG_SND_ES1688 is not set # CONFIG_SND_ES18XX is not set # CONFIG_SND_GUSCLASSIC is not set # CONFIG_SND_GUSEXTREME is not set # CONFIG_SND_GUSMAX is not set # CONFIG_SND_INTERWAVE is not set # CONFIG_SND_INTERWAVE_STB is not set # CONFIG_SND_OPTI92X_AD1848 is not set # CONFIG_SND_OPTI92X_CS4231 is not set # CONFIG_SND_OPTI93X is not set # CONFIG_SND_SB8 is not set # CONFIG_SND_SB16 is not set # CONFIG_SND_SBAWE is not set # CONFIG_SND_WAVEFRONT is not set # CONFIG_SND_ALS100 is not set # CONFIG_SND_AZT2320 is not set # CONFIG_SND_CMI8330 is not set # CONFIG_SND_DT019X is not set # CONFIG_SND_OPL3SA2 is not set # CONFIG_SND_SGALAXY is not set # CONFIG_SND_SSCAPE is not set # # PCI devices # CONFIG_SND_AC97_CODEC=m # CONFIG_SND_ALI5451 is not set # CONFIG_SND_ATIIXP is not set # CONFIG_SND_AU8810 is not set # CONFIG_SND_AU8820 is not set # CONFIG_SND_AU8830 is not set # CONFIG_SND_AZT3328 is not set # CONFIG_SND_BT87X is not set # CONFIG_SND_CS46XX is not set # CONFIG_SND_CS4281 is not set # CONFIG_SND_EMU10K1 is not set # CONFIG_SND_KORG1212 is not set # CONFIG_SND_MIXART 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=m # 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_INTEL8X0M is not set # CONFIG_SND_SONICVIBES is not set # CONFIG_SND_VIA82XX is not set # CONFIG_SND_VX222 is not set # # ALSA PowerMac devices # # # ALSA PowerMac requires I2C # # # Open Sound System # CONFIG_SOUND_PRIME=m # CONFIG_SOUND_BT878 is not set # CONFIG_SOUND_CMPCI is not set # CONFIG_SOUND_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_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=m # CONFIG_SOUND_TRACEINIT is not set # CONFIG_SOUND_DMAP is not set # CONFIG_SOUND_AD1816 is not set # CONFIG_SOUND_AD1889 is not set # CONFIG_SOUND_SGALAXY is not set # CONFIG_SOUND_ADLIB is not set # CONFIG_SOUND_ACI_MIXER is not set CONFIG_SOUND_CS4232=m # CONFIG_SOUND_SSCAPE is not set # CONFIG_SOUND_GUS is not set # CONFIG_SOUND_VMIDI is not set # CONFIG_SOUND_TRIX is not set # CONFIG_SOUND_MSS is not set # CONFIG_SOUND_MPU401 is not set # CONFIG_SOUND_NM256 is not set # CONFIG_SOUND_MAD16 is not set # CONFIG_SOUND_PAS is not set # CONFIG_SOUND_PSS is not set # CONFIG_SOUND_SB is not set # CONFIG_SOUND_AWE32_SYNTH is not set # CONFIG_SOUND_WAVEFRONT is not set # CONFIG_SOUND_MAUI is not set # CONFIG_SOUND_YM3812 is not set # CONFIG_SOUND_OPL3SA1 is not set # CONFIG_SOUND_OPL3SA2 is not set # CONFIG_SOUND_YMFPCI is not set # CONFIG_SOUND_UART6850 is not set # CONFIG_SOUND_AEDSP16 is not set # CONFIG_SOUND_ALI5455 is not set # CONFIG_SOUND_FORTE is not set # CONFIG_SOUND_RME96XX is not set # CONFIG_SOUND_AD1980 is not set # # USB support # # CONFIG_USB is not set # # USB Gadget Support # # CONFIG_USB_GADGET 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 is not set CONFIG_ROMFS_FS=y # CONFIG_QUOTA is not set # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_ZISOFS_FS=y # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y # CONFIG_DEVFS_FS is not set # CONFIG_DEVPTS_FS_XATTR is not set CONFIG_TMPFS=y # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_ASFS_FS is not set CONFIG_HFS_FS=m CONFIG_HFSPLUS_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=m # CONFIG_UFS_FS_WRITE is not set # # Network File Systems # CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFS_V4 is not set # CONFIG_NFS_DIRECTIO is not set CONFIG_NFSD=y CONFIG_NFSD_V3=y # CONFIG_NFSD_V4 is not set # CONFIG_NFSD_TCP is not set # CONFIG_ROOT_NFS is not set CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_EXPORTFS=y CONFIG_SUNRPC=y # CONFIG_RPCSEC_GSS_KRB5 is not set CONFIG_SMB_FS=m CONFIG_SMB_NLS_DEFAULT=y CONFIG_SMB_NLS_REMOTE="iso8859-15" # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set CONFIG_CODA_FS=m # CONFIG_CODA_FS_OLD_API 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=y 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_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_EFI_PARTITION is not set # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=m # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set CONFIG_NLS_CODEPAGE_850=m # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # 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 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set CONFIG_NLS_ISO8859_1=m # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set CONFIG_NLS_ISO8859_15=m # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Library routines # CONFIG_CRC_CCITT=m CONFIG_CRC32=m # CONFIG_LIBCRC32C is not set CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=m # # Profiling support # # CONFIG_PROFILING is not set # # Kernel hacking # CONFIG_DEBUG_KERNEL=y # CONFIG_DEBUG_SLAB is not set CONFIG_MAGIC_SYSRQ=y # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_KGDB is not set CONFIG_XMON=y # CONFIG_BDI_SWITCH is not set # CONFIG_DEBUG_INFO is not set CONFIG_BOOTX_TEXT=y # # Security options # # CONFIG_SECURITY is not set # # Cryptographic options # # CONFIG_CRYPTO is not set ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-02 0:31 ` Sebastian Heutling @ 2005-01-03 12:26 ` Marc Dietrich 2005-01-04 0:54 ` evilninja 2005-01-04 11:31 ` Sebastian Heutling 0 siblings, 2 replies; 41+ messages in thread From: Marc Dietrich @ 2005-01-03 12:26 UTC (permalink / raw) To: sheutlin; +Cc: linuxppc-dev Hi Christian, Am Sonntag, 2. Januar 2005 01:31 schrieb Sebastian Heutling: > Hi Marc, > > On Mon, 2004-12-27 at 22:37 +0100, Marc Dietrich wrote: > > Hallo Christian, > > > > maybe this helps: > > > > I used the config file you sent me (and added serial console). > > > > when booting a working 2.4.24-pre1 I get: > > > > [...] > > PCI: Probing PCI hardware > > Setting PCI interrupts for a "Utah (Powerstack II Pro4000)" > > PCI: moved device 00:0b.1 resource 4 (101) to 1480 > > PCI: moved device 00:0b.1 resource 5 (101) to 1490 > > PCI: moved device 00:11.0 resource 0 (1208) to 0 > > [...] > > SCSI subsystem driver Revision: 1.00 > > new devtbl [4096] @c049e000. > > PCI: Enabling device 00:0c.0 (0000 -> 0003) > > sym53c8xx: at PCI bus 0, device 12, function 0 > > sym53c8xx: setting PCI_COMMAND_MASTER PCI_COMMAND_PARITY...(fix-up) > > sym53c8xx: changing PCI_LATENCY_TIMER from 0 to 80. > > sym53c8xx: 53c825a detected > > sym53c825a-0: rev 0x13 on pci bus 0 device 12 function 0 irq 15 > > new MPOOL [ 188] @c049f000. > > new VTOB [ 12] @c049f100. > > new NCB [2408] @c049c000. > > new SQUEUE [2336] @c049d000. > > new VTOB [ 12] @c049f110. > > new DQUEUE [2336] @c049a000. > > new TARGTBL [ 256] @c049b000. > > new VTOB [ 12] @c049f120. > > new SCRIPT [3504] @c0498000. > > new SCRIPTH [1504] @c049b800. > > new CCB [1300] @c0499000. > > sym53c825a-0: ID 7, Fast-10, Parity Checking > > > > I already changed the irq of slot 12 to 15 and slot 14 to irq 11. > > You don't really need to change any IRQ above slot 9 on a 2.6.? kernel > because the slot is 2 (while it was on 12 in 2.4 kernels). ah yes, now I understand. You just copied all numbers from top to down. > > [...] > > PCI: Probing PCI hardware > > Setting PCI interrupts for a "Utah (Powerstack II Pro4000)" > > PCI: Cannot allocate resource region 5 of device 0000:00:01.1 > > This is the IDE chip which gets IRQ 0 and therefore results in an error. > Try changing the value of Slot 1 from 0 to 4 (which is IRQ 14). I don't > really think it changes the SCSI timeouts maybe it helps - no one knows > for sure ;). Ok - did that also. > > SCSI subsystem initialized > > [...] > > PCI: Enabling device 0000:00:02.0 (0000 -> 0003) > > sym0: <825a> rev 0x13 at pci 0000:00:02.0 irq 15 so I guess 0000:00:02.0 is right as oposed to 0000:00:0C.0 with 2.4 kernels. > > [...] > > new BADLUNTBL [ 256] @c7d9aa00. > > sym0: SCSI BUS has been reset. > > scsi0 : sym-2.1.18m > > elevator: using anticipatory as default io scheduler > > sym0:0:0:ccb @c7d9ac00 using tag 256. > > sym0: queuepos=2. > > sym0:0:0: ABORT operation started. > > sym0:0:0: ABORT operation timed-out. > > sym0:0:0: DEVICE RESET operation started. > > sym0:0:0: DEVICE RESET operation timed-out. > > sym0:0:0: BUS RESET operation started. > > sym0:0:0: BUS RESET operation timed-out. > > sym0:0:0: HOST RESET operation started. > > sym0:0:0:ccb @c7d9ac00 freeing tag 256. > > sym0: SCSI BUS has been reset. > > [ hangs here ] > > Hmmm strange ... is there anything attached on scsi? Yes - a hard disk and a cdrom. Both are working under 2.4 kernels (see the boot.log of the 2.4.24-pre1 kernel). I don't use net boot. My system (debian sarge) is installed on sda3. Anyway - also on a netboot system, the kernel should hang when trying to initialize the scsi controler. > ... wait a second ... looking at the lspci output ... you use a USB PCI > card? The IRQ-sharing doesn't work well and the USB PCI card is on the > same slot as the SCSI controller resulting in both using the same IRQ. > Remove the USB card and check wether it changes anything. If it does > work now: Did it ever work with USB using another kernel? If so maybe > there is something else wrong, if not it's a HW Problem. > I also attached a config file from my powerstack (which I use as a > router and runs a 2.6 kernel since june last year or so) I didn't checked if the usb card is working under a 2.4 kernel, but it boots without problems. I removed it now, just to eleminate possible trouble. I setup a kernel using your config file and added vga console and offb and removed the nfs drivers to get an image smaller then 1.44 Mb (I'm using XFree86-3.3.6 with the cirrus 5664 card). This has the same effect than before: scsi not working. It seems, that this config is not for a 2.6.10 kernel. What kernel version are you using? Maybe some bad things happened in newer kernels. Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I can write it to a floppy disk)? How does your boot.log looks like? Greetings Marc ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-03 12:26 ` Marc Dietrich @ 2005-01-04 0:54 ` evilninja 2005-01-04 11:31 ` Sebastian Heutling 1 sibling, 0 replies; 41+ messages in thread From: evilninja @ 2005-01-04 0:54 UTC (permalink / raw) To: linuxppc-dev -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marc Dietrich schrieb: > Hi Christian, > actually, Sebastian is the helping hand here ;) > Yes - a hard disk and a cdrom. Both are working under 2.4 kernels (see the > boot.log of the 2.4.24-pre1 kernel). I don't use net boot. My system (debian > sarge) is installed on sda3. Anyway - also on a netboot system, the kernel > should hang when trying to initialize the scsi controler. i can't help you much at the scsi-issue here. as i said, i don't have a disk attached to the machine any more. the last time i booted with disk was a 2.4 kernel. and these errors (ABORT operation started / timed-out) occured upon heavy load on the scsi bus. i think i've never booted a 2.6 kernel with a scsi disk attached. but the errors look familiar :-( > I setup a kernel using your config file and added vga console and offb and > removed the nfs drivers to get an image smaller then 1.44 Mb (I'm using > XFree86-3.3.6 with the cirrus 5664 card). This has the same effect than > before: scsi not working. :-( > It seems, that this config is not for a 2.6.10 kernel. What kernel version are > you using? Maybe some bad things happened in newer kernels. ironically, now that i am able to netboot the machine, i'm not *using* it anymore. but i'm building PReP kernel everyday, results and a config-file is here: http://www.nerdbynature.de/bits/sheep/latest-kernel/ > Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I can > write it to a floppy disk)? yes, i'll upload working zImage.prep + .config here: http://www.nerdbynature.de/bits/sheep/prep/ > How does your boot.log looks like? i'll upload a boot.log too. Christian. - -- BOFH excuse #78: Yes, yes, its called a design limitation -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB2ekxC/PVm5+NVoYRAs/MAKCGSNylixVnx6W20TIK/h5ALwivxQCfc9pi IL8BTtzcpDTJ9KNwhixVqXc= =ggNI -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-03 12:26 ` Marc Dietrich 2005-01-04 0:54 ` evilninja @ 2005-01-04 11:31 ` Sebastian Heutling 2005-01-04 14:04 ` Marc Dietrich 1 sibling, 1 reply; 41+ messages in thread From: Sebastian Heutling @ 2005-01-04 11:31 UTC (permalink / raw) To: Marc Dietrich; +Cc: linuxppc-dev [-- Attachment #1: Type: text/plain, Size: 3820 bytes --] Hello Marc, Marc Dietrich wrote: >Hi Christian, > > Erm ... I'm Sebastian ;-) >Am Sonntag, 2. Januar 2005 01:31 schrieb Sebastian Heutling: > > >>You don't really need to change any IRQ above slot 9 on a 2.6.? kernel >>because the slot is 2 (while it was on 12 in 2.4 kernels). >> >> > >ah yes, now I understand. You just copied all numbers from top to down. > > Yep. > > >>>[...] >>>PCI: Probing PCI hardware >>>Setting PCI interrupts for a "Utah (Powerstack II Pro4000)" >>>PCI: Cannot allocate resource region 5 of device 0000:00:01.1 >>> >>> >>This is the IDE chip which gets IRQ 0 and therefore results in an error. >>Try changing the value of Slot 1 from 0 to 4 (which is IRQ 14). I don't >>really think it changes the SCSI timeouts maybe it helps - no one knows >>for sure ;). >> >> > >Ok - did that also. > > > >>>SCSI subsystem initialized >>>[...] >>>PCI: Enabling device 0000:00:02.0 (0000 -> 0003) >>>sym0: <825a> rev 0x13 at pci 0000:00:02.0 irq 15 >>> >>> > >so I guess 0000:00:02.0 is right as oposed to 0000:00:0C.0 with 2.4 kernels. > > Yes. > > >>>[...] >>>new BADLUNTBL [ 256] @c7d9aa00. >>>sym0: SCSI BUS has been reset. >>>scsi0 : sym-2.1.18m >>>elevator: using anticipatory as default io scheduler >>>sym0:0:0:ccb @c7d9ac00 using tag 256. >>>sym0: queuepos=2. >>>sym0:0:0: ABORT operation started. >>>sym0:0:0: ABORT operation timed-out. >>>sym0:0:0: DEVICE RESET operation started. >>>sym0:0:0: DEVICE RESET operation timed-out. >>>sym0:0:0: BUS RESET operation started. >>>sym0:0:0: BUS RESET operation timed-out. >>>sym0:0:0: HOST RESET operation started. >>>sym0:0:0:ccb @c7d9ac00 freeing tag 256. >>>sym0: SCSI BUS has been reset. >>>[ hangs here ] >>> >>> >>Hmmm strange ... is there anything attached on scsi? >> >> > >Yes - a hard disk and a cdrom. Both are working under 2.4 kernels (see the >boot.log of the 2.4.24-pre1 kernel). I don't use net boot. My system (debian >sarge) is installed on sda3. Anyway - also on a netboot system, the kernel >should hang when trying to initialize the scsi controler. > > > >>... wait a second ... looking at the lspci output ... you use a USB PCI >>card? The IRQ-sharing doesn't work well and the USB PCI card is on the >>same slot as the SCSI controller resulting in both using the same IRQ. >>Remove the USB card and check wether it changes anything. If it does >>work now: Did it ever work with USB using another kernel? If so maybe >>there is something else wrong, if not it's a HW Problem. >>I also attached a config file from my powerstack (which I use as a >>router and runs a 2.6 kernel since june last year or so) >> >> > >I didn't checked if the usb card is working under a 2.4 kernel, but it boots >without problems. I removed it now, just to eleminate possible trouble. > >I setup a kernel using your config file and added vga console and offb and >removed the nfs drivers to get an image smaller then 1.44 Mb (I'm using >XFree86-3.3.6 with the cirrus 5664 card). This has the same effect than >before: scsi not working. > >It seems, that this config is not for a 2.6.10 kernel. What kernel version are >you using? Maybe some bad things happened in newer kernels. > > I am using a 2.6.8 (I was too lazy to patch & compile a 2.6.9 and wanted to test 2.6.10 when it's (the sources) in debian/unstable). >Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I can >write it to a floppy disk)? > > I will do that and tell you later where you can download it. >How does your boot.log looks like? > > Attached it. Note that I use a Matrox MilleniumII gfx card and XFree4 runs fine (without any crash) since I got a 2.6 kernel running (although I am not using XFree because I use the Powerstack as a router/server which has no Monitor). Sebastian [-- Attachment #2: boot.log --] [-- Type: text/plain, Size: 8383 bytes --] Total memory = 256MB; using 512kB for hash table (at c0380000) Linux version 2.6.8 (root@sengor) (gcc version 3.3.5 (Debian 1:3.3.5-2)) #8 Tue Nov 9 15:59:40 CET 2004 PReP architecture On node 0 totalpages: 65536 DMA zone: 65536 pages, LIFO batch:16 Normal zone: 0 pages, LIFO batch:1 HighMem zone: 0 pages, LIFO batch:1 Built 1 zonelists Kernel command line: root=/dev/sda2 console=ttyS0 PID hash table entries: 2048 (order 11: 16384 bytes) time_init: decrementer frequency = 16.657680 MHz Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 255232k available (2204k kernel code, 1144k data, 160k init, 0k highmem) Calibrating delay loop... 299.00 BogoMIPS Mount-cache hash table entries: 512 (order: 0, 4096 bytes) NET: Registered protocol family 16 PCI: Probing PCI hardware Setting PCI interrupts for a "Utah (Powerstack II Pro4000)" PCI: Cannot allocate resource region 5 of device 0000:00:01.1 Linux Plug and Play Support v0.97 (c) Adam Belay SCSI subsystem initialized PCI: Enabling device 0000:00:08.0 (0080 -> 0082) matroxfb: Matrox Millennium (PCI) detected matroxfb: 640x480x8bpp (virtual: 640x6553) matroxfb: framebuffer at 0xC1800000, mapped to 0xf1800000, size 4194304 fb0: MATROX frame buffer device fb0: initializing hardware Installing knfsd (copyright (C) 1996 okir@monad.swb.de). isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Console: switching to colour frame buffer device 80x30 Macintosh non-volatile memory driver v1.1 Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx W82C105: IDE controller at PCI slot 0000:00:01.1 PCI: Enabling device 0000:00:01.1 (0000 -> 0001) W82C105: chipset revision 5 W82C105: 100% native mode on irq 14 W82C105: dma_base is invalid (0x0000) ide0: W82C105 Bus-Master DMA disabled (BIOS) W82C105: dma_base is invalid (0x0000) ide1: W82C105 Bus-Master DMA disabled (BIOS) Probing IDE interface ide0... hda: ST380021A, ATA DISK drive hdb: IBM-DTLA-305040, ATA DISK drive hda: selected PIO 4 (120ns) (0240) hdb: selected PIO 4 (120ns) (0240) Using anticipatory io scheduler ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... Probing IDE interface ide1... Probing IDE interface ide2... ide2: Wait for ready failed before probe ! Probing IDE interface ide3... ide3: Wait for ready failed before probe ! hda: max request size: 128KiB hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=65535/16/63 hda: hda1 hdb: max request size: 128KiB hdb: 80418240 sectors (41174 MB) w/380KiB Cache, CHS=65535/16/63 hdb: hdb1 PCI: Enabling device 0000:00:02.0 (0000 -> 0003) sym0: <825a> rev 0x13 at pci 0000:00:02.0 irq 15 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: SCSI BUS has been reset. scsi0 : sym-2.1.18j Vendor: IBM Model: DPSS-309170N Rev: S93E Type: Direct-Access ANSI SCSI revision: 03 sym0:0:0: tagged command queuing enabled, command queue depth 16. scsi(0:0:0:0): Beginning Domain Validation sym0:0: wide asynchronous. sym0:0: FAST-10 WIDE SCSI 20.0 MB/s ST (100.0 ns, offset 8) scsi(0:0:0:0): Ending Domain Validation st: Version 20040403, fixed bufsize 32768, s/g segs 256 SCSI device sda: 16777216 512-byte hdwr sectors (8590 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 mice: PS/2 mouse device common for all mice serio: i8042 AUX port at 0x60,0x64 irq 12 atkbd.c: keyboard reset failed on isa0060/serio1 serio: i8042 KBD port at 0x60,0x64 irq 1 atkbd.c: keyboard reset failed on isa0060/serio0 NET: Registered protocol family 2 IP: routing cache hash table of 2048 buckets, 16Kbytes TCP: Hash tables configured (established 16384 bind 32768) NET: Registered protocol family 1 NET: Registered protocol family 17 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 160k init 36k pmac 4k chrp 4k openfirmware Adding 262136k swap on /dev/sda3. Priority:-1 extents:1 EXT3 FS on sda2, internal journal Linux Tulip driver version 1.1.13 (May 11, 2002) PCI: Enabling device 0000:00:04.0 (0000 -> 0003) tulip0: EEPROM default media type Autosense. tulip0: Index #0 - Media AUI (#2) described by a 21140 non-MII (0) block. tulip0: Index #1 - Media MII (#11) described by a 21140 MII PHY (1) block. tulip0: MII transceiver #8 config 3100 status 786b advertising 01e1. eth0: Digital DS21140 Tulip rev 34 at 0x1800, 08:00:3E:29:2E:45, IRQ 11. de2104x PCI Ethernet driver v0.7 (Mar 17, 2004) kjournald starting. Commit interval 5 seconds EXT3 FS on hda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on hdb1, internal journal EXT3-fs: mounted filesystem with ordered data mode. eth0: Setting full-duplex based on MII#8 link partner capability of 45e1. CSLIP: code copyright 1989 Regents of the University of California PPP generic driver version 2.4.2 ip_tables: (C) 2000-2002 Netfilter core team ip_conntrack version 2.1 (2048 buckets, 16384 max) - 296 bytes per conntrack eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others PCI: Enabling device 0000:00:06.0 (0000 -> 0003) eth1: 0000:00:06.0, 00:02:B3:1A:8C:72, IRQ 10. Board assembly 751767-003, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. Secondary interface chip i82555. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x8e695832). PPP BSD Compression module registered PPP Deflate Compression module registered eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. UDP: bad checksum. From 213.97.110.54:5889 to 83.129.181.72:4472 ulen 27 UDP: bad checksum. From 82.90.52.67:12826 to 83.129.248.97:4223 ulen 27 eth1: TX underrun, threshold adjusted. eth1: TX underrun, threshold adjusted. sym0:0:0: ABORT operation started. sym0:0:0: ABORT operation timed-out. sym0:0:0: ABORT operation started. sym0:0:0: ABORT operation timed-out. sym0:0:0: ABORT operation started. sym0:0:0: ABORT operation timed-out. sym0:0:0: ABORT operation started. sym0:0:0: ABORT operation timed-out. sym0:0:0: DEVICE RESET operation started. sym0:0:0: DEVICE RESET operation timed-out. sym0:0:0: BUS RESET operation started. sym0: SCSI BUS reset detected. sym0: SCSI BUS has been reset. sym0:0:0: BUS RESET operation complete. eth1: TX underrun, threshold adjusted. UDP: short packet: From 217.126.164.250:5676 33/27 to 83.129.160.15:11124 eth1: TX underrun, threshold adjusted. UDP: short packet: From 82.254.199.92:1024 132/26 to 83.129.199.46:571 UDP: bad checksum. From 217.126.164.250:5676 to 83.129.174.118:5667 ulen 27 UDP: bad checksum. From 82.50.40.247:7689 to 83.129.1.186:4120 ulen 28 UDP: bad checksum. From 218.90.225.199:3357 to 83.129.16.247:3258 ulen 26 UDP: short packet: From 217.126.164.250:2960 11925/27 to 83.129.63.189:4662 UDP: short packet: From 83.129.64.153:888 0/27 to 83.129.70.178:13054 UDP: bad checksum. From 217.126.164.250:5676 to 83.129.70.178:3454 ulen 33 UDP: bad checksum. From 217.126.164.250:5676 to 83.129.70.178:12855 ulen 80 ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-04 11:31 ` Sebastian Heutling @ 2005-01-04 14:04 ` Marc Dietrich 2005-01-04 14:42 ` Sebastian Heutling [not found] ` <1104850036.6164.25.camel@weizen.left.earth> 0 siblings, 2 replies; 41+ messages in thread From: Marc Dietrich @ 2005-01-04 14:04 UTC (permalink / raw) To: Sebastian Heutling; +Cc: linuxppc-dev Hallo Sebastian, Am Dienstag, 4. Januar 2005 12:31 schrieben Sie: > Hello Marc, > > Marc Dietrich wrote: > >Hi Christian, > > Erm ... I'm Sebastian ;-) ah! - sorry Sebastian, to many confusion in the last time... > I am using a 2.6.8 (I was too lazy to patch & compile a 2.6.9 and wanted > to test 2.6.10 when it's (the sources) in debian/unstable). > > >Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I can > >write it to a floppy disk)? > > I will do that and tell you later where you can download it. This may no longer be necessary, but see below. Acording to your log, your scsi drive also fails later, but boots from ide (how did you managed to install the ide disks?). I posted a message to linux-scsi describing this problem. I guess the sym2 driver never worked on the PReP machines. I tried it also with 2.4 kernels. So to summerize it: No one has a working Powerstack with 2.6 kernel and booting from SCSI. I hope there will be some input from the scsi list. > >How does your boot.log looks like? > > Attached it. > Note that I use a Matrox MilleniumII gfx card and XFree4 runs fine > (without any crash) since I got a 2.6 kernel running (although I am not > using XFree because I use the Powerstack as a router/server which has no > Monitor). Yeah - I search so many times for a Millenium card on eBay. Now I got one for EUR 1.00 but it is in Germany, while I'm in France now for holidays :-( I also have a P9100 here, but it is not supported (yet?) under linux... Greetings Marc ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-04 14:04 ` Marc Dietrich @ 2005-01-04 14:42 ` Sebastian Heutling [not found] ` <1104850036.6164.25.camel@weizen.left.earth> 1 sibling, 0 replies; 41+ messages in thread From: Sebastian Heutling @ 2005-01-04 14:42 UTC (permalink / raw) To: Marc Dietrich; +Cc: linuxppc-dev On Tue, 2005-01-04 at 15:04 +0100, Marc Dietrich wrote: > Hallo Sebastian, > > Am Dienstag, 4. Januar 2005 12:31 schrieben Sie: > > Hello Marc, > > > > Marc Dietrich wrote: > > >Hi Christian, > > > > Erm ... I'm Sebastian ;-) > > ah! - sorry Sebastian, to many confusion in the last time... Hehe :) > > > I am using a 2.6.8 (I was too lazy to patch & compile a 2.6.9 and wanted > > to test 2.6.10 when it's (the sources) in debian/unstable). > > > > >Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I can > > >write it to a floppy disk)? > > > > I will do that and tell you later where you can download it. > > This may no longer be necessary, but see below. > > Acording to your log, your scsi drive also fails later, but boots from ide > (how did you managed to install the ide disks?). Yep, it fails later but it doesn't boot from IDE. The SCSI disk is recognized correctly and the system is on the SCSI drive. The IDE disks only contain data. It fails later that is right but it still works after failure. Making IDE work was easy. A friend soldered the connectors and then I passed "ide0=ide0=0x1f0,0x3f6,14" as kernel parameter to make channel 0 work. Later on after, discovering what was wrong with 2.6 kernels, I enabled the correct interrupt in the appropriate table in prep_pci.c. > > I posted a message to linux-scsi describing this problem. I guess the sym2 > driver never worked on the PReP machines. I tried it also with 2.4 kernels. > > So to summerize it: No one has a working Powerstack with 2.6 kernel and > booting from SCSI. I hope there will be some input from the scsi list. As said above, it does really work although I have to admit there is a problem with PCI or IRQ handling in general. You can also see in my log that one of the ethernet devices has problems every now and then. All in all it is sort of functional. You can also try to remove every additional PCI device except the gfx card and see what happens. I had to remove an additional SCSI host controller in order to avoid problems with other PCI devices (mostly it was one of the ethernet devices which lost an interrupt). But I share your thoughts that there is something wrong with the sym2 driver. > > > >How does your boot.log looks like? > > > > Attached it. > > Note that I use a Matrox MilleniumII gfx card and XFree4 runs fine > > (without any crash) since I got a 2.6 kernel running (although I am not > > using XFree because I use the Powerstack as a router/server which has no > > Monitor). > > Yeah - I search so many times for a Millenium card on eBay. Now I got one for > EUR 1.00 but it is in Germany, while I'm in France now for holidays :-( > I also have a P9100 here, but it is not supported (yet?) under linux... :( Sebastian ^ permalink raw reply [flat|nested] 41+ messages in thread
[parent not found: <1104850036.6164.25.camel@weizen.left.earth>]
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) [not found] ` <1104850036.6164.25.camel@weizen.left.earth> @ 2005-01-05 11:33 ` Marc Dietrich 2005-01-05 15:47 ` Sven Luther 0 siblings, 1 reply; 41+ messages in thread From: Marc Dietrich @ 2005-01-05 11:33 UTC (permalink / raw) To: sheutlin; +Cc: linuxppc-dev [-- Attachment #1: Type: text/plain, Size: 1405 bytes --] Hallo Sebastian, Am Dienstag, 4. Januar 2005 15:47 schrieb Sebastian Heutling: > Hello again Marc, > > > > >Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I > > > > can write it to a floppy disk)? > > > > (...) > It is on: http://sengor.ath.cx/~sheutlin/prep/zImage.prep hehe! It is booting!!! Different to your setup, I get no timeouts here (boot.log is attached) - this makes me wondering if there are different board revisions out there. Another thing is, I tried to compile a stock 2.6.8 kernel with your config from "/proc/config.gz" and the modified irq tables in prep_pci.c (I guess you also did this modification). This kernel does not boot! It even doesn't show the boot loader - it just hangs after finished loading the kernel from floppy disk. Either a) I have a corrupt kernel tree, b) my compiler (gcc 3.3.4, debian/sarge) has problems or c) you changed something else in your kernel. I check a) and I think it is ok. for b) I'm currently downloading the 3.3.5 compile from unstable debian (the you you are using I guess), and will try it again. c) how does you prep_pci.c looks like, any other changes? I have to leave this machine alone tomorrow, so I won't be able to do any testing further. From what we have now here, it seems that something is broken for kernels >2.6.8. It would be nice, if someone can double check this. Best wishes Marc [-- Attachment #2: dmsg-2.6.8-Sebastian --] [-- Type: text/plain, Size: 5552 bytes --] Total memory = 128MB; using 256kB for hash table (at c0340000) Linux version 2.6.8 (root@sengor) (gcc version 3.3.5 (Debian 1:3.3.5-5)) #10 Tue Jan 4 13:03:42 CET 2005 PReP architecture On node 0 totalpages: 32768 DMA zone: 32768 pages, LIFO batch:8 Normal zone: 0 pages, LIFO batch:1 HighMem zone: 0 pages, LIFO batch:1 Built 1 zonelists Kernel command line: root=/dev/sda3 console=tty0 video=clgen:mode:640x480 PID hash table entries: 1024 (order 10: 8192 bytes) time_init: decrementer frequency = 16.657984 MHz Console: colour VGA+ 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 126208k available (1932k kernel code, 1060k data, 156k init, 0k highmem) Calibrating delay loop... 398.33 BogoMIPS Mount-cache hash table entries: 512 (order: 0, 4096 bytes) NET: Registered protocol family 16 PCI: Probing PCI hardware Setting PCI interrupts for a "Utah (Powerstack II Pro4000)" PCI: Cannot allocate resource region 5 of device 0000:00:01.1 Linux Plug and Play Support v0.97 (c) Adam Belay SCSI subsystem initialized RAM (1024 kB) at 0xxc0000000, Cirrus Logic chipset on PCI bus cirrusfb: Driver for Cirrus Logic based graphic boards, v2.0-pre2 isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found cirrusfb: This board has 1048576 bytes of DRAM memory cirrusfb: This board has 1048576 bytes of DRAM memory Console: switching to colour frame buffer device 80x30 Macintosh non-volatile memory driver v1.1 Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx W82C105: IDE controller at PCI slot 0000:00:01.1 PCI: Enabling device 0000:00:01.1 (0000 -> 0001) W82C105: chipset revision 5 W82C105: 100% native mode on irq 14 W82C105: dma_base is invalid (0x0000) ide0: W82C105 Bus-Master DMA disabled (BIOS) W82C105: dma_base is invalid (0x0000) ide1: W82C105 Bus-Master DMA disabled (BIOS) Probing IDE interface ide0... Probing IDE interface ide1... Probing IDE interface ide0... Probing IDE interface ide1... Probing IDE interface ide2... ide2: Wait for ready failed before probe ! Probing IDE interface ide3... ide3: Wait for ready failed before probe ! PCI: Enabling device 0000:00:02.0 (0000 -> 0003) sym0: <825a> rev 0x13 at pci 0000:00:02.0 irq 15 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: SCSI BUS has been reset. scsi0 : sym-2.1.18j Using anticipatory io scheduler Vendor: SEAGATE Model: ST34573W Rev: 5764 Type: Direct-Access ANSI SCSI revision: 02 sym0:1:0: tagged command queuing enabled, command queue depth 16. scsi(0:0:1:0): Beginning Domain Validation sym0:1: wide asynchronous. sym0:1: FAST-10 WIDE SCSI 20.0 MB/s ST (100.0 ns, offset 8) scsi(0:0:1:0): Domain Validation skipping write tests scsi(0:0:1:0): Ending Domain Validation Vendor: NEC Model: CD-ROM DRIVE:463 Rev: 1.05 Type: CD-ROM ANSI SCSI revision: 02 scsi(0:0:3:0): Beginning Domain Validation sym0:3: FAST-10 SCSI 10.0 MB/s ST (100.0 ns, offset 8) scsi(0:0:3:0): Domain Validation skipping write tests scsi(0:0:3:0): Ending Domain Validation st: Version 20040403, fixed bufsize 32768, s/g segs 256 SCSI device sda: 8888924 512-byte hdwr sectors (4551 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 > Attached scsi disk sda at scsi0, channel 0, id 1, lun 0 sr0: scsi-1 drive Uniform CD-ROM driver Revision: 3.20 Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0 Attached scsi generic sg0 at scsi0, channel 0, id 1, lun 0, type 0 Attached scsi generic sg1 at scsi0, channel 0, id 3, lun 0, type 5 mice: PS/2 mouse device common for all mice serio: i8042 AUX port at 0x60,0x64 irq 12 input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 serio: i8042 KBD port at 0x60,0x64 irq 1 input: AT Translated Set 2 keyboard on isa0060/serio0 NET: Registered protocol family 2 IP: routing cache hash table of 1024 buckets, 8Kbytes TCP: Hash tables configured (established 8192 bind 16384) NET: Registered protocol family 1 NET: Registered protocol family 17 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 156k init 36k pmac 4k chrp 4k openfirmware Adding 262252k swap on /dev/sda2. Priority:-1 extents:1 EXT3 FS on sda3, internal journal kjournald starting. Commit interval 5 seconds EXT3 FS on sda5, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on sda6, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on sda7, internal journal EXT3-fs: mounted filesystem with ordered data mode. cirrusfb: This board has 1048576 bytes of DRAM memory cirrusfb: This board has 1048576 bytes of DRAM memory cirrusfb: This board has 1048576 bytes of DRAM memory cirrusfb: This board has 1048576 bytes of DRAM memory cirrusfb: This board has 1048576 bytes of DRAM memory cirrusfb: This board has 1048576 bytes of DRAM memory cirrusfb: This board has 1048576 bytes of DRAM memory cirrusfb: This board has 1048576 bytes of DRAM memory ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-05 11:33 ` Marc Dietrich @ 2005-01-05 15:47 ` Sven Luther 2005-01-05 17:10 ` Christian 0 siblings, 1 reply; 41+ messages in thread From: Sven Luther @ 2005-01-05 15:47 UTC (permalink / raw) To: Marc Dietrich; +Cc: linuxppc-dev On Wed, Jan 05, 2005 at 12:33:25PM +0100, Marc Dietrich wrote: > > Hallo Sebastian, > > Am Dienstag, 4. Januar 2005 15:47 schrieb Sebastian Heutling: > > Hello again Marc, > > > > > > >Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I > > > > > can write it to a floppy disk)? > > > > > > (...) > > It is on: http://sengor.ath.cx/~sheutlin/prep/zImage.prep > > hehe! It is booting!!! > > Different to your setup, I get no timeouts here (boot.log is attached) - this > makes me wondering if there are different board revisions out there. > > Another thing is, I tried to compile a stock 2.6.8 kernel with your config > from "/proc/config.gz" and the modified irq tables in prep_pci.c (I guess you > also did this modification). This kernel does not boot! It even doesn't show > the boot loader - it just hangs after finished loading the kernel from floppy > disk. Either a) I have a corrupt kernel tree, b) my compiler (gcc 3.3.4, > debian/sarge) has problems or c) you changed something else in your kernel. > > I check a) and I think it is ok. > for b) I'm currently downloading the 3.3.5 compile from unstable debian (the > you you are using I guess), and will try it again. > c) how does you prep_pci.c looks like, any other changes? > > I have to leave this machine alone tomorrow, so I won't be able to do any > testing further. From what we have now here, it seems that something is > broken for kernels >2.6.8. It would be nice, if someone can double check > this. Did you try : http://people.debian.org/~luther/prep/d-i-2005.01.03-prep It is the debian kernel with the prep_pci patch, and the debian-installer (yesterdays or so daily-built) initrd on top of it. I simply boot it from netboot with : boot enet:192.168.1.10,d-i-2005.01.03-prep,192.168.1.17 (where .10 is my tftp server, and .17 a random free address on the subnet). And it works fine. I plan to do a kernel upload soonishly to fix those issues in debian, but i would like to have also the fixes for the other prep systems if needed. Friendly, Sven Luther ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-05 15:47 ` Sven Luther @ 2005-01-05 17:10 ` Christian 2005-01-05 17:39 ` Sven Luther 0 siblings, 1 reply; 41+ messages in thread From: Christian @ 2005-01-05 17:10 UTC (permalink / raw) To: linuxppc-dev -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Dienstag, 4. Januar 2005 15:47 schrieb Sebastian Heutling: >> >>>Hello again Marc, >>> >>> >>>>>>Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I >>>>>>can write it to a floppy disk)? >>>>> >>>(...) >>>It is on: http://sengor.ath.cx/~sheutlin/prep/zImage.prep >> yes, it's booting, but i get timeouts here on my PReP (however Marc says, that he does not get errors). would you be so kind and publish the .config too? > Did you try : > > http://people.debian.org/~luther/prep/d-i-2005.01.03-prep > and Sven: nice d-i, really. but i couldn't see any config for this kernel either. it would be nice if you could put the config somewhere too. mine are here, now with SCSI enabled too and thus errors showing up: http://www.nerdbynature.de/bits/hal/daily/configs/config-ppc-2.6.10 http://www.nerdbynature.de/bits/hal/daily/boot/dmesg-2.6.10 (but network is fine now ;-)) thank you both, Chrisitian. - -- BOFH excuse #305: IRQ-problems with the Un-Interruptible-Power-Supply -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB3B9+C/PVm5+NVoYRAmjiAJ4hrZAtauVVUjR6cWj+7l70+4X+lgCg/RlD rPCFIAeCt5eiGxTYplSDONk= =9pzA -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-05 17:10 ` Christian @ 2005-01-05 17:39 ` Sven Luther 2005-01-06 16:00 ` Christian 0 siblings, 1 reply; 41+ messages in thread From: Sven Luther @ 2005-01-05 17:39 UTC (permalink / raw) To: Christian; +Cc: linuxppc-dev On Wed, Jan 05, 2005 at 06:10:22PM +0100, Christian wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Am Dienstag, 4. Januar 2005 15:47 schrieb Sebastian Heutling: > >> > >>>Hello again Marc, > >>> > >>> > >>>>>>Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I > >>>>>>can write it to a floppy disk)? > >>>>> > >>>(...) > >>>It is on: http://sengor.ath.cx/~sheutlin/prep/zImage.prep > >> > > yes, it's booting, but i get timeouts here on my PReP (however Marc says, > that he does not get errors). would you be so kind and publish the .config > too? > > > Did you try : > > > > http://people.debian.org/~luther/prep/d-i-2005.01.03-prep > > > > and Sven: nice d-i, really. but i couldn't see any config for this kernel > either. it would be nice if you could put the config somewhere too. It is the standard powerpc debian kernel. apt-get install kernel-image-2.6.8-powerpc, and you will find the config in /boot/config-2.6.8-powerpc. All the rest of the stuff can be found in the debian kernel svn repo : http://svn.debian.org/wsvn/kernel/trunk/kernel/ > mine are here, now with SCSI enabled too and thus errors showing up: > > http://www.nerdbynature.de/bits/hal/daily/configs/config-ppc-2.6.10 > http://www.nerdbynature.de/bits/hal/daily/boot/dmesg-2.6.10 > > (but network is fine now ;-)) Well, i am really interested to know if the above debian kernel boots for you or not. And to find the patches that fix it if it doesn't. Friendly, Sven Luther ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-05 17:39 ` Sven Luther @ 2005-01-06 16:00 ` Christian 2005-01-06 16:27 ` Sven Luther 0 siblings, 1 reply; 41+ messages in thread From: Christian @ 2005-01-06 16:00 UTC (permalink / raw) To: linuxppc-dev -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sven Luther schrieb: > > It is the standard powerpc debian kernel. apt-get install > kernel-image-2.6.8-powerpc, and you will find the config in > /boot/config-2.6.8-powerpc. All the rest of the stuff can be found in the [...] > > Well, i am really interested to know if the above debian kernel boots for you > or not. And to find the patches that fix it if it doesn't. ok. but 2.6.8 +2.6.9 won't boot for me, as it does not include the prep_pci.c fix, which was introduced in 2.6.10-rc3. i assume http://people.debian.org/~luther/prep/d-i-2005.01.03-prep is made from a current kernel, thus containing the fix (because it's booting, upon "configure network" the network actually works too ;)) i've fetched kernel-source-2.6.9 now, applied the prep_pci fix and compiled the kernel. i *had* to make changes to the debian-config (config-2.6.9-powerpc) because i am still not able to boot via disk. so i enabled CONFIG_ROOT_NFS and CONFIG_TULIP, details here: http://www.nerdbynature.de/bits/hal/daily/boot/config-2.6.9-powerpc http://www.nerdbynature.de/bits/hal/daily/boot/config-2.6.9-powerpc.my http://www.nerdbynature.de/bits/hal/2.6.10-rc3/prep_pci_renumbered-2.6.10-rc3.patch the kernel boots, network is set up, but since everything else is modular, it cries about several things. i can ping the host and i really think this all would work, except when i set CONFIG_SCSI_SYM53C8XX_2=y http://www.nerdbynature.de/bits/hal/daily/boot/config-2.6.9-powerpc.my+scsi then the ABORT and RESET errors show upon upon initialization of the scsi-adapter (no disk attached). i don't have a fix for this scsi-issue at hand. maybe i missed something... hope this helps anyhow to get PReP ready for debian sometimes... Christian. - -- BOFH excuse #148: Insert coin for new game -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB3WCjC/PVm5+NVoYRAqH/AKDP1Dds54VDC7+F/rz/ykBpbsC6yQCg/3oC ukrDN1HRvS+5kfgYtO2CJ4w= =/h4o -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-06 16:00 ` Christian @ 2005-01-06 16:27 ` Sven Luther 2005-01-06 20:27 ` Christian 0 siblings, 1 reply; 41+ messages in thread From: Sven Luther @ 2005-01-06 16:27 UTC (permalink / raw) To: Christian; +Cc: linuxppc-dev On Thu, Jan 06, 2005 at 05:00:35PM +0100, Christian wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Sven Luther schrieb: > > > > It is the standard powerpc debian kernel. apt-get install > > kernel-image-2.6.8-powerpc, and you will find the config in > > /boot/config-2.6.8-powerpc. All the rest of the stuff can be found in the > [...] > > > > Well, i am really interested to know if the above debian kernel boots for you > > or not. And to find the patches that fix it if it doesn't. > > ok. but 2.6.8 +2.6.9 won't boot for me, as it does not include the > prep_pci.c fix, which was introduced in 2.6.10-rc3. i assume Sure, and backported to the debian kernel. > http://people.debian.org/~luther/prep/d-i-2005.01.03-prep > > is made from a current kernel, thus containing the fix (because it's > booting, upon "configure network" the network actually works too ;)) Nope, same kernel-source-2.6.8 based one as will ship with sarge. It is not uploaded yet, will probably be uploaded this WE. > i've fetched kernel-source-2.6.9 now, applied the prep_pci fix and > compiled the kernel. i *had* to make changes to the debian-config > (config-2.6.9-powerpc) because i am still not able to boot via disk. so i > enabled CONFIG_ROOT_NFS and CONFIG_TULIP, details here: These should be enabled by default in the debian config though :/ > http://www.nerdbynature.de/bits/hal/daily/boot/config-2.6.9-powerpc > http://www.nerdbynature.de/bits/hal/daily/boot/config-2.6.9-powerpc.my > http://www.nerdbynature.de/bits/hal/2.6.10-rc3/prep_pci_renumbered-2.6.10-rc3.patch > > the kernel boots, network is set up, but since everything else is modular, > it cries about several things. i can ping the host and i really think this > all would work, except when i set CONFIG_SCSI_SYM53C8XX_2=y > > http://www.nerdbynature.de/bits/hal/daily/boot/config-2.6.9-powerpc.my+scsi > > then the ABORT and RESET errors show upon upon initialization of the > scsi-adapter (no disk attached). i don't have a fix for this scsi-issue at > hand. maybe i missed something... Mmm, it works well here, so maybe your scsi hardware has some problems ? > hope this helps anyhow to get PReP ready for debian sometimes... > Christian. Well, prep on powerstack will be easy, the others will depend on people submiting a kernel patch for them ? Friendly, Sven Luther ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-06 16:27 ` Sven Luther @ 2005-01-06 20:27 ` Christian 2005-01-06 21:07 ` Sven Luther 0 siblings, 1 reply; 41+ messages in thread From: Christian @ 2005-01-06 20:27 UTC (permalink / raw) To: linuxppc-dev On Thu, January 6, 2005 17:27, Sven Luther said: >> ok. but 2.6.8 +2.6.9 won't boot for me, as it does not include the >> prep_pci.c fix, which was introduced in 2.6.10-rc3. i assume > > Sure, and backported to the debian kernel. now i'm confused: i've extracted kernel-source-2.6.9.tar.bz2 from kernel-source-2.6.9_2.6.9-4_all.deb but the prep_pci [1] fix still applied! how was it backported then? >> http://people.debian.org/~luther/prep/d-i-2005.01.03-prep >> >> is made from a current kernel, thus containing the fix (because it's >> booting, upon "configure network" the network actually works too ;)) > > Nope, same kernel-source-2.6.8 based one as will ship with sarge. It is > not uploaded yet, will probably be uploaded this WE. hm, very strange. so d-i-2005.01.03-prep is made from 2.6.8+backported prep_pci fix (but see my notes above), and it boots fine (network is ok, but no disks are found as none are attached and thus "Partition the Harddisk" fails) >> i've fetched kernel-source-2.6.9 now, applied the prep_pci fix and >> compiled the kernel. i *had* to make changes to the debian-config >> (config-2.6.9-powerpc) because i am still not able to boot via disk. so >> i enabled CONFIG_ROOT_NFS and CONFIG_TULIP, details here: > > These should be enabled by default in the debian config though :/ erm, yes, they were, but as modules only. i needed them statically (CONFIG_ROOT_NFS!) > Mmm, it works well here, so maybe your scsi hardware has some problems ? no disks attached, but i will do some more tests on this tonight... thanks for your concern, Christian. [1] http://www.nerdbynature.de/bits/hal/2.6.10-rc3/prep_pci_renumbered-2.6.10-rc3.patch -- make bzImage, not war ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-06 20:27 ` Christian @ 2005-01-06 21:07 ` Sven Luther 2005-01-06 21:21 ` Christian 0 siblings, 1 reply; 41+ messages in thread From: Sven Luther @ 2005-01-06 21:07 UTC (permalink / raw) To: Christian; +Cc: linuxppc-dev On Thu, Jan 06, 2005 at 09:27:10PM +0100, Christian wrote: > On Thu, January 6, 2005 17:27, Sven Luther said: > >> ok. but 2.6.8 +2.6.9 won't boot for me, as it does not include the > >> prep_pci.c fix, which was introduced in 2.6.10-rc3. i assume > > > > Sure, and backported to the debian kernel. > > now i'm confused: i've extracted kernel-source-2.6.9.tar.bz2 from > kernel-source-2.6.9_2.6.9-4_all.deb but the prep_pci [1] fix still > applied! > how was it backported then? To 2.6.8. 2.6.9 is not all that important, because 2.6.8 is what will ship with sarge (well, 2.6.8 + a bunch of backports and fixes), and since i hadn't much time, i didn't yet apply it to 2.6.9. > >> http://people.debian.org/~luther/prep/d-i-2005.01.03-prep > >> > >> is made from a current kernel, thus containing the fix (because it's > >> booting, upon "configure network" the network actually works too ;)) > > > > Nope, same kernel-source-2.6.8 based one as will ship with sarge. It is > > not uploaded yet, will probably be uploaded this WE. > > hm, very strange. so d-i-2005.01.03-prep is made from 2.6.8+backported > prep_pci fix (but see my notes above), and it boots fine (network is ok, > but no disks are found as none are attached and thus "Partition the > Harddisk" fails) Ah, the disk is found here with this one. > >> i've fetched kernel-source-2.6.9 now, applied the prep_pci fix and > >> compiled the kernel. i *had* to make changes to the debian-config > >> (config-2.6.9-powerpc) because i am still not able to boot via disk. so > >> i enabled CONFIG_ROOT_NFS and CONFIG_TULIP, details here: > > > > These should be enabled by default in the debian config though :/ > > erm, yes, they were, but as modules only. i needed them statically > (CONFIG_ROOT_NFS!) I remember putting that as builtin in the 2.4 kernels. But as the 2.6 packages are minimal kernels with most of the stuff as modules, you can still make it work by building an initrd including them, and loading the necessary stuff. I don't know if mkinitrd from the initrd-tools package is able to do that, but if so, it would be best to fill a bug report aboutthis. > > Mmm, it works well here, so maybe your scsi hardware has some problems ? > > no disks attached, but i will do some more tests on this tonight... Ah, no wonder you don't see a disk then ... I wonder if d-i is upto installing a NFS-root system, i don't think so. > thanks for your concern, > Christian. > > [1] > http://www.nerdbynature.de/bits/hal/2.6.10-rc3/prep_pci_renumbered-2.6.10-rc3.patch See : http://svn.debian.org/wsvn/kernel/trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian/patches/powerpc-prep-powerstack-irq.dpatch?op=file&rev=0&sc=0 Friendly, Sven Luther ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-06 21:07 ` Sven Luther @ 2005-01-06 21:21 ` Christian 2005-01-06 21:49 ` Sven Luther 0 siblings, 1 reply; 41+ messages in thread From: Christian @ 2005-01-06 21:21 UTC (permalink / raw) To: linuxppc-dev On Thu, January 6, 2005 22:07, Sven Luther said: >> >> no disks attached, but i will do some more tests on this tonight... > > Ah, no wonder you don't see a disk then ... ;-) > I wonder if d-i is upto installing a NFS-root system, i don't think so. yes, i can see that. nfsroot is my only way to go here. (will probably get a proper scsi-cable soon) > See : > http://svn.debian.org/wsvn/kernel/trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian/patches/powerpc-prep-powerstack-irq.dpatch?op=file&rev=0&sc=0 ah, ok. will try. thanks, Christian. -- make bzImage, not war ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-06 21:21 ` Christian @ 2005-01-06 21:49 ` Sven Luther 0 siblings, 0 replies; 41+ messages in thread From: Sven Luther @ 2005-01-06 21:49 UTC (permalink / raw) To: Christian; +Cc: linuxppc-dev On Thu, Jan 06, 2005 at 10:21:04PM +0100, Christian wrote: > On Thu, January 6, 2005 22:07, Sven Luther said: > >> > >> no disks attached, but i will do some more tests on this tonight... > > > > Ah, no wonder you don't see a disk then ... > > ;-) > > > I wonder if d-i is upto installing a NFS-root system, i don't think so. > > yes, i can see that. nfsroot is my only way to go here. (will probably get > a proper scsi-cable soon) If your NFS server is also powerpc, you could just debootstrap the partition there :) I guess pure NFS support will have to wait for sarge+1. Now that d-i is branched, patches are welcome though. > > See : > > http://svn.debian.org/wsvn/kernel/trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian/patches/powerpc-prep-powerstack-irq.dpatch?op=file&rev=0&sc=0 > > ah, ok. will try. I just moved it to 2.6.9, but these kernel-source are not yet released, and probably won't be until this WE or something, at which point the official powerpc kernels will include it. With a bit of luck we will have real prep support in d-i two weeks from now, depending how i am able to fix the partman-prep horror story. (Added bunch of logs -> it worked, removed them -> don't work anymore, altough it works on power4 chrp hardware :/) Friendly, Sven Luther ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2004-12-27 2:47 ` Christian 2004-12-27 21:37 ` Marc Dietrich @ 2004-12-31 9:55 ` Sven Luther 2004-12-31 15:00 ` Sebastian Heutling 1 sibling, 1 reply; 41+ messages in thread From: Sven Luther @ 2004-12-31 9:55 UTC (permalink / raw) To: Christian; +Cc: linuxppc-dev, Marc Dietrich On Mon, Dec 27, 2004 at 03:47:05AM +0100, Christian wrote: > Marc Dietrich schrieb: > >Hi all, > > > >I read this thread about booting a PowerStack with newer kernels. > >Motivated by this, I tried to compile a 2.6.10 kernel on my machine (with > >sym53c825a onboard). Sadly, the scsi controller always timeouts during > >initialisation. I I also have some strange issues with network support using the standard debian 2.6.8 kernel. ifconfig upping the decchip ethernet on the powerstack freezes the kernel, and i hear reports of problems on IBM PReP hardware too with not working ethernet, altough there is no freeze. Any idea on this ? Friendly, Sven Luther ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2004-12-31 9:55 ` Sven Luther @ 2004-12-31 15:00 ` Sebastian Heutling 2004-12-31 22:28 ` Sven Luther 0 siblings, 1 reply; 41+ messages in thread From: Sebastian Heutling @ 2004-12-31 15:00 UTC (permalink / raw) To: Sven Luther; +Cc: linuxppc-dev, Marc Dietrich On Fri, 2004-12-31 at 10:55 +0100, Sven Luther wrote: > On Mon, Dec 27, 2004 at 03:47:05AM +0100, Christian wrote: > > Marc Dietrich schrieb: > > >Hi all, > > > > > >I read this thread about booting a PowerStack with newer kernels. > > >Motivated by this, I tried to compile a 2.6.10 kernel on my machine (with > > >sym53c825a onboard). Sadly, the scsi controller always timeouts during > > >initialisation. I > > I also have some strange issues with network support using the standard debian > 2.6.8 kernel. ifconfig upping the decchip ethernet on the powerstack freezes > the kernel, and i hear reports of problems on IBM PReP hardware too with not > working ethernet, altough there is no freeze. > > Any idea on this ? Does it contain the IRQ patch? Where does it boot from SCSI or net? What PCI-Devices are installed? I use an older patched 2.6.8 debian kernel. It works fine here except that I can't insert the eepro100 module via /etc/modules on boot because some times it crashes on module insertion (or on ifconfig via init script - I don't remember exactly) and sometimes not. Therefore I do it by hand after boot up. Sebastian Heutling ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2004-12-31 15:00 ` Sebastian Heutling @ 2004-12-31 22:28 ` Sven Luther 2005-01-01 23:56 ` Sebastian Heutling 0 siblings, 1 reply; 41+ messages in thread From: Sven Luther @ 2004-12-31 22:28 UTC (permalink / raw) To: Sebastian Heutling; +Cc: linuxppc-dev, Marc Dietrich On Fri, Dec 31, 2004 at 04:00:49PM +0100, Sebastian Heutling wrote: > On Fri, 2004-12-31 at 10:55 +0100, Sven Luther wrote: > > On Mon, Dec 27, 2004 at 03:47:05AM +0100, Christian wrote: > > > Marc Dietrich schrieb: > > > >Hi all, > > > > > > > >I read this thread about booting a PowerStack with newer kernels. > > > >Motivated by this, I tried to compile a 2.6.10 kernel on my machine (with > > > >sym53c825a onboard). Sadly, the scsi controller always timeouts during > > > >initialisation. I > > > > I also have some strange issues with network support using the standard debian > > 2.6.8 kernel. ifconfig upping the decchip ethernet on the powerstack freezes > > the kernel, and i hear reports of problems on IBM PReP hardware too with not > > working ethernet, altough there is no freeze. > > > > Any idea on this ? > > Does it contain the IRQ patch? Where does it boot from SCSI or net? What > PCI-Devices are installed? Probably not, just the standard debian kernel, i donÃ't remember any irq patches, but there where a bunch of patches from leighbb. it is done netbooting, and the only pci device installed is the cirruss logic graphic card. > I use an older patched 2.6.8 debian kernel. It works fine here except > that I can't insert the eepro100 module via /etc/modules on boot because > some times it crashes on module insertion (or on ifconfig via init > script - I don't remember exactly) and sometimes not. Therefore I do it > by hand after boot up. Can you mail me the patch in question, or better yet mail it to the bug report about this ? 287933@bugs.debian.org Friendly, Sven Luther ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2004-12-31 22:28 ` Sven Luther @ 2005-01-01 23:56 ` Sebastian Heutling 2005-01-02 9:39 ` Sven Luther 0 siblings, 1 reply; 41+ messages in thread From: Sebastian Heutling @ 2005-01-01 23:56 UTC (permalink / raw) To: Sven Luther; +Cc: linuxppc-dev, Marc Dietrich On Fri, 2004-12-31 at 23:28 +0100, Sven Luther wrote: > On Fri, Dec 31, 2004 at 04:00:49PM +0100, Sebastian Heutling wrote: > > On Fri, 2004-12-31 at 10:55 +0100, Sven Luther wrote: > > > On Mon, Dec 27, 2004 at 03:47:05AM +0100, Christian wrote: > > > > Marc Dietrich schrieb: > > > > >Hi all, > > > > > > > > > >I read this thread about booting a PowerStack with newer kernels. > > > > >Motivated by this, I tried to compile a 2.6.10 kernel on my machine (with > > > > >sym53c825a onboard). Sadly, the scsi controller always timeouts during > > > > >initialisation. I > > > > > > I also have some strange issues with network support using the standard debian > > > 2.6.8 kernel. ifconfig upping the decchip ethernet on the powerstack freezes > > > the kernel, and i hear reports of problems on IBM PReP hardware too with not > > > working ethernet, altough there is no freeze. > > > > > > Any idea on this ? > > > > Does it contain the IRQ patch? Where does it boot from SCSI or net? What > > PCI-Devices are installed? > > Probably not, just the standard debian kernel, i donÃ't remember any irq > patches, but there where a bunch of patches from leighbb. it is done The patch is the one that is included in 2.6.10 which is mentioned above and this thread already has somewhere in the beginning. I attached it below. I haven't had the time yet to test the 2.6.10 kernel. Maybe there is another problem now ... > netbooting, and the only pci device installed is the cirruss logic graphic > card. If you use the standard debian kernel - ok, it doesn't work because of wrong IRQs on the PowerstackII (Utah). BTW: The onboard Winbond IDE chip works as well although no connector is provided. You only need a little bit of soldering and adjusting the IRQ of Slot 1 from 0 to 4. :-) Sebastian Heutling -- diff -puN arch/ppc/platforms/prep_pci.c~ppc32-fix-motorola-prep-powerstackii-utah-pci-irq-map arch/ppc/platforms/prep_pci.c --- 25/arch/ppc/platforms/prep_pci.c~ppc32-fix-motorola-prep-powerstackii-utah-pci-irq-map 2004-12-07 01:01:16.000000000 -0800 +++ 25-akpm/arch/ppc/platforms/prep_pci.c 2004-12-07 01:01:16.000000000 -0800 @@ -49,10 +49,10 @@ static char Utah_pci_IRQ_map[23] __prepd 0, /* Slot 1 - unused */ 5, /* Slot 2 - SCSI - NCR825A */ 0, /* Slot 3 - unused */ - 1, /* Slot 4 - Ethernet - DEC2114x */ + 3, /* Slot 4 - Ethernet - DEC2114x */ 0, /* Slot 5 - unused */ - 3, /* Slot 6 - PCI Card slot #1 */ - 4, /* Slot 7 - PCI Card slot #2 */ + 2, /* Slot 6 - PCI Card slot #1 */ + 3, /* Slot 7 - PCI Card slot #2 */ 5, /* Slot 8 - PCI Card slot #3 */ 5, /* Slot 9 - PCI Bridge */ /* added here in case we ever support PCI bridges */ ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-01 23:56 ` Sebastian Heutling @ 2005-01-02 9:39 ` Sven Luther 2005-01-02 21:33 ` Sebastian Heutling 0 siblings, 1 reply; 41+ messages in thread From: Sven Luther @ 2005-01-02 9:39 UTC (permalink / raw) To: Sebastian Heutling; +Cc: linuxppc-dev, Marc Dietrich On Sun, Jan 02, 2005 at 12:56:29AM +0100, Sebastian Heutling wrote: > On Fri, 2004-12-31 at 23:28 +0100, Sven Luther wrote: > > On Fri, Dec 31, 2004 at 04:00:49PM +0100, Sebastian Heutling wrote: > > > On Fri, 2004-12-31 at 10:55 +0100, Sven Luther wrote: > > > > On Mon, Dec 27, 2004 at 03:47:05AM +0100, Christian wrote: > > > > > Marc Dietrich schrieb: > > > > > >Hi all, > > > > > > > > > > > >I read this thread about booting a PowerStack with newer kernels. > > > > > >Motivated by this, I tried to compile a 2.6.10 kernel on my machine (with > > > > > >sym53c825a onboard). Sadly, the scsi controller always timeouts during > > > > > >initialisation. I > > > > > > > > I also have some strange issues with network support using the standard debian > > > > 2.6.8 kernel. ifconfig upping the decchip ethernet on the powerstack freezes > > > > the kernel, and i hear reports of problems on IBM PReP hardware too with not > > > > working ethernet, altough there is no freeze. > > > > > > > > Any idea on this ? > > > > > > Does it contain the IRQ patch? Where does it boot from SCSI or net? What > > > PCI-Devices are installed? > > > > Probably not, just the standard debian kernel, i donÃ't remember any irq > > patches, but there where a bunch of patches from leighbb. it is done > > The patch is the one that is included in 2.6.10 which is mentioned above > and this thread already has somewhere in the beginning. I attached it > below. > I haven't had the time yet to test the 2.6.10 kernel. Maybe there is > another problem now ... The one with three lines of modified irq lines from tom rini ? I found it in google, but i also saw another bunch of prep changes which got in 2.6.9 i think. Since debian is still using 2.6.8 and a bunch of backports, these may be relevant, i think. Also, i think for some reason i was unsubscribed while the list moved to ozlab, and lost maybe the start of the thread, thanks for the attachement. > > netbooting, and the only pci device installed is the cirruss logic graphic > > card. > > If you use the standard debian kernel - ok, it doesn't work because of > wrong IRQs on the PowerstackII (Utah). Which i will now fix now that i am aware of the problem. There seem to be also a problem on IBM prep hardware, may it be related ? > BTW: The onboard Winbond IDE chip works as well although no connector is > provided. You only need a little bit of soldering and adjusting the IRQ > of Slot 1 from 0 to 4. :-) Ah, wondered about that, and saw the slots are not soldered. I wonder why go to all the trouble including a IDE chip, but not solder the connectors. Seems to me like peanut savings or something. Friendly, Sven Luther > > > Sebastian Heutling > > -- > diff -puN > arch/ppc/platforms/prep_pci.c~ppc32-fix-motorola-prep-powerstackii-utah-pci-irq-map arch/ppc/platforms/prep_pci.c > --- > 25/arch/ppc/platforms/prep_pci.c~ppc32-fix-motorola-prep-powerstackii-utah-pci-irq-map 2004-12-07 01:01:16.000000000 -0800 > +++ 25-akpm/arch/ppc/platforms/prep_pci.c 2004-12-07 > 01:01:16.000000000 -0800 > @@ -49,10 +49,10 @@ static char Utah_pci_IRQ_map[23] __prepd > 0, /* Slot 1 - unused */ > 5, /* Slot 2 - SCSI - NCR825A */ > 0, /* Slot 3 - unused */ > - 1, /* Slot 4 - Ethernet - DEC2114x */ > + 3, /* Slot 4 - Ethernet - DEC2114x */ > 0, /* Slot 5 - unused */ > - 3, /* Slot 6 - PCI Card slot #1 */ > - 4, /* Slot 7 - PCI Card slot #2 */ > + 2, /* Slot 6 - PCI Card slot #1 */ > + 3, /* Slot 7 - PCI Card slot #2 */ > 5, /* Slot 8 - PCI Card slot #3 */ > 5, /* Slot 9 - PCI Bridge */ > /* added here in case we ever support PCI bridges */ > > > ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-02 9:39 ` Sven Luther @ 2005-01-02 21:33 ` Sebastian Heutling 0 siblings, 0 replies; 41+ messages in thread From: Sebastian Heutling @ 2005-01-02 21:33 UTC (permalink / raw) To: Sven Luther; +Cc: linuxppc-dev, Marc Dietrich On Sun, 2005-01-02 at 10:39 +0100, Sven Luther wrote: > On Sun, Jan 02, 2005 at 12:56:29AM +0100, Sebastian Heutling wrote: > > On Fri, 2004-12-31 at 23:28 +0100, Sven Luther wrote: > > > On Fri, Dec 31, 2004 at 04:00:49PM +0100, Sebastian Heutling wrote: > > > > On Fri, 2004-12-31 at 10:55 +0100, Sven Luther wrote: > > > > > On Mon, Dec 27, 2004 at 03:47:05AM +0100, Christian wrote: > > > > > > Marc Dietrich schrieb: > > > > > > >Hi all, > > > > > > > > > > > > > >I read this thread about booting a PowerStack with newer kernels. > > > > > > >Motivated by this, I tried to compile a 2.6.10 kernel on my machine (with > > > > > > >sym53c825a onboard). Sadly, the scsi controller always timeouts during > > > > > > >initialisation. I > > > > > > > > > > I also have some strange issues with network support using the standard debian > > > > > 2.6.8 kernel. ifconfig upping the decchip ethernet on the powerstack freezes > > > > > the kernel, and i hear reports of problems on IBM PReP hardware too with not > > > > > working ethernet, altough there is no freeze. > > > > > > > > > > Any idea on this ? > > > > > > > > Does it contain the IRQ patch? Where does it boot from SCSI or net? What > > > > PCI-Devices are installed? > > > > > > Probably not, just the standard debian kernel, i donÃ't remember any irq > > > patches, but there where a bunch of patches from leighbb. it is done > > > > The patch is the one that is included in 2.6.10 which is mentioned above > > and this thread already has somewhere in the beginning. I attached it > > below. > > I haven't had the time yet to test the 2.6.10 kernel. Maybe there is > > another problem now ... > > The one with three lines of modified irq lines from tom rini ? I found it in > google, but i also saw another bunch of prep changes which got in 2.6.9 i Hmmm ... I didn't realise any other prep changes in 2.6.9 > think. Since debian is still using 2.6.8 and a bunch of backports, these may > be relevant, i think. You mean debian/testing? > > Also, i think for some reason i was unsubscribed while the list moved to > ozlab, and lost maybe the start of the thread, thanks for the attachement. That explains a lot ;-) > > > > netbooting, and the only pci device installed is the cirruss logic graphic > > > card. > > > > If you use the standard debian kernel - ok, it doesn't work because of > > wrong IRQs on the PowerstackII (Utah). > > Which i will now fix now that i am aware of the problem. There seem to be also > a problem on IBM prep hardware, may it be related ? Looking at the IRQ tables in prep_pci.c it very possible. There are a lot structures which have a lot of low numbered slots initialised to 0. Might be that its the same problem: PCI slotnumbering has changed resulting in wrong used entries in this tables. People should look at this particular place if they have problems like lost interrupts, kernel output saying that a device got IRQ 0, timeouts or something like that. > > > BTW: The onboard Winbond IDE chip works as well although no connector is > > provided. You only need a little bit of soldering and adjusting the IRQ > > of Slot 1 from 0 to 4. :-) > > Ah, wondered about that, and saw the slots are not soldered. I wonder why go > to all the trouble including a IDE chip, but not solder the connectors. Seems > to me like peanut savings or something. I am not sure but I think there are two versions of this machine: One with only IDE connectors and one with only SCSI connector. But to be honest: I don't know as well why they didn't solder all connectors. Sebastian Heutling ^ permalink raw reply [flat|nested] 41+ messages in thread
[parent not found: <200501051733.06350.marvin24@gmx.de>]
[parent not found: <20050105165551.GA29287@pegasos>]
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) [not found] ` <20050105165551.GA29287@pegasos> @ 2005-01-05 20:57 ` Marc Dietrich 2005-01-09 23:17 ` Sebastian Heutling 0 siblings, 1 reply; 41+ messages in thread From: Marc Dietrich @ 2005-01-05 20:57 UTC (permalink / raw) To: Sven Luther; +Cc: linuxppc-dev Hi all, I didn't recognise that the kernel from Sebastian - which was working fine here - was build from the debian sources (no hint in the kernel version). So I build everything again from debian source and fixed the irq's in prep_pci.c. I can confirm now, that this debian+irq_fix kernel 2.6.8 runs fine and produces no scsi timeouts! Something happend in kernels >= 2.6.9 which makes the scsi unusable. Also it seems, that even in 2.6.8 kernels and with ide hard disks (Sebastians setup) the scsi controller timeouts, but continues to operate - correct? That's all for now (and this year), because I have to leave this nice machine alone and go home. Thanks to all who helped me - maybe see you next year again... Greetings Marc Am Mittwoch, 5. Januar 2005 17:55 schrieben Sie: > > (...) > > Also, apt-get install kernel-patch-debian-2.6.8 should give you the latest > debian patch. No idea how it applies to the non-free pruned stuff though. > > > Do you have any idea, why a stock 2.6.8 kernel (with prep_pci.c patch) > > doesn't boot a prep image? > > Either a missing patch or a wrong .config. > > I am personally much more interested in having the debian kernel working > correctly though. > > Friendly, > > Sven Luther ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-05 20:57 ` Marc Dietrich @ 2005-01-09 23:17 ` Sebastian Heutling 2005-01-10 6:34 ` Sven Luther 2005-01-10 6:54 ` Sven Luther 0 siblings, 2 replies; 41+ messages in thread From: Sebastian Heutling @ 2005-01-09 23:17 UTC (permalink / raw) To: Marc Dietrich; +Cc: linuxppc-dev Marc Dietrich wrote: >Hi all, > >I didn't recognise that the kernel from Sebastian - which was working fine >here - was build from the debian sources (no hint in the kernel version). >So I build everything again from debian source and fixed the irq's in >prep_pci.c. > > Erm ... well ... yes - it's a debian kernel ;). >I can confirm now, that this debian+irq_fix kernel 2.6.8 runs fine and >produces no scsi timeouts! > >Something happend in kernels >= 2.6.9 which makes the scsi unusable. Also it >seems, that even in 2.6.8 kernels and with ide hard disks (Sebastians setup) >the scsi controller timeouts, but continues to operate - correct? > > Yep correct. I also tried the 2.6.10 and found out that it doesn't work here as well. First I get a lot of lost interrupts from the IDE driver and after that I also get the SCSI timeouts. It must have something to do with the prep changes in 2.6.9. One difference in IRQ setup I noticed is in prep_pcibios_fixup(). If I remember correctly before 2.6.9 at least on this Utah machine the IRQs are assigned from Motherboard_routes[] without doing anything else. Now additionally the IRQ is also written into the devices pci config space which might not work on the PowerstackII Utah. It's only a guess and I haven't had the time yet to test it. Sebastian ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-09 23:17 ` Sebastian Heutling @ 2005-01-10 6:34 ` Sven Luther 2005-01-10 15:19 ` Sebastian Heutling 2005-01-10 6:54 ` Sven Luther 1 sibling, 1 reply; 41+ messages in thread From: Sven Luther @ 2005-01-10 6:34 UTC (permalink / raw) To: Sebastian Heutling; +Cc: linuxppc-dev On Mon, Jan 10, 2005 at 12:17:54AM +0100, Sebastian Heutling wrote: > Marc Dietrich wrote: > > >Hi all, > > > >I didn't recognise that the kernel from Sebastian - which was working fine > >here - was build from the debian sources (no hint in the kernel version). > >So I build everything again from debian source and fixed the irq's in > >prep_pci.c. > > > > > Erm ... well ... yes - it's a debian kernel ;). Notice that 2.6.8-9, currently in unstable, has this patch, as well as the d-i image which will be built in a few hours. The same goes for 2.6.9-4, which i am uploading and should be in unstable tomorrow evening. For d-i, we have to wait for the 2.6.8-9 kernel to enter testing so it is fully operational. In the meantime, you have to : 1) when you reach partman, you have to switch to console 2, or go back unto the main menu and chose shell console if on serial console, and run parted by hand and create the prep-boot partition (set 1 prep on). An 8MB prep partition would be ideal. 2) you *have* to use /dev/hda3 as /. The debian kernel is configured for that, and there is not yet a way to modify this. 3) after base-install, you will get the no bootloader message, telling you the root path, there you have to go into a shell again, chroot to /target, and wget the unstable 2.6.8-9 kernel (or othrwise apt-get it, but this needs modifying the /etc/apt/sources.list to include unstable). 4) once the kernel is installed, you exit the chroot, and simply need to dd the kernel to the prep partition with : # dd if=/target/boot/vmlinuz-2.6.8-powerpc of=/dev/scsi/host3/bus0/target0/lun0/part1 (or whatever your disk is, in devfs paths). You have to use the daily-builds d-i images, not RC2 obviously. All these steps will be made unnecessary once the 2.6.8-9 kernel makes it to testing (in 2-3 days), and i upload both partman-prep (which allow to set the prep partition in partman), and prep-installer (which takes care of dd-ing the kernel). 2.6.10 powerpc kernels will follow, but they may be some time in the NEW queue. > >I can confirm now, that this debian+irq_fix kernel 2.6.8 runs fine and > >produces no scsi timeouts! > > > >Something happend in kernels >= 2.6.9 which makes the scsi unusable. Also > >it seems, that even in 2.6.8 kernels and with ide hard disks (Sebastians > >setup) the scsi controller timeouts, but continues to operate - correct? > > > > > > Yep correct. > I also tried the 2.6.10 and found out that it doesn't work here as well. > First I get a lot of lost interrupts from the IDE driver and after that > I also get the SCSI timeouts. It must have something to do with the prep > changes in 2.6.9. One difference in IRQ setup I noticed is in > prep_pcibios_fixup(). If I remember correctly before 2.6.9 at least on > this Utah machine the IRQs are assigned from Motherboard_routes[] > without doing anything else. Now additionally the IRQ is also written > into the devices pci config space which might not work on the > PowerstackII Utah. > It's only a guess and I haven't had the time yet to test it. Can you try the debian kernels i upload and fill bugreports against them ? Friendly, Sven Luther ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-10 6:34 ` Sven Luther @ 2005-01-10 15:19 ` Sebastian Heutling 0 siblings, 0 replies; 41+ messages in thread From: Sebastian Heutling @ 2005-01-10 15:19 UTC (permalink / raw) To: Sven Luther; +Cc: linuxppc-dev On Mon, 2005-01-10 at 07:34 +0100, Sven Luther wrote: [...] > > I also tried the 2.6.10 and found out that it doesn't work here as well. > > First I get a lot of lost interrupts from the IDE driver and after that > > I also get the SCSI timeouts. It must have something to do with the prep > > changes in 2.6.9. One difference in IRQ setup I noticed is in > > prep_pcibios_fixup(). If I remember correctly before 2.6.9 at least on > > this Utah machine the IRQs are assigned from Motherboard_routes[] > > without doing anything else. Now additionally the IRQ is also written > > into the devices pci config space which might not work on the > > PowerstackII Utah. > > It's only a guess and I haven't had the time yet to test it. > > Can you try the debian kernels i upload and fill bugreports against them ? I tried the 2.6.9 kernel. Same problem as in 2.6.10. I hacked a little in prep_pci.c/prep_pcibios_fixup() but nothing. Then I replaced prep_pci.c and prep_setup.c by using the 2.6.8 ones to be sure that this problem isn't coming from elsewhere and guess what: It worked again. So something from 2.6.8 to 2.6.9 in those two files must be causing this IRQ problem. Sebastian ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-09 23:17 ` Sebastian Heutling 2005-01-10 6:34 ` Sven Luther @ 2005-01-10 6:54 ` Sven Luther 1 sibling, 0 replies; 41+ messages in thread From: Sven Luther @ 2005-01-10 6:54 UTC (permalink / raw) To: Sebastian Heutling; +Cc: linuxppc-dev On Mon, Jan 10, 2005 at 12:17:54AM +0100, Sebastian Heutling wrote: > Marc Dietrich wrote: > > >Hi all, > > > >I didn't recognise that the kernel from Sebastian - which was working fine > >here - was build from the debian sources (no hint in the kernel version). > >So I build everything again from debian source and fixed the irq's in > >prep_pci.c. > > > > > Erm ... well ... yes - it's a debian kernel ;). Mmm, partman-prep was accepted, so it will make it to unstable tomorrow. It is strange though since it worked on Cajus power4 ibm box, but not on my powerstack. I am still investigating this, but the fix should happen quicker now. Friendly, Sven Luther ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) @ 2005-01-04 2:12 Christian 2005-01-04 13:23 ` Marc Dietrich 0 siblings, 1 reply; 41+ messages in thread From: Christian @ 2005-01-04 2:12 UTC (permalink / raw) To: linuxppc-dev -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > anymore. but i'm building PReP kernel everyday, results and a config-file > is here: > > http://www.nerdbynature.de/bits/sheep/latest-kernel/ sorry, it should read: http://www.nerdbynature.de/bits/hal/daily/ > yes, i'll upload working zImage.prep + .config here: > > http://www.nerdbynature.de/bits/sheep/prep/ and: http://www.nerdbynature.de/bits/hal/daily/results/ >>>How does your boot.log looks like? will show up in http://www.nerdbynature.de/bits/hal/daily/boot/ sorry for the confusion, Christian. - -- BOFH excuse #57: Groundskeepers stole the root password -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB2fuGC/PVm5+NVoYRAiCxAKC8B1L+FVw/5CoG3y7IpFVxpqzrgACfVSK7 gXQcGiHCfHg3vEabXHtaZaU= =2cwH -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-04 2:12 Christian @ 2005-01-04 13:23 ` Marc Dietrich 2005-01-04 15:08 ` Christian 0 siblings, 1 reply; 41+ messages in thread From: Marc Dietrich @ 2005-01-04 13:23 UTC (permalink / raw) To: Christian; +Cc: linuxppc-dev Hallo Christian, thanks for your info. I was also a little confused by all these configs and images ... So you are using netboot and it seems that when having a root-fs via nfs _no_ disk driver is initialized even if it is compiled in (acording to your config). Funny, didn't know that. Sebastian just send me a mail with his bootlog, and later also some zImage url I hope. He is running a 2.6.8 kernel and his kernel (scsi: sym2 2.1.18j) seems to detect the hard disk but fails later due to the same scsi timeouts. Luckily, he managed to install 2 IDE disks... Greetings Marc Am Dienstag, 4. Januar 2005 03:12 schrieben Sie: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > anymore. but i'm building PReP kernel everyday, results and a config-file > > is here: > > > > http://www.nerdbynature.de/bits/sheep/latest-kernel/ > > sorry, it should read: > > http://www.nerdbynature.de/bits/hal/daily/ > > > yes, i'll upload working zImage.prep + .config here: > > > > http://www.nerdbynature.de/bits/sheep/prep/ > > and: http://www.nerdbynature.de/bits/hal/daily/results/ > > >>>How does your boot.log looks like? > > will show up in http://www.nerdbynature.de/bits/hal/daily/boot/ > > sorry for the confusion, > Christian. > - -- > BOFH excuse #57: > > Groundskeepers stole the root password > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.5 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFB2fuGC/PVm5+NVoYRAiCxAKC8B1L+FVw/5CoG3y7IpFVxpqzrgACfVSK7 > gXQcGiHCfHg3vEabXHtaZaU= > =2cwH > -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 41+ messages in thread
* Re: [FYI] linux 2.6 still not working with PReP (ppc32) 2005-01-04 13:23 ` Marc Dietrich @ 2005-01-04 15:08 ` Christian 0 siblings, 0 replies; 41+ messages in thread From: Christian @ 2005-01-04 15:08 UTC (permalink / raw) To: linuxppc-dev; +Cc: Marc Dietrich -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marc Dietrich schrieb: > > So you are using netboot and it seems that when having a root-fs via nfs _no_ > disk driver is initialized even if it is compiled in (acording to your > config). Funny, didn't know that. > whoops! so, the 2.6.10-rc3 bootlog shows indeed no scsi-initialization - i'll boot a proper scsi-enabled config then and upload another bootlog ;-) - -- BOFH excuse #401: Sales staff sold a product we don't offer. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB2rF+C/PVm5+NVoYRAjkRAKCiSC6zSmw6Rvhy5RAbUtw4yFKvJgCfTMnA IIfoTniXDIT/YvsORjexf38= =vX/q -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 41+ messages in thread
end of thread, other threads:[~2005-01-10 15:19 UTC | newest]
Thread overview: 41+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-04 22:45 [FYI] linux 2.6 still not working with PReP (ppc32) Christian Kujau
2004-12-05 0:41 ` Sebastian Heutling
2004-12-05 17:41 ` Christian Kujau
2004-12-06 1:46 ` Sebastian Heutling
2004-12-06 4:15 ` [FYI] linux 2.6 still not^Wnow " Christian Kujau
2004-12-05 19:57 ` [PATCH] linux 2.6 " Christian Kujau
2004-12-06 18:49 ` Tom Rini
2004-12-06 19:33 ` Christian
-- strict thread matches above, loose matches on Subject: below --
2004-12-26 13:35 [FYI] linux 2.6 still not " Marc Dietrich
2004-12-27 2:47 ` Christian
2004-12-27 21:37 ` Marc Dietrich
2005-01-02 0:31 ` Sebastian Heutling
2005-01-03 12:26 ` Marc Dietrich
2005-01-04 0:54 ` evilninja
2005-01-04 11:31 ` Sebastian Heutling
2005-01-04 14:04 ` Marc Dietrich
2005-01-04 14:42 ` Sebastian Heutling
[not found] ` <1104850036.6164.25.camel@weizen.left.earth>
2005-01-05 11:33 ` Marc Dietrich
2005-01-05 15:47 ` Sven Luther
2005-01-05 17:10 ` Christian
2005-01-05 17:39 ` Sven Luther
2005-01-06 16:00 ` Christian
2005-01-06 16:27 ` Sven Luther
2005-01-06 20:27 ` Christian
2005-01-06 21:07 ` Sven Luther
2005-01-06 21:21 ` Christian
2005-01-06 21:49 ` Sven Luther
2004-12-31 9:55 ` Sven Luther
2004-12-31 15:00 ` Sebastian Heutling
2004-12-31 22:28 ` Sven Luther
2005-01-01 23:56 ` Sebastian Heutling
2005-01-02 9:39 ` Sven Luther
2005-01-02 21:33 ` Sebastian Heutling
[not found] ` <200501051733.06350.marvin24@gmx.de>
[not found] ` <20050105165551.GA29287@pegasos>
2005-01-05 20:57 ` Marc Dietrich
2005-01-09 23:17 ` Sebastian Heutling
2005-01-10 6:34 ` Sven Luther
2005-01-10 15:19 ` Sebastian Heutling
2005-01-10 6:54 ` Sven Luther
2005-01-04 2:12 Christian
2005-01-04 13:23 ` Marc Dietrich
2005-01-04 15:08 ` Christian
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).