Re: cvsup on recent -CURRENT
Christian Weisgerber wrote: On this machine which runs -CURRENT from two days ago or so, I'm seeing frequent cvsup client failures of this type: TreeList failed: Network write failure: Connection closed I don't recall ever running into this before. Same here. Last night was okay. It started about 5 days ago. If you just start over it usually finishes okay. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Abit BP6 - UDMA66 and non IBM disks
Greg Lehey wrote: On Monday, 8 May 2000 at 9:57:54 +0200, [EMAIL PROTECTED] wrote: Not all non IBM disks has problems, that was not the message back then, at least not from me. What I said, and still says, is that Maxtor and WDC has a bad reputation on making drives that can't work reliably with UDMA66, quantum has its share too but not so bad. There are some WDC disks that work nicely. This is from a BP6 board too: ad0: 26105MB WDC WD273BA [53040/16/63] at ata0-master using UDMA33 ad1: 26105MB WDC WD273BA [53040/16/63] at ata1-master using UDMA33 ad2: 26105MB IBM-DPTA-372730 [53040/16/63] at ata2-master using UDMA66 ad3: 26105MB WDC WD273BA [53040/16/63] at ata3-master using UDMA66 As far as I know, the WD273BA is in reality a DPTA-372730 in disguise, so I guess I shouldn't be surprised. Anybody know if it's possible to put the original IBM firmware on these disks? I've been having trouble with this one in UDMA66 mode, also on a BP6. The system just hangs solid at random: ad4: 13042MB WDC WD136BA [26500/16/63] at ata2-master using UDMA66 It works fine on UDMA33. I notice that you have ad2 and ad3 running in UDMA66 mode. I didn't realise this was possible; I'll experiment. If you shut off the PIIX contoller in the BIOS the Highpoint uses ad0-3 if not it uses ad4-7 I have found problems with cdroms on the highpoint so I use both. Not the controllers fault but the applications. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Abit BP6 - UDMA66 and non IBM disks
Alan Cox wrote: About two days ago, I tested a machine with four IDE drives each on its own cable as the master. All four drives were: ad0: 29311MB Maxtor 53073U6 [59554/16/63] at ata0-master using UDMA66 I used the motherboard controller to support two of the drives. It was a atapci0: Intel ICH ATA66 controller port 0xffa0-0xffaf at device 31.1 on pci0 and a Highpoint-based ATA66 controller for the other two drives. The Highpoint locked up with the "resetting devices" message as soon as the system was stressed. I replaced the Highpoint controller with a Promise ATA66 and didn't see any problems after that. (I've never seen any problems with the Maxtor's on the Intel ATA66 controller either.) In summary, same disks, three different controllers, problems only occur with the Highpoint controller. (I believe the Abit BP6 uses the Highpoint controller.) I use the BP6 with FreeBSD-current and Slackware. The Highpoint works great with FreeBSD however I have a problem with the Maxtor running fsck under Linux. This has occurred since the beginning of support for the Highpoint. I have used Hedricks patches and nagged him about problems but the only remaining issue is fsck. It works perfectly with the PIIX controller. Benchmarks sizzle with the Maxtor/Highpoint almost 24MB/sec so the tradeoff is acceptable(to me). The best the IBM could muster was 20MB/sec. The Maxtor/PIIX runs a little over 19MB/sec occasionally hitting 20MB/sec. Regards, -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Abit BP6 - UDMA66 and non IBM disks
"Rodney W. Grimes" wrote: [Charset ISO-8859-1 unsupported, filtering to ASCII...] It seems Arun Sharma wrote: I have the following disk: ad4: 9787MB WDC AC310200R [19885/16/63] at ata2-master using UDMA33 and am experiencing hangs when I run it with UDMA66. That exact disk model cant do UDMA66 reliably, even Linux has it on the blacklist in the driver I read the threads from Feb, where it was said that non IBM disks had problems with the UDMA66 code in FreeBSD. Some of you said that the disks worked just fine with other OSes. Not all non IBM disks has problems, that was not the message back then, at least not from me. What I said, and still says, is that Maxtor and WDC has a bad reputation on making drives that can't work reliably with UDMA66, quantum has its share too but not so bad. IBM's on the other hand works as expected... Perhaps that is why Western Digital has gotten the nick name around here of ``We Don't Care''. :-) In all seriousness we stopped using WD drives in the retail store front computers over 2 years ago due to they problems we have had with them. Been using Fujitsu with very good luck, and IBM on the higher end and been very happy with them. We use to be big in Quantum scsi drives, but with IBM finally getting it's supplier side act togeather as far as channel avaliability of the SCSI products we've switched the AAI commercial server side over to them. I can't remeber when the last problem was, ohh.. yea... 1 doa unit out of 32 drives, probably caused during the assembly process of stuffing them in the kingston canisters (a not too gental operation). Infact now that I think about it that is the only problem we have had with IBM drives in over 500 units sold. Not bad, thats a .2% AQL, something I don't recall seeing in any disk drive product line we have used over the last 8 years !! We have had the same luck with IBM also. Maxtor(Diamond Max Plus) is also very close. Except for several 15GB models(we since have dropped that model) we have seen a 0 failure rate with them. I don't recall ever seeing quality, price and performance like we do now. The same goes for several brands of motherboards too. This has to be the PC's golden age. Look at memory prices and quality. 1GB of PC133 can be had for under $900 and again with the assurance that a failure would be pretty rare. Regards, -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't assign resources
Trent Nelson wrote: Ted Sikora wrote: I have been getting these messages from my kernel for some time now. Could the culprit be these 2 isa cards: non-pnp SB16 sbc0 ne2000 ed0 They are on a SMP BP6 I've posted a message both to current and questions about this now. I'm experiencing the same thing with roughly the same I/O addresses being claimed. I doubt it has anything to do with the ISA cards you mention as many of the addresses relate to things like the DMA registers/timer and other associated resources. Could someone please either take a look at this, or give an authoritative comment as to why it's happening. If someone points me in the direction of the particular code where the unknown driver is claiming the devices; I'll make an attempt to take a look at it myself. May 3 14:53:19 telecast /kernel: unknown0: PNP at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 May 3 14:53:19 telecast /kernel: unknown1: PNP0200 at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 Your right the addresses seem to be standard machine resources. Are you using SMP? The irq's are remapped on a SMP machine so maybe that's were the trouble lies? The PNP tag is what has me stumped. I replaced the isa cards with pci this evening out of curiosity...same thing. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't assign resources
Trent Nelson wrote: Ted Sikora wrote: Your right the addresses seem to be standard machine resources. Are you using SMP? The irq's are remapped on a SMP machine so maybe that's were the trouble lies? The PNP tag is what has me stumped. I replaced the isa cards with pci this evening out of curiosity...same thing. Nope, I'm using a UP kernel. Like you mention, I've also taken out my only PCI card (fxp) and disabled the sound interface via the BIOS and I get the same thing. I've toggled the `PnP OS' flag in my BIOS as well which doesn't do anything. From what you've said and what I've experienced; I'm even more convinced the problem's nothing to do with ISA/PCI devices. I'm going to have a look at the code a bit more later on tonight... Another interesting point is the dmesg I get now after I set "int bootverbose" to '1' in `/usr/src/sys/i386/i386/machdep.c'. I'd really love to hear from a coding-type figure that could determine the severity of a lot of the error messages reported. Ted, would it be possible to see a copy of your kernel? Also, what motherboard do you have? ABit BP6 2x400 Celerons @ 468Mhz or 6x78 The kernel bootup messages are attached. --Ted May 4 12:20:03 telecast /kernel: Copyright (c) 1992-2000 The FreeBSD Project. May 4 12:20:03 telecast /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 May 4 12:20:03 telecast /kernel: The Regents of the University of California. All rights reserved. May 4 12:20:03 telecast /kernel: FreeBSD 5.0-CURRENT #0: Thu May 4 09:54:48 EDT 2000 May 4 12:20:03 telecast /kernel: [EMAIL PROTECTED]:/usr/src/sys/compile/TELECAST May 4 12:20:03 telecast /kernel: Timecounter "i8254" frequency 1193182 Hz May 4 12:20:03 telecast /kernel: CPU: Pentium II/Pentium II Xeon/Celeron (467.98-MHz 686-class CPU) May 4 12:20:03 telecast /kernel: Origin = "GenuineIntel" Id = 0x665 Stepping = 5 May 4 12:20:03 telecast /kernel: Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR May 4 12:20:03 telecast /kernel: real memory = 67108864 (65536K bytes) May 4 12:20:03 telecast /kernel: avail memory = 61837312 (60388K bytes) May 4 12:20:03 telecast /kernel: Programming 24 pins in IOAPIC #0 May 4 12:20:03 telecast /kernel: IOAPIC #0 intpin 2 - irq 0 May 4 12:20:03 telecast /kernel: FreeBSD/SMP: Multiprocessor motherboard May 4 12:20:03 telecast /kernel: cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 May 4 12:20:03 telecast /kernel: cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 May 4 12:20:03 telecast /kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 May 4 12:20:03 telecast /kernel: Preloaded elf kernel "kernel" at 0xc0365000. May 4 12:20:03 telecast /kernel: Pentium Pro MTRR support enabled May 4 12:20:03 telecast /kernel: npx0: math processor on motherboard May 4 12:20:03 telecast /kernel: npx0: INT 16 interface May 4 12:20:03 telecast /kernel: pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard May 4 12:20:03 telecast /kernel: pci0: PCI bus on pcib0 May 4 12:20:03 telecast /kernel: pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 May 4 12:20:03 telecast /kernel: pci1: PCI bus on pcib1 May 4 12:20:03 telecast /kernel: pci1: NVidia Riva Ultra Vanta TNT2 graphics accelerator at 0.0 irq 16 May 4 12:20:03 telecast /kernel: isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 May 4 12:20:03 telecast /kernel: isa0: ISA bus on isab0 May 4 12:20:03 telecast /kernel: atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 May 4 12:20:03 telecast /kernel: ata1: at 0x170 irq 15 on atapci0 May 4 12:20:03 telecast /kernel: pci0: Intel 82371AB/EB (PIIX4) USB controller at 7.2 May 4 12:20:03 telecast /kernel: Timecounter "PIIX" frequency 3579545 Hz May 4 12:20:03 telecast /kernel: intpm0: Intel 82371AB Power management controller port 0x5000-0x500f irq 9 at device 7.3 on pci0 May 4 12:20:03 telecast /kernel: intpm0: I/O mapped 5000 May 4 12:20:03 telecast /kernel: intpm0: intr IRQ 9 enabled revision -1072311040 May 4 12:20:03 telecast /kernel: smbus0: System Management Bus on intsmb0 May 4 12:20:03 telecast /kernel: smb0: SMBus general purpose I/O on smbus0 May 4 12:20:03 telecast /kernel: intpm0: PM I/O mapped 4000 May 4 12:20:03 telecast /kernel: ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xc400-0xc41f irq 19 at device 9.0 on pci0 May 4 12:20:03 telecast /kernel: ed0: supplying EUI64: 00:60:67:ff:fe:22:c8:84 May 4 12:20:03 telecast /kernel: ed0: address 00:60:67:22:c8:84, type NE2000 (16 bit) May 4 12:20:03 telecast /kernel: pcm0: AudioPCI ES1370 port 0xc800-0xc83f irq 17 at device 13.0 on pci0 May 4 12:20:03 telecast /kernel: atapci1: HighPoint HPT366 ATA66 controller port 0xd400-0xd4ff,0xd000-0xd003,0xcc00-0xcc07 irq 18 at device 19.0 on pci0 May 4 12:
can't assign resources
I have been getting these messages from my kernel for some time now. Could the culprit be these 2 isa cards: non-pnp SB16 sbc0 ne2000 ed0 They are on a SMP BP6 May 3 14:53:19 telecast /kernel: unknown0: PNP at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 May 3 14:53:19 telecast /kernel: unknown1: PNP0200 at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 May 3 14:53:19 telecast /kernel: unknown2: PNP0100 at port 0x40-0x43 irq 0 on isa0 May 3 14:53:19 telecast /kernel: unknown3: PNP0b00 at port 0x70-0x71 irq 8 on isa0 May 3 14:53:19 telecast /kernel: unknown: PNP0303 can't assign resources May 3 14:53:19 telecast /kernel: unknown4: PNP0800 at port 0x61 on isa0 May 3 14:53:19 telecast /kernel: unknown5: PNP0c04 at port 0xf0-0xff irq 13 on isa0 May 3 14:53:19 telecast /kernel: unknown6: PNP0c01 at iomem 0-0x9,0xfffe-0x,0xfec0-0xfec0,0xfee0-0xfee0,0x10-0x3ff on isa0 May 3 14:53:19 telecast /kernel: unknown7: PNP0c02 at iomem 0xf-0xf3fff,0xf4000-0xf7fff,0xf8000-0xf,0xd1800-0xd3fff on isa0 May 3 14:53:19 telecast /kernel: unknown: PNP0a03 can't assign resources May 3 14:53:19 telecast /kernel: unknown: PNP0f13 can't assign resources May 3 14:53:19 telecast /kernel: unknown: PNP0501 can't assign resources May 3 14:53:19 telecast /kernel: unknown: PNP0700 can't assign resources May 3 14:53:19 telecast /kernel: unknown: PNP0400 can't assign resources -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: high CPU usage by xmms
VINSON WAYNE HOWARD wrote: Ok, I checked, and vmstat shows cpu usage to be quite normal, about 6% while playing. What's up w/ top? Xmms on my SMP current machine: top shows 40 to 43% system vmstat shows 10 to 11% -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: high CPU usage by xmms
Ted Sikora wrote: VINSON WAYNE HOWARD wrote: Ok, I checked, and vmstat shows cpu usage to be quite normal, about 6% while playing. What's up w/ top? Xmms on my SMP current machine: top shows 40 to 43% system vmstat shows 10 to 11% vmstat -w 1 matches top exactly about 41-43% system on my box. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: high CPU usage by xmms
Kenneth Wayne Culver wrote: I guess it depends on your soundcard, I'm getting the behavior I'm getting with a ViBRA 16X and a kernel as of this morning. This didn't start happening until about 4 days ago with a -CURRENT kernel. Maybe you have an older -CURRENT. I did a make build/installworld and kernel this afternoon after I cvsup'd(current). I have an original non-pnp SB16. (Best sounding sound card on the market IMOP) Aureal and any ESS equiped cards are excellent too. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: high CPU usage by xmms
Kenneth Wayne Culver wrote: Hmm, I don't know then, I'm using that ViBRA 16X which seems to cause problems a lot. On Sun, 30 Apr 2000, Ted Sikora wrote: Kenneth Wayne Culver wrote: I guess it depends on your soundcard, I'm getting the behavior I'm getting with a ViBRA 16X and a kernel as of this morning. This didn't start happening until about 4 days ago with a -CURRENT kernel. Maybe you have an older -CURRENT. I did a make build/installworld and kernel this afternoon after I cvsup'd(current). I have an original non-pnp SB16. (Best sounding sound card on the market IMOP) The VibraX used to be the card everyone recommended to stay away from. It's not full-duplex. Early on it was hard writing for it (mostly due to lack of specs and noise problems). It seems most problems have been solved now. Like someone mentioned already I think it's a 4.0 problem. Xmms worked perfectly under 3.4 for me too. The eq problem appeared after the upgrades. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current errors
Any ideas as to the cause of the following errors in current. I have (2)isa non-pnp cards.. SB16(pcm) and a ne2000(ed0). The only other card is an AGP TNT2 video card. Apr 17 23:07:42 telecast /kernel: unknown0: PNP at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 Apr 17 23:07:42 telecast /kernel: unknown1: PNP0200 at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 Apr 17 23:07:42 telecast /kernel: unknown2: PNP0100 at port 0x40-0x43 irq 0 on isa0 Apr 17 23:07:42 telecast /kernel: unknown3: PNP0b00 at port 0x70-0x71 irq 8 on isa0 Apr 17 23:07:42 telecast /kernel: unknown: PNP0303 can't assign resources Apr 17 23:07:42 telecast /kernel: unknown4: PNP0800 at port 0x61 on isa0 Apr 17 23:07:42 telecast /kernel: unknown5: PNP0c04 at port 0xf0-0xff irq 13 on isa0 Apr 17 23:07:42 telecast /kernel: unknown6: PNP0c01 at iomem 0-0x9,0xfffe-0x,0xfec0-0xfec0,0xfee0-0xfee0,0x10-0x7ff on isa0 Apr 17 23:07:42 telecast /kernel: unknown7: PNP0c02 at iomem 0xf-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfbfff,0xfc000-0xf on isa0 Apr 17 23:07:42 telecast /kernel: unknown: PNP0a03 can't assign resources Apr 17 23:07:42 telecast /kernel: unknown: PNP0f13 can't assign resources Apr 17 23:07:42 telecast /kernel: unknown: PNP0501 can't assign resources Apr 17 23:07:42 telecast /kernel: unknown: PNP0700 can't assign resources Apr 17 23:07:42 telecast /kernel: unknown: PNP0400 can't assign resources Apr 17 23:07:42 telecast /kernel: APIC_IO: Testing 8254 interrupt delivery Apr 17 23:07:42 telecast /kernel: APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Apr 17 23:07:42 telecast /kernel: SMP: AP CPU #1 Launched! Regards, -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
MAKEDEV warning
After building a new kernel yesterday after a cvsup the following appeared. Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices I did a MAKEDEV all and the message still persists. Regards, -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV warning
"Chris D. Faulhaber" wrote: On Tue, 18 Apr 2000, Ted Sikora wrote: After building a new kernel yesterday after a cvsup the following appeared. Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices I did a MAKEDEV all and the message still persists. ls -l /dev | grep ^b and remake/remove those devices as appropriate Thanks that did it. What is the reason behind it? Their are other unused devices in /dev. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall broken :(
John Baldwin wrote: Hmph, it seems sysinstall (and thus make release) is broken in -current: cc -O -pipe -Wall -I/usr/src/release/sysinstall/../../gnu/lib/libdialog -I/usr/obj/usr/src/release/sysinstall -I/usr/src/release/sysinstall/../../sys -c bail: Comments? It's broken for me too! I just did a 4.0-RELEASE install last night and cvs'upd this morning to -current. I get the kget message also: src/release/sysinstall -I/usr/src/release/sysinstall/../../sys -c kget.c kget.c: In function `kget': kget.c:83: sizeof applied to an incomplete type kget.c:85: dereferencing pointer to incomplete type kget.c:86: dereferencing pointer to incomplete type kget.c:89: dereferencing pointer to incomplete type -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] http://powerusersbbs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RealPlayer 7
Donn Miller wrote: Anyone get this beast to work on -current? The audio works, but the video doesn't work at all. I have COMPAT_LINUX in my kernel, and RealPlayer 5.0 works pretty well. $ printenv LD_LIBRARY_PATH /usr/local/qt/lib:/usr/local/lib/rvplayer5.0:/usr/local/RealPlayer7/Common:/usr/local/RealPlayer7/Codecs:/usr/local/RealPlayer7/Plugins:/usr/local/RealPlayer7 I have it under 5.0-current with XFree86-4.0. Like the other guy said just do the standard install and it works. I have /usr/compat/linux/usr/local/RealPlayer7 in my path and export REALPLAYER7=/usr/compat/linux/usr/local/RealPlayer7 in /etc/profile. For the mimeinstall and plugins go to the RealPlayer /dir and run #./mimeinstall.sh #./pluginstall.sh -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] http://powerusersbbs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RealPlayer 7
Ted Sikora wrote: Donn Miller wrote: Anyone get this beast to work on -current? The audio works, but the video doesn't work at all. I have COMPAT_LINUX in my kernel, and RealPlayer 5.0 works pretty well. $ printenv LD_LIBRARY_PATH /usr/local/qt/lib:/usr/local/lib/rvplayer5.0:/usr/local/RealPlayer7/Common:/usr/local/RealPlayer7/Codecs:/usr/local/RealPlayer7/Plugins:/usr/local/RealPlayer7 I have it under 5.0-current with XFree86-4.0. Like the other guy said just do the standard install and it works. I have /usr/compat/linux/usr/local/RealPlayer7 in my path and export REALPLAYER7=/usr/compat/linux/usr/local/RealPlayer7 in /etc/profile. For the mimeinstall and plugins go to the RealPlayer /dir and run #./mimeinstall.sh #./pluginstall.sh Correction: /usr/compat/linux/usr/local/bin is in my path. Just ln -s realplay and rpnphelper to it. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RealPlayer 7
"Jacques A . Vidrine" wrote: On Fri, Mar 17, 2000 at 12:42:33AM -0500, Donn Miller wrote: I think I found the problem -- it had "disable custom sampling rates" checked in the preferences section. I unchecked that, and at least the audio is working better. I still have to try the video, though... Maybe there's a conflict with running it with XFree86 4.0 and 16 bpp. No, I have 4.0-STABLE and XFree86 4.0 here, running at 16bpp, and can play video streams fine with RealPlayer. Although not as a Netscape plugin -- it dumps core I haven't had a chance to see why yet. -- Most of the plugins give the 'bad magic' error. It works perfectly under the Linux-Netscape version however. That's why I run both in FreeBSD. With the Linux version I get all plugins like flash4 and so on. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] http://powerusersbbs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RealPlayer 7
Kris Kennaway wrote: On Fri, 17 Mar 2000, Ted Sikora wrote: Most of the plugins give the 'bad magic' error. It works perfectly under the Linux-Netscape version however. That's why I run both in FreeBSD. With the Linux version I get all plugins like flash4 and so on. You can't use a foreign plugin with a native freebsd netscape..unfortunately there aren't many plugins available in native format - this is a good reason to use the linux version. There are a couple of exceptions to that. The Linux plugger works under FreeBSD provided you have the .conf file in the FreeBSD Netscape directory. Also the new acroread plugin works with FreeBSD. The new (SuSE) version not the one in ports/packages. It's compiled to work with glibc. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] http://powerusersbbs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD branches?
Does anyone know what they are now or will be? I want to follow 4.0-stable if there will be one. Right now I have been cvsup'ing from 4.0-RC to 5.0-current. I am assuming there will be: 3-stable 4-stable 5-current Yes, no, maybe? Will 4.0-RELEASE turn into the 4-stable branch? -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree86-4.0 error
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 Any ideas on a fix. Xfree86-4.0 is solid otherwise. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] http://powerusersbbs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4.0 error
Andrey Sverdlichenko wrote: On Tue, 14 Mar 2000, Ted Sikora wrote: XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24 options SHMALL=1025 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=1025 options SHMMIN=2 options SHMMNI=256 options SHMSEG=128 config, make, install. Thanks. Just added it and it's fixed...after removing wdc.h from ../../sys/i386/isa/isa_compat.h -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] http://powerusersbbs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree86-4 mouse?
My problem is a little different. XFree86-4.0 loads fine looks great but the mouse does not work. There are no errors. I tried PS/2 , serial, etc same with them all. The pointer appears then moves to the upper right and dissappers. I tried moving it...Mouse1, etc. but nothing Any ideas? Note:XF86Config works well but XFree86 -configure gives a bad config Regards, -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] http://powerusersbbs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 mouse?
Ted Sikora wrote: My problem is a little different. XFree86-4.0 loads fine looks great but the mouse does not work. There are no errors. I tried PS/2 , serial, etc same with them all. The pointer appears then moves to the upper right and dissappers. I tried moving it...Mouse1, etc. but nothing Any ideas? Note:XF86Config works well but XFree86 -configure gives a bad config Got it working. The new config takes a bit getting used to. The default xf86config generated script puts all devices at 1 as in "Mouse 1". When I changed the mouse to "0 "and set it at auto it worked. All others I left at "1". XFree86 -configure sets all at "0" but leaves a bit of info out rendering it useless without editing. It leaves the screen modes out. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] http://powerusersbbs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
