Re: malfunctioning floppy drive
On Fri, Oct 03, 2003 at 02:47:56PM -0700, Joshua Sanders wrote: This may seem obvious, but have you checked the cable on the back of the Floppy? Is pin 1 aligned correctly? I think you are correct on this - the cable is twisted 180 degrees, either at the mobo or at the floppy drive. The giveaway was that the activity light stays on constantly, which is always caused by this particular type of mis-cabling. Good luck. --Jay++ - Jay A EstabrookHPTC - LINUX support Hewlett-Packard Company - MRO1-2/K15 (508) 467-2080 200 Forest Street, Marlboro MA 01752 [EMAIL PROTECTED] -
Re: malfunctioning floppy drive
On Sat, 4 Oct 2003 14:23:14 -0400 JE == Jay Estabrook [EMAIL PROTECTED] wrote: JE JE On Fri, Oct 03, 2003 at 02:47:56PM -0700, Joshua Sanders wrote: This may seem obvious, but have you checked the cable on the back of the Floppy? Is pin 1 aligned correctly? JE JE I think you are correct on this - the cable is twisted 180 degrees, JE either at the mobo or at the floppy drive. JE JE The giveaway was that the activity light stays on constantly, which is JE always caused by this particular type of mis-cabling. Another guess is absence of floppy drive support in kernel (not compiled in, or compiled as module and not loaded). -- Alexander Kotelnikov Saint-Petersburg, Russia
Re: mysterious xmms buildd failure on alpha buildd
On Sat, Sep 27, 2003 at 09:38:17PM -0500, Kelledin wrote: On Saturday 27 September 2003 06:37 pm, Josip Rodin wrote: [...] I tried to build it on escher and faure and it worked fine on both, there was no such failure. I couldn't do it on lully itself as there was no libgtk1.2-dev (maybe I should ask -admin to install it?). Yes, ask an admin to install it. That contains the static gtk+ libraries, which you WILL need to build xmms with --enable-static. When you're linking stuff into a static library, everything you link in needs to either be a static library or an object file. I imagine libtool is trying to build the static mpg123 plugin, needs the static gtk+ library for it, but can only find the dynamic version. Of course, this only causes a problem when building the static plugin, and guess when the errors are thrown away... :/ No, unfortnately that's not the cause, I've tried the failing commandline: riff Input/mpg123 gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../xmms -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -D_REENTRANT -I../../intl -I../.. -g -O2 -Wall -Wpointer-arith -finline-functions -ffast-math -funroll-all-loops -MT mpg123.lo -MD -MP -MF .deps/mpg123.Tpo -c mpg123.c -o mpg123.o mpg123.c: In function `decode_loop': mpg123.c:837: error: unrecognizable insn: (insn 555 554 2298 32 0x2f87918 (set (reg/f:DI 366) (symbol_ref:DI (@Lmpg123_ip))) -1 (nil) (expr_list:REG_EQUAL (symbol_ref:DI (@Lmpg123_ip)) (nil))) mpg123.c:837: internal compiler error: in extract_insn, at recog.c:2175 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. Exit 1 riff Input/mpg123 gcc --version gcc (GCC) 3.3.2 20030908 (Debian prerelease) which seems to be the ICE already filed as #207564. Cheers Thimo
Re: mysterious xmms buildd failure on alpha buildd
Thimo Neubauer [EMAIL PROTECTED] writes: mpg123.c:837: error: unrecognizable insn: (insn 555 554 2298 32 0x2f87918 (set (reg/f:DI 366) (symbol_ref:DI (@Lmpg123_ip))) -1 (nil) (expr_list:REG_EQUAL (symbol_ref:DI (@Lmpg123_ip)) (nil))) mpg123.c:837: internal compiler error: in extract_insn, at recog.c:2175 This is a well known gcc bug (http://gcc.gnu.org/PR11717), fixed in GCC 3.3.2 which is to be released Real Soon Now[tm]. -- Falk
