Brian Buhrow | 1 Apr 17:11 2007

Parallels and NetBSD and sound generation

	Hello folks.  I know from reading various archives of this list that
some of you are running NetBSD under Parallels on Mac OsS X based systems.
For those of you that are, are you able to get sound to work under NetBSD?
If so, what is the quality of the sound, and how reliable is it?  What
driver is used to talk to the emulated sound card?

-thanks
-Brian

Brian Buhrow | 1 Apr 17:14 2007

Serial consoles and USB serial ports

	Hello.  I'm wondering if anyone has tried using a usb-connected serial
port as a serial console with NetBSD and if they've had success.  If not,
can anyone speculate on how hard it would be to get this to work?  Do some
BIOS's support legacy serial port emulation over USB devices?
-thanks
-Brian

Manuel Bouyer | 1 Apr 18:41 2007

Re: Netbsd-3-1 Zone file updates.

On Fri, Mar 30, 2007 at 07:20:55PM -0500, Greg A. Woods wrote:
> This definitely is not a port-i386 specific question -- it's probably
> better on tech-userlevel or netbsd-users or even netbsd-help.  You may
> want to repost in whatever you think is the more appropriate forum.
> 
> 
> At Thu, 29 Mar 2007 11:59:52 -0400, Derrick Lobo wrote:
> Subject: Netbsd-3-1 Zone file updates.
> > 
> > I was under the impression that the zone files have been updated from
> > Netbsd2.1 onwards...
> 
> Actually it would appear to me that pullups of the most recently
> imported tzdata files have not yet been done for the netbsd-3 branch
> (and its related release branches).

it was done yesterday

--

-- 
Manuel Bouyer <bouyer <at> antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--

Greg A. Woods | 1 Apr 20:10 2007
X-Face

Re: Netbsd-3-1 Zone file updates.

At Sun, 1 Apr 2007 18:41:18 +0200, Manuel Bouyer wrote:
Subject: Re: Netbsd-3-1 Zone file updates.
> 
> On Fri, Mar 30, 2007 at 07:20:55PM -0500, Greg A. Woods wrote:
> > This definitely is not a port-i386 specific question -- it's probably
> > better on tech-userlevel or netbsd-users or even netbsd-help.  You may
> > want to repost in whatever you think is the more appropriate forum.
> > 
> > 
> > At Thu, 29 Mar 2007 11:59:52 -0400, Derrick Lobo wrote:
> > Subject: Netbsd-3-1 Zone file updates.
> > > 
> > > I was under the impression that the zone files have been updated from
> > > Netbsd2.1 onwards...
> > 
> > Actually it would appear to me that pullups of the most recently
> > imported tzdata files have not yet been done for the netbsd-3 branch
> > (and its related release branches).
> 
> it was done yesterday

ah the joys of always being at least a day behind with an rsync'ed repo :-)

Thanks!  (though I think I'm going to abandon netbsd-3 for netbsd-4)

--

-- 
						Greg A. Woods

H:+1 416 218-0098 W:+1 416 489-5852 x122 VE3TCP RoboHack <woods <at> robohack.ca>
Planix, Inc. <woods <at> planix.com>       Secrets of the Weird <woods <at> weird.com>
(Continue reading)

Manuel Bouyer | 1 Apr 22:12 2007

Re: ACPI and invalid devices

On Fri, Mar 30, 2007 at 02:50:08PM -0400, Todd Kover wrote:
> db{0}> trace 
> cpu_Debugger(c097fca3,c0b927b4,c0b927a8,c048c525,e) at netbsd:cpu_Debugger+0x4
> panic(c09555a4,c38c0480,c0b927d8,c0464b1f,c0a9ef82) at netbsd:panic+0x155
> free(c38c0480,c0a4ca00,c0b92858,c051fd1c,c38c0480) at netbsd:free+0x1de
> AcpiOsFree(c38c0480,c0a014a0,2,c3db1f20,c3db1f20) at netbsd:AcpiOsFree+0x1a
> mpacpi_pcibus_cb(c3db1660,2,c3d0f300,0,1000000) at netbsd:mpacpi_pcibus_cb+0xfc
> AcpiNsWalkNamespace(6,c3db1e00,64,1,c051fc20) at netbsd:AcpiNsWalkNamespace+0xde
> 
> AcpiWalkNamespace(6,c3db1e00,64,c051fc20,c3d0f300) at netbsd:AcpiWalkNamespace+0
> x7e
> mpacpi_find_interrupts(c3d0f300,43b8c9,18,c3d0f358,c3d0f300) at netbsd:mpacpi_fi
> nd_interrupts+0x789
> acpi_md_callback(c3d0f300,c076eea0,c3d0f358,c38c0f10,1) at netbsd:acpi_md_callba
> ck+0x67
> acpi_attach(c38a4f80,c3d0f300,c0b92b3c,0,c0b92b3c) at netbsd:acpi_attach+0x176
> config_attach_loc(c38a4f80,c09f5480,0,c0b92b3c,0) at netbsd:config_attach_loc+0x
> 156
> config_found_ia(c38a4f80,c093e296,c0b92b3c,0,c3821f40) at netbsd:config_found_ia
> +0x32
> mainbus_attach(0,c38a4f80,0,c047f6be,c093d799) at netbsd:mainbus_attach+0x1c1
> config_attach_loc(0,c09f3db8,0,0,0) at netbsd:config_attach_loc+0x156
> config_attach(0,c09f3db8,0,0,c0b8f010) at netbsd:config_attach+0x2c
> config_rootfound(c093d799,0,c0b92c28,c0480ebf,c0a020a0) at netbsd:config_rootfou
> nd+0x44    
> cpu_configure(c0a020a0,a,0,0,c0aa44f0) at netbsd:cpu_configure+0x27
> configure(c0aa0d80,1,0,0,ffff) at netbsd:configure+0x2f
> main(fbff,c01002d2,0,0,0) at netbsd:main+0x115

Well, it works fine for me on a pe2950, with both i386 and amd64 GENERIC
(Continue reading)

Derrick Lobo | 3 Apr 00:02 2007

RE: Netbsd-3-1 Zone file updates.

Thanks Manuel

Derrick 
-----Original Message-----
From: Manuel Bouyer [mailto:bouyer <at> antioche.eu.org] 
Sent: Sunday, April 01, 2007 12:41 PM
To: NetBSD/i386 Discussion List
Cc: Derrick Lobo
Subject: Re: Netbsd-3-1 Zone file updates.

On Fri, Mar 30, 2007 at 07:20:55PM -0500, Greg A. Woods wrote:
> This definitely is not a port-i386 specific question -- it's probably 
> better on tech-userlevel or netbsd-users or even netbsd-help.  You may

> want to repost in whatever you think is the more appropriate forum.
> 
> 
> At Thu, 29 Mar 2007 11:59:52 -0400, Derrick Lobo wrote:
> Subject: Netbsd-3-1 Zone file updates.
> > 
> > I was under the impression that the zone files have been updated 
> > from Netbsd2.1 onwards...
> 
> Actually it would appear to me that pullups of the most recently 
> imported tzdata files have not yet been done for the netbsd-3 branch 
> (and its related release branches).

it was done yesterday

--

-- 
(Continue reading)

Jason Thorpe | 3 Apr 19:28 2007

Re: Serial consoles and USB serial ports


On Apr 1, 2007, at 8:14 AM, Brian Buhrow wrote:

> 	Hello.  I'm wondering if anyone has tried using a usb-connected  
> serial
> port as a serial console with NetBSD and if they've had success.

I don't know of anyone who has tried this.

>   If not,
> can anyone speculate on how hard it would be to get this to work?

Probably pretty difficult.  A lot of the kernel needs to be up and  
running for USB to work, and the console is needed quite early.

> Do some
> BIOS's support legacy serial port emulation over USB devices?

I am not aware of any.

It's a real shame that a traditional serial port is considered "legacy".

-- thorpej

Manuel Bouyer | 8 Apr 23:36 2007

Re: ACPI and invalid devices

On Sun, Apr 01, 2007 at 10:12:46PM +0200, Manuel Bouyer wrote:
> On Fri, Mar 30, 2007 at 02:50:08PM -0400, Todd Kover wrote:
> > db{0}> trace 
> > cpu_Debugger(c097fca3,c0b927b4,c0b927a8,c048c525,e) at netbsd:cpu_Debugger+0x4
> > panic(c09555a4,c38c0480,c0b927d8,c0464b1f,c0a9ef82) at netbsd:panic+0x155
> > free(c38c0480,c0a4ca00,c0b92858,c051fd1c,c38c0480) at netbsd:free+0x1de
> > AcpiOsFree(c38c0480,c0a014a0,2,c3db1f20,c3db1f20) at netbsd:AcpiOsFree+0x1a
> > mpacpi_pcibus_cb(c3db1660,2,c3d0f300,0,1000000) at netbsd:mpacpi_pcibus_cb+0xfc
> > AcpiNsWalkNamespace(6,c3db1e00,64,1,c051fc20) at netbsd:AcpiNsWalkNamespace+0xde
> > 
> > AcpiWalkNamespace(6,c3db1e00,64,c051fc20,c3d0f300) at netbsd:AcpiWalkNamespace+0
> > x7e
> > mpacpi_find_interrupts(c3d0f300,43b8c9,18,c3d0f358,c3d0f300) at netbsd:mpacpi_fi
> > nd_interrupts+0x789
> > acpi_md_callback(c3d0f300,c076eea0,c3d0f358,c38c0f10,1) at netbsd:acpi_md_callba
> > ck+0x67
> > acpi_attach(c38a4f80,c3d0f300,c0b92b3c,0,c0b92b3c) at netbsd:acpi_attach+0x176
> > config_attach_loc(c38a4f80,c09f5480,0,c0b92b3c,0) at netbsd:config_attach_loc+0x
> > 156
> > config_found_ia(c38a4f80,c093e296,c0b92b3c,0,c3821f40) at netbsd:config_found_ia
> > +0x32
> > mainbus_attach(0,c38a4f80,0,c047f6be,c093d799) at netbsd:mainbus_attach+0x1c1
> > config_attach_loc(0,c09f3db8,0,0,0) at netbsd:config_attach_loc+0x156
> > config_attach(0,c09f3db8,0,0,c0b8f010) at netbsd:config_attach+0x2c
> > config_rootfound(c093d799,0,c0b92c28,c0480ebf,c0a020a0) at netbsd:config_rootfou
> > nd+0x44    
> > cpu_configure(c0a020a0,a,0,0,c0aa44f0) at netbsd:cpu_configure+0x27
> > configure(c0aa0d80,1,0,0,ffff) at netbsd:configure+0x2f
> > main(fbff,c01002d2,0,0,0) at netbsd:main+0x115
> 
(Continue reading)

Henry R. Bent | 13 Apr 00:20 2007
Picon

Darwin emulation?

Hi all,

Does Darwin emulation work on i386?  I have COMPAT_MACH, COMPAT_DARWIN, 
and EXEC_MACHO turned on but it looks like binaries aren't even trying 
to run.  I have emulators/darwin_lib installed and have verified that it 
is universal.  Yet when I try to run /bin/ls from an OS X 10.4.9 intel 
machine:

aelfric% ./ls
./ls: Exec format error. Binary file not executable.

ktrace is no help, because it never even tries running the binary as 
anything but netbsd and a shell script:

aelfric% ktrace ./ls
./ls: 9: Syntax error: ";" unexpected
aelfric% kdump
  28017      1 ktrace   EMUL  "netbsd"
  28017      1 ktrace   CALL  execve(0xbfbfedeb,0xbfbfed14,0xbfbfed1c)
  28017      1 ktrace   NAMI  "./ls"
  28017      1 ktrace   RET   execve -1 errno 8 Exec format error
  28017      1 ktrace   CALL  execve(0xbbbc77f0,0xbfbfe800,0xbfbfed1c)
  28017      1 ktrace   NAMI  "/bin/sh"

Am I missing some extra setup, or is this not going to work?

-Henry Bent

Jason Thorpe | 13 Apr 01:55 2007

Re: Darwin emulation?


On Apr 12, 2007, at 3:20 PM, Henry R. Bent wrote:

> Hi all,
>
> Does Darwin emulation work on i386?  I have COMPAT_MACH,  
> COMPAT_DARWIN, and EXEC_MACHO turned on but it looks like binaries  
> aren't even trying to run.  I have emulators/darwin_lib installed  
> and have verified that it is universal.  Yet when I try to run /bin/ 
> ls from an OS X 10.4.9 intel machine:
>
> aelfric% ./ls
> ./ls: Exec format error. Binary file not executable.

Our Darwin compat code hasn't been worked on in quite some time, and  
I'm almost certain it has not been updated for OS X on Intel.

>
>
> ktrace is no help, because it never even tries running the binary as  
> anything but netbsd and a shell script:
>
> aelfric% ktrace ./ls
> ./ls: 9: Syntax error: ";" unexpected
> aelfric% kdump
> 28017      1 ktrace   EMUL  "netbsd"
> 28017      1 ktrace   CALL  execve(0xbfbfedeb,0xbfbfed14,0xbfbfed1c)
> 28017      1 ktrace   NAMI  "./ls"
> 28017      1 ktrace   RET   execve -1 errno 8 Exec format error
> 28017      1 ktrace   CALL  execve(0xbbbc77f0,0xbfbfe800,0xbfbfed1c)
(Continue reading)


Gmane