On Thu, Sep 11, 2008 at 03:14:46PM +0100, Bruce M Simpson wrote:
> Jeremy Chadwick wrote:
>> ...
>> Might mention this to jhb@ to see if it's related to the SMBus changes
>> made 1.5 years ago:
>> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/alpm.c
>>
>
> Thanks for the pointers. The other
On Thu, Sep 11, 2008 at 10:40:24AM -0400, Michael Butler wrote:
> Bruce M. Simpson wrote:
> > Miroslav Lachman wrote:
> >> Jeremy Chadwick wrote:
> >>
> >>> I suppose a lot of these could be addressed if I released the code in a
> >>> preliminary fashion (providing folks the ability to help me with
Bruce M Simpson wrote:
>
> Eugene Grosbein wrote:
> > For me, it helps to include these knobs to Nano config file:
> >
> > CONF_WORLD='
> > BOOT_MBR_FLAGS=0x0
> > BOOT_BOOT1_FLAGS=0x0
> > ...
> > '
> >
>
> I added this to the CONF_WORLD in my config file. Unfortunately this
> seems to break USB b
Under linux: install pci-tools or something, then "lspci".
Adrian
2008/9/4 Dan Allen <[EMAIL PROTECTED]>:
>
> On 3 Sep 2008, at 1:58 PM, Wesley Shields wrote:
>
>> I installed the June snapshot of -current on my laptop and it supports
>> my Intel 4965 just fine. Support for this card is out th
Hello. I have same error message on Sharp PC-CV50.
Is it a hardware or BIOS problem ?
The device dosen't have PCIM_CMD_PORTEN bit on PCIR_COMMAND
(address 0x04, bit 0), and dosen't have any valid address on PCIR_BAR(x).
pciconf can't write PCIR_BAR(x).
`pciconf -lv` shows:
[EMAIL PROTECTED]
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 some sleep.
cheers
BMS
Eugene Grosbein wrote:
For me, it helps to include these knobs to Nano config file:
CONF_WORLD='
BOOT_MBR_FLAGS=0x0
BOOT_BOOT1_FLAGS=0x0
...
'
I added this to the CONF_WORLD in my config
On Sun, Aug 10, 2008 at 08:54:17AM +0200, Harald Weis wrote:
> On Sat, Aug 09, 2008 at 11:56:23AM -0300, Carlos A. M. dos Santos wrote:
>
> > 1. Try to insert the CD and wait until it stops pinning before
> > starting mplayer. Some drives are a bit lazy on media recognition.
Doesn't make a differ
I have removed /usr/obj and am going through the whole buildworld/
buildkernel/installkernel process again. There were a bunch of stale
files under /usr/obj/usr/src/sys/i386/compile that may be the issue.
Dan
On Sep 11, 2008, at 2:55 PM, Dan Mack wrote:
I have a custom kernel without nvram
I have a custom kernel without nvram defined anywhere, however, make
installkernel still attempts to install the module. About 45 days
ago, I didn't have this issue. I didn't see anything about this in
UPDATING so I thought I would check here. This system is currently
running stable from
On Thursday 11 September 2008 10:14:46 am Bruce M Simpson wrote:
> Jeremy Chadwick wrote:
> > ...
> > Might mention this to jhb@ to see if it's related to the SMBus changes
> > made 1.5 years ago:
> > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/alpm.c
> >
>
> Thanks for the pointers. The
On Thu, 11 Sep 2008 16:49:56 BST, Bruce M Simpson wrote:
> Interesting, that's classic USB-HDD geometry (255H, 63S). Can you
> tell me what make, model of stick this is?
It's Kingston DTI/512
# diskinfo -v da0
da0
512 # sectorsize
512753664 # mediasize in bytes (
On Thu, Sep 11, 2008 at 01:55:01PM +0100, Bruce M Simpson wrote:
> I have hacked NanoBSD locally to deal with generation of images for
> booting off USB keys. I am using the RELENG_7 branch as real-mode BTX
> support is necessary to support USB boot.
>
> During testing I noticed that whilst the
[Ccing to list to track up thread]
Douglas Berry wrote:
Perhaps this doesn't help... I do RELENG_7 based images
for USB keys/CDROM using the FreesBIE toolkit, and haven't
noticed such delays. I do fill the stick 'tho. Here's
fdisk output...
*** Working on device /dev/md4 ***
paramete
Bruce M. Simpson wrote:
Bruce M Simpson wrote:
...
During testing I noticed that whilst the images eventually boot,
there is an extremely long delay before doing so, between when the
BIOS reads the boot sector and when the BTX loader messages appear.
I can reproduce the boot delay condition
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
>>> ichsmb0: port 0x18e0-0x18ff mem
>>> 0xf4a03000-0xf4a030ff irq 17 at device 31.
Richard Tector wrote:
Interestingly, I just tried on a couple of our webservers. Dell
PowerEdge 860's with ICH7 running 7.0-STABLE, amd64. Loading the
ichsmb module gives:
ichsmb0: port 0x8c0-0x8df at
device 31.3 on pci0
pcib0: no PRT entry for 0.31.INTB
ichsmb0: can't get IRQ
device_attach
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
ichsmb0: port 0x18e0-0x18ff mem
0xf4a03000-0xf4a030ff irq 17 at device 31.3 on pci0
ichsmb0: [GIANT-LOCKED]
ichsmb0: [ITHREAD
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 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
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
ichsmb0: port 0x18e0-0x18ff mem
0xf4a03000-0xf4a030ff irq 17 at device 31.3 on pci0
ichsmb0: [GIANT-LOCKED]
ichsmb0: [ITHREAD]
daffy# smbmsg -p
Prob
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, status=0x41
...in dmesg.
I have a
Bruce M. Simpson wrote:
> Miroslav Lachman wrote:
>> Jeremy Chadwick wrote:
>>
>>> I suppose a lot of these could be addressed if I released the code in a
>>> preliminary fashion (providing folks the ability to help me with
>>> documentation, etc.). Hmm... Yeah, I should really get a beta tarball
>
Miroslav Lachman wrote:
Jeremy Chadwick wrote:
I suppose a lot of these could be addressed if I released the code in a
preliminary fashion (providing folks the ability to help me with
documentation, etc.). Hmm... Yeah, I should really get a beta tarball
up, and/or make a FreeBSD port for it alr
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, status=0x41
...in dmesg.
cheers
BMS
Jeremy Chadwick wrote:
...
Might mention this to jhb@ to see if it's related to the SMBus changes
made 1.5 years ago:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/alpm.c
Thanks for the pointers. The other reports sound like duplicate reports
of the same issue.
I'm not sure that backi
Bruce M Simpson wrote:
...
During testing I noticed that whilst the images eventually boot, there
is an extremely long delay before doing so, between when the BIOS
reads the boot sector and when the BTX loader messages appear.
P.S. It appears none of QEMU, VMware 3.0, or VirtualBox 1.6.6 are
Hi,
I have hacked NanoBSD locally to deal with generation of images for
booting off USB keys. I am using the RELENG_7 branch as real-mode BTX
support is necessary to support USB boot.
During testing I noticed that whilst the images eventually boot, there
is an extremely long delay before doi
Ian Smith wrote:
> % man sysinstall | tail says it all. However sysinstall has enough bits
> (modules, really) that don't suck to make its presence still worthy.
>
> The wrappers around fdisk and bsdlabel alone are worth a lot, despite a
> notion that 'real men' figure out cylinder and sli
Jeremy Chadwick wrote:
On Thu, Sep 11, 2008 at 11:51:52AM +0200, Miroslav Lachman wrote:
Are you still actively working on bsdhwmon and do you plan to support
non-Supermicro servers?
Yes, I'm still actively working on it -- it is in no way shape or form a
dead project. Most of the delays
On Thu, Sep 11, 2008 at 11:44:20AM +0100, Bruce M Simpson wrote:
> How can I load the alpm(4) module for SMBus support on my ASUS Vintage
> AH-1 system?
>
> It appears the I/O range it uses is claimed by the acpi(4) driver. Can I
> override the mapping in some way i.e. tell ACPI not to claim th
On Thu, Sep 11, 2008 at 12:08:47PM +0200, Michael Grant wrote:
> On Thu, Sep 11, 2008 at 11:20 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> > On Thu, Sep 11, 2008 at 10:38:36AM +0200, Michael Grant wrote:
> >> My box crashed again:
> >>
> >> panic: kmem_malloc(4096): kmem_map too small: 1073741
On Thu, Sep 11, 2008 at 11:51:52AM +0200, Miroslav Lachman wrote:
> Are you still actively working on bsdhwmon and do you plan to support
> non-Supermicro servers?
Yes, I'm still actively working on it -- it is in no way shape or form a
dead project. Most of the delays of releasing the software
Hi,
How can I load the alpm(4) module for SMBus support on my ASUS Vintage
AH-1 system?
It appears the I/O range it uses is claimed by the acpi(4) driver. Can I
override the mapping in some way i.e. tell ACPI not to claim the range?
I don't see anything obvious about this in the acpi(4) man
On Thu, 11 Sep 2008, Vincent Hoffman wrote:
> Ian Smith wrote:
>
>
> > The wrappers around fdisk and bsdlabel alone are worth a lot, despite a
> > notion that 'real men' figure out cylinder and slice offsets themselves.
> > If even those sections were broken out to separate tools, I'd ra
Ian Smith wrote:
> The wrappers around fdisk and bsdlabel alone are worth a lot, despite a
> notion that 'real men' figure out cylinder and slice offsets themselves.
> If even those sections were broken out to separate tools, I'd rarely
> need to fire up sysinstall to, for example, partition
On Thu, Sep 11, 2008 at 11:20 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 11, 2008 at 10:38:36AM +0200, Michael Grant wrote:
>> My box crashed again:
>>
>> panic: kmem_malloc(4096): kmem_map too small: 1073741824 total allocated
>> cpuid = 0
>> Uptime: 33d11h12m58s
>> Dumping 3327
Jeremy Chadwick wrote:
On Wed, Sep 10, 2008 at 11:19:10PM +0100, Bruce M Simpson wrote:
Hi there,
I have been looking at a system which has the Intel ICH7 south bridge.
Whenever I try to probe the SMBus on this system with 'smbmsg -p', I get
a lot of status=41 timeout messages in dmesg from
On Thu, Sep 11, 2008 at 10:38:36AM +0200, Michael Grant wrote:
> My box crashed again:
>
> panic: kmem_malloc(4096): kmem_map too small: 1073741824 total allocated
> cpuid = 0
> Uptime: 33d11h12m58s
> Dumping 3327 MB (2 chunks)
> chunk 0: 1MB (151 pages) ... ok
> chunk 1: 3327MB (851568 pages)
My box crashed again:
panic: kmem_malloc(4096): kmem_map too small: 1073741824 total allocated
cpuid = 0
Uptime: 33d11h12m58s
Dumping 3327 MB (2 chunks)
chunk 0: 1MB (151 pages) ... ok
chunk 1: 3327MB (851568 pages) <---hung here
Still no valid dump.
There is 4gig of physical memory in the
On Sun, 7 Sep 2008, Ken Smith wrote:
> On Sat, 2008-09-06 at 14:51 +1000, Ian Smith wrote:
> > I just booted off the 7.0 disc1 to check, and /usr/local/bin/links is
> > still the default browser in Options, available during installation from
> > another vty. So I was a bit surprised, on rebo
40 matches
Mail list logo
