Hi,
Tilman Schmidt wrote:
mISDN has two problems, which are of course interrelated:
mISDN has one problem that is even bigger than these: the kernel oopses
if modules aren't loaded in the right order. misdn-init works around
that, but if it doesn't work for some reason (and I can think of
Hi,
[please CC me, I'm not subscribed to the list]
I'm writing a driver for a pretty simple USB device, and most of what I
need I can see in similar drivers; right now I'm lifting a lot of code
from drivers/usb/class/usblp.c.
In the read routine, this driver gathers a few locks, then checks
whet
On Thu, 17 May 2001, Jussi Hamalainen wrote:
> > CPU is a Pentium 166 MMX on an Asus TX97 mainboard, ISA cards are a 3c509
> > and a Soundblaster.
> The Asus TX97 is known to be a CPU toaster. I've replaced dozens of
> them because of overheating problems. I don't know why the problem
> seems to
Hi,
I just switched my brother's computer to a 2.2 kernel, and now the CPU
overheats under Linux after about half an hour (reproducible). It works
fine under Windows 95b and worked under Linux 2.0.38.
CPU is a Pentium 166 MMX on an Asus TX97 mainboard, ISA cards are a 3c509
and a Soundblaster.
On Mon, 7 May 2001, Dan Hollis wrote:
> > Erm, it was bad RAM everytime it happened to me. On standard PCs, you
> > don't see those because you don't have ECC and the error is simply not
> > detected.
> So a 440bx motherboard with ECC ram is a non-standard PC?
I bet the board doesn't force you
On Mon, 7 May 2001, Bene, Martin wrote:
[MCE caused by bad RAM]
> I don't think there is a way a machine check exception can be triggered by
> software - which it would have to be in order to be caused by bad RAMs.
A MCE is triggered by an ECC error - no software involved. A good trap
handler w
On Mon, 7 May 2001, Bene, Martin wrote:
> Definitely not caused by:
> Bad Rams, mb-chipset.
Erm, it was bad RAM everytime it happened to me. On standard PCs, you
don't see those because you don't have ECC and the error is simply not
detected.
Simon
--
GPG public key available from ht
On Fri, 4 May 2001, Nico Schottelius wrote:
> I have searched a long time for a method to disable the internal
> speaker for every application, every daemon and so on.
It would be cool if that weren't a compile time option but configurable at
runtime (via sysctl).
Simon
--
GPG public key a
On Tue, 17 Apr 2001, Grover, Andrew wrote:
> We are going to need some software that handles button events, as well as
> thermal events, battery events, polling the battery, AC adapter status
> changes, sleeping the system, and more.
Yes, that will be a separate daemon that will also get the eve
On Tue, 17 Apr 2001, Andreas Ferber wrote:
[Extending the current signalling mechanism]
> The problem with this is that there is no single init. Most
> distribution run the same SysV init, but there are quite a few init
> replacements around. Should we really break all of them?
We don't break a
On Mon, 16 Apr 2001, Grover, Andrew wrote:
> > From: Pavel Machek [mailto:[EMAIL PROTECTED]]
> > There are 32 signals, and signals can carry more information, if
> > required. I really think doing it way UPS-es are done is right
> > approach.
> I would think that it would make sense to keep shut
On Tue, 17 Apr 2001, Andreas Ferber wrote:
> > Okay, but at least take a better signal than SIGINT, probably one that the
> > init maintainers like so it gets adopted faster (or extend SIGPWR).
> Extending SIGPWR will break inits not yet supporting the extensions,
> so this is IMO not an option.
On Mon, 16 Apr 2001, Pavel Machek wrote:
> > Because we'd be running out of signals soon, when all the other ACPI
> > events get available.
> There are 32 signals, and signals can carry more information, if
> required. I really think doing it way UPS-es are done is right
> approach.
Okay, but a
On Mon, 16 Apr 2001, Andreas Ferber wrote:
> > A power failure is a different thing from a power button press.
> And why not do exactly this with init? Have a look in /etc/inittab:
> You can shut down your machine there, but you can also have it play a
> cancan on power failure. It is up to you
On Fri, 13 Apr 2001, Pavel Machek wrote:
> > Then a more general user space tool could be used that would do policy
> > appropriate stuff, ending with init 0.
> init _is_ the tool which is right for defining policy on such issues.
> Take a look how UPS managment is handled.
A power failure is
On Thu, 8 Mar 2001, Geert Uytterhoeven wrote:
> - There are still some politically-incorrect (PI) logos of a penguin holding
> a glass of beer or wine (or perhaps even worse? :-).
Heh. Those are cool. Don't remove them. The Windoze people always look
jealous at the beer tux... :-)
Simo
On Thu, 1 Mar 2001, Sébastien HINDERER wrote:
> According to linux/drivers/console.c, function setterm_commands, case 12,
> one can change the virtual console by sending an escape sequence to
> /dev/cnsole (what I want to do), hower, this is not documented in man
> pages.
From the source of the
On Thu, 1 Mar 2001, Sébastien HINDERER wrote:
> Could someone tell me where I can find a document listing all the
> escape-sequences that could be sent to the console (/dev/console) and what
> they do.
Please don't use those sequences directly, as not everyone has
/dev/console on a vt. You can f
On Tue, 20 Feb 2001, michaelc wrote:
> I found that acpi driver has some bugs, I compiled the 2.4.2-pre4
> kernel with the acpi support option and SMP enabled, it caused hang at the
> boot time, but when I disabled the SMP option, it 's OK , so I look
> into the acpi driver source c
On Mon, 23 Oct 2000, Joe wrote:
> 1) If it does not already do this it should probably start with
> warnings like printk statements. (I'll hope it does).
A user will only see printks if he sits at the console (=> desktop
machine) and there is no X running that has grabbed the graphics board (=>
On Sun, 8 Oct 2000, David Ford wrote:
> > > Linux 2.4 Status/TODO Page
> > > * RTL 8139 cards sometimes stop responding.
> > (2.2.18pre) Both drivers oops a lot for me, so there seems to be a more
> > serious problem here.
> This is the 2.4 status/todo page, see t
On Mon, 9 Oct 2000 [EMAIL PROTECTED] wrote:
> Linux 2.4 Status/TODO Page
> * RTL 8139 cards sometimes stop responding. Both drivers don't
>handle this quite good enough yet. (reported by Rogier Wolff,
>tentatively reported as fixed by David Ford.)
(
On Mon, 2 Oct 2000, Marcelo Tosatti wrote:
> > I'm running 2.2.17 with the rtl8139 fix from 2.2.18pre, and after about
> > two hours of normal operation (no crashes, no fs corruption -- Thanks
> > Jeff) the network suddenly stops responding. Calling "ifconfig" (just
> > looking at the stats) some
On Mon, 2 Oct 2000, Marcelo Tosatti wrote:
> > I'm running 2.2.17 with the rtl8139 fix from 2.2.18pre, and after about
> > two hours of normal operation (no crashes, no fs corruption -- Thanks
> > Jeff) the network suddenly stops responding. Calling "ifconfig" (just
> > looking at the stats) some
Hi,
I'm running 2.2.17 with the rtl8139 fix from 2.2.18pre, and after about
two hours of normal operation (no crashes, no fs corruption -- Thanks
Jeff) the network suddenly stops responding. Calling "ifconfig" (just
looking at the stats) sometimes cures the problem, taking all interfaces
down and
Hi,
there seems to be a number of issues regarding the above setup. Symptoms:
- Directory listings of big (read: more than approx. 200 files)
directories show up as empty in 95% of all cases
- Requests fail randomly (5-10%)
No. 2 is especially annoying for cron jobs, because the problems
Hi,
I just upgraded our server (486DX2/120, running 186 days`) with a 100MBit
RTL8139B network card and moved from 2.2.14 to 2.2.17 in this process,
using the same .config (oldconfig) with two differences: IPv6 and the
RTL8139 drivers.
After about 20k of network activity the machine crashes (I c
On Thu, 7 Sep 2000, Andrey G. Kaplanov wrote:
> For instance, following command writes transDsc descriptor to the
> stream streamDsc.
> int ret = ioctl(streamDsc, I_SENDFD, transDsc);
> On Red Hat Linux kernel 2.2.16 ret is -1, errno is 22 - Invalid argument.
Implementing this ioctl for Li
On Thu, 7 Sep 2000, Martin Dalecki wrote:
> > I've done an implementation of some of the Win32 "system calls" in a kernel
> > module in an attempt to speed up Wine.
> 1. Linux is UNIX not NT... (in terms of API)
What about a Win32 personality?
> 2. WINE in itself is barely usefull - even in fa
On 4 Sep 2000, Henning P. Schmiedehausen wrote:
["FreeBSD will laugh at us"]
> And Linux did not succeed because it was aimed "at the server market"
> or "at the end user" but because there is a bunch of people _that_
> _do_ _not_ _care_ _at_ _all_ about the "marketability" of a feature
> but fo
On 29 Aug 2000, Stuart Lynne wrote:
> >I think this needs to be resolved ASAP. I don't have kernel sources handy,
> >so I cannot tell you whether the functions are actually worth being
> >protected (inb/outb doesn't belong to this group really),
> If it is in the header file I think it should be
31 matches
Mail list logo
