Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

freebsd-questions Digest, Vol 305, Issue 11

5 views

Skip to first unread message

freebsd-ques...@freebsd.org

unread,

Apr 10, 2010, 2:27:24 AM4/10/10

to freebsd-...@freebsd.org

Send freebsd-questions mailing list submissions to
freebsd-...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
or, via email, send a message with subject or body 'help' to
freebsd-ques...@freebsd.org

You can reach the person managing the list at
freebsd-que...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-questions digest..."

Today's Topics:

1. Re: Kernel Config for NAT (Robert Huff)
2. Re: Adding a Disk and Changing Mountpoints
(Programmer In Training)
3. Re: USB Powered Speakers (Programmer In Training)
4. Re: USB Powered Speakers (Programmer In Training)
5. Re: Adding a Disk and Changing Mountpoints (Polytropon)
6. Re: USB Powered Speakers (Programmer In Training)
7. sendmail && /etc/resolv.conf modified by DHCP (Matthias Apitz)
8. Re: perl qstn... (Alejandro Imass)
9. Re: Kernel Config for NAT (Ian Smith)
10. Re: USB Powered Speakers (Programmer In Training)
11. wdm doesn't start windowing manager. (Neil Short)
12. Re: RootBSD? (Garance A Drosehn)
13. Re: wdm doesn't start windowing manager. (Adam Vande More)
14. Re: USB Powered Speakers (Warren Block)
15. Re: USB Powered Speakers (Programmer In Training)
16. perl links (Aiza)
17. Re: perl links (Chuck Swiger)
18. Re: perl links (Erik Trulsson)
19. Re: USB Powered Speakers (Chris Whitehouse)
20. Re: USB Powered Speakers (Programmer In Training)
21. LSI MegaRAID SAS 9211-8i on FreeBSD 8/9? (O. Hartmann)
22. Re: USB Powered Speakers (mikel king)
23. Re: USB Powered Speakers (Programmer In Training)
24. Re: Kernel Config for NAT (per...@pluto.rain.com)
25. Re: USB Powered Speakers (per...@pluto.rain.com)
26. Re: USB Powered Speakers (Programmer In Training)
27. Custom kernel & atheros (harvey dent)

----------------------------------------------------------------------

Message: 1
Date: Fri, 9 Apr 2010 08:34:45 -0400
From: Robert Huff <rober...@rcn.com>
Subject: Re: Kernel Config for NAT
To: Ian Smith <smi...@nimnet.asn.au>
Cc: Adam Vande More <amvan...@gmail.com>, Robert Huff
<rober...@rcn.com>, freebsd-...@freebsd.org
Message-ID: <19391.7909.8...@jerusalem.litteratus.org>
Content-Type: text/plain; charset=us-ascii

Ian Smith writes:

> > So ... double-checking I'm doing this right:
> >
> > 1) in /boot/loader.conf:
> >
> > ipfw_load="YES"
> > ipdivert_load="YES"
>
> I thought from your earlier mail that you wanted to use in-kernel
> NAT?

I want whatever works. :-)
Beyond that ... all other things being more-or-less equal I'll
do this with modules.
Let's build that. So in /etc/sysctl.conf:

net.inet.ip.fw.default_to_accept="1"
net.inet.ip.fw.verbose="1"
net.inet.ip.fw.verbose_limit="100"

check.

> I believe all these can be accomplished with modules on GENERIC
> kernel, at least on 8.x, with the exception of FIREWALL_FORWARD
> functionality which does require a custom kernel as it messes
> with lots of ip paths.

This machine has a custom kernel, so that's not a an issue.
And in /boot/loader.conf:

ipfw_load="YES"
ipfw_nat="YES" # in-kernel ipfw nat
libalias="YES" # for in-kernel ipfw nat

check.
and in the kernel config:

#options IPFIREWALL #firewall
#options IPFIREWALL_VERBOSE #enable logging to syslogd(8)

options IPFIREWALL_FORWARD

#options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity
#options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default
#options IPDIVERT
#options IPFIREWALL_NAT #ipfw kernel nat support
#options LIBALIAS # required for NAT

check.
This combination will get me a) ipfw, using the standard
rc.conf "firewall_" variables, and b) NAT ... do I still need to
have a "nat" setting in the firewall rules?

Less confused than last time,

Robert Huff

------------------------------

Message: 2
Date: Fri, 09 Apr 2010 07:44:34 -0500
From: Programmer In Training <p...@joseph-a-nagy-jr.us>
Subject: Re: Adding a Disk and Changing Mountpoints
To: freebsd-...@freebsd.org
Message-ID: <4BBF2132...@joseph-a-nagy-jr.us>
Content-Type: text/plain; charset="utf-8"

On 04/09/10 00:48, Polytropon wrote:
> On Thu, 08 Apr 2010 17:38:03 -0500, Programmer In Training <p...@joseph-a-nagy-jr.us> wrote:
>> Saturday I'll be adding a second 40GB and a tertiary 6GB disk to the
>> system (in favor of adding a CD-RW to a system that already has a DVD
>> super multi-format drive). I'd like to rearrange my mount points a bit.
>
> Here we go. :-)
<snip>

Thank you for the detailed response. Without knowing any of that, I
would have totally messed up. I'll be printing out the email so I have
it handy on Saturday.

Again, thank you!
--
Yours In Christ,

PIT
Emails are not formal business letters, whatever businesses may want.
Original content copyright under the OWL http://owl.apotheon.org
Please do not CC me. If I'm posting to a list it is because I am subscribed.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20100409/69398908/signature-0001.pgp

------------------------------

Message: 3
Date: Fri, 09 Apr 2010 07:56:45 -0500
From: Programmer In Training <p...@joseph-a-nagy-jr.us>
Subject: Re: USB Powered Speakers
To: freebsd-...@freebsd.org
Message-ID: <4BBF240D...@joseph-a-nagy-jr.us>
Content-Type: text/plain; charset="utf-8"

On 04/09/10 02:17, Fbsd1 wrote:
> Antonio Olivares wrote:
>> On 4/8/10, Programmer In Training <p...@joseph-a-nagy-jr.us> wrote:
>>> I have acquired a pair of Compaq USB /powered/ speakers. On my parents
>>> XP machine they don't seem to cause any problems, but when I hook it up
>>> to listen on my FreeBSD box I have absolutely nothing but problems with
>>> the speakers (even when turned off but still plugged in) interrupting
>>> the normal operation of my keyboard (basically it seems that power is
>>> cut to my keyboard at random). I have a beefy power supply (650W) so I
>>> really shouldn't be having any power distribution issues.
>>>
>>> I've tried the speakers in both the on-board USB ports and the USB
>>> expansion card (PCI) with the same results.
>>>
>>> Any ideas?
>
> You really need to explain in detail the problem.

That's as much detail, except for the question below, that I have.

> Without these new speakers plugged in does wall powered speakers work?

Yeah, normal wall speakers work, but I gave those to my mom since these
speakers, even at full blast, only put out a tiny sound on her computer
(normal volume on mine).

--
Yours In Christ,

------------------------------

Message: 4
Date: Fri, 09 Apr 2010 07:58:05 -0500
From: Programmer In Training <p...@joseph-a-nagy-jr.us>
Subject: Re: USB Powered Speakers
To: freebsd-...@freebsd.org
Message-ID: <4BBF245...@joseph-a-nagy-jr.us>
Content-Type: text/plain; charset="utf-8"

On 04/09/10 02:51, per...@pluto.rain.com wrote:
> Programmer In Training <p...@joseph-a-nagy-jr.us> wrote:
>
>> ... they are only attached for power purposes ...
>
>> Input power: DC 5V 500mA
>
> Any chance these speakers need a USB 2.0 port, and all the ports

The expansion card is 2.0

> on your FreeBSD box are 1.x? I don't remember the USB power spec
> offhand, but 2.5W may exceed what a USB 1.x port can supply --
> a limit that applies regardless of the system's overall power
> provisioning.

That would explain why the sound was so small on my parents computer.
All they have is 1.x
--
Yours In Christ,

------------------------------

Message: 5
Date: Fri, 9 Apr 2010 15:01:12 +0200
From: Polytropon <fre...@edvax.de>
Subject: Re: Adding a Disk and Changing Mountpoints
To: Programmer In Training <p...@joseph-a-nagy-jr.us>
Cc: freebsd-...@freebsd.org
Message-ID: <20100409150112....@edvax.de>
Content-Type: text/plain; charset=US-ASCII

On Fri, 09 Apr 2010 07:44:34 -0500, Programmer In Training <p...@joseph-a-nagy-jr.us> wrote:
> Thank you for the detailed response. Without knowing any of that, I
> would have totally messed up. I'll be printing out the email so I have
> it handy on Saturday.

I made a mistake. Please check and correct this in your
hardcopy. In the example for copying the home directories,
I wrote:

# mount -o ro /dev/ad0s1f /usr
# mount -o ro /dev/ad2s1e /home

The second -o ro is wrong, has to be -o rw, because
you're writing to this partition in the next step:

# mount -o ro /dev/ad0s1f /usr
# mount -o rw /dev/ad2s1e /home

The basic idea is to work with least dangerous
permissions, so if you're going to read files from
a partition, -o ro is sufficient. But of course it's
not sufficient for writing. :-)

And for the final /etc/fstab, this is wrong:

/dev/ad0s1d /tmp ufs rw 2 2
/dev/ad0s1e /scratch ufs rw 2 2

It would have to be:

/dev/ad0s1d /scratch ufs rw 2 2
/dev/ad0s1e /tmp ufs rw 2 2

becausse /dev/ad0s1d previously was /var.

In any case, as you're working with maximum privileges
on file systems, pay attention to device names and
directories. Triple-check them. Always.

--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

------------------------------

Message: 6
Date: Fri, 09 Apr 2010 08:07:00 -0500
From: Programmer In Training <p...@joseph-a-nagy-jr.us>
Subject: Re: USB Powered Speakers
To: freebsd-...@freebsd.org
Message-ID: <4BBF2674...@joseph-a-nagy-jr.us>
Content-Type: text/plain; charset="utf-8"

On 04/09/10 06:25, Warren Block wrote:
> On Fri, 9 Apr 2010, per...@pluto.rain.com wrote:
>
>> Programmer In Training <p...@joseph-a-nagy-jr.us> wrote:
>>
>>> ... they are only attached for power purposes ...
>>
>>> Input power: DC 5V 500mA
>>
>> Any chance these speakers need a USB 2.0 port, and all the ports
>> on your FreeBSD box are 1.x? I don't remember the USB power spec
>> offhand, but 2.5W may exceed what a USB 1.x port can supply --
>> a limit that applies regardless of the system's overall power
>> provisioning.
>
> 500 mA is 5 unit loads for USB 2.0, or powered hub territory. The
> device has to request that high power mode, and the system can say no
> and disable the port. That should show in /var/log/messages.
<snip>

The following messages so far haven't shown up today.

Apr 8 22:30:01 heaven root: Unknown USB device: vendor 0x046e product
0x5542 bus uhub4
Apr 8 22:30:01 heaven kernel: uhid0: <vendor 0x046e product 0x5542,
class 0/0, rev 1.10/1.10, addr 3> on usbus4
Apr 8 22:30:01 heaven kernel: uhub_explore:611: illegal enable change,
port 3
Apr 8 22:30:15 heaven kernel: ugen4.3: <vendor 0x046e> at usbus4
(disconnected)
Apr 8 22:30:15 heaven kernel: ukbd0: at uhub4, port 3, addr 3
(disconnected)
Apr 8 22:30:15 heaven kernel: uhid0: at uhub4, port 3, addr 3
(disconnected)
Apr 8 22:30:16 heaven kernel: usb_alloc_device:1586: set address 3
failed (USB_ERR_IOERROR, ignored)
Apr 8 22:30:16 heaven kernel: usb_alloc_device:1624: getting device
descriptor at addr 3 failed, USB_ERR_IOERROR!

--
Yours In Christ,

------------------------------

Message: 7
Date: Fri, 9 Apr 2010 15:26:46 +0200
From: Matthias Apitz <gu...@unixarea.de>
Subject: sendmail && /etc/resolv.conf modified by DHCP
To: freebsd-...@freebsd.org
Message-ID: <20100409132...@current.Sisis.de>
Content-Type: text/plain; charset=iso-8859-1

Hello,

At home I have my WLAN as 192.168.2.0/24. After moving to my office and
rebooting there, I encounter that sendmail receives messages (via
fetchmail) terrible slow. I digged into this and see that the sendmail
issues wrong DNS requests as (for example):

08:51:18.753491 IP xx.xx.xx.xx.49812 > 192.168.2.1.53: 12793+ MX? ubuntu.com.Sisis.de. (37)
08:51:18.867365 IP xx.xx.xx.xx.42619 > 192.168.2.1.53: 12793+ MX? physik.uni-wuerzburg.de.Sisis.de. (50)
08:51:18.982491 IP xx.xx.xx.xx.52554 > 192.168.2.1.53: 12794+ AAAA? lexasoft.ru. (29)
08:51:19.095490 IP xx.xx.xx.xx.10093 > 192.168.2.1.53: 12794+ AAAA? des.no. (24)

The reason is obvious:
- the /etc/resolv.conf on shutdown at home has this DNS resolver;
- in my office the system comes up and when at some point the WLAN
interface associates, it gets an IP and a new /etc/resolv.conf file;

Why sendmail does not honour the new /etc/resolv.conf and stays with the
old DNS server IP? How this is supposed to fix? An idea would be to
restart sendmail via a devd hook, but maybe there is some config values
for sendmail that it always check /etc/resolv.conf for fresh?

Thx

matthias

--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <gu...@unixarea.de> - w http://www.unixarea.de/
¡Ya basta! ¡Tropas de OTAN, fuera de Afghanistan!
There's an end of it! NATO troups out of Afghanistan!
Schluss jetzt endlich! NATO raus aus Afghanistan!

------------------------------

Message: 8
Date: Fri, 9 Apr 2010 10:38:14 -0400
From: Alejandro Imass <a...@p2ee.org>
Subject: Re: perl qstn...
To: "Randal L. Schwartz" <mer...@stonehenge.com>
Cc: gla...@freebsd.org, kl...@thought.org, FreeBSD Mailing List
<freebsd-...@freebsd.org>
Message-ID:
<o2ra14066a01004090738mb...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Apr 9, 2010 at 5:56 AM, Randal L. Schwartz
<mer...@stonehenge.com> wrote:
>>>>>> "Alejandro" == Alejandro Imass <a...@p2ee.org> writes:
>
> Alejandro> did you mean unless? ;-)
>
> Did you read this:
>
>>> Augh. I hit send just as I realized that's backwards. Need
>>> more caffiene. Swap the true and false blocks there. :)
>

Yeah, but _after_ I had pressed send .
That sparked the comment that unless was a bad idea in C and then all
helll broke loose <lol>

> --
> Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
> <mer...@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
> See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
>

------------------------------

Message: 9
Date: Sat, 10 Apr 2010 01:07:32 +1000 (EST)
From: Ian Smith <smi...@nimnet.asn.au>
Subject: Re: Kernel Config for NAT
To: Robert Huff <rober...@rcn.com>
Cc: Adam Vande More <amvan...@gmail.com>,
freebsd-...@freebsd.org
Message-ID: <2010040923...@sola.nimnet.asn.au>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 9 Apr 2010, Robert Huff wrote:
> Ian Smith writes:
>
> > > So ... double-checking I'm doing this right:
> > >
> > > 1) in /boot/loader.conf:
> > >
> > > ipfw_load="YES"
> > > ipdivert_load="YES"
> >
> > I thought from your earlier mail that you wanted to use in-kernel
> > NAT?
>
> I want whatever works. :-)

natd works, as ever. ipfw nat is reputed to work faster.

> Beyond that ... all other things being more-or-less equal I'll
> do this with modules.
> Let's build that. So in /etc/sysctl.conf:
>
> net.inet.ip.fw.default_to_accept="1"
> net.inet.ip.fw.verbose="1"
> net.inet.ip.fw.verbose_limit="100"
>
> check.
>
> > I believe all these can be accomplished with modules on GENERIC
> > kernel, at least on 8.x, with the exception of FIREWALL_FORWARD
> > functionality which does require a custom kernel as it messes
> > with lots of ip paths.
>
> This machine has a custom kernel, so that's not a an issue.
> And in /boot/loader.conf:
>
> ipfw_load="YES"
> ipfw_nat="YES" # in-kernel ipfw nat
> libalias="YES" # for in-kernel ipfw nat

ipfw_nat_load="YES"
libalias_load="YES"

> check.
> and in the kernel config:
>
> #options IPFIREWALL #firewall
> #options IPFIREWALL_VERBOSE #enable logging to syslogd(8)
>
> options IPFIREWALL_FORWARD

Planning on using any 'fwd' rules?

> #options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity
> #options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default
> #options IPDIVERT
> #options IPFIREWALL_NAT #ipfw kernel nat support
> #options LIBALIAS # required for NAT
>
> check.
> This combination will get me a) ipfw, using the standard
> rc.conf "firewall_" variables, and b) NAT ... do I still need to
> have a "nat" setting in the firewall rules?

The 'client' ruleset now has rules for either natd or ipfw nat. The
'simple' ruleset works with natd (from natd_enable and natd_interface in
rc.conf), but still lacks the patch for ipfw nat - my remiss for seeking
comment in ipfw@ rather than sending it with a PR, as one should.

Time I redid it, you can be guinea pig :) What freebsd version?

cheers, Ian

------------------------------

Message: 10
Date: Fri, 09 Apr 2010 13:31:25 -0500
From: Programmer In Training <p...@joseph-a-nagy-jr.us>
Subject: Re: USB Powered Speakers
To: FreeBSD Questions <freebsd-...@freebsd.org>
Message-ID: <4BBF727D...@joseph-a-nagy-jr.us>
Content-Type: text/plain; charset="iso-8859-1"

On 04/09/10 10:15, Brodey Dover wrote:
> "Apr 8 22:30:16 heaven kernel: usb_alloc_device:1624: getting device
> descriptor at addr 3 failed, USB_ERR_IOERROR!"
>
> exactly! That is what is causing the issues. From what I can see, it
> is like it was explained before. The OS has chosen to play nice and
> request that the speakers are disabled.
>
> The power requirements will not affect the system until the speakers
> are producing sound. In other words, the system will only draw UP to
> the power input rating while in operation. At idle, I'd wager they may
> only use 1/10 of its power rating for the idle ICs and a power LED.
<snip>

Only it's not the speakers that have their operation interrupted, JUST
the keyboard (not even the mouse is affected).

--
Yours In Christ,

------------------------------

Message: 11
Date: Fri, 9 Apr 2010 11:17:42 -0700 (PDT)
From: Neil Short <nes...@yahoo.com>
Subject: wdm doesn't start windowing manager.
To: freebsd-...@freebsd.org
Message-ID: <811305....@web56502.mail.re3.yahoo.com>
Content-Type: text/plain; charset=us-ascii

Has anybody had this problem and fixed it?
wdm runs my ~/.xsession file; but no X-applications run. It just runs past them and returns to the wdm login screen.

Currently I am running xdm; but it's kind of bland and spicing it up requires a very steep learning curve.
======

"What did you do?" the man holding the flashlight asked.

"I put down a spider," he said, wondering why the man didn't see; in the beam of yellow light the spider bloated up larger than life. "So it could get away."

------------------------------

Message: 12
Date: Fri, 9 Apr 2010 14:34:53 -0400
From: Garance A Drosehn <g...@FreeBSD.org>
Subject: Re: RootBSD?
To: Tom Ierna <t...@shockergroup.com>, freebsd-questions
<freebsd-...@FreeBSD.org>
Message-ID: <p06240800c7e522c2458c@[128.113.24.47]>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

At 9:04 AM -0400 4/6/10, Tom Ierna wrote:
>Hi,
>
>Anyone have any experience with RootBSD.net?
>
>I'm looking to move an office-hosted machine's services to the
>cloud, and they seem to be one of the only VPS companies centered
>around BSD support instead of Linux.

I've been using them for a few years now. What I have with them is a
system which is meant to be used as a "hot backup" for a system which
is here in my office. So, the main things I wanted was (1) real
freebsd systems, (2) which were someplace far away from Troy NY. I
wanted to be pretty sure that any problem which took out my main
system would NOT take out my "hot backup" system!

I've had absolutely no trouble with them. The few times that I've
had to contact them, they've been happy to provide whatever help I
needed. On the other hand, my main system has been working fine for
almost three years now, so this backup system that I have at
rootbsd.net has not seen much activity. I just rsync the main system
to the backup system once a day, and then every few months I upgrade
the FreeBSD that I'm running on the system at rootbsd.net.

--
Garance Alistair Drosehn = dro...@rpi.edu
Senior Systems Programmer or g...@FreeBSD.org
Rensselaer Polytechnic Institute; Troy, NY; USA

------------------------------

Message: 13
Date: Fri, 9 Apr 2010 14:57:43 -0500
From: Adam Vande More <amvan...@gmail.com>
Subject: Re: wdm doesn't start windowing manager.
To: Neil Short <nes...@yahoo.com>
Cc: freebsd-...@freebsd.org
Message-ID:
<g2h6201873e1004091257hb...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Apr 9, 2010 at 1:17 PM, Neil Short <nes...@yahoo.com> wrote:

> Has anybody had this problem and fixed it?
> wdm runs my ~/.xsession file; but no X-applications run. It just runs past
> them and returns to the wdm login screen.
>
> Currently I am running xdm; but it's kind of bland and spicing it up
> requires a very steep learning curve.
>

I've had issue with desktop environment in the past with similar behavior.
Usually for me is was a permissions problem, but you should be able to turn
up logging verbosity to figure out where your specific issue is.

--
Adam Vande More

------------------------------

Message: 14
Date: Fri, 9 Apr 2010 14:24:05 -0600 (MDT)
From: Warren Block <wbl...@wonkity.com>
Subject: Re: USB Powered Speakers
To: FreeBSD Questions <freebsd-...@freebsd.org>
Message-ID: <alpine.BSF.2.00.1...@wonkity.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Fri, 9 Apr 2010, Programmer In Training wrote:

> On 04/09/10 10:15, Brodey Dover wrote:
>> "Apr 8 22:30:16 heaven kernel: usb_alloc_device:1624: getting device
>> descriptor at addr 3 failed, USB_ERR_IOERROR!"
>>
>> exactly! That is what is causing the issues. From what I can see, it
>> is like it was explained before. The OS has chosen to play nice and
>> request that the speakers are disabled.
>>
>> The power requirements will not affect the system until the speakers
>> are producing sound. In other words, the system will only draw UP to
>> the power input rating while in operation. At idle, I'd wager they may
>> only use 1/10 of its power rating for the idle ICs and a power LED.

Just to add:

When you plug in a USB device, it is a "low power" device (single unit
load, 100 mA) by default.

If that device wants to draw more power, it has to request high power (5
unit loads) from the hub. The hub can provide that power, or shut down
the port.

> Only it's not the speakers that have their operation interrupted, JUST
> the keyboard (not even the mouse is affected).

Guesses:

Total power budget (but FIFO?).
Speaker/keyboard USB ports are on the same internal hub.
High-power OLED keyboard (my eyes!).
Speakers labelled 500 mA but really only a low-power USB device.

-Warren Block * Rapid City, South Dakota USA

------------------------------

Message: 15
Date: Fri, 09 Apr 2010 15:54:00 -0500
From: Programmer In Training <p...@joseph-a-nagy-jr.us>
Subject: Re: USB Powered Speakers
To: freebsd-...@freebsd.org
Message-ID: <4BBF93E8...@joseph-a-nagy-jr.us>
Content-Type: text/plain; charset="iso-8859-1"

On 04/09/10 15:24, Warren Block wrote:
> On Fri, 9 Apr 2010, Programmer In Training wrote:
>
>> On 04/09/10 10:15, Brodey Dover wrote:
>>> "Apr 8 22:30:16 heaven kernel: usb_alloc_device:1624: getting device
>>> descriptor at addr 3 failed, USB_ERR_IOERROR!"
>>>
>>> exactly! That is what is causing the issues. From what I can see, it
>>> is like it was explained before. The OS has chosen to play nice and
>>> request that the speakers are disabled.
>>>
>>> The power requirements will not affect the system until the speakers
>>> are producing sound. In other words, the system will only draw UP to
>>> the power input rating while in operation. At idle, I'd wager they may
>>> only use 1/10 of its power rating for the idle ICs and a power LED.
>
> Just to add:
>
> When you plug in a USB device, it is a "low power" device (single unit
> load, 100 mA) by default.
>
> If that device wants to draw more power, it has to request high power (5
> unit loads) from the hub. The hub can provide that power, or shut down
> the port.

I never knew that about USB ports.

>> Only it's not the speakers that have their operation interrupted, JUST
>> the keyboard (not even the mouse is affected).
>
> Guesses:
>
> Total power budget (but FIFO?).

I don't get that. Do you mean total power allocated to USB?

> Speaker/keyboard USB ports are on the same internal hub.

I'm not sure what you mean here. I've put the speakers on the internal,
builtin USB ports (1.x) and they work fine except keyboard starts
flaking out. I put them on the USB expansion card (which mouse and
keyboard are on because they were starting to flake out on the builtins)
with the same exact behavior.

> High-power OLED keyboard (my eyes!).

Keyboard label (if it is to be believed) is +5V 100mA. It's just a
standard keyboard with some extra multimedia keys that aren't active (a
pity, too).

> Speakers labelled 500 mA but really only a low-power USB device.

Than they shouldn't be messing with the keyboard, right?

It usually takes about an hour or so for the keyboard to settle down to
a usable state (until then, I'm doing a lot of mousing as the keyboard
is near useless).

I really don't know where to look for this. I've never even heard of USB
powered speakers until I got these (no, I don't pay much attention to
what's available unless I have a great need for it). I'm thinking I'm
just going to wait until Tuesday and get a brand new pair of
wall-powered speakers. This hassle is NOT worth it (they put out decent
sound).

--
Yours In Christ,

------------------------------

Message: 16
Date: Sat, 10 Apr 2010 07:14:48 +0800
From: Aiza <aiz...@comclark.com>
Subject: perl links
To: FreeBSD Questions <freebsd-...@freebsd.org>
Message-ID: <4BBFB4E8...@comclark.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

When installing perl i see 2 links between /usr/local/bin and /usr/bin.
Is this still required or is it something left over from when perl was
part of the base system?

symlinking /usr/local/bin/perl5.8.9 and /usr/bin/perl
symlinking /usr/local/bin/perl5.8.9 and /usr/bin/perl5

------------------------------

Message: 17
Date: Fri, 09 Apr 2010 16:22:49 -0700
From: Chuck Swiger <csw...@mac.com>
Subject: Re: perl links
To: Aiza <aiz...@comclark.com>
Cc: FreeBSD Questions <freebsd-...@freebsd.org>
Message-ID: <9FBA659F-FB72-493D...@mac.com>
Content-Type: text/plain; charset=us-ascii

On Apr 9, 2010, at 4:14 PM, Aiza wrote:
> When installing perl i see 2 links between /usr/local/bin and /usr/bin. Is this still required or is it something left over from when perl was part of the base system?
>
> symlinking /usr/local/bin/perl5.8.9 and /usr/bin/perl
> symlinking /usr/local/bin/perl5.8.9 and /usr/bin/perl5

This is to compensate for Perl scripts which assume they know where the path to the interpreter is, rather than using env....

Regards,
--
-Chuck

------------------------------

Message: 18
Date: Sat, 10 Apr 2010 01:28:24 +0200
From: Erik Trulsson <ertr...@student.uu.se>
Subject: Re: perl links
To: Aiza <aiz...@comclark.com>
Cc: FreeBSD Questions <freebsd-...@freebsd.org>
Message-ID: <20100409232...@owl.midgard.homeip.net>
Content-Type: text/plain; charset=us-ascii

On Sat, Apr 10, 2010 at 07:14:48AM +0800, Aiza wrote:
> When installing perl i see 2 links between /usr/local/bin and /usr/bin.
> Is this still required or is it something left over from when perl was
> part of the base system?
>
> symlinking /usr/local/bin/perl5.8.9 and /usr/bin/perl
> symlinking /usr/local/bin/perl5.8.9 and /usr/bin/perl5

It is still required (at least the first one.) It is there to be
compatible with a very large number of existing Perl scripts which
assume that the Perl interpreter can be found as /usr/bin/perl

This has nothing do to with when Perl was part of the base system - it
is a Perl convention which was established before FreeBSD (or Linux for
that matter) even existed.

--
<Insert your favourite quote here.>
Erik Trulsson
ertr...@student.uu.se

------------------------------

Message: 19
Date: Sat, 10 Apr 2010 00:31:31 +0100
From: Chris Whitehouse <cwh...@onetel.com>
Subject: Re: USB Powered Speakers
To: Programmer In Training <p...@joseph-a-nagy-jr.us>
Cc: freebsd-...@freebsd.org
Message-ID: <4BBFB8D3...@onetel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Programmer In Training wrote:
>
> I really don't know where to look for this. I've never even heard of USB
> powered speakers until I got these (no, I don't pay much attention to
> what's available unless I have a great need for it). I'm thinking I'm
> just going to wait until Tuesday and get a brand new pair of
> wall-powered speakers. This hassle is NOT worth it (they put out decent
> sound).
>

Unless you insist on an operating system solution what you are really
after is a 5 volt supply. What about buying a mains USB charger of the
right capacity, or if you are handy with bits of wire have a look
through all those old power supplies for a 5 volt one? Or even use the 5
volt supply from inside your computer (if it is a desktop not laptop)

Chris

------------------------------

Message: 20
Date: Fri, 09 Apr 2010 18:41:25 -0500
From: Programmer In Training <p...@joseph-a-nagy-jr.us>
Subject: Re: USB Powered Speakers
To: freebsd-...@freebsd.org
Message-ID: <4BBFBB25...@joseph-a-nagy-jr.us>
Content-Type: text/plain; charset="iso-8859-1"

On 04/09/10 18:31, Chris Whitehouse wrote:
<snip>
> Unless you insist on an operating system solution what you are really
> after is a 5 volt supply. What about buying a mains USB charger of the
> right capacity, or if you are handy with bits of wire have a look

I wouldn't know where to look for one.

> through all those old power supplies for a 5 volt one? Or even use the 5
> volt supply from inside your computer (if it is a desktop not laptop)
>
> Chris

It is a desktop. There is a 5V supply in there?!

--
Yours In Christ,

------------------------------

Message: 21
Date: Sat, 10 Apr 2010 02:40:34 +0200
From: "O. Hartmann" <ohar...@mail.zedat.fu-berlin.de>
Subject: LSI MegaRAID SAS 9211-8i on FreeBSD 8/9?
To: freebsd-...@freebsd.org, freebsd...@FreeBSD.org
Message-ID: <4BBFC902...@mail.zedat.fu-berlin.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed

I'd like to build a new Workstation based on Intels 'Gulftown' for some
numerical modelling purposes. Since I realised that on our Dell
Poweredge Server with built-in Fusion MPT RAID/JBOD controller even
attached SATA 3 GB hard disks seem to be 'faster' than on most Intel
ICH9/ICH10 machines we also utilise with FreeBSD 8/amd64, I'd like to
have a replacement SAS 2.0 controller like the LSI MegaRAID SAS 9211-8.
I do not know much about this controller. I don't want to wait for
native SATA 6Gb on Intel chipsets since this is announce for next year
and I feel better being 'back to the roots' with SCSI/SAS 2 on FreeBSD.

Are there any contraints on this above mentioned LSI SAS 2.0 controller
execpt lacking RAID 5/6 level (it should be an replacement for the ICH10
so far for 7 or 8 hard disks/SSDs)?

Any comment would be appreciated (please set CC to my email since I do
not subscribe the questions-list).

Thanks in advance,

O. Hartmann

------------------------------

Message: 22
Date: Fri, 9 Apr 2010 20:58:22 -0400
From: mikel king <mikel...@olivent.com>
Subject: Re: USB Powered Speakers
To: Programmer In Training <p...@joseph-a-nagy-jr.us>
Cc: freebsd-...@freebsd.org
Message-ID: <D94BD482-09CE-4728...@olivent.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes

On Apr 9, 2010, at 7:41 PM, Programmer In Training wrote:

> On 04/09/10 18:31, Chris Whitehouse wrote:
> <snip>
>> Unless you insist on an operating system solution what you are really
>> after is a 5 volt supply. What about buying a mains USB charger of
>> the
>> right capacity, or if you are handy with bits of wire have a look
>
> I wouldn't know where to look for one.
>
>> through all those old power supplies for a 5 volt one? Or even use
>> the 5
>> volt supply from inside your computer (if it is a desktop not laptop)
>>
>> Chris
>
> It is a desktop. There is a 5V supply in there?!
>
> --
> Yours In Christ,

Out of curiosity, have you tried an active USB 2.0 HUB to buffer the
speakers from the computer's USB ports? Or even a AC to USB adapter?

Regards,
Mikel King
CEO, Olivent Technologies
Senior Editor, BSD News Network
Columnist, BSD Magazine
skype:mikel.king
http://olivent.com
http://www.linkedin.com/in/mikelking
http://twitter.com/mikelking

------------------------------

Message: 23
Date: Fri, 09 Apr 2010 20:01:53 -0500
From: Programmer In Training <p...@joseph-a-nagy-jr.us>
Subject: Re: USB Powered Speakers
To: freebsd-...@freebsd.org
Message-ID: <4BBFCE01...@joseph-a-nagy-jr.us>
Content-Type: text/plain; charset="iso-8859-1"

On 04/09/10 19:58, mikel king wrote:
<snip>
> Out of curiosity, have you tried an active USB 2.0 HUB to buffer the
> speakers from the computer's USB ports? Or even a AC to USB adapter?
<snip>

I don't have one of either of those items. I only have a passive 2.0 HUB
(at least I think it's 2.0). Either way, looks as if there is a trip to
the store and/or the website for my mobo manufacturer and a trip into
the shed to find my EET books.

--
Yours In Christ,

------------------------------

Message: 24
Date: Fri, 09 Apr 2010 18:59:45 -0700
From: per...@pluto.rain.com
Subject: Re: Kernel Config for NAT
To: smi...@nimnet.asn.au
Cc: freebsd-...@freebsd.org
Message-ID: <4bbfdb91.TJ1v3uRXSquSIsC4%per...@pluto.rain.com>
Content-Type: text/plain; charset=us-ascii

Ian Smith <smi...@nimnet.asn.au> wrote:
> > > http://www.freebsd.org/doc/handbook/firewalls-ipfw.html
> <rant>
> This is absolutely the worst section of an otherwise great
> handbook ... Nothing short of a rewrite from scratch could
> fix it ...

As always, I'm sure a patch -- to provide that rewrite --
would be welcome.

------------------------------

Message: 25
Date: Fri, 09 Apr 2010 19:04:29 -0700
From: per...@pluto.rain.com
Subject: Re: USB Powered Speakers
To: freebsd-...@freebsd.org
Message-ID: <4bbfdcad.W6JoDlxI393oub38%per...@pluto.rain.com>
Content-Type: text/plain; charset=us-ascii

Programmer In Training <p...@joseph-a-nagy-jr.us> wrote:

> I'm thinking I'm just going to wait until Tuesday and get a brand
> new pair of wall-powered speakers. This hassle is NOT worth it ...

If "speakers on USB 2.0 card, all else on 1.x builtins" doesn't
work, you might want to try a power adapter that has a USB host
connector. (I've seen such at Fry's, intended for devices like
iPods that were designed to recharge their internal batteries
from a USB port.) This would effectively convert your current
set to wall-powered, which might be less costly than a new set.

WRT the suggestion to hack something together, I wouldn't suggest
attempting it unless you're quite sure of what would be involved.
It wouldn't be exactly difficult, but getting something backwards
-- or connecting to the +12 instead of the +5 supply -- would at
least let all the magic blue smoke out of the speakers :)

------------------------------

Message: 26
Date: Fri, 09 Apr 2010 21:26:25 -0500
From: Programmer In Training <p...@joseph-a-nagy-jr.us>
Subject: Re: USB Powered Speakers
To: freebsd-...@freebsd.org
Message-ID: <4BBFE1D1...@joseph-a-nagy-jr.us>
Content-Type: text/plain; charset="iso-8859-1"

On 04/09/10 21:04, per...@pluto.rain.com wrote:
> Programmer In Training <p...@joseph-a-nagy-jr.us> wrote:
>
>> I'm thinking I'm just going to wait until Tuesday and get a brand
>> new pair of wall-powered speakers. This hassle is NOT worth it ...
>
> If "speakers on USB 2.0 card, all else on 1.x builtins" doesn't

What I don't get is that the speakers work no matter what I hook it up
to. 1.x builtins (they were recognized as 1.x by Windows, I assume they
still are seeing as how they cannot be upgraded) or 2.0 card. And no
matter what I hook up the speakers too, it messes with the keyboard,
though I had not tried to put the keyboard and mouse back on the 1.x
builtins (don't really need 2.0 speed for such devices) as they were
starting to act up on them.

> work, you might want to try a power adapter that has a USB host
> connector. (I've seen such at Fry's, intended for devices like
> iPods that were designed to recharge their internal batteries
> from a USB port.) This would effectively convert your current
> set to wall-powered, which might be less costly than a new set.

Perhaps, but I've been wanting a new set for a while now. The set I had
before this one was old when I got them. Last new set I had was from
Creative. Two full range satellites with a 6 1/2" omni-directional
sub-woofer for about $80; unfortunately that was ages ago. I miss them
(the satellite's died before the sub).

> WRT the suggestion to hack something together, I wouldn't suggest
> attempting it unless you're quite sure of what would be involved.

I'm fairly certain solder (rosin-core as acid-core would corrode the
contacts), electrical tape and a few prayers that I avoid the below
stated consequences (seriously, there is a +5 and +12 on my motherboard?
man I am seriously under-utilizing this thing).

> It wouldn't be exactly difficult, but getting something backwards
> -- or connecting to the +12 instead of the +5 supply -- would at
> least let all the magic blue smoke out of the speakers :)

--
Yours In Christ,

------------------------------

Message: 27
Date: Sat, 10 Apr 2010 08:02:59 +0200
From: harvey dent <harvey.two...@gmail.com>
Subject: Custom kernel & atheros
To: freebsd-...@freebsd.org
Message-ID:
<p2r132803231004092302x7...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

hi everybody
I try to make a custom kernel (for a "emachines" notebook), but i always get
this same error or a similar (dependent of choosing ath_hal or for example
ath_rf2425):

*ar2425.o(.text+0x582): In function
`ar2425RfAttach':

/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:691: undefined reference to
`ath_hal_malloc'

ar2425.o(.text+0x5d4):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:705:
undefined reference to
`ar5212GetNfAdjust'
ar2425.o(.text+0x614): In function
`ar2425RfDetach':

/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:674: undefined reference to
`ath_hal_free'

ar2425.o(.text+0x6fd): In function `ar2425SetRfRegs':
/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:193: undefined reference to
`ar5212ModifyRfBuffer'
ar2425.o(.text+0x725):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:194:
undefined reference to `ar5212ModifyRfBuffer'
ar2425.o(.text+0xa84): In function `ar2425SetChannel':
/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:99: undefined reference to
`ath_hal_reverseBits'
ar2425.o(.text+0xb4c):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:113:
undefined reference to `ath_hal_reverseBits'
ar2425.o(.text+0xb62):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:115:
undefined reference to `ath_hal_reverseBits'
ar2425.o(.text+0xbba):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:117:
undefined reference to `ath_hal_reverseBits'
ar2425.o(.text+0xbd0):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:119:
undefined reference to `ath_hal_reverseBits'
ar2425.o(.text+0xc21):/usr/src/sys/dev/ath/ath_hal/ar5212/ar2425.c:121: more
undefined references to `ath_hal_reverseBits' follow
sample.o(.text+0x404): In function `ath_rate_sysctl_stats':
/usr/src/sys/dev/ath/ath_rate/sample/sample.c:916: undefined reference to
`ieee80211_iterate_nodes'
sample.o(.text+0x539): In function `calc_usecs_unicast_packet':
/usr/src/sys/dev/ath/ath_rate/sample/sample.h:236: undefined reference to
`ath_hal_computetxtime'
sample.o(.text+0x5b5):/usr/src/sys/dev/ath/ath_rate/sample/sample.h:246:
undefined reference to `ath_hal_computetxtime'
sample.o(.text+0x745): In function `ath_rate_newassoc':
/usr/src/sys/dev/ath/ath_rate/sample/sample.c:771: undefined reference to
`ieee80211_note_mac'
sample.o(.text+0x7ea):/usr/src/sys/dev/ath/ath_rate/sample/sample.c:801:
undefined reference to `ieee80211_note'
sample.o(.text+0xcec): In function `update_stats':
/usr/src/sys/dev/ath/ath_rate/sample/sample.c:530: undefined reference to
`ieee80211_note_mac'
sample.o(.text+0x1040): In function `ath_rate_findrate':
/usr/src/sys/dev/ath/ath_rate/sample/sample.c:273: undefined reference to
`ieee80211_note_mac'
sample.o(.text+0x1216):/usr/src/sys/dev/ath/ath_rate/sample/sample.c:316:
undefined reference to `ieee80211_note_mac'
sample.o(.text+0x160c): In function `ath_rate_tx_complete':
/usr/src/sys/dev/ath/ath_rate/sample/sample.c:572: undefined reference to
`ieee80211_note_mac'
sample.o(.text+0x16e3):/usr/src/sys/dev/ath/ath_rate/sample/sample.c:590:
undefined reference to `ieee80211_note_mac'
sample.o(.text+0x18bc):/usr/src/sys/dev/ath/ath_rate/sample/sample.c:636:
more undefined references to `ieee80211_note_mac' follow
*** Error code 1

Stop in /usr/obj/usr/src/sys/PCBSD1.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.*

I ran "config", and no problem were find.
When I build a GENERIC kernel, there's no any problem.

Here the uname -a:
*FreeBSD pcbsd-8040 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Tue Jan 5
16:02:27 UTC 2010
ro...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
i386
*
Here the kernel config file:

*#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the config(5) manual page,
# and/or the handbook section on Kernel Configuration Files:
#
#
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD$

cpu I686_CPU
ident PCBSD1

# To statically compile in device wiring instead of /boot/device.hints
#hints "GENERIC.hints" # Default places to look for devices.

# Use the following to compile in values accessible to the kernel
# through getenv() (or kenv(1) in userland). The format of the file
# is 'variable=value', see kenv(1)
#
# env "GENERIC.env"

makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols

options SCHED_ULE # ULE scheduler
options PREEMPTION # Enable kernel thread preemption
options INET # InterNETworking
options INET6 # IPv6 communications protocols
options SCTP # Stream Control Transmission Protocol
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
options UFS_GJOURNAL # Enable gjournal-based UFS journaling
options MD_ROOT # MD is a potential root device
options NFSCLIENT # Network Filesystem Client
options NFSSERVER # Network Filesystem Server
options NFSLOCKD # Network Lock Manager
options NFS_ROOT # NFS usable as /, requires NFSCLIENT
options PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS # Pseudo-filesystem framework
options GEOM_PART_GPT # GUID Partition Tables.
options GEOM_LABEL # Provides labelization
options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty)
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
options COMPAT_FREEBSD6 # Compatible with FreeBSD6
options COMPAT_FREEBSD7 # Compatible with FreeBSD7
options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
options KTRACE # ktrace(1) support
options STACK # stack(9) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options P1003_1B_SEMAPHORES # POSIX-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time
extensions
options PRINTF_BUFR_SIZE=128 # Prevent printf output being
interspersed.
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4)
options AUDIT # Security event auditing
options MAC # TrustedBSD MAC Framework
options FLOWTABLE # per-cpu routing cache
#options KDTRACE_HOOKS # Kernel DTrace hooks

# Enable i386 a.out binary support
options COMPAT_AOUT

# To make an SMP kernel, the next two lines are needed
#options SMP # Symmetric MultiProcessor Kernel
device apic # I/O APIC

# CPU frequency control
device cpufreq

# Bus support.
device acpi
device pci

##############################
# MCA bus:
#
# The MCA bus device is `mca'. It provides auto-detection and
# configuration support for all devices on the MCA bus.
# No hints are required for MCA.

#device mca # Mca Bus only in old ibm pc and some servers

# SMB bus
#
# System Management Bus support is provided by the 'smbus' device.
# Access to the SMBus device is via the 'smb' device (/dev/smb*),
# which is a child of the 'smbus' device.
#
# Supported devices:
# smb standard I/O through /dev/smb*
#
# Supported SMB interfaces:
# iicsmb I2C to SMB bridge with any iicbus interface
# bktr brooktree848 I2C hardware interface
# intpm Intel PIIX4 (82371AB, 82443MX) Power Management Unit
# alpm Acer Aladdin-IV/V/Pro2 Power Management Unit
# ichsmb Intel ICH SMBus controller chips (82801AA, 82801AB, 82801BA)
# viapm VIA VT82C586B/596B/686A and VT8233 Power Management Unit
# amdpm AMD 756 Power Management Unit
# amdsmb AMD 8111 SMBus 2.0 Controller
# nfpm NVIDIA nForce Power Management Unit
# nfsmb NVIDIA nForce2/3/4 MCP SMBus 2.0 Controller
#
device smbus # Bus support, required for smb below.
device ichsmb
device smb

#############################

##################### BIOS
device smbios

# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
device ataraid # ATA RAID drives
options ATA_STATIC_ID # Static device numbering

# SCSI Controllers
device ahc # AHA2940 and onboard AIC7xxx devices
options AHC_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~128k to driver.
device amd # AMD 53C974 (Tekram DC-390(T))

# SCSI peripherals
device scbus # SCSI bus (required for SCSI)
device ch # SCSI media changers
device da # Direct Access (disks)
device cd # CD
device pass # Passthrough device (direct SCSI access)
device ses # SCSI Environmental Services (and SAF-TE)

# RAID controllers
device aacp # SCSI passthrough for aac (requires CAM)

# atkbdc0 controls both the keyboard and the PS/2 mouse
device atkbdc # AT keyboard controller
device atkbd # AT keyboard

#################
# Options for atkbd:
options ATKBD_DFLT_KEYMAP # specify the built-in keymap
makeoptions ATKBD_DFLT_KEYMAP=fr.iso.acc
####################

device psm # PS/2 mouse

device kbdmux # keyboard multiplexer

device vga # VGA video card driver

# syscons is the default console driver, resembling an SCO console
device sc
###################
options VESA
options SC_PIXEL_MODE
options SC_HISTORY_SIZE=800 # number of history buffer lines
device dpms
options SC_TWOBUTTON_MOUSE
########
device agp # support several AGP chipsets

################# CONSOLE UTF8
options TEKEN_UTF8
options TEKEN_XTERM

#####################################
device drm # DRM core module required by DRM drivers
device i915drm # Intel i830 through i915

####################################

# Power management support (see NOTES for more options)
#device apm
# Add suspend/resume support for the i8254.
device pmtimer

# PCCARD (PCMCIA) support
# PCMCIA and cardbus bridge support
#device cbb # cardbus (yenta) bridge
#device pccard # PC Card (16-bit) bus
#device cardbus # CardBus (32-bit) bus

# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device miibus # MII bus support
device bge # Broadcom BCM570xx Gigabit Ethernet

# ISA Ethernet NICs. pccard NICs included.
#device cs # Crystal Semiconductor CS89x0 NIC
# 'device ed' requires 'device miibus'
#device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards

# Wireless NIC cards
options IEEE80211_DEBUG # enable debug msgs
options IEEE80211_AMPDU_AGE # age frames in AMPDU reorder q's
options IEEE80211_SUPPORT_MESH # enable 802.11s draft support
#device ath_hal # pci/cardbus chip support
options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors
device ath_rf2425
device ath_rate_sample # SampleRate tx rate control for ath

# Pseudo devices.
device loop # Network loopback
device random # Entropy device
device ether # Ethernet support
device tun # Packet tunnel.
device pty # BSD-style compatibility pseudo ttys
device md # Memory "disks"
device gif # IPv6 and IPv4 tunneling
device faith # IPv6-to-IPv4 relaying (translation)
device firmware # firmware assist module

# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
# Note that 'bpf' is required for DHCP.
device bpf # Berkeley packet filter

# USB support
device uhci # UHCI PCI->USB interface
device ehci # EHCI PCI->USB interface (USB 2.0)
device usb # USB Bus (required)
device ukbd # Keyboard
device ums # Mouse
device urio # Diamond Rio 500 MP3 player
# Modules
makeoptions MODULES_OVERRIDE="msdosfs msdosfs_iconv ntfs ntfs_iconv tmpfs
zfs udf udf_iconv usb/umass cd9660 cd9660_iconv hptrr linux linprocfs
linsysfs /ata/atapicd dc sound/sound sound/driver/hda speaker ahci usb/uhid
usb/ulpt ipfw wlan wlan_wep wlan_tkip wlan_ccmp wlan_amrr crypto ath if_lagg
tx nullfs splash /syscons/blank /syscons/dragon /syscons/fade /syscons/green
/syscons/logo /syscons/rain /syscons/snake /syscons/star /syscons/warp
libmchain libiconv zlib opensolaris geom/geom_eli geom/geom_journal
geom/geom_mirror geom/geom_uzip"
*
Thank you.

------------------------------

End of freebsd-questions Digest, Vol 305, Issue 11
**************************************************

0 new messages