On Monday, April 25, 2011 5:38:30 pm Przemyslaw Frasunek wrote:
> > I don't think so. You can try swapping the hints for sio0 and sio1 and
> > seeing if
> > sio1 suddenly shows up as working and valid. If so, then the changes in 8
> > to bind
> > unit numbers using hints might work for you to g
> I don't think so. You can try swapping the hints for sio0 and sio1 and
> seeing if
> sio1 suddenly shows up as working and valid. If so, then the changes in 8 to
> bind
> unit numbers using hints might work for you to get COM1 back as sio0.
Few days ago I decided to upgrade to 8.2-STABLE, pa
On Tuesday, April 19, 2011 7:05:34 pm Przemyslaw Frasunek wrote:
> > The _STA method is used to query a device's status, and a status of 0 means
> > that the device is disabled. I believe that this means that when you have
> > SOL enabled (SOLE?) that COM1 is marked inactive so the OS ignores the
> The _STA method is used to query a device's status, and a status of 0 means
> that the device is disabled. I believe that this means that when you have
> SOL enabled (SOLE?) that COM1 is marked inactive so the OS ignores the device.
Good catch, thanks! I had a feeling, that it must be caused by
On Monday, April 18, 2011 1:22:59 pm Przemyslaw Frasunek wrote:
> > 1) Add a printf to sioprobe() in sys/dev/sio/sio.c to output an error
> > message
> > when it fails to allocate a SYS_RES_IOPORT device at the very beginning.
>
> Done. I'll need to wait until next reboot - it's a production box,
> 1) Add a printf to sioprobe() in sys/dev/sio/sio.c to output an error message
> when it fails to allocate a SYS_RES_IOPORT device at the very beginning.
Done. I'll need to wait until next reboot - it's a production box, so it has to
be done in night hours.
> 2) Capture 'acpidump -d' output and
On Saturday, April 16, 2011 7:13:16 pm Przemyslaw Frasunek wrote:
> > Hmm, I don't see it even trying to probe the COM1 device. I'll have to wait
> > until you get a verbose dmesg to investigate further I'm afraid. :(
>
> I've got verbose dmesg now: http://www.frasunek.com/tmp/dmesg-verb.txt
Hum
> Hmm, I don't see it even trying to probe the COM1 device. I'll have to wait
> until you get a verbose dmesg to investigate further I'm afraid. :(
I've got verbose dmesg now: http://www.frasunek.com/tmp/dmesg-verb.txt
___
freebsd-stable@freebsd.org mai
On Friday, April 15, 2011 3:04:49 pm Przemyslaw Frasunek wrote:
> > Hmm, that unknown device is your COM1. Do you have a copy of your current
> > dmesg available? I'm curious if sio0 failed to probe the UAR1 device and
> > then
> > later attached to UAR2.
>
> Sure, this is my non-verbose dmes
> Hmm, that unknown device is your COM1. Do you have a copy of your current
> dmesg available? I'm curious if sio0 failed to probe the UAR1 device and
> then
> later attached to UAR2.
Sure, this is my non-verbose dmesg: http://www.frasunek.com/tmp/dmesg.txt
It's from 7.3-RELEASE, but on 7.4
On Friday, April 15, 2011 2:31:20 pm Przemyslaw Frasunek wrote:
> > Hmm, can you post the output of 'devinfo -vr' and a verbose dmesg at a
URL?
>
> Devinfo output is here: http://www.frasunek.com/tmp/devinfo.txt
>
> I'll post verbose dmesg after next reboot, which is already scheduled on
sunday
> Hmm, can you post the output of 'devinfo -vr' and a verbose dmesg at a URL?
Devinfo output is here: http://www.frasunek.com/tmp/devinfo.txt
I'll post verbose dmesg after next reboot, which is already scheduled on sunday
morning.
--
* Fido: 2:480/124 ** WWW: http://www.frasunek.com ** NICHDL:
On Friday, April 15, 2011 1:03:03 pm Przemyslaw Frasunek wrote:
> >> sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on
> >> acpi0
> >> sio0: type 16550A, console
> >> sio0: [FILTER]
> > Do you have any hints for sio* in /boot/device.hints?
>
> My /boot/device.hints are unmodi
>> sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on
>> acpi0
>> sio0: type 16550A, console
>> sio0: [FILTER]
> Do you have any hints for sio* in /boot/device.hints?
My /boot/device.hints are unmodified:
[root@kalina-gw ~]# grep sio /boot/device.hints
hint.sio.0.at="isa"
hin
On Tuesday, April 12, 2011 7:08:22 pm Jeremy Chadwick wrote:
> On Tue, Apr 12, 2011 at 11:13:06PM +0200, Pawel Tyll wrote:
> > >> P.S. -- What's "BMC" stand for?
> > > Baseband Management Controller. It's the separate NIC (sometimes it's
> > > piggy-backed on a NIC) used for remote management of m
On Tuesday, April 12, 2011 3:35:11 pm Przemyslaw Frasunek wrote:
> Hello,
>
> I'm struggling with enabling serial console on Intel SR1630GP server
> platform and FreeBSD 7.4.
>
> In default configuration, my serial ports are detected correctly:
>
> sio0: <16550A-compatible COM port> port 0x3f8-0
On Tue, Apr 12, 2011 at 11:13:06PM +0200, Pawel Tyll wrote:
> >> P.S. -- What's "BMC" stand for?
> > Baseband Management Controller. It's the separate NIC (sometimes it's
> > piggy-backed on a NIC) used for remote management of motherboards.
> > Usually includes IPMI support. Depending on the mot
Hi,
>> P.S. -- What's "BMC" stand for?
> Baseband Management Controller. It's the separate NIC (sometimes it's
> piggy-backed on a NIC) used for remote management of motherboards.
> Usually includes IPMI support. Depending on the motherboard, it may
> even include support for keyboard/video/mous
On Tue, Apr 12, 2011 at 1:49 PM, Jeremy Chadwick
wrote:
> P.S. -- What's "BMC" stand for?
Baseband Management Controller. It's the separate NIC (sometimes it's
piggy-backed on a NIC) used for remote management of motherboards.
Usually includes IPMI support. Depending on the motherboard, it may
On Tue, Apr 12, 2011 at 09:35:11PM +0200, Przemyslaw Frasunek wrote:
> Hello,
>
> I'm struggling with enabling serial console on Intel SR1630GP server
> platform and FreeBSD 7.4.
>
> In default configuration, my serial ports are detected correctly:
>
> sio0: <16550A-compatible COM port> port 0x3
Hello,
I'm struggling with enabling serial console on Intel SR1630GP server
platform and FreeBSD 7.4.
In default configuration, my serial ports are detected correctly:
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A
sio0: [FILTER]
sio1: <16550A-com
21 matches
Mail list logo
