No need to worry, I'm already downloading the ISOs. All will be well soon
enough :-D
--
www.kuro5hin.org -- technology and culture, from the trenches.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
Andrew Morton wrote:
> 1: Include `magic sysrq' support in the kernel and use ALT-SYSRQ-T and S
>when it has locked up. If you get some traces then please feed them
>into `ksymoops -m System.map' and report back.
That was locked as well, AFAIK.
> 2: If the above doesn't work, add `nmi
Hi. While doing some file tranfers to our new server (a Compaq Proliant
8way XEON 500 with 4gb ram and an EEPro100 NIC), the box socked solid (no
oops, no response via network, no response via console). The other hardware
in the system was a Compaq Smart Array 9SMART2 driver). It's runn
Colonel wrote:
> Ah, notice that the IRQ shifted? Perhaps there is something else on
> irq 10, such as the SCSI controller? My video cards always end up on
> that IRQ, perhaps the computer is still accessible via the network?
I would expect the IRQ to shift as the system has a different
motherb
Colonel wrote:
> Look in the people/mingo directory for a patch
The patch did not work.
> I have:
>
> Linux video capture interface: v1.00
> bttv: driver version 0.7.63 loaded
> bttv: using 2 buffers with 2080k (4160k total) for capture
> bttv: Host bridge needs ETBF enabled.
> bttv: Bt8xx car
I should mention, there are also NFS3 mounts on the system..
Dylan Griffiths wrote:
> -=-
>
> kernel BUG at inode.c:486!
> invalid operand:
> CPU:0
> EIP:0010:[]
> EFLAGS: 00013286
> eax: 001b ebx: c726a2c0 ecx: 0001 edx: c022a068
> es
Found these lurking in dmesg.. no timestamp on them, so I have no idea when
they happened.. the system seems ok, but I'm going to go fsck it a bit now..
Asus A7M266 board (VIA Southbridge). VIA82CXXX chipset support is on, use
DMA by default is on. ext2 partitions on a 20gb drive:
Filesystem
I upgraded a fileserver to 2.4.5 because of the RAID support (the 0.90
patch I grabbed did not apply cleanly to 2.2.19, despite it being a fresh
copy). Besides a nice speed increase (the EEPro now pumps 10 megs a second,
instead of 2 or 3), there is a problem with the video4linux in it.
Johannes Erdfelt wrote:
> > I think this may be a problem in the dc2xx.o then, since uhci didn't reveal
> > any new messages.
>
> It's possible. Many cameras are touchy wrt to the commands it receives.
> If one is slightly wrong, some of them will just stop talking.
Yeah, looks like I get to see
Robert Love wrote:
> > Can you give the CVS driver a try? Snapshots are available here:
> > http://opensource.creative.com/snapshot.html
> >
> > The driver in the kernel is based on a CVS snapshot from last summer, the
> > problem may be fixed in CVS. Also, the CVS driver is a common driver for
>
Johannes Erdfelt wrote:
> Could you load uhci with the debug=1 option?
I did an 'insmod uhci.o debug=1' but the dmesg output did not alter.
My easy steps to reproduce it is to 'delete selected images' in gphoto such
that there will be no images in the camera left when the operation is done.
At
Another thing I was happy to find working better in 2.4.5, was USB. I had
just dumped off ~70 high res pics (which would've taken forever via the
usual RS232 method), and was deleting the last pics when gphoto froze. The
dmesg log has the same messages it had before when I experimented with 2.4.
Kernel 2.4.5 has a working emu10k1 driver (all apps which hung with
2.2.19's driver worked fine, none of the working ones stopped working).
Could we perhaps see this backported to the 2.2.20 prepatches so that us 2.2
lovers can enjoy working sound?
--
www.kuro5hin.org -- technology an
Hi. The emu10k1 drivers shipped with 2.2.19 do not work well past 1Ghz.
In the original system, an Athlon 550, all OSS sound applications worked.
Loki games, libsdl games, XMMS, mplayer, RealPlayer, and the 'play' command
from the sox pacnage. When I upgraded my machine to a 1Ghz TBird
Alan Cox wrote:
> > I'm wondering if anyone knows/has a fix for memory past 64mb not
being
> > detected (unless you use append="mem=...M" in lilo) on the Via VT8371
> > [KX133] North bridge. (Please CC any replies since I'm off kernel list
> > atm.)
>
> Consult your BIOS vendor
Actually
I'm wondering if anyone knows/has a fix for memory past 64mb not being
detected (unless you use append="mem=...M" in lilo) on the Via VT8371
[KX133] North bridge. (Please CC any replies since I'm off kernel list
atm.)
--
www.kuro5hin.org -- technology and culture, from the trenches.
Mark Hahn wrote:
> mine (gigabyte ga-7zm) shows NONE of these under 2.4.0 or the last
> 100 or so pre-2.4 kernels. I have no idea what it does on obsolete kernels.
The symptoms have occured on a Gigabyte 7-ZX-1 and a 7-VX-1. I have a bit
of a suspicion that the 250W power supplies aren't enough
The VIA KT133 chipset exhibits the following bugs under Linux 2.2.17 and
2.4.0:
1) PS/2 mouse cursor randomly jumps to upper right hand corner of screen and
locks for a bit
2) Detects a maximum of 64mb of ram, unless worked around by the "mem="
switch
3) The clock drifts slowly (more so under heav
Hello. I recently upgraded my workstation from an EPoX MPV3-G to a
Gigabyte 7-VX-1. In XFree 3.3.6 the mouse cursor will randomly jump to the
upper-right hand corner of the screen and remain there until I scroll the
mousewheel. This used to happen on the old workstation when switching
b
The problem: I can't have the Tulip and EEPro drivers loaded at the same
time. If I have the Tulip driver loaded, and I load the EEPro driver, the
self check fails with 0x and complains that I don't have the card in
a bus master slot. If I have the EEPro driver loaded and the ether teste
Hi. Just wanted to report that the which things seems not to have been
fixed for Slackware (at least). Output of 'make menuconfig':
--8<--8<--8<--
/bin/sh: -c: line 1: syntax error near unexpected token `(/'
/bin/sh: -c: line 1: `if which: no gcc272 in
(/usr/local/qt/bin:/usr/local/bin:/
Hello. I have a firewall at home which is used to protect my LAN. But I
have a small problem in that for the past few months (using kernels 2.2.14,
and a 2.2.17pre with the TCP "hang" fix), outgoing connections to a
destination port of 80 seem to "hang," and will timeout. Connections to
22 matches
Mail list logo
