John Baldwin wrote:
Umm, ACPI will allow children devices to allocate their resources out of
the "sysresource" pool. IPMI has to do this on some systems where ACPI
claims the IPMI I/O ports as a system resource.
But surely if alpm(4) were to attach to such a range in this way, it
would need
On Wed, 23 Jul 2008 11:16:02 -0400
John Baldwin <[EMAIL PROTECTED]> wrote:
> I've committed the patch. However, I think this actually points out
> a slightly bigger issue in that the HPET timer is probably
> piggybacking on the ichsmb0 device's BAR, and they really should both
> be able to attach
Bruce M Simpson wrote:
I fished out the A/Open MX3S board I have.
...
So I can confirm SMBus works on the MX3S from Linux 2.6.x. I'll blow
it away with 7.1-BETA and see what happens next.
I can confirm that SMBus appears to work on the A/Open MX3S under
FreeBSD 7.1-BETA.
After kldload ich
Bruce M Simpson wrote:
Jeremy Chadwick wrote:
I'm trying my best to make things better, doing things purely from a
userland perspective and using SMBus exclusively (since the interface is
quite reliable, assuming the SMBus driver used on FreeBSD is working
correctly). I understand-- Bruce is ha
Jeremy Chadwick wrote:
I don't consider this a "dependency issue" at all. These are all
literally separate things; you do not meed smbus(4) and smb(4) if you
just simply want to tie a driver to a feature/device that's on the PCI
bus (e.g. ichsmb(4)).
Besides, does kldload or kernel modules in g
Eugene Grosbein wrote:
I also always use boot0 for my NanoBSDs as I need safe way for remote
upgrades, so have two code slices. And I always use these knobs:
NANO_BOOTLOADER="boot/boot0"
NANO_BOOT0CFG="-o packet -s 1 -m 3 -t 36"
...
Good p
On Fri, Sep 12, 2008 at 05:53:39PM +0100, Bruce M. Simpson wrote:
>So it appears the "active" flag was not being set for the first
> partition, it seems NanoBSD's fdisk script didn't set it; that should
> probably get patched, as this was the root cause of the USB booting delay.
I also alwa
On Fri, Sep 12, 2008 at 01:12:34PM -0500, Chris Ruiz wrote:
>
> On Sep 12, 2008, at 12:57 PM, Jeremy Chadwick wrote:
>
>> On Fri, Sep 12, 2008 at 12:19:55PM -0500, Chris Ruiz wrote:
>>> I have an ICH9 system and get the following:
>>>
>>> First, my kernel:
>>> FreeBSD attack.young-alumni.com 7.1-PR
On Sep 12, 2008, at 12:57 PM, Jeremy Chadwick wrote:
On Fri, Sep 12, 2008 at 12:19:55PM -0500, Chris Ruiz wrote:
I have an ICH9 system and get the following:
First, my kernel:
FreeBSD attack.young-alumni.com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE
#0: Sat Sep 6 08:33:04 CDT 2008 root@:/usr
Chris Ruiz wrote:
Error:
attack:~ root# smbmsg -p
smbmsg: Cannot open /dev/smb0: No such file or directory
Looks like the smb.ko module ain't loaded.
cheers,
BMS
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/
On Fri, Sep 12, 2008 at 12:19:55PM -0500, Chris Ruiz wrote:
> I have an ICH9 system and get the following:
>
> First, my kernel:
> FreeBSD attack.young-alumni.com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE
> #0: Sat Sep 6 08:33:04 CDT 2008 root@:/usr/src/sys/amd64/compile/
> ATTACK amd64
>
> Dm
Jeremy Chadwick wrote:
I'm trying my best to make things better, doing things purely from a
userland perspective and using SMBus exclusively (since the interface is
quite reliable, assuming the SMBus driver used on FreeBSD is working
correctly). I understand-- Bruce is having problems with ichsm
On Sep 11, 2008, at 9:14 AM, Bruce M Simpson wrote:
Does anyone have ichsmb(4) actually seeing SMBus devices?
e.g. you run "smbmsg -p" on your FreeBSD-STABLE system and see
something.
I just tried it again on my IBM ThinkPad T43 and saw nothing, all I
get is:
ichsmb0: device timeout, s
Bruce M. Simpson wrote:
Woops, I noticed right after I sent this message, that there was an
I/O error writing to the USB key from dd in my shell -- I think I was
using a 32768 block size instead of 16384 which might account for the
problem.
I'll be sure to try this all again after I've had som
В пт, 12/09/2008 в 12:39 +0200, Marian Hettwer пишет:
> Reply to myself:
>
> it seems, that the nvidia card isn't recognized by the nvidia kld.
> xorg.log states:
> (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please
> ensure
> (EE) NVIDIA(0): that there is a supported NVIDIA
Jeremy Chadwick wrote:
> didn't think anyone was still using Intel 440BX boards in this day and
> age! (A great chipset, though!)
I just updated an i440BX based dual-celeron-466 from some
old 4.8-stable to 7.1-prerelease. "make buildworld"
takes about eight hours (without -j), but I don't car
Reply to myself:
it seems, that the nvidia card isn't recognized by the nvidia kld.
xorg.log states:
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please
ensure
(EE) NVIDIA(0): that there is a supported NVIDIA GPU in this system,
and
(EE) NVIDIA(0): that the NVIDIA device
"Bruce M. Simpson" <[EMAIL PROTECTED]> writes:
Hi,
>I just tried to port over some of the hardware IDs from OpenBSD 4.3's
> viapm(4) driver to the driver in 6.3-RELEASE, as I really need to see
> what working SMBus support looks like in a FreeBSD system.
Same here, Abit KV8, VIA8237 and viap
Hi All,
I'm testing 7.1 Prerelease right now and am having difficulties to get my
xorg with nvidia up and running.
I updated from:
[EMAIL PROTECTED] <~>uname -a
FreeBSD motor.mobile.rz 7.0-STABLE FreeBSD 7.0-STABLE #0: Mon Aug 4
16:54:32 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERI
On Thu, Sep 11, 2008 at 11:28:03AM -0400, Michael Butler wrote:
> Richard Tector wrote:
> > Bruce M Simpson wrote:
> >> Richard,
> >>
> >> Thanks for this.
> >>
> >> Richard Tector wrote:
> >>>
> >>> I have an ICH9 machine, Tyan motherboard:
> >>> FreeBSD 7.0-STABLE #0: Fri Aug 1 14:57:33 BST 2008
20 matches
Mail list logo
