All
I am looking into an issue with timecounter hardware on a number of HP
DL165 G7's
They all run FreeBSD 9.1-RELEASE and all have the same CPU and firmware.
However they report strange results when you probe kern.timecounter.choice
and
kern.timecounter.hardware
Take this example
ssh
Jan Mikkelsen wrote:
On 15/01/2012, at 6:00 PM, Roman Kurakin wrote:
Hi,
Jan Mikkelsen wrote:
Hi,
I'm looking to upgrade a system running frame relay over a Sangoma A101 card
and WANPIPE.
Sangoma do not support FreeBSD anymore, so I'm looking for alternatives.
What har
On 15/01/2012, at 6:00 PM, Roman Kurakin wrote:
> Hi,
>
> Jan Mikkelsen wrote:
>> Hi,
>>
>> I'm looking to upgrade a system running frame relay over a Sangoma A101 card
>> and WANPIPE.
>>
>> Sangoma do not support FreeBSD anymore, so I
so I'm looking for alternatives.
>>
>> What hardware does ng_frame_relay support now that ar(4) and sr(4) are not
>> in FreeBSD 9?
>>
>> Specifically, will ng_frame_relay work with a Digium TE121 and
>> ports/dahdi-kmod?
>>
>> Any sugges
Hi,
Jan Mikkelsen wrote:
Hi,
I'm looking to upgrade a system running frame relay over a Sangoma A101 card
and WANPIPE.
Sangoma do not support FreeBSD anymore, so I'm looking for alternatives.
What hardware does ng_frame_relay support now that ar(4) and sr(4) are not in
On 1/13/12 11:00 PM, Jan Mikkelsen wrote:
Hi,
I'm looking to upgrade a system running frame relay over a Sangoma A101 card
and WANPIPE.
Sangoma do not support FreeBSD anymore, so I'm looking for alternatives.
What hardware does ng_frame_relay support now that ar(4) and sr(4)
Hi,
I'm looking to upgrade a system running frame relay over a Sangoma A101 card
and WANPIPE.
Sangoma do not support FreeBSD anymore, so I'm looking for alternatives.
What hardware does ng_frame_relay support now that ar(4) and sr(4) are not in
FreeBSD 9?
Specifically, will ng_f
You mean something like this?
http://www.freebsd.org/releases/8.1R/hardware.html
Regards.
2010/11/3 Bob Brower
> While searching the Archives I saw a reference to a txt
> filecontaining a listing of driver supported hardware. Is this listing
> available
>
While searching the Archives I saw a reference to a txt
filecontaining a listing of driver supported hardware. Is this listing
available
via forums?
thnx
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org
on 06/04/2010 15:47 Andriy Gapon said the following:
> on 30/03/2010 19:43 Andriy Gapon said the following:
>> do you think that periodic saving of system clock to hardware and making
>> resettodr
>> asynchronous are dependent issues? Or are they orthogonal and c
on 30/03/2010 19:43 Andriy Gapon said the following:
>
> do you think that periodic saving of system clock to hardware and making
> resettodr
> asynchronous are dependent issues? Or are they orthogonal and can be
> implemented
> independently?
A new version
e a callout
> schedule a task for taskqueue_thread).
Guys,
do you think that periodic saving of system clock to hardware and making
resettodr
asynchronous are dependent issues? Or are they orthogonal and can be
implemented
independently?
--
Andriy Gapon
On Sunday 28 March 2010 7:45:25 am Dag-Erling Smørgrav wrote:
> Peter Jeremy writes:
> > A new kthread which sleeps on channel "update_rtc". When woken, it
> > checks to see if it's within (say) 50msec of a second boundary and so,
> > it does a trylock on the (new) RTC mutex. If it grabs the mut
Peter Jeremy writes:
> Traditionally, the (PC) RTC is on the ISA bus (though it's possible it
> might use I2C on other architectures or LPC on current PCs).
AFAIK, it's usually on I2C on non-i386 platforms. I2C RTC chips are
dirt cheap and easy to integrate, especially if you already have I2C
te
On 2010-Mar-27 01:38:36 +0100, Dag-Erling Smørgrav wrote:
>Peter Jeremy writes:
>> It's not especially important how regularly the RTC is updated, just
>> that it _is_ updated. This suggests that an alternative approach
>> would be for adjtime() / ntp_adjtime() to directly call resettodr() if
>>
Peter Jeremy writes:
> It's not especially important how regularly the RTC is updated, just
> that it _is_ updated. This suggests that an alternative approach
> would be for adjtime() / ntp_adjtime() to directly call resettodr() if
> it's more than P minutes since resettodr() was last called.
It
Peter Jeremy writes:
> At least some versions of Linux also save a RTC drift approximation
> and "last set" timestamp whenever the RTC is updated. This allows the
> kernel to better set the system clock from the RTC at boot (ie, our
> inittodr()). The downside is that this needs to store 8-16 by
On 2010-Mar-26 17:30:14 +0100, Dag-Erling Smørgrav wrote:
>Andriy Gapon writes:
>> Dag-Erling Smørgrav writes:
>> > Andriy Gapon writes:
>> > > Also, I am aware that the period should be configurable (sysctl).
>> > Why?
>> Because there would always be someone who would want a different value :
Andriy Gapon writes:
> Dag-Erling Smørgrav writes:
> > Andriy Gapon writes:
> > > Also, I am aware that the period should be configurable (sysctl).
> > Why?
> Because there would always be someone who would want a different value :)
> > Although I can see an argument for a sysctl to turn it on o
on 26/03/2010 17:44 Dag-Erling Smørgrav said the following:
> Andriy Gapon writes:
>> What do you think about the following patch or something similar?
>
> I've wondered for years why we didn't already do this.
>
>> Also, I am aware that the period should be configurable (sysctl).
>
> Why?
Bec
Andriy Gapon writes:
> What do you think about the following patch or something similar?
I've wondered for years why we didn't already do this.
> Also, I am aware that the period should be configurable (sysctl).
Why?
Although I can see an argument for a sysctl to turn it on or off.
IIRC, Linu
on 26/03/2010 17:12 Ed Schouten said the following:
> * Andriy Gapon wrote:
>> +timeout(periodic_resettodr, NULL, 1800 * hz);
>
> By the way, wouldn't it be a little nicer to use callout(9)?
I don't know :-)
I see that timeout is deprecated and is unsafe in some respects, but using
callout
* Andriy Gapon wrote:
> + timeout(periodic_resettodr, NULL, 1800 * hz);
By the way, wouldn't it be a little nicer to use callout(9)?
--
Ed Schouten
WWW: http://80386.nl/
pgpz0oTdiuq2Z.pgp
Description: PGP signature
* Andriy Gapon wrote:
> What do you think about the following patch or something similar?
Yes, please. :-)
I had an Intel motherboard which had a clock drift. A couple of seconds
a day. When I had to reboot after upgrading/etc, it was not a serious
problem, but say, the system locked up and rebo
What do you think about the following patch or something similar?
Just in case, I am already aware about missing empty lines before the code in
the
new functions. Also, I am aware that the period should be configurable
(sysctl).
Reference:
http://lists.freebsd.org/pipermail/freebsd-hardware
Does anybody know if Gigabyte provides special ACPI interfaces for HWM on their
motherboards? Maybe something like ASUS does (acpi_aiboost)?
Or do they access HWM chip directly?
They have this EasyTune software, so they must be doing something.
DSDT of GA-MA780G-UD3H doesn't even provide TZ.
Thi
Hello,
There are two ways to managed a RNG in FreeBSD, I'm asking which is the
best:
- feed the random subsystem via random_harvest(9)
- add the RNG to random(4) as the Nehemiah RNG (VIA padlock)
In fact, i do not understand why the Nehemiah RNG is not managed by
padlock(4).
Thanks, regards.
__
er each driver reload.
Let me know how it goes.
Andrew
--
View this message in context:
http://www.nabble.com/Hardware-support-for-AMD-Geode-CS5536-audio--tp15002428p20920300.html
Sent from the freebsd-hackers mailing list archive at Nabble.com.
_
manufacturers of hardware. More recently there were times when anybody from
because managers/bosses concentrate on majority, not minority of users.
manufacturers did not notice Linux. However now it is possible to find a few
given out "put normal OS - their list is at us on a site and
this message in context:
http://www.nabble.com/Hardware-support-for-AMD-Geode-CS5536-audio--tp15002428p20786956.html
Sent from the freebsd-hackers mailing list archive at Nabble.com.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mail
ase tell me if there's anything else I can provide to help you.
>
> [1] http://www.fit-pc.com/new/fit-pc-1-0-specifications.html
>
> Cheers,
> --
> Lionel Flandrin
> ___
> freebsd-hackers@freebsd.org mailing list
> http://l
On Wed, Nov 26, 2008 at 07:30:41PM -0800, ancelgray wrote:
>
> To AMD CS5536 users:
>
> This is Andrew Gray. I have finished the audio driver for the AMD CS5536
> companion
> chip. It is working on a PC Engines Alix 1C low power board under FreeBSD
> 7.0.
> It can be found at:
>
> http://mod
Cyrix). The driver was
part of an effort to "undo" drivers that had been
put into the Geode's "hypervisor" (sort of an extended
ACPI that provided device emulators ("device models");
it turned out that was considered reverse engineering
hardware and so was a
On Thu, Nov 27, 2008 at 1:30 AM, ancelgray <[EMAIL PROTECTED]> wrote:
>
> To AMD CS5536 users:
>
> This is Andrew Gray. I have finished the audio driver for the AMD CS5536
> companion
> chip. It is working on a PC Engines Alix 1C low power board under FreeBSD
> 7.0.
> It can be found at:
>
> http
initions are not copyrightable if they are dictated by external
> factors, such as compatibility with existing software or hardware.
>
> There are even cases in which actual code is not copyrightable,
> specifically if the algorithm it implements is so simple that no
> reasonable progr
dictated by external
factors, such as compatibility with existing software or hardware.
There are even cases in which actual code is not copyrightable,
specifically if the algorithm it implements is so simple that no
reasonable programmer would have implemented it in any other way.
(SCO tried to
it's free and better documented.
http://www.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/arch/i386/pci/auglx.c
I don't have the hardware to test.
My 0,02 euros.
Regards.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listin
ancelgray AT y a h o o DOT com
--
View this message in context:
http://www.nabble.com/Hardware-support-for-AMD-Geode-CS5536-audio--tp15002428p20713056.html
Sent from the freebsd-hackers mailing list archive at Nabble.com.
___
freebsd-hackers@freebsd.org
On 2008-10-02 05:05, [EMAIL PROTECTED] wrote:
> To All,
>
> I finally have a working CS5536 audio driver for FreeBSD 6.2. The filename
> is snd_amd5536.ko and I will be making it available shortly. I have been
> using an ALIX-1C motherboard for my testing. Anyone have othe
hardware that they want to test it on?
Another question. How does one get the FreeBSD people to put this
driver into their OS?
You have to generate a patch for 8-current and send it to
[EMAIL PROTECTED] for review. There may be some improvement
suggestions or bug reports then. Fix the
[EMAIL PROTECTED] skrev:
Another question. How does one get the FreeBSD people to put this
> driver into their OS?
Make the source code available somewhere and hopefully someone (usually
ariff@ or mav@) with knowledge about the sound subsystem will review it.
Just make sure that you follow
To All,
I finally have a working CS5536 audio driver for FreeBSD 6.2. The filename is
snd_amd5536.ko and I will be making it available shortly. I have been using an
ALIX-1C motherboard for my testing. Anyone have other hardware that they want
to test it on?
Another question. How does one
To All,
I finally have a working CS5536 audio driver for FreeBSD 6.2. The filename is
snd_amd5536.ko and I will be making it available shortly. I have been using an
ALIX-1C motherboard for my testing. Anyone have other hardware that they want
to test it on?
Another question. How does one
Hello FreeBSD-Hackers,
I have 3 cards to be given away, $129 value. There is a catch -- you need to
volunteer to port the card to FreeBSD and make your modifications publically
available. Join and contribute to an open source effort to enable Video4Linux
drivers to run on BSD here:
http://vide
OK,
After doing a little more reading, I see that a DOS test program is impossible
because
the MSR registers for the audio controller are accessed in protected mode only.
There actually are opcoded assembler instructions to access the MSR's:
RDMSR
WRMSR
This is a show stopper in DOS.
This i
d 4.6 drivers still work on freebsd 6.2 and 7.0?
Not sure, I haven't had relevant Geode hardware up
for awhile... I'd be rather surprised if even for
the CS5530 something hadn't changed or needed
tweaking, but I don't know.
>
> Are you working on this CS5536 driver? Do y
compact flash in its bay, and just use it as a flash HD. This works fine:
http://www.mini-box.com/Alix-1C-Board-1-LAN-1-MINI-PCI?sc=8&category=754
A question for you? Do Freebsd 4.6 drivers still work on freebsd 6.2 and 7.0?
Are you working on this CS5536 driver? Do you have hardware yet?
Following up with some corrections/additional info:
On Thu, 2008-02-07 at 01:04 +1030, Wayne Sierke wrote:
> I have a Compaq ML370 Proliant server here which is likely to remain
> unused for the foreseeable future. Some of its key specs are:
>
> - Dual 800MHz PIII/133MHz/256MB CPU
Of course, t
I have a Compaq ML370 Proliant server here which is likely to remain
unused for the foreseeable future. Some of its key specs are:
- Dual 800MHz PIII/133MHz/256MB CPU
- 1.25GB ECC Memory
- 2 x 9G 10k SCSI-UW2
- 1 x 18G 10k SCSI-UW2
- 2 x Intel EtherExpress PRO/100 Ethernet
I've been contempl
Quoting Bruce R. Montague, who wrote on Wed, Jan 23, 2008 at 10:06:51PM -0800 ..
>
> Hi, re:
>
> > I'm hoping someone will be able to help me out with the audio is
> > the Geode CS5536.
>
> Those AMD Geode systems with the CS5536 look almost
> cheap enough to afford one for each hand. I'll
Hi, re:
> I'm hoping someone will be able to help me out with the audio is
> the Geode CS5536.
Those AMD Geode systems with the CS5536 look almost
cheap enough to afford one for each hand. I'll
look into upgrading the 5530 audio driver for the
5536, but it will take sometime. If someone
Bruce R. Montague wrote:
I would try to fix/upgrade this driver if I had any
hardware with a CS5536, but I don't. That said, can
anyone recomend a cheap system that includes the
CS5536, is generally available, doesn't cost very
much and can be used as a minimal dev platform?
(Sure
Am 23.01.2008 um 12:09 schrieb Alec Kloss:
On 2008-01-22 22:34, Bruce R. Montague wrote:
I would try to fix/upgrade this driver if I had any
hardware with a CS5536, but I don't.
The specific device I'm targeting is a "koolu",
http://www.koolu.com.
Or take a look at h
ple claiming he
might...
> I would try to fix/upgrade this driver if I had any
> hardware with a CS5536, but I don't. That said, can
> anyone recomend a cheap system that includes the
> CS5536, is generally available, doesn't cost very
> much and can be used as a minimal dev
bsd.org/soundsystem
My googling may be mistaken about a thread last February.
> I would try to fix/upgrade this driver if I had any
> hardware with a CS5536, but I don't. That said, can
> anyone recomend a cheap system that includes the
> CS5536, is generally available, doesn't
le of pings along the line of
the above. I honestly hadn't realized anybody was
using it (I guess that's the problem with it working).
If there was a thread last february, I must have
missed it. I dont think I've ever seen the soundsystem
wiki.
I would try to fix/upgrade this driver if
://www.amd.com/us-en/ConnectivitySolutions/ProductInformation/0,,50_2330_9863_9864^13054,00.html
I'd be happy to try whatever people suggest, or even provide access
to a RELENG_7 or -current machine running this hardware. Remote
debugging options are limited because there are no serial po
On Mon, Nov 19, 2007 at 09:02:33AM +0100 I heard the voice of
Søren Schmidt, and lo! it spake thus:
>
> I'd like to get the final verdict of the attached patch and if it
> fixes the problem or not.
Behind the curve, as usual, I just upgraded one of my systems that's
had the problem in the past to
Joao Barros wrote:
On 11/20/07, Thierry Herbelot <[EMAIL PROTECTED]> wrote:
Le Tuesday 20 November 2007, Ari Suutari a écrit :
I have Promise TX2 (PDC20575). It didn't work with 7.0 betas
before, but with this patch things run as well as they did
on 6.x.
Ari S.
Hello,
Ha
Hi,
On man, nov 19, 2007 at 09:02:33 +0100, Søren Schmidt wrote:
Hi All!
I'd like to get the final verdict of the attached patch and if it fixes
the problem or not.
Please test and report, its a bit urgent if it need to get into R7 :)
I have Promise TX2 (PDC20575). It didn't work with
Le Tuesday 20 November 2007, Ari Suutari a écrit :
> I have Promise TX2 (PDC20575). It didn't work with 7.0 betas
> before, but with this patch things run as well as they did
> on 6.x.
>
> Ari S.
Hello,
Has anyone an idea why the Promise controllers seemed to work correctly under
6.x, then
On 11/20/07, Thierry Herbelot <[EMAIL PROTECTED]> wrote:
> Le Tuesday 20 November 2007, Ari Suutari a écrit :
>
> > I have Promise TX2 (PDC20575). It didn't work with 7.0 betas
> > before, but with this patch things run as well as they did
> > on 6.x.
> >
> > Ari S.
>
> Hello,
>
> Has anyone a
Le Monday 19 November 2007, Søren Schmidt a écrit :
> Hi All!
>
> I'd like to get the final verdict of the attached patch and if it fixes
> the problem or not.
>
> Please test and report, its a bit urgent if it need to get into R7 :)
>
>
> -Søren
Hello SoS,
From what I read, it seems that the las
On man, nov 19, 2007 at 09:02:33 +0100, Søren Schmidt wrote:
> Hi All!
>
> I'd like to get the final verdict of the attached patch and if it fixes
> the problem or not.
>
> Please test and report, its a bit urgent if it need to get into R7 :)
>
>
Hi!
I'm sorry I wasn't able to test this earli
Hi All!
I'd like to get the final verdict of the attached patch and if it fixes
the problem or not.
Please test and report, its a bit urgent if it need to get into R7 :)
-Søren
? promise-fix2
? promise-fix3
Index: ata-chipset.c
Ulf Lilleengen wrote:
I tried the patch, but I end up with the partition table being incorrectly
read (probably) on the drives connected to my TX4 card. Normally, there's
one partition on the drive, but when I apply the patch, the drive provider
(ad6) is all that shows up in /dev.
When I rever
On fre, nov 02, 2007 at 01:34:51 +0300, Alexander Sabourenkov wrote:
> Hello.
>
> I have ported the workaround for the hardware bug that causes data
> corruption on Promise SATA300 TX4 cards to RELENG_7.
>
> Bug description:
> SATA300 TX4 hardware chokes if last PRD entry (
By the way, is there any chance to get RAID5 working with this controller?
rik
Alexander Sabourenkov wrote:
Arno J. Klaassen wrote:
Rather than the marginal HW part, it seems, for me, closely related to
MB/BIOS (as well (Alexander apperently has about the same setup as I
have for this test)
Roman Kurakin wrote:
By the way, is there any chance to get RAID5 working with this controller?
Software only.
--
./lxnt
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send a
Arno J. Klaassen wrote:
>
> Rather than the marginal HW part, it seems, for me, closely related to
> MB/BIOS (as well (Alexander apperently has about the same setup as I
> have for this test)):
>
[...]
>
> I vaguely remember from another PR that the Promise card does
> something with PCI-bursti
Arno J. Klaassen wrote:
Hello,
Alexander Sabourenkov <[EMAIL PROTECTED]> writes:
Hello.
I have ported the workaround for the hardware bug that causes data
corruption on Promise SATA300 TX4 cards to RELENG_7.
Bug description:
SATA300 TX4 hardware chokes if last PRD entry (in
Hello,
> [ ... ]
> > I will test again with "#define PDC_MAXLASTSGSIZE 32*4" (just to see
> > if that makes a difference)
> >
> One thing to try is to loose any geom raid, if raid needed use ataraid
> instead.
Nope : i did a "newfs ad6" (the disk at the Promise TX4) and then an
rsync on it panic
Arno J. Klaassen wrote:
definitely an improvement, but not sufficient (for my setup ) :
amd64-releng_6 on an ASUS A8V UP (box ran rock-stable
for years i386-releng_5 with same hardware apart TX4 and
drives)
from dmesg :
atapci0: port 0xe000-0xe07f,0xd800-0xd8ff
mem 0xfbb0-0xfbb00fff
Alexander Sabourenkov <[EMAIL PROTECTED]> writes:
> Arno J. Klaassen wrote:
> > definitely an improvement, but not sufficient (for my setup ) :
> >
> > amd64-releng_6 on an ASUS A8V UP (box ran rock-stable
> > for years i386-releng_5 with same hardware apart
Arno J. Klaassen wrote:
> definitely an improvement, but not sufficient (for my setup ) :
>
> amd64-releng_6 on an ASUS A8V UP (box ran rock-stable
> for years i386-releng_5 with same hardware apart TX4 and
> drives)
>
> from dmesg :
>
Setup is identical to mine, exc
Hello,
Alexander Sabourenkov <[EMAIL PROTECTED]> writes:
> Hello.
>
> I have ported the workaround for the hardware bug that causes data
> corruption on Promise SATA300 TX4 cards to RELENG_7.
>
> Bug description:
> SATA300 TX4 hardware chokes if last PRD entry (in
Søren Schmidt wrote:
Søren Schmidt wrote:
Good catch!
However from my quick glimpse at the Promise sources the limit seems
to be 32 Dwords ie 32*4 = 128bytes.
Please see driver named 4_sataii150-300_linux2.6-src_x86-64_v1.01.0.23
I'll investigate further and ask Promise for the gory details
Søren Schmidt wrote:
Good catch!
However from my quick glimpse at the Promise sources the limit seems
to be 32 Dwords ie 32*4 = 128bytes.
I'll investigate further and ask Promise for the gory details, stay
tuned...
I dont think the PRD count limitation is a real problem, I've newer
seen that
Alexander Sabourenkov wrote:
Hello.
I have ported the workaround for the hardware bug that causes data
corruption on Promise SATA300 TX4 cards to RELENG_7.
Bug description:
SATA300 TX4 hardware chokes if last PRD entry (in a dma transfer) is
larger than 164 bytes. This was found while
Hello.
I have ported the workaround for the hardware bug that causes data
corruption on Promise SATA300 TX4 cards to RELENG_7.
Bug description:
SATA300 TX4 hardware chokes if last PRD entry (in a dma transfer) is
larger than 164 bytes. This was found while analysing vendor-supplied
linux driver
On Thursday 01 February 2007 14:40, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Luigi Rizzo <[EMAIL PROTECTED]> writes:
> : On Thu, Feb 01, 2007 at 11:38:51AM -0700, M. Warner Losh wrote:
> : > In message: <[EMAIL PROTECTED]>
> : > Peter Jeremy <[EMAIL PROTECTE
Peter Jeremy wrote:
> Daniel Rudy wrote:
> > None of this stuff appears on my system and I'm running 6.1. I can't
> > even find dmidump anywhere on the system or in ports either.
>
> Please elaborate. kenv(8) states that it first appeared in 4.1.1 and
> I don't recall seeing any reference
At about the time of 2/1/2007 11:33 PM, Danny Braniss stated the following:
>> --ikeVEW9yuYc//A+q
>> Content-Type: text/plain; charset=us-ascii
>> Content-Disposition: inline
>> Content-Transfer-Encoding: quoted-printable
>>
>> On Thu, 2007-Feb-01 21:49:43 -0800, Daniel Rudy wrote:
>>> None of this
>
> --ikeVEW9yuYc//A+q
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Thu, 2007-Feb-01 21:49:43 -0800, Daniel Rudy wrote:
> >None of this stuff appears on my system and I'm running 6.1. I can't
> >even find dmidump
On Thu, 2007-Feb-01 21:49:43 -0800, Daniel Rudy wrote:
>None of this stuff appears on my system and I'm running 6.1. I can't
>even find dmidump anywhere on the system or in ports either.
Please elaborate. kenv(8) states that it first appeared in 4.1.1 and
I don't recall seeing any reference to '
At about the time of 2/1/2007 11:40 AM, M. Warner Losh stated the following:
> In message: <[EMAIL PROTECTED]>
> Luigi Rizzo <[EMAIL PROTECTED]> writes:
> : On Thu, Feb 01, 2007 at 11:38:51AM -0700, M. Warner Losh wrote:
> : > In message: <[EMAIL PROTECTED]>
> : > Peter Jere
In message: <[EMAIL PROTECTED]>
Luigi Rizzo <[EMAIL PROTECTED]> writes:
: On Thu, Feb 01, 2007 at 11:38:51AM -0700, M. Warner Losh wrote:
: > In message: <[EMAIL PROTECTED]>
: > Peter Jeremy <[EMAIL PROTECTED]> writes:
: > : On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wro
On Thu, Feb 01, 2007 at 11:38:51AM -0700, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Peter Jeremy <[EMAIL PROTECTED]> writes:
> : On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote:
> : >If the machine is a PXE-compliant device [2], it should have a GUID/
> : >UUID [1]
In message: <[EMAIL PROTECTED]>
Peter Jeremy <[EMAIL PROTECTED]> writes:
: On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote:
: >If the machine is a PXE-compliant device [2], it should have a GUID/
: >UUID [1] available. This can be exposed by sysutil/hal [3] via the
: >smbios.sy
On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote:
>If the machine is a PXE-compliant device [2], it should have a GUID/
>UUID [1] available. This can be exposed by sysutil/hal [3] via the
>smbios.system.uuid field.
You can also get it via kenv(8) without needing any ports:
# kenv smbios.sy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 27, 2007, at 23:35 , Daniel Rudy wrote:
At about the time of 12/19/2006 7:19 AM, Devon H. O'Dell stated the
following:
2006/12/19, Koen Martens <[EMAIL PROTECTED]>:
Hi All,
I was wondering, if something like a uniq
At about the time of 12/19/2006 7:19 AM, Devon H. O'Dell stated the
following:
> 2006/12/19, Koen Martens <[EMAIL PROTECTED]>:
>> Hi All,
>>
>> I was wondering, if something like a unique hardware identification
>> would be possible on FreeBSD.
>>
>&
>
> > I'm thinking of something like combining serial numbers from
> > CPU/disks for example, but there does not seem to be a clear way to
> > obtain these (not all cpu's even have a serial number in there).
>
> the simplest thing that comes to my mind is parsing `dmidump` for
> serial numbers, h
> I'm thinking of something like combining serial numbers from
> CPU/disks for example, but there does not seem to be a clear way to
> obtain these (not all cpu's even have a serial number in there).
the simplest thing that comes to my mind is parsing `dmidump` for
serial numbers, hoping there ar
In response to "Devon H. O'Dell" <[EMAIL PROTECTED]>:
> 2006/12/19, Koen Martens <[EMAIL PROTECTED]>:
> > Hi All,
> >
> > I was wondering, if something like a unique hardware identification
> > would be possible on FreeBSD.
> >
> >
In <[EMAIL PROTECTED]>, Koen Martens <[EMAIL PROTECTED]> typed:
> Hi All,
>
> I was wondering, if something like a unique hardware identification
> would be possible on FreeBSD.
>
> I'd like a machine to authenticate to a server, for which it will
> need a
2006/12/19, Koen Martens <[EMAIL PROTECTED]>:
Hi All,
I was wondering, if something like a unique hardware identification
would be possible on FreeBSD.
I'd like a machine to authenticate to a server, for which it will
need a unique identification. Problem is, it should b
Hi All,
I was wondering, if something like a unique hardware identification
would be possible on FreeBSD.
I'd like a machine to authenticate to a server, for which it will
need a unique identification. Problem is, it should be generated
automatically and not easy to fake / detect without al
ROTECTED]';
> '[EMAIL PROTECTED]'
> Subject: FreeBSD: driver for ssl hardware accelerator board based on
> broadcom bcm5825, bcm5862 chips
>
>
> Hello,
> I am working on FreeBSD driver for bcm5825 (5862) based board.
> Would you please help me.
>
> First o
-Original Message-
From: Alex Aronson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 10:48 AM
To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]';
'[EMAIL PROTECTED]'
Subject: FreeBSD: driver for ssl hardware acc
1 - 100 of 418 matches
Mail list logo
