ad0: WRITE command timeout...
Hello, After upgrading a computer from FreeBSD 4.8-something to 4.10-RELEASE-p3, I'm getting lots of the following: ad0: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done I cannot recall seeing these before. Would anyone know what this implies? It's still doing an installworld in single user mode, so I cannot post the disk make and model yet... And please CC me in your reply - I am not on the -questions list. Best regards, Are Bryne -- Communiqué DAOffice: +47 22 44 33 99 Postboks 9050 Grønland Mobile:+47 900 22 009 NO-0133 Oslo URL: http://www.communique.no___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ad0: WRITE command timeout...
Hello, After upgrading a computer from FreeBSD 4.8-something to 4.10-RELEASE-p3, I'm getting lots of the following: ad0: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done I cannot recall seeing these before. Would anyone know what this implies? It's still doing an installworld in single user mode, so I cannot post the disk make and model yet... And please CC me in your reply - I am not on the -questions list. Best regards, Are Bryne -- Communiqué DAOffice: +47 22 44 33 99 Postboks 9050 Grønland Mobile:+47 900 22 009 NO-0133 Oslo URL: http://www.communique.no___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad0: WRITE command timeout...
On Thu, 4 Nov 2004, Nelis Lamprecht wrote: On Thu, 4 Nov 2004 14:10:42 +0100 (CET), Are Bryne [EMAIL PROTECTED] wrote: [...] After upgrading a computer from FreeBSD 4.8-something to 4.10-RELEASE-p3, I'm getting lots of the following: ad0: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done The disk in question is a FUJITSU MPC3043AT/6018 using ATA/ATAPI rev 3 according to atacontrol. It is master on its controller and uses UDMA33 transfers, and has an idle PIO4 cd-rom player as a slave. The controller is identified in dmesg as: atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on pci0 [...] Hi, Seen this once before and in my case it was a faulty hard drive cable. Check to see whether your cable is not loose or incorrectly inserted and perhaps try a new one. Thank you - I will check that. It may also be caused by an incorrect DMA setting if memory serves me correct. I might try turning DMA off to see if that helps... Nelis Again, please CC me to make sure I see the whole thread. Regards, Are Bryne -- Communiqué DAOffice: +47 22 44 33 99 Postboks 9050 Grønland Mobile:+47 900 22 009 NO-0133 Oslo URL: http://www.communique.no___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
VueScan and FreeBSD's Linux (USB) emulation
Hello, I am trying to get the Linux version of VueScan (http://www.hamrick.com/) to work under FreeBSD's Linux emulation. With FreeBSD 4.7-RELEASE-p9, linux_base-7.1_5, and RedHat's gtk+-1.2.9-4.i386.rpm, it starts and operates ok, except for not finding any USB devices. I have an Epson USB scanner that operates fine under Sane, but find the available frontends lacking when wanting to scan negatives... Is this supposed to work? I.e., should VueScan and other Linux programs be able to access USB connected scanners and other devices? There does not seem to be any major changes to the Linux code further down the RELENG_4 branch... Does anyone have any suggestions as to how I could make this work? Thank you in advance. Regards, Are Bryne [Please keep [EMAIL PROTECTED] CC'd as I am not on the list. Thx.] -- Communiqué DAOffice: +47 22 44 33 99 Postboks 9050 Grønland Mobile:+47 900 22 009 NO-0133 Oslo URL: http://www.communique.no ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
`bfd_arch_' undeclared in make buildworld (RELENG_4_6)
Hello, I am getting the following errors when doing a make buildworld on freshly (20020927) cvsup'ed RELENG_4_6 sources. Last make world on this machine was about 20010921, and it is therefore currently 4.4-STABLE. Does anyone have a clue to what this could be? I have a cvsup refuse file that keeps sendmail, r* utilities and YP stuff out of my source tree, and patch files that make sure these are not built. However, I haven't touched ld's sources or anything related (that I can conceive of, at least). === gnu/usr.bin/binutils/ld cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/ld/i386 -I/usr/src/gnu/usr.bin/binutils/ld -I/usr/src/gnu/usr.bin/binutils/ld/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/include -DDEFAULT_EMULATION=\elf_i386\ -DTARGET=\i386-unknown-freebsd\ -DSCRIPTDIR=\/usr/libdata\ -I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld -I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/bfd -DVERSION=\2.11.2 20010719 [FreeBSD]\ -DBFD_VERSION=\2.11.2 20010719 [FreeBSD]\-c eelf_i386.c eelf_i386.c: In function `gldelf_i386_before_parse': eelf_i386.c:71: `bfd_arch_' undeclared (first use in this function) eelf_i386.c:71: (Each undeclared identifier is reported only once eelf_i386.c:71: for each function it appears in.) *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/ld. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I looked through the sources, and cannot find any reference to 'bfd_arch_', only bfd_arch_i386, etc. Thanks in advance. [And please keep me cc'd.] Cheers, Are Bryne -- Communiqué DAOffice: +47 22 44 33 99 Postboks 9050 Grønland Mobile:+47 900 22 009 NO-0133 Oslo URL: http://www.communique.no To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
