Asus M2A-VM HDMI - FreeBSD
For hardware info, see the main page.
This machine runs the amd64 version of FreeBSD.
new ("quiet") the internal ide drive is sliced up like this:
root@kg-quiet# gpart show -p ad0 => 63 312581745 ad0 MBR (149G) 63 78140097 ad0s1 freebsd (37G) RELENG_7 78140160 78140160 ad0s2 freebsd (37G) RELENG_6 156280320 78140160 ad0s3 freebsd [active] (37G) RELENG_8 - FreeBSD 8.3-stable 234420480 78156225 ad0s4 freebsd (37G) 312576705 5103 - free - (2.5M)
old: The first sata drive (ad4) is sliced up like this:
slice 1 - 120 GB - a FreeBSD install (RELENG_7) slice 2 - 120 GB - a NetBSD install slice 3 - 111 GB - a FreeBSD install (RELENG_6) slice 4 - 111 GB - a FreeBSD install (RELENG_8)
work log
2013-02-12: ad0s3 - some needed changes. In /boot/loader.conf - sound driver:
snd_hda_load="YES"
comment out the sbp driver (firewire) - it's not needed anymore.
#sbp_load="YES"
That's it.
2013-02-12: ad0s3 - The new "quiet" machine. dmesg output: normal, verbose.
root@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #2: Fri Jan 4 19:18:15 CET 2013 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
from dmesg:
CPU: AMD Phenom(tm) 9500 Quad-Core Processor (2199.93-MHz K8-class CPU) real memory = 8589934592 (8192 MB) avail memory = 8115838976 (7739 MB)
that's all.
2012-07-26: slice 4 - after the crash, check and start the virtual machines again:
tingo@kg-vm$ VBoxManage list vms "FreeBSD-v3" {003ebcaa-1c74-4672-86af-6493341287e7} "xubuntu-v4" {07826334-8d9a-4c68-8132-b9cc4cea67a8} "FreeBSD-v5" {5312412c-353b-41bf-9535-497e1c45de44} tingo@kg-vm$ VBoxManage list runningvms
start v3:
tingo@kg-vm$ VBoxManage startvm FreeBSD-v3 -type headless Waiting for the VM to power on... VM has been successfully started.
start v5:
tingo@kg-vm$ VBoxManage startvm FreeBSD-v5 -type headless Waiting for the VM to power on... VM has been successfully started.
check that they are running:
tingo@kg-vm$ VBoxManage list runningvms "FreeBSD-v3" {003ebcaa-1c74-4672-86af-6493341287e7} "FreeBSD-v5" {5312412c-353b-41bf-9535-497e1c45de44}
The rest is on the vm's page.
2012-07-26: slice 4 - the server had a kernel panic again (MCA), and hung in the dump routine (at 31%). After reboot, no core dumps. The change point in /var/log/messages:
Jul 26 22:50:15 kg-vm ntpd[1845]: kernel time sync status change 6001 Jul 26 23:49:42 kg-vm syslogd: kernel boot file is /boot/kernel/kernel
output from 'last':
root@kg-vm# last tingo pts/0 kg-u35jc.kg4.no Thu Jul 26 23:50 still logged in root ttyv0 Thu Jul 26 23:49 still logged in reboot ~ Thu Jul 26 23:49 tingo pts/2 kg-v2.kg4.no Sat Jul 21 13:58 - 14:18 (00:20) tingo pts/1 kg-v2.kg4.no Sat Jul 21 13:51 - crash (5+09:58) tingo pts/0 kg-u35jc.kg4.no Sat Jul 21 13:49 - 14:33 (2+00:43) root ttyv0 Sat Jul 21 13:49 - crash (5+10:00) reboot ~ Sat Jul 21 13:48 tingo pts/1 kg-u35jc.kg4.no Thu Jul 12 00:01 - crash (9+13:47) tingo pts/1 kg-u35jc.kg4.no Mon Jul 9 19:04 - 23:00 (03:56) tingo pts/1 kg-u35jc.kg4.no Fri Jul 6 18:32 - 18:46 (2+00:13) wtmp begins Wed Jul 4 16:11:14 CEST 2012
That's it.
2012-07-21: slice 4 - after the crash, check and start the virtual machines again:
tingo@kg-vm$ VBoxManage list vms "FreeBSD-v3" {003ebcaa-1c74-4672-86af-6493341287e7} "xubuntu-v4" {07826334-8d9a-4c68-8132-b9cc4cea67a8} "FreeBSD-v5" {5312412c-353b-41bf-9535-497e1c45de44} tingo@kg-vm$ tingo@kg-vm$ VBoxManage list runningvms tingo@kg-vm$
OK. none is running. Start v3:
tingo@kg-vm$ VBoxManage startvm FreeBSD-v3 -type headless Waiting for the VM to power on... VM has been successfully started.
Start v5:
tingo@kg-vm$ VBoxManage startvm FreeBSD-v5 -type headless Waiting for the VM to power on... VM has been successfully started.
Check that they are running:
tingo@kg-vm$ VBoxManage list runningvms "FreeBSD-v3" {003ebcaa-1c74-4672-86af-6493341287e7} "FreeBSD-v5" {5312412c-353b-41bf-9535-497e1c45de44}
OK. The rest is on the virtual machines page.
2012-07-21: slice 4 - the machine hung (totally, no response from keyboard) and had to be reset (reset switch). No info on console, and no info in logs afterwards. last says this:
root@kg-vm# last tingo pts/1 kg-v2.kg4.no Sat Jul 21 13:51 still logged in tingo pts/0 kg-u35jc.kg4.no Sat Jul 21 13:49 still logged in root ttyv0 Sat Jul 21 13:49 still logged in reboot ~ Sat Jul 21 13:48 tingo pts/1 kg-u35jc.kg4.no Thu Jul 12 00:01 - crash (9+13:47) tingo pts/1 kg-u35jc.kg4.no Mon Jul 9 19:04 - 23:00 (03:56) tingo pts/1 kg-u35jc.kg4.no Fri Jul 6 18:32 - 18:46 (2+00:13) wtmp begins Wed Jul 4 16:11:14 CEST 2012
And the change point in /var/log/messages is here:
Jul 21 02:48:49 kg-vm ntpd[1844]: kernel time sync status change 2001 Jul 21 13:48:31 kg-vm syslogd: kernel boot file is /boot/kernel/kernel
No crash dump. What else?
2012-03-13: slice 4 - the machine hung (totally, no response from keyboard) and had to be reset (reset switch). No info in logs afterwards.
2012-02-09: slice 4 - the server had a kernel panic again (MCA again):
root@kg-vm# head -45 /var/crash/core.txt.2 kg-vm.kg4.no dumped core - see /var/crash/vmcore.2 Thu Feb 9 18:45:33 CET 2012 FreeBSD kg-vm.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Dec 17 17:47:43 CET 2011 root@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 panic: machine check trap GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: MCA: Bank 0, Status 0xb431a00000000145 MCA: Global Cap 0x0000000000000106, Status 0x0000000000000007 MCA: Vendor "AuthenticAMD", ID 0x100f22, APIC ID 2 MCA: CPU 2 UNCOR DCACHE L1 DWR error MCA: Address 0x5e343b80 Fatal trap 28: machine check trap while in user mode cpuid = 2; apic id = 02 instruction pointer = 0x43:0x80070c74b stack pointer = 0x3b:0x7fffffffe248 frame pointer = 0x3b:0x8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 3, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 61474 (initial thread) trap number = 28 panic: machine check trap cpuid = 2 KDB: stack backtrace: #0 0xffffffff80614b0e at kdb_backtrace+0x5e #1 0xffffffff805e1d77 at panic+0x187 #2 0xffffffff808ce180 at trap_fatal+0x290 #3 0xffffffff808ce6ba at trap+0x10a #4 0xffffffff808b5f04 at calltrap+0x8 Uptime: 18d8h5m9s Dumping 619 out of 3951 MB:..3%..11%..21%..31%..42%..52%..62%..73%..81%..91% root@kg-vm#
That's all.
2012-01-22: slice 4 - trying to install the VirtualBox extension pack:
tingo@kg-vm$ VBoxManage extpack install ~/dl/Oracle_VM_VirtualBox_Extension_Pack-4.0.8-71778.vbox-extpack 0%... Progress state: NS_ERROR_FAILURE VBoxManage: error: Failed to install "/home/tingo/dl/Oracle_VM_VirtualBox_Extension_Pack-4.0.8-71778.vbox-extpack": The installer failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): Device not configured tingo@kg-vm$
Ok, that isn't going to work.
2012-01-22: slice 4 - Fixing VirtualBox for networking and usb support (bridged network worked without this): networking, temporary:
root@kg-vm# ll /dev/vb* crw------- 1 root wheel 0, 148 Jan 21 23:37 /dev/vboxdrv0 crw------- 1 root wheel 0, 154 Jan 21 20:52 /dev/vboxdrv1 crw------- 1 root wheel 0, 127 Jan 21 21:08 /dev/vboxnetctl root@kg-vm# chown root:vboxusers /dev/vboxnetctl root@kg-vm# chmod 0660 /dev/vboxnetctl root@kg-vm# ll /dev/vb* crw------- 1 root wheel 0, 148 Jan 21 23:37 /dev/vboxdrv0 crw------- 1 root wheel 0, 154 Jan 21 20:52 /dev/vboxdrv1 crw-rw---- 1 root vboxusers 0, 127 Jan 21 21:08 /dev/vboxnetctl
networking, permanent: add this to /etc/devfs.conf:
own vboxnetctl root:vboxusers perm vboxnetctl 0660
usb support: set up for devs.rules in /etc/rc.conf by adding this line:
# enable rules in /etc/devfs.rules
devfs_system_ruleset="devfsrules_local"
create /etc/devfs.rules with this content:
[devfsrules_local=5]
add path 'usb/*' mode 0660 group operator
restart devfs:
root@kg-vm# service devfs restart
and now your vbox user can see see the usb devices (if he is a member of the operator group).
2012-01-21: slice 4 - the virtual machines now looks like this:
tingo@kg-vm$ VBoxManage list vms "FreeBSD-v3" {003ebcaa-1c74-4672-86af-6493341287e7} "xubuntu-v4" {07826334-8d9a-4c68-8132-b9cc4cea67a8}
which ones are running:
tingo@kg-vm$ VBoxManage list runningvms "xubuntu-v4" {07826334-8d9a-4c68-8132-b9cc4cea67a8}
only the Xubuntu one. Start the other one:
tingo@kg-vm$ VBoxManage startvm FreeBSD-v3 -type headless Waiting for the VM to power on... VM has been successfully started.
That's it.
2012-01-21: slice 4 - edited /etc/X11/xorg.conf to switch to the radeon driver, because the radeonhd drive (now deprecated) would lock up the machine. It works now. From /var/log/Xorg.0.log:
(--) PCI:*(0:1:5:0) 1002:791e:1043:826d ATI Technologies Inc RS690 [Radeon X1200 Series] rev 0, Mem @ 0xf0000000/134217728, 0xfdcf0000/65536, 0xfdb00000/1048576, I/O @ 0x0000de00/256, BIOS @ 0x????????/65536 (II) Primary Device is: PCI 01@00:05:0 (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support (II) RADEON(0): TOTO SAYS 00000000fdcf0000 (II) RADEON(0): MMIO registers at 0x00000000fdcf0000: size 64KB (II) RADEON(0): PCI bus 1 card 5 func 0 (**) RADEON(0): Depth 24, (--) framebuffer bpp 32 (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) (==) RADEON(0): Default visual is TrueColor (II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (==) RADEON(0): RGB weight 888 (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) (--) RADEON(0): Chipset: "ATI Radeon X1200" (ChipID = 0x791e) (--) RADEON(0): Linear framebuffer at 0x00000000f0000000 (II) RADEON(0): PCI card detected (II) RADEON(0): ATOM BIOS Rom: SubsystemVendorID: 0x1043 SubsystemID: 0x826d IOBaseAddress: 0xde00 Filename: BR26529.bin BIOS Bootup Message: ATI Radeon Xpress ?1250? for Asus/M2A-VM (II) RADEON(0): Framebuffer space used by Firmware (kb): 16 (II) RADEON(0): Start of VRAM area used by Firmware: 0x7ffc000 (II) RADEON(0): AtomBIOS requests 16kB of VRAM scratch space (II) RADEON(0): AtomBIOS VRAM scratch base: 0x7ffc000 (II) RADEON(0): Cannot get VRAM scratch space. Allocating in main memory instead (II) RADEON(0): Default Engine Clock: 400000 (II) RADEON(0): Default Memory Clock: 200000 (II) RADEON(0): Maximum Pixel ClockPLL Frequency Output: 1200000 (II) RADEON(0): Minimum Pixel ClockPLL Frequency Output: 0 (II) RADEON(0): Maximum Pixel ClockPLL Frequency Input: 13500 (II) RADEON(0): Minimum Pixel ClockPLL Frequency Input: 1000 (II) RADEON(0): Maximum Pixel Clock: 400000 (II) RADEON(0): Reference Clock: 14320 (II) RADEON(0): Will try to use DMA for Xv image transfers (II) RADEON(0): Generation 2 PCI interface, using max accessible memory (II) RADEON(0): Detected total video RAM=131072K, accessible=131072K (PCI BAR=131072K) (--) RADEON(0): Mapped VideoRAM: 131072 kByte (128 bit DDR SDRAM) (II) RADEON(0): Color tiling enabled by default (II) RADEON(0): Supported detailed timing: (II) RADEON(0): clock: 148.5 MHz Image Size: 477 x 268 mm (II) RADEON(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0 (II) RADEON(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0 (II) RADEON(0): Serial No: 72904847SL0 (II) RADEON(0): Ranges: V min: 50 V max: 76 Hz, H min: 24 H max: 83 kHz, PixClock max 170 MHz (II) RADEON(0): Monitor name: BenQ G2220HD II) RADEON(0): Using exact sizes for initial modes (II) RADEON(0): Output VGA-0 using initial mode 1920x1080 (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated. (**) RADEON(0): Display dimensions: (480, 270) mm (**) RADEON(0): DPI set to (101, 180)
That's it.
2011-12-17: slice 4 - I upgraded to latest FreeBSD 8.2-stable, using csup and make world. dmesg output: normal, verbose.
root@kg-vm# uname -a FreeBSD kg-vm.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Dec 17 17:47:43 CET 2011 root@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
and of course, manual start of VMs again:
tingo@kg-vm$ VBoxManage list vms "FreeBSD-v3" {003ebcaa-1c74-4672-86af-6493341287e7} tingo@kg-vm$ VBoxManage startvm FreeBSD-v3 -type headless Waiting for the VM to power on... VM has been successfully started.
2011-12-17: slice 4 - the server had a kernel panic again. This time it hung in core dump routine, while dumping pages to the disk, thus no core dump. But it was a MCA interrupt again. Afterwards, I had to restart the VMs again:
tingo@kg-vm$ VBoxManage list vms "FreeBSD-v3" {003ebcaa-1c74-4672-86af-6493341287e7} tingo@kg-vm$ VBoxManage startvm FreeBSD-v3 -type headless Waiting for the VM to power on... VM has been successfully started. tingo@kg-vm$
That's all.
2011-11-28: slice 4 - the server had a kernel panic again. This time it hung in core dump routine, while dumping pages to the disk, thus no core dump. But it was a MCA interrupt again.
2011-09-23: slice 4 - the machine had a kernel panic again. Yes, MCA this time too:
root@kg-vm# more /var/crash/info.1 Dump header from device /dev/ad4s1b Architecture: amd64 Architecture Version: 2 Dump Length: 652357632B (622 MB) Blocksize: 512 Dumptime: Fri Sep 23 15:51:49 2011 Hostname: kg-vm.kg4.no Magic: FreeBSD Kernel Dump Version String: FreeBSD 8.2-STABLE #3: Fri Mar 4 21:16:39 CET 2011 root@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC Panic String: machine check trap Dump Parity: 3705971839 Bounds: 1 Dump Status: good
The machine restarted automatically - good. But I had to restart the virtual machine(s) manually: Which vm's do we have?
tingo@kg-vm$ VBoxManage list vms "FreeBSD-v3" {003ebcaa-1c74-4672-86af-6493341287e7}
Ok, let's start it:
tingo@kg-vm$ VBoxManage startvm FreeBSD-v3 -type headless Waiting for the VM to power on... VM has been successfully started. tingo@kg-vm$
That's all.
2011-08-12: dd_rescue, fil, slice 1:
root@kg-vm# ls /dev/da0* /dev/da0 /dev/da0s1b /dev/da0s1f /dev/da0s2d /dev/da0s3 /dev/da0s3e /dev/da0s1 /dev/da0s1d /dev/da0s2 /dev/da0s2e /dev/da0s3a /dev/da0s3f /dev/da0s1a /dev/da0s1e /dev/da0s2a /dev/da0s2f /dev/da0s3d root@kg-vm# dd_rescue -v -l /storage/fil-s1.log.txt -o /storage/fil-s1.bb.txt /dev/da0s1 /storage/fil-s1.image dd_rescue: (info): about to transfer 0.0 kBytes from /dev/da0s1 to /storage/fil-s1.image dd_rescue: (info): blocksizes: soft 65536, hard 512 dd_rescue: (info): starting positions: in 0.0k, out 0.0k dd_rescue: (info): Logfile: /storage/fil-s1.log.txt, Maxerr: 0 dd_rescue: (info): Reverse: no , Trunc: no , interactive: no dd_rescue: (info): abort on Write errs: no , spArse write: if err dd_rescue: (info): ipos: 18868224.0k, opos: 18868224.0k, xferd: 18868224.0k errs: 0, errxfer: 0.0k, succxfer: 18868224.0k +curr.rate: 28942kB/s, avg.rate: 24905kB/s, avg.load: 4.3% dd_rescue: (info): problems at ipos 18868288.0k: Unknown error: 0 fall back to smaller blocksize dd_rescue: (info): ipos: 18868288.0k, opos: 18868288.0k, xferd: 18868288.0k * errs: 0, errxfer: 0.0k, succxfer: 18868288.0k +curr.rate: 2201kB/s, avg.rate: 24904kB/s, avg.load: 4.3% dd_rescue: (info): read /dev/da0s1 (18868312.0k): EOF dd_rescue: (info): Summary for /dev/da0s1 -> /storage/fil-s1.image: dd_rescue: (info): ipos: 18868312.0k, opos: 18868312.0k, xferd: 18868312.0k errs: 0, errxfer: 0.0k, succxfer: 18868312.0k +curr.rate: 10195kB/s, avg.rate: 24904kB/s, avg.load: 4.3%
dd_rescue fil, slice 2:
root@kg-vm# dd_rescue -v -l /storage/fil-s2.log.txt -o /storage/fil-s2.bb.txt /dev/da0s2 /storage/fil-s2.image dd_rescue: (warning): read /dev/da0s2 (2368649.0k): Unknown error: 0! ^Cdd_rescue: (fatal): Caught signal 2 "Interrupt: 2". Exiting! dd_rescue: (info): Summary for /dev/da0s2 -> /storage/fil-s2.image: dd_rescue: (info): ipos: 2368649.5k, opos: 2368649.5k, xferd: 2368649.5k errs: 302227, errxfer: 151113.5k, succxfer: 2217536.0k +curr.rate: 30kB/s, avg.rate: 1499kB/s, avg.load: 2.4% Ok, lots of errors on this one.
dd_rescue fil, slice 3:
root@kg-vm# dd_rescue -v -l /storage/fil-s3.log.txt -o /storage/fil-s3.bb.txt /dev/da0s3 /storage/fil-s3.image dd_rescue: (info): about to transfer 0.0 kBytes from /dev/da0s3 to /storage/fil-s3.image dd_rescue: (info): blocksizes: soft 65536, hard 512 dd_rescue: (info): starting positions: in 0.0k, out 0.0k dd_rescue: (info): Logfile: /storage/fil-s3.log.txt, Maxerr: 0 dd_rescue: (info): Reverse: no , Trunc: no , interactive: no dd_rescue: (info): abort on Write errs: no , spArse write: if err dd_rescue: (info): ipos: 18873344.0k, opos: 18873344.0k, xferd: 18873344.0k errs: 0, errxfer: 0.0k, succxfer: 18873344.0k +curr.rate: 22878kB/s, avg.rate: 25588kB/s, avg.load: 4.3% dd_rescue: (info): problems at ipos 18874240.0k: Unknown error: 0 fall back to smaller blocksize dd_rescue: (info): ipos: 18874240.0k, opos: 18874240.0k, xferd: 18874240.0k * errs: 0, errxfer: 0.0k, succxfer: 18874240.0k +curr.rate: 19581kB/s, avg.rate: 25588kB/s, avg.load: 4.3% dd_rescue: (info): read /dev/da0s3 (18874296.0k): EOF dd_rescue: (info): Summary for /dev/da0s3 -> /storage/fil-s3.image: dd_rescue: (info): ipos: 18874296.0k, opos: 18874296.0k, xferd: 18874296.0k errs: 0, errxfer: 0.0k, succxfer: 18874296.0k +curr.rate: 31532kB/s, avg.rate: 25588kB/s, avg.load: 4.3%
That one looks ok.
2011-07-13: slice 4 - the server had a kernel panic again. This time it hung in core dump routine, while dumping pages to the disk, thus no core dump. But it was a MCA interrupt again.
2011-06-19: dd_rescue, part 3: after an interesting post on the comp.unix.bsd.freebsd.misc newsgroup, I'm now trying to make an image of the whole slice. Here goes:
root@kg-vm# dd_rescue -v -l /storage/web-usr-hd3.log.txt -o /storage/web-usr-hd3.bb.txt /dev/da0s1 /storage/web-usr-hd3.image
We'll see how that works out. Seems to have worked well:
root@kg-vm# dd_rescue -v -l /storage/web-usr-hd3.log.txt -o /storage/web-usr-hd3.bb.txt /dev/da0s1 /storage/web-usr-hd3.image dd_rescue: (info): about to transfer 0.0 kBytes from /dev/da0s1 to /storage/web-usr-hd3.image dd_rescue: (info): blocksizes: soft 65536, hard 512 dd_rescue: (info): starting positions: in 0.0k, out 0.0k dd_rescue: (info): Logfile: /storage/web-usr-hd3.log.txt, Maxerr: 0 dd_rescue: (info): Reverse: no , Trunc: no , interactive: no dd_rescue: (info): abort on Write errs: no , spArse write: if err dd_rescue: (info): ipos: 101998592.0k, opos: 101998592.0k, xferd: 101998592.0k errs: 0, errxfer: 0.0k, succxfer: 101998592.0k +curr.rate: 22813kB/s, avg.rate: 22418kB/s, avg.load: 3.8% dd_rescue: (info): problems at ipos 101999104.0k: Unknown error: 0 fall back to smaller blocksize dd_rescue: (info): ipos: 101999104.0k, opos: 101999104.0k, xferd: 101999104.0k * errs: 0, errxfer: 0.0k, succxfer: 101999104.0k +curr.rate: 43kB/s, avg.rate: 22360kB/s, avg.load: 3.8% dd_rescue: (info): read /dev/da0s1 (101999136.0k): EOF dd_rescue: (info): Summary for /dev/da0s1 -> /storage/web-usr-hd3.image: dd_rescue: (info): ipos: 101999136.0k, opos: 101999136.0k, xferd: 101999136.0k errs: 0, errxfer: 0.0k, succxfer: 101999136.0k +curr.rate: 8kB/s, avg.rate: 22341kB/s, avg.load: 3.8%
Now, time to do something more. Let's try to mount it:
root@kg-vm# mdconfig -f /storage/web-usr-hd3.image md0 root@kg-vm# ls /dev/md0* /dev/md0 /dev/md0a /dev/md0b /dev/md0d /dev/md0e /dev/md0f
It got all the partitions right too. Cool! Let us find out what fsck thinks:
root@kg-vm# fsck_ufs -y /dev/md0f ** /dev/md0f CANNOT READ BLK: 220542432 CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 220542432, 220542433, 220542434, 220542435, ioctl (GCINFO): Inappropriate ioctl for device fsck_ufs: /dev/md0f: can't read disk label
Not so good. Does the other partitions check out:
root@kg-vm# fsck_ufs -y /dev/md0e ** /dev/md0e ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 90 files, 2834 used, 250981 free (37 frags, 31368 blocks, 0.0% fragmentation) ***** FILE SYSTEM IS CLEAN ***** root@kg-vm# fsck_ufs -y /dev/md0d ** /dev/md0d ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1841 files, 91812 used, 651043 free (915 frags, 81266 blocks, 0.1% fragmentation) ***** FILE SYSTEM IS CLEAN ***** root@kg-vm# fsck_ufs -y /dev/md0a ** /dev/md0a ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 2920 files, 138604 used, 115211 free (1235 frags, 14247 blocks, 0.5% fragmentation) ***** FILE SYSTEM IS CLEAN *****
Yes, they are ok. fsck -b then:
root@kg-vm# fsck_ufs -y -b 160 /dev/md0f
lots of output then ends like this:
UPDATE STANDARD SUPERBLOCK? yes WRITING ZERO'ED BLOCK 220542464 TO DISK UNEXPECTED SOFT UPDATE INCONSISTENCY CANNOT WRITE BLK: 220542464 UNEXPECTED SOFT UPDATE INCONSISTENCY CONTINUE? yes THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 220542464, 220542465, 220542466, 220542467, 220542468, 220542469, 220542470, 220542471, 220542472, 220542473, 220542474, 220542475, 220542476, 220542477, 220542478, 220542479, 220542480, 220542481, 220542482, 220542483, 220542484, 220542485, 220542486, 220542487, 220542488, 220542489, 220542490, 220542491, 220542492, 220542493, 220542494, 220542495, ***** FILE SYSTEM MARKED DIRTY ***** ***** FILE SYSTEM WAS MODIFIED ***** ***** PLEASE RERUN FSCK *****
So, it didn't work any better.
2011-06-16: dd_rescue, after part 2: try to fsck the image:
root@kg-vm# mdconfig -f /storage/web-usr-hd2.image md0 root@kg-vm# fsck_ufs -y /dev/md0 ** /dev/md0 CANNOT READ BLK: 220542432 CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 220542432, 220542433, 220542434, 220542435, ioctl (GCINFO): Inappropriate ioctl for device fsck_ufs: /dev/md0: can't read disk label
Ouch! Ok, I re-tried with the alternate superblock:
root@kg-vm# fsck_ufs -y -b 160 /dev/md0 which produced lots of output, then this: ***** FILE SYSTEM MARKED DIRTY ***** ***** FILE SYSTEM WAS MODIFIED ***** ***** PLEASE RERUN FSCK *****
Ok, Again:
root@kg-vm# fsck_ufs -y -b 160 /dev/md0
Still got this:
THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 190450044, 190450045, 190450046, 190450047, ***** FILE SYSTEM MARKED DIRTY ***** ***** FILE SYSTEM WAS MODIFIED ***** ***** PLEASE RERUN FSCK *****
One more time, but it didn't change. Let's try the normal fsck incantation:
root@kg-vm# fsck_ufs -y /dev/md0 ** /dev/md0 CANNOT READ BLK: 220542432 CONTINUE? yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 220542432, 220542433, 220542434, 220542435, ioctl (GCINFO): Inappropriate ioctl for device fsck_ufs: /dev/md0: can't read disk label
Nope, it still doesn't work.
2011-06-16: dd_rescue operation, part 2: I will try to make a new image of the damaged hard disk partition, this time with a dd_rescue log file. But first, I must save a copy of the image a made last time (just in case). So I attach an external hard drive:
root@kg-vm# gpart show da0 => 63 976773105 da0 MBR (466G) 63 668410 - free - (326M) 668473 20478 1 !12 (10M) 688951 976084217 - free - (465G)
add a partition:
root@kg-vm# gpart add -t freebsd da0 da0s2 added root@kg-vm# gpart show da0 => 63 976773105 da0 MBR (466G) 63 668410 - free - (326M) 668473 20478 1 !12 (10M) 688951 17 - free - (8.5K) 688968 976084200 2 freebsd (465G)
Plenty of space. I chickened out again, and used sysinstall to label and newfs the partition, resulting in this:
root@kg-vm# df -h /media Filesystem Size Used Avail Capacity Mounted on /dev/da0s2d 451G 4.0K 415G 0% /media
Copy the image:
root@kg-vm# cp -pv /storage/web-usr-hd.image /media
and delete it from /storage:
root@kg-vm# rm /storage/web-usr-hd.image
then unmount the external disk
root@kg-vm# umount /media
Now we are ready to connect the old, bad disk and run dd_rescue again: old disk shows up as da0 too:
root@kg-vm# ls /dev/da0* /dev/da0 /dev/da0s1 /dev/da0s1a /dev/da0s1b /dev/da0s1d /dev/da0s1e /dev/da0s1f
I want the da0s1f partition:
root@kg-vm# dd_rescue -v -l /storage/web-usr-hd2.log.txt -o /storage/web-usr-hd2.bb.txt /dev/da0s1f /storage/web-usr-hd2.image
we'll find out how that goes.
root@kg-vm# dd_rescue -v -l /storage/web-usr-hd2.log.txt -o /storage/web-usr-hd2.bb.txt /dev/da0s1f /storage/web-usr-hd2.image dd_rescue: (info): about to transfer 0.0 kBytes from /dev/da0s1f to /storage/web-usr-hd2.image dd_rescue: (info): blocksizes: soft 65536, hard 512 dd_rescue: (info): starting positions: in 0.0k, out 0.0k dd_rescue: (info): Logfile: /storage/web-usr-hd2.log.txt, Maxerr: 0 dd_rescue: (info): Reverse: no , Trunc: no , interactive: no dd_rescue: (info): abort on Write errs: no , spArse write: if err dd_rescue: (info): ipos: 95216640.0k, opos: 95216640.0k, xferd: 95216640.0k errs: 0, errxfer: 0.0k, succxfer: 95216640.0k +curr.rate: 22943kB/s, avg.rate: 22206kB/s, avg.load: 3.7% dd_rescue: (info): problems at ipos 95217152.0k: Unknown error: 0 fall back to smaller blocksize dd_rescue: (info): ipos: 95217152.0k, opos: 95217152.0k, xferd: 95217152.0k * errs: 0, errxfer: 0.0k, succxfer: 95217152.0k +curr.rate: 35kB/s, avg.rate: 22132kB/s, avg.load: 3.7% dd_rescue: (info): read /dev/da0s1f (95217184.0k): EOF dd_rescue: (info): Summary for /dev/da0s1f -> /storage/web-usr-hd2.image: dd_rescue: (info): ipos: 95217184.0k, opos: 95217184.0k, xferd: 95217184.0k errs: 0, errxfer: 0.0k, succxfer: 95217184.0k +curr.rate: 7kB/s, avg.rate: 22108kB/s, avg.load: 3.7%
That is it. Let's see if the files are there:
root@kg-vm# ls -lh /storage total 95263732 drwxrwxr-x 2 root operator 512B Jun 1 21:07 .snap -rw-r----- 1 root wheel 91G Jun 16 23:01 web-usr-hd2.image -rw-r----- 1 root wheel 1.8K Jun 16 23:01 web-usr-hd2.log.txt
Hmm, no error block file.
2011-06-05: slice 4 - Xorg: when using startxfce4, it takes many minutes (more than ten) before the desktop comes up. /var/log/Xorg.0.log doesn't contain anything that looks suspicious, and the only "interesting" lines in /var/log/messages are these:
Jun 4 23:26:57 kg-vm kernel: drm0: <ATI Radeon RS690 X1250 IGP> on vgapci0 Jun 4 23:26:57 kg-vm kernel: info: [drm] MSI enabled 1 message(s) Jun 4 23:26:57 kg-vm kernel: info: [drm] Initialized radeon 1.31.0 20080613 Jun 4 23:50:59 kg-vm kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 465, size: 4096 Jun 4 23:50:59 kg-vm sshd[24977]: error: ssh_msg_send: write Jun 4 23:55:05 kg-vm kernel: info: [drm] Setting GART location based on new memory map Jun 4 23:55:05 kg-vm kernel: info: [drm] Loading RS690/RS740 Microcode Jun 4 23:55:05 kg-vm kernel: info: [drm] Num pipes: 1 Jun 4 23:55:05 kg-vm kernel: info: [drm] writeback test succeeded in 1 usecs Jun 4 23:55:05 kg-vm kernel: drm0: [ITHREAD]
Notice the times in the log. If I try startx, it doesn't take long:
Jun 5 23:40:27 kg-vm kernel: info: [drm] Setting GART location based on new memory map Jun 5 23:40:27 kg-vm kernel: info: [drm] Loading RS690/RS740 Microcode Jun 5 23:40:27 kg-vm kernel: info: [drm] Num pipes: 1 Jun 5 23:40:27 kg-vm kernel: info: [drm] writeback test succeeded in 1 usecs Jun 5 23:40:27 kg-vm kernel: drm0: [ITHREAD] Jun 5 23:40:40 kg-vm kernel: info: [drm] Num pipes: 1
Strange. Ok, now startxfce4 doesn't take long either. It seems it s only the first start that takes extra long time.
2011-06-01: Then I use dd_rescue to recover data from a FreeBSD partition with bad blocks:
root@kg-vm# dd_rescue -v /dev/da0s1f /Storage/web-usr-hd.image
we will see how that works out. This is the /usr partition (102 GB) on the old, broken hard drive of the machine web. It ended like this:
root@kg-vm# dd_rescue -v /dev/da0s1f /storage/web-usr-hd.image dd_rescue: (info): about to transfer 0.0 kBytes from /dev/da0s1f to /storage/web-usr-hd.image dd_rescue: (info): blocksizes: soft 65536, hard 512 dd_rescue: (info): starting positions: in 0.0k, out 0.0k dd_rescue: (info): Logfile: (none), Maxerr: 0 dd_rescue: (info): Reverse: no , Trunc: no , interactive: no dd_rescue: (info): abort on Write errs: no , spArse write: if err dd_rescue: (info): ipos: 95216640.0k, opos: 95216640.0k, xferd: 95216640.0k errs: 0, errxfer: 0.0k, succxfer: 95216640.0k +curr.rate: 22627kB/s, avg.rate: 26328kB/s, avg.load: 4.8% dd_rescue: (info): problems at ipos 95217152.0k: Unknown error: 0 fall back to smaller blocksize dd_rescue: (info): ipos: 95217152.0k, opos: 95217152.0k, xferd: 95217152.0k * errs: 0, errxfer: 0.0k, succxfer: 95217152.0k +curr.rate: 30kB/s, avg.rate: 26204kB/s, avg.load: 4.8% dd_rescue: (info): read /dev/da0s1f (95217184.0k): EOF dd_rescue: (info): Summary for /dev/da0s1f -> /storage/web-usr-hd.image: dd_rescue: (info): ipos: 95217184.0k, opos: 95217184.0k, xferd: 95217184.0k errs: 0, errxfer: 0.0k, succxfer: 95217184.0k +curr.rate: 7kB/s, avg.rate: 26171kB/s, avg.load: 4.8%
Hmm, no errors reported. Let's try to mount it:
root@kg-vm# mdconfig -f /storage/web-usr-hd.image md0 root@kg-vm# mount /dev/md0 /media root@kg-vm# df -h /media Filesystem Size Used Avail Capacity Mounted on /dev/md0 102G 3.5G 90G 4% /media
so far, so good. Later, I found that therer are some errors in the backup.
2011-06-01: let me try to add some more space to FreeBSD:
root@kg-vm# gpart show ad4 => 63 976773105 ad4 MBR (466G) 63 253746612 1 freebsd (121G) 253746675 253746675 2 !169 (121G) 507493350 234870300 3 freebsd (112G) 742363650 234409518 4 freebsd [active] (112G)
Ok, ad4 is full. ad6 then:
root@kg-vm# gpart show ad6 => 63 625142385 ad6 MBR (298G) 63 1985 - free - (993K) 2048 150992887 1 linux-data [active] (72G) 150994935 150994935 3 linux-data (72G) 301989870 302745616 - free - (144G) 604735486 20406274 2 ebr (9.7G) 625141760 688 - free - (344K)
Aha, free space! Try to add a partition:
root@kg-vm# gpart add -t freebsd-ufs ad6 gpart: Invalid argument
Hmm, user error?
root@kg-vm# gpart add -t freebsd ad6 ad6s4 added root@kg-vm# gpart show ad6 => 63 625142385 ad6 MBR (298G) 63 1985 - free - (993K) 2048 150992887 1 linux-data [active] (72G) 150994935 150994935 3 linux-data (72G) 301989870 302745555 4 freebsd (144G) 604735425 61 - free - (31K) 604735486 20406274 2 ebr (9.7G) 625141760 688 - free - (344K)
Nice.I then used sysinstall to create a filessystem on ad6s4d and mount it on /storage (yes, I know, I'm a chicken).
root@kg-vm# df -h /storage Filesystem Size Used Avail Capacity Mounted on /dev/ad6s4d 140G 4.0K 129G 0% /storage
And that was it.
2011-05-01: slice 4 - I recompiled ImageMagick with SVG support. Still, no icons in launchers in Xfce. OK, I stopped Xfce,
renamed ~/.config to ~/.config_old and restarted Xfce, which made it ask about default configuration again. That seems to have fixed it.
2011-04-29: slice 4 - The application menu wasn't working in Xfce 4.8. simple fix - reinstall garcon (I used portupgrade -f garcon). Now I only need to fix the launchers. That was icons something, wasn't it?
2011-04-28: slice 4 - I installed Xorg on the machine. In /etc/X11/xorg.conf I corrected gamma by putting this in the "Monitor" section:
Gamma 2.20
We will see if that works.
2011-03-04: slice 4 - I upgraded to FreeBSD 8.2-stable, using csup and make world. dmesg output: normal, verbose.
2011-02-05: slice 4 - I upgraded to latest FreeBSD 8.2-prerelease, using csup. dmesg output: normal, verbose.
2011-01-05: the machine has been running memtest86+ (version 4.10) for about 27 hours now; 19 passes, no errors detected.
2011-01-04: slice 4 - this afternoon I noticed that the server had a kernel panic. It was hanging on the reboot screen (picture), no response from keyboard. When the server was rebooted, it saved core (textdump), here is output from /var/crash/info.0:
root@kg-vm# more /var/crash/info.0 Dump header from device /dev/ad4s1b Architecture: amd64 Architecture Version: 2 Dump Length: 581758976B (554 MB) Blocksize: 512 Dumptime: Tue Jan 4 18:03:33 2011 Hostname: kg-vm.kg4.no Magic: FreeBSD Kernel Dump Version String: FreeBSD 8.2-PRERELEASE #1: Sat Jan 1 23:46:16 CET 2011 root@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC Panic String: machine check trap Dump Parity: 2377774135 Bounds: 0 Dump Status: good
This is the second time the machine has panic'ed with a machine check after upgrading to 8.2-prerelease (I didn't manage to catch the first one, dump device wasn't configured).
2011-01-01: slice 4 - I upgraded to FreeBSD 8.2-prerelease, using csup. dmesg output: normal, verbose.
2010-10-30: slice 4 - I upgraded to latest FreeBSD 8.1-stable, using csup. dmesg output: normal, verbose.
2010-10-29: slice 4 - I installed FreeBSD 8.1-release from a CD. dmesg output: normal, verbose.
2010-09-18: I booted FreeBSD 8.1-release from a usb stick. dmesg output: normal, verbose.
2010-07-04: I upgraded slice 3 to FreeBSD 6.4-stable. dmesg output: normal, verbose. For some reason the network (re0) doesn't work.
2010-07-04: slice 1 - updated to FreeBSD 7.3-stable. dmesg output: normal, verbose. Upgraded the kqemu port.
2010-03-13: slice 1 - updated to FreeBSD 7.3-prerelease. dmesg output: normal, verbose. Upgraded the kqemu port.
2009-10-10: slice 1 - updated to latest FreeBSD 7.2-stable. dmesg output: normal, verbose. Upgraded the kqemu port.
2009-05-29: slice 1 - I upgraded to FreeBSD 7.2-stable. dmesg output: normal. In the "make world" procedure, I replaced 'mergemaster' with '/usr/src/usr.sbin/mergemaster/mergemaster.sh' to avoid the "upgrade files no matter what" bug.
2009-05-17: The module acpi_aiboost works on this machine. After loading, this shows up in /var/log/messages:
May 17 01:27:40 kg-vm kernel: acpi_aiboost0: <ASUStek AIBOOSTER> on acpi0
and I can get data with:
root@kg-vm# sysctl dev.acpi_aiboost dev.acpi_aiboost.0.%desc: ASUStek AIBOOSTER dev.acpi_aiboost.0.%driver: acpi_aiboost dev.acpi_aiboost.0.%location: handle=\_SB_.PCI0.ASOC dev.acpi_aiboost.0.%pnpinfo: _HID=ATK0110 _UID=16843024 dev.acpi_aiboost.0.%parent: acpi0 dev.acpi_aiboost.0.temp0: 340 dev.acpi_aiboost.0.temp1: 340 dev.acpi_aiboost.0.volt0: 1152 dev.acpi_aiboost.0.volt1: 3376 dev.acpi_aiboost.0.volt2: 4945 dev.acpi_aiboost.0.volt3: 11968 dev.acpi_aiboost.0.fan0: 1323 dev.acpi_aiboost.0.fan1: 986 dev.acpi_aiboost.0.fan2: 968
Cool!
2009-01-11: slice 1 - I upgraded to FreeBSD 7.1-stable. dmesg output: normal, verbose. Here is a pciconf -lv output too.
2008-11-02: slice 3 - I added the patch described here for if_re under FreeBSD 6.4-prerelease. This actually makes the re(4) network interface stable and usable. Nice!
2008-09-21: I upgraded slice 3 to FreeBSD 6.4-PRERELEASE. dmesg output: normal, verbose.
2008-09-18: upgraded bios to version 2101. I can't see any change in FreeBSD for better or worse. Here is dmesg output: normal, verbose and dmidecode output for completeness. kenv output for smbios:
root@kg-vm# kenv | grep smb smbios.bios.reldate="08/27/2008" smbios.bios.vendor="Phoenix Technologies, LTD" smbios.bios.version="ASUS M2A-VM HDMI ACPI BIOS Revision 2101" smbios.chassis.maker="Chassis Manufacture" smbios.chassis.serial="EVAL " smbios.chassis.tag="123456789000" smbios.chassis.version="Chassis Version" smbios.planar.maker="ASUSTeK Computer INC." smbios.planar.product="M2A-VM HDMI" smbios.planar.serial="123456789000" smbios.planar.version="1.XX " smbios.socket.enabled="1" smbios.socket.populated="1" smbios.system.maker="System manufacturer" smbios.system.product="System Product Name" smbios.system.serial="System Serial Number" smbios.system.uuid="875b440a-a2b2-6a59-8306-dbacfc5e6107" smbios.system.version="System Version"
2008-08-13: added a patch (http://people.freebsd.org/~mav/hda.20080812.patch) for snd_hda:
cd /usr/src/sys/dev/sound/pci patch < /home/tingo/work/snd_hda-uaa/hda.7.20080812.patch
and rebuilt the module. Now 'cat /dev/sndstat' shows:
root@kg-vm# cat /dev/sndstat FreeBSD Audio Driver (newpcm: 64bit 2007061600/amd64) Installed devices: pcm0: <HDA codec Realtek ALC883 PCM #0> at hdac0 cad 0 kld snd_hda [20080812_0000] [MPSAFE] (1p:1v/1r:1v channels duplex default) pcm1: <HDA codec Realtek ALC883 PCM #1> at hdac0 cad 0 kld snd_hda [20080812_0000] [MPSAFE] (1p:1v/1r:1v channels duplex) pcm2: <HDA codec Realtek ALC883 PCM #2> at hdac0 cad 0 kld snd_hda [20080812_0000] [MPSAFE] (1p:1v/0r:0v channels)
dmesg output (normal, verbose) with the new patch.
2008-08-13: upgraded to latest FreeBSD 7.0-stable. dmesg output: normal, verbose. Output from 'cat /dev/sndstat':
root@kg-vm# cat /dev/sndstat FreeBSD Audio Driver (newpcm: 64bit 2007061600/amd64) Installed devices: pcm0: <ATI SB600 High Definition Audio Controller> at memory 0xfe020000 irq 16 kld snd_hda [20080420_0052] [MPSAFE] (1p:1v/1r:1v channels duplex default)
2008-05-12: well, there still seems to be issues with if_re. I upgraded to latest FreeBSD 7.0-stable, we will see if that fixes it. dmesg output.
2008-04-12: Upgraded to latest FreeBSD 7.0-stable. the ixp 600 sata controller is detected without the need to add any patches. I didn't add any patches for if_re - we'll see how that works out. dmesg output.
2008-03-08: still running FreeBSD 7.0-stable, here s the devinfo -rv: output.
2008-02-28: Now that FreeBSD 7.0 has been released, I decided to upgrade to latest FreeBSD 7.0-stable again. I included the patches for the ixp600 sata controller. dmesg output. kqemu-kmod port upgraded. After the upgrade, I found out that I was wrong about the if_re patches not being needed. The if_re patches are still needed. Added those and rebuilt kernel.
2008-02-23: Upgrade to latest FreeBSD 7.0-stable, with patches for the ixp600 sata controller. Hopefully, the if_re patch isn't needed anymore. kqemu-kmod port upgraded. dmesg output.
2008-01-27: Upgraded to FreeBSD 6.3-stable on slice 3. Here is the dmesg output. The sata patch works, dmesg output with sata patch. if_re does not work reliable (it stops passing traffic after a while, and ssh connections to the machine drops randomly. Actually, if_re didn't work in 6.3-rc2 either, it had the same problems. I tried using a usb NIC (if_ural) instead, but it makes the machine panic after some amount of traffic (example: start csup for ports, it panics in about a couple of minutes). Hard to tell the reason for that.
2008-01-26: upgraded to latest FreeBSD 7.0-stable, with patches for if_re and ixp600 sata controller. dmesg output. kqemu-kmod port upgraded.
2008-01-20: added a patch for the SATA controller (from the FreeBSD-stable mailing list). Afer the patch, all ports on the controller is recognized.
atapci0: <ATI IXP600 SATA300 controller> port 0xfc00-0xfc07,0xf800-0xf803,0xf400-0xf407,0xf000-0xf003,0xec00-0xec0f mem 0xfe02f000-0xfe02f3ff irq 22 at device 18.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: <ATA channel 0> on atapci0 ata2: [ITHREAD] ata3: <ATA channel 1> on atapci0 ata3: [ITHREAD] ata4: <ATA channel 2> on atapci0 ata4: [ITHREAD] ata5: <ATA channel 3> on atapci0 ata5: [ITHREAD]
Very good!
2008-01-15: upgraded to latest FreeBSD 7-stable (RELENG_7). Here is dmesg output. kqemu-kmod port upgraded.
2008-01-11: FreeBSD 7.0-prerelease. Here are dmesg and dmidecode output after bios upgrade to version 1604.
2008-01-04: I modified xorg.conf so that I can start Xorg with either the radeonhd driver or the vesa driver. To start with vesa driver, i use this command: startxfce4 +l -- -screen Screen1 (the '+l' (lowercase L) is just a dummy client parameter).
2008-01-01: Installed FreeBSD 6.3-RC2 on a slice (s3). I did have to do the ifconfig re0 up trick in the rescue shell on vty4 before I could configure
networking in sysinstall. This version of FreeBSD also panics if I have an usb keyboard attached during boot.
Same message as in 7.0-beta4 / RELENG_7. Here is FreeBSD 6.3-rc2 output from dmesg, pciconf -lv, dmidecode, lspci -v.
2007-12-26: Xorg 7.3.1 installed. Xorg.0.log here. The ATI Radeon X1250 chip works with the radeonhd driver.
2007-12-24: Hmm, interesting. If I plug an usb keyboard into the machine after it has booted, it works. dmesg output:
ukbd0: <Logitech USB Receiver, class 0/0, rev 1.10/30.07, addr 2> on uhub2 kbd2 at ukbd0 ums0: <Logitech USB Receiver, class 0/0, rev 1.10/30.07, addr 2> on uhub2 ums0: 16 buttons and Z dir.
usbdevs -v output:
port 2 addr 2: low speed, power 98 mA, config 1, USB Receiver(0xc512), Logitech(0x046d), rev 30.07
However, if I boot the machine with the usb keyboard plugged in, it panics during boot. It doesn't matter which usb port, and what type of usb keyboard I try. If I boot with an usb mouse plugged in, it doesn't panic, but the usb port is disabled.
2007-12-23: cpuid output (misc/cpuid) for reference.
2007-12-23: tried k8temp (sysutils/k8temp), but it didn't work. Error output, k8temp -derror output.
2007-12-23: Installed FreeBSD 7.0-BETA4 on the machine. The amd64 "version" of course. For som reason, the network card didn't work when I tried a bootonly
cd, so I had to use disc1 instead. The network card wasn't working properly during installation, so after reboot i did a ifconfig re0 up and then it worked.
Strange. After putting the required configuration (hostname, ifconfig_re0="DHCP" and so on) in /etc/rc.conf and doing a reboot everything was fine.
Anyway, here is dmesg output, pciconf -lv output, dmidecode output, lspci -v output.