Novatel Merlin

2003-06-18 Thread Glenn Dawson
I'm trying to get a Novatel Merlin for Ricochet working under -CURRENT.
http://www.novatelwireless.com/support/support_ricochet.html
I've been able to connect to their network via PPP and do things like ping 
and traceroute to the rest of the internet.  However, when I try things 
that produce larger packets (ftp, telnet, ssh, etc), nothing works.

I've noticed (in the PPP logs and when sending AT commands directly) that 
characters get dropped occasionally.  I also found this document 
http://homepages.nyu.edu/~gmp216/nrm6842/bigfastuart.html which explains 
that the Merlin for Ricochet has a 576 byte buffer which, if full, will try 
and flush itself on a single interrupt.  Apparently under linux this is a 
problem because the serial buffer is only 512 bytes and it overflows.  Is 
this also a problem in FreeBSD?

I also get a lot of messages like this in /var/log/messages and on the console:

Jun 16 23:31:16 foo kernel: sio4: 137 more interrupt-level buffer overflows 
(total 821)

That would seem to indicate that dumping 576 bytes on a single interrupt is 
too much.  yes? no?

If the serial buffer is too small, would it be difficult to increase it's size?

Any help would be greatly appreciated.  If I need to provide more info just 
let me know what to provide.

Thanks!

-Glenn

dmesg:

Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.1-CURRENT #2: Tue Jun 17 01:09:59 GMT 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/foo
Preloaded elf kernel "/boot/kernel/kernel" at 0xc04ac000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04ac21c.
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 1666204780 Hz
CPU: AMD Athlon(TM) XP 2000+ (1666.20-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x662  Stepping = 2
  Features=0x383fbff
OV,PAT,PSE36,MMX,FXSR,SSE>
  AMD Features=0xc040
real memory  = 536854528 (511 MB)
avail memory = 516341760 (492 MB)
Pentium Pro MTRR support enabled
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 11 entries at 0xc00f2050
acpi0: power button is handled as a fixed feature programming model.
Timecounter "ACPI-fast"  frequency 3579545 Hz
acpi_timer0: <32-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0
acpi_cpu0:  on acpi0
acpi_cpu: CLK_VAL field overlaps THT_EN bit
acpi_button0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
pcib0: slot 5 INTA is routed to irq 10
pcib0: slot 9 INTA is routed to irq 4
pcib0: slot 9 INTB is routed to irq 11
pcib0: slot 9 INTC is routed to irq 10
pcib0: slot 13 INTA is routed to irq 11
pcib0: slot 15 INTA is routed to irq 12
pcib0: slot 15 INTB is routed to irq 4
agp0:  mem 0xe000-0xe3ff at device 
0.0 o
n pci0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pci1:  at device 0.0 (no driver attached)
pci0:  at device 5.0 (no driver attached)
pci0:  at device 9.0 (no driver attached)
pci0:  at device 9.1 (no driver attached)
pci0:  at device 9.2 (no driver attached)
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xb800-0xb87f mem 
0xd700-0xd700
007f irq 11 at device 13.0 on pci0
xl0: Ethernet address: 00:01:02:2a:53:0e
miibus0:  on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
cbb0:  irq 12 at device 15.0 on pci0
cardbus0:  on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb1:  irq 4 at device 15.1 on pci0
cardbus1:  on cbb1
pccard1: <16-bit PCCard bus> on cbb1
isab0:  at device 17.0 on pci0
isa0:  on isab0
atapci0:  port 0xb400-0xb40f at device 17.1 
on pci
0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
atkbdc0:  port 0x64,0x60 irq 1 on acpi0
atkbd0:  flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
orm0:  at iomem 0xc-0xc7fff on isa0
pmtimer0 on isa0
fdc0: ready for input in output
fdc0: cmd 3 failed at out byte 1 of 3
ppc0: parallel port not found.
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250 or not responding
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounters tick every 10.000 msec
pccard1: Allocation failed for cfe 32
sio4:  at port 0x2f8-0x2ff irq 4 
functio
n 0 config 33 on pccard1
sio4: type 16550A
sio4: unable to activate interrupt in fast mode - using normal mode
ata1-master: timeout waiting for interrupt
ata1-master: ATA identify failed
ad0: 13031MB  [26476/16/63] at ata0-master UDMA66
Mounting root from ufs:/dev/ad0s1a 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: kern/43345: Support for the SiS 651 ATA controller

2003-02-12 Thread Glenn Dawson
I have the same hardware from shuttle and tried using the same patch on 
-STABLE.

I found that while the patch would let the machine boot and at least use 
the drive at ATA100 speeds, the system was unstable.  During periods of 
heavy disk usage there were random errors reading from the disk.

I opted to keep DMA disabled and wait for Soeren's update.

-Glenn

At 09:24 AM 2/12/2003, you wrote:
Hi,

When I attempted to install FreeBSD 5.0-RELEASE on a Shuttle SS51G box, 
just like some other users, I encountered the "ata0: READ command timeout" 
error during boot.  I then tried 4.7-RELEASE and saw the same problem.

A quick search of the FreeBSD mail archives turned up other users with my 
same hardware (which uses the SiS 651 ata controller) who had encountered 
this.  Those messages told me that I needed to either disable UDMA in my 
system's BIOS, or set the sysctl variable hw.ata.ata_dma to zero.  I 
disabled UDMA in my BIOS and was able to complete the install.

Then on one of the messages, I noticed a link to Patrick Bihan-Faou's 
problem report, read it, and tried out his patch under 5.0-CURRENT (having 
completed my install of 5.0-RELEASE and updated to -CURRENT). Of course 
the line numbers were a bit different, but a hand patch of the two files 
was quick and easy.  A quick kernel recompile, BIOS re-enable of UDMA, and 
boot proved the patch worked!

Thank you, Patrick, for your patch!

Now for a few questions:

Is there any way Patrick's solution could be temporarily committed to 
-CURRENT and/or -STABLE until Soeren's forthcoming real solution is 
available (the one Soeren mentions in the PR)? Is there some bad side 
effect to Patrick's two-line temporary fix that I should worry about? If 
there are no negatives to the patch (other than a better fix is coming in 
the future), is there some other reason that the patch is not a good 
temporary solution for users with SiS 651 based systems, so they can 
install and boot to FreeBSD without the work-arounds (BIOS or sysctl 
setting change)?

Thanks for your good work, Soeren, and thanks again for your patch, Patrick.

Aaron out.

P.S. Here is Patrick's solution as a diff against a recent 5.0-CURRENT:

--- /usr/src/sys/dev/ata/ata-dma.c.orig Fri Feb  7 11:22:38 2003
+++ /usr/src/sys/dev/ata/ata-dma.c  Fri Feb  7 11:23:24 2003
@@ -645,6 +645,7 @@
ata_find_dev(parent, 0x06401039, 0) ||  /* SiS 640 */
ata_find_dev(parent, 0x06451039, 0) ||  /* SiS 645 */
ata_find_dev(parent, 0x06501039, 0) ||  /* SiS 650 */
+   ata_find_dev(parent, 0x06511039, 0) ||  /* SiS 651 */
ata_find_dev(parent, 0x07301039, 0) ||  /* SiS 730 */
ata_find_dev(parent, 0x07331039, 0) ||  /* SiS 733 */
ata_find_dev(parent, 0x07351039, 0) ||  /* SiS 735 */
--- /usr/src/sys/dev/ata/ata-pci.c.orig Fri Feb  7 11:22:46 2003
+++ /usr/src/sys/dev/ata/ata-pci.c  Fri Feb  7 11:23:40 2003
@@ -189,6 +189,7 @@
ata_find_dev(dev, 0x06401039, 0) ||
ata_find_dev(dev, 0x06451039, 0) ||
ata_find_dev(dev, 0x06501039, 0) ||
+   ata_find_dev(dev, 0x06511039, 0) ||
ata_find_dev(dev, 0x07301039, 0) ||
ata_find_dev(dev, 0x07331039, 0) ||
ata_find_dev(dev, 0x07351039, 0) ||


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message