From jakob at fuyu.mindrot.org Tue Nov 4 06:07:45 2008 From: jakob at fuyu.mindrot.org (Jakob Schlyter) Date: Tue, 4 Nov 2008 06:07:45 +1100 (EST) Subject: [flashboot] CVS: fuyu.mindrot.org: flashboot Message-ID: <20081103190745.DBA71A4F6C@fuyu.mindrot.org> CVSROOT: /var/cvs Module name: flashboot Changes by: jakob at fuyu.mindrot.org 08/11/04 06:07:45 Modified files: . : ChangeLog list.largekernel Log message: - (jakob) fixes for list.largekernel; from Yannick Gravel Diff commands: cvs -nQq rdiff -u -r1.178 -r1.179 flashboot/ChangeLog cvs -nQq rdiff -u -r1.11 -r1.12 flashboot/list.largekernel CVSWeb: http://cvsweb.mindrot.org/index.cgi/flashboot/ChangeLog?r1=1.178;r2=1.179 http://cvsweb.mindrot.org/index.cgi/flashboot/list.largekernel?r1=1.11;r2=1.12 Please note that there may be a delay before commits are available on the public CVSWeb site. From russ at quist.ca Tue Nov 4 02:43:23 2008 From: russ at quist.ca (Russell Sutherland) Date: Mon, 3 Nov 2008 10:43:23 -0500 Subject: [flashboot] problems compiling OpenBSD 4.4 Message-ID: <2cb417230811030743l39f66dd5s4c31ba104cb05997@mail.gmail.com> I've just updated the source tree of my build machine using cvs to revision: OPENBSD_4_4 When I attempt to perform the: # sh ./build-release.sh after almost an hour of compiling the error occurs: ===> bin/md5 cc -O2 -pipe -Wall -Wconversion -Wmissing-prototypes -I/usr/src/bin/md5 -nostdinc -idirafter /usr/local/src/flashboot/flash-dist/usr/include -c /usr/src/bin/md5/crc.c cc -O2 -pipe -Wall -Wconversion -Wmissing-prototypes -I/usr/src/bin/md5 -nostdinc -idirafter /usr/local/src/flashboot/flash-dist/usr/include -c /usr/src/bin/md5/md5.c cc -o md5 crc.o md5.o md5.o(.data+0x168): undefined reference to `SHA256_Init' md5.o(.data+0x16c): undefined reference to `SHA256_Update' md5.o(.data+0x170): undefined reference to `SHA256_Final' md5.o(.data+0x174): undefined reference to `SHA256_End' md5.o(.data+0x194): undefined reference to `SHA384_Init' md5.o(.data+0x198): undefined reference to `SHA384_Update' md5.o(.data+0x19c): undefined reference to `SHA384_Final' md5.o(.data+0x1a0): undefined reference to `SHA384_End' md5.o(.data+0x1c0): undefined reference to `SHA512_Init' md5.o(.data+0x1c4): undefined reference to `SHA512_Update' md5.o(.data+0x1c8): undefined reference to `SHA512_Final' md5.o(.data+0x1cc): undefined reference to `SHA512_End' collect2: ld returned 1 exit status *** Error code 1 Stop in /usr/src/bin/md5 (line 95 of /usr/share/mk/bsd.prog.mk). *** Error code 1 Stop in /usr/src/bin (line 48 of /usr/share/mk/bsd.subdir.mk). *** Error code 1 Stop in /usr/src (line 48 of /usr/share/mk/bsd.subdir.mk). *** Error code 1 Stop in /usr/src (line 73 of Makefile). 43m13.24s real 26m39.58s user 12m6.45s system How can I fix this dependency error? -- Russell Sutherland russ at quist.ca +1.416.696.7600 From yg at ygunit.net Thu Nov 6 00:08:35 2008 From: yg at ygunit.net (Yannick Gravel) Date: Wed, 05 Nov 2008 08:08:35 -0500 Subject: [flashboot] problems compiling OpenBSD 4.4 In-Reply-To: <2cb417230811030743l39f66dd5s4c31ba104cb05997@mail.gmail.com> References: <2cb417230811030743l39f66dd5s4c31ba104cb05997@mail.gmail.com> Message-ID: <49119AD3.9020108@ygunit.net> Hi Russell, The issue may be that you build server is not at the target revision. I suggest that you upgrade(install 4.4) on your build server first. I have an new install of OpenBSD 4.4 (patched to -stable) on which build-release.sh & cie work flawlessly. In essence, some changes between 4.3 and 4.4 may be playing against you. So the easy fix, install 4.4 release the patch and finish with rebuilding you flashboot images or you may get somewhere by only upgrading yacc, libc, libm, libiberty and gcc doing it the hard way. For the hard way, follow the instruction here on how to track current and what are the stop blocks between releases. http://www.openbsd.org/faq/upgrade-old.html Cheers Y. ps.: Make sure you updated you source tree to 4.4 after 2008/11/02 so that it include errata 001 and 002. Russell Sutherland wrote: > I've just updated the source tree of my build machine using cvs to > revision: OPENBSD_4_4 > > When I attempt to perform the: > > # sh ./build-release.sh > > after almost an hour of compiling the error occurs: > > ===> bin/md5 > cc -O2 -pipe -Wall -Wconversion -Wmissing-prototypes > -I/usr/src/bin/md5 -nostdinc -idirafter > /usr/local/src/flashboot/flash-dist/usr/include -c > /usr/src/bin/md5/crc.c > cc -O2 -pipe -Wall -Wconversion -Wmissing-prototypes > -I/usr/src/bin/md5 -nostdinc -idirafter > /usr/local/src/flashboot/flash-dist/usr/include -c > /usr/src/bin/md5/md5.c > cc -o md5 crc.o md5.o > md5.o(.data+0x168): undefined reference to `SHA256_Init' > md5.o(.data+0x16c): undefined reference to `SHA256_Update' > md5.o(.data+0x170): undefined reference to `SHA256_Final' > md5.o(.data+0x174): undefined reference to `SHA256_End' > md5.o(.data+0x194): undefined reference to `SHA384_Init' > md5.o(.data+0x198): undefined reference to `SHA384_Update' > md5.o(.data+0x19c): undefined reference to `SHA384_Final' > md5.o(.data+0x1a0): undefined reference to `SHA384_End' > md5.o(.data+0x1c0): undefined reference to `SHA512_Init' > md5.o(.data+0x1c4): undefined reference to `SHA512_Update' > md5.o(.data+0x1c8): undefined reference to `SHA512_Final' > md5.o(.data+0x1cc): undefined reference to `SHA512_End' > collect2: ld returned 1 exit status > *** Error code 1 > > Stop in /usr/src/bin/md5 (line 95 of /usr/share/mk/bsd.prog.mk). > *** Error code 1 > > Stop in /usr/src/bin (line 48 of /usr/share/mk/bsd.subdir.mk). > *** Error code 1 > > Stop in /usr/src (line 48 of /usr/share/mk/bsd.subdir.mk). > *** Error code 1 > > Stop in /usr/src (line 73 of Makefile). > 43m13.24s real 26m39.58s user 12m6.45s system > > How can I fix this dependency error? > > > From massimo at cedoc.mo.it Wed Nov 12 22:22:25 2008 From: massimo at cedoc.mo.it (Massimo Lusetti) Date: Wed, 12 Nov 2008 12:22:25 +0100 Subject: [flashboot] 4.4-CURRENT and LE565 Message-ID: <20081112122225.37f73865@intanto> I'm experiencing freezes with a -CURRENT of one and a half week ago with the COMMELL LE-565 board. To let the onboard CF card readed attached as wd0 to work I've to set 0x0ffc flags on wd* kernel device, plus to effectively use the four re nic I've to disable (comment out) pcibios kernel device. Does anyone else have tried a 4.4 system on these boards? Or have some hints on where i should look at? Thanks -- Massimo You definitely intend to start living sometime soon. From djm at mindrot.org Wed Nov 12 23:42:02 2008 From: djm at mindrot.org (Damien Miller) Date: Wed, 12 Nov 2008 23:42:02 +1100 (EST) Subject: [flashboot] 4.4-CURRENT and LE565 In-Reply-To: <20081112122225.37f73865@intanto> References: <20081112122225.37f73865@intanto> Message-ID: On Wed, 12 Nov 2008, Massimo Lusetti wrote: > I'm experiencing freezes with a -CURRENT of one and a half week ago > with the COMMELL LE-565 board. > > To let the onboard CF card readed attached as wd0 to work I've to set > 0x0ffc flags on wd* kernel device, plus to effectively use the four re > nic I've to disable (comment out) pcibios kernel device. > > Does anyone else have tried a 4.4 system on these boards? > Or have some hints on where i should look at? I had an LE565 until recently, but it stopped working with a puff of smoke :( It never had any trouble with CF, but it did have interrupt routing problems (long before 4.4) that went away with pcibios being turned off. You might want to try disabling apm instead and seeing if ACPI solves them - it didn't work for me the last time I checked, but there have been many improvements since then. -d From massimo at cedoc.mo.it Tue Nov 18 22:15:48 2008 From: massimo at cedoc.mo.it (Massimo Lusetti) Date: Tue, 18 Nov 2008 12:15:48 +0100 Subject: [flashboot] 4.4-CURRENT and LE565 In-Reply-To: References: <20081112122225.37f73865@intanto> Message-ID: <20081118121548.04e3de1a@intanto> On Wed, 12 Nov 2008 23:42:02 +1100 (EST) Damien Miller wrote: > I had an LE565 until recently, but it stopped working with a puff of > smoke :( Really sorry for that > It never had any trouble with CF, but it did have interrupt routing > problems (long before 4.4) that went away with pcibios being turned > off. You might want to try disabling apm instead and seeing if ACPI > solves them - it didn't work for me the last time I checked, but > there have been many improvements since then. > > -d Well with pcibios turned off the interrupts routes correctly but the CR reader still hangs with DMA issues. Did you set any particular value into the BIOS? I must say I've tried some without any luck. Thanks for any hints. -- Massimo Save energy: be apathetic. From stu at spacehopper.org Tue Nov 18 22:26:32 2008 From: stu at spacehopper.org (Stuart Henderson) Date: Tue, 18 Nov 2008 11:26:32 +0000 Subject: [flashboot] 4.4-CURRENT and LE565 In-Reply-To: <20081118121548.04e3de1a@intanto> References: <20081112122225.37f73865@intanto> <20081118121548.04e3de1a@intanto> Message-ID: <20081118112632.GY14612@pyxis.spacehopper.org> On 2008/11/18 12:15, Massimo Lusetti wrote: > On Wed, 12 Nov 2008 23:42:02 +1100 (EST) > Damien Miller wrote: > > > I had an LE565 until recently, but it stopped working with a puff of > > smoke :( > > Really sorry for that > > > It never had any trouble with CF, but it did have interrupt routing > > problems (long before 4.4) that went away with pcibios being turned > > off. You might want to try disabling apm instead and seeing if ACPI > > solves them - it didn't work for me the last time I checked, but > > there have been many improvements since then. > > > > -d > > Well with pcibios turned off the interrupts routes correctly but the CR > reader still hangs with DMA issues. > > Did you set any particular value into the BIOS? I must say I've tried > some without any luck. The Commell probably doesn't have DMA lines wired to the CF socket, but your card probably does support DMA. The OS can't detect this other than by lack of response from the card after trying DMA. This problem is compounded by many CF cards which don't correctly honour the RESET command sent when the OS tries to revert to PIO mode when it detects this situation. Try disabling DMA: boot -c, "change wd", and set the flags to 0x0ff0 - see wd(4) for more details. You can make it permanent with config(8) or by editing kernel config. It mightn't be a bad idea for the flashboot config files to use these flags anyway.. From stu at spacehopper.org Wed Nov 19 01:48:45 2008 From: stu at spacehopper.org (Stuart Henderson) Date: Tue, 18 Nov 2008 14:48:45 +0000 Subject: [flashboot] 4.4-CURRENT and LE565 In-Reply-To: <20081118152344.7dec026e@intanto> <20081118152237.4c502af6@intanto> References: <20081112122225.37f73865@intanto> <20081118121548.04e3de1a@intanto> <20081118112632.GY14612@pyxis.spacehopper.org> <20081118152344.7dec026e@intanto> <20081112122225.37f73865@intanto> <20081118121548.04e3de1a@intanto> <20081118112632.GY14612@pyxis.spacehopper.org> <20081118152237.4c502af6@intanto> Message-ID: <20081118144845.GD14612@pyxis.spacehopper.org> On 2008/11/18 15:22, Massimo Lusetti wrote: > For what i know flashboot kernel didn't support boot -c but... ah, I'm not sure about that, haven't tried. > I simply noted this issues coming out with >= 4.3 and not with my > previous version which was based on 4.1 DMA was not supported for most flash devices (except the majority of 1GB+ sandisk and one other brand I know of whose name escapes me) until 4.3. (specifically any device with 1-sector I/O). > BTW this is the error with default wd flags: > > pciide0:0:1: bus-master DMA error: missing interrupt, status=0x41 > wd1c: device timeout reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying > wd1(pciide0:0:1): timeout > type: ata > c_bcount: 512 > c_skip: 0 > pciide0:0:1: bus-master DMA error: missing interrupt, status=0x41 > wd1: transfer error, downgrading to Ultra-DMA mode 1 > wd0(pciide0:0:0): using PIO mode 4 > wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 1 > wd1c: device timeout reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying indeed, this is your device ignoring the reset sent when the OS downgrades. If you try one of the Sandisk cards which supports, it will almost certainly fall back correctly. From massimo at cedoc.mo.it Wed Nov 19 01:22:37 2008 From: massimo at cedoc.mo.it (Massimo Lusetti) Date: Tue, 18 Nov 2008 15:22:37 +0100 Subject: [flashboot] 4.4-CURRENT and LE565 In-Reply-To: <20081118112632.GY14612@pyxis.spacehopper.org> References: <20081112122225.37f73865@intanto> <20081118121548.04e3de1a@intanto> <20081118112632.GY14612@pyxis.spacehopper.org> Message-ID: <20081118152237.4c502af6@intanto> On Tue, 18 Nov 2008 11:26:32 +0000 Stuart Henderson wrote: > The Commell probably doesn't have DMA lines wired to the CF socket, > but your card probably does support DMA. The OS can't detect this > other than by lack of response from the card after trying DMA. This > problem is compounded by many CF cards which don't correctly honour > the RESET command sent when the OS tries to revert to PIO mode when > it detects this situation. That could be but i cannot understand why Damien didn't experience the same problem with the same board... > Try disabling DMA: boot -c, "change wd", and set the flags to 0x0ff0 > - see wd(4) for more details. For what i know flashboot kernel didn't support boot -c but... > You can make it permanent with config(8) or by editing kernel config. ... I've slightly modified a flashboot kernel (even GENERIC-RD) to totally disable DMA (0x0ffc) and with that the kernel/OS boot regularly. I simply noted this issues coming out with >= 4.3 and not with my previous version which was based on 4.1 > It mightn't be a bad idea for the flashboot config files to use these > flags anyway.. Yep... definitely since the flash isn't accessed at all during normal operation. Regards -- Massimo Change your thoughts and you change your world. From massimo at cedoc.mo.it Wed Nov 19 01:23:44 2008 From: massimo at cedoc.mo.it (Massimo Lusetti) Date: Tue, 18 Nov 2008 15:23:44 +0100 Subject: [flashboot] 4.4-CURRENT and LE565 In-Reply-To: <20081118112632.GY14612@pyxis.spacehopper.org> References: <20081112122225.37f73865@intanto> <20081118121548.04e3de1a@intanto> <20081118112632.GY14612@pyxis.spacehopper.org> Message-ID: <20081118152344.7dec026e@intanto> On Tue, 18 Nov 2008 11:26:32 +0000 Stuart Henderson wrote: > Try disabling DMA: boot -c, "change wd", and set the flags to 0x0ff0 > - see wd(4) for more details. BTW this is the error with default wd flags: pciide0:0:1: bus-master DMA error: missing interrupt, status=0x41 wd1c: device timeout reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying wd1(pciide0:0:1): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:0:1: bus-master DMA error: missing interrupt, status=0x41 wd1: transfer error, downgrading to Ultra-DMA mode 1 wd0(pciide0:0:0): using PIO mode 4 wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 1 wd1c: device timeout reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying Thanks for any hints. -- Massimo You are deeply attached to your friends and acquaintances. From massimo at cedoc.mo.it Wed Nov 19 02:47:54 2008 From: massimo at cedoc.mo.it (Massimo Lusetti) Date: Tue, 18 Nov 2008 16:47:54 +0100 Subject: [flashboot] 4.4-CURRENT and LE565 In-Reply-To: <20081118144845.GD14612@pyxis.spacehopper.org> References: <20081112122225.37f73865@intanto> <20081118121548.04e3de1a@intanto> <20081118112632.GY14612@pyxis.spacehopper.org> <20081118152344.7dec026e@intanto> <20081112122225.37f73865@intanto> <20081118121548.04e3de1a@intanto> <20081118112632.GY14612@pyxis.spacehopper.org> <20081118152237.4c502af6@intanto> <20081118144845.GD14612@pyxis.spacehopper.org> Message-ID: <20081118164754.124e3a11@intanto> On Tue, 18 Nov 2008 14:48:45 +0000 Stuart Henderson wrote: > DMA was not supported for most flash devices (except the majority > of 1GB+ sandisk and one other brand I know of whose name escapes me) > until 4.3. (specifically any device with 1-sector I/O). That all make sense. Great. > indeed, this is your device ignoring the reset sent when the OS > downgrades. If you try one of the Sandisk cards which supports, > it will almost certainly fall back correctly. As i said that make sense, thanks for taking time to answer, your comments were really appreciated, thanks. Regards -- Massimo Good night to spend with family, but avoid arguments with your mate's new lover.