5.3-STABLE ACPI problems after 12/17 with Toshiba Tecra 8100
look here : http://lists.freebsd.org/pipermail/freebsd-acpi/2004-December/001050.html __ Do you Yahoo!? Dress up your holiday email, Hollywood style. Learn more. http://celebrity.mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB scanner not attached when connected after system startup]
On Thu, Dec 30, 2004 at 09:33:32AM +0100, Marc Fonvieille wrote:
> On Wed, Dec 29, 2004 at 04:49:05PM +0100, Harald Weis wrote:
> >
> > My scanner (EPSON PERFECTION 1650) is working alright if it is connected
> > before system startup.
> > But when connected to the running system it doesn't get attached by usbd. I
> > can't find out from Handbook, manpages or mailing lists what could be the
> > reason.
> >
>
> I assume you followed the Image Scanner section in the Handbook.
> Is usbd really running? Are you using the default usbd.conf?
In reply to both Marc and Roland, I confirm and say:
1. usbd is really running all the time (usbd_enable="YES" being in rc.conf)
2. using the default usbd.conf, which I studied only recently to find out what
could be missing.
3. added the following lines to it for testing:
device "Perfection 1650 scanner"
devname "uscanner[0-9]+"
attach "sane-find-scanner -q"
detach "sane-find-scanner -q"
I still haven't got a clue of what other command could be useful here. I think
Ialso understood that the proper attachment/detachment function of usbd has
nothing to do with those commands. Right or wrong?
4. Killing usbd and running ``usbd -dvv'' confirms that usbd does not detect
any event when I connect or disconnect the signal cable of the scanner
(needless to say that the scanner is connected to power). No error message in
the debugging output, just this:
algol{me} ~ # usbd -dvv
usbd: opened /dev/usb0
usbd: reading configuration file /etc/usbd.conf
usbd: action 1: ActiveWire board, firmware download
.
.
.
usbd: action 6: Perfection 1650 scanner
devname: uscanner[0-9]+
attach='sane-find-scanner -q'
detach='sane-find-scanner -q'
usbd: action 7: USB device
usbd: 7 actions
usbd: opened /dev/usb
usbd: doing timeout discovery on /dev/usb0
usbd: processing event queue due to timeout on /dev/usb
etc, etc ad infinitum
No event, no action. Normal.
Harald :-(
--
FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dump/restore with ufs2
On Thu, Dec 30, 2004 at 09:53:38PM +0100, Roland Smith wrote: > On Thu, Dec 30, 2004 at 05:54:25PM +, Ceri Davies wrote: > > On Tue, Dec 28, 2004 at 01:23:50PM -0500, Brian Szymanski wrote: > > > When I run the following script, I get a warning message, and I'm > > > wondering if it's ignorable or indicates there is a little more work to be > > > done in getting dump/restore happy with ufs2... > > > > > > $ cd /altroot > > > $ dump -L -0 -a -f - /dev/$ROOT | restore -rf - > > > ... > > > warning: ./.snap: File exists > > > > > > Does this mean my snapshots are being overwritten on the target disk? And > > > if so, that's a good thing, right? > > > > That's just a warning that .snap already exists in the current directory > > (which is because it gets created by newfs); the contents will remain > > unaffected since snapshots are not dumped (I believe). > > A snapshot _is_ what is being dumped when you use the -L option to > dump. See the manual page. I know that. I meant that snapshots are not included in the dump. Ceri -- Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-- Einstein (attrib.) pgpzWBJRtlcXu.pgp Description: PGP signature
Re: USB scanner not attached when connected after system startup]
On Fri, Dec 31, 2004 at 04:07:12PM +0100, Harald Weis wrote: > > In reply to both Marc and Roland, I confirm and say: > > 1. usbd is really running all the time (usbd_enable="YES" being in rc.conf) > 2. using the default usbd.conf, which I studied only recently to find out > what could be missing. > 3. added the following lines to it for testing: > device "Perfection 1650 scanner" > devname "uscanner[0-9]+" > attach "sane-find-scanner -q" > detach "sane-find-scanner -q" > > I still haven't got a clue of what other command could be useful here. > I think Ialso understood that the proper attachment/detachment > function of usbd has nothing to do with those commands. Right or > wrong? [...] Do not add anything in /etc/usbd.conf, use the file you can find in /usr/share/examples/etc/usbd.conf Then follow http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html that section was written with many scanners for testing purposes, and one of them was a Perfection 1650... Marc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
IPNAT & IPv6
my original ipnat rule is rdr rl0 0.0.0.0/0 port 80 -> 127.0.0.1 port 8000 tcp which redirect a priv port to a non-priv port but when i setup dual stack, i find it's unable to handle ipv6 connections. when i change 0.0.0.0 to ::0, ipnat complains it can't resolve it. even when i use domains instead of numeric format, still no help. so it seems that ipnat doesn't work with ipv6? any solution? -- freewizard (at) gmail.com http://blog.tsing.org/freewizard/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ports directories are broken again?
About a month ago I saw a problem where many of the packaged ports disappeared from the main and mirror ftp sites. I didn't have time to drop a message then, and just compiled them myself. However I'm seeing this problem again today. And it isn't just this one package -- numerous items that appear in the ports searches are missing. neptune.sv$ fetch ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/All/frontpage-5.0.2.2623_1.tbz fetch: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/All/frontpage-5.0.2.2623_1.tbz: File unavailable (e.g., file not found, no access) neptune.sv$ pkg_add -r frontpage Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/Latest/frontpage.tbz: File unavailable (e.g., file not found, no access) neptune.sv$ ftp ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/All/ Trying 204.152.184.73... Connected to ftp.freebsd.org. ...etc clipped login readme 250 Directory successfully changed. 250 Directory successfully changed. ftp> ls front* 229 Entering Extended Passive Mode (|||13369|) 150 Here comes the directory listing. -rw-r--r--1 110 0 250431 Oct 21 21:21 frontline-0.5.4_1.tbz 226 Directory send OK. -- Joe Rhett Senior Geek Meer.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports directories are broken again?
On Fri, Dec 31, 2004 at 11:09:04AM -0800, Joe Rhett wrote: > About a month ago I saw a problem where many of the packaged ports > disappeared from the main and mirror ftp sites. I didn't have time to drop > a message then, and just compiled them myself. However I'm seeing this > problem again today. And it isn't just this one package -- numerous items > that appear in the ports searches are missing. > > neptune.sv$ fetch > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/All/frontpage-5.0.2.2623_1.tbz > fetch: > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/All/frontpage-5.0.2.2623_1.tbz: > File unavailable (e.g., file not found, no access) > > neptune.sv$ pkg_add -r frontpage > Error: FTP Unable to get > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/Latest/frontpage.tbz: > File unavailable (e.g., file not found, no access) > frontpage has not been packaged for years because a dependency (compat3x) is forbidden for security reasons. It looks like your expectations are broken here :) Kris pgp4Hm35kB0C9.pgp Description: PGP signature
ad2: FAILURE - READ_DMA, but CD on slave controller recognized?
this has started bugging me ever since moving from 4-stable to 5-stable. "ad2", which had been recognized no problem on the former, fails on the latter. since i have a multibooter, i can boot 4.10 residing on "ad2" without trouble. 4.10 can access "ad0" and "ad1" fine (this is how i got the initial install in place), but i used "ad2" for backups and this doesn't work anymore. the system otherwise works and there are no DMA related hardware errors ever reported except for "ad2" not beeing recognized. this seems to indicate that the problem lies in the initial disk checking phase. my boot/device.hints was installed with hints from the "GENERIC" kernel. everything else works fine. i tried to check the PRs (timed out), but google didn't return anything not related to failing hardware or misconfiguration, so could someone please look through this (verbose) dmesg(8)? ar: FreeBSD check1 failed ata1-slave: pio=0x0c wdma=0x22 udma=0x42 cable=40pin ata1-master: pio=0x0c wdma=0x22 udma=0x44 cable=40pin ata1-master: setting PIO4 on VIA 82C596 chip ata1-master: setting UDMA33 on VIA 82C596 chip ata1-slave: setting PIO4 on VIA 82C596 chip ad2: ATA-4 disk at ata1-master ad2: 19569MB (40079088 sectors), 39761 C, 16 H, 63 S, 512 B ad2: 16 secs/int, 1 depth queue, UDMA33 GEOM: new disk ad0 GEOM: new disk ad1 GEOM: new disk ad2 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:33350877 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 32256 length 17075649024 end 17075681279 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:16498692 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad1s1, start 32256 length 8447330304 end 8447362559 ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=40079025 ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=58 ostat1=50 ad2: stat=0x80 err=0x80 lsb=0x80 msb=0x80 ad2: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata1-slave: stat=0x10 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=50 stat1=10 devices=0x9 ata1: resetting done .. ata1-slave: pio=0x0c wdma=0x22 udma=0x42 cable=40pin ad2: pio=0x0c wdma=0x22 udma=0x44 cable=40pin ad2: setting PIO4 on VIA 82C596 chip ad2: setting UDMA33 on VIA 82C596 chip ata1-slave: setting PIO4 on VIA 82C596 chip ata1: device config done .. ad2: FAILURE - READ_DMA timed out ar: FreeBSD read conf failed ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=0 ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=58 ostat1=50 ad2: stat=0x80 err=0x80 lsb=0x80 msb=0x80 ad2: stat=0x50 err=0x01 lsb=0x00 msb=0x00 acd0: stat=0x10 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=50 stat1=10 devices=0x9 ata1: resetting done .. acd0: pio=0x0c wdma=0x22 udma=0x42 cable=40pin ad2: pio=0x0c wdma=0x22 udma=0x44 cable=40pin ad2: setting PIO4 on VIA 82C596 chip ad2: setting UDMA33 on VIA 82C596 chip acd0: setting PIO4 on VIA 82C596 chip ata1: device config done .. ad2: FAILURE - READ_DMA timed out ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=0 ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=58 ostat1=50 ad2: stat=0x80 err=0x80 lsb=0x80 msb=0x80 ad2: stat=0x50 err=0x01 lsb=0x00 msb=0x00 acd0: stat=0x10 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=50 stat1=10 devices=0x9 ata1: resetting done .. acd0: pio=0x0c wdma=0x22 udma=0x42 cable=40pin ad2: pio=0x0c wdma=0x22 udma=0x44 cable=40pin ad2: setting PIO4 on VIA 82C596 chip ad2: setting UDMA33 on VIA 82C596 chip acd0: setting PIO4 on VIA 82C596 chip ata1: device config done .. ad2: FAILURE - READ_DMA timed out ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=1 ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=58 ostat1=50 ad2: stat=0x80 err=0x80 lsb=0x80 msb=0x80 ad2: stat=0x50 err=0x01 lsb=0x00 msb=0x00 acd0: stat=0x10 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=50 stat1=10 devices=0x9 ata1: resetting done .. acd0: pio=0x0c wdma=0x22 udma=0x42 cable=40pin ad2: pio=0x0c wdma=0x22 udma=0x44 cable=40pin ad2: setting PIO4 on VIA 82C596 chip ad2: setting UDMA33 on VIA 82C596 chip acd0: setting PIO4 on VIA 82C596 chip ata1: device config done .. ad2: FAILURE - READ_DMA timed out ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=0 ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=58 ostat1=50 ad2: stat=0x80 err=0x80 lsb=0x80 msb=0x80 ad2: stat=0x50 err=0x01 lsb=0x00 msb=0x00 acd0: stat=0x10 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=50 stat1=10 devices=0x9 ata1: resetting done .. acd0: pio=0x0c wdma=0x22 udma=0x42 cable=40pin ad2: pio=0x0c wdma=0x22 udma=0x44 cable=40pin ad2: setting PIO4 on VIA 82C596 chip ad2: setting UDMA33 on VIA 82C596 chip acd0: setting PIO4 on VIA 82C596 chip ata1: device config done .. ad2: FAILURE - READ_DMA timed out GEOM: Configure ad0s1a, start 0 length 314572800 end 314572799 GEOM: Confi
ACPI + SMBus disables ISA bus
I'm trying to upgrade a system from 4.10 to 5.3p2 and am running into problems with the ISA bus disappearing (not probing or attaching) when I have both ACPI and SMBus enabled. This leads to a panic when something tries to do a sysctl on the (non-existent) console. The problem is masked if I use a serial console because the only ISA device I need is the VGA adapter and the lack of vga0 and syscons doesn't worry the serial console. I've had a google around and it looks like this combination should work. At least, I can't find anything forbidding it and can find some dmesgs showing both ACPI and SMBus. The relevant sections of a GENERIC "boot -v" shows: ... AcpiOsDerivePciId: bus 0 dev 17 func 0 AcpiOsDerivePciId: bus 0 dev 17 func 0 ... found-> vendor=0x1106, dev=0x3147, revid=0x00 bus=0, slot=17, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0087, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base fc00, size 4, enabled ... pci1: at device 0.0 (no driver attached) pci0: at device 8.0 (no driver attached) pci0: at device 11.0 (no driver attached) isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 If I add the following options to GENERIC: device smbus device viapm device smb device iicbb device iicbus then the ISA bus vanishes and the above probe messages change to: ... pci1: at device 0.0 (no driver attached) pci0: at device 8.0 (no driver attached) pci0: at device 11.0 (no driver attached) viapropm0: SMBus I/O base at 0x400 viapropm0: port 0x400-0x40f at device 17.0 on pci0 viapropm0: SMBus revision code 0x0 smbus0: on viapropm0 smb0: on smbus0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 The motherboard is a Gigabyte GA-7VRXP with F12 BIOS (the latest AFAIK). Switching between PIC and APIC modes in the BIOS has no effect. There's no explicit "PnP/nonPnP" option. Should this work? If so, where should I look for clues as to why it doesn't for me? -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports directories are broken again?
> On Fri, Dec 31, 2004 at 11:09:04AM -0800, Joe Rhett wrote: > > neptune.sv$ pkg_add -r frontpage > > Error: FTP Unable to get > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/Latest/frontpage.tbz: > > File unavailable (e.g., file not found, no access) On Fri, Dec 31, 2004 at 12:29:29PM -0800, Kris Kennaway wrote: > frontpage has not been packaged for years because a dependency > (compat3x) is forbidden for security reasons. It looks like your > expectations are broken here :) I have no expecation other than that if the freebsd site indicates that a package is available, that it should be there. It provides a link to a supposed package, which does not exist. And your comment of "for years" makes no sense when applied to versions of the OS which haven't existed for more than a few months. (not that it isn't true, but it certainly defies basic logic, no?) I'm checking for a package for 5.3-release, which is only a few months old. It indicates that a package exists, and provides a URL. The URL fails indicating the file isn't found. ... and "my expectations are broken" ? Can you really think of nothing else wrong here? -- Joe Rhett Senior Geek Meer.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB scanner not attached when connected after system startup]
On Fri, Dec 31, 2004 at 04:07:12PM +0100, Harald Weis wrote: > On Thu, Dec 30, 2004 at 09:33:32AM +0100, Marc Fonvieille wrote: > > On Wed, Dec 29, 2004 at 04:49:05PM +0100, Harald Weis wrote: > > > > > > My scanner (EPSON PERFECTION 1650) is working alright if it is connected > > > before system startup. > > > But when connected to the running system it doesn't get attached by usbd. > > > I can't find out from Handbook, manpages or mailing lists what could be > > > the reason. > > > > > > > I assume you followed the Image Scanner section in the Handbook. > > Is usbd really running? Are you using the default usbd.conf? > > In reply to both Marc and Roland, I confirm and say: > > 1. usbd is really running all the time (usbd_enable="YES" being in rc.conf) > 2. using the default usbd.conf, which I studied only recently to find out > what could be missing. > 3. added the following lines to it for testing: > device "Perfection 1650 scanner" > devname "uscanner[0-9]+" > attach "sane-find-scanner -q" > detach "sane-find-scanner -q" What are you trying to accomplish here? sane-find-scanner just lists the devices it finds. > I still haven't got a clue of what other command could be useful > here. I think Ialso understood that the proper attachment/detachment > function of usbd has nothing to do with those commands. Right or > wrong? On 5.3, I don't have to use usbd at all. The device node is created by devfs (on 5.3). You might have to do it manually on 4.x?. I use devfs.rules to make the scanner device available to a group usb, of which I'm a member, and that's it. Sane can use the scanner. For the record, my dll.conf looks like this: --- dll.conf --- # Load the epson backend. epson --- dll.conf --- And epson.conf contains just: -- epson.conf -- usb /dev/uscanner0 -- epson.conf -- > 4. Killing usbd and running ``usbd -dvv'' confirms that usbd does not > detect any event when I connect or disconnect the signal cable of the > scanner (needless to say that the scanner is connected to power). No > error message in the debugging output, just this: I usually do it the other way around. I keep the USB cable plugged in, and connect or disconnect the power to the transformer, because the 1650 doesn't have an on/off switch. Do you see anything in dmesg output after you plug in the scanner? Roland -- R.F. Smith /"\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \Respect for open standards pgp12DclDKTaa.pgp Description: PGP signature
Re: ports directories are broken again?
On Fri, Dec 31, 2004 at 03:57:55PM -0800, Joe Rhett wrote: > > On Fri, Dec 31, 2004 at 11:09:04AM -0800, Joe Rhett wrote: > > > neptune.sv$ pkg_add -r frontpage > > > Error: FTP Unable to get > > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/Latest/frontpage.tbz: > > > File unavailable (e.g., file not found, no access) > > On Fri, Dec 31, 2004 at 12:29:29PM -0800, Kris Kennaway wrote: > > frontpage has not been packaged for years because a dependency > > (compat3x) is forbidden for security reasons. It looks like your > > expectations are broken here :) > > I have no expecation other than that if the freebsd site indicates that a > package is available, that it should be there. It provides a link to a > supposed package, which does not exist. It provides a link to where the package would be if it exists. The web frontend has no knowledge of which packages are available at any given point in time because this set fluctuates on a daily basis, so the frontend is always going to have windows where it's out of date with respect to what's on the ftp site. One could imagine changing this with some hard work, or at least improving the documentation, but that's how things are today. You're welcome to submit a PR with your suggestion on how to change the documentation to annotate this. > And your comment of "for years" makes no sense when applied to versions of > the OS which haven't existed for more than a few months. (not that it > isn't true, but it certainly defies basic logic, no?) No, the ports tree is independent of the version of FreeBSD you're running. No version of FreeBSD has been able to produce a package of frontpage for a long time, because the package is not buildable in the underlying ports collection. Kris pgpaDSKYiM2Qr.pgp Description: PGP signature
Re: ports directories are broken again?
On Fri, Dec 31, 2004 at 05:22:00PM -0800, Kris Kennaway wrote: > On Fri, Dec 31, 2004 at 03:57:55PM -0800, Joe Rhett wrote: > > > On Fri, Dec 31, 2004 at 11:09:04AM -0800, Joe Rhett wrote: > > > > neptune.sv$ pkg_add -r frontpage > > > > Error: FTP Unable to get > > > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/Latest/frontpage.tbz: > > > > File unavailable (e.g., file not found, no access) > > I have no expecation other than that if the freebsd site indicates that a > > package is available, that it should be there. It provides a link to a > > supposed package, which does not exist. BTW, where are you seeing this link? The port index under www.freebsd.org/ports *does* know that frontpage will not appear in packages, and doesn't provide a link to it. http://www.freebsd.org/ports/www.html Kris pgpHyfCearSB1.pgp Description: PGP signature
BTX halted
hi all... i'm trying to install 5.3 on an amd machine... i got the discs and they are ok but when i start the off the disk the boot stops with BTX halted no matter which boot mode i chose. i looked on google and i found a few posts about bios issues but non of that helped - i couldn't find how to disable DMA. the only location i saw the DMA mentioned was under PnP/PCI configurations => Resources Controlled by in the bios but there the setting is Auto(ESCD). i tried al the options there and it still stops at the same place... anybody can help?! thanks -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
