You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(210) |
Jun
(169) |
Jul
(167) |
Aug
(128) |
Sep
(218) |
Oct
(120) |
Nov
(86) |
Dec
(71) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(91) |
Feb
(179) |
Mar
(52) |
Apr
(56) |
May
(183) |
Jun
(62) |
Jul
(63) |
Aug
(49) |
Sep
(36) |
Oct
(35) |
Nov
(72) |
Dec
(30) |
2002 |
Jan
(53) |
Feb
(61) |
Mar
(56) |
Apr
(13) |
May
(1) |
Jun
(7) |
Jul
(80) |
Aug
(73) |
Sep
(30) |
Oct
(29) |
Nov
(8) |
Dec
(40) |
2003 |
Jan
(10) |
Feb
(2) |
Mar
(4) |
Apr
(9) |
May
(3) |
Jun
(19) |
Jul
(64) |
Aug
(53) |
Sep
(28) |
Oct
(7) |
Nov
(3) |
Dec
(21) |
2004 |
Jan
(11) |
Feb
(30) |
Mar
(18) |
Apr
(1) |
May
(13) |
Jun
(18) |
Jul
(13) |
Aug
|
Sep
(9) |
Oct
(5) |
Nov
|
Dec
|
2005 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(10) |
Aug
(21) |
Sep
(7) |
Oct
(10) |
Nov
(6) |
Dec
|
2006 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
(6) |
Oct
(10) |
Nov
(8) |
Dec
(3) |
2007 |
Jan
(3) |
Feb
(6) |
Mar
(1) |
Apr
(6) |
May
(10) |
Jun
(7) |
Jul
(13) |
Aug
(8) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
From: Glenn H. <gh...@c2...> - 2001-02-09 17:58:12
|
On 09-Feb-01, Michel Dänzer wrote: > CVSROOT: /cvsroot/linux-apus > Module name: 2.3 > Repository: 2.3/arch/ppc/kernel/ > Changes by: mdaenzer@usw-pr-cvs1. 01/02/09 06:53:25 > Modified files: > 2.3/arch/ppc/kernel/: apus_pci.c > Log message: > some additions inspired by chrp_pci.c (thanks Geert :) - someone please > test and post dmesg output dmesg output (only the lines that mentioned pci) : apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 PCI: Probing PCI hardware apus_pcibios_fixup_bus: PCI mem resource requested apus_pci.c line 179 iirc : <<<<<<< apus_pci.c ======= What the hell is this? CVS messed up ? PCI still doesn't work btw... - glenn |
From: Alan B. <al...@ms...> - 2001-02-09 17:38:13
|
hi, > inclluding 2.2 and 2.3 (within APUS). Is this 2.3 the latest kernel > (2.4)? When I tried to connect to XFree CVS anonymously the CVS server > rejected connection. How can I get the latest XFree86 then? And what cvs -d:pserver:an...@an...:/cvs password (yes! a password! ) is 'anoncvs' its all on the CVS pages, readbale at www.xfree86.org beware, the main tree is 210Mb and the 4.0.2 branch is 223Mb > being)! How will one get an summaray about all CVS modules available > usable with APUS? 8-) serious? ;-) alan |
From: Michel D?n. <mda...@us...> - 2001-02-09 14:52:59
|
CVSROOT: /cvsroot/linux-apus Module name: 2.3 Repository: 2.3/arch/ppc/kernel/ Changes by: mdaenzer@usw-pr-cvs1. 01/02/09 06:53:25 Modified files: 2.3/arch/ppc/kernel/: apus_pci.c Log message: some additions inspired by chrp_pci.c (thanks Geert :) - someone please test and post dmesg output |
From: T. <Ren...@gm...> - 2001-02-09 13:32:40
|
Hi Michel! Again thanx for your quick answering! Michel Dänzer schrieb: > René Thol wrote: > > > I tried to compile the sources from sourceforge/apus cvs 2.3 dir with > > different options set, but it won't work at all! I got the latest error > > output and will attach it. Unfortunately I forgot my config file, if I > > should post it too, please say so. I (in my opinion) disabled all > > uneccessary options. The errors are from the scsi-part I presume. I > > enabled GVP, Fastlane and CyberstormMKIII option. > > BTW a good way to get a working 2.4 config from a 2.2 one is to copy the > .config file and then do 'make oldconfig'. That will keep your config as much > as possible and only ask you about new or changed options. > I'll try. > > > When I tried to connect to XFree CVS anonymously the CVS server > > rejected connection. How can I get the latest XFree86 then? > > See http://www.xfree86.org/cvs/ on how to do it. > > ... > > fs/fs.o: In function `read_inode_bitmap': > > fs/fs.o(.text+0x268f8): undefined reference to `ext2_get_group_desc' > > fs/fs.o(.text+0x268f8): relocation truncated to fit: R_PPC_REL24 ext2_get_group_desc > > My first thought here was that you may have missed ext2 support, but some of > the ext2 functions are there so I don't know... Have you done make dep before > make vmlinux? > ext2 is enabled; I made make dep clean > > > drivers/char/char.o: In function `chr_dev_init': > > drivers/char/char.o(.text.init+0x25c): undefined reference to `lp_m68k_init' > > drivers/char/char.o(.text.init+0x25c): relocation truncated to fit: R_PPC_REL24 lp_m68k_init > > You probably have configured a parallel driver as a module but it should be in > the kernel or vice versa. I disabled loadable module support and configured everything of parallel port and printer to be compiled into the kernel! (I'll check this again). Kind regards -- ======================== René Thol ------------------------------------ Multimedia Computing University of Ulm ======================== E-Mail: Ren...@gm... ======================== |
From: Michel <mic...@ii...> - 2001-02-09 13:20:37
|
Ren=E9 Thol wrote: > I tried to compile the sources from sourceforge/apus cvs 2.3 dir with > different options set, but it won't work at all! I got the latest error > output and will attach it. Unfortunately I forgot my config file, if I > should post it too, please say so. I (in my opinion) disabled all > uneccessary options. The errors are from the scsi-part I presume. I > enabled GVP, Fastlane and CyberstormMKIII option. BTW a good way to get a working 2.4 config from a 2.2 one is to copy the .config file and then do 'make oldconfig'. That will keep your config as = much as possible and only ask you about new or changed options. > When I tried to connect to XFree CVS anonymously the CVS server > rejected connection. How can I get the latest XFree86 then? See http://www.xfree86.org/cvs/ on how to do it. > And what else CVS repositories are at sourceforge containing which modu= les > and can I use/compile them using APUS? SourceForge hosts thousands of projects. You don't expect anyone to know = them all, do you? :) As for if you can compile them, most stuff for 'Linux' should build on AP= US. In particular, all architectures of Linux/PPC are even binary compatible. Unfortunately though, a lot of people think 'Linux =3D=3D i386' and that'= s how they write code. Which then often doesn't work or even build on other architectures. > There are no informations given at sourceforge page (at least not for a > normal browsing/searching human being)! How will one get an summaray ab= out > all CVS modules available usable with APUS? There is no easy way. Search SourceForge for interesting projects and fin= d out if they are already packaged (most likely in Debian ;) and if not, you'll probably have to find out yourself if they build and work. > fs/fs.o: In function `read_inode_bitmap': > fs/fs.o(.text+0x268f8): undefined reference to `ext2_get_group_desc' > fs/fs.o(.text+0x268f8): relocation truncated to fit: R_PPC_REL24 ext2_g= et_group_desc My first thought here was that you may have missed ext2 support, but some= of the ext2 functions are there so I don't know... Have you done make dep be= fore make vmlinux? > drivers/char/char.o: In function `chr_dev_init': > drivers/char/char.o(.text.init+0x25c): undefined reference to `lp_m68k_= init' > drivers/char/char.o(.text.init+0x25c): relocation truncated to fit: R_P= PC_REL24 lp_m68k_init You probably have configured a parallel driver as a module but it should = be in the kernel or vice versa. > drivers/scsi/scsidrv.o: In function `ncr53c8xx_detect': > drivers/scsi/scsidrv.o(.text.init+0x281c): undefined reference to > `zorro_find' This is strange again, Zorro support is explicitly enabled for APUS... --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
From: T. <Ren...@gm...> - 2001-02-09 13:01:18
|
Roman Zippel schrieb: > Hi, > > On Fri, 9 Feb 2001, René Thol wrote: > > > I tried to compile the sources from sourceforge/apus cvs 2.3 dir with > > different options set, but it won't work at all! I got the latest error > > output and will attach it. Unfortunately I forgot my config file, if I > > should post it too, please say so. I (in my opinion) disabled all > > uneccessary options. The errors are from the scsi-part I presume. I > > enabled GVP, Fastlane and CyberstormMKIII option. > > Could you send me your .config file? > Unfortunately I forgot it today. I'll send it to you at monday, at the latest! (If I won't forget it again)! Bye -- ======================== René Thol ------------------------------------ Multimedia Computing University of Ulm ======================== E-Mail: Ren...@gm... ======================== |
From: Roman Z. <zi...@fh...> - 2001-02-09 12:41:07
|
Hi, On Fri, 9 Feb 2001, Ren=E9 Thol wrote: > I tried to compile the sources from sourceforge/apus cvs 2.3 dir with > different options set, but it won't work at all! I got the latest error > output and will attach it. Unfortunately I forgot my config file, if I > should post it too, please say so. I (in my opinion) disabled all > uneccessary options. The errors are from the scsi-part I presume. I > enabled GVP, Fastlane and CyberstormMKIII option. Could you send me your .config file? > By the way: Where can I get all module names stored in sourceforge CVSs? What you see in cvsweb is all that is there. :) Aliases are stored CVSROOT/modules. > If I browse the tree using a Webbrowser there are only a few dirs shown, > inclluding 2.2 and 2.3 (within APUS). Is this 2.3 the latest kernel > (2.4)? Yes. bye, Roman |
From: T. <Ren...@gm...> - 2001-02-09 11:04:39
|
Hello everybody! I tried to compile the sources from sourceforge/apus cvs 2.3 dir with different options set, but it won't work at all! I got the latest error output and will attach it. Unfortunately I forgot my config file, if I should post it too, please say so. I (in my opinion) disabled all uneccessary options. The errors are from the scsi-part I presume. I enabled GVP, Fastlane and CyberstormMKIII option. By the way: Where can I get all module names stored in sourceforge CVSs? If I browse the tree using a Webbrowser there are only a few dirs shown, inclluding 2.2 and 2.3 (within APUS). Is this 2.3 the latest kernel (2.4)? When I tried to connect to XFree CVS anonymously the CVS server rejected connection. How can I get the latest XFree86 then? And what else CVS repositories are at sourceforge containing which modules and can I use/compile them using APUS? There are no informations given at sourceforge page (at least not for a normal browsing/searching human being)! How will one get an summaray about all CVS modules available usable with APUS? Many thanx in advance! Kind regards -- ======================== René Thol ------------------------------------ Multimedia Computing University of Ulm ======================== E-Mail: Ren...@gm... ======================== |
From: Geert U. <ge...@li...> - 2001-02-09 11:01:37
|
On Fri, 9 Feb 2001, Sven LUTHER wrote: > On Fri, Feb 09, 2001 at 09:53:59AM +0100, Glenn Hisdal wrote: > > Sven LUTHER wrote: > > > > > > On Wed, Feb 07, 2001 at 06:57:51PM +0100, Glenn Hisdal wrote: > > > > Hi, > > > > > > > > I have just tried a 2.4.1 kernel with PCI support enabled. > > > > > > apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. > > > > > > > > APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 > > > > > > > > PCI: Probing PCI hardware > > > > > > Erm, ... > > > > > > what is the content of /proc/pci, i think it is empty. > > > > /proc/pci doesn't exist at all. > > Ok ... > > > > Notice that pci code seems to be broken on 2.4 kernels right now (well for > > > apus-pci anyway, not the generic pci code naturally). > > > > > Help is wanted to fix this, you volunteer ? > > > > I'm not sure how much I can help with the coding. > > If someone can point me in the right direction, and give me some info on > > the implementation of the pci code, I could have a look, but I doubt > > I'll be able to fix anything. Think it may be a bit lowlevel for me... > > Did we not all begin like that, ... > > Just have a look, and read the docs. > > Not sure even if it all that low level, Michel, any hint on that ? As an example, you can take a look at all `gg2' stuff in arch/ppc/kernel/chrp_pci.c. It's known to work fine on my PPC box. Basically you need to know - how to access PCI config space (old code knew) - wehere PCI memory and I/O space are located, to set up the bus resources. And enable all DEBUG code in drivers/pci/*.c and arch/ppc/kernel/pci.c. Good luck! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
From: Michel <mic...@ii...> - 2001-02-09 10:10:40
|
Sven LUTHER wrote: > We should maybe fix PCI in the 2.4 kernel any idea ofwhat the problem i= s ? The PPC PCI code has changed heavily and we are probably missing some kin= d of initialization. Like setting up bus resources, etc. --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
From: Sven L. <lu...@dp...> - 2001-02-09 08:55:14
|
On Fri, Feb 09, 2001 at 09:53:59AM +0100, Glenn Hisdal wrote: > Sven LUTHER wrote: > > > > On Wed, Feb 07, 2001 at 06:57:51PM +0100, Glenn Hisdal wrote: > > > Hi, > > > > > > I have just tried a 2.4.1 kernel with PCI support enabled. > > > > apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. > > > > > > APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 > > > > > > PCI: Probing PCI hardware > > > > Erm, ... > > > > what is the content of /proc/pci, i think it is empty. > > /proc/pci doesn't exist at all. Ok ... > > Notice that pci code seems to be broken on 2.4 kernels right now (well for > > apus-pci anyway, not the generic pci code naturally). > > > Help is wanted to fix this, you volunteer ? > > I'm not sure how much I can help with the coding. > If someone can point me in the right direction, and give me some info on > the implementation of the pci code, I could have a look, but I doubt > I'll be able to fix anything. Think it may be a bit lowlevel for me... Did we not all begin like that, ... Just have a look, and read the docs. Not sure even if it all that low level, Michel, any hint on that ? Sven Luther |
From: Glenn H. <gh...@c2...> - 2001-02-09 08:53:44
|
Sven LUTHER wrote: > > On Wed, Feb 07, 2001 at 06:57:51PM +0100, Glenn Hisdal wrote: > > Hi, > > > > I have just tried a 2.4.1 kernel with PCI support enabled. > > apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. > > > > APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 > > > > PCI: Probing PCI hardware > > Erm, ... > > what is the content of /proc/pci, i think it is empty. /proc/pci doesn't exist at all. > > Notice that pci code seems to be broken on 2.4 kernels right now (well for > apus-pci anyway, not the generic pci code naturally). > Help is wanted to fix this, you volunteer ? I'm not sure how much I can help with the coding. If someone can point me in the right direction, and give me some info on the implementation of the pci code, I could have a look, but I doubt I'll be able to fix anything. Think it may be a bit lowlevel for me... But If someone writes any patches, I'll be happy to test it ! - glenn |
From: Sven L. <lu...@dp...> - 2001-02-09 08:38:35
|
On Wed, Feb 07, 2001 at 06:57:51PM +0100, Glenn Hisdal wrote: > Hi, > > I have just tried a 2.4.1 kernel with PCI support enabled. > > When I run dmesg, it has only three lines that mentions PCI, so it doesn't > look like the PCI code does much. I was expecting a lot more when debug was > enabled: > > apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. > > APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 > > PCI: Probing PCI hardware Erm, ... what is the content of /proc/pci, i think it is empty. Notice that pci code seems to be broken on 2.4 kernels right now (well for apus-pci anyway, not the generic pci code naturally). Help is wanted to fix this, you volunteer ? Friendly, Sven Luther |
From: Sven L. <lu...@dp...> - 2001-02-09 08:36:14
|
On Wed, Feb 07, 2001 at 02:55:17PM +0100, Robert Ramiega wrote: > On Wed, Feb 07, 2001 at 02:50:21PM +0100, Frank Rudolf Georg Petzold wrote: > > On Wed, Feb 07, 2001 at 01:02:42PM +0000, Alan Buxey wrote: > > > > - problems with BVision > > > > > > what type of problem? we need details. > > > > Not from me. I have a CV64/3D. I was just summarizing averything I know of. > BVision doesn't cause problems.. it's PCI and XF4 that causes them =o))) Erm, ... We should maybe fix PCI in the 2.4 kernel any idea ofwhat the problem is ? (well i guess there were lot's of changes in the 2.4 pci code with regard to the 2.2 one, or the time Michel wrote the PCI support). There will nextly be a 4.0.2 bugfix succesor, which should fix the bugs in XF 4.0.2, and should be packaged almost immediately by branden i think, which should fix the use of non-PCI (or broken PCI) 2.4 kernels. But best would be if someone could test current cvs XF4 on a broken PCI kernel, or maybe even better the XF4 from the 4.0.2 branch. Maybe i should setup a cross compiler on my box here at work and compile one for people to test. Any experience with cross compiling X ? Friendly, Sven Luther |
From: Frank R. G. P. <pe...@he...> - 2001-02-08 07:59:52
|
On Wed, Feb 07, 2001 at 05:54:06PM +0100, Michel D?nzer wrote: > Frank Rudolf Georg Petzold wrote: > > > > We fixed such a problem in late 2.1 or early 2.2, maybe the fix got lost > > > in our 2.4? > > > > Like the fix for the parallel driver? > > No, the one about ppp panicking the kernel on 'heavy' traffic (did I misquote? > Sorry if yes). I was meaning: The fix got lost like the fix for parallel? -- Dipl. Informatikingenieur ETH Frank Petzold <pe...@he...> ceterum censeo parvomollem esse delendam. |
From: Glenn H. <gh...@c2...> - 2001-02-08 06:49:12
|
Roman Zippel wrote: > > Hi, > > On Wed, 7 Feb 2001, Glenn Hisdal wrote: > > > apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. > > > > APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 > > > > PCI: Probing PCI hardware > > The prints in the pci code have debug level, add 'debug' to bootstrap at I did that... > startup or use 'loglevel 8' or 'dmesg -n8'. I'll try this when I get back home today - glenn |
From: Roman Z. <zi...@fh...> - 2001-02-07 23:21:05
|
Hi, On Wed, 7 Feb 2001, Glenn Hisdal wrote: > apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. > > APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 > > PCI: Probing PCI hardware The prints in the pci code have debug level, add 'debug' to bootstrap at startup or use 'loglevel 8' or 'dmesg -n8'. bye, Roman |
From: Glenn H. <gh...@c2...> - 2001-02-07 18:00:29
|
Hi, I have just tried a 2.4.1 kernel with PCI support enabled. When I run dmesg, it has only three lines that mentions PCI, so it doesn't look like the PCI code does much. I was expecting a lot more when debug was enabled: apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 PCI: Probing PCI hardware - glenn |
From: Michel <mic...@ii...> - 2001-02-07 16:55:08
|
Frank Rudolf Georg Petzold wrote: > > We fixed such a problem in late 2.1 or early 2.2, maybe the fix got l= ost > > in our 2.4? >=20 > Like the fix for the parallel driver? No, the one about ppp panicking the kernel on 'heavy' traffic (did I misq= uote? Sorry if yes). --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
From: Frank R. G. P. <pe...@he...> - 2001-02-07 15:49:03
|
On Wed, Feb 07, 2001 at 04:25:46PM +0100, Michel D?nzer wrote: > We fixed such a problem in late 2.1 or early 2.2, maybe the fix got lost in > our 2.4? Like the fix for the parallel driver? AFAIK, the fix was done in the generic code, not in the amiga specific parport_amiga. But as I have no revision history of that time, I can't have a look. -- Dipl. Informatikingenieur ETH Frank Petzold <pe...@he...> ceterum censeo parvomollem esse delendam. |
From: Michel <mic...@ii...> - 2001-02-07 15:39:05
|
Frank Rudolf Georg Petzold wrote: > > I perfectly understand users who stick to 2.2 for now when they have = found > > out that 2.4 doesn't meet their needs yet. >=20 > Only that there is the shared memory problem that prevents burning CDs = in > 2.2. Yes, that's just one of the reasons why all users really want 2.4 . Most = of them just don't know yet. ;) > - Internal parallel does not work (garbage arrives at printer) Robert says it kind of works, can you two work that out please? > > That's why I think putting stuff like this in 2.2 is a bad idea. >=20 > Backports are OK, perhaps even mandatory though. Maybe, but this topic didn't start from a backport but from new developme= nt done in the 2.2 tree. Bug fixes are important, backports should be option= al and low priority. After all, each backport keeps more users from upgradin= g. PS: Can you please submit bugs for the problems you experience? Thanks. --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
From: Roman Z. <zi...@fh...> - 2001-02-07 15:30:09
|
Hi, On Wed, 7 Feb 2001, Frank Rudolf Georg Petzold wrote: > - Internal parallel does not work (garbage arrives at printer) > - MFCIII driver does not compile For these problems you might want to ask on the linux-m68k list or Joerg Dorchain (jo...@do...) directly, as he is still the maintainer of these drivers. bye, Roman |
From: Michel <mic...@ii...> - 2001-02-07 15:26:47
|
Alan Buxey wrote: > > - kernel crashes (reboot) when using ppp for more than 10 Minutes and > > heavy transfer over serial. >=20 > ouch. theres certainly no problem of this sort under 2.2 -> Having > downloaded 125Mb over the past 3 days without a single reboot I know th= is. We fixed such a problem in late 2.1 or early 2.2, maybe the fix got lost = in our 2.4? --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
From: Robert R. <ro...@pl...> - 2001-02-07 13:55:34
|
On Wed, Feb 07, 2001 at 02:50:21PM +0100, Frank Rudolf Georg Petzold wrote: > On Wed, Feb 07, 2001 at 01:02:42PM +0000, Alan Buxey wrote: > > > - problems with BVision > > > > what type of problem? we need details. > > Not from me. I have a CV64/3D. I was just summarizing averything I know of. BVision doesn't cause problems.. it's PCI and XF4 that causes them =o))) -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
From: Frank R. G. P. <pe...@he...> - 2001-02-07 13:50:02
|
On Wed, Feb 07, 2001 at 01:02:42PM +0000, Alan Buxey wrote: > > - problems with BVision > > what type of problem? we need details. Not from me. I have a CV64/3D. I was just summarizing averything I know of. -- Dipl. Informatikingenieur ETH Frank Petzold <pe...@he...> ceterum censeo parvomollem esse delendam. |