headers
Aaron J. Grier | 1 Aug 2006 03:13

AMD GX3 geode support

I've got an geode-based IEI WAFER LX 800 3.5" single-board-computer [1]
it boots and (mostly) runs NetBSD-3, but has some showstopping caveats
for my application.

I've attached the full dmesg, but here's the bits that concern me:

* IDE support:

pciide0 at pci0 dev 15 function 2
pciide0: Advanced Micro Devices product 0x209a (rev. 0x01)
pciide0: bus-master DMA support present, but unused (no driver support)
pciide0: primary channel wired to compatibility mode
pciide0: primary channel ignored (other hardware responding at addresses)
pciide0: secondary channel wired to compatibility mode
pciide0: secondary channel ignored (not responding; disabled or no drives?)

performance is poor, as expected.  but it does work.

* audio:

Advanced Micro Devices product 0x2093 (audio multimedia, revision 0x01) at pci0 dev 15 function 3 not configured

the codec is an avance logic (realtek) ALC203.  I assume only the glue
to the AC97 bus is missing to get this working.

this is a showstopper for my application.

* floating point:

npx0 at isa0 port 0xf0-0xff: error reporting broken; not using
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jonathan A. Kollasch | 1 Aug 2006 05:24
Gravatar

Re: AMD GX3 geode support

On Mon, Jul 31, 2006 at 06:13:45PM -0700, Aaron J. Grier wrote:
> I've got an geode-based IEI WAFER LX 800 3.5" single-board-computer [1]
> it boots and (mostly) runs NetBSD-3, but has some showstopping caveats
> for my application.
> 
> I've attached the full dmesg, but here's the bits that concern me:
> 
> * IDE support:
> 
> pciide0 at pci0 dev 15 function 2
> pciide0: Advanced Micro Devices product 0x209a (rev. 0x01)
> pciide0: bus-master DMA support present, but unused (no driver support)
> pciide0: primary channel wired to compatibility mode
> pciide0: primary channel ignored (other hardware responding at addresses)
> pciide0: secondary channel wired to compatibility mode
> pciide0: secondary channel ignored (not responding; disabled or no drives?)
> 
> performance is poor, as expected.  but it does work.
> 

Probably could be supported by geodeide(4) or viaide(4)

> * audio:
> 
> Advanced Micro Devices product 0x2093 (audio multimedia, revision 0x01) at pci0 dev 15 function 3 not configured
> 
> the codec is an avance logic (realtek) ALC203.  I assume only the glue
> to the AC97 bus is missing to get this working.
> 
> this is a showstopper for my application.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rick Kelly | 2 Aug 2006 03:02

sound cards


Which sound cards, that are currently offered for sale, will work with
NetBSD 3.0_stable, and also work with Quake II? When I run it on my
ASUS A8V board:

auvia0 at pci0 dev 17 function 5: VIA Technologies VT8237 AC'97 Audio (rev 0x60)
auvia0: ac97: ext id 9c6<AC97_23,LDAC,SDAC,CDAC,SPDIF,DRA>

Quake II shuts off the sound because it doesn't like the chip.

loading oss sound output driver, ok
SNDDMA_Init: Sorry, but your soundcard doesn't support trigger or mmap. (00001100)

--

-- 
Rick Kelly	rmk <at> rmkhome.com
		<http://www.rmkhome.com/>
		<http://rkba.rmkhome.com/>
Permalink | Reply | 1 comment |
headers
Jukka Marin | 2 Aug 2006 17:32
Picon

Re: momentary freezes in -current

An update:

On Mon, Jul 24, 2006 at 01:16:30PM +0300, Jukka Marin wrote:
> I'm setting up this SMP amd64 system, now running the i386 port, -current
> kernel and binaries built yesterday.
> 
> I have a large raidframe "disk" (raid1, two SATA disks).  I used tar
> to archive some 30 GB of files into a partition (no softdep) on the
> raid disk.  The source files were read over NFS.  Nothing else (but
> systat) was running on the system.
> 
> A few times during the copy, the system froze completely and then
> woke up again.  When this happens, the system does not respond to
> ping, it doesn't update the systat display or do anything visible.
> During the copy, over 40 ping packets were lost.

The system does _not_ freeze, but the network interface does.

I had been using the amd64 system over LAN only, so when the network
interface paused, my ssh connection (and ping etc) was also paused.

Sorry for spreading misinformation about this ;)

This what dmesg says about the networking hardware:

nfe0 at pci0 dev 10 function 0APCH: Picked IRQ 21 with weight 1: ioapic0 pin 21 (irq 10), address 00:e0:81:55:90:81
makphy0 at nfe0 phy 1: Marvell 88E1111 Gigabit PHY, rev. 2
makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Lord | 3 Aug 2006 03:49

Unable to boot NetBSD 3.0 on Asus P4R800V m/b


I have two fileservers, Asus P4R800V + Celeron 2400, running FreeBSD 
since Feb 2004 currently v5.3. I decided to move these onto NetBSD 
3.0 rather than upgrade to FreeBSD 6.x as already using NetBSD for 
firewall and internet facing server.

I first tried with 3.0.1 boot floppy then booting from 3.0 cdrom with 
same result on both servers. Partway through boot process the 
keyboard leds flash on then off, and remain off, then shortly after 
one of messages is 'kbc: cmd write error' and then hangs at probing 
for isa pnp.

Anyone already have a solution to this?

David
Permalink | Reply | 1 comment |
headers
David Lord | 3 Aug 2006 13:31

Re: Unable to boot NetBSD 3.0 on Asus P4R800V m/b

On 3 Aug 2006, at 1:49, NetBSD mailing list <port-i38 wrote:

> I have two fileservers, Asus P4R800V + Celeron 2400, running 
FreeBSD
> since Feb 2004 currently v5.3. I decided to move these onto NetBSD 
3.0
> rather than upgrade to FreeBSD 6.x as already using NetBSD for
> firewall and internet facing server.
> 
> I first tried with 3.0.1 boot floppy then booting from 3.0 cdrom 
with
> same result on both servers. Partway through boot process the 
keyboard
> leds flash on then off, and remain off, then shortly after one of
> messages is 'kbc: cmd write error' and then hangs at probing for 
isa
> pnp.
> 
> Anyone already have a solution to this?

I've now tried with NetBSD 1.6.1 which shows same problem.
Possibly I have 1.6.1 on one of small hdds (420MB or 240MB) that 
might be worth trying as kernels were well trimmed down for running 
in only 8 MB ram.

Other thing I've tried is to interrupt boot and try boot -c but this
just causes leds on kbd to flash as before and when userconf prompt 
appears kbd is out of action so getting this working is looking even 
more unlikely.
(Continue reading)

Permalink | Reply | 501 comments |
headers
David Lord | 3 Aug 2006 19:00

Re: Unable to boot NetBSD 3.0 on Asus P4R800V m/b

On 3 Aug 2006, at 11:31, David Lord wrote:

> On 3 Aug 2006, at 1:49, NetBSD mailing list <port-i38 wrote:
> 
> > I have two fileservers, Asus P4R800V + Celeron 2400, running 
> FreeBSD
> > since Feb 2004 currently v5.3. I decided to move these onto NetBSD 
> 3.0
> > rather than upgrade to FreeBSD 6.x as already using NetBSD for
> > firewall and internet facing server.
> > 
> > I first tried with 3.0.1 boot floppy then booting from 3.0 cdrom 
> with
> > same result on both servers. Partway through boot process the 
> keyboard
> > leds flash on then off, and remain off, then shortly after one of
> > messages is 'kbc: cmd write error' and then hangs at probing for 
> isa
> > pnp.
> > 
> > Anyone already have a solution to this?
> 
> I've now tried with NetBSD 1.6.1 which shows same problem.
> Possibly I have 1.6.1 on one of small hdds (420MB or 240MB) that might
> be worth trying as kernels were well trimmed down for running in only
> 8 MB ram.
> 
> Other thing I've tried is to interrupt boot and try boot -c but this
> just causes leds on kbd to flash as before and when userconf prompt
> appears kbd is out of action so getting this working is looking even
(Continue reading)

Permalink | Reply | 501 comments |
headers
Stéphane Witzmann | 4 Aug 2006 17:23
Picon

Re: clcs audio problem

Henry R. Bent wrote:

> Hello all,
> 
> I have an i386 box running 3.99.18 from mid-April that has been having
> audio problems with the clcs driver.  Until very recently the sound
> quality would remain good for a long time, maybe 10 or 15 days, until it
> slowly started to degrade into ringing digitized mush.  Now it will remain
> good for day or so until it very suddenly changes for the worse.  A reboot
> always fixes things, but I use NetBSD so that I don't have to reboot :-)
>
> My questions are as follows:
> 
> -Does anyone know what is happening and why?  Could this be a hardware
> problem?
> -Should I try updating to the latest -current?  My experiences with it on
> other machines lead me to believe that it is not at all stable right now,
> so I am rather hesitant to do that.

I'm sorry for not reading this post sooner.

This is a driver issue (I've been working on it since last year). I spent
much time comparing clcs(4) with its FreeBSD and Linux counterparts. We
fixed a few bugs in clcs, and this one is the last one standing.

Anyway, I have a fix so that you don't have to reboot. Open xmms, play a
mp3, then keep pressing 'c' (play/pause). After a few seconds (a few dozens
start/stop cycles), the sound will be back to normal. This can also be used
to trigger the bug.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Todd Vierling | 5 Aug 2006 03:00
Gravatar

Xen3/PAE problems with domainU

This is Bcc:'d to port-i386 as it also concerns PAE, which may be required
to get things working correctly.  The main thread should remain on port-xen.

So I am in contact with the proprietor of a hosting company that is offering
Xen-based hosting, and is moving to Xen 3.  We had a pretty well working
NetBSD domU setup for Xen2.  But for PAE and other things, this host has to
move to Xen3.

I got the 20060803 build of the Xen3 kernels, and the host ran into this
when creating the domain.  The host has Linux kernel 2.6.16 compiled
directly from xensource + distro sources, and has xentools 3.0.2-2
installed.

==========

[2006-08-04 17:27:10 xend.XendDomainInfo] DEBUG (XendDomainInfo:178)
XendDomainInfo.create(['vm', ['name', 'xen30'], ['memory', 96], ['vcpus', 1], ['image', ['linux',
['kernel', '/boot/netbsd-XEN3_DOMU'], ['root', '/dev/xbd0a']]], ['device', ['vbd', ['uname',
'phy:/dev/xen/xen30-disk'], ['dev', 'hda1'], ['mode', 'w']]], ['device', ['vbd', ['uname',
'phy:/dev/xen/xen30-swap'], ['dev', 'hda2'], ['mode', 'w']]]])
[2006-08-04 17:27:10 xend.XendDomainInfo] DEBUG (XendDomainInfo:284) parseConfig: config is ['vm',
['name', 'xen30'], ['memory', 96], ['vcpus', 1], ['image', ['linux', ['kernel',
'/boot/netbsd-XEN3_DOMU'], ['root', '/dev/xbd0a']]], ['device', ['vbd', ['uname',
'phy:/dev/xen/xen30-disk'], ['dev', 'hda1'], ['mode', 'w']]], ['device', ['vbd', ['uname',
'phy:/dev/xen/xen30-swap'], ['dev', 'hda2'], ['mode', 'w']]]]
[2006-08-04 17:27:10 xend.XendDomainInfo] DEBUG (XendDomainInfo:380) parseConfig: result is
{'ssidref': None, 'uuid': None, 'on_crash': None, 'on_reboot': None, 'image': ['linux', ['kernel',
'/boot/netbsd-XEN3_DOMU'], ['root', '/dev/xbd0a']], 'on_poweroff': None, 'cpus': None, 'name':
'xen30', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'vcpu_avail': None, 'memory': 96, 'device':
[('vbd', ['vbd', ['uname', 'phy:/dev/xen/xen30-disk'], ['dev', 'hda1'], ['mode', 'w']]), ('vbd',
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Lord | 5 Aug 2006 21:13

NetBSD 3.0 on Asus P4R800V auixp and SMbus support


I managed to get NetBSD 3.0.1 to install over NFS onto the ASUS 
P4R800V PC (took < 15 minutes for full install from mounted 3.0.1 
release directory).

First boot was a problem with screen filling up with continuous lines 
of:
  auixp0: codec read timeout (reg 26).

I disabled auixp0 at bootup and compiled a kernel without that 
driver. The dmesg output now shows a couple of devices as not 
configured:

ATI Technologies SB200 SMBus Controller (SMBus serial bus, revision 
0x18) at pci0 dev 20 function 0 not configured
ATI Technologies IXP AC'97 Audio Controller (audio multimedia) at 
pci0 dev 20 function 5 not configured

Any ideas as to how to get both these or at least auixp0 working.

FWIW I've checked throug backup of previous FreeBSD 5.3 on this m/b 
and find similar with both being detected but neither configured.

I could buy a pci soundcard but I'd rather avoid that if possible.

David
Permalink | Reply | 0 comments |

Gmane