Re: Linux X Server
"Bill A. K." wrote: > Has anyone ever run a Linux X Server under FreeBSD/Linux Emulation? I'm > trying to run the Voodoo Banshee server from Creative Labs. The reason I'm > trying to do this is because when I run XFree86 3.3.5, it screws up my > console display when I exit X. The Linux Server is looking to open /dev/tty9 > and it can't. I tried putting a hard link from /dev/tty9 to /dev/ttyv9 but > when i started X it paniced the kernel :) > > Is there any way first of all to fix 3.3.5 to work, and if not, to get the > Linux server to work? Is there any way to somehow mimic /dev/tty9 for it? The Banshee only seems to have this problem when switching from a graphical mode to the _standard_ text mode (80x25). Adding the following line to /etc/rc.conf allscreens_flags="80x30" fixed it for me. Frank To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ata-related crash following notebook resume
$apm -Z // going to sleep //... 10 hours later ... // key pressed ata0: resetting devices .. done ata1: resetting devices .. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01e6e42 stack pointer = 0x10:0xc0243028 frame pointer = 0x10:0xc0243028 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = trap number = 12 panic: page fault syncing disks ... 1 1 1 1 1 1 1 1 1 1 1 1 1 done $ nm /kernel | grep c01e6e c01e6e3c T atapi_reinit $ dmesg ... ata-pci0: at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ad0: ATA-4 disk at ata0 as master ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 acd0: CDROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, DMA acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked ata_command: timeout waiting for interrupt (-current kernel dated Fri Sep 24 19:30:18 GMT) Thank you for your attention. Frank To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wd0: interrupt timeout (status 58 error 1)
Soren Schmidt wrote:
>
> Hmm try the patch below so we can tell what command it is failing on..
>
> Index: ata-all.c
> --- ata-all.c 1999/08/06 17:39:37 1.16
> +++ ata-all.c 1999/08/11 07:00:09
> @@ -693,7 +693,8 @@
> scp->active = ATA_WAIT_INTR;
> outb(scp->ioaddr + ATA_CMD, command);
> if (tsleep((caddr_t)scp, PRIBIO, "atacmd", 500)) {
> - printf("ata_command: timeout waiting for interrupt\n");
> + printf("ata_command: timeout waiting for interrupt (cmd=0x%02x)\n,
> + command");
> scp->active = ATA_IDLE;
> return -1;
> }
After removing the quotation mark after the word command in the above
patch (smile), it prints:
ata_command: timeout waiting for interrupt (cmd=0xa1)
What is command 0xa1?
Frank
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: wd0: interrupt timeout (status 58 error 1)
Soren Schmidt wrote: > > It seems Francis Jordan wrote: > > /kernel: acd0: CDROM drive at ata1 as master > > /kernel: acd0: drive speed 4134KB/sec, 128KB cache > > /kernel: acd0: supported read types: CD-R, CD-RW, CD-DA > > /kernel: acd0: Audio: play, 256 volume levels > > /kernel: acd0: Mechanism: ejectable tray > > /kernel: acd0: Medium: CD-ROM unknown medium, unlocked > > /kernel: ata_command: timeout waiting for interrupt > > > > --^ > > > > It happens everytime I boot. What does the last line mean, and why does > > it appear? BTW, there's an audio CD in the CD-ROM drive, so it's not > > exactly "unknown" medium. What can I do to help fix this? > > I assume you only have those two devices on the ide channels right ?? > Then the problem is that the CDROM drive doesn't respond proberly > to a command, in fact it doesn't respond at all, there is no interrupt. > Have you tried another CDROM drive ?? This smells alot like substandard > hardware. Yes, HDD on the primary, CD-ROM on the secondary controller. This is a notebook I'm talking about, so I haven't tried any other CD-ROM drives. If it doesn't respond at all, then how do you get all the other information, such as supported read types, speed, etc? Perhaps there is some other way of making this particular CD-ROM drive generate an interrupt? Of course, it's just a minor annoyance (and otherwise I'm very pleased with the driver's performance - many thanks to SOS), but if the new ATA driver were to eventually replace the old one, it's not a bad idea to try and get rid of as many silly error messages as possible. Is there just one standard that all ATAPI CD-ROM drives must comply with, or can there be variations? I apologize if this is a silly question. Frank To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wd0: interrupt timeout (status 58 error 1)
An unrelated question: I get the following in my dmesg: /kernel: ata0: master: setting up UDMA2 mode on PIIX4 chip OK /kernel: ad0: ATA-4 disk at ata0 as master /kernel: ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S /kernel: ad0: piomode=4, dmamode=2, udmamode=2 /kernel: ad0: 16 secs/int, 0 depth queue, DMA mode /kernel: acd0: CDROM drive at ata1 as master /kernel: acd0: drive speed 4134KB/sec, 128KB cache /kernel: acd0: supported read types: CD-R, CD-RW, CD-DA /kernel: acd0: Audio: play, 256 volume levels /kernel: acd0: Mechanism: ejectable tray /kernel: acd0: Medium: CD-ROM unknown medium, unlocked /kernel: ata_command: timeout waiting for interrupt --^ It happens everytime I boot. What does the last line mean, and why does it appear? BTW, there's an audio CD in the CD-ROM drive, so it's not exactly "unknown" medium. What can I do to help fix this? Frank To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
Cameron Grant wrote: > > to let newpcm out of the cage so you can all get your grubby little hands on > it. > > http://www.vilnya.demon.co.uk/newpcm+dfrpnp-19990807.diff.gz > > this is a patch against a recent -current. if you have a pci or isapnp > soundcard, you should have pnp0 and pcm0 in your kernel config as > appropriate. isapnp cards should not need any pnp lines in kernel.conf. > > the list of supported cards is as for luigi's driver, with the addition of a > couple more mss-clones, and trident 4dwave. there is a part done aureal > vortex driver which is as yet nonfunctional. mmap() is supported but not > well tested. format conversions are supported. the code seems to be > stable. > > please test it and email me success and failure reports. > > - cameron Hi, First, I'd like to thank Cameron for his great work on the pcm driver. It builds and installs cleanly, and generally looks very impressive. I apologize in advance if the following message is a bit on the long side, but the problem I'm going to describe is very odd. I must also make clear that the sound card works fine under Windoze, and it also worked fine with the old pcm driver, until something got broken around 20 April this year (_after_ the integration of new bus). The sound card settings are changeable in the BIOS; this is what I have (the card is a non-PnP Yamaha): Sound: Enabled (other options are: Disabled and Auto) SB I/O address: 220-22F WSS I/O address:530-538 Adlib I/O address: 388-38F MPU I/O address:300-301 CTRL I/O address: 100 (OPL3 chip control) DMA A: DMA 1 (other options: 0,7) DMA B: DMA 0 (other options: 1,7) IRQ:IRQ 5 In accordance with these settings, I used the following line in the kernel: device pcm0 at isa? port 0x530 irq 5 drq 1 flags 0x10 (Note the order of the DMA channels - 1, then 0) Now this is what happens: the driver successfully detects the card, but fails to register an interrupt: /kernel: mss_detect - chip revision 0x0a /kernel: mss_detect() - Detected CS4231 /kernel: pcm0: at port 0x530-0x53f,0x310-0x311 irq 5 drq 1 flags 0xa210 on isa0 /kernel: pcm: setmap 3, ff00; 0xc7bdd000 -> 3 /kernel: pcm: setmap 4, ff00; 0xc7bed000 -> 4 /kernel: device combination doesn't support shared irq3 /kernel: intr_connect(irq3) failed, result=-1 /kernel: device combination doesn't support shared irq4 /kernel: intr_connect(irq4) failed, result=-1 /kernel: device combination doesn't support shared irq5 /kernel: intr_connect(irq5) failed, result=-1 /kernel: device combination doesn't support shared irq7 /kernel: intr_connect(irq7) failed, result=-1 /kernel: device combination doesn't support shared irq9 /kernel: intr_connect(irq9) failed, result=-1 /kernel: device combination doesn't support shared irq12 /kernel: intr_connect(irq12) failed, result=-1 /kernel: device combination doesn't support shared irq14 /kernel: intr_connect(irq14) failed, result=-1 /kernel: device combination doesn't support shared irq15 /kernel: intr_connect(irq15) failed, result=-1 IRQ 5 is definitely unused, and exactly the same setup worked fine with the old pcm driver. Another strange thing is that cat /dev/sndstat shows: FreeBSD Audio Driver (newpcm) Aug 8 1999 21:55:41 Installed devices: pcm0: at io 0x530 irq 5 drq 1:0 (1/1 channels duplex) as if everything were ok. It also seems that although intr_connect fails, IRQ 5 is marked as being in use, because pcic then chooses the next one available (10): /kernel: PC-Card VLSI 82C146 (5 mem & 2 I/O windows) /kernel: pcic: controller irq 10 Now the VERY odd thing: if I use DMA channels 0 and 1 (as opposed to 1 and 0), change the BIOS settings accordingly, and compile the kernel with device pcm0 at isa? port 0x530 irq 5 drq 0 flags 0x11 I get the following error: /kernel: mss_detect - chip revision 0x0a /kernel: mss_detect() - Detected CS4231 /kernel: pcm0: at port 0x530-0x53f,0x310-0x311 irq 5 flags 0xa211 on isa0 + /kernel: device_probe_and_attach: pcm0 attach returned 6 /kernel: device combination doesn't support shared irq3 /kernel: intr_connect(irq3) failed, result=-1 /kernel: device combination doesn't support shared irq4 /kernel: intr_connect(irq4) failed, result=-1 /kernel: device combination doesn't support shared irq7 /kernel: intr_connect(irq7) failed, result=-1 /kernel: device combination doesn't support shared irq9 /kernel: intr_connect(irq9) failed, result=-1 /kernel: device combination doesn't support shared irq12 /kernel: intr_connect(irq12) failed, result=-1 /kernel: device combination doesn't support shared irq14 /kernel: intr_connect(irq14) failed, result=-1 /kernel: device combination doesn't support shared irq15 /kernel: intr_connect(irq15) failed, result=-1 /kernel: PC-Card VLSI 82C146 (5 mem & 2 I/O windows) + /kernel: pcic: controller irq 5 and cat: /dev/s
