Last week I decided to blow away my newer laptop's ancient 4.3
installation (well, actually, Lose XP decided to do it for me, but
that's another story). I had just gotten my complimentary developer's
CD set from FreeBSDmall.com (thanks, guys!) and decided to reinstall
everything from scratch.
So after I finished fighting with Windows eXtreme Punishment, I stick
the 4.7 install CD and reboot. Windows loads again. I spend the next
hour playing all sorts of games with the BIOS, and so far as I can
tell it just absolutely refuses to load the 4.7 CD. (Windows
installed from CD just fine.) I borrow a Debian 3.0 CD from a
cow-orker, and it gets a little bit further, but crashes before
loading the kernel. Finally, I give up in despair and make boot
floppies. Works perfectly.
I do as minimal an installation as I possibly can, and immediately
cvsup to -current. Buildworld runs perfectly; installworld drops dead
pretty quickly, as I hadn't yet rebooted with the new kernel. Having
done that, everything goes smoothly.
Every reboot, ACPI prints some odd messages on my console:
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
initial configuration
\\_SB_.LNKA irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.11.0
\\_SB_.LNKB irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.11.1
\\_SB_.LNKC irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.9.0
\\_SB_.LNKE irq 3: [ 3 4] low,level,sharable 0.7.0
\\_SB_.LNKD irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.13.0
\\_SB_.LNKD irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.12.0
\\_SB_.LNKD irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.5.3
\\_SB_.LNKD irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.15.0
\\_SB_.LNKA irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.16.0
before setting priority for links
before fixup boot-disabled links -
after fixup boot-disabled links --
arbitrated configuration -
\\_SB_.LNKA irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.11.0
\\_SB_.LNKB irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.11.1
\\_SB_.LNKC irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.9.0
\\_SB_.LNKE irq 3: [ 3 4] low,level,sharable 0.7.0
\\_SB_.LNKD irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.13.0
\\_SB_.LNKD irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.12.0
\\_SB_.LNKD irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.5.3
\\_SB_.LNKD irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.15.0
\\_SB_.LNKA irq 11: [ 5 6 7 10 11 12] low,level,sharable 0.16.0
pci0: ACPI PCI bus on pcib0
agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xd000-0xdfff at device
0.0 on pci0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
initial configuration
\\_SB_.LNKD irq 11: [ 5 6 7 10 11 12] low,level,sharable 1.0.0
before setting priority for links
before fixup boot-disabled links -
after fixup boot-disabled links --
arbitrated configuration -
\\_SB_.LNKD irq 11: [ 5 6 7 10 11 12] low,level,sharable 1.0.0
pci1: ACPI PCI bus on pcib1
This looks to me like debugging information that probably should not
be printed by default. The ASL and raw DSDT are available on request.
What else is there to mention
NEWCARD worked beautifully with my Enterasys RoamAbout card and with
my old standby 3C589D (which I use when I need a static address). I
am noticing some surprising network hesitation on the 3Com when I send
large files to the laptop. Now that I have working CardBus I should
try upgrading to a 32-bit network card.
After deleting the cvsup that I had originally installed and
installing an older (non-gui) version, I was able to build X from
scratch with no trouble. Mozilla 1.2 also built without error. KDE
was another story, but I didn't care to spend a lot of time debugging
huge C++ programs so I stopped bothering with it. I also built
ImageMagick, which I need when downloading images from my digital
camera, and had no trouble other than the useless dependency that it
has on some library or other that I couldn't care less about and never
builds for me anyway. I had to back the openssh-portable port off to
the previous version so that the Kerberos patches would apply.
(Perhaps this needs to be separated out into a separate port.)
All the commits I made this past weekend were build-tested on the
laptop (accessing it remotely from home), so from that perspective at
least the system seems pretty solid.
Disklabel is unhappy with GEOM, as others have already noted. I don't
anticipate needing to redo the label any time soon, so I'm not
immediately concerned about this.
I have no clue how to interpret the output from `sysctl
hw.acpi.thermal'.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
