on Karmic, this is sufficient to get ntop to start and log RRD network
data:
sudo apt-get install ntop
sudo install -d /var/lib/ntop
sudo install -o nobody -d /var/lib/ntop/interfaces
sudo install -o nobody -d /var/lib/ntop/rrd
sudo ntop
A little more detail on my blog:
http://johntellsall.blogsp
helps :)
thanks so much!
- john
On Mon, Oct 26, 2009 at 5:18 PM, Leann Ogasawara
wrote:
> Hi JohnMitchell,
>
> The warning reported here typically indicates that it took longer for
> your system to resume from suspend than expected. I believe there is a
> 5 sec barrier whic
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/34376152/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/34376153/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/34376154/ArecordDevices.t
Public bug reported:
no idea, I get this red box saying something about a crash.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be
restarted.
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: johnm 1306
If this helps: I have two 1.5T disks, ext4, and lvm2 in the mix, in
addition to a bunch of usb-disk ports, and of course the normal hard
drive, dvd, and NVidia graphics card.
--
devkit-disks-helper-ata-smart-collect assert failure:
devkit-disks-helper-ata-smart-collect: atasmart.c:2687: sk_disk_
Searching for the "virtual wire irq" led me to our friends at Red Hat,
who have a workaround:
In my case:
qemu-system-x86_64 -hda /var/qemu/vdisk.img -cdrom isos/mini-x86.iso -boot
d
I used the magic string "install noapic" to start the normal install
process.
https://bugzilla.redhat.com/s
I'm getting the identical error as Mike: "MP-BIOS" croaks quite early on
in a qemu-x86_64 boot of a Ubuntu disc.
In my case:
qemu-system-x86_64 -cdrom isos/mini-x86.iso -boot d
If I enable "Command-line expert install" I get slightly more detail:
MP-BIOS bug, trying to set up timer, found ap
