On Mon, Jan 08, 2001 at 02:56:05PM -0800, J Sloan wrote:
> In my case, that meant nuking mesa from my system and
> letting Linux use what was left, which got me back the good
> accelerated performance - you may choose a less drastic
> option. I don't see any breakage from the absence of mesa.
We
On Mon, Jan 08, 2001 at 10:45:09PM +, Michael D. Crawford wrote:
> glxinfo says dri is not available if I remove the library as I did. So I
> rebuilt Mesa and reinstalled it. The full output of glxinfo on my machine
> follows. Note that it says "direct rendering: Yes" but the version string
On Mon, Jan 08, 2001 at 04:37:32PM -0800, J Sloan wrote:
> Ragnar Hojland Espinosa wrote:
> > Well, the real problem is that (at least Voodoo3) DRI didn't work _before_
> > with the "latest" test and pre kernels, and X < 4.0.2 (unless there was some
> > co
On Fri, Jan 19, 2001 at 11:15:27AM +, Jason Saunders wrote:
> Since about 2.4.0-prerelease, I've been getting odd errors on compilation. A
> sample is included below. It happens for every source file that includes
> - is it anything to worry about?
>
> In file included from /usr/src/linux/
On Sat, Jan 20, 2001 at 05:19:17PM +0100, [EMAIL PROTECTED] wrote:
> I just wanted to say that Linus´ CodingStyle is the ONLY SANE style of
> writing code in bigger projects. At university we are forced to use exactly the
And the lord spake, saying, "First shalt thou write thy holy code. Indentin
On Sun, Nov 19, 2000 at 07:00:41PM -0800, Dan Hollis wrote:
> On Mon, 20 Nov 2000, David Woodhouse wrote:
> > On Sun, 19 Nov 2000, Dan Hollis wrote:
> > > Writeprotect the flashbios with the motherboard jumper, and remove the
> > > cmos battery.
> > > Checkmate. :-)
> > Only if you run your kernel
On Tue, Nov 21, 2000 at 08:14:51AM +0300, Eugene Crosser wrote:
> zero entries on the mounted CD, and each "ls" attempt causes this
> kernel message:
>
> _isofs_bmap: block < 0
Same here, except that once showed
_isofs_bmap: block >= EOF (1633681408, 4096)
--
/| Ragnar Højland
On Thu, Nov 23, 2000 at 12:26:30AM +, Russell King wrote:
> Albert D. Cahalan writes:
> > > Function entered at [] from []
> > > Function entered at [] from []
> > > Code: e51f2024 e5923000 (e5813000) e3a0 e51f3030
> >
> > All those numbers get looked up. Keep going for another 25 lines t
On Thu, Nov 23, 2000 at 04:50:22AM +0100, [EMAIL PROTECTED] wrote:
> Below a working patch for which the isofs images I got
> all are OK. (There is still a lot of silliness here -
> superfluous parentheses, a rename of isofs_cmp to isofs_comp
> in one file to avoid confusion with the isofs_cmp in
On Thu, Nov 23, 2000 at 09:20:15AM -0800, Linus Torvalds wrote:
> Can you check whether the single patch of _just_ removing the extra "f_pos
> >= i_size" test in do_isofs_readdir() fixes it? The other changes of
> Andries patch look like they should not affect code generation at all, but
> I'd sti
I still get those at random (and no, I'm not hot-rebooting from ms windows)
Normally the cookie is 0xfff8 or similar.
--
/| Ragnar Højland Freedom - Linux - OpenGL Fingerprint 94C4B
\ o.O| 2F0D27DE025BE2302C
=(_)= "Thou shalt
as per subject.. BUG in schedule (sched.c, 115)
--
/| Ragnar Højland Freedom - Linux - OpenGL Fingerprint 94C4B
\ o.O| 2F0D27DE025BE2302C
=(_)= "Thou shalt not follow the NULL pointer for 104B78C56 B72F0822
U chaos and
On Wed, Dec 06, 2000 at 02:00:12PM -0800, Mike Kravetz wrote:
> Ragnar,
>
> Are you sure that was line 115? Could it have been line 515?
Yes, yes, it was 515. 115 is the result of human cache corruption ;)
> Also, do you have any Oops data?
It just froze there.
--
/| Ragnar Højland
On Fri, Sep 08, 2000 at 11:10:13PM +0200, Kurt Garloff wrote:
> Stop making stupid statements like this, please, and comparing well-defined
> RFC standards with proprietary formats.
> MIME is a way for people that happen to use non 7bit characters to be able
> to print their name correctly, even
On Thu, Oct 19, 2000 at 11:04:44AM -0700, Dan Hollis wrote:
> On Thu, 19 Oct 2000, Alex Buell wrote:
> > Feel free to send complaints to [EMAIL PROTECTED] and get his account
> > yanked for abuse of mailing lists.
>
> http://www.ilan.net/contact.htm for a nice list of addresses to send
> complai
On at least test8 onwards on hd[abc] I sometimes get an
printk("%s: IRQ probe failed (0x%lx)\n", drive-> name, cookie);
with cookie being ~0
VT82C586
hda: ST320423A, ATA DISK drive
hdc: SAMSUNG VG34323A (4.32GB), ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0
On Wed, Nov 01, 2000 at 06:44:25PM -0600, M.H.VanLeeuwen wrote:
> "CRADOCK, Christopher" wrote:
> > I have a similar hardware list and I don't observe any of these problems on
> > 2.4.0-test10x. Is it possibly a hardware conflict somewhere?
> >
> > What I do see occasionally is if X was ever heav
On Thu, Nov 02, 2000 at 06:57:06PM +0100, Ragnar Hojland Espinosa wrote:
> Well, here never did until today :) With test9, I had left the box idle
Just happened with test10, same circumstances .. font map got corrupted, and
noise on the screen. Switching back and forth from X to a vc fixed
On Fri, Nov 03, 2000 at 01:25:10AM -0500, [EMAIL PROTECTED] wrote:
> > Just happened with test10, same circumstances .. font map got corrupted, and
> > noise on the screen. Switching back and forth from X to a vc fixed it, tho.
> >
> > Sort of amusing that it (apparently) only happens with ppp
On Thu, Nov 09, 2000 at 12:13:21PM +0100, Erik Mouw wrote:
> On Thu, Nov 09, 2000 at 12:08:32PM +0100, Michele Iacobellis wrote:
> > [Summary]
> > No tcp connection establishment with 2.4
> >
> [snip]
>
> Disable "Explicit congestion notification support" in the networking
> options. It breaks w
On Wed, Dec 13, 2000 at 12:41:19AM +0100, J . A . Magallon wrote:
> There are various patches-ways-to-do available, kernel gurus are still working
> on it...
> (leave always some 4% of mem for root, kill some process when mem is exhausted,
> which one to kill...)
which is a bad idea; 4% of 1GB i
On Thu, Sep 28, 2000 at 01:45:40AM +0200, Igmar Palsenberg wrote:
> Some arguments why not to use it in the kernel :
>
> - C++ gives overhead. With something like a kernel that's unwanted.
You pay for what you use, no less no more. C++ compilers don't generate
bloated code `per se' but, yes, i
On Wed, Sep 27, 2000 at 05:38:23PM -0400, Mike A. Harris wrote:
> This message may be seen by some to be OT, but it concerns
> ISP's SMTP. I figured despite the slowness, it would solve the
> problem. Now I'm getting back all sorts of bounces from machines
> blocking using something at "www.mail
On Thu, Sep 28, 2000 at 04:44:55PM -0400, Horst von Brand wrote:
> Ragnar Hojland Espinosa <[EMAIL PROTECTED]> said:
> > On Thu, Sep 28, 2000 at 01:45:40AM +0200, Igmar Palsenberg wrote:
> > Let's put it the other way... there aren't many people who know C++
&g
On Thu, Sep 28, 2000 at 08:25:09PM +, Miquel van Smoorenburg wrote:
> In article <3776575819.970144217@[10.10.1.2]>,
> And unreliable ISP SMTP servers? Hard to imagine, as 99.5% of the
> userbase undoubtedly uses that SMTP server and I can't believe
> that a reasonable ISP randomly drops email
On Fri, Sep 29, 2000 at 11:41:20AM +0200, Lars Steinke wrote:
> When using ide-scsi to access a CDRW writer, the recording process works
> but I am not able to mount any CD-ROM media in that drive for reading.
And here it's exactly the opposite :)
If anyone has a Philips CDD-36xx drive and cdr
On Sat, Sep 30, 2000 at 01:06:13PM -0500, Thomas Molina wrote:
> My CD-RW is a Phillips CDD-3610. I'm not sure who the person wanting
> input from a Phillips user was so I hope that person is reading here. I
> got cdrecord working by NOT compiling in ATAPI CD ROM support, and by
> compiling ide-
On Sat, Oct 07, 2000 at 11:16:30AM -0700, Andre Hedrick wrote:
> On Sat, 7 Oct 2000, Jeff V. Merkey wrote:
>
> > append "hdd=ide-scsi"
>
> append "hdd=scsi" is better.
Care to explain why?
--
/| Ragnar Højland Freedom - Linux - OpenGL Fingerprint 94C4B
\ o.O|
After mounting; Doing 1 or 2 ls, works fine. However if you do a cat * >
/dev/null, it oopses.
I'm not sure if this is the real evil-doer since it spews a couple of oopses
out of scrollback reach, but the last point appears to be in d_lookup, in
the for.
0xc013bfc6 : movl 0x0(
Burnt a CD, compared the file with the original, and found out the
following. As you can see, the mismatch is the same depending on
the offset.
What's wrong? I'm using the ide-scsi patch Andre posted, btw.
07CEE45D: 63 73
0C96C5FF: 85 05
0D4B259A: B8 38
0FA3259A: DC 5C
1259745D: E1 F1
17CAA45D
On Tue, Jan 23, 2001 at 12:33:45AM -0500, Mike A. Harris wrote:
> On Mon, 15 Jan 2001, Trever Adams wrote:
>
> >I had a similar experience. All I can say is windows 98
> >and ME seem to have it out for Linux drives running late
> >2.3.x and 2.4.0 test and release. I had windows completely
> >fr
On Wed, Jul 04, 2001 at 11:16:43PM -0400, Bill Pringlemeir wrote:
> I also have had problems with a machine that had 128Mb + 64 Mb. I
> discovered the following about 2.4.x. You _should_ have a swap file
> that is double RAM. Mixing different SDRAM types is probably a bad
> thing. So if you up
32 matches
Mail list logo
