On 29 Jan 2001 14:33:39 +, Anton Altaparmakov wrote:
> Can anyone tell me whether there is support for the HP Colorado 8Gb (IDE
> version) tape drive in the Linux kernel and/or user space?
>
> If there is kernel support which of the kernel options do I have to enable
> / where do I get user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sajeev wrote:
> Hi.
> I am not able to mount my floppy drive. When I try to mount it gives me the
> following error
> 'mount: /dev/fd0 has wrong major or minor number'
> I am running the latest kernel release i.e. 2.4 .
> I tried recreating the node
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Torkar wrote:
> Matthias Juchem wrote:
>
> > Hi there.
> >
> > I rewrote my previous bugreport.pl in bash. I would appreciate it if you
> > had a look on this one. Run it once and give me feedback if you like.
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthias Juchem wrote:
> Hi there.
>
> I rewrote my previous bugreport.pl in bash. I would appreciate it if you
> had a look on this one. Run it once and give me feedback if you like.
>
Well it certantly works here. Almost everything is extracted co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timothy A. DeWees wrote:
> Hello,
>
> I am trying to compile the rtl8139 driver for my SMC
> 10/100 NIC. I have turned on all 10/100 devices (i.e. 3Com
> cards -n- such); however, I can not get the rtl driver to show
> up as an option in my menu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike wrote:
> Hi !!
>
> When i boot linux from rescue disk, i get following message:
>
> VFS: Insert root floppy disk to be loaded in RAM disk and press ENTER
>
> Now how can i create a root disk... I am trying to boot Redhat 6.0
>
>
> Regards,
> Mik
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I use redHat 7.0 and the much discussed kgcc :)
I edited the Makefile and changed to kgcc as usual.
This didn't happen with 2.4.0-test12.
This is what I get during a make bzImage (make dep && make clean already
done). Last in this mail is my config.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Hollis wrote:
> On Tue, 5 Dec 2000, Gerard Sharp wrote:
> > Gnea wrote:
> > > > [1.] One line summary of the problem:
> > > > Intermittent corruption of 4 bytes in SMP kernels using HPT366
> > > [snip]
> > > Have you tried updating the bios on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ARND BERGMANN wrote:
> Hi!
>
> I think I found a bug in the IDE subsystem. When I do 'cat
> /proc/ide/hde/identify', the system locks up completely, not
> even Alt+RysRq+B helps. Everything else under /proc/ide works.
> hdparm can cause the same symp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Riley wrote:
> Richard Torkar wrote:
> >
> > Well David, there is such a "manual".
> >
> > http://ftp.sunet.se/LDP/FAQ/faqs/GCC-SIG11-FAQ
>
> Yes. And if you ask the average new Linux user if they&#x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Riley wrote:
> Jeff Epler wrote:
> >
> > On Tue, Nov 21, 2000 at 04:08:26PM -0500, David Riley wrote:
> > > Windoze is not the only OS to handle bad hardware better than Linux. On
> > > my Mac, I had a bad DIMM that worked fine on the MacOS si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrei Smirnov wrote:
>
> I have a newly installed RH-7.0 distribution on a Celeron Pentium 400.
> When I tried to compile the kernel I got the following:
>
> 1. I ran make xconfig (or make menuconfig) and saved without changing any
>options - co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Torkar wrote:
> Jim Bonnet wrote:
>
> > I am using the 2.4.0-test10 kernel. I have a sound blaster 16 which
> > works fine under 2.2.17.
> >
> > I see that a while back someone posted on this problem previously
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Bonnet wrote:
> I am using the 2.4.0-test10 kernel. I have a sound blaster 16 which
> works fine under 2.2.17.
>
> I see that a while back someone posted on this problem previously but
> there were no answers I can find..
>
> Is support for sou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John R Lenton wrote:
> Several oops come up when using a lot of memory (using
> imagemagick on PIA1.tif from photojournal.jpl.nasa.gov/tiff,
> on a 64MB machine, for example)
>
> The weird thing is the oops happen *after* I've finished with
> im
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John R Lenton wrote:
> Several oops come up when using a lot of memory (using
> imagemagick on PIA1.tif from photojournal.jpl.nasa.gov/tiff,
> on a 64MB machine, for example)
>
> The weird thing is the oops happen *after* I've finished with
> im
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doing some heavy i/o on my 2.4.0-test10 (rar) while downloading at
10Mb/s at the same time resulted in this:
Oct 22 20:03:38 toor kernel: kernel BUG at vmscan.c:102!
Oct 22 20:03:38 toor kernel: invalid operand:
Oct 22 20:03:38 toor kernel: CPU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 14 Oct 2000, safemode wrote:
> cvs server: cannot rewrite CVS/Entries.Backup: No space left on device
>
> These are the sort of errors i'm getting from cvs but this is what df -m
> tells me on the partition i'm downloading on
> /dev/hda4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 29 Sep 2000, David M. Rector wrote:
>
> Has anyone tried Redhat 7.0 yet? What a mess.
>
> 1) It would not compile stock kernels out of the box. (ends at
> compress.S) with a fatal error.
Unable to reproduce.
> 2) Trying to compile the k
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 3 Sep 2000, Mohammad A. Haque wrote:
> Ok, looking better. I havent been able to forcibly corrupt my mailboxes
> like I did before. Yet anyways. I left my machine for about 10 mins and
> came back and noticed this...
>
> Sep 3 16:46:29 vipe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 29 Aug 2000, Bob_Tracy wrote:
> I *thought* I wanted to buy some memory from Crucial :-). Can't
> get there from here with my 2.4.0-test7 machine, but Win95 seems
> to be ok, and 2.4.0-test5 worked ok from a different location
> yesterday.
21 matches
Mail list logo
