Date: Fri, 17 Dec 2004 13:54:56 -0500 From: "J. Seth Henry" <jshamlet@comcast.net> To: freebsd-questions@freebsd.org Subject: Variety pack of problems installing 5.3-REL on a HP Pavilion XE746 Message-ID: <200412171355.18153.jshamlet@comcast.net>
next in thread | raw e-mail | index | archive | help
Guys,
I recently attempted to install FreeBSD 5.3-REL on a HP Pavilion XE746. This
system contains a TriGem Cognac+ mainboard, based on the Intel i810 chipset.
For the curious, it is running the HP branded 3.0.7 BIOS firmware. ACPI is
enabled be default, and can't be disabled - so that could be part of the
problem. The system has been upgraded to a PIII-850 and 256MB of RAM. As
usual, the system runs WinXP Pro like a champ.
dmesg output:
FreeBSD 5.3-RELEASE #0: Tue Dec 14 11:34:44 EST 2004
root@testbed.alexandria.homeunix.net:/usr/src/sys/i386/compile/testbed
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel Pentium III (847.43-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x68a Stepping = 10
Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory = 267321344 (254 MB)
avail memory = 251936768 (240 MB)
ACPI APIC Table: <PTLTD APIC >
ioapic0 <Version 2.0> irqs 0-23 on motherboard
npx0: [FAST]
npx0: <math processor> on motherboard
npx0: INT 16 interface
acpi0: <PTLTD RSDT> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
cpu0: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
agp0: <Intel 82810 (i810 GMCH) SVGA controller> mem
0xf4000000-0xf407ffff,0xf8000000-0xfbffffff irq 16 at device 1.0 on pci0
pcib1: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci1: <ACPI PCI bus> on pcib1
ahc0: <Adaptec 2940A Ultra SCSI adapter> port 0x3000-0x30ff mem
0xf4100000-0xf4100fff irq 18 at device 11.0 on pci1
ahc0: [GIANT-LOCKED]
aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs
pcib2: <PCI-PCI bridge> at device 14.0 on pci1
pci2: <PCI bus> on pcib2
fxp0: <Intel 82558 Pro/100 Ethernet> port 0x4000-0x401f mem
0xf4200000-0xf42fffff,0xf4400000-0xf4400fff irq 16 at device 4.0 on pci2
miibus0: <MII bus> on fxp0
inphy0: <i82555 10/100 media interface> on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:50:8b:66:49:fe
fxp1: <Intel 82558 Pro/100 Ethernet> port 0x4020-0x403f mem
0xf4300000-0xf43fffff,0xf4401000-0xf4401fff irq 17 at device 5.0 on pci2
miibus1: <MII bus> on fxp1
inphy1: <i82555 10/100 media interface> on miibus1
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: Ethernet address: 00:50:8b:66:49:ff
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH UDMA66 controller> port
0x1800-0x180f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
uhci0: <Intel 82801AA (ICH) USB controller> port 0x1820-0x183f irq 19 at
device 31.2 on pci0
uhci0: [GIANT-LOCKED]
usb0: <Intel 82801AA (ICH) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ums0: Microsoft Microsoft IntelliMouse\M-. Explorer, rev 1.10/1.07, addr 2,
iclass 3/1
ums0: 5 buttons and Z dir.
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
pci0: <multimedia, audio> at device 31.5 (no driver attached)
acpi_button0: <Power Button> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
fdc0: <floppy drive controller> port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0: <ECP parallel printer port> port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on
acpi0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
orm0: <ISA Option ROMs> at iomem 0xd0000-0xd3fff,0xc0000-0xc9fff on isa0
pmtimer0 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 847428179 Hz quality 800
Timecounters tick every 1.000 msec
IP Filter: v3.4.35 initialized. Default = block all, Logging = enabled
acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0%
ad0: 2014MB <WDC AC22100H/10.07H09> [4092/16/63] at ata0-master WDMA2
ata1-slave: FAILURE - ATA_IDENTIFY timed out
ata1-slave: FAILURE - ATA_IDENTIFY timed out
ata1-slave: FAILURE - ATA_IDENTIFY timed out
acd0: CDRW <CD-W54E/1.1B> at ata1-master PIO4
da0 at ahc0 bus 0 target 0 lun 0
da0: <SEAGATE ST32430N 0712> Fixed Direct Access SCSI-2 device
da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled
da0: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C)
Mounting root from ufs:/dev/da0s1a
First off, I removed the original HDD to preserve the Windows installation.
This install was done to an old 2GB drive that was laying around. The drive
is known good - I previously installed 4.10 REL to the drive, and have since
verified it was working again. Anyway, during the install I got numerous
errors while trying to format the slices. I finally managed to find settings
that allowed this stage of the install to proceed, only to get more errors
about the volume being full. I used the following slice sizes:
128MB on ad0s1a for /
128MB on ad0s1b for <swap>
64MB for ad0s1d for /var
1694 for ad0s1e for /usr
The install had a real issue with /usr, until I manually newfs'ed using -U -O2
-b 4096. With the default settings, the installer would complain that it
couldn't complete the operation. Once it failed, the installed couldn't see
the drive at all anymore, and I had to restart the installer.
After that hurdle was crossed, I ran into another. The installed got halfway
through the base package, and complained that it was out of diskspace (I have
another 5.3 system with almost identical slice sizes, and / is only 34%
full). Needless to say, the install didn't go very well. I tried several
times, and it finally made it through the first-stage install. During the
first boot, when you are supposed to type random junk to initialize the
entropy file, it crapped out again complaining that it couldn't write to the
disk. The boot sequence continued with a great deal of errors, until I was
finally able to login - except that all of the configuration files were
filled with random junk. (literally junk - resolv.conf had 20 lines of random
characters in it) I chalked it up to a bad drive, and replaced it with
another older HDD (this time a 1.3GB drive)
I used the same partition sizes, and got similar results. So, I installed an
Adaptec 2940AU, and an old 2GB SCSI hard disk. This time, the install went
fine (though gruellingly slow). The system made it through the first boot
with no problems, and I was able to login and check things out - all looked
great. The system is excruciatingly slow, but stable.
So, I reinstalled the first ATA drive, and attempted to manually install
FreeBSD on it. I created the slice structure, and mounted everything at /mnt
- and proceeded to "copy -Rp /<dir> ." stuff over. I started getting the
filesystem full errors again, ala:
pid 781 (cp), uid 0 inumber 6174 on /mnt: filesystem full
pid 781 (cp), uid 0 inumber 6175 on /mnt: filesystem full
pid 781 (cp), uid 0 inumber 6176 on /mnt: filesystem full
pid 781 (cp), uid 0 inumber 6177 on /mnt: filesystem full
pid 781 (cp), uid 0 inumber 6178 on /mnt: filesystem full
pid 781 (cp), uid 0 inumber 6179 on /mnt: filesystem full
pid 781 (cp), uid 0 inumber 6180 on /mnt: filesystem full
pid 781 (cp), uid 0 inumber 6181 on /mnt: filesystem full
It crapped out on /rescue. On the SCSI disk, /rescue is 3.5MB. When I checked
the ATA drive after stopping the copy, the directory was at 95MB (and the
filesystem hopelessly full at 109%). I tried again using copy with the same
results. Then, I tar'ed the folder, and extracted the tar file to the ATA
drive. That worked, the folder was 3.5MB just like the SCSI drive. I found I
could move files reliably from the SCSI drive to the ATA drive using tar, but
not cp.
I can (so far) copy files between slices on the same disk with cp without
error. For example, I can copy a binary from /usr to /, and the file is
identical.
Note, this system has the i810 chipset, which tops out at UDMA/66 - however,
the drive is so old, that it only supports WDMA2 (16MB/s) I am using a 40
conductor ATA cable, which shouldn't be a problem at these low speeds.
The second problem is equally pernicious - the system doesn't reliably reboot.
Sometimes, I can command a reboot and the system will boot normally. Other
times, it will hang at "rebooting". I haven't seen a pattern form yet, but
this is a serious problem for a machine with is supposed to be available
24/7. One note, when this occurs, I have to hold the power button in for the
4-seconds required for a manual power off. The machine is completely hung
(keyboard lights are stuck) I have a suspicion that this is ACPI related -
but, there is problem three.
The machine will not boot if turn off ACPI. If I attempt to boot without ACPI,
I get a kernel panic reliably. I have managed to boot into safe mode, though.
I haven't attempted to remove ACPI from the kernel configuration, given this
- but this is (literally) a testbed at the moment, so I'm open to trying
anything. Unfortunately, there aren't any controls in the BIOS to disable
ACPI - the machine was literally designed for Windows. All I can do is set
whether a PnP OS is in use. (this is currently set to FALSE)
At the moment, it looks like I may have to revert to 4.10 on this machine -
which isn't too big a deal, except that 5.3 did fix one thing - the unusually
long latency for my dual-port NIC card.
Regards,
Seth Henry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412171355.18153.jshamlet>