USB-keyboard not recognize after connection

I have an USB-keyboard/-mouse connected to a switchbox which is itself connected to a PowerMac (MacOS) and my PC running Linux. I do regularly switch my USB-devices between Mac and PC. Since I upgraded to kernel 2.4.0 and now 2.4.2 it happens from time to time that Linux does not recognize my keyb

Linux should better cope with power failure

Lately I had an USB failure, leaving me without any access to my system since I only use an USB-keyboard/-mouse. All I could do in that situation was switching power off and on after a few minutes of inactivity. From the impression I got during the following startup, I assume Linux (2.4.2, EXT2-fi

Re: Linux should better cope with power failure

Jeremy Jackson wrote: > > Brian Gerst wrote: > > > "Richard B. Johnson" wrote: > > > > > > On Mon, 19 Mar 2001, Otto Wyss wrote: > > > > > > > Lately I had an USB failure, leaving me without any access to my system [..] > > &

Re: Linux should better cope with power failure

"Stephen Gutknecht (linux-kernel)" wrote: > > Otto, > [...] > Have you considered telnet into your box from a second machine? Even a 486 > system would do this fine... network cards are cheap. You could try to > recover the system or at least do a shutdown. > It was just a simple test machine

Re: Linux should better cope with power failure

> I had a similar experience: > X crashed , hosing the console , so I could not initiate > a proper shutdown. > > Here I must note that the response you got on linux-kernel is > shameful. > Thanks, but I expected it a little bit. All around Linux is centered around getting the highest performanc

Re: Linux should better cope with power failure

> No, the correct answer is if you want a reliable recovery then run your disks > in non write buffered mode. I.e. turn on sync in fstab. > You probably haven't tried to use sync or you would have noticed the performace penalty. I think nobody really considers sync an alternative. O. Wyss - To

Re: Linux should better cope with power failure

> > You probably haven't tried to use sync or you would have noticed the > > performace penalty. I think nobody really considers sync an alternative. > > > > O. Wyss > > You can't have the best of everything. There are tradeoffs. A viable option is > a >journaled filesystem. Linux boasts a fe

Framebuffer drivers and start options

I've used an ATI RageII card with frame buffer driver atyfb compiled into the kernel and specified 'append = "video=atyfb:800x600@72"' in lilo.conf. I've just gotten a second computer with a ATI RagePro128 card (frame buffer driver aty128fb) and compiled both driver as modules. Now the 'append...'

Console display in portrait mode with unusual dpi resolution

Overview: At business I just got a brand new EIZO 18" LCD display L675 to test its usability for working in portrait mode to show a full A4 page. These test were done on Windows NT4 but I'd really like to know how well Linux would have done. I'm going to describe all the obstacles I encountered on

Why is debugging under Linux such a pain

Sorry if this is off topic here but IMO this _has_ to be discussed in a broader audience since it probably has a rather large impact about the acceptance of Linux even if it isn't the kernel's fault. I just build the minimal sample of the wxWidgets framework and it crashed when playing around with

PROBLEM: Framebuffer does not handle kernel parameter when compiled as a module

I have two almost identical computers with different graphic cards (ATI RageII, Matrox G200). I'd like to have the framebuffer devices compiled as modules, but then the kernel parameters from lilo (i.e. append = "video=atyfb:800x600@72") doesn't work. Afterwards switching with fbset works. It seem