Make broken, top broken, flock errors, kernel modules broken

Make broken, top broken, flock errors, kernel modules broken

Post by William Burr » Sat, 18 May 1996 04:00:00

So many repetitive messages asking the same questions!  Does noone bother
to grep the topics for possible solutions?

Here are some of the answers to your problems:

If you upgrade to ELF libraries, you need an ELF linker:  get new

If you upgrade your kernel, you will likely need to upgrade to (or higher):
termcap 2.0.8, proc-ps.0.99a, libc 5.3.12 (see below!), modules-1.3.69f,
gcc 2.7.2.

If you upgrade your libc, you will need to patch or upgrade make to make

It may possible that when you upgrade your compiler, you may need to
install a new (ELF) libc.

William Burrow  --  Fredericton Area Network


1. 2.5: ieee1394 still broken, vesafb still broken, ipv6 still broken

I am surprised that Linus thinks now is the time to move towards a
stable 1.6 release, I don't see any sign for increased stability in
2.5.59.  I am still forced to use 2.5.53 because that is the last kernel
that has working ieee1394.

To reiterate the problems:

  ohci1394 detects my controller, sbp2 gets the same unsolicited packets
    from my Maxtor firewire hard disk as 2.5.53, but no sign of a
    detected SCSI device.

  vesafb is told to go to 1024x768-32, does so, but then reads from my
    TFT display that 1600x1200 is the native resolution and then thinks
    that is the resolution it is using (even fbset says so).  The result
    is that I can only see the upper half of my screen, and the display
    is garbled to boot because the line length is too large, meaning
    writing something in the right half of the 1600x1200 screen results
    in overwriting something on the left of my real 1024x768 screen.

  ipv6 is still broken because running npush and then starting npoll on
    another virtual terminal will hang the kernel hard instantaneously.
    So hard, in fact, that I don't have a trace I could give you.  Since
    vesafb is broken (hint, hint), I only see the last lines, which say
    something about a fatal error in an interrupt routine and a callback
    where the last lines are call_socketcall and call_syscall (IIRC).
    npush and npoll are from the ncp package, which you can find at

We should not make any wind about even mentioning 2.6 to the press until
we at least reach the basic functionality requirements, let alone
stability of 2.4.  I find the situation pretty embarassing considering
that I am running around and telling customers to install Linux (come
see me at LinuxTag, by the way, I'm talking about scalable network
programming on Linux there.  It would be really embarassing if I
couldn't present the slides about the cool 2.5 features because 2.5 just
happens to still suck then.

And if you are right now considering to tell me that I should go to
nvidia tech support, please limit yourself to private email as to reduce
the embarrassment and damage you are causing to the rest of this list
with Theo DeRaadt style user alienation.  And unless you are going to
investigate these, don't even bother with private email as well.
Bullshit like that makes Windows look like the better option.  The
FreeBSD people are probably having a field day with this nvidia episode

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at
Please read the FAQ at

2. Help: Linux network slow

3. Flock () broken error help

4. joystick , etc

5. 1.3.9x and broken flock() error fix.

6. Need PC-Linux serial port re-direction

7. is flock broken in 2.4 or 2.5 kernels or what does this mean?

8. Solaris x86 and sound card

9. Linux-1.3.97 - kernel: fcntl_setlk() called by process 74 with broken flock() emulation

10. Kernel 1.3.95 & broken flock / fcntl

11. Linux-1.3.97 - kernel: fcntl_setlk() called by process 74 with broken flock() emulation

12. broken flock(), how do I get rid of this error?

13. Kernel 2.4.8 - EMU10K1 - Kernel Compile Breaks in Module main.o